Tivoli Header
Tivoli Storage Manager for NetWare Backup-Archive Client Installation and User's Guide
The first time you run a full incremental backups, Tivoli Storage Manager
backs up all of the files and directories on the volumes you specify.
This process can take a long time if you have several files to back up.
Successive full incremental backups will only back up new and changed
files. This allows the backup server to maintain current versions of
your NetWare server files, without having to waste time or space by backing up
files that already exist in server storage. Depending on your storage
management policies, the server may keep more than one version of your files
in storage. The most recently backed up files are active backup
versions. Older copies of your backed up files are inactive
versions. However, if you delete a file from your NetWare server, the
backup server will not maintain an active backup version of that file.
If you need to retrieve a file you have deleted, you will need to access the
backup server's inactive file versions. See Chapter 8, Understanding Storage Management Policies for more information about storage management
polices.
To perform a full incremental backup see Performing Command Line Backups for more information.
During an incremental backup, the client queries the server to determine
the exact state of your files since last incremental backup. The client
uses this information to:
- Rename files if the information about the NetWare volume name has
changed.
- Back up new files
- Back up files whose contents changed since the last backup. Changes
include any of the following:
- File size
- Date or time of last modification
- File attributes, except for the A attribute (the archive
attribute). The client ignores the archive attribute because other
programs change the attribute during file copying, even if the file does not
change. When you restore a file, Tivoli Storage Manager restores the
attributes to what they were when you backed up the file.
- Trustee rights
- Back up files whose directory attributes have changed.
- Expire backup versions of files on the server that do not have
corresponding files on the workstation. The result is that files which
no longer exist on your NetWare server will not have active backup versions on
the server.
- Rebind backup versions to management classes if you change management
class assignments, even if you do not back up the file.
Attention: If a file's modification timestamp changes,
it will be backed up during the next full incremental backup. The
directories in the path that contain the file are also backed up, unless they
already exist on the server. A directory that already exists on the
server is only backed up again if its permissions or time stamp change.
Directories and NDS container objects count in the number of objects backed
up. To exclude directories from backup, use the
exclude.dir option. For more about
exclude.dir, see Exclude Options.
When you requst a backup, Tivoli Storage Manager backs up a file if all of
the follwing requirements are met:
- You do not exclude the file backup in your include-exclude list. If
you do not have an include-exclude list, all files will be candidates for
backup.
- The selected management class contains a backup copy group. See Chapter 7, Automating Tasks for more information on management classes and backup copy
groups.
- The file meets the serialization requirements defined in the backup copy
group. If serialization is static or shared
static, and the file is in use during back up, the backup does not
occur. See Using Management Classes and Copy Groups for more information.
- The file meets the mode requirements defined in the backup copy
group. If the mode is modified, the file must have changed
since the last backup. If the mode is absolute, the file can
be backed up even if it does not change. See Using Management Classes and Copy Groups for more information.
- The file meets the frequency requirements defined in the backup copy
group. The specified minimum number of days since the last backup must
elapse before a file is backed up. Frequency is ignored for partial
incremental backups. See Using Management Classes and Copy Groups for more information.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]