IBM Tivoli Storage Manager for Windows Backup-Archive Clients ...

Options File
Place this option in the client options file (dsm.opt). You can set this option on the
Scheduler tab, Maximum command retries field of the Preferences editor.
Syntax
►► MAXCMDRetries maxcmdretries ►◄
Parameters
maxcmdretries
Specifies the number of times the client scheduler can attempt to process a
scheduled command that fails. The range of values is zero through 9999; the
default is 2.
Examples
Options file:
maxcmdr 4
Command line:
-maxcmdretries=4
This option is valid only on the initial command line. It is not valid in interactive
mode.
Memoryefficientbackup
The memoryefficientbackup option specifies the memory-conserving algorithm to
use for processing full file space backups.
One method backs up one directory at a time, using less memory. The other
method uses much less memory, but requires more disk space.
Use the memoryefficientbackup option with the incremental command when your
workstation is memory constrained. You can also use this option as a parameter to
the include.fs option in order to select the algorithm Tivoli Storage Manager uses
on a per-filespace basis.
Use memoryefficientbackup=diskcachemethod for any file space that has too many
files for Tivoli Storage Manager to complete the incremental backup with either the
default setting, memoryefficientbackup=no, or with memoryefficientbackup=yes.
The disk cache file created by the initial disk cache incremental backup can require
up to 5 gigabytes of disk space for each million files or directories being backed
up.
The actual amount of disk space required for the disk cache file created by disk
cache incremental backups depends on the number of files and directories included
in the backup and on the average path length of the files and directories to be
backed up. Estimate 2 bytes per character in the path name. For example, if there
are 1 000 000 files and directories to be backed up and the average path length is
200 characters, then the database occupies approximately 400 MB. Another way to
estimate for planning purposes is to multiply the number of files and directories
by the length of the longest path to establish a maximum database size.
Chapter 12. Processing options 411