Veritas NetBackup™ for SAP Administrator's Guide
- Introduction to NetBackup for SAP
- Introduction to NetBackup SAP HANA
- Installing NetBackup for SAP
- Installing NetBackup for SAP HANA
- Configuring NetBackup for SAP
- About configuring a backup policy for an SAP database
- NetBackup for SAP backup scripts
- About SAP configuration files
- Configuring NetBackup for SAP HANA
- Performing backups and restores of SAP
- Using BRTools to start an SAP backup (for Oracle database only)
- Performing an SAP archive
- Restarting failed NetBackup for SAP backups and restores
- Performing backups and restores of SAP HANA
- NetBackup for SAP with Snapshot Client
- How the NetBackup for SAP Snapshot Client works
- About configuring Snapshot Client with NetBackup for SAP
- About configuring NetBackup for SAP block-level incremental backups on UNIX
- Configuring policies for BLI backups with NetBackup for SAP
- About NetBackup for SAP restores of volumes and file systems using snapshot rollback
- NetBackup for SAP on MaxDB databases
- Troubleshooting NetBackup for SAP and SAP HANA
- NetBackup debug logs and reports
- sapdba logs and messages (Oracle-based SAP environments only)
- About troubleshooting NetBackup for SAP HANA
- Appendix A. backint command line interface
- Appendix B. Input and output files for SAP HANA
- Appendix C. backint -i in_file contents
- Appendix D. backint -o out_file contents
- Appendix E. NetBackup for SAP environment variables for backint
- Appendix F. NetBackup for SAP configuration or bp.conf file settings
- Appendix G. Parameters used in initSID.utl
- sort_backup_type <value>
- sort_restore_type <value>
- Appendix H. Configuring split mirror backups
- Appendix I. Register authorized locations
Redirecting a restore to a different client (SAP on Oracle databases only)
You have the option to restore an SAP database to a client other than the one that originally supplied the backup. This process to restore data to a different client is called a redirected restore.
Note:
In some situations, you can restore from lower to higher release levels of Oracle. For more information, see your Oracle documentation.
To perform a redirected restore, the following conditions must be present:
The source client and destination client must have identical computer system architectures, OS versions, and bit levels.
The source client and destination client must have identical Oracle RDBMS levels.
The redirected restore has the following process:
Configure the NetBackup server.
Copy files from the source client to the destination client.
Configure the NetBackup for SAP destination client.
Perform the redirected restore.
The following procedures explain each part of the process. For more information on redirected restores, see the NetBackup Administrator's Guide, Volume 1.
To configure the NetBackup server
- Verify that you are logged on as the NetBackup administrator.
- To allow any client to restore the backups of any other client, create the following file on the NetBackup master server:
Windows:
install_path\NetBackup\db\altnames\No.Restrictions
UNIX or Linux:
/usr/openv/netbackup/db/altnames/No.Restrictions
- Continue with step 7.
- To allow only the destination client to restore from all other clients, create the following file:
Windows:
install_path\NetBackup\db\altnames\client_name
UNIX or Linux:
/usr/openv/netbackup/db/altnames/client_name
where client_name is the name of the destination client that is allowed to perform the redirected restore.
- If you performed step 5, and want to restrict the destination client to only restore from the source client, add the name of the NetBackup for SAP source client to the client_name file.
- On the destination client, back up the existing control files to preserve the original configuration.
These files are usually in the $ORACLE_HOME/dbs (%ORACLE_HOME%\database) directory.
To configure the NetBackup for SAP destination client
- Change the client parameter on the destination client.
Do one of the following:
Change the client parameter in the initSID.utl file on the destination client to the name of the source client.
Set the SAP_CLIENT environment variable on the destination client to the name of the source client. For example:
SAP_CLIENT=source_client export SAP_CLIENT
The SAP_CLIENT variable has higher priority than the value in the initSID.utl file.
- (Windows) On the destination client, create a file path like the one on the source client.
For example:
Source client actual path is:
C:\Oracle\SAP
Destination client actual path is:
C:\Oracle\SAP
- (UNIX or Linux) Create a symbolic link on the destination client that resembles the actual path of the source client. Point it to the directory that points to the SAP files.
To copy the configuration and the control files (UNIX or Linux)
- Copy configuration and control files from the NetBackup for SAP source client to the NetBackup for SAP destination client.
Copy the following files from the source client, usually $ORACLE_HOME/dbs, to the same location on the destination client:
initSID.sap initSID.utl initSID.ora initSID.dba
Copy the $SAPDATA_HOME/sapbackup directory from the source client to the same location on the destination client.
To copy the configuration and the control files (Windows)
- Copy configuration and control files from the NetBackup for SAP source client to the NetBackup for SAP destination client.
Copy the following files from the source client, usually %ORACLE_HOME%\database, to the same location on the destination client:
initSID.sap initSID.utl initSID.ora initSID.dba
Copy the %SAPDATA_HOME%\sapbackup directory from the source client to the same location on the destination client.
To perform a NetBackup for SAP redirected restore
- Log onto the NetBackup for SAP destination client.
- Enter the following command:
brrestore -d util_file -b last -m full
Do not use the -m dest_dir option with brrestore. This option restores the files to the directory you specify, rather than to the original directories.