The copy serialization attribute determines whether a file can be in use during a backup or archive, and what to do if it is.
The value for this attribute can be one of the following:
- Static. A file or directory must not be modified during a backup or archive. If the object is changed during a backup or archive attempt, it is not backed up or archived.
Note: For all supported Windows 32-bit versions: During an image backup, the static copy serialization value is no longer controlled by the server management class, but is instead controlled directly from the client, using the snapshotproviderimage option. - Shared static. A file or directory must not be modified during backup or archive. Tivoli® Storage Manager attempts to perform a backup or archive as many as four additional times, depending on the value specified on the changingretries option in your options file. If the object is changed during every backup or archive attempt, it is not backed up or archived.
- Dynamic. A file or directory is backed up or archived on the first attempt regardless of whether it changes during a backup or archive. Important: For all supported Windows 32-bit versions: During an image backup, the dynamic copy serialization value is no longer controlled by the server management class, but is instead controlled directly from the client, using the snapshotproviderimage option.
- Shared dynamic. A file or directory is backed up or archived regardless of whether it changes during a backup or archive. Tivoli Storage Manager attempts to back up or archive as many as four additional times. The number of attempts depend on the value that was specified on the changingretries option in your options file, without the file changing during the attempt. The file is backed up or archived on the last try even if it has changed.
If you select a management class that permits a file to be backed up or archived while it is in use, the backup version or archived copy that is stored on the server might be a fuzzy copy. A fuzzy copy is a backup version or archived copy that does not accurately reflect what is currently in the file. It might contain some, but not all, of the changes. If that is not acceptable, select a management class that creates a backup version or archive copy only if the file does not change during a backup or archive. When you use static serialization, applications cannot open a file for write access while the file is being backed up.
If you restore or retrieve a file that contains a fuzzy copy, the file might not be usable. Do not use dynamic or shared dynamic serialization to back up files unless you are certain that a fuzzy copy that is restored is usable.
Important: Be careful when you select a management class containing a copy group that specifies shared dynamic or serialization dynamic backup.