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

The expiration date for the remaining versions is based on the retain extra versionsand retain only version parameters.Retain extra versionsThe Retain Extra Versions attribute specifies how many days all but the most recentbackup version is retained. The most recent version is the active version, andactive versions are never erased. If Nolimit is specified, then extra versions are keptuntil the number of backup versions exceeds the versions data exists or versions datadeleted parameter settings. In this case, the oldest extra version is deletedimmediately.Retain only versionThe Retain Only Version attribute specifies the number of days the last remaininginactive version of a file or directory is retained. If Nolimit is specified, the lastversion is retained indefinitely.This parameter goes into effect during the next incremental backup after a file isdeleted from the client machine. Any subsequent updates to this parameter willnot affect files that are already inactive. For example: If this parameter is set to 10days when a file is inactivated during an incremental backup, the file will bedeleted from the server in 10 days.CopyserializationThe Copy Serialization attribute determines whether a file can be in use during abackup or archive, and what to do if it is. The value for this attribute can be one ofthe following:v Static. A file or directory must not be modified during a backup or archive. Ifthe object is changed during a backup or archive attempt, it is not backed up orarchived.Note: During an image backup, the static copy serialization value is no longercontrolled by the server management class, but is instead controlled directlyfrom the client, using the imagetype option. See “Imagetype” on page 265 formore information.v Shared static. A file or directory must not be modified during backup orarchive. Tivoli Storage Manager attempts to perform a backup or archive asmany as four additional times, depending on the value specified on thechangingretries option in your dsm.sys file. If the object is changed during everybackup or archive attempt, it is not backed up or archived.v Dynamic. A file or directory is backed up or archived on the first attemptregardless of whether it changes during a backup or archive.Note: During an image backup, the dynamic copy serialization value is nolonger controlled by the server management class, but is instead controlleddirectly from the client, using the imagetype option. See “Imagetype” on page265 for more information.v Shared dynamic. A file or directory is backed up or archived regardless ofwhether it changes during a backup or archive. Tivoli Storage Manager attemptsto perform a backup or archive as many as four additional times, depending onthe value specified on the changingretries option in your client system optionsfile without the file changing during the attempt. The file is backed up orarchived on the last try even if it has changed.Chapter 8. Understanding storage management policies 161