Oracle RMAN 11g Backup and Recovery (71 page)
Read Oracle RMAN 11g Backup and Recovery Online
Authors: Robert Freeman
Chapter 9: RMAN and Tivoli Storage Manager
191
FIGURE 9-1
TSM architecture
Node Name
Operating System
Role
tsm01
Linux
TSM server
tsmadmin
Linux
Integrated Solutions Console, Administration Center
server
oc1
Linux
Oracle database, Tivoli Data Protection
for Oracle; TSM client
winxp07
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
TABLE 9-2
Raw Disks for TSM Storage Devices
192
Part II: Setup Principles and Practices
FIGURE 9-2
Client/TSM relationship and TSM system objects
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.
Chapter 9: RMAN and Tivoli Storage Manager
193
Backup Copy Groups and Archive Copy Groups
A
copy group
specifies the common attributes that control these characteristics of a backup or archive file:
■
Generation
How many copies of each file are retained
■
Destination
Which storage pool will contain the backup
■
Expiration
When a file will be deleted because the expiration date or retention period has passed
A
backup copy group
contains attributes that control whether a file that has changed since the last backup is backed up again, how many days must elapse before a file is backed up again, and how a file is processed if it is in use during a backup. In contrast, an
archive copy group
contains attributes that control whether a file is archived if it is in use, where the server stores archived copies of the files, and how long the server keeps archived copies of the files. TDPO only uses backup copy groups for Oracle backups.
TSM Client
You install the client piece of TSM, which includes the TSM API, on any server that needs to use a TSM server for backup or recovery. Also included in an installation on an Oracle server is the RMAN library interface to TSM: Tivoli Data Protection for Oracle (TDPO).
Real World Example
Suppose you are working for a web site development and hosting company. The company has several production Oracle databases that are backed up using TDPO and TSM by using a common management class. The backups are stored on tape for 30 days before the backups are deleted. Also, backups are copied to an offsite storage location the next day. Also, several nonproduction databases are used by developers for development web sites.
When you arrive Monday morning, you find that a hardware failure has occurred that hosts a nonproduction database. A disk failure has resulted in several online redo logs and all control files being lost. Since there are no backups, you spend several days re-creating the database, and the developers spend several more days redoing their changes. Afterward, management would like to start backing up development databases as well. But to keep the cost of tape storage down, the backups will only be kept for seven days, and backups will not be stored offsite.
You decide the best way to meet both requirements without impacting your production backups would be to create a second management class. You ask your TSM administrator to create a new management class that has a seven-day retention period and won’t be copied offsite. When backing up nonproduction databases, you reference this new management class. Nonproduction databases can be backed up and retained for seven days and will not be copied offsite, and the production backups will not be affected.
194
Part II: Setup Principles and Practices
Using TDPO, RMAN can back up these database objects to TSM:
■ Databases
■ Tablespaces
■ Datafiles
■ Archive log files
■ Control files
■ Pfiles and Spfiles
Plus, you can perform a full database restoration while the database is offline; you can perform tablespace or datafile restores while the database is either online or offline.
The server oc1 is a client node in an Oracle Real Application Clusters (RAC) database in Figure 9-1 and is a client of TSM on server tsm01.
TSM Administration Center and Web Client
The Administration Center is a web-based interface that you use to centrally configure and manage IBM TSM version 5.3 servers. You install it as an IBM Integrated Solutions Console (ISC) component—as a result, you can use ISC to manage a number of heterogeneous systems and applications using a common management interface.
In Figure 9-1, the server tsmadmin hosts ISC and the Administration Center plug-in. TSM
administrators use a web browser on the workstation winxp07 to connect to ISC on tsmadmin, which in turn sends console commands and receives status information from the TSM server tsm01. You can administer TSM using this method from any web browser that has a network connection to server tsmadmin.
RMAN Workshop:
Configuring TDPO for Oracle
Workshop Notes
For this workshop you will need an operational TSM server and client environment and Oracle database home installed.
Step 1.
To install TDPO on your Oracle server, you need to install the following RPM packages:
■
TIVguid.i386.rpm
Creates a globally unique identifier (GUID) to uniquely distinguish this server from other servers that will access TSM
■
TIVsm-API.i386.rpm
Installs the application program interface (API) libraries to support TDPO or any other application that will programmatically access TSM
■
TDP-Oracle.i386.rpm
Contains the libraries and link definitions that Oracle RMAN will use to connect to TSM
Here is what you see when you install TDP-Oracle:
Chapter 9: RMAN and Tivoli Storage Manager
195
[root@oc1 DPO]# rpm -i TDP-Oracle.i386.rpm
Post Installation of IBM Tivoli Storage Manager for Databases - Oracle.
Checking Tivoli Signature File.
Created Tivoli Signature File.
Creating symbolic links
created link /opt/tivoli/tsm/client/oracle/bin/libobk.so
/usr/lib/libobk.so
created link /opt/tivoli/tsm/client/oracle/bin/tdpoconf /usr/bin/tdpoconf Post Installation of IBM Tivoli Storage Manager
for Databases - Oracle Complete.
Be sure to set up the system configuration file
before starting the client!
[root@oc1 DPO]#
Step 2.
The next step is to register the client oc1 on the TSM server: TSM:SERVER1> reg node oc1 oracle orabakpw maxnummp 2 passexp 0
ANR2017I Administrator SERVER CONSOLE issued command:
REGISTER NODE oc1 oracle ?***? maxnummp 2 passexp 0
ANR2060I Node OC1 ORACLE registered in policy domain STANDARD.
ANR2099I Administrative userid OC1 ORACLE defined
for OWNER access to node OC1.
TSM:SERVER1>
Note that we’re setting
maxnummp=2
: this specifies the maximum number of parallel sessions that the client can use when backing up to tape. Even though we’re using disk drives for backup in these examples, it’s a good idea to define the parallelism you need on those occasions when you do back up to tape.
Registering a client node also creates an administrative account that you can use to connect to the TSM server; however, creating individual server accounts for each administrator gives you more control over privileges assigned to each administrator as well as more precise auditing information when an administrator changes the TSM server’s configuration.
Next steps are to connect the Oracle database on server oc1 to the TSM server on tsm01. You do this by:
1.
Defining the TDPO options in the configuration file tdpo.opt
2.
Creating dsm.opt
3.
Creating dsm.sys
4.
Registering the TDPO node with the TSM server and defining other policy requirements
5.
Configuring TSM copy group options
6.
Generating the password file for the TSM server
7.
Creating symbolic links in the Oracle library directory
8.
Testing TDPO connectivity
196
Part II: Setup Principles and Practices
Step 3.
Define TDPO options. On the Oracle client node oc1, change to the directory /opt/
tivoli/tsm/client/oracle/bin, and copy tdpo.opt.smp (the sample file) to tdpo.opt. The file tdpo.opt, as you might expect, defines the TDPO-specific options, such as how TDPO will connect to the TSM server. Uncomment the line beginning with TDPO_NODE and replace
************************************************************
* Data Protection for Oracle
*
* Sample tdpo.opt for the Linux86 Data Protection for Oracle
************************************************************
*DSMI LOG /opt/tivoli/tsm/client/oracle/bin
*TDPO FS /adsmorc
TDPO NODE oc1 oracle
*TDPO OWNER
*TDPO PSWDPATH /opt/tivoli/tsm/client/oracle/bin
*TDPO DATE FMT 1
*TDPO NUM FMT 1
*TDPO TIME FMT 1
*TDPO MGMT CLASS 2 mgmtclass2
*TDPO MGMT CLASS 3 mgmtclass3
*TDPO MGMT CLASS 4 mgmtclass4
Step 4.
Create dsm.sys. The file dsm.sys defines how to connect to each TSM server, specifying the port number, TCP/IP address, and so forth. Copy the file /opt/tivoli/tsm/client/api/bin/dsm.sys
.smp to /opt/tivoli/tsm/client/oracle/bin/dsm.sys and change the values as follows:
