Backing Up Oracle - Computing at Cornell
Backing Up Oracle - Computing at Cornell
Backing Up Oracle - Computing at Cornell
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
This option can be set in the TDP for <strong>Oracle</strong> option file using the following<br />
parameter:<br />
TDPO_NUM_BUFFERS #<br />
This option specifies the number of buffers TDP for <strong>Oracle</strong> uses to support<br />
multi-buffering. By entering a value, multi buffering is activ<strong>at</strong>ed.<br />
The minimum value (number of buffers) is 5, and the maximum value<br />
(number of buffers) is 15. When this option is not set, TDP for <strong>Oracle</strong><br />
oper<strong>at</strong>es with a single buffer.<br />
We measured this options with runtimes of a full d<strong>at</strong>abase backup with values<br />
of 2, 4, 8 and without this option. We achieved the best results with only 2<br />
buffers.<br />
C.3.2 Duplex copy function<br />
<strong>Oracle</strong> 8.1.x allows you to make up to four, exact duplic<strong>at</strong>e copies of a backup<br />
th<strong>at</strong> can be stored on different backup media. TDP for <strong>Oracle</strong> Version 2.2<br />
supports this Duplex Backup fe<strong>at</strong>ure. This Duplex Backup fe<strong>at</strong>ure uses<br />
different management classes for each backup copy. By default, the primary<br />
management class is the one assigned to the TSM client node name.<br />
To activ<strong>at</strong>e the duplexing, the following setup steps must be performed.<br />
12.3.4.2 <strong>Oracle</strong> configur<strong>at</strong>ion<br />
In the init.ora file, the parameter backup_tape_io_slaves must be set to true.<br />
BACKUP_TAPE_IO_SLAVES specifies whether I/O server processes ("slaves") are<br />
used by the Recovery Manager to back up, copy, or restore d<strong>at</strong>a to tape.<br />
When the value is set to TRUE, <strong>Oracle</strong> uses an I/O server process to write to<br />
or read from a tape device. When the value is set to FALSE (the default),<br />
<strong>Oracle</strong> does not use I/O server process for backups. Instead, the shadow<br />
process engaged in the backup accesses the tape device.<br />
Typically, I/O server processes are used to simul<strong>at</strong>e asynchronous I/O on<br />
pl<strong>at</strong>forms th<strong>at</strong> either do not support asynchronous I/O or implement it<br />
inefficiently. However, you can use I/O server processes even when<br />
synchronous I/O is available. In th<strong>at</strong> case, the I/O server processes will use<br />
asynchronous I/O. Only one process can access a tape device <strong>at</strong> any given<br />
time. Therefore, this parameter is Boolean, and allows or disallows<br />
deployment of an I/O server process to access a tape device.<br />
216 <strong>Backing</strong> <strong>Up</strong> <strong>Oracle</strong> using Tivoli Storage Management
Change language