Backing Up Oracle - Computing at Cornell
Backing Up Oracle - Computing at Cornell
Backing Up Oracle - Computing at Cornell
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
4.7 Policy management consider<strong>at</strong>ions<br />
When deciding how to set up your TSM server to store <strong>Oracle</strong> backup<br />
objects, you need to decide on how you are going to organize your nodes into<br />
domains. You must also correctly define and configure your management<br />
classes.<br />
4.7.1 Domain consider<strong>at</strong>ions<br />
You can use one domain for all your client d<strong>at</strong>a or you can specify multiple<br />
TSM domains to group nodes with the same backup characteristics together.<br />
Using multiple domains helps ensure th<strong>at</strong> the d<strong>at</strong>a objects get bound to the<br />
appropri<strong>at</strong>e management class. The following are some items to consider if<br />
you wish to use multiple domains:<br />
Backup-archive client, API client<br />
Pl<strong>at</strong>forms separ<strong>at</strong>ed, such as AIX, Sun, Windows<br />
Critical d<strong>at</strong>a, non-critical d<strong>at</strong>a<br />
Group nodes with the same d<strong>at</strong>a characteristics together<br />
Because the policy requirements for <strong>Oracle</strong> backups are different from the<br />
desired settings for regular TSM backup clients, a different management<br />
class must be defined within TSM for managing these <strong>Oracle</strong> backups. There<br />
are two ways to implement this different management class setup:<br />
Define a new management class within an existing policy domain.<br />
Define a separ<strong>at</strong>e policy domain where the default management class<br />
contains the required settings.<br />
4.7.1.1 Define a new management class in an existing domain<br />
If you choose to define a new management class within an existing policy<br />
domain (which is not the default management class for th<strong>at</strong> domain), then you<br />
must add an include st<strong>at</strong>ement in the client options file (dsm.opt for Windows,<br />
dsm.sys for UNIX) th<strong>at</strong> is used by the <strong>Oracle</strong> node. This include st<strong>at</strong>ement<br />
binds the <strong>Oracle</strong> backup objects to th<strong>at</strong> management class th<strong>at</strong> you have<br />
defined for managing these backups.<br />
The include st<strong>at</strong>ement would look similar to this:<br />
include * ManagementClassName<br />
4.7.1.2 Define a separ<strong>at</strong>e policy domain<br />
The recommended way is to define a separ<strong>at</strong>e policy domain where the<br />
default management class has the required settings. Then just register the<br />
node th<strong>at</strong> will be used for <strong>Oracle</strong> backups to this new domain.<br />
48 <strong>Backing</strong> <strong>Up</strong> <strong>Oracle</strong> using Tivoli Storage Management