There are other Tivoli® Storage Manager client options that you can use when you are configuring Data Protection for Oracle.
You can specify other options in the Tivoli Storage Manager client system options file dsm.sys.
You can specify other options in the Tivoli Storage Manager client user options file dsm.opt.
When any of the following conditions exist, you should specify yes:
When any of the following conditions exist, you should specify no:
You can monitor processor and network resource usage with the Performance Monitor program that is shipped with Windows.
After a completed backup operation, view the throughput rate and the compression status for a backup object in the Tivoli Storage Manager server activity log file. Run the Tivoli Storage Manager server QUERY ACTLOG command in the Tivoli Storage Manager server administrative client window. The throughput rate and the compression status are not written to the activity log when activity logging is disabled on the Tivoli Storage Manager server. See the SET ACTLOGRETENTION command in the Tivoli Storage Manager Administrator's Reference for complete activity logging information.
You can also determine whether objects were compressed by running the tdposync query command.
You can determine if objects are deduplicated by running the tdposync query command or by examining the Tivoli Storage Manager server activity log file.
The deduplication and enablelanfree options are mutually exclusive. Therefore, you must use either one option or the other, but not both options together.
The deduplication and enableclientencryptkey options are also mutually exclusive. Therefore, you must use either one option or the other, but not both options together.
The enablelanfree and deduplication options are mutually exclusive. Therefore, you must use either one option or the other, but not both options together.
You must add an include statement to the dsm.sys file.
You must add an include statement to the dsm.opt file.
This include statement binds the Oracle backup objects to the management class that is defined for managing these objects. The include statement uses the following naming convention:
/FilespaceName//ObjectName
\FilespaceName\orcnt\ObjectName
The FORMAT parameter in the RMAN script can also be used to assist with object naming. For example, if the FORMAT parameters (in the RMAN script) specified the following values for databases and logs:
format 'DB_%u_%p_%c'
format 'LOG_%u_%p_%c'
INCLUDE /adsmorc/.../DB* mgmtclassnameforDBs
INCLUDE /adsmorc/.../LOG* mgmtclassnameforLogs
INCLUDE \FilespaceName\orcnt\DB* mgmtclassname
INCLUDE \FilespaceName\orcnt\LOG* mgmtclassname
Make sure that the FORMAT parameter specifies a unique name for the backup. If the object name exists on the Tivoli Storage Manager server, the backup might fail with an RC=8 error that is recorded in the sbtio.log file.
You can specify the databases that you want encrypted by adding an include statement with the include.encrypt option in the dsm.sys file.
You can specify the databases that you want encrypted by adding an include statement with the include.encrypt option in the client user options file dsm.opt.
For example, to enable transparent encryption, do the following steps:
include.encrypt /adsmorc/.../*
include.encrypt \adsmorc\...\*
enableclientencryptkey yes
encryptiontype aes128
include.encrypt /adsmorc/.../*
enableclientencryptkey yes
encryptiontype aes128
include.encrypt \adsmorc\...\*
See IBM® Tivoli Storage Manager Using the Application Programming Interface for more details about the enableclientencryptkey option.
You can determine whether objects were encrypted by running the tdposync query command.