Table of Contents
TDP Oracle tuning and performances
useful links
allocate multiple channels
Into RMAN backup script, we can use the parameter allocate channel
Ex:
connect target agnttest/agttest
run
{
allocate channel ch1 type 'SBT_TAPE' parms
'ENV=(TDPO_OPTFILE=C:\oracle\tdpo.opt)';
allocate channel ch2 type 'SBT_TAPE' parms
'ENV=(TDPO_OPTFILE=C:\oracle\tdpo.opt)';
allocate channel ch3 type 'SBT_TAPE' parms
'ENV=(TDPO_OPTFILE=C:\oracle\tdpo.opt)';
allocate channel ch4 type 'SBT_TAPE' parms
'ENV=(TDPO_OPTFILE=C:\oracle\tdpo.opt)';
backup (database);
release channel ch1;
release channel ch2;
release channel ch3;
release channel ch4;
}
Don't forget to increate the number of connection for the client on Spectrum Protect server
upd node node_name MAXNUMMP=6
Another possibility is to use the RMAN duplex parameter:
#Specify the following option in the RMAN backup script: set duplex=4
Increase the disk buffer on client
The parameter DISKBuffsize can be changed into dsm.sys. Value can be from 16 to 1023. default value is 32.
The diskbuffsize option specifies the maximum disk I/O buffer size (in kilobytes) that the client can use when reading files. The diskbuffsize option replaces the largecommbuffers option.
Optimal backup, archive, or HSM migration client performance can usually be achieved if the value for this option is equal to or smaller than the amount of file read ahead provided by the client file system. A larger buffer requires more memory and it might not improve performance.
An optimal value can be 256
Adjust the DISKBUFFSIZE option value as needed, to be equal or lower than the Oracle BLKSIZE value. If not specified with the RMAN script, the BLKSIZE value defaults to 262144.
The Oracle backup was initiated with RMAN script using BLKSIZE=262144 with the allocate channel. For example :
allocate channel ch1 type 'SBT_TAPE' parms 'BLKSIZE=262144,ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
https://www.ibm.com/support/pages/data-protection-oracle-backup-performance
Change bloc size
Default value for bloc size is 256k. You have to test with larger value, if no contention on network
Ex:
CONFIGURE CHANNEL 3 DEVICE TYPE ‘SBT_TAPE’ PARM ‘BLKSIZE=1048576
You can also change the size of the section parameter Ex:
backup device type sbt section size 4G database format '%d_%U';
Trace / debug
To generate the Tivoli Storage Manager API trace file, add the following lines in your dsm.opt file:
tracefile /home/oracle/rman/tsmapi.out traceflag service
