Specifies how many devices are locked prior to starting a session. Devices that
are specified per object through the -targetdevice option are locked in any
case. The max value is increased by Data Protector if the number of statically
assigned devices is higher than the specified max value.
Min specifies the minimum number of available devices (devices that are not
being used by another Data Protector session and have the license to be started)
required for starting the session. If fewer devices are available than specified
here, the session will queue. The default is 1.
Max specifies the maximum number of available devices that Data Protector will
use in the session. The highest number you can specify is 32. The default is 5.
Data Protector will lock the number of devices that you specify using this
parameter if so many devices are available. If this option is not specified, the
default value for max is the number of specified devices.
-targetprotect {none | weeks n | days n | until Date | per-
manent}
Sets the level of protection for the copy object. The media containing this object
copy session cannot be overwritten until the protection expires. By default (if this
option is not specified), the protection is the same as the original protection for
the source object.
The old —recycle option, which was the equivalent of —targetprotect
none, is deprecated.
-keepcatalog {weeks n | days n | until Date |
same_as_data_protection}
Specifies file catalog retention time. If you do not want to save the file catalog
at all, use the -no_log option. By default (if this option is not specified), the
protection is the same as for the source object.
-log
Specifies the logging level of the object copy session. All detailed information
about backed up files and directories (filenames, file versions, and attributes)
are logged to the Data Protector internal database (IDB). This allows you to
browse directories and files before restore and in addition look at the file
attributes. Data Protector can fast position on the tape when restoring a specific
file.
If the logging level is not specified, it is set to the same logging level as for the
source object.
-no_log
Specifies the logging level of the object copy session. Disables the logging of
backed up files to the catalog database. By default, the filename and backup
history of each backed up file is written to the catalog database.
182
To Next Page
Loading...
Need help?
General