5.6 HP StorageWorks X9000 File Serving Software User Guide (TA768-96035, June 2011)

The number of snapshots to keep per file system. For the P2000 G3 MSA System/MSA2000
G2 array, the maximum is 32 snapshots per file system. For Dell EqualLogic arrays, the maximum
is eight snapshots per file system.
If the strategy type is linear, enter the number of snapshots to keep, such as -k 6.
If the strategy type is DWMGroup, enter the number of days, weeks, and months to retain
snapshots. The numbers must be separated by commas, such as -k 2,7,28.
NOTE: When the DWMGroup strategy is used, one snapshot is kept per day for the specified
number of days. For example, if you enter 6 as the daily count, the snapshot feature keeps 1
snapshot per day through the 6th day. On the 7th day, the oldest snapshot is deleted. Similarly,
the weekly count specifies the number of weeks that snapshots are retained, and the monthly
count specifies the number of months that snapshots are retained.
-k KEEP
The number of snapshots to mount per file system. The maximum number of snapshots is 7 per
file system.
If the strategy type is linear, enter the number of snapshots to mount, such as -m 7.
If the strategy type is DWMGroup, enter the number of snapshots to mount per day, week, and
month. The numbers must be separated by commas, such as -m 2,2,3. The sum of the numbers
must be less than or equal to 7.
-m MOUNT
Snapshot name template. The template specifies a scheme for creating unique names for the
snapshots. Use the variables listed below for the template.
-N NAMESPEC
Snapshot mountpoint template. The template specifies a scheme for creating unique mountpoints
for the snapshots. Use the variables listed below for the template.
–M MOUNTSPEC
Variables for snapshot name and mountpoint templates.
yyyy_mm_dd_HHmmz + GMTfulldate
yyyy_mm_ddshortdate
Strategy type specified by the -T option (linear or DWMGroup)type
Same as type but with the name of the “snapshot strategy” appendedstrategy
File system namefsname
You can specify one or more of these variables, enclosed in braces ({ }) and separated by
underscores (_). The template can also include text strings. Two sample templates follow. When a
snapshot is created using one of these templates, the variables will be replaced with the values
listed above.
{fsname}_snap_{fulldate}
snap_{shortdate}_{fsname}
Scheduling and starting automated snapshots
The ibrix_at command is used to create the snapshot schedule. The command has two parts
separated by a colon. The first part is a cron-style scheduling string. See the following web page
for information about writing the string.
http://wiki.opensymphony.com/display/QRTZ1/CronTriggers+Tutorial
The second part of the ibrix_at command is the ibrix_snap -A command, which starts the
snapshots. The following command takes a snapshot at 11:30am on the 10th of every month. The
snapshot strategy, specified with the -n option, is monthly1.
ibrix_at "0 30 11 10 * ?" : ibrix_snap –A -f ifs1 -n monthly1
Other automated snapshot procedures
Use the following procedures to manage automated snapshots.
102 Creating snapshots