Tivoli Header
Tivoli Storage Manager for Windows Backup-Archive Clients Installation and User's Guide
Some files on your system might be in use when you try to back them
up. These are called open files because they are opened by
an application for its use. Because an open file may change, it is
likely that any backup of an open file will not correctly reflect the contents
of the file at a given time.
If certain files are not backed up because they are open and they change
when you try to back them up or when the backup schedule starts, consider the
following points:
- If the file is unimportant or can be easily rebuilt (a temporary file for
example), you might not care if the file is backed up, and might choose to
exclude it.
- If the file is important:
- Ensure the file is closed before backing it up. If backups are run
according to a schedule, use the preschedulecmd option to enter a
command that closes the file. For example, if the open file is a
database, issue a command to close the database, such as the
quiesce command. You can use the postschedulecmd
option to restart the application that uses the file after the backup
completes. If you are not using a schedule for the backup, close the
application that uses the file before you start the backup.
- Tivoli Storage Manager can back up the file even if it is open and changes
during the backup. This is only useful if the file will be usable even
if it changes during backup. To back up these files, assign a
management class with dynamic or shared dynamic
serialization. See Selecting a Management Class for Files for information about assigning management classes, and see Displaying Information about Management Classes and Copy Groups for information to determine which
management classes are available to you.
- Note:
- While Tivoli Storage Manager attempts to back up open files, this is not
always possible. Some files are open exclusively for the application
that opened them. If Tivoli Storage Manager encounters such a file, it
cannot read it for backup purposes. If you are aware of such file types
in your environment, you should exclude them from backup to avoid seeing error
messages in the log file.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]