IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive ...

TaskBack up the /dev/lv01 raw logical volume.Command: dsmc backup image f:Related information“Imagegapsize” on page 328“Snapshotproviderimage” on page 404“Snapshotcachesize” on page 402“Mode” on page 350“Comparing methods 1 and 2” on page 143 to decide which method is appropriatefor your environment.Static, dynamic, and snapshot image backupThe traditional image backup prevents write access to the volume by other systemapplications during the operation. Use the dynamicimage option to back up thevolume as is without remounting it read-only. Corruption of the backup can occurif applications write to the volume while the backup is in progress. In this case,run fsck after a restore.The dynamicimage option is not supported for JFS2 volumes.For Linux x86/x86_64 clients only: By default, Tivoli Storage Manager performs asnapshot image backup of file systems residing on a logical volume created by theLinux Logical Volume Manager during which the volume is available to othersystem applications. Snapshot image backup requires a Version 5.1 Tivoli StorageManager server.For AIX clients only: By default, Tivoli Storage Manager performs a snapshotimage backup of JFS2 volumes during which the volume is available to othersystem applications. AIX allows the creation of a snapshot of a JFS2 volume whileit is still online. The snapshot is created inside the same volume group as thesource volume. You must ensure that the volume group provides enough free diskspace to create the snapshot. The snapshot contains the old data blocks while themodified data is stored in the source volume. Use the snapshotcachesize optionwith the backup image command, in the dsm.sys file, or with the include.imageoption to specify an appropriate snapshot size so that all old data blocks can bestored while the image backup occurs. A snapshot size of 20 percent will ensure avalid snapshot.The Linux Logical Volume Manager allows the creation of a snapshot of a logicalvolume while the logical volume itself is still online. The snapshot is created insidethe same volume group as the source logical volume. You must ensure that thevolume group provides enough free disk space to create the snapshot. Thesnapshot contains the old data blocks while the modified data is stored in thesource logical volume. Use the snapshotcachesize option with the backup imagecommand, in the dsm.sys file, or with the include.image option to specify anappropriate snapshot size so that all old data blocks can be stored while the imagebackup occurs. A snapshot size of 100 percent will ensure a valid snapshot.Chapter 11. Using commands 451