Databases Reference
In-Depth Information
In this case, it makes sense for RMAN to create the backup pieces on multiple file systems. Usually you define as
many channels as there are mount points. So, you can have mount points such as /oraback/loc1, /oraback/loc2, and
so on. In our example script, we're assuming there are eight mount points: /oraback/loc1 through /oraback/loc8.
Accordingly, we have configured eight channels.
We use three types of parameters in the script:
Fixed: The parameters that are fixed for a site. Examples of such parameters are the e-mail
addresses of DBAs, the name of the central log server, and so on. These parameters do not
change from database to database.
DB specific: The parameters that change between databases. Examples are the Oracle SID,
the Oracle Home, the type of the backup (full, incremental, and so on), and the media,
such as tape and disk.
Derived: The parameters that are derived from the previous two types of parameters.
Examples are the location of the
rman
executable in the bin directory of Oracle Home, and
so on. You don't need to change these parameters.
Table
9-1
shows a line-by-line explanation of the script.
Table 9-1.
Line-by-Line Explanation of the Unix Shell Script to Back Up via RMAN
Line Number
Explanation
3
The Oracle Home for that database. Change for another database.
4
The SID of the database being backed up.
5
The location on the server where this script is executed.
6
The media where the backup is stored, such as tape or disk. This parameter is only for naming
the log file, not for directing the target of the backup.
7
The type of backup, such as full or incremental. This is only for naming the log file. This
parameter does not actually cause the backup to be full or otherwise.
The
MAXPIECESIZE
parameter for RMAN. This parameter in RMAN creates the backup pieces to
be limited to a certain size, which is a limitation on some operating systems. The limit should
be based on the database size as well. If your database is fairly small and you want to remove
any limit, just specify a very high number. In this example, we have assumed a 16GB limit.
8
11
The backups will be made to /oraback/loc1 through /oraback/loc8.
12
The e-mail that says where the successful notification should be sent.
13
The e-mail that says where the failure e-mail should be sent, usually a pager.
14
The server where the log files of each run are stored.
15
The user ID of the log server.
16
The directory where the logs are kept on the central log server.
17
The connection string for the catalog connection. Here we assume that your catalog database
connect string is
catalog
and you have defined a separate catalog owner for each database,
where the owner's name is the same as the SID of the database being backed up and the password
is the same as the owner name. This is not absolutely necessary; you can have a common owner
for catalogs of all databases. Whatever your decision is, update this parameter to reflect that.
(
continued
)
