12.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

The <strong>Linux</strong> Logical Volume <strong>Manager</strong> 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 imagecomm<strong>and</strong>, in the dsm.opt 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. See“Snapshotcachesize” on page 350 <strong>for</strong> more in<strong>for</strong>mation.Utilizing image backup to per<strong>for</strong>m file system incrementalbackupThere are two methods of utilizing image backups to per<strong>for</strong>m efficient incrementalbackups of your file system. These backup methods allow you to per<strong>for</strong>mpoint-in-time restore of your file systems <strong>and</strong> improve backup <strong>and</strong> restoreper<strong>for</strong>mance. You can per<strong>for</strong>m the backup only on <strong>for</strong>matted volumes; not on rawlogical volumes. You can use one of the following methods to per<strong>for</strong>m imagebackups of volumes with mounted file systems.Method 1 Using image backup with file system incremental:1. Per<strong>for</strong>m a full incremental backup of the file system, <strong>for</strong> example:dsmc incremental /myfilesystem2. Per<strong>for</strong>m an image backup of the same file system, <strong>for</strong> example:dsmc backup image /myfilesystem3. Periodically, per<strong>for</strong>m incremental backups, <strong>for</strong> example:dsmc incremental /myfilesystemYou must follow these steps in the order shown to ensure that the serverrecords additions <strong>and</strong> deletions accurately.4. The following comm<strong>and</strong> restores the file system to its exact state as of the lastincremental backup:dsmc restore image /myfilesystem -incremental -deletefilesDuring the restore, the client does the following:v Restores the most recent image on the server.v Deletes all of the files restored in the previous step which are inactive on theserver. These are files which existed at the time of the image backup, butwere subsequently deleted <strong>and</strong> recorded by a later incremental backup.v Restores new <strong>and</strong> changed files from the incremental backups.If you do not follow the steps exactly, two things can occur:v After the original image is restored, all files backed up with the incrementalcomm<strong>and</strong> are restored individually.v If you per<strong>for</strong>m a backup image be<strong>for</strong>e per<strong>for</strong>ming an incremental, files deletedfrom the original image are not deleted from the final restored file system.Method 2 Using image backup with image incremental mode:1. Per<strong>for</strong>m an image backup of the same file system, <strong>for</strong> example:dsmc backup image /myfilesystem2. Per<strong>for</strong>m an incremental image backup of the file system, <strong>for</strong> example:dsmc backup image /myfilesystem -mode=incrementalChapter 10. Using comm<strong>and</strong>s 407

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!