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...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

You can use these methods to view the available management classes <strong>and</strong> theirattributes:v GUI or Web Client: Select View Policy In<strong>for</strong>mation from the Utilities menu.v comm<strong>and</strong>-line client: Run dsmc query mgmtclass -detail.Note: During expiration processing on a <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> server, if anarchived directory is eligible <strong>for</strong> expiration, the server checks if any existingarchived files require the archived directory to remain. If so, the archived directoryis not expired <strong>and</strong> the <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> client updates the insert date on thearchived directory to ensure that the directory is not expired be<strong>for</strong>e the files underit.Binding management classes to filesBinding associates a file with a management class. When you back up a file <strong>for</strong> thefirst time, <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> binds it to either the default management classor the management class specified in your include-exclude list.If the backup copy group <strong>for</strong> the management class specifies keeping multiplebackup versions of the file, <strong>and</strong> you request multiple backups, the server alwayshas one active backup version (the current version) <strong>and</strong> one or more inactivebackup versions of the file. All backup versions of a file are bound to the samemanagement class <strong>and</strong> are managed based on the attributes in the backup copygroup.When you archive a file <strong>for</strong> the first time, <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> binds it to thedefault management class, to the management class specified in yourinclude-exclude list, or to a management class you specify when modifying yourarchive options during an archive.<strong>Archive</strong>d files are never rebound to a different management class. If you changethe management class <strong>for</strong> a file using an include.archive statement, the archmcoption, or through a <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> GUI, any previous copies of the filethat you archived remain bound to the management class specified when youarchived them.If a file is deleted on the client system then that file’s inactive objects are notrebound.Refer to the <strong>IBM</strong> <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> Administrator’s Guide <strong>for</strong> your operatingsystem, <strong>for</strong> more in<strong>for</strong>mation on how files <strong>and</strong> directories are associated withmanagement classes.Rebinding backup versions of filesRebinding associates a file or a logical volume image with a new management class.<strong>Backup</strong>s of files are bound again to a different management class in the followingconditions. In each condition, the files (active <strong>and</strong> inactive) are not bound againuntil the next backup.vYou specify a different management class in an Include statement to change themanagement class <strong>for</strong> the file. The backups are managed based on the oldmanagement class until you run another backup.Chapter 9. Underst<strong>and</strong>ing storage management policies 237

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

Saved successfully!

Ooh no, something went wrong!