Tivoli Header

Tivoli Storage Manager for UNIX Backup-Archive Clients Installation and User's Guide

Incremental

The incremental command backs up all new or changed files or directories in the default client domain or from file systems, directories, or files you specify, unless you exclude them from backup services.

To incrementally back up selected files or directories, enter a file specification in the command. If you do not enter a file specification, the default is to back up files or directories in the default domain.

The following attributes in the management class assigned to the file or directory affect whether the data is actually backed up:

Frequency
The number of days that must elapse between successive backups for the file. Use this attribute during a full incremental backup.

Mode
Permits you to back up only files that changed since the last backup (modified). Also permits you to back up the files whether they changed or not (absolute).

Serialization
Permits or denies backup of files or directories according to the following values:

For more information on management classes, see Chapter 8, "Understanding Storage Management Policies".

Using the include option in an include-exclude list, you can assign the default management class to a file. You can also assign a specific management class to a file.

You can perform either a full incremental backup or an incremental by date backup. The default is a full incremental backup.

You can also use the selective command to perform a selective backup that backs up only the files, directories or empty directories that you specify. For more information, see Selective.

A full incremental backs up all files or directories that are new or have changed since the last incremental backup. During a full incremental backup, the client queries the server to determine the exact condition of your storage. Tivoli Storage Manager uses this information to:

Incremental-by-Date

An incremental-by-date backup backs up new and changed files with a modification date later than the date of the last incremental backup stored at the server, unless the files are excluded from backup by an exclude statement.

If an incremental-by-date is performed on only part of a file system, the date of the last full incremental is not updated, and the next incremental-by-date will back up these files again. Changes to the access control lists (ACL) are not backed up during an incremental-by-date. Use the query filespace command to determine the date and time of the last incremental backup of the entire file system.

To perform an incremental-by-date backup, use the incrbydate option with the incremental command.

Unlike a full incremental, an incremental-by-date does not maintain current server storage of all your workstation files because:

For these reasons, if you have limited time during the week to perform backups, but extra time on the weekends, you can perform an incremental-by-date backup on weekdays and a full incremental backup on weekends to maintain current server storage of your workstation files.

If the incremental command is retried because of a communication failure or session loss, the transfer statistics will display the number of bytes Tivoli Storage Manager attempted to transfer during all command attempts. Therefore, the statistics for bytes transferred may not match the file statistics, such as those for file size.

Supported File Systems and ACL Support

Special file systems contain dynamic information generated by the operating system; they contain no data or files. The UNIX client ignores special file systems and their contents. Special file systems include the following:

Tivoli Storage Manager provides ACL support for the client file systems in Table 37.

Table 37. Supported File Systems and ACL Support

Platform File System ACL Support
AIX jfs
gpfs
afs/dfs
JFS2
yes
yes
yes
yes
AIX 5L jfs
gpfs
afs/dfs
JFS2
yes
yes
yes
yes
HP-UX hfs
VxFS (JFS Veritas)
yes
yes (V3.3.Layout 4)
Linux86 ext2
ext3
jfs
reiserfs
no
no
no
no
Linux/390 ext2
ext3
jfs
yes
no
no
OS/390 UNIX hfs
zfs
no
yes
SGI efs
xfs
no
yes
Solaris ufs
VxFS
QFS
yes
yes
no

Beginning with Version 3.7.2, Tivoli Storage Manager provides full ACL support for GPFS file systems on the AIX client and XFS file systems on the SGI client. Files with an ACL set, backed up with a Version 3.7.1 or lower client, must be backed up again even if the files have not changed. This updates the ACL data on the server.

Notes:

  1. The standalone package LSCqfs 3.5.0 is the only supported version of QFS. In addition, the following restrictions also apply to the QFS file system:

Attention: If you are running GPFS for AIX in a multi-node cluster, and all nodes share a mounted GPFS file system, Tivoli Storage Manager processes this file system as a local file system. Tivoli Storage Manager backs up the file system on each node during an incremental backup. To avoid this, you can do one of the following:

Supported Clients

This command is valid for all UNIX clients.

Syntax

                              .-----------------.
                              V                 |
>>-Incremental--+----------+----+-------------+-+--------------><
                '- options-'    +- filespec---+
                                '- "filespec"-'
 
 

Parameters

options
You can use these command line options with the incremental command: dirsonly, filelist, filesonly, incrbydate, volinformation. For more information, see Chapter 10, "Using Options with Commands".

You can use these common options with the incremental command: changingretries, domain, , memoryefficientbackup, subdir, , tapeprompt. For information about these options, see Chapter 9, Setting Processing Options.

filespec
Specifies the path and file name that you want to back up. Use wildcards to select a group of files or all the files in a directory. You can also enter up to 20 file specifications in a command by separating the file specifications with a space. If you do not specify a file specification, the default domain or the domain specified as an option is backed up.

If you specify a file system, all new and changed files are backed up. In addition, the last incremental date for the file space is updated on the server. If you specify a file or directory, the last incremental date is not updated. This means the file or directory might be backed up again if a later backup is performed using the incrbydate option.

If you specify a file system, specify the file system without a trailing slash.

Examples

Task
Run an incremental backup of the default client domain specified in your client user options file (dsm.opt).

Command: Incremental

Task
Run an incremental backup for the /home, /usr, and /proj file systems.

Command: Incremental /home /usr /proj

Task
Run an incremental backup for the /proj/test directory.

Command: Incremental /proj/test/

Task
Run an incremental-by-date backup for the /home file system.

Command: Incremental -incrbydate /home

Task
Run an incremental backup of all files in the /fs/dir1 directory that begin with the string abc.

Command: Incremental -subdir=yes "/fs/dir1/abc*"

Task
Run an incremental backup of the abc file in the /fs/dir1 directory.

Command: Incremental -subdir=yes /fs/dir1/abc

Task
Run an incremental backup of the directory object /fs/dir1, but not any of the files in the /fs/dir1 directory.

Command: Incremental /fs/dir1

Task
Run an incremental backup of the directory object /fs/dir1 and all of the files in the /fs/dir1 directory.

Command: Incremental -subdir=yes /fs/dir1/


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]