HP 3PAR Recovery Manager 4.5.0 for Oracle on Solaris, Red Hat Linux, and Oracle Enterprise Linux User's Guide (QL226-97705, May 2014)
Backup Schedule 1. Create a schedule for full backup.
2. If you wish to perform client-side database backup (initiated from Recovery Manager), set the
backup window to 0.
3. If you also wish to perform server-side database backup (initiated from NBU), specify the backup
window to fit your needs.
Set the backup client to the host name of the backup server, as the backup process will actually
take place on the backup server.
Backup Clients
Configuring the NetBackup Policy for Archive Log Backup
This procedure is to backup the archive logs only. For Recovery Manager for Oracle to perform
backup and restoration correctly, you must use the following guidelines in conjunction with Symantec
NetBackup documentation when configuring a NBU policy:
Backup Attribute 1. Select the standard type for the policy.
2. Select the cross mount points option.
3. Deselect the Allow multiple data stream and Block level incremental options.
Backup
Selections
1. It is recommended that you enter /dummy for the backup selections.
2. Recovery Manager generates the backup selection list on the fly to replace the value you entered.
Backup Schedule 1. Create two schedules, one for full backup and one for incremental backup (optional). For the
incremental backup schedule, you can create either a differential incremental or cumulative
incremental backup schedule.
NOTE: Incremental backup of archive log using RMAN is not supported.
2. If you wish to perform client-side archive log backup (initiated from Recovery Manager), set the
backup window to 0.
3. If you also wish to perform server-side archive log backup (initiated from NBU), specify the
backup window to fit your needs.
Set the backup client to the host name of the backup server, as the backup process will actually
take place on the backup server.
Backup Clients
Setting Up NetBackup Configuration Parameters for the Backup Server
Recovery Manager uses bpstart and bpend scripts as a hook to NetBackup to create Virtual
Copy of a database, then present the database Virtual Copy to the backup server for backup, and
to cleanup the Virtual Copy after backup process completes respectively. The BPSTART_TIMEOUT
and BPEND_TIMEOUT in the /usr/openv/netbackup/bp.conf on the backup server should
be set to at least 600 seconds (10 minutes) to allow enough time for Recovery Manager to perform
all necessary operations prior to the actual backup.
For example, to set the BPSTART_TIMEOUT and BPEND_TIMEOUT parameters to 600 seconds
(10 minutes), modify the corresponding parameters in /usr/openv/netbackup/bp.conf on
the backup server as follows:
BPSTART_TIMEOUT = 600
BPEND_TIMEOUT = 600
Setting Up NetBackup Configuration Parameters for the Database Server
If a database is setup for High Availability (HA), then the CLIENT_NAME parameter in the /usr/
openv/netbackup/bp.conf on the database server should be set to the virtual host name of
the database server instead of the physical host name. This allows a backup image to be restored
to the actual database server even if the database has fail-overed to another database server.
For example, to set the CLIENT_NAME parameter to a virtual host name, modify the corresponding
parameter in the /usr/openv/netbackup/bp.conf on the database server as follows:
CLIENT_NAME = <virtual_hostname>
50 Configuring Recovery Manager for Oracle