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.

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 either use image backup with file system incremental or youcan use image backup with image incremental mode to per<strong>for</strong>m image backups ofvolumes with mounted file systems.The following are some examples of using image backup with file system incremental.v To per<strong>for</strong>m a full incremental backup of the file system: dsmc incremental/myfilesystemv To per<strong>for</strong>m an image backup of the same file system: dsmc backup image/myfilesystemv To periodically per<strong>for</strong>m incremental backups: dsmc incremental /myfilesystemYou must follow the next steps in the order shown to ensure that the serverrecords additions <strong>and</strong> deletions accurately.Use this comm<strong>and</strong> to restore the file system to its exact state as of the lastincremental backup: dsmc restore image /myfilesystem -incremental-deletefiles.During 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, but weresubsequently 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:1. After the original image is restored, all files backed up with the incrementalcomm<strong>and</strong> are restored individually.2. 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.The following are some examples of using image backup with image incremental mode.v To per<strong>for</strong>m an image backup of the same file system: dsmc backup image/myfilesystemv To per<strong>for</strong>m an incremental image backup of the file system: dsmc backup image/myfilesystem -mode=incrementalThis sends only those files that were added or changed since the last imagebackup to the server.v To periodically per<strong>for</strong>m full image backups: dsmc backup image /myfilesystemv To restore the image: dsmc restore image /myfilesystem -incrementalOn restore, <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> ignores the deletefiles option when theimage+image incremental technique of backing up has been used. The restorewill include files that were deleted after the last full image backup plus thelatest versions of files added or changed after the last image backup.452 <strong>IBM</strong> <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> <strong>for</strong> <strong>UNIX</strong> <strong>and</strong> <strong>Linux</strong> <strong>Backup</strong>-<strong>Archive</strong> Clients Version 6.1: Installation <strong>and</strong> User’s Guide

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

Saved successfully!

Ooh no, something went wrong!