Tài liệu Oracle RMAN 11g Backup and Recovery- P5 pdf

The Data Protector Oracle Integration agent uses the information in the recovery catalog or in the control file to determine how to execute the requested backup and restore operations..

from the RMAN repository, RMAN sends the request to NetBackup to delete the corresponding images from its repository, regardless of the retention level The code for deleting expired backups

is shown next:

RMAN> allocate channel for maintenance type 'SBT TAPE';

RMAN> crosscheck backup;

RMAN> delete expired backup;

The crosscheck command should be used only in cases where files marked with the status

“Available” that no longer exist can be expired and marked deleted RMAN should control the retention using the following command If you configure the channel with the tape parameters,

there is no need to allocate channels This feature is available in Oracle 9i Database and newer

versions

RMAN> allocate channel for maintenance type 'SBT TAPE';

RMAN> delete noprompt obsolete;

RMAN Sample Scripts

Something particularly clever about the NetBackup for Oracle agent installation is that it includes

RMAN backup and recovery sample scripts that are pre-instrumented (that is, they already include code snippets or templates) with code for using NetBackup Look for the sample scripts in

/<install_path>/netbackup/ext/db_ext/oracle/samples/rman

These sample scripts will be included:

cold database backup.sh hot database backup proxy.sh cold duplex database backup full.sh hot tablespace backup.sh

database restore.sh hot tablespace backup proxy.sh hot database backup.sh

pit database restore.shNew scripts can be generated from the Administration Console For anyone who has suffered through the time-consuming effort of trying to locate elusive punctuation errors, these scripts come as a pleasant surprise

The following is an RMAN code snippet for calling NetBackup:

rman target / catalog <user>/<password>@rman cat db log <my output.log>

run { allocate channel t1 type 'SBT TAPE' parms "ENV (NB ORA SERV <storage server>,

NB ORA POLICY RMAN DEFAULT, NB ORA CLIENT <db server>)";

backup database format 'db %d%U%t' }

The NetBackup Administrator’s Guide recommends adding a %t at the end of the format

string, since NetBackup uses a timestamp as part of its search criteria for catalog images You

can also do this by using configure.

The following is an RMAN code snippet for calling NetBackup that uses configure

commands:

rman target / catalog <user>/<password>@rman cat db log <my output.log>

rman> CONFIGURE CHANNEL DEVICE TYPE 'SBT TAPE' PARMS 'SBT LIBRARY /<install path>/netbackup/bin/libobk.so64.1, ENV (NB ORA SERV <storage server>, NB ORA POLICY <policy name>,

NB ORA CLIENT <db server>)';

rman> CONFIGURE DEVICE TYPE 'SBT TAPE' FORMAT 'db %d%U%t' rman> backup database;

Troubleshooting

Inevitably, something will break in the environment Knowing how to prioritize problems in advance helps to resolve them more smoothly This section highlights steps to help troubleshoot issues

The following are general troubleshooting steps to take:

1 Verify Oracle agent installation by making sure that the proper libraries exist in /<install_

path>/netbackup/bin Refer to Table 7-2 earlier in the chapter to determine which library (for example, libobk.a) corresponds to your operating system

2 Check the database server (client) to ensure that the bphdb executable exists This is used

by both the NetBackup scheduler and the GUI to start backups

3 Check that the following executables exist:

/<install_path>/netbackup/bin/bpdbsbora /<install_path>/netbackup/bin/bpubsora /<install_path>/lib/libdbsbrman.so /<install_path>/lib/libnbberman.so

4 Check that the following /<install_path>/netbackup/logs directories exist with

777 permissions:

On the database server (client): bpdbsbora, dbclient, bphdb, and bpcd

On the master server: bprd and bpdbm

On the media server: bpbrm and bptm

Use NetBackup Logs

NetBackup generates logs for backup and restore operations These logs can be used to investigate media manager problems, but RMAN errors will be written to the RMAN logs There are two types of NetBackup logs:

Progress logs Located in /<install_path>/netbackup/logs/user_ops/username/logs, these

logs are generated for any backup or restore operations These files can sometimes be large and cumbersome They contain sizable amounts of data The key here is knowing

how to extract the data you need There are basically two error types, numbers 16 and 32; 16 is an error failure and 32 is a critical failure The best way to find them is to search the log files for <16> and <32>.

Debug logs Each debug log corresponds to a NetBackup process and executable When

debugging is turned on, the logs are written to /<install_path>/netbackup/logs These logs can grow quickly in size, so use debugging only when necessary

To enable logging on the database server (client), modify the /<install_path>/netbackup/bp.conf file with this line:

Determine Which Library Is in Use

Find out which NetBackup library is interfacing with Oracle:

ls -l $( echo $LD LIBRARY PATH | sed -e "s/:/ /g")/libobk* | grep libobk

Security Best Practices

Since the NetBackup software runs in a networked environment, it is susceptible to vulnerabilities such as denial of service attacks To prevent these situations from happening, the following best practices are recommended by Veritas, which is now Symantec:

Allow administrative access to privileged users only

Allow remote access only from trusted servers

Apply the latest patches

Install NetBackup behind a firewall

Ensure virus protection is running on the servers

Monitor network traffic for malicious activity

Block external access to the default ports used by NetBackup

NetBackup server and clients should face toward the internal network

Cost Justification

It’s not always easy to justify the costs of purchasing expensive software and licenses for an information technology department, which is traditionally considered to be a non-revenue generating part of an organization This section provides some ideas for demonstrating to

management the value of purchasing VERITAS NetBackup for Oracle.

The NetBackup for Oracle software extends the capabilities of RMAN Since the software

allows RMAN to speak directly to storage servers, it automates processes that would otherwise

be done by people It shortens backup and recovery time by eliminating some steps altogether and by cutting out process variation Essentially, this translates into better overall application performance (since backups take less time), reduced business outages during recovery events, more error-free recoveries, and greater productivity of database and storage administrators.The NetBackup software could easily pay for itself during just one significant business outage where productivity and revenue are negatively impacted

Summary

We have explored how NetBackup software is used to facilitate a networked backup and recovery environment We outlined the ways in which it extends existing RMAN functionality We described how to configure each layer for direct component communication, which eliminates the need for manual intervention We discovered that using NetBackup to enhance RMAN results in faster backup and recovery, reduced process variation, and shorter business outages during recovery

events NetBackup for Oracle software has been thoughtfully developed for those of us who are

excited about easily deployed and feature-rich backup and recovery solutions

Configuring HP Data Protector for Oracle

n large environments, it’s hard for database administrators to schedule, manage, monitor, and report all database backups centrally Another challenge for DBAs

is managing the backup media: setting the protection, monitoring the usage, and checking on the backup history For HP customers, using a backup user interface with RMAN such as HP Data Protector overcomes all these issues

This chapter begins with a discussion of the integration between Oracle RMAN and HP Data Protector It then describes the configuration of Oracle backups with Data Protector You will learn how to back up and restore an Oracle database with Data Protector Finally, you will learn how to set up synchronization between Oracle RMAN Metadata and Data Protector Media Management Database

Integration of Oracle and Data Protector

You must properly integrate Oracle and Data Protector in order to run successful backup/restore operations To integrate them, therefore, you’ll now learn about the support matrix and the integration components, and do a workshop on integration configuration

Support Matrix

HP Data Protector A.06.00 supports Oracle 11g Recovery Manager on the following operating

systems:

Oracle 11g 64-bit Oracle 11g 32-bit

HP-UX 11.23 (64-bit) (Itanium and PA-RISC)HP-UX 11.31 (64-bit) (Itanium and PA-RISC)Solaris (Sparc) 9, 10 (64-bit) (x86 and x64)Oracle Enterprise Linux 4.0, 5.0 (64-bit) (x64)Oracle Enterprise Linux 5.3 (64-bit)

Red Hat Enterprise Linux 3.0, 4.x, 5.x (x64)

SuSE Linux Enterprise Server 9, 10 (x64)Windows Server 2003 (x64)

Windows Server 2008 (32-bit) (64-bit)

AIX 5.x, 6.1

SuSE Linux Enterprise Server 9 and 10

Red Hat Enterprise Linux 3.0, 4.x, 5.x Oracle Enterprise Linux 4.0, 5.x (32-bit)

Windows Server 2003 (32-bit)

Integration Components

For Oracle and Data Protector integration, RMAN and the Data Protector Oracle Integration software work together to accomplish backup, copy, restore, recovery, and duplication operations The Data Protector Oracle Integration agent uses the information in the recovery catalog or

in the control file to determine how to execute the requested backup and restore operations By using this integration, you can perform Oracle full and incremental (up to incremental level 4) backups Oracle incremental backups can be differential or cumulative By default, Data Protector performs Oracle differential incremental backups By changing the default RMAN script created

by Data Protector, you can specify a cumulative backup

I

Even if you configure an Oracle incremental backup, you won’t see the backup definition as “incremental” in Data Protector Data Protector will mark it “full,” because Data Protector incremental backup is a different concept, used on file system backups.

With Data Protector, both online and offline database backups can be performed However,

successful backups require proper configurations For an online database backup, the database instance must be in ARCHIVELOG mode, and for an offline database backup, the database needs

to be prepared for backup with the Pre-exec and Post-exec options in the backup specification You can use these options for shutting down the database or making a tablespace offline before backup, and then reverse operations after backup

Figure 8-1 shows the general architecture of Oracle and Data Protector integration

Data Protector User Interface

Data Protector Cell Manager

IDB

Ob2rman.pl

DP backup specification SM

Devices Media Agent Clients

ORACLE Data Protector MML

RMAN

Datafiles Control files Archived logs

Oracle Server Executables Backup API

RMAN Recovery Log

MA

Data

Control

The components of this integration, as shown in Figure 8-1, are

SM The Data Protector Session Manager, which manages the backup and restore sessions.

MA The Data Protector General Media Agent, which reads and writes data from and to media

devices

Data Protector MML The Data Protector Oracle Integration Media Management Library, which

is a set of routines that enables data transfer between the Oracle server and Data Protector The Data Protector MML links Data Protector and Oracle server software

Ob2rman.pl The Data Protector Oracle Integration agent, which works with RMAN to manage

all aspects of the backup/recovery operations on the Oracle target database

Backup API The Oracle-defined application programming interface.

IDB The Internal Database, where all the information about Data Protector sessions, including

session messages, objects, data, used devices, and media, is written

RMAN The Oracle Recovery Manager.

RMAN WORKSHOP: Integration Configuration

Workshop Notes

To run a successful RMAN backup of an Oracle Database using Data Protector Integration, you should have the Oracle target database mounted or opened, the recovery catalog database configured and opened if being used, Oracle Net Services properly configured, and Data Protector Disk Agent, Media Agent, and Oracle Integration installed on the server the target database resides on

In this workshop, it is assumed that devices and media are ready for use, and that Data Protector Cell Manager is installed and properly configured HP OpenView Storage Data Protector Manager software, which may reside in a PC, will be used to configure the integration

Step 1. First you must install the Data Protector agent to target server

a Run HP OpenView Storage Data Protector Manager software and connect the Cell Manager

b In the Context List, select Clients, and in the Scoping Pane, right-click Clients and click

Add Clients

c In the Add Client Systems window, select the platform of the target server (Windows or

Unix), and choose the installation server, which can be the Cell Manager Click Next

d Type the IP or host name (if it can be resolved) of the target server in the Name box and

click Add Click Next (see Figure 8-2)

e Select the components you want to install For Oracle Database backups, Disk Agent,

Media Agent, and Oracle Integration must be installed on the target server Select the components and click Finish (see Figure 8-3) After the installation completes, continue the configuration with Step 2

FIGURE 8-2 Defining client IP/host name

FIGURE 8-3 Component selection

Step 2. MML is invoked by the Oracle server when it needs to write to or read from devices using Data Protector For this integration to work properly, a manual link needs to be created between Oracle server software and the Media Management Library on the target system MML

is located in the following directory:

HP-UX and Solaris /opt/omni/lib Other Unix /usr/omni/lib

The filename for the MML also differs depending on the platform, as shown in the following table:

HP-UX libob2oracle8.sl libob2oracle8_64bit.slHP-UX on IA-64 libob2oracle8.so libob2oracle8_64bit.soSolaris libob2oracle8.so libob2oracle8_64bit.so

Other Unix libob2oracle8.so libob2oracle8_64bit.soNow, proceed as follows:

a Change to the <ORACLE_HOME>/lib directory.

b Run:

HP-UX mv libobk.sl libobk.sl.orig Other Unix mv libobk.so libobk.so.orig NOTE

Perform the preceding step only if the libobk.sl (HP-UX) or libobk so (other Unix) file is already created in the <ORACLE_HOME>/lib directory Otherwise, skip this step.

c Run:

HP-UX 32-bit ln -s /opt/omni/lib/libob2oracle8.sl libobk.sl 64-bit ln -s /opt/omni/lib/libob2oracle8_64bit.sl libobk.sl Solaris

32-bit ln -s /optS/omni/lib/libob2oracle8.so libobk.so 64-bit ln -s /opt/omni/lib/libob2oracle8_64bit.so libobk.so

■

■

■

■

Other Unix 32-bit ln -s /opt/omni/lib/libob2oracle8.so libobk.so 64-bit ln -s /opt/omni/lib/libob2oracle8_64bit.so libobk.so

If you start a backup without manually linking Oracle server software and MML as just shown, you will probably see this error message:

RMAN Backup Configuration on Data Protector

To configure an Oracle RMAN backup configuration on Data Protector, decide which devices, media pool, and media will be used for that backup operation Then you can create the Data Protector Oracle backup specification

Data Protector offers database backup templates that can be used when creating the backup specification You can also create templates tailored to your needs

RMAN WORKSHOP: Backup Configuration

Workshop Notes

Now that you have added the target host to Data Protector successfully, you can define a backup specification Using this specification, you will be able to start the backup immediately or to schedule it to run within a specific period

Step 1 Run HP OpenView Storage Data Protector Manager and connect the Cell Manager Step 2 In the Context List, select Backup; in the Scoping Pane, expand Backup Specifications;

then, right-click Oracle Server and click Add Backup

Step 3 In the Create New Backup window, you can select one of the predefined backup templates,

or select Blank Backup to specify backup operation details later (see Figure 8-4) Click OK

Step 4 In the next window, Data Protector asks for Client, Application Database, Username,

and Group Name information Specify the client the target database resides in, the SID of the target database, the username, and the name of the group that owns the Oracle instance (see Figure 8-5) Click Next

■

■

FIGURE 8-4 Template selection

FIGURE 8-5 Target selection

Step 5 In the Configure Oracle window, specify information about the target database On

the General tab, specify the Oracle Server Home Directory (see Figure 8-6) On the Primary tab, specify username, password, and service information Don’t forget that this user must have been granted Oracle SYSDBA or SYSOPER rights Service is the name used to identify

an SQL*Net server process for the target database The Catalog tab requires the username, password, and service information for the Catalog database if it’s being used The last tab, Standby, is necessary to fill if the Oracle Data Guard environment is in use and will be backed

up Click OK

Step 6 This step asks you to specify which components of the database you want to back up

If you selected Blank Backup in Step 3, you will see all components unchecked (see Figure 8-7) Select the components you want to back up and then click Next

Step 7 Now, Data Protector asks you which hardware will be used for this backup Select the

drive that you want to use (see Figure 8-8) If you defined it earlier, you can also specify the Media Pool that will be used for the backup Select the drive and click Properties You’ll see a drop-down menu to select a Media Pool Make your choice and click Next

FIGURE 8-6 Oracle configuration

FIGURE 8-7 Database component selection

FIGURE 8-8 Device/drive selection

Step 8 This step allows you to specify detailed configuration As you can see in Figure 8-9, the

three categories each have an Advanced button You can define pre- and post-execution scripts under Backup Specification Options You can define backup objects’ protection and report level under Common Application Options Lastly, you can see an overview of the prepared RMAN script and disable/enable Data Protector managed control file backup under Application Specific Options Make your selections and click Next

Step 9 You can schedule the configured backup in this step Specify the dates and times that

you want backups performed Select the Holiday box if you want to indicate that you do not want scheduled backups to run on holidays

Step 10 This last step gives you three options:

Save as Save the newly created backup/template.

Start Backup Begin an interactive backup with the current backup specification.

Start Preview Begin an interactive preview (test) of backup with the current backup

Editing the Oracle RMAN Script

You can edit the RMAN script section only after the Data Protector Oracle backup specification has been saved

To manually edit the RMAN script, in the Context List, select Backup; in the Scoping Pane, expand Backup Specifications; expand Oracle Server; and click the backup specification that you will edit On the Options tab, click Advanced in the Application Specific Options box The RMAN script appears with an Edit button When you click Edit a warning will appear as:

“This operation will save the backup specification now and reopen the editor after the RMAN Script is saved Would you like to continue?”

Click Yes and manually configure the script You can save the configuration by clicking Save

If the RMAN script contains additional manually entered backup commands—for example,

a second backup command for backing up a database that is already listed in the first backup command—the object selection is disabled, and it is only possible to browse the Source tab

Use either Data Protector GUI or the Data Protector CLI to start an interactive backup of

a predefined Oracle backup specification

Use Data Protector Scheduler to schedule a backup of a predefined Oracle backup specification

Use either Oracle Recovery Manager or Oracle Enterprise Manager to start a backup on the Oracle server

Running an Interactive Backup

To start an interactive backup of an Oracle database using the Data Protector GUI:

1 In the HP OpenView Storage Data Protector Manager (Data Protector GUI), select Backup

in the drop-down menu

2 In the left pane, choose Backup | Backup Specifications | Oracle Server.

3 Right-click the backup specification you want to start and select Start Backup.

Scheduling a Backup

To schedule an Oracle backup specification:

1 In the HP OpenView Storage Data Protector Manager, select Backup in the drop-down menu.

2 In the left pane, choose Backup | Backup Specifications | Oracle Server.

3 Double-click the backup specification you want to schedule and click the Schedule tab.

■

■

■

4 In the Schedule page, select a date in the calendar, and click Add to open the Schedule

Backup dialog box

5 Specify necessary scheduling options.

Starting Oracle Database Backup Using RMAN or Enterprise Manager

You can also use RMAN CLI or Enterprise Manager to perform backups of Data Protector integrated databases To use Data Protector backup media in Oracle database backups, you must specify the channel type SBT_TAPE

Backup Procedure

When a backup is started with Data Protector, the following happens in the background:

1 Data Protector executes ob2rman.pl, which starts RMAN on the client and sends the

preconfigured RMAN script

2 RMAN contacts the Oracle server, which contacts Data Protector via the MML interface

and initiates the backup

3 During the backup session, the Oracle server reads data from the disk and sends it to

Data Protector for writing to the backup device

4 Messages from the Data Protector backup session and messages generated by Oracle are

logged to the Data Protector database

Restoring Oracle Using the Data Protector GUI

You can restore the following database objects by using both the Data Protector GUI and RMAN:

Control filesDatafilesTablespacesDatabasesRecovery catalog databasesYou can also duplicate a database by using the Data Protector GUI You need to create an Oracle instance in order to restore or duplicate a database

Before you restore any database item or you duplicate a database, ensure that the database is

in the correct state:

Item to Restore Database State

Control file, duplicating a database Nomount (started)

NOTE

When restoring only a few tablespaces or datafiles, the database can

be open with the tablespaces or datafiles to be restored offline.

For restore, RMAN scripts are generated with necessary commands, depending on selections made in the GUI If you want to perform additional actions, you cannot edit the RMAN restore script, but you can perform the actions manually from RMAN itself.

Restoring the Control File

Depending on the type of the control file backup, three types of restore are possible when restoring the control file:

Restoring from Data Protector Managed Control File Backup (CONTROLFILE FROM DP MANAGED BACKUP)

The control file was backed up automatically by ob2rman.pl at the end of a backup session, unless the option “Disable Data Protector managed control file backup” was selected

The recovery catalog is not required for this restore option

The control files are restored to the following locations:

Windows <Data_Protector_home>\tmp\ctrl<DB_NAME>.dbf HP-UX and Solaris /var/opt/omni/tmp/ctrl<DB_NAME>.dbf Other UNIX /usr/opt/omni/tmp/ctrl<DB_NAME>.dbf

After the restore session finishes, you must run the following script:

run { allocate channel 'dev0' type disk;

restore controlfile from '<TMP FILENAME>';

release channel 'dev0';

}where <TMP_FILENAME> is the location to which the file was restored

Restoring from RMAN Autobackup (CONTROLFILE FROM RMANAUTOBACKUP)

The control file was automatically backed up by RMAN, and the recovery catalog is not available

Restoring from RMAN Backup Set (CONTROLFILE FROM RMANBACKUPSET)

The recovery catalog is required

Restoring Oracle Database Objects

To restore Oracle database objects:

1 Put the database in the mount state.

2 In the Data Protector GUI, switch to the Restore context.

3 Under Restore Objects, expand Oracle Server, expand the client on which the database

whose objects you’re restoring resides, and then click the database

4 In the Restore Action drop-down list, select the type of restore you wish to perform.

5 In the Results Area, select objects for restore If you are restoring datafiles, you can restore

the files to a new location Right-click the database object, click Restore As, and in the Restore As dialog box, specify the new datafile location

When restoring to a new location, current datafiles will be switched to the restored datafile copies only if you have selected Perform Restore and Recovery from the Restore Action drop-down list.

6 On the Options page, from the Client drop-down list, select the client on which the

Data Protector Oracle Integration agent will be started To restore the database objects

to a different database than the agent has selected, click Settings and specify the login information for the target database

7 In the Devices page, select the devices to be used for the restore You can restore using

a device other than that used for backup, although Data Protector defaults to the original device on which the backup was made To change the device from which an item is restored, select your desired device and click Change

Data Protector has its own data protection policy that is not automatically synchronized with Oracle RMAN metadata To have both catalogs synchronized, run the following command using RMAN:

allocate channel for maintenance type 'sbt tape' parms 'ENV=(OB2MAINTENANCE=1)';

crosscheck backup completed after "TO DATE('01/13/10 12:00:00','MM/DD/YY HH24:MI:SS')";

To delete expired backup objects from the recovery catalog database, run the following command using RMAN:

delete expired backup;

Summary

This chapter has given an overview of using HP Data Protector software for Oracle RMAN backups After you configure the integration properly, preparing and scheduling backup configurations that meet your backup needs, it will be easy to manage the backup/restore operations

RMAN and Tivoli Storage Manager

f you already use Tivoli Storage Manager (TSM) for backing up files in your enterprise, taking the next step and using TSM to back up your Oracle database makes a lot of sense: you not only can leverage an existing data protection asset, but also get a seamless connection from Oracle’s RMAN utility to TSM With only

a few minor modifications to your RMAN scripts and a straightforward one-time TSM client installation, you won’t even know that the tape or disk drive you’re using for backup

is on a different server In your DBA role, you may never even have to run a TSM console command

In this chapter, we’ll cover a number of topics related to TSM, the TSM client in general, and

the add-on module known as Tivoli Data Protection for Oracle (TDPO) First, we’ll give you a

brief overview of the TSM architecture and how an Oracle client connects to it Your in-depth involvement with TSM begins when you must test and configure TDPO on the server where you will perform the RMAN backup commands

Throughout this chapter, we’ll briefly cover a couple of TSM and Oracle client utilities that you will use to perform initial and routine configuration and monitoring tasks

We’ll next perform a couple of backups using RMAN and see the effect of this backup in the storage pool assigned to your TSM Oracle client

At the end of the chapter, we will cover a couple of common problems you might encounter

in backing up Oracle databases with TSM and TDPO and how to resolve them

Overview of Tivoli Storage Manager

TSM is a multitiered architecture: when you use it to back up an Oracle database, you may have as many as four tiers In contrast, you could host all tiers on a single server, but this is not recommended in a distributed environment where you want to keep your backup server separate from the server whose data you want to back up

Figure 9-1 is a diagram of a typical TSM environment In the next few sections, we’ll drill down into a few of the components shown in Figure 9-1 and explain some TSM concepts along the way

Table 9-1 outlines the nodes shown in Figure 9-1 These nodes are used in the examples throughout this chapter to show you how you can distribute the TSM components across your network

Table 9-2 lists and briefly describes the disk devices you will use on server tsm01 for your Oracle RMAN backups

TSM Server System Objects

The multilevel structure of system objects in a TSM server makes it easy to optimally configure your backups for each of the wide variety of data sources in your environment For the same reason, this flexible hierarchy also makes it easy to assign a specific configuration to unrelated data sources! Figure 9-2 shows the relationship between TSM system objects as well as the types and number of objects that a client uses on any given TSM server

I

for Oracle; TSM clientwinxp07 Windows XP Integrated Solutions Console/Administration Center

web client

TABLE 9-1 TSM Node Names and Roles

Physical Device Name Linux Mount Point Capacity Purpose

/dev/sda1 /tsm01 3.5GB Disk 1 for Oracle backup pool/dev/sdb1 /tsm02 3.5GB Disk 2 for Oracle backup pool/dev/sdc1 /tsm03 3.5GB Disk 3 for Oracle backup pool/dev/sdd1 /tsm04 3.5GB Disk 4 for Oracle backup pool

At the highest level is the policy domain: a policy domain consists of one or more policy sets, and each policy set consists of one or more management classes Each management class can have one archive copy group and one backup copy group We’ll tell you more about each of these objects in the following sections.

Policy Domain

A policy domain is a group of clients with similar requirements for backing up and archiving data

You might use a policy domain for everyone in a particular department, a particular building or floor, or all users of a specific file server

A default TSM installation includes one default policy domain called standard For the examples later in this chapter, we will use the standard policy domain You assign backup

clients to a policy domain

Policy Set

A policy set is a group of management classes Each policy domain can contain one or more

policy sets, but only one policy set in a policy domain can be active at any given time You use policy sets to easily switch between available management classes

Management Class

A management class is a collection of zero, one, or two copy groups You designate one

management class within a policy set as the default management class You typically use management classes to partition client data based on its criticality to the business, how frequently

it changes, or whether the data must be retained indefinitely A management class can have at most one backup copy group and at most one archive copy group

FIGURE 9-2 Client/TSM relationship and TSM system objects