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.
4.8.4 Specifying the domain<br />
The node th<strong>at</strong> is used for backing up <strong>Oracle</strong> to TSM must belong to a domain<br />
th<strong>at</strong> contains the required management class. The domain th<strong>at</strong> a node<br />
belongs to can be specified when the node is initially registered, or the node<br />
can be upd<strong>at</strong>ed to belong to a new domain. To do this, specify<br />
DOMAIN=domain_name when registering or upd<strong>at</strong>ing the node.<br />
4.8.5 Setting the MAXNUMMP<br />
A node is restricted to the number of tape mounts specified with this option.<br />
In order for the TSM client to use multiple sessions when sending backups to<br />
tape, the maximum number of mount points parameter MAXNUMMP must be<br />
equal to or gre<strong>at</strong>er than the number of sessions involved in the backup. The<br />
number of session used during a backup corresponds to the number of<br />
channels alloc<strong>at</strong>ed in an RMAN script.<br />
The MAXNUMMP must not be set to a value gre<strong>at</strong>er than the actual number<br />
of physical drives defined to the TSM server. If TDP for <strong>Oracle</strong> is unable to<br />
acquire enough tape mounts, either because this value is set lower than the<br />
number of sessions, or because the tape mounts are not available, the<br />
backups may fail, or have to wait for one session to finish. MAXNUMMP=2<br />
(to allow the client to mount a maximum of 2 drives).<br />
4.9 Storage pool consider<strong>at</strong>ions<br />
Storage pools (STG) represent the actual physical devices th<strong>at</strong> will hold your<br />
d<strong>at</strong>a. Each copy group (backup or archive) will send its d<strong>at</strong>a to the associ<strong>at</strong>ed<br />
storage pool (configur<strong>at</strong>ion parameter: destin<strong>at</strong>ion). It is possible to have<br />
only one storage pool (for example one tape storage pool) to hold all the d<strong>at</strong>a<br />
from all the TSM clients. We do not recommend to do this.<br />
In the remainder of this section, we provide some suggestions to consider<br />
when designing your storage pools:<br />
Specifying MAXSIZE (disk STG parameter)<br />
For a storage pool, you can specify the maximum size object th<strong>at</strong> it will<br />
accept. If a d<strong>at</strong>a object is larger than the maxsize, it will try to go to the<br />
next storage pool (typically tape). If the d<strong>at</strong>a object is larger than the<br />
maxsize of all storage pools in the hierarchy, then the TSM server will<br />
reject th<strong>at</strong> object.<br />
You can utilize this option to send really large d<strong>at</strong>abase objects to tape<br />
instead of to your disk pool. If you do not have enough disk space to hold<br />
an entire days worth of backups, and you use migr<strong>at</strong>ion to free up space,<br />
Chapter 4. TSM server consider<strong>at</strong>ions 53
Change language