![]() |
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| Solaris BigAdmin RSS BigAdmin RSS Feed from Sun |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| roll 1.1.3 (Default branch) | iBot | Software Releases - RSS News | 0 | 01-29-2008 11:00 AM |
| BitNami serves ready-to-roll CMS stacks | iBot | UNIX and Linux RSS News | 0 | 01-23-2008 03:30 PM |
| In Wake Of SCO Ruling, Linux Continues To Roll - Information Week Weblog | iBot | UNIX and Linux RSS News | 0 | 08-14-2007 01:10 AM |
| Roll back problem | tushar_johri | Shell Programming and Scripting | 3 | 06-17-2005 01:42 AM |
| Comparison, which way to roll? | edua | UNIX for Dummies Questions & Answers | 0 | 04-01-2005 03:02 PM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
|||||
|
zfs.roll.snapshot
This script will create (or recreate, if it already exists) a ZFS snapshot, and then use the ZFS "clone" functionality to automatically mount the snapshot in an alternate location. This process prevents you from having to point the backup software at a .zfs/snapshot directory, which is clumsy.By default the script will mount the clone under /zbackup, although this behavior can be changed with options or by editing the script. Because a ZFS clone is created using the same type of copy-on-write pointers as the snapshot itself, it uses additional space only when data changes in the live volume.Read BigAdmin article that describes usage of this script: http://www.sun.com/bigadmin/content/...apshot_zfs.jsp
More... |
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|