290217

Veritas NetBackup for SAP Administrators Guide
for UNIX and Linux
Release 6.5
12308320
Veritas NetBackup for SAP Administrators Guide

Copyright 2007 Symantec Corporation. All rights reserved. NetBackup 6.5 Symantec, the Symantec logo, and NetBackup are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm. Copyright 1991-92, RSA Data Security, Inc. Created 1991. All rights reserved. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THIS DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID, SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software and commercial computer software documentation as defined in FAR Sections 12.212 and DFARS Section 227.7202. Symantec Corporation
20330 Stevens Creek Blvd.
Cupertino, CA 95014
www.symantec.com Printed in the United States of America.
Third-party legal notices

Third-party software may be recommended, distributed, embedded, or bundled with this Symantec product. Such third-party software is licensed separately by its copyright holder. All third-party copyrights associated with this product are listed in the accompanying release notes.
AIX is a registered trademark of IBM Corporation.
HP-UX is a registered trademark of Hewlett-Packard Development Company, L.P.
Linux is a registered trademark of Linus Torvalds.
Solaris is a trademark of Sun Microsystems, Inc.
Licensing and registration

Veritas NetBackup is a licensed product. See the NetBackup Installation Guide for license installation instructions.
Technical support
For technical assistance, visit http://entsupport.symantec.com and select phone or email support. Use the Knowledge Base search feature to access resources such as TechNotes, product alerts, software downloads, hardware compatibility lists, and our customer email notification service.
Contents
Chapter 1
Introduction
NetBackup for SAP features ...............................................................................12
NetBackup for SAP overview .............................................................................13
Technical overview ......................................................................................13
Sequence of operation .................................................................................15
NetBackup for SAP on Oracle databases ..................................................15
NetBackup for SAP on MaxDB databases .................................................19
Chapter 2
Installing the agent

Verifying the installation prerequisites ...........................................................21
Operating system and platform compatibility ........................................21
NetBackup software .....................................................................................22
Database software ........................................................................................22
Cluster software ...........................................................................................23
Installing NetBackup for SAP ............................................................................23
Remote installation of NetBackup for SAP ..............................................23
Local installation of NetBackup for SAP ..................................................31
Linking NetBackup for SAP with backint
(Oracle databases without RMAN only) ....................................................34
Linking the Oracle database with the SBT library
(Oracle databases with RMAN only) ..........................................................35
Chapter 3
Configuration
User interface terminology notes .....................................................................39
Configuring the Maximum jobs per client .......................................................40
Configuring a backup policy for a database .....................................................41
Adding a new policy .....................................................................................41
Adding schedules .........................................................................................43
Adding clients ...............................................................................................47
Adding backup selections ...........................................................................48
Backing up files mounted with LOFS ........................................................50
Creating scripts ....................................................................................................50
Modifying the backup scripts .....................................................................51
Script parameters ........................................................................................53
Modifying the configuration files .....................................................................54
Files to configure ......................................................................................... 54

Relationships between files ....................................................................... 54
Modifying the initSID.utl file ..................................................................... 55
Modifying the initSID.sap file
(NetBackup for SAP on Oracle databases only) ............................... 56
Modifying the bsi.env file
(NetBackup for SAP on MaxDB databases) ...................................... 59
Testing configuration settings .......................................................................... 61
Testing multiple drives and files ....................................................................... 62
Chapter 4
Using NetBackup for SAP

Performing a backup ........................................................................................... 65
Method 1: Using Netbackup schedules to start an SAP backup ........... 65
Method 2: Using BRTools to start an SAP backup (for Oracle database
only) ....................................................................................................... 66
Performing an archive ........................................................................................ 70
Method 1: Using the NetBackup multiple copies feature ...................... 70
Method 2: Using two brarchive commands in sequence ....................... 71
Performing a restore ........................................................................................... 72
Using the SAPDBA utility (NetBackup for SAP on Oracle databases
only) ....................................................................................................... 72
Redirecting a restore to a different client (NetBackup for SAP on Oracle
databases only) ..................................................................................... 72
Disaster recovery using BRRECOVER ...................................................... 76
Restarting failed backups and restores ............................................................ 76
Restarting backups ...................................................................................... 76
Restarting restores ...................................................................................... 81
Chapter 5
NetBackup for SAP with Snapshot Client

Using NetBackup for SAP to backup large databases .................................... 87
NetBackup for SAP with Snapshot Client overview ....................................... 89
Snapshot backup .......................................................................................... 90
Instant recovery ........................................................................................... 90
Off-host backup ............................................................................................ 90
Block-level incremental backup ................................................................ 90
RMAN proxy copy ........................................................................................ 90
RMAN stream-based backups .................................................................... 91
RMAN proxy and RMAN stream-based backups intermixed ................ 91
How does NetBackup for SAP Snapshot Client work? ................................... 91
Sequence of operations: backup ................................................................ 92
Sequence of operation: restore .................................................................. 96
Database objects that are supported by advanced backup methods ... 97
Configuring snapshot backups ..........................................................................97

Configuration requirements ......................................................................98
Configuring an SAP policy with Snapshot Client backup methods .....99
Restoring data from a snapshot backup .........................................................105
Restoring individual files ..........................................................................105
Restoring volumes and file systems using snapshot rollback ............105
Configuring block-level incremental backups ...............................................107
How does BLI work? ...................................................................................108
Storage Checkpoint ....................................................................................109
Configuration requirements ....................................................................111
Configuring policies for BLI backups ......................................................111
Additional snapshot client configuration information ...............................113
Backup types ...............................................................................................113
Backup scripts ............................................................................................114
Additional configuration that is required for brbackup using RMAN
proxy ....................................................................................................114
Intermixing RMAN stream and RMAN proxy backups ........................115
Performing user-directed backups ..........................................................115
Additional configuration required for Network Attached Storage (NAS) 116
BACKINT backups with NAS ....................................................................116
RMAN proxy backups with NAS ..............................................................117
Chapter 6
NetBackup for SAP on MaxDB databases

Configuration .....................................................................................................119
Creating a backup medium ...............................................................................120
Using NetBackup for SAP on a MaxDB database to perform backups and
restores ........................................................................................................121
Performing a backup .................................................................................121
Performing a query ....................................................................................122
Performing a restore .................................................................................122
Performing backups and restores using parallel medium groups .....122
Chapter 7
Troubleshooting
Setting the debug level ......................................................................................125
NetBackup reports .............................................................................................125
Enabling logging ........................................................................................126
Accessing the log files ...............................................................................126
NetBackup server reports .........................................................................127
sapdba logs and messages (Oracle-based SAP environments only) ...........127
Backup and restore log files .....................................................................128
Archive log files ..........................................................................................128
Minimizing timeout failures on large database restores .............................129
Appendix A Appendix B Appendix C
backint command line backint -i in_file contents backint -o out_file contents
131
135
137
Information returned for a backup ................................................................. 137

Information returned for a restore ................................................................. 137
Information returned for an inquiry .............................................................. 138
Appendix D Appendix E Appendix F
Environment variables bp.conf file Parameters used in initSID.utl
139
141
Parameter summary .......................................................................................... 143

Parameters .......................................................................................................... 145
backint_dir work_directory ......................................................... 145
backup_stream_buffersize size ................................................... 146
bplist_filter script_path ........................................................... 146
client client_machine_name ......................................................... 147
custom_sort_file file_path ......................................................... 147
drives number_of_drives ................................................................ 149
inquiry_query_period months ........................................................ 149
master_time_offset minutes ......................................................... 150
media_notify_script script_path ............................................. 150
policy policy_name ............................................................................ 150
policy2 policy_name ......................................................................... 151
restore_filter script_path ......................................................... 151
restore_stream_buffersize size ................................................. 152
retry_backup number_of_retries ............................................... 152
schedule schedule_name .................................................................. 152
schedule2 schedule_name ................................................................ 152
server server_name ............................................................................ 153
sleep seconds ....................................................................................... 153
sort_backup_type value .................................................................. 153
sort_restore_type value ................................................................ 157
switch_list control_file_path ................................................. 159
switch_log control_file_path .................................................... 159
switch_sem control_file_path .................................................... 160
Appendix G
Using NetBackup for SAP to back up SAPDB

Creating backup environment configuration files ....................................... 162
backint for SAPDB configuration file ..................................................162

Adapter program configuration file ........................................................163
NetBackup for SAP configuration file, initSID.utl ................................165
Defining a backup medium in SAPDB .............................................................165
Performing a backup .........................................................................................165
Performing a restore .........................................................................................166
Appendix H
Configuring split mirror backups

Local-host snapshot method: nbu_snap (Solaris SPARC platform only) ..167
Requirements .............................................................................................167
Configuration ..............................................................................................168
Local-host snapshot method: VxVM (Solaris SPARC, HP-UX, Windows
2000/2003) ..................................................................................................169
Requirements .............................................................................................169
Configuration ..............................................................................................169
Local-host snapshot method: VxFS_Checkpoint ..........................................170
Offhost alternate client: flashsnap method ...................................................170
Requirements .............................................................................................170
Configuration ..............................................................................................171
Offhost alternate client: VVR method (Solaris SPARC, HP-UX) .................172
Requirements .............................................................................................172
Configuration ..............................................................................................173
Hardware array-based snapshot method: Hitachi Shadow Image, EMC
TimeFinder, HP Business Copy ................................................................175
Appendix I Index
Differences in NetBackup for SAP in release 6.x
177
179
10
Chapter
Introduction
This chapter contains the following topics:

NetBackup for SAP features on page 12 NetBackup for SAP overview on page 13
NetBackup for SAP integrates the database backup and recovery capabilities of SAP with the backup and recovery management capabilities of NetBackup. NetBackup for SAP supports SAP environments based on the following databases:

Oracle databases. In an Oracle environment, you can use the Oracle database either with or without the recovery manager (RMAN). SAP DB and MaxDBTM databases. This documentation describes using NetBackup for SAP with both SAP DB and MaxDB databases. For readability, the remainder of this manual uses only the term MaxDB to describe these database platforms. The SAP DB name refers to the 7.4 and earlier releases. The MaxDB name refers to the 7.5 and later releases.
This chapter explains the differences and similarities between using NetBackup for SAP in each environment. For example, one major difference is that the SAP tools are supported only for Oracle databases. Note: This manual differentiates between SAP on an Oracle database and SAP on a MaxDB database only when necessary to explain differences between using NetBackup for SAP with these specific databases. For most tasks, NetBackup for SAP operates the same way in each environment.
12 Introduction NetBackup for SAP features
NetBackup for SAP features

Table 1-1 shows NetBackup for SAPs main features and introduces some terms used in the NetBackup for SAP documentation.
Table 1-1 Feature

Media and device management
NetBackup for SAP features and descriptions Description

All devices supported by Media Manager are available to NetBackup for SAP.
Scheduling facilities NetBackup scheduling facilities on the master server can be used to schedule automatic and unattended SAP backups. This also lets you choose the times when these operations can occur. For example, to prevent interference with normal daytime operations, you can schedule your database backups to occur only at night. Multiplexed backups NetBackup for SAP lets you take advantage of NetBackups and restores multiplexing capabilities. Multiplexing directs multiple data streams to one backup device, thereby reducing the time necessary to complete the operation. Transparent SAP and regular file system backup and restore operations All backups and restores run simultaneously and transparently without any action from the NetBackup administrator. The database administrator can run database backup and restore operations through NetBackup. Alternatively, if you are using NetBackup for SAP on an Oracle database, you can use SAP tools as if NetBackup were not present. An administrator or any other authorized user can use NetBackup to run database backups and restores. Sharing the same storage units used for other file backups Centralized and networked backup operations It is possible to share the same devices and media used for other backups or to give SAP exclusive use of certain devices and media. NetBackup for SAP can use Media Manager, disk, and PureDisk storage units. From the NetBackup master server, you can schedule database backups or start them manually for any client. The SAP databases can also reside on hosts that are different from the devices on which NetBackup stores the backups.
Introduction NetBackup for SAP overview
13
Table 1-1 Feature

Graphical user interfaces
NetBackup for SAP features and descriptions (continued) Description

NetBackup provides the following graphical user interfaces for client users and administrators:

NetBackup administration console for Java NetBackup administration console for Windows
A database administrator or NetBackup administrator can start backup or restore operations for SAP from the NetBackup graphical user interface on the master server. Parallel backup and restore operations NetBackup for SAP supports the parallel backup and restore capabilities of the SAP tools. For example, this permits the user to run more than one tape device at a time for a single SAP backup or restore, thereby reducing the time necessary to complete the operation. Compression increases backup performance over the network and reduces the size of the backup image that NetBackup writes to the storage unit. NetBackup for SAP supports compression for the following types of backups:

Compression
Stream-based backups through both MaxDB and RMAN. File-based backups through backint. Snapshot Client backups through backint.
NetBackup for SAP does not support compression for snapshot client backups through RMAN.
For more information on general NetBackup terminology, see the NetBackup Administrators Guide, Volume I.
NetBackup for SAP overview

The following sections provide a technical overview and explain the sequence of operation for NetBackup for SAP.
Technical overview
Figure 1-1 shows the major components in a NetBackup for SAP configuration. The server that is hosting the Oracle or the MaxDB database must be a NetBackup client. It must also have NetBackup for SAP installed.
14 Introduction NetBackup for SAP overview
Figure 1-1
NetBackup for SAP environment on an Oracle or MaxDB database
System hosting the Oracle or MaxDB database NetBackup for SAP supplies: Oracle or MaxDB database backint Interface Sample script files
Additional required NetBackup software: NetBackup client
Network (TCP/IP)
NetBackup master server or remote media server NetBackup software: NetBackup master server NetBackup media server (if system is a media server)
Storage unit
NetBackup for SAP assumes either an Oracle or a MaxDB database as the underlying database. The following additional components are present depending on the underlying database:

In an Oracle environment, the SAP tools perform database-related tasks. The brbackup, brarchive, and brrestore utilities communicate with NetBackup through the NetBackup for SAP backint interface. The sapdba component of SAP tools accesses the backup catalog used by NetBackup in order to determine the status of the valid backups. In a MaxDB environment, you initiate backups and restores through the MaxDB administrative interface. This interface can be the database manager graphical user interface (DBM GUI), the database manager command line interface (DBM CLI), and the Web database manager (Web DBM).
15
Sequence of operation
NetBackup users or schedules start database backups or restores by selecting an SAP script. A NetBackup process called bphdb starts the SAP script on the client if the backup is initiated by a policy on the master server. The SAP application then starts the requested operation on the databases. Figure 1-2 shows the sequence of operation. Figure 1-2 NetBackup for SAP operations
Database files
SAP tools or MaxDB administrative interface (DBM CLI)
NetBackup for SAP backint
NetBackup XBSA API
Script
Command line
bphdb NetBackup client
NetBackup master server Scheduler NetBackup
For a backup, brbackup calls the NetBackup for SAP backint interface. The
backint interface calls the XBSA API to interface with NetBackup.
A restore works similarly except that the NetBackup for SAP backint interface
calls the XBSA API, causing NetBackup to retrieve the data from secondary
storage and send it to the client.
NetBackup for SAP on Oracle databases

The following sections provide an overview of the software in a NetBackup for SAP on Oracle database environment. You can use NetBackup for SAP on Oracle databases either with or without the recovery manager (RMAN). The following subsections explain the components in Oracle environments with and without RMAN.
Using NetBackup for SAP on Oracle databases without RMAN

Figure 1-3 shows the components found in a NetBackup for SAP on Oracle database environment. Figure 1-3 Software components in a NetBackup for SAP on Oracle database environment
SAP environment Oracle database
NetBackup for SAP brbackup sapdba brrestore brarchive brconnect SAP tools backint Interface
NetBackup
XBSA API
Using NetBackup for SAP on Oracle databases with RMAN

NetBackup for SAP implements the Oracle defined SBT interface, which integrates the SAP tools with RMAN. You do not need to use RMAN to use NetBackup for SAP on Oracle databases, but the benefits of using RMAN backups are as follows:

RMAN supports incremental backups, which are backups of only those blocks that have changed since the previous backup. This reduces the number of blocks that are backed up. Unused and unchanged database blocks are not backed up. RMAN detects logical errors in database blocks during backup processing. The BEGIN BACKUP and END BACKUP commands are not needed for online backups because RMAN performs a block-by-block check to verify data consistency. This reduces the amount of redo log information. You can use RMANs verify command to verify backups.
17
Figure 1-4 shows a NetBackup for SAP on Oracle database environment that includes RMAN. Figure 1-4 Software components in a NetBackup for SAP on Oracle database environment with RMAN
SAP tools
Oracle database
Phase 2
Phase 1
RMAN
Oracle server libobk (liborasap) (NetBackup for Oracle)
Control files Profiles Log files
backint
NetBackup for SAP
NetBackup
Storage unit
Local disk
If you are in a NetBackup for SAP on Oracle database environment with RMAN, the backup consists of two phases:

Phase 1 backs up the Oracle database files. Phase 2 backs up the SAP control, log, and configuration files.
SAP tools overview

The SAP environment consists of many modules and applications. One component is the SAP tools. You can use the SAP tools whether or not you also use RMAN. Table 1-2 shows the software included in the SAP tools. Table 1-2 Component
sapdba
SAP tools software Function

sapdba is a menu-driven utility, with menus designed to reflect the users point of view. sapdba provides easy access to brbackup, brarchive, and brrestore for database backups and restores. The tool can restore a backup of an entire database or reset the database to a previous state.
brbackup
This command brings database servers online or offline, checks the status of SAP files, and places database tablespaces into BACKUP mode to guarantee their data consistency. The brbackup command provides online and offline backups. It also keeps a profile and log of each backup. brbackup uses the NetBackup software, through NetBackup for SAP, for the following actions:

SAP data file backups Data file and online log backups Error handling
brarchive
This command archives Oracle offline redo log files by communicating with the NetBackup for SAP backint interface. These files are copied by Oracle in its archiving directory. The brarchive command ensures that duplicates of these logs are available and that original files are not deleted prematurely. This command also keeps a profile and log of each archive. This command recovers database data files, control files, and online redo log files through the NetBackup for SAP backint interface. The brrestore command ensures that sufficient space is available prior to restoring these files, and it removes files that are overwritten during the recovery. This command also provides a query mode. This is a small script that contains SAP commands such as brbackup and brrestore.
brrestore
SAP script
19

Figure 1-5 shows the components found in a NetBackup for SAP on MaxDB database environment. Figure 1-5 Software components for a NetBackup for SAP on MaxDB database environment
DBM CLI
DBM GUI
Web DBM
MaxDB server
MaxDB Instance
Named pipes
NetBackup for SAP (backint)
NetBackup
Chapter
Installing the agent

This chapter includes the following topics:

Verifying the installation prerequisites on page 21 Installing NetBackup for SAP on page 23 Linking NetBackup for SAP with backint (Oracle databases without RMAN only) on page 34 Linking the Oracle database with the SBT library (Oracle databases with RMAN only) on page 35
Perform the procedures in this chapter before you configure NetBackup for SAP.
Verifying the installation prerequisites

Perform the procedures in this section before you install the database agent. These requirements apply for remote and local installations.
Operating system and platform compatibility

Verify that NetBackup for SAP is supported on your operating system or platform. To verify compatibility 1 2 3 4 Go to the technical support Web page: http://entsupport.symantec.com. From the Product Lookup list, choose NetBackup Enterprise Server and click on the > button. From the list on the right, click on Compatibility List. In the list of documents, click Veritas NetBackup Enterprise Server (tm) x.x/ NetBackup Server x.x Database Agent Compatibility (Updated date).
For x.x, look for the current release. For date, look for the most recent date.
22 Installing the agent Verifying the installation prerequisites
For information on supported cluster environments for NetBackup for SAP, see NetBackup (tm) x.x Cluster Compatibility (updated date). 5 6 Click the link for the PDF document, which is a downloadable file that enables you to view the supported database spreadsheet for this release. Read the document and verify that the software in your environment is compatible with the NetBackup and the database agent.
NetBackup software
Verify that the following requirements are met for the NetBackup server and client software:
The NetBackup server software is installed and operational on the

NetBackup server. The NetBackup server platform can be any that NetBackup supports. For installation information, see the NetBackup Installation Guide.
The NetBackup client software is installed on the client that has the
databases you want to back up.
The version of the NetBackup client and the version of the database agent
you want to install must be the same (for example, 6.5).
There must be adequate disk space on each machine upon which you want to
install the database agent. Less than two megabytes of additional disk space is required in the /usr/openv/netbackup directory. However, more disk space might be needed at run time.
Make sure that you configure any backup media that the storage unit uses.
The amount of backup media that is required depends on the devices that are used, the sizes of the databases that you want to back up, the amount of data that you want to archive, the size of your backups, and the frequency of backups or archives. For information on using Media Manager, see the NetBackup Administrators Guide, Volume I.
Database software
Verify the following regarding the database software on the NetBackup client:
SAP vendor software must be installed and operational. One or more SAP instances must exist.
Installing the agent Installing NetBackup for SAP
23
Cluster software
Verify the following requirements if you are installing the database agent software on a NetBackup server configured in a NetBackup cluster:
The SAP vendor software is installed and operational on each node to which
NetBackup can failover.
The NetBackup server software is installed and configured to work in a

NetBackup cluster. Follow the instructions in the NetBackup Installation Guide, including running the cluster_config script after the NetBackup server software has been installed. You only need to run the cluster_config script after you install the NetBackup server software. You do not need to run cluster_config after installing the database agent on a NetBackup server that is part of a NetBackup cluster. The following additional information also pertains to cluster environments:
Make sure you install the NetBackup client software and the database agent
software on each node to which NetBackup can failover.
Run commands such as bpplclients and update_dbclients from the

active NetBackup master or media server. To perform a remote installation where you push the database agent software to clients located in a cluster, specify the individual node names in the client list, not the virtual names.
Installing NetBackup for SAP

You can install the database agent software in one of the following ways:

A remote installation. The user loads the software onto a master server or a media server and then pushes the database software out to the clients. You can perform an initial or upgrade remote installation in this manner. Remote installation of NetBackup for SAP on page 23 describes this procedure. A local installation. The user loads and installs the software onto the local machine only.
Local installation of NetBackup for SAP on page 31 describes this
procedure.
Remote installation of NetBackup for SAP

During a remote installation, you load the database agent files onto either a UNIX master server or media server. Then you push the software to the clients to install it.
24 Installing the agent Installing NetBackup for SAP
Loading the database agent files onto the server

Use the following procedure to load the files onto the server. To load the database agent files on a UNIX server 1 Review Verifying the installation prerequisites on page 21. If you want to install the database agent on a clustered NetBackup server, read Cluster software on page 23. (Conditional) Perform this step only if you want to install on a server that is part of a NetBackup cluster. a Freeze the active NetBackup node. When you install NetBackup for SAP, install the software on all the inactive nodes first, then install on the active node. For information on how to freeze the active node in your specific cluster environment, see the NetBackup High Availability Administrators Guide. Decide which of the inactive nodes to install the software on first. In the next step, you log in to the first machine and start the installation process. Because you need to perform the installation on all inactive nodes first, make sure that the first machine you select is an inactive node.
Log in as the root user on the master server or media server. If you are already logged in, but are not the root user, run the following command:
su - root
Verify that a registered and valid license key for NetBackup for SAP resides on the master server. You can obtain master server license information from either the master server or the media server. To view or add license keys, perform one of the following actions:

From the master server or media server, run the following command: /usr/openv/netbackup/bin/admincmd/get_license_key
When the system prompts you, type the host name of the NetBackup master server.
Open the NetBackup administration console and choose Help > License Keys. If the NetBackup master server is part of a NetBackup cluster, the license key must be registered on each node. Mount the CD-ROM. For more information on how to mount a CD-ROM, see the NetBackup Installation Guide.
25
Change the working directory to the CD-ROM directory. For example: cd /CD_mount_point
Run the install script to load and install the software. For example: ./install
a Select the NetBackup Database Agent Software option.
The following prompt appears:
Do you want to do a local installation? (y/n) [n]
b c d e
Type n. Select the NetBackup for SAP option. Type q to quit selecting options.
A prompt appears that asks if the list is correct.
Type y. The install script identifies the types of client software that is loaded during the installation of the NetBackup server. By default, any matching NetBackup for SAP software is automatically loaded. If there are more platforms available, the script displays a menu that gives you the opportunity to add more client types to the default list. After the list is complete, the installation script copies the database agent version files and the install_dbext script to directory /usr/openv/netbackup/dbext. (These files are tar(1) files compressed with gzip(1).)
(Conditional) Select another node upon which to install the software. Perform this step under the following circumstances:

If you want to install the NetBackup for SAP software on a server that is part of a NetBackup cluster. and
If you have any nodes that still need the software installed.
If there are any inactive nodes that do not yet have the software installed,
select one of these inactive nodes. Then repeat step 3 through step 8 for
that node.
If you installed the software on all the inactive nodes, select the active node
and repeat step 3 through step 8 for that node.
If you installed on all the nodes, proceed to step 9.
(Conditional) Unfreeze the active node. Perform this step if you want to install the NetBackup for SAP software on a server that is part of a NetBackup cluster. The last step in the installation
process is to unfreeze the active node. Unfreeze the active node only after
all the software is installed on all nodes.
For information on how to unfreeze the active node in your specific cluster
environment, see the NetBackup High Availability Administrators Guide.
10 Decide how you want to distribute the NetBackup for SAP software to the clients. Use one of the following methods whether you want to upgrade clients in an existing environment or you want to perform a new installation:

Distribute to all clients currently specified in the database policy. This method distributes the NetBackup for SAP software to all clients that are currently included in the database policy. You can use this method only if you want to push from a master server. For information on this method, see Pushing the software to all clients on page 26. Distribute to selected clients. This method distributes the NetBackup for SAP software to selected clients only. If you want to perform a new installation and you plan to add clients to a database policy after you install the software. You can install the software on such clients now and configure the policy later. This method also allows you to skip any clients that you do not want to upgrade to 6.5 at this time. You can use this method whether you want to push from a master server or from a media server. For information on this method, see Pushing the software to new or selected clients on page 29.
Note: Make sure that the NetBackup for SAP version is the same version as the NetBackup client software.
Pushing the software to all clients

Use the following procedure to install or upgrade the database agent software on all clients currently configured in a NetBackup database policy. You can use this procedure only from a master server. To push the software to all clients Note: If you want to push the database agent software from a server that is part of a NetBackup cluster, type all commands in this procedure from the active NetBackup node.
27
Note: If you want to push the database agent software from a server that is part of a NetBackup cluster to an inactive node in the cluster, you need to force the installation to the inactive node. 1 Run the update_dbclients command to launch the installation script. Type the following command: Examine the client list that the update_dbclients command returns. a Locate the client list. The update_dbclients command compiles a list of clients that it detects are included in the policy. It presents this list to you. If 9 or fewer clients are in the client list, update_dbclients displays all the client names. If 10 or more clients are on the client list, update_dbclients writes the first 9 to standard output. It writes the entire list to $TMPDIR/NB_DBCLIENT_LIST.identifier. identifier is a mix of date, time, and process identifier information. The TMPDIR environment variable is defined as /tmp. Check the client list. The host names of the clients must be the clients individual node names. They cannot be virtual names. The hostname(1) and the domainname(1) commands return the correct value for the individual node names. The format can be either hostname or hostname.domainname. If the client list contains virtual names, you cannot complete this procedure. Do one of the following:

/usr/openv/netbackup/bin/update_dbclientsSAP ALL ALL
To exit this procedure if there are two or more clients, press the Enter key. Then type n to stop the upgrade and exit from this installation dialog box. To install the software in this situation, use Pushing the software to new or selected clients on page 29.
To exit this procedure if there is only one client, type n. To install the software in this situation, use Pushing the software to new or selected clients on page 29. If the client list contains only individual node names, proceed to the following step.

Check the skipped client list, if any.
If update_dbclients detects that it cannot update a particular client, it does not include the name of that client in the client list. Such clients are skipped for one or more of the following reasons:

The client is a PC client. You cannot install or upgrade NetBackup for SAP on a PC client from a UNIX server. The database agent does not support the client's platform type. The database agent software for that client type was not loaded onto the server. (In the procedure To load the database agent files on a UNIX server on page 24.) The client does not belong to the database policy type. The skipped client list is in $TMPDIR/skipped_clients.PID, where PID is the process identifier. The TMPDIR environment variable is defined as /tmp. If no file is present, no clients were skipped.
(Conditional) Specify the number of simultaneous client updates. If you want to update more than one client, the installation software displays the number of updates that are required to distribute the software to the clients. If the software detects the need to update more than one client, it displays the following prompt:
Enter the number of simultaneous updates you wish to take place.
[1 - max] (default: dflt)
max The maximum number of simultaneous updates that is allowed. The value that is displayed ranges from 1 to 30. The number the program uses if you press Enter without specifying a number. The value that is displayed ranges from 1 to 15.
dflt
If you want the installation software to perform dflt simultaneous updates, press Enter. You can specify a different number of simultaneous updates. Indicate a number that is greater or equal to 1 and less than or equal to the max, then press Enter. For example, if three clients are to be updated, the max and dflt values are 3. If 50 clients are to be updated, the max value is 30, and the dflt value is 15. update_dbclients starts the number of updates that you specify. This number may be less than the total number of client updates to be performed. If so, new updates start as the previous updates finish until all of the updates have been completed. 4 Indicate whether or not you want to upgrade the clients at this time.
29
Based on your answer, the time it takes to update the clients appears, followed by this question:
Do you want to upgrade the clients now? (y/n) [y]
Type y or n for the prompt. If you type n, update_dbclients quits and leaves the list of clients it would have updated in a file. You can use this file later as the argument to the -ClientList parameter. By default, the installation software writes the client list to $TMPDIR/NB_DBCLIENT_LIST.identifier, where identifier is a mix of date, time, and process identifier information. The TMPDIR environment variable is defined as /tmp. If you type y, you continue the installation process. The following actions occur:

The update_dbclients command distributes the software to the client. If it is successful, update_dbclients invokes the install_dbext script on the client. The install_dbext script runs on each client. If it is successful, it writes a version file in directory /usr/openv/share that contains the version of NetBackup for SAP that was installed. The update_dbclients command displays a note on whether the update was successful for each client. When the update_dbclients command completes, it displays a file name that contains a complete log of what happened for each client. If the update failed for any client, examine the log file to determine the problem.
Pushing the software to new or selected clients

Use the following procedure if you want to install or upgrade the NetBackup for SAP software on selected clients. You can use this procedure from either a master server or from a media server. To push the software to new or selected clients Note: If you want to push the NetBackup for SAP software from a server that is part of a NetBackup cluster, type all commands in this procedure from the active NetBackup node.
Note: If you want to push the database agent software from a server that is part of a NetBackup cluster to an inactive node in the cluster, you need to force the installation to the inactive node.
On the master server, type the following command to ensure that the bpdbm daemon is running: /usr/openv/netbackup/bin/bpps
If the output shows that the bpdbm daemon is not running, type the following command to start the daemon: /usr/openv/netbackup/bin/initbpdbm
Type the following command to change to the NetBackup bin directory: cd /usr/openv/netbackup/bin
Use the bpplclients(1M) command to create a file that contains a list of clients currently configured in the NetBackup database. The options for this command depend on whether you want to install from a master server or from a media server, as follows:

2 3
If you want to perform the install from the master server, type the following command:
./admincmd/bpplclients -allunique -noheader > file
If you want to perform the install from a media server, type the following command:
./admincmd/bpplclients -allunique -noheader -M ms_name > file

ms_name file Name of the NetBackup master server in this environment. Name of the file to contain the list of unique clients. If no clients have been configured in the NetBackup database, file is empty. Create file using the same format as that generated by bpplclients.
bpplclients writes output to file in the following format:

hardware op_system client
hardware The hardware name. For examples, type the ls(1) command in directory /usr/openv/netbackup/client. The operating system name. For examples, type the ls(1) command in directory /usr/openv/netbackup/client/hardware. The name of the client.
op_system
client
For example, file might contain a line like the following: Solaris Solaris8 curry
4 (Optional) Edit file. Perform this step to change the contents of file. Edit file to contain only those clients you want to update with NetBackup for SAP software.
31
The host names of the clients must be the clients individual node names. They cannot be virtual names. The hostname(1) and the domainname(1) commands return the correct value for the individual node names. The format can be either hostname or hostname.domainname. 5 Run the update_dbclients command to install the software. Specify the file you created in step 3 as the argument to update_dbclients. The command installs the software on the clients
that are listed in file.
For example:
./update_dbclients SAP -ClientList file
Answer questions as prompted by the update_dbclients command. The update_dbclients command initiates a dialog with you. It asks you to confirm actions during the update process and presents options to you if there are choices to be made. For more information, see step 2 of the procedure To push the software to all clients on page 26.
Note: You do not need to run the cluster_config script after you install the database agent on a server that is part of a NetBackup cluster.
Local installation of NetBackup for SAP

During a local installation, the database agent files are extracted and installed. The local machine can be a client or a server that also happens to be a NetBackup for SAP client. To install NetBackup for SAP on a local machine 1 Review Verifying the installation prerequisites on page 21. To install the database agent on a clustered NetBackup server, read Cluster software on page 23. (Conditional) Perform this step only if you want to install on a server that is part of a NetBackup cluster. a Freeze the active NetBackup node. When you install NetBackup for SAP, install the software on all the inactive nodes first, then install on the active node. For information on how to freeze the active node in your specific cluster environment, see the NetBackup High Availability Administrators Guide. Decide which of the inactive nodes to install the software on first.
In the next step, you log in to the first machine and start the installation process. Because you need to perform the installation on all inactive nodes first, make sure that the first machine you select is an inactive node. 3 Log in as the root user on the machine. If you are already logged in, but are not the root user, run the following command. su - root
(Conditional) Log into a media server or the master server. Perform this step if the local machine is a NetBackup client. Verify that a registered and valid license key for NetBackup for SAP resides on the master server.
You can obtain master server license information from either the master
server or the media server. To view or add license keys, perform one of the
following actions:
4 5
From the master server or media server, type the following command: /usr/openv/netbackup/bin/admincmd/get_license_key
When the system prompts you, type the host name of the NetBackup master server.
Open the NetBackup administration console and choose Help > License Keys. If the NetBackup master server is part of a NetBackup cluster, the license key must be registered on each node. (Conditional) Log out of the media server or master server and return to the local client. Perform this step if you logged into a media server or the master server in step 4 to verify the license. Mount the CD-ROM. For more information on how to mount a CD-ROM, see the NetBackup Installation Guide. Change the working directory to the CD-ROM directory. For example: cd /CD_mount_point
Run the install script to load and install the software.
Note: Make sure that the NetBackup for SAP version is the same version as the NetBackup client software.
33
Type the following command: ./install

a Select the NetBackup Database Agent Software option. The following prompt appears:
Do you want to do a local installation? (y/n) [n]
b c d e
Type y. A menu of all database agents available on the CD-ROM appears. Select the NetBackup for SAP option. Type q to quit if you do not want to select other options. A prompt appears that asks if the list is correct. Type y. The following actions occur:

The script writes the version file, a tar(1) file compressed with gzip(1), and the install_dbext script to directory /usr/openv/netbackup/dbext. The install script automatically runs the install_dbext script. If install_dbext completes successfully, it writes a version file in directory /usr/openv/share that contains the version of NetBackup for SAP that was installed.
Type q to quit from the script.
Note: You do not need to run the cluster_config script after you install NetBackup for SAP on a server that is part of a NetBackup cluster. 10 (Conditional) Select another node upon which to install the software. Perform this step under the following circumstances:

If you want to install the NetBackup for SAP software on a server that is part of a NetBackup cluster. and
If you have any nodes that still need the software installed.
If there are any inactive nodes that do not yet have the software installed,
select one of these inactive nodes. Then repeat step 3 through step 10 for
that node.
If you installed the software on all the inactive nodes, select the active node
and repeat step 3 through step 10 for that node.
If you installed on all the nodes, proceed to step 11.
11 (Conditional) Unfreeze the active node.
34 Installing the agent Linking NetBackup for SAP with backint (Oracle databases without RMAN only)
Perform this step to install the NetBackup for SAP software on a server that is part of a NetBackup cluster. The last step in the installation process is to unfreeze the active node. Unfreeze the active node only after all the software has been installed on all nodes. For information on how to unfreeze the active node in your specific cluster environment, see the NetBackup High Availability Administrators Guide.
Linking NetBackup for SAP with backint (Oracle databases without RMAN only)
Perform the linking described in this section only if you are using NetBackup for SAP with an Oracle database but without the Oracle recovery manager (RMAN). SAP requires that all SAP tools be located in a predetermined directory. The directory path is as follows:
/usr/sap/SID/SYS/exe/run
where SID is the unique name for an Oracle database instance. SID is also known as the System ID. The directory should contain the following commands:

brarchive brbackup brconnect brrestore brtools sapdba
To link the NetBackup for SAP binary file

Link backint from the NetBackup install directory to the SAP tools directory. For example, if the Oracle instance name is CER, enter the following command: ln -s /usr/openv/netbackup/bin/backint \
/usr/sap/CER/SYS/exe/run/backint
Installing the agent Linking the Oracle database with the SBT library (Oracle databases with RMAN only)
35
Linking the Oracle database with the SBT library (Oracle databases with RMAN only)
Perform the linking described in this section only if you are using NetBackup for SAP with an Oracle database and RMAN. The exact linking command to use depends on your operating system platform. To link the NetBackup for SAP binary file on AIX (32-bit or 64-bit) and 32-bit Oracle8 or Oracle8i software

Enter the following command to link the Oracle database and the SBT library to NetBackup: ln -s /usr/openv/netbackup/bin/libsapora.a \
$ORACLE_HOME/lib/libobk.a
To link the NetBackup for SAP binary file on AIX (64-bit) and 64-bit Oracle8i software

Enter the following command to link the Oracle database and the SBT library to NetBackup: ln -s /usr/openv/netbackup/bin/libsapora.a64 \
$ORACLE_HOME/lib64/libobk.a
To link the NetBackup for SAP binary file on AIX and 64-bit Oracle9i software

Enter the following command to link the Oracle database and the SBT library to NetBackup: ln -s /usr/openv/netbackup/bin/libsapora.a64 \
$ORACLE_HOME/lib/libobk.a
To link the NetBackup for SAP binary file on HP-UX (32-bit or 64-bit) and 32-bit Oracle8 or Oracle8i software

Enter the following command to link the Oracle database and the SBT library to NetBackup: ln -s /usr/openv/netbackup/bin/libsapora.sl \
$ORACLE_HOME/lib/libobk.sl
To link the NetBackup for SAP binary file on HP-UX (64-bit) and 64-bit Oracle8 or Oracle8i software

Enter the following command to link the Oracle database and the SBT library to NetBackup: ln -s /usr/openv/netbackup/bin/libsapora.sl \
$ORACLE_HOME/lib64/libobk.sl
36 Installing the agent Linking the Oracle database with the SBT library (Oracle databases with RMAN only)
To link the NetBackup for SAP binary file on HP-UX (32-bit or 64-bit) and 64-bit Oracle9i or later software

Enter the following command to link the Oracle database and the SBT library to NetBackup: ln -s /usr/openv/netbackup/bin/libsapora.sl64 \
$ORACLE_HOME/lib/libobk.sl
To link the NetBackup for SAP binary file on Linux and Oracle8 or Oracle8i software

Enter the following command to link the Oracle database and the SBT library to NetBackup: ln -s /usr/openv/netbackup/bin/libsapora.so
$ORACLE_HOME/lib/libobk.so
To link the NetBackup for SAP binary file on Linux and Oracle9i or later software

Enter the following command to link the Oracle database and the SBT library to NetBackup: ln -s /usr/openv/netbackup/bin/libsapora.so \
To link the NetBackup for SAP binary file on Solaris (32-bit or 64-bit) and 32-bit Oracle8 or Oracle8i software

Enter the following command to link the Oracle database and the SBT library to NetBackup: ln -s /usr/openv/netbackup/bin/libsapora.so.1
To link the NetBackup for SAP binary file on Solaris (32-bit or 64-bit) and 64-bit Oracle8 or Oracle8i software

Enter the following command to link the Oracle database and the SBT library to NetBackup: ln -s /usr/openv/netbackup/bin/libsapora.so64.1 \
$ORACLE_HOME/lib64/libobk.so
To link the NetBackup for SAP binary file on Solaris (32-bit or 64-bit) and 32-bit Oracle 9i or later software

Enter the following command to link the Oracle database and the SBT library to NetBackup: ln -s /usr/openv/netbackup/bin/libsapora.so.1 \
Installing the agent Linking the Oracle database with the SBT library (Oracle databases with RMAN only)
37
To link the NetBackup for SAP binary file on Solaris (32-bit or 64-bit) and 64-bit Oracle 9i or later software

Enter the following command to link the Oracle database and the SBT library to NetBackup: ln -s /usr/openv/netbackup/bin/libsapora.so64.1 \
To link the NetBackup for SAP binary file on Tru64

Enter the following command to link the Oracle database and the SBT library to NetBackup: ln -s /usr/openv/netbackup/bin/libsapora.so.1 \
$ORACLE_HOME/lib/libobk.so.1
38 Installing the agent Linking the Oracle database with the SBT library (Oracle databases with RMAN only)
Chapter
Configuration

User interface terminology notes on page 39 Configuring the Maximum jobs per client on page 40 Configuring a backup policy for a database on page 41 Creating scripts on page 50 Modifying the configuration files on page 54 Testing configuration settings on page 61 Testing multiple drives and files on page 62
Before attempting to configure NetBackup for SAP, complete the installation procedure as described in Installing the agent on page 21. After you complete the installation, follow the procedures in this chapter to configure your environment. Note: If you are using NetBackup for SAP on an Oracle database, all the information in this chapter applies to you. If you are using NetBackup for SAP on a MaxDB database, this section notes a few differences. Also refer to NetBackup for SAP on MaxDB databases on page 119.
User interface terminology notes

You can perform many of the configuration steps in this chapter from the NetBackup administration console on the master server. Depending on your master servers platform, the console is available in one or two forms. NetBackup supports a Java interface for both Windows and UNIX master servers. In addition, NetBackup supports a Windows interface for Windows master servers.
40 Configuration Configuring the Maximum jobs per client
The Java and Windows interfaces are nearly identical. If interface differences exist in the configuration procedures, this manual uses the following headings to identify the interface being described: From the Windows interface: From the Java interface:
Configuring the Maximum jobs per client

The following procedure shows how to set the Maximum jobs per client attribute. To configure the maximum jobs per client 1 2 3 4 5 In the left pane of the NetBackup administration console, expand Host Properties. Select Master Server. In the right pane, double-click the server icon. Click Global Attributes. Change the Maximum jobs per client value to 99. The Maximum jobs per client specifies the maximum number of concurrent backups that are allowed per client. The default is 1. You can use the following formula to calculate a smaller value: Maximum jobs per client = number_of_drives X number_of_policies
number_of_drives The number of concurrent brbackup jobs. The drives parameter in the initSID.utl file defines these jobs. The number of policies of any type that can back up this client at the same time. This number can be greater than one. For example, a client can be in two policies in order to back up two different databases. These backup windows can overlap.
number_of_policies
Tip: Enter a large enough value for the Maximum jobs per client attribute to meet the number of jobs that SAP runs. You might need to experiment with different values at your site.
Configuration Configuring a backup policy for a database
41
Configuring a backup policy for a database
A NetBackup backup policy for a database defines the backup criteria for a specific group of one or more clients. These criteria include:

Storage unit and media to use Policy attributes Backup schedules Clients to be backed up The script files to be executed on the clients
To back up a database environment, you need to define at least one SAP policy with the appropriate schedules. A configuration can have a single policy that includes all clients, or there can be many policies, some of which include only
one client.
Most requirements for database policies are the same as for file system backups.
In addition to the policy attributes for this database agent, other attributes are
available that you should consider.
For configuration instructions and information on all the attributes available,
see the NetBackup Administrators Guide, Volume I.
Adding a new policy

These instructions describe how to add a new backup policy for a database.
To configure a backup policy for databases
1 2 3 4 Log on to the master server as administrator (Windows) or root (UNIX).
Start the NetBackup Administration console.
If your site has more than one master server, choose the one on which you want to add the policy. From the Windows interface: In the left pane, right-click Policies and choose New Policy. From the Java interface: In the left pane, click Policies. In the All Policies pane, right-click the master server, and click New Policy. In the Add a New Policy dialog box, in the Policy name field, type a unique name for the new policy. Click OK.
5 6
42 Configuration Configuring a backup policy for a database
In the Add a New Policy or Change Policy dialog box, in the Policy type list, select the SAP policy type. The database agent policy type does not appear in the drop-down list unless your master server has a license key for the database agent. Complete the entries on the Attributes tab. For more information, see Description of attributes, which follows this procedure. Add other policy information.

To add schedules, see Adding schedules on page 43. To add clients, see Adding clients on page 47. To add scripts to the backup selections list, see Adding backup selections on page 48.
10 When you have added all the schedules, clients, and backup selections you need, click OK.
Description of attributes
With a few exceptions, NetBackup manages a database backup like a file system backup. Table 3-1 shows the policy attributes that are different for SAP backups. This information is used when you add a new policy. Other policy attributes vary according to your specific backup strategy and system configuration.
43
For more information on policy attributes, see the NetBackup Administrators Guide, Volume I. Table 3-1 Attribute
Policy type
Policy attribute descriptions Description

Determines the types of clients that can be in the policy. In some cases the policy type determines the types of backups that NetBackup can perform on those clients. To use the database agent, you must define at least one policy of type that is SAP. This option is available for SAP policies on UNIX. Select this attribute to back up files from NFS mounted file systems. If this option is not selected, NetBackup cannot perform a backup of NFS mounted files. Note: This option is not available for snapshot backups. For more details on this option, refer to Backing up files mounted with LOFS on page 50. Also see the NetBackup Administrator's Guide for UNIX.
Follow NFS
Keyword phrase
For NetBackup for SAP, the Keyword phrase entry is ignored.
Adding schedules
Each policy has its own set of schedules. These schedules initiate automatic backups and specify when a user can initiate operations. A database backup has two types of schedules: Application Backup and Automatic Backup.
Tips for configuring schedules

Set the window for the Application Backup schedule for 24 hours per day, seven days per week. This window ensures that your operations are never locked out due to the Application Backup schedule.
Configuring an Application Backup schedule

A database backup requires an Application Backup schedule. You cannot perform backups if this type of schedule is not included in the policy. The database agent automatically creates this schedule, named Default-Application-Backup, when you configure a new database policy.
To configure an Application Backup schedule 1 In the Policy dialog box, click the Schedules tab. To access the Policy dialog box, double-click the policy name in the Policies list in the NetBackup administration console. Double-click the schedule that is named Default-Application-Backup. Specify the other properties for the schedule. See Schedule properties. The backup window for an Application Backup schedule must encompass the time period during which all scheduled jobs and unscheduled jobs can occur. This window is necessary because the Application Backup schedule starts the processes that are required for all database backups, including those started automatically. For example, assume the following:

2 3
Users perform database backup operations during business hours, 08:00 to 13:00.
The Automatic backups that use this policy start between 18:00 and 22:00. In this scenario, the Application Backup schedule must have a start time of 0800 and a duration of 14 hours. Table 3-2 on page 44 shows this example schedule.

Table 3-2 Type of backup

Application Backup
Example settings for an Application Backup schedule Schedule settings

Retention
Description
Settings
The length of time the backup images 2 weeks are retained in the NetBackup catalog for restore. The time during which a NetBackup operation can be initiated. Sunday through Saturday 00:08:00 - 22:00:00
Backup Window
Note: Specify the Application Backup schedule name in the initSID.utl file on the client.
Configuring Automatic Backup schedules

You also need one or more automatic backup schedules if you plan to have NetBackup perform automatic backups, or if you use Snapshot Client features.
45
To configure an Automatic Backup schedule 1 2 3 4 5 On the Policy dialog box, click the Schedules tab. Click New. Specify a unique name for the schedule. Select the Type of backup. See Types of backup schedules. Specify the other properties for the schedule. See Schedule properties, which follows this procedure. Table 3-3 shows example settings for an automatic backup schedule.
Table 3-3 Type of backup

Automatic Backup
Example settings for an Automatic Backup schedule Schedule settings

Retention
Description
The length of time to store the record of a backup, which NetBackup uses to determine if the schedule needs to be run. Frequency determines how often a backup should be performed. The time during which a NetBackup operation can be initiated.
Settings
2 weeks
Frequency
every week
Backup Window
Sunday, 18:00:00 22:00:00
If this schedule is the last schedule, click OK. To add other schedules, repeat step 1 through step 6.
Types of backup schedules

Table 3-4 shows the backup schedules you can specify. Table 3-4 Backup type
Application Backup
SAP backup types Description

The Application Backup schedule enables user-controlled NetBackup operations from the client. These operations include those initiated from the client and those initiated by an automatic schedule on the master server. NetBackup uses the Application Backup schedule when the user starts a backup manually. Configure at least one Application Backup schedule for each database policy. The Default-Application-Backup schedule is configured automatically as an Application Backup schedule.
Table 3-4 Backup type
SAP backup types (continued) Description

An Automatic Full Backup schedule specifies the dates and times for NetBackup to automatically start backups. NetBackup runs the SAP scripts in the order that they appear in the file list. If there is more than one client in the SAP policy, the SAP scripts are run on each client. An Automatic Incremental Backup is a backup of only those blocks that have changed since the last Automatic Full (baseline) Backup. This kind of backup takes less time and space than a full backup because the Automatic Incremental Backup contains only the changed data. NetBackup for SAP supports this type of backup in MaxDB environments and in Oracle environments with RMAN.
Automatic Full Backup
Automatic Incremental Backup
Schedule properties
Some of the schedule properties have a different meaning for database backups than for a regular file system backup. Table 3-5 explains the schedule properties. Table 3-5 Property
Type of backup
Description of schedule properties Description

Specifies the type of backup that this schedule controls. The selection list shows only the backup types that apply to the policy you want to configure. For more information, see Types of backup schedules.
Frequency
This setting is used only for scheduled backups and not for user-directed backups. Frequency specifies the period of time that can elapse until the next backup or archive operation begins on this schedule. For example, assume that the frequency is seven days and a successful backup occurs on Wednesday. The next full backup does not occur until the following Wednesday. Typically, incremental backups have a shorter frequency than full backups. This setting is used only for scheduled backups. It is not used for user-directed backups. The Calendar option allows you to schedule backup operations that are based on specific dates, recurring week days, or recurring days of the month.
Calendar
47
Table 3-5 Property

Retention
Description of schedule properties (continued) Description

The retention period for an Application Backup schedule refers to the length of time that NetBackup keeps backup images. The retention period for an Automatic Backup schedule controls how long NetBackup keeps records of when scheduled backups have occurred. Frequency-based scheduling Set a retention period that is longer than the frequency setting for the schedule. For example, if the frequency setting is set to one week, set the retention period to be more than one week. The NetBackup scheduler compares the latest record of the Automatic Backup schedule to the frequency of that Automatic Backup schedule to determine whether a backup is due. This means that if you set the retention period to expire the record too early, the scheduled backup frequency is unpredictable. However, if you set the retention period to be longer than necessary, the NetBackup catalog accumulates unnecessary records. Calendar-based scheduling The retention period setting is not significant for calendar-based scheduling.
Multiple copies
If you want to specify multiple copies of a backup for the policy, configure Multiple copies on the Application Backup schedule.
Other schedule properties vary according to your specific backup strategy and system configuration. For more information on schedule properties, consult the NetBackup Administrators Guide, Volume I.
Adding clients
The client list is the list of clients on which your SAP scripts are run during an automatic backup. A NetBackup client must be in at least one policy but can be in more than one. For a database policy, clients you want to add must have the following software installed:

SAP NetBackup client or server NetBackup for SAP The backup or restore script(s)
To add clients to a policy 1 In the Policy dialog box, click the Clients tab. To access the Policy dialog box, double-click the policy name in the Policies list in the NetBackup administration console. Click New. Enter the name of the client you want to add. If SAP is installed in a NetBackup cluster, specify the virtual SAP name as the client name. From the Windows interface

2 3
Type the name of the client and press Enter. If NetBackup cannot detect the hardware and operating system, a dialog box displays so you can specify this information. OR
Click the Browse for Computer button to choose the client from the network. From the Java interface
a b 4 5
In the Client name field, type the name of the client you want to add. Choose the Hardware and operating system type and click Add.
To add another client, repeat step 2 and step 3. If this client is the last client, click OK.
Adding backup selections

The backup selections list in a database policy has a different meaning than for non-database policies. For example, in a Standard or Windows-NT policy, the list contains files and directories to be backed up. In a database policy, you specify scripts to be run.
Rules for scripts

Observe the following when using scripts:

Make sure the scripts reside on each client in the client list. Scripts can reside in any location. Make sure that NetBackup can access the location you choose and that NetBackup can run the scripts. NetBackup installs sample scripts when you install the software, and you can modify these scripts for your own use. Write the scripts to a location outside of the original installation location. This way future NetBackup installations do not overwrite your sites scripts.
49
If you use NetBackup for SAP in a NetBackup server cluster, make sure that the scripts reside in a location that is available after a failover.
Add scripts to the backup selections list only if you want to set up a policy for automatic backups. These scripts are run for manual backups and for Automatic Backup schedules as specified under the Schedules tab. NetBackup runs the scripts in the order that the scripts appear in the backup selections list. For more information on backup scripts, see Creating scripts on page 50.
Adding scripts to the backup selections list

The following procedures describe how to add scripts to the backup selections list using the Java interface and using the Windows interface. Caution: Be sure to specify the correct script names in the backup selections list to prevent an error or possibly a wrong operation. Make sure that the script resides on the client before you try to add it to the backup selections list. For more information on backup scripts, see Creating scripts on page 50. To add scripts to the backup selections list from the Java interface 1 Open the Policy dialog box. To access the Policy dialog box, double-click the policy name in the Policies list in the NetBackup administration console. Click the Backup Selections tab.
Click New.
Specify the names of the scripts that you want NetBackup to use.
a In the Script: box, type the full path name of a script on the client. For example: Click Add to add the script to the list. Repeat step a and step b to add any other scripts.
2 3 4
/usr/openv/netbackup/ext/db_ext/sap/scripts/sap_oracle/sap_offline_backup
b c 5
Click OK.
For more information on backup scripts, see Creating scripts on page 50. To add scripts to the backup selections list from the Windows interface 1 In the Policy dialog box, click the Backup Selections tab. To access the Policy dialog box, double-click the policy name in the Policies list in the NetBackup administration console.
50 Configuration Creating scripts
2 3
Click New. Specify the names of the scripts you want NetBackup to use. Use one of the following methods:

Type the full path name of the script on the client. For example: Click the Remote Folder button. Navigate to and select the script file. Click OK.
/usr/openv/netbackup/ext/db_ext/sap/scripts/sap_oracle/sap_offline_backup
Click OK.
Backing up files mounted with LOFS

The NetBackup for SAP Agent supports backups of files from a loopback virtual file system (LOFS). An LOFS file system allows you to create a virtual file system that provides access to existing files through the use of alternate pathnames. Consider a loopback mount of the /oracle file system onto the /database file system. This loopback mount allows the /oracle file system to also appear under the /database file system. All files in /oracle are then accessible either from a pathname relative to /oracle or relative to /database. For example, /database/sapdata1/system/system.dbf. If you have a local file system mounted as an LOFS, you do not need to select Follow NFS. Select the Follow NFS option for backups of an LOFS if the actual file system (for example, /oracle) is either of the following

an NFS mount a global zone file system and mounted with LOFS in a Solaris Zone
Creating scripts
If you configured a policy for automatic scheduling in Adding backup selections on page 48, you also need to specify backup scripts to be run automatically. You can either create your own scripts or you can modify one or more of the scripts included in the following locations: /usr/openv/netbackup/ext/db_ext/sap/scripts/sap_oracle
/usr/openv/netbackup/ext/db_ext/sap/scripts/sap_maxdb
Configuration Creating scripts
51
NetBackup for SAP scripts on page 51 shows the scripts in the sap_oracle and sap_maxdb directories. Table 3-6 NetBackup for SAP scripts Used by (underlying database)
Oracle without RMAN
Script name
sap_offline_backup
Comments
Issues a brbackup command and performs a full offline database backup. Use the export command to make $SAP_SERVER and $SAP_POLICY, which are created by bphdb in root, available to the NetBackup for SAP backint interface process. Issues the brbackup and brarchive commands and performs a full online database backup. Issues the brarchive command and backs up the offline redo log files. Issues the brbackup command with the RMAN option. Issues a dbmcli command and uses the specified backup medium.
sap_online_backup
Oracle without RMAN
sap_redo_log_backup
Oracle without RMAN
sap_rman_backup
Oracle with RMAN
sap_maxdb_backup
MaxDB
If you decide to use these scripts, customize them for your environment. Caution: Always specify the correct script when configuring automatic backups or when starting operations through NetBackup. NetBackup for SAP does not generate an error if a restore script is used for a backup operation or a backup script is used for a restore operation.
Modifying the backup scripts

To modify the backup scripts 1 Copy the example script(s) from /usr/openv/netbackup/ext/db_ext/sap/scripts/sap_oracle or /usr/openv/netbackup/ext/db_ext/sap/scripts/sap_maxdb to a different location on your client. The SAP scripts can reside anywhere on the client. Do not store your scripts in the sample directory because your modifications are lost if you upgrade
52 Configuration Creating scripts
or reinstall. Always relocate your scripts to a safe location. In a NetBackup server cluster, this location must be available after a failover. 2 Enable proper permissions on the script files so NetBackup can run the scripts. Set the access permissions of these scripts to 775. chmod 775 script_name Open the script file with a text editor. For example, you can use the following command if you are modifying the sap_offline_backup script: vi sap_offline_backup Modify the script according to the instructions in the file. In particular, remember to edit lines that starts with su. If you do not include su - user (where user is the SAP administrator account) in your script, the script does not run with the proper account and environment variables. This situation can lead to problems with database backups and restores. For example, the sap_offline_backup script contains the following lines:
#!/bin/sh # #NOTE:IF your SAP user (in this script orasap) runs in C shell, environmental
#variables can not be exported. In that case, you should modify this script to
#work in your environment. For example:
# SAP_SERVER=$SAP_SERVER; export SAP_SERVER; (Correct for Bourne and Korn shells)
# can change into
# setenv SAP_SERVER $SAP_SERVER; (Correct for C shell)
#
#
#This environment variable are created by Netbackup (bphdb)
#
echo echo echo echo "SAP_SCHEDULED = $SAP_SCHEDULED"
"SAP_USER_INITIATED = $SAP_USER_INITIATED"
"SAP_SERVER = $SAP_SERVER"
"SAP_POLICY = $SAP_POLICY"
RETURN_STATUS=0
SAP_ENV=""
#
# If SAP_SERVER exists then export it to make it available to backint
#
if [ -n "$SAP_SERVER" ]
then
SAP_ENV="$SAP_ENV SAP_SERVER=$SAP_SERVER; export SAP_SERVER;"
Configuration Creating scripts
53
#if Oracle DBA account( orasap user) uses C Shell, comment the above line and
#uncomment next line
# SAP_ENV="$SAP_ENV setenv SAP_SERVER $SAP_SERVER;"
fi
#
# If SAP_POLICY exists then export it to make it available to backint
#
if [ -n "$SAP_POLICY" ]
then
SAP_ENV="$SAP_ENV SAP_POLICY=$SAP_POLICY;export SAP_POLICY;"
#if Oracle DBA account( orasap user) uses C Shell, comment the above line and
#uncomment next line
# SAP_ENV="$SAP_ENV setenv SAP_POLICY $SAP_POLICY;"
fi
#
# Full offline backup
#
CMD_LINE="$SAP_ENV brbackup -c -d util_file -t offline -m all"
#
# The username on the "su" command needs to be replaced with the correct
# user name.
#
echo "Execute $CMD_LINE"
su - orasap -c "$CMD_LINE"
RETURN_STATUS=$?
exit $RETURN_STATUS
Test the scripts you just created. For information on testing, see Testing configuration settings on page 61.
Script parameters
The SAP scripts that enable the SAP utilities to perform backups and restores use parameters defined in the following sources:

Environment variables Configuration files. For example, initSID.utl, where SID is the instance. See Modifying the configuration files on page 54. NetBackup configuration file (bp.conf)
You can use the different parameter sources to create SAP scripts to perform
different database backup and restore tasks. For example, you can define
$SAP_POLICY in an SAP script to perform different types of backups.
54 Configuration Modifying the configuration files
When NetBackups automatic scheduler runs an SAP script, it creates the following environment variables locally. Environment variable
$SAP_POLICY $SAP_SCHEDULED
Purpose
Names the NetBackup for SAP policy. Set to 1 if this is an automatic backup (scheduled SAP). Names the NetBackup server. Set to 1 if this is a user-initiated backup. That is, if the SAP backup is started from the master server.
$SAP_SERVER $SAP_USER_INITIATED
When an SAP script starts from the Java interface, it creates all of the preceding variables except for the $SAP_POLICY variable.
Modifying the configuration files

The following sections show how to modify the NetBackup for SAP configuration files. The NetBackup for SAP software distribution includes several example configuration files.
Files to configure
Table 3-7 on page 54 shows the files you need to modify depending upon whether your underlying database is an Oracle database or a MaxDB database. Table 3-7 File
initSID.utl
Database configuration files Underlying database

Oracle and MaxDB
Comments
SAP parameter file. This file specifies policy, schedule, client, and other information to the backint interface. SAP profile file. This file contains information that the SAP tools use to interact with the backint interface. MaxDB configuration file. This file contains information that the SAP tools use to interact with the backint interface.
initSID.sap
Oracle
bsi.env
MaxDB
Relationships between files

The SAP tools and NetBackup for SAP pass information in these configuration files to the backint interface. When backint runs, the following occurs:
Configuration Modifying the configuration files
55
In NetBackup for SAP on Oracle databases, you specify the actual initSID.utl file name as the argument to the util_par_file parameter in the initSID.sap file. In NetBackup for SAP on MaxDB databases, you specify the actual initSID.utl file name as the argument to the PARAMETERFILE parameter in the bsi.env file. The initSID.utl file name becomes the argument to the backint commands -p par_file parameter.
Modifying the initSID.utl file

The initSID.utl file is the SAP parameter file. Edit this file as part of configuring NetBackup for SAP. To modify the initSID.utl file 1 Check for an existing parameter file. If an initSID.utl file already exists in the $ORACLE_HOME/dbs directory, copy it to a backup file. Create a new parameter file. Copy the parameter file included in the NetBackup for SAP software distribution to the $ORACLE_HOME/dbs directory. For example, if the Oracle instance is SAP, copy the NetBackup example .utl file to initSAP.utl, as follows:
cp /usr/openv/netbackup/ext/db_ext/sap/scripts/sap_oracle/initSAP.utl \
$ORACLE_HOME/dbs/initSAP.utl
Modify initSID.utl file with a text editor to set the parameters to values that are appropriate to your site.
The following parameters are required: client, switch_list,
switch_log, switch_sem.
You can set the following additional parameters depending on whether or
not you use RMAN:
If you use RMAN, set policy, schedule, and server.
If you do not use RMAN, set drives, policy, schedule, and server. For example, assume that initSAP.utl is your parameter file, and the policy you are configuring is called sap_policy_1. You can use the following procedure to set the policy parameter:
a b
Use a text editor to open the initSAP.utl file. Find the following line: policy sap_backup
Copy and paste this line under the original. policy sap_backup policy sap_backup Comment out the original line. #policy sap_backup policy sap_backup Change sap_backup to sap_policy_1. #policy sap_backup policy sap_policy_1 Repeat the preceding steps for each parameter you want to change. When you are finished changing parameters, save and close the file.
The following shows an example initSID.utl file with all the parameters required for NetBackup for SAP on Oracle databases: policy sap_policy_1
schedule Default-Application-Backup
client puffin
server puffin
drives 2
switch_list /oracle/sap/sapbackup/.switch.lis
switch_sem /oracle/sap/sapbackup/.switch.sem
switch_log /oracle/sap/sapbackup/.switch.log
Note: The question mark (?) and ampersand (&) Oracle substitution characters and the $ORACLE_HOME environment variable are not allowed in the initSID.utl file. This is because they are not allowed in the par_file that the backint -p parfile option identifies.
Modifying the initSID.sap file

(NetBackup for SAP on Oracle databases only)
The initSID.sap file is the SAP profile file. This file signals to the SAP tools that you are using the backint interface and conveys information about NetBackup for SAP to the SAP tools. Edit this file as part of configuring NetBackup for SAP when the underlying database is Oracle.
57
To modify the initSID.sap file 1 Check for an existing profile file. If an initSID.sap file already exists in the $ORACLE_HOME/dbs directory, copy it to a backup file. Create a new profile file. Copy the profile file included in the NetBackup for SAP software distribution to the $ORACLE_HOME/dbs directory. For example, if the Oracle instance is SAP, copy the NetBackup example .sap file to initSAP.sap, as follows:
cp /usr/openv/netbackup/ext/db_ext/sap/scripts/sap_oracle/initSAP.sap \
$ORACLE_HOME/dbs/initSAP.sap
Modify the initSID.sap file with a text editor to set the backup_dev_type and util_par_file parameters to values that are appropriate to your site. For example, assume that initSAP.sap is your profile file, and initSAP.utl is your parameter file. You can use the following procedure to set parameters: a b c Use a text editor to open the initSAP.sap file. Find the following line: backup_dev_type = tape
Copy and paste this line under the original. backup_dev_type = tape
backup_dev_type = tape
Comment out the original line. #backup_dev_type = tape
backup_dev_type = tape
Change tape to util_file. #backup_dev_type = tape backup_dev_type = util_file Find the following line: util_par_file = file_path
Copy and paste this line under the original. util_par_file = file_path
util_par_file = file_path
Comment out the original line. #util_par_file = file_path
util_par_file = file_path
Change file_path to the path to the initSID.utl parameter file.
f g
#util_par_file = file_path
util_par_file = ?/dbs/init@.utl
This example file uses environment variable settings and Oracle substitution characters. When the SAP tools interpret the initSID.sap profile file, they replace the question mark (?) and at sign (@) characters with the values assigned to the $ORACLE_HOME and $ORACLE_SID environment variables, respectively. 4 (Conditional) Specify the rman_parms parameter and set the NB_ORA_SAP environment variable to the value SAP. Perform this step only if you are using NetBackup for SAP on an Oracle database with RMAN. For example: rman_parms = ENV=(NB_ORA_SAP=file)
where file specifies the full path to the initSID.utl file. Do not use
substitution in the file specification.
For example, this parameter might look like the following:
rman_parms = ENV=(NB_ORA_SAP=$ORACLE_HOME/dbs/initCER.utl)
Depending on your site practices, you might want to specify the following additional NetBackup environment variables and their values as arguments to the rman_parms parameter: NB_ORA_POLICY, NB_ORA_SCHEDULE, NB_ORA_CLIENT, and NB_ORA_SERV. You can also specify values for these environment variables in the initSID.utl file. If you specify differing values, the ones in initSID.sap override those in initSID.utl. For example, if you want to use one policy and schedule for the first part of a backup (data files) and a different policy and schedule for the second part of a backup (the control file backup), you can set the NB_ORA_POLICY and NB_ORA_SCHEDULE variables in initSID.sap to pertain to the first part of the backup. Then, you can set these variables to different values that pertain to the second part of the backup in initSID.utl because NetBackup for SAP checks only initSID.utl when backing up the control files; it does not check initSID.sap. You can include other RMAN parameters in this file. For more information on other parameters, see your SAP documentation. 5 Save and close the initSID.sap file.
59
Modifying the bsi.env file

(NetBackup for SAP on MaxDB databases)
The bsi.env file specifies the following:

The backint for MaxDB programs location, which is NetBackup for SAP on MaxDB. How to communicate with backint.
The database manager uses this information when it performs backups and restores. bsi.env is the default name for this configuration file, but if you want to change this name, you can specify a different name in the BSI_ENV environment variable in the MaxDB user environment. To create a MaxDB configuration file 1 Use a text editor to create the MaxDB configuration file, bsi.env. The following command creates bsi.env in a UNIX environment: vi bsi.env
Note: You can give the MaxDB configuration file a name other than bsi.env. If you do this, edit the BSI_ENV environment variable and include the full path to this file. 2 Use the parameters to specify backup characteristics. You must include the following parameters in bsi.env: BACKINT, INPUT, OUTPUT, ERROROUTPUT, and PARAMETERFILE. All other parameters are optional. The following is an example of a file with the minimum configuration specified:
BACKINT /usr/openv/netbackup/bin/backint
INPUT /export/home/sapdb/logs/backint.in
OUTPUT /export/home/sapdb/logs/backint.out
ERROROUTPUT /export/home/sapdb/logs/backint.err
PARAMETERFILE /export/home/sapdb/indep_data/wrk/initSAP.utl
The following list shows the parameters you can include in the bsi.env file. Parameter
BACKINT absolute_path/file_name
Description
Specifies the absolute path and file name of the backint for MaxDB program. The INPUT parameter specifies the absolute path and file name of the standard input file. The OUTPUT parameter specifies the absolute path and file name of the standard output file. The ERROROUTPUT file specifies the absolute path and file name of the standard error output file. The database manager creates these files temporarily and uses them for standard input, output, and error output for backint for MaxDB.
INPUT absolute_path/file_name OUTPUT absolute_path/file_name ERROROUTPUT absolute_path/file_name
PARAMETERFILE absolute_path/file_name
Specifies the absolute path and file name of the configuration file for the backint for MaxDB program, initSAP.utl. The number of seconds after which the backup tool exits and after the database kernel has copied all data successfully. Default is 300. This is the period of time after which the database manager terminates the backup tool if all data has been copied to the pipes. Note that the backup tool always exits after this defined period, whether all data copied from the database kernel has been backed up by the backup tool or not.
TIMEOUT_SUCCESS seconds
Configuration Testing configuration settings
61
Parameter
TIMEOUT_FAILURE seconds
Description
This parameter is effective only if the database kernel has stopped the backup due to an error. In such a case, seconds specifies the number of seconds after which the backup tool exits. Default is 300. Allow enough time for the backup tool to save all data copied by the database kernel because the backup tool always exits when this timeout is reached, even if not all of the copied data has been saved yet. However, do not specify too much time, or you risk a situation in which a backup stopped by the database kernel blocks other backups, such as automatic nightly backups, from being started.
ORIGINAL_RUNDIRECTORY absolute_path
Specifies the absolute path of the run directory of the source database. The default value is the run directory of the current database instance. This value is case sensitive. Specify this parameter only for a migration. The prerequisite for the migration from one computer to another is that the version of backint for MaxDB that you are using can make backups from the source computer available on the target computer.
Testing configuration settings

After you configure the master server for NetBackup for SAP, test the configuration settings. Perform a manual backup (or backups) with the automatic backup schedules you created. For a description of status codes and other troubleshooting information, see the NetBackup Troubleshooting Guide.
62 Configuration Testing multiple drives and files
To test the configuration settings 1 2 3 Log onto the master server as administrator (Windows) or root (UNIX). Start the NetBackup administration console. In the left pane, click Policies. From the Windows interface: The policy list appears in the right pane. From the Java interface: The right pane splits into an All Policies pane and a details pane. Click the policy you want to test. Choose Actions > Manual Backup. The Schedules pane contains the name of an automatic schedule (or schedules) configured for the policy that you want to test. The Clients pane contains the name of the client(s) listed in the policy that you want to test. Follow the directions in the Manual Backup dialog box. Click Activity Monitor on the NetBackup administration console. The Activity Monitor and the script output indicates the status of the backup operation. If the manual backup does not exit with a successful status, see Troubleshooting on page 125.
4 5
6 7
Testing multiple drives and files

To test multiple drives, you must have the following in your environment:

More than one tablespace to back up Multiple storage units to write to at the same time
You can also use the multiplex value to simulate multiple tape and disk drives.
To test multiple drives 1 2 Complete the configuration of NetBackup, NetBackup for SAP, and SAP tools as described previously in this chapter. Change the number of tape and disk drives specified by the drives parameter in $ORACLE_HOME/dbs/initSAP.utl to equal the number of storage units. For example, the multiplex value multiplied by the number of tape drives = drives. For more information, see the drives parameter in Parameters used in initSID.utl on page 143.
drives 2
When you perform a backup, you should see two or more backups running, depending upon how many drives you have identified in the $ORACLE_HOME/dbs/initSAP.utl parameter file. The number of drives in the utility file should match the number of drives multiplied by the multiplex
Configuration Testing multiple drives and files
63
value. The NetBackup for SAP backint interface waits for all backups to complete before reporting success or failure to brbackup.
64 Configuration Testing multiple drives and files
Chapter
Using NetBackup for SAP


Performing a backup on page 65 Performing an archive on page 70 Performing a restore on page 72 Restarting failed backups and restores on page 76
When all installation and configuration is complete, you can start SAP backups and restores through NetBackup. Caution: Always specify the correct SAP script when you configure automatic backups or when you start operations through NetBackup. See Creating scripts on page 50. NetBackup for SAP does not generate an error if a restore script is used for a backup operation. Nor is an error generated if a backup script is used for a restore operation.
Performing a backup
This section shows two different methods for performing backups.
Method 1: Using Netbackup schedules to start an SAP backup

Automatic backup
The most convenient way to back up your database is to set up schedules for automatic backups. When the NetBackup scheduler invokes a schedule for an automatic backup, the SAP scripts run as follows:
In the same order as they appear in the file list
66 Using NetBackup for SAP Performing a backup
On all clients that have them (with path names that match)
The SAP scripts start the database backup. You can create and configure a policy that uses the SAP scripts to back up your database automatically, according to the schedules you specify. See Configuration on page 39. To add or change schedules, see Adding schedules on page 43.
Manual backup
The administrator can use the NetBackup server software to execute an automatic backup schedule manually for the SAP policy. See Testing configuration settings on page 61.
Method 2: Using BRTools to start an SAP backup (for Oracle database only)
Note: The information in this section applies to NetBackup for SAP on Oracle databases only. Different configuration is required for NetBackup for SAP on a MaxDB database. See the chapter NetBackup for SAP on MaxDB databases on page 119. You can start a backup in one of the following ways.

Through the SAPDBA utilitys menus Through the brbackup command line
When you use the SAPDBA utility or the brbackup command to start a backup, the following events occur: 1 brbackup status messages appear on the console. These messages report when the database server is started or stopped. They also report when the backup mode of the tables is changed. The brbackup command starts the NetBackup for SAP backint interface, and it submits files to be backed up. The NetBackup for SAP backint interface processes input files and calls the XBSA interface. During the file-online mode, each database file is backed up, one at a time. The NetBackup for SAP backint interface coordinates with brbackup using a semaphore file. After all files are backed up, the full file list is displayed. The file list is displayed in the format that the NetBackup for SAP backint interface specification requires as to success or failure. This format includes a backup ID (BID) to be used for later restores. The SAP tools also maintain a log of the
2 3
Using NetBackup for SAP Performing a backup
67
backup session. The standard NetBackup logs keep track of the images created. The NetBackup for SAP backint interface only needs to keep track of the BID date and time. This allows cross-referencing by brrestore.
SAPDBA offline backup

The following procedure shows how to perform an offline backup with SAPDBA. To perform an offline backup using SAPDBA 1 2 3 4 Verify that you have completely configured NetBackup, NetBackup for SAP, and the SAP Tools. See Configuration on page 39. Verify that you are user sapadm. Run the stopsap R3 command to stop SAP. Start sapdba. The following appears:
___________________________________________________________________ SAPDBA V6.20 - SAP Database Administration

___________________________________________________________________ ORACLE version: ORACLE_SID : ORACLE_HOME : DATABASE : SAPR3 : a b c d e f 9.2.0.1.0
CER
/home/orasap/Ora920
open
5, not connected
h i j k l m Backup database
Backup offline redo logs
Restore/recovery
Additional functions
Show/cleanup
User and security
Startup/shutdown instance Instance information Tablespace administration Reorganization Export/import Archive mode
q - Quit
Please select ==> h
Type h to select the Backup database menu item. The following appears:
__________________________________________________________________ Backup Database

__________________________________________________________________ Current value
Normal backup
initCER.sap
a - Backup function b - Parameter file
68 Using NetBackup for SAP Performing a backup
c d e g h i j k l
Backup device type Objects for backup Backup type Query only Special options ...
Standard backup Backup from disk backup
Restart backup
Make part. backups compl.
external backup tool (backint)

all
offline (force)
no
yes
S - Start BRBACKUP (V6.20)

q - Return
Please select ==> d
Type d to select Objects for backup. The following appears:
___________________________________________________________________ Backup Mode/Backup Objects

___________________________________________________________________ Current selection: all
a b c d e f g h all all_data full incr sap_dir ora_dir whole database backup
whole database backup without index tablespaces
full backup (level 0)
incremental backup (level 1)
SAP directories backup
ORACLE directories backup
a tablespace name
an ORACLE file id <number>
or a range of file ids <number>-<number>
- an absolute or directory name
- a combination: <item> or <item>,<item>,...
i j q - Return
Please select
==>g
Enter tablespace name

Enter objects for backup (<return> only for no change)=> PSAPUSER1D
Type g and type the name of the object to back up. For example: PSAPUSER1D. The following appears:
___________________________________________________________________ Backup Mode/Backup Objects

___________________________________________________________________
Using NetBackup for SAP Performing a backup
69
Current selection: PSAPUSER1D

a b c d e f g h all all_data full incr sap_dir ora_dir whole database backup
whole database backup without index tablespaces
full backup (level 0)
incremental backup (level 1)
SAP directories backup
ORACLE directories backup
a tablespace name
an ORACLE file id <number>
or a range of file ids <number>-<number>
- an absolute file or directory name
- a combination: <item> or <item>,<item>,...
i j q - Return
Please select
==>q
Type q to go back to the previous menu. The information that is returned indicates the following:

The backup device type is external backup tool (backint). The backup type is offline_force.
Tablespace is PSAPUSER1D.
For example:
___________________________________________________________________ Backup database

___________________________________________________________________ Current value
Normal backup
initCER.sap
external backup tool (backint)
PSAPUSER1D
offline (force)
no
a b c d e g h i j l m
Backup function Parameter file Backup device type Objects for backup Backup type Query only Special options ...
Standard backup Backup from disk backup
Restart backup
Make part. backups compl.
yes
S - Start BRBACKUP (V6.20)

q - Return
Please select ==>S
Type S to start the backup.
70 Using NetBackup for SAP Performing an archive
brbackup online backup

You can use brbackup instead of sapdba to perform database backups. This section shows an online backup. You can change the backup_mode by changing the initSAP.sap parameter file or by specifying -t online on the brbackup command. Here is what these changes look like in initSAP.sap: backup_type = online_file This backup mode allows sapdba or brbackup to use a semaphore file with the NetBackup for SAP backint interface. This mode provides a better online backup for very large files because only the necessary tablespaces are placed in backup mode. When NetBackup is ready to process another file, it notifies brbackup. You can change the backup_mode to online to test this mode. To use brbackup 1 2 3 Verify that you have completely configured NetBackup, NetBackup for SAP, and the SAP tools. See Configuration on page 39. Verify that you are user sapadm. Enter the brbackup command.

To initiate an online backup, enter the following command: brbackup -d util_file_online -t online -m all
To initiate a full backup when you use RMAN, enter the following command: brbackup -d rman_util -t offline -m full -c
To initiate an incremental backup when you use RMAN, enter the following command: brbackup -d rman_util -t online -m incr -c
Performing an archive
This section explains how to create two backup copies of an archive log. An archive is performed in a fashion similar to a backup. You can use the NetBackup multiple copies feature or brarchive command to create the backup copies. You can store each copy on separate media and retrieve them. Depending on how you use NetBackup for SAP, create archive log backups copies with the method that is easiest for you.
Method 1: Using the NetBackup multiple copies feature

If multiple copies is enabled in a backup schedule, NetBackup automatically makes up to four copies of a backup. The brarchive command uses this information and creates the specified number of backup copies of the archive
Using NetBackup for SAP Performing an archive
71
log file. For more information on the multiple copies feature, see the NetBackup Administration Guide, Volume 1.
Examples
Example 1. When multiple copies is enabled, the following command creates the number of backup copies that are specified and writes each copy to a different tape: brarchive -d util_file -s
Example 2. To restore the first available copy of an archive log file, issue the following command: brrestore -d util_file -a log_number where log_number is the number of the archive log you want to restore.
Method 2: Using two brarchive commands in sequence

You can also create a backup copy of the archive log by issuing two brarchive commands in sequence. You can write each backup copy to different media. For example, you can write each backup copy to two different tapes, to disk and tape, or to any combination of media.
Examples
This example assumes that only one archive log is to be backed up, archive log 77. To create the backup copies For the first copy, call brarchive with the -s option. For the second copy, call brarchive with the -sc option. Both commands automatically determine that the archive log file needs to be backed up and perform the backup. 1 2 To create the first backup copy, issue the following command: brarchive -d util_file -s
To create the second backup copy, issue the following command: brarchive -d util_file -sc
To restore the archived log files

1 2 To restore the first backup copy, issue the following command:
brrestore -a 77
To restore the second backup copy, issue the following command: brrestore -a2 77
72 Using NetBackup for SAP Performing a restore
Performing a restore
The following sections explain how to perform a restore if you have NetBackup for SAP on an Oracle database. NetBackup for SAP on a MaxDB database required a different configuration. See Using NetBackup for SAP on a MaxDB database to perform backups and restores on page 121.
Using the SAPDBA utility (NetBackup for SAP on Oracle databases only)
To restore a partial database or full Oracle database, you must have a list of valid restores. Use the sapdba system to maintain the list of restores for specific tablespace or complete database restores. When the user restores either individual tablespaces or full databases, the user is prompted before an existing copy of the target file is deleted. sapdba then invokes the brrestore command. brrestore submits the BID and file name list to the NetBackup for SAP backint interface. The backint interface cross-references the exact date and time to when the backup was made and uses NetBackup to recover the file. The backint interface monitors the progress of the restore and reports status back to brrestore. Upon completion, the backint interface saves a copy of the NetBackup restore logs for auditing purposes. sapdba then provides required database recovery, such as media recovery, and restarts the database server. To use brrestore to restore database files

In Oracle-based environments without RMAN, use the command with the following options: brrestore -d util_file -b last -m full -c force
In Oracle-based environments with RMAN, use the command with the following options: brrestore -d rman_util -b last -m full -c force
Redirecting a restore to a different client (NetBackup for 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. In order to perform a redirected restore, the following conditions must be present:
Using NetBackup for SAP Performing a restore
73
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.
Note: In some situations, you can restore from lower to higher release levels of Oracle. For more information, see your Oracle documentation. The redirected restore is a four-part process: 1 2 3 4 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 procedure explains each part of the process. For more information on redirected restores, see the NetBackup Administrators Guide. To perform a NetBackup for SAP redirected restore
1 2 Verify that you are logged in as the NetBackup administrator.
Configure the NetBackup server to allow redirected restores.
This step differs depending on whether you want to allow restores from any client or from only selected clients. a To remove restrictions for all clients, create the following file on the Netbackup master server: /usr/openv/netbackup/db/altnames/No.Restrictions
OR To restrict clients to restore only from certain other clients, create the following file: /usr/openv/netbackup/db/altnames/client_name
where client_name is the name of the client that are allowed to perform the redirected restore. If you performed step b, add the name of the NetBackup for SAP source client to the client_name file.
c 3
On the destination client, back up the existing control files to preserve the original configuration. These files are usually in the $ORACLE_HOME/dbs directory. Copy configuration and control files from the NetBackup for SAP source client to the NetBackup for SAP destination client.
74 Using NetBackup for SAP Performing a restore
For example, you can use ftp(1) to perform the copies. a 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
b 5
Copy the $SAPDATA_HOME/sapbackup directory from the source client to the same location on the destination client.
Configure the NetBackup for SAP destination client. a Change the client parameter in the initSID.utl file on the destination client to the name of the source client. OR 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
Note: The SAP_CLIENT variable has higher priority than the value in the initSID.utl file. b (Conditional) Set the restore_filter parameter in the initSID.utl file on the destination client. Perform this step only if you want to restore images created with a NetBackup for SAP version before 6.0. For example, consider if the source client path is set to /home_db/oracle/sap and the input file contains the path /oracle/SAP. Then the value of restore_filter is a script such as the following:
#!\/bin\/sh
# this shell is used to change some logically linked files
# during a restore
sed -e '
s\/oracle\/SAP\/home_db\/oracle\/sap\/' $1 > $2
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.
Using NetBackup for SAP Performing a restore
75
Note: 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. 6 Perform the redirected restore. a b Log onto the NetBackup for SAP destination client. Enter the following command: brrestore -d util_file -b last -m full
Redirected restore sample environment

This sample environment shows how a redirected restore uses the restore_filter script. This example assumes the following:

Source client

Actual path is /home_db/oracle/sap Includes soft link /oracle/SAP (SAP is the sytem ID), which points to /home_db/oracle/sap.
Destination client

Actual path is /home2/sap Also has soft link /oracle/SAP, which points to /home2/sap. Make soft link /home_db/oracle/sap, which points to /home2/sap
In the restore_filter script, substitute the path that was provided in the input file list of the destination client with the actual path of the source client. The resulting script sample might look like the following:
#!/bin/sh
# this shell is used to change some logically linked files
# during a restore
sed -e '
s\/oracle\/SAP\/home_db\/oracle\/sap\/' $1 > $2
When the backup starts, the file list contains the file path with the following soft link: /oracle/SAP/sapdata1/btabd_1/btabd.data1 However, the file is backed up with the following actual path: /home_db/oracle/sap/sapdata1/btab_d/btabd.data When the request for a restore is issued, the input file list contains file paths with soft links. These are converted to the actual path of the destination client. Because this path is different from the source client path, the restore would fail in the inquire phase. To prevent this kind of failure, use the restore_filter script.
76 Using NetBackup for SAP Restarting failed backups and restores
Disaster recovery using BRRECOVER

When running disaster recovery using BRRECOVER, if the initDBSID.sap file is not present, BRRECOVER calls BACKINT without the -p init<DBSID>.utl parameter. If Netbackup for SAP is called without the util file parameter, it checks for the SAP_RECOVERY environment variable. If the environment variable is set to disaster, the restore is allowed without util file parameter. Netbackup for SAP then restores using the default SAP policy.
Restarting failed backups and restores

A backup or a restore can fail or terminate because of system error or resource contention. For example, a backup can fail because the tape library ran out of tapes, the storage unit ran out of space, or a network connection was lost. In the case of large environments with more than a terabyte of data, it might not be feasible to repeat the backup all over again. You might have already missed the current backup window, so the backup can happen only in the next backup window. In this situation, you can use the checkpoint restart capability. Netbackup for SAP enables you to restart backups and restores from the point of failure. By default, Netbackup for SAP takes checkpoints every 15 minutes during a backup. You can specify that these checkpoints occur at a different interval on the backup policys attributes tab. For a failed job, the agent retains partial image and catalog entries in the netbackup catalog for the files that have been already backed up. Note: Netbackup for SAP uses backint to restart failed backups and restores of Oracle databases. Netbackup for SAP does not support the use of RMAN to restart failed backups and restores of Oracle databases. Nor can it restart failed backups or restores of any databases that are based on MaxDB.
Restarting backups
The following sections explain how the NetBackup for SAP backup process works and how to restart a backup. Caution: Follow the instructions in this section to restart a backup. Attempts to restart a backup from the Activity Monitor will fail.
Using NetBackup for SAP Restarting failed backups and restores
77
How does the backup process work?

The brbackup command initiates the backup for SAP on Oracle databases. The brbackup command calls the Netbackup for SAP agent (backint) with appropriate options and gives a list of files for backup. Backups can be either successful or unsuccessful. The results are as follows:
For a successful backup: For each file that is backed up successfully, backint sends the following message to brbackup: #SAVED BID filename For each SAVED ... message that brbackup receives, brbackup writes the following information to its log file: #FILE..... /home1/orasap/inp/file1
#SAVED.... VXF1134574401
For an unsuccessful backup: For each file that is not backed up successfully, backint sends the
following message to brbackup:
#ERROR filename
For each ERROR ... message that brbackup receives, brbackup writes
the following message to its log file:
BR0233E Backup utility has reported an error while saving
file /home/orasap/inp/filename
A backup can fail for several reasons that are unrelated to NetBackup operations:

The tape library ran out of tapes A network connection problem occurred The user killed the backup but wants to restart it sometime later
For situations like these, Netbackup for SAP saves the partial image for the files that have been already backed up. Catalog entries in the NetBackup catalog are also saved. It returns the following messages:

#SUCCESS BID filename - For the files that were backed up #ERROR filename - For the files that were not backed up
If a backup has terminated because of any problems that are not related to NetBackup, you do not have to repeat a complete backup again. Use the brbackup command and the -f logfile parameter. The brbackup command automatically determines the files that still need to be backed up. The next section describes how to use the -f parameter to restart a backup.
Configuring the checkpoint restart option in a backup policy

To restart backups from the point of failure, you must enable checkpointing in your NetBackup for SAP policy. To enable this feature, in the attributes for the policy, select Take Checkpoints Every. By default, this option is disabled. When this option is not enabled, a failed backup that is based on this policy is restarted from the beginning of the job. When Take Checkpoints Every is enabled, by default the NetBackup for SAP agent takes a checkpoint every 15 minutes. You can configure this time interval for a different duration.
Restarting a backup
You can use the brbackup commands -f option to back up only the files that failed to be backed up. You do not have to specify that all files be backed up again. Use the following procedure to restart a backup. To restart a backup

Run the brbackup command with the -f logfile parameter. For logfile, specify one of the following:

The log file name of the failed job. When the log file is specified, brbackup checks it for the files that were not backed up successfully. The keyword last. When this keyword is specified, brbackup checks the status of the last backup job for the files that were not backed up successfully.
The brbackup command examines the specified file. It determines the files that were backed up successfully and the files that were not backed up successfully. brbackup sends backint the list of files that still need to be backed up. brbackup starts a new job only for the files that still need to be backed up. Example 1. The following command specifies a log file:
brbackup -d util_file -m all -c -f bdprcayp.aff
Example 2. The following command specifies the last backup job:

brbackup -d util_file -m all -c -f last
Example: Restarting a backup job

The example in this section shows how to restart a failed backup job. Assume the following:

The backup job was deliberately cancelled from the activity manager. In a real user case, a job might fail for different reasons.
79
You enabled checkpointing (the Take Checkpoints Every option in the policy). You ran the backup according to the following brbackup command:
#brbackup -d util_file -t offline -m all -c force
The following is an excerpt from the output log:

BR0280I BRBACKUP time stamp: 2006-02-28 21.07.59
BR0057I Backup of database: SUD
BR0058I BRBACKUP action ID: bdsbecnl
BR0059I BRBACKUP function ID: aff
BR0110I Backup mode: ALL
BR0077I Database files for backup:
/oracle/SUD/origlogA/log1_m1.dbf
/oracle/SUD/origlogB/log2_m1.dbf
/oracle/SUD/saparch/cntrl/cntrlSUD.dbf
BR0061I 29 files found for backup, total size 853.604 MB
The previous output log shows the 29 files for backup. brbackup calls the NetBackup SAP agent for backup. In this example, we have configured the checkpoint frequency for 5 minutes. By the time first checkpoint was taken (that is, in the first 5 minutes), 13 files were backed up. The user killed the job from the NetBackup activity monitor after NetBackup took the first checkpoint. backint returned #SUCCESS messages to brbackup for 13 files that were backed up. For the files that were yet to be backed up, backint retuned #ERROR. The following are the output messages from the brbackup log:
BR0229I Calling backup utility with function 'backup'...
BR0278I Command output of '/usr/sap/SUD/SYS/exe/run/backint -u SUD -f backup -i
/oracle/SUD/sapbackup/.bdsbecnl.lst -t file -p /home1/orasap/ora920/dbs/initSUD.utl
-c':
*******************************************************************
Program: /usr/sap/SUD/SYS/exe/run/backint 6.5
Input File: /oracle/SUD/sapbackup/.bdsbecnl.lst
Profile: /home1/orasap/ora920/dbs/initSUD.utl
Function: BACKUP
Backup Type: BACKUP_FILE
*******************************************************************
#FILE..... /oracle/SUD/sapdata1/btabd_1/btabd.data1
#SAVED.... VXF1141141105
#FILE..... /oracle/SUD/sapdata2/btabi_1/btabi.data1
#SAVED.... VXF1141141105
.
.
BR0233E Backup utility has reported an error while saving file

*******************************************************************
BR0279E Return code from '/usr/sap/SUD/SYS/exe/run/backint -u SUD -f backup -i
-c': 2
BR0232E 13 of 29 files saved by backup utility
BR0231E Backup utility call failed
BR0304I Starting and opening database instance SUD ...
BR0305I Start and open of database instance SUD successful
BR0056I End of database backup: bdsbecnl.aff 2006-02-28 21.15.50
BR0054I BRBACKUP terminated with errors
You can then restart the preceding job with following command:
#brbackup -d util_file -t offline -m all -f last -c force
The brbackup command examined the last backup log and found that the backup failed for some files. It writes following messages in the beginning of output log for this session:
BR0051I BRBACKUP 6.40 (22)
BR0055I Start of database backup: bdsbedhj.aff 2006-02-28 21.16.35
BR0453W Error message found in /oracle/SUD/sapbackup/bdsbecnl.aff:
'BR0233E Backup utility has reported an error while saving file
/oracle/SUD/sapraw/rawDev4'
'BR0233E Backup utility has reported an error while saving file
/oracle/SUD/sapraw/rawDev5'
.
.
'BR0279E Return code from '/usr/sap/SUD/SYS/exe/run/backint -u SUD -f backup -i
-c': 2'
'BR0232E 13 of 29 files saved by backup utility'
'BR0231E Backup utility call failed'
BR0459W Backup /oracle/SUD/sapbackup/bdsbecnl.aff terminated with errors
.
.
BR0057I Backup of database: SUD
BR0058I BRBACKUP action ID: bdsbedhj
BR0059I BRBACKUP function ID: aff
81
BR0110I Backup mode: ALL

BR0077I Database files for backup:
BR0061I 16 files found for backup, total size 283.502 MB
BR0091I 13 files were already saved in: bdsbecnl.aff
As the preceding output log shows, 13 files were already backed up. The following is the output of a successful brbackup restart job. This job is the one that backed up the remaining 16 files:
BR0229I Calling backup utility with function 'backup'...
BR0278I Command output of '/usr/sap/SUD/SYS/exe/run/backint -u SUD -f backup -i
/oracle/SUD/sapbackup/.bdsbedhj.lst -t file -p /home1/orasap/ora920/dbs/initSUD.utl
-c':
*******************************************************************
Program: /usr/sap/SUD/SYS/exe/run/backint 6.5 Input File: /oracle/SUD/sapbackup/.bdsbedhj.lst Profile: home1/orasap/ora920/dbs/initSUD.utl Function: BACKUP Backup Type: BACKUP_FILE *******************************************************************
#FILE..... /oracle/SUD/sapraw/rawDev4
#SAVED.... VXF1141141607
.
.
#FILE..... /oracle/SUD/saparch/cntrl/cntrlSUD.dbf
#SAVED.... VXF1141141607
*******************************************************************
BR0232I 16 of 16 files saved by backup utility
BR0230I Backup utility called successfully
Restarting restores
The following sections explain how the NetBackup for SAP restore process works and how to restart a restore. Caution: Follow the instructions in this section to restart a restore. Attempts to restart a restore from the Activity Monitor will fail.
How does the restore process work?

You can restore an SAP database that is based on Oracle by using the brrestore command. The brrestore command writes a record into the input file for each file to be restored. This record is named BID filename. brrestore then calls the Netbackup for SAP agent (backint) with the appropriate options. Restores can be either successful or unsuccessful. For each record in the input file, the brrestore command expects one of the following messages from backint:

For a successful restore:
#FILE..... filename
#RESTORED BID
For an unsuccessful restore:
#ERROR filename
If the restore is successful, backint reports #RESTORED BID filename.
Then, brrestore writes the following:
#FILE..... /oracle/CER/sapdata1/btabd_1/btabd.data1
#RESTORED. VXF1147974254
brrestore does not write any messages if backint reports #ERROR filename. If the restore job fails after restoring some files, the Netbackup for SAP agent (backint) reports #RESTORED for the files it restored. It reports #ERROR for the files that it did not restore.
Restarting a restore
You can use the brrestore commands -f option to restore only the files that failed to be restored. You do not have to specify that all files be restored again. Use the following procedure to restart a restore. To restart a restore

Run the brrestore command with the -f logfile parameter. For logfile, specify one of the following:

The log file name of the failed job. When the log file is specified, brrestore checks it for the files that were not restored successfully. The keyword last. When this keyword is specified, brbackup checks the status of the last restore job for the files that were not restored successfully.
The brrestore command examines the specified file. It determines the files that were restored successfully and the files that were not restored successfully.
83
brrestore sends backint the list of files that still need to be restored. brrestore starts a new job only for the files that still need to be restored. Example 1. The following command specifies a log file:
brrestore -d util_file -m all -f rdsqcxdf.rsb
Example 2. The following command specifies the last restore job:

brrestore -d util_file -m all -f last
Example: restarting a restore job

This section shows how to restart a failed restore job. Assume that the you deliberately cancelled the job from the activity monitor. In reality, the job might fail due to different reasons. This example shows the log messages that brrestore created while restoring the files for the CER database, using the following command:
brrestore -d util_file -b last -m all
The following are excerpts from the corresponding brrestore log file:
BR0280I BR0407I BR0408I BR0409I BR0449I BR0419I BR0416I BR0421I BR0134I BRRESTORE time stamp: 2006-05-18 23.18.15 Restore of database: CER BRRESTORE action ID: rdsqcxdf BRRESTORE function ID: rsb Restore mode: ALL Files will be restored from backup: bdsqcwtl.aff 2006-05-18 23.14.01 19 files found to restore, total size 645.148 MB Restore device type: util_file Unattended mode with 'force' active - no operator confirmation allowed
BR0280I BRRESTORE time stamp: 2006-05-18 23.18.16

BR0229I Calling backup utility with function 'restore'...
BR0278I Command output of '/usr/sap/CER/SYS/exe/run/backint -u CER -f restore -i
/oracle/CER/sapbackup/.rdsqcxdf.lst -t file -p /home/orasap/Ora920/dbs/initCER.utl
-c':
******************************************************************************
Program: /usr/sap/CER/SYS/exe/run/backint 6.5
Input File: /oracle/CER/sapbackup/.rdsqcxdf.lst
Profile: /home/orasap/Ora920/dbs/initCER.utl
Function: RESTORE
******************************************************************************
#FILE..... /oracle/CER/sapdata1/btabd_1/btabd.data1
.
.
#FILE..... /oracle/CER/sapdata1/el46bi_1/el46bi.data1
***********************************************************************
BR0374E 7 of 19 files restored by backup utility
BR0231E Backup utility call failed
After you start the brrestore command, you cancel the restore job from the activity monitor. As the preceding log indicates, brrestore restored 7 out of the 19 files. You can restore the remaining files as part of a new brrestore session. In a production situation, you should identify and correct the cause of failure before restarting brrestore. Enter the following command with the -f option to start brrestore:
brrestore -d util_file -m all -f last
The following output is an excerpt from the corresponding brrestore log file:
BR0453W Error message found in /oracle/CER/sapbackup/rdsqcxdf.rsb: 'BR0374E 7 of 19 files restored by backup utility' BR0453W Error message found in /oracle/CER/sapbackup/rdsqcxdf.rsb: 'BR0231E Backup utility call failed' BR0471W Restore /oracle/CER/sapbackup/rdsqcxdf.rsb terminated with errors BR0428W File /oracle/CER/sapdata6/es46bd_1/es46bd.data1 will be overwritten
BR0280I BR0407I BR0408I BR0409I BR0449I BR0419I BR0416I BR0445I BR0421I BRRESTORE time stamp: 2006-05-18 23.19.20
Restore of database: CER
BRRESTORE action ID: rdsqcxfs
BRRESTORE function ID: rsb
Restore mode: ALL
Files will be restored from backup: bdsqcwtl.aff 2006-05-18 23.14.01
12 files found to restore, total size 520.094 MB
7 files were already restored in the following run: rdsqcxdf.rsb
Restore device type: util_file
brrestore checks the previous log file and finds that 12 files need to be restored and that 7 files are already restored. brrestore directs backint to restore the 12 files. The log file is as follows:
BR0134I Unattended mode with 'force' active - no operator confirmation allowed
BR0229I Calling backup utility with function 'restore'...
BR0278I Command output of '/usr/sap/CER/SYS/exe/run/backint -u CER -f restore -i
/oracle/CER/sapbackup/.rdsqcxfs.lst -t file -p /home/orasap/Ora920/dbs/initCER.utl
-c':
***********************************************************************
Program:/usr/sap/CER/SYS/exe/run/backint 6.5
Input File:/oracle/CER/sapbackup/.rdsqcxfs.lst
Profile:/home/orasap/Ora920/dbs/initCER.utl
Function:RESTORE
***********************************************************************
#FILE..... /oracle/CER/sapdata6/es46bd_1/es46bd.data1
.
.
85
#FILE..... /oracle/CER/sapdata1/system_1/system.data1
***********************************************************************
BR0374I 12 of 12 files restored by backup utility
BR0230I Backup utility called successfully
As the preceding log shows, the remaining 12 files are restored successfully.
Chapter
NetBackup for SAP with Snapshot Client


Using NetBackup for SAP to backup large databases on page 87 NetBackup for SAP with Snapshot Client overview on page 89 How does NetBackup for SAP Snapshot Client work? on page 91 Configuring snapshot backups on page 97 Restoring data from a snapshot backup on page 105 Configuring block-level incremental backups on page 107 Additional snapshot client configuration information on page 113
When Netbackup for SAP is used with Snapshot Client, the environments that are based on Oracle are supported. Environments that are based on MaxDB databases are not supported. The ability to restore your environment quickly depends on your ability to back up business-critical data quickly. Backups enable you to restore your environment in the event of logical database errors or physical errors such as hardware failures or disasters. Symantec recommends that customers perform online backups at least daily and offline backups once a week. Periods of low SAP system activity are few and far between because customers tend to run long batch jobs on weekends or during night hours.
Using NetBackup for SAP to backup large databases

Symantec recommends that customers with production databases back up their environments on a daily basis. However, due to the following concerns, this
88 NetBackup for SAP with Snapshot Client Using NetBackup for SAP to backup large databases
daily backup often is not feasible for databases of a size between 100 GB to over 1 TB:

Server performance. The backup process for large databases can cause severe performance problems because the process consumes the database server's resources. CPU time, the system bus, the I/O bus, hard disk controllers, and volume controllers become saturated. As a result, online use of the SAP system is limited and system performance is unpredictable during the backup. System availability. Traditionally, backup activities were carried out when there was little or no system activity. This time window usually occurred at night. In todays production environments, which require little or no system downtime, this window is small, if one even exists. Network performance. A backup of large databases from the production host and over the network can lead to instability and further performance loss.
NetBackup for SAP with Snapshot Client supports split mirror backups. Split mirror backups are the recommended backup method for large databases because these backups overcome the preceding concerns. Figure 5-1 on page 88 shows a split mirror environment. Figure 5-1 SAP split mirror backup scenario
Database server for live system
Database server for backup; also secondary system
Constant copy (split) Mirror1 Live data
Local copy Mirror2
In SAP environments, the Snapshot Client technology supports the following major backup strategies:
NetBackup for SAP with Snapshot Client NetBackup for SAP with Snapshot Client overview
89
Offhost backup, which offers more performance. It offloads database backup activity and CPU cycles from the production host to the backup host. Thus, it improves the performance of the production environment. Snapshot backup, which requires no downtime of your production system. SAP supports both offline and online split mirror backups. In an online split mirror backup, the production database remains available for user transactions. The need for backup windows is eliminated and 24/7 uptime functionality is provided for continuous business transactions. Block-level incremental (BLI) backup. BLI backups decrease the amount of backup media that is required and significantly reduce CPU and network overhead during backups. Split mirror backups. Because the mirrors are split from their standard devices and mounted on the backup server, the backup does not overload the network. The backup is run on the backup server without affecting the network.
NetBackup for SAP with Snapshot Client overview

The NetBackup for SAP Snapshot Client software consolidates a variety of snapshot-based technologies into a single, easy-to-use backup solution. Table 5-10 on page 73 summarizes some of the Snapshot Client features. Table 5-1 Snapshot Client major features Key benefit
Supports a variety of array and software snapshots and provides a base for all Snapshot Client solutions. Backup overhead shifts from critical systems to an alternate backup host. Less data leads to high performance data protection.
Snapshot Client feature

Array and software snapshot integration Offhost backup
Block-level incremental backup and recovery RMAN proxy and RMAN stream backup intermixed
Allows you to intermix off-host full backup and on-host incremental backup.
The following sections describe the features that Table 5-1 introduces. In addition, these sections describe additional features as they pertain to NetBackup for SAP.
90 NetBackup for SAP with Snapshot Client NetBackup for SAP with Snapshot Client overview
Snapshot backup
A snapshot is a disk image of the client's data that is created almost instantaneously. When it is used with Snapshot Client, NetBackup for SAP backs up Oracle objects by taking snapshot images of the component files on the local host. Later it backs up the snapshot version to a storage unit. Snapshot backup captures the data at a particular instant without causing significant client downtime. Client operations and user access continue without interruption during the backup. The resulting capture or snapshot can be backed up without affecting the performance or availability of the database. You can perform snapshot backup by using backint or by using RMAN proxy copy.
Instant recovery
This feature makes backups available for instant recovery from disk. Instant recovery combines snapshot technology with the ability to do rapid disk-based restores. NetBackup creates the image without interrupting user access to data. Optionally, you can specify that the image be retained on disk and backed up to storage. Instant recovery makes it possible to perform block-level restores, file promotion, and rollback.
Off-host backup
An off-host backup shifts the burden of the backup process onto a separate backup agent, such as an alternate client. An off-host backup reduces the effect on the client's resources that a local backup ordinarily causes. The backup agent reads the data from the client disk and writes it to storage. You can perform off-host backups by using backint or by using RMAN proxy.
Block-level incremental backup

A block-level incremental (BLI) backup uses the change tracking capabilities of the Veritas File System (VxFS) Storage Checkpoint feature. In a BLI backup, only the changed blocks of data are backed up, not the entire file or file system. A BLI backup saves time, decreases the amount of backup media that is required, and significantly reduces CPU and network overhead during backups.
RMAN proxy copy

Proxy copy is an extension to Oracle's Media Management API. A proxy copy is a special type of backup in which RMAN turns over control of the data transfer to the NetBackup for SAP agent. The agent can then manage the entire data movement between the disks that contain the Oracle data files and the storage devices that NetBackup manages.
NetBackup for SAP with Snapshot Client How does NetBackup for SAP Snapshot Client work?
91
With proxy copy, RMAN provides a list of files that require backup or restore to the NetBackup for SAP agent. The NetBackup for SAP agent determines how the data is moved and when to move the data.
RMAN stream-based backups

RMAN stream-based operations are the standard way by which NetBackup for SAP implements conventional RMAN backups and restores. In a stream-based backup, NetBackup moves the data that the Oracle server process provides. NetBackup for SAP captures the data stream content that RMAN provides. If the user specifies multiple streams, the following occurs:

RMAN opens multiple streams NetBackup catalogs the multiple streams as separate images
RMAN proxy and RMAN stream-based backups intermixed

RMAN Proxy backups can be used to perform off-host snapshot based split mirror full backups. For example, you can use RMAN proxy for weekly full backups. RMAN stream-based backups can be used to perform on-host incremental backups. In this way you can perform daily backups. NetBackup for SAP offers you the flexibility to intermix backup methods. You can specify both RMAN proxy copy off-host snapshot backups and RMAN stream-based on-host incremental backups. When you perform both types of backups, you remove the backup load from the production host during full backups. You also reduce the amount of data for incremental backups.
How does NetBackup for SAP Snapshot Client work?

NetBackup initiates a database backup when a user requests a backup or when a schedule indicates that it is time to run a backup. A shell script in the backup selections list of a NetBackup for SAP policy contains the backup commands. These are the commands that the brtools need to use to perform the backup. The brtools include the brbackup command. The brbackup command initiates backup of the specified objects. The brbackup command provides a list of physical file names to NetBackup for SAP. For more information, see Database objects that are supported by advanced backup methods on page 97. Netbackup for SAP verifies that the policy it selected for the backup is configured with the appropriate Snapshot Client attributes. NetBackup for SAP then initiates file-based backups of the Oracle files, either through backint or RMAN proxy. NetBackup determines whether to use backint or RMAN when it
92 NetBackup for SAP with Snapshot Client How does NetBackup for SAP Snapshot Client work?
reads the file that is specified as an argument to the -d parameter on the

brbackup command. The NetBackup Snapshot Client interface performs the
data movement.
Before NetBackup for SAP performs the backups, it requests that brbackup or
RMAN put the data files being backed up into backup mode.
NetBackup then creates a snapshot of the files. When the snapshot is complete,
NetBackup for SAP signals back to brbackup or RMAN to take the datafiles out
of backup mode. The datafiles that are selected for backup are in backup mode
only for the period of time necessary to capture a snapshot of the data.
Sequence of operations: backup

The following sections show how NetBackup for SAP performs database split mirror backups.
SAP Oracle database split mirror backup (using backint)

Figure 5-2 on page 93 shows the sequence of operations when you use backint to perform a backup.
93
Figure 5-2
SAP Oracle online and offline backups using brbackup and backint
2. Check policy for Snapshot Client attributes
3. Shut down or put database in backup mode
Production database host brbackup Oracle database engine File system 7. Backup snapshot backint NetBackup
6. Database mode online A and B Mirror A and B 4. Create snapshot 1. File information 5. Snapshot taken 8. Backup image information
Files are backed up to tape or disk
When NetBackup for SAP performs a backup by using backint, the following occurs: 1 2 3 NetBackup for SAP receives a list of files to back up from brbackup. Netbackup for SAP queries the policy to check whether the Snapshot Client policy attributes are specified. When NetBackup for SAP is ready to back up the files, it sends a request to brbackup to put the data files into backup mode. Depending on the parameters with which the brbackup command was invoked, brbackup either shuts down the database or puts the database in backup mode.
If brbackup is invoked with following command, brbackup shuts down the database: If brbackup is invoked with following command, brbackup puts the database or tablespace into backup mode:
# brbackup -d util_file_online -t offline -m all -c force
# brbackup -d util_file_online -t online -m all -c force
4 5 6 7 8
Netbackup for SAP quickly creates a snapshot of the files to back up. This operation typically takes a few seconds or minutes. Netbackup for SAP notifies brbackup that the snapshot has been taken and that the database can be either started or taken out of backup mode. brbackup either starts the database or takes the database out of backup mode. NetBackup backs up the snapshot that it created. NetBackup returns backup image information to brbackup.
SAP Oracle database split mirror backup (using RMAN proxy)

Figure 5-3 on page 95 shows sequence of operations when you use RMAN proxy to perform a backup.
95
Figure 5-3
SAP Oracle online and offline backups using RMAN proxy
brbackup
2. Check policy for Snapshot Client attributes 3. Shut down or put database in backup mode
Production database host RMAN proxy Oracle database engine File system 7. Backup snapshot libobk NetBackup
6. Database mode online A and B Mirror A and B 4. Create snapshot 1. File information 5. Snapshot taken
Files are backed up to tape or disk
8. Backup image information returned to brbackup through RMAN
When NetBackup for SAP performs a backup by using RMAN, the following occurs: 1 2 3 NetBackup for SAP receives a list of files to back up from RMAN. Netbackup for SAP queries the policy to check whether the Snapshot Client policy attributes are specified. When NetBackup for SAP is ready to back up the files, it sends a request to RMAN. RMAN puts the data files into backup mode or shuts down. NetBackup sends this request by using an SBT API. Depending on the parameters with which the brbackup command was invoked, RMAN either shuts down the database or puts the database in backup mode.
If brbackup is invoked with following command, RMAN shuts down the database: If brbackup is invoked with following command, RMAN puts the database or tablespace into backup mode:
# brbackup -d rman_util -t offline -m full -c force
# brbackup -d rman_util -t online -m full -c force
4 5 6 7 8
Netbackup for SAP quickly creates a snapshot of the files to back up. This operation typically takes a few seconds or minutes. Netbackup for SAP notifies RMAN that the snapshot has been taken and that the database can be either started or taken out of backup mode. RMAN either starts the database or takes the database out of backup mode. NetBackup backs up the snapshot that it created. NetBackup returns backup image information to brbackup.
Notes on brbackup command parameters

NetBackup for SAP does not perform snapshot backups if the following parameters are specified on the brbackup command line:
-d util_file -t offline/online
When you specify these parameters, brbackup either shuts down the database or brbackup puts the database in backup mode. Then brpbackup calls the NetBackup for SAP agent. The database remains in backup mode for the duration of entire backup. There is no value to doing snapshot-based backups in this scenario. The snapshot technology adds no value because the database is either offline or in backup mode for several hours. If you initiate backups with these parameters in effect, NetBackup for SAP performs only standard backups directly to the secondary device. NetBackup for SAP ignores any snapshot-related configuration in the policy
Sequence of operation: restore

If you use the NetBackup for SAP Snapshot Client during a backup, you can use the typical NetBackup for SAP restore process. The Snapshot Client has no effect on the restore process. Follow the existing NetBackup for SAP mechanism to perform restores of split mirror backups or block-level incremental backups. If you use the instant recovery with rollback option, you need to export the SAP_RESTORE environment variable. For information on this kind of a restore, see Restoring data from a snapshot backup on page 105.
NetBackup for SAP with Snapshot Client Configuring snapshot backups
97
Database objects that are supported by advanced backup methods

The brbackup command and Oracle RMAN control the kinds of database objects that proxy copy can back up. They also control what NetBackup can back up using Snapshot Client backup methods. Oracle allows proxy copy backups of databases, table spaces, and data files. For profile and configuration files, the NetBackup for SAP backint command performs standard backups directly to the configured storage unit. NetBackup for SAP uses advanced methods only when it moves Oracle data files. The following is additional information on special file types:

Symbolic links and raw data files. NetBackup for SAP with Snapshot Client backs up and restores the data files that consist of symbolic links and regular files. NetBackup for SAP backs up and restores both the symbolic link and the file. However, if you selected Retain snapshots for instant recovery, the symbolic link must reside on the same file system as the data file. When you use instant recovery, if the symbolic link resides on a different file system than the data file it points to, the restore fails. NetBackup for SAP with Snapshot Client backs up and restores the data files that are created on raw partitions Quick I/O data files. NetBackup for SAP with Snapshot Client backs up and restores quick I/O Oracle data files. A quick I/O file consists of two components: a hidden file with space allocated for it and a link that point to the quick I/O interface of the hidden file.

On the backup, NetBackup for SAP with Snapshot Client follows the symbolic link and backs up both components of the quick I/O file: the symbolic link and the hidden file. On the restore, NetBackup for SAP with Snapshot Client restores both components from the backup image. If one or both of the components are missing, NetBackup for SAP with Snapshot Client creates the missing component(s).
Configuring snapshot backups

You can combine two NetBackup features, snapshot backup and instant recovery, to enable fast database backups and recoveries. These features are as follows:

A snapshot backup occurs when NetBackup creates a point-in-time disk image of the database and copies that image to disk. This process is nearly instantaneous, so user access to the database is not interrupted during the backup.
98 NetBackup for SAP with Snapshot Client Configuring snapshot backups
An instant recovery occurs when NetBackup restores the on-disk snapshot copy of the database.
Another feature, off-host backup, can reduce the I/O processing load on the client that hosts the database. To use off-host backup, specify an alternate client (UNIX and Windows clients) or a data mover (UNIX clients only) to assume the I/O processing load.
Configuration requirements
Each agent has its own hardware requirements, software requirements, compatibility with certain features, and snapshot methods that are supported. There are also special requirements for specific types of backups. Refer to the NetBackup Snapshot Client Administrators Guide and the Symantec Support Web site for more information. Familiarize yourself with this information before you configure any snapshot backups. The following list highlights some of the requirements that pertain to database agents:

The user identification and group identification numbers (UIDs and GIDs) associated with the files to be backed up must be available to both the primary client and the alternate backup client. You should allocate at least two different volumes or file systems for database activities, as follows:

Allocate one or more volumes or file systems to the database data files.
Allocate a different set of volumes or file systems to the Oracle executables, configuration files, and the archive redo logs. One reason for to have two different volumes is to separate the data files from the other files. If the logs are configured on the same volumes (or file systems) as the data files, the logs are temporarily frozen while NetBackup takes the snapshot. The Oracle process cannot access the logs when the database is active, so the database activity might freeze until the logs become accessible again. Another reason for writing the data files to their own repository is because it is required for an instant recovery point-in-time rollback. Only data files may exist on the volume or file system being restored.

The hardware and software that is required for the appropriate snapshot method must be installed and configured correctly. NetBackup Snapshot Client must be installed and configured correctly, and the license key for this option must be registered.
99
To perform off-host backups, perform any special configuration that is required. To perform Snapshot Client backups or restores through RMAN proxy, you need brtools version 6.40, patch level 36 or greater.
Configuring an SAP policy with Snapshot Client backup methods

This section explains how to configure snapshot and instant recovery backups for an SAP policy. For information on how a snapshot method is automatically selected and details on the types of backup methods, see the NetBackup Snapshot Client Administrators Guide. Snapshot backups do not back up all database objects. Your backup configuration must include schedule types to perform file-based and stream-based backups. This configuration ensures that the entire database can be restored successfully. For snapshot or instant recovery backups, configure the following policy and schedules:

An SAP policy with the following attributes:

Snapshot methods for the file systems (raw partitions or logical volumes) on which the data objects (data files) reside. A backup method on the policy attributes dialog box. An Automatic Full Backup schedule to perform file-based snapshot and off-host backups of the datafiles in brbackup phase 1. An Application Backup schedule to back up the profile files in brbackup phase 2. NetBackup for SAP does not support snapshot backups for brbackup phase 2.
Configuring a snapshot policy

The following procedure shows how to configure a snapshot policy with optional instant recovery, snapshot retention, and off-host backup. To configure a snapshot policy 1 2 3 Open the policy you want to configure. Click on the Attributes tab. Select the SAP policy type. Figure 5-4 on page 100 shows the interface that lets you configure a snapshot policy.
Figure 5-4
Snapshot policy interface
Select the policy type Select appropriate storage unit or storage unit group
Click Perform snapshot backups (Optional) Click Retain snapshots for instant recovery
(Optional) Click Perform off-host backup and specify a method
Select a policy storage unit from the Policy storage unit list. Select a policy storage unit in this step even if you plan to select Instant Recovery Snapshots Only later in this procedure. NetBackup for SAP uses this storage unit to back up the profile files and configuration files that are backed up in brbackup phase 2. Click Perform snapshot backups. (Optional) Click Advanced Snapshot Options to choose a snapshot method. By default NetBackup chooses a snapshot method for you. To choose a snapshot method, click auto (the default) or click one of the methods that are presented in the list. The snapshot method you can use depends on your hardware environment and software environment. Only certain snapshot methods are supported in certain environments. See the NetBackup Snapshot Client Administrators
5 6
101
Guide or the supported platforms matrix on the Symantec Support Web site
for more information.
You can configure only one snapshot method per policy. For example,
assume you want one snapshot method for clients a, b, and c, and a different
method for clients d, e, and f. Then you need to create two policies for each
group of clients and select one method for each policy.
7 (Optional) Select Retain snapshots for instant recovery. When this option is selected, NetBackup retains the snapshot backup image on disk for later use in recovery. (Optional) Select Perform off-host backup. By default, the client that hosts the database performs the backup. If you want to reduce the I/O processing load on the client that hosts the database, specify an alternate client to perform the backup. Select an off-host backup method by specifying the following:

Use alternate client (UNIX and Windows clients). If you click Use alternate client, also specify the name of the client to perform the backup. This option might require additional configuration. The alternate client must be a client that shares the disk array. Use data mover (UNIX clients only). If you click Use data mover, also select one of the possible data movers:

Network Attached Storage
Click the Schedules tab.
10 Click New. Configure both an Automatic schedule and an Application Backup schedule, as follows:

The Automatic schedule is for the database files. If you want to create only disk images, in the Destination panel, under Instant Recovery, select Snapshots only. This suppresses NetBackups default behavior, which is to copy the snapshot to a storage unit. When you select Snapshots only, NetBackup creates the on-disk snapshot copy of the database, but it does not copy the snapshot to a storage unit. The on-disk snapshot becomes the only backup copy. Note that the on-disk snapshot is not considered to be a replacement for a traditional backup. The Application Backup schedule backs up of profile and configuration files, which are backed up in brbackup phase 2. NetBackup for SAP copies the profile files or configuration files to the storage unit you selected.
11 Click the Clients tab.
Specify the clients to be included in this policy. 12 Click the Backup Selections tab. Specify a backup script. For information about using scripts, seeAdditional snapshot client configuration information on page 113. 13 Configure other attributes and add any additional schedules and backup selections.
NAS snapshot policy with optional SnapVault capabilities

To use NAS snapshot with NetBackup for SAP, the SAP database must be
installed and configured to work in a NAS environment. NetBackup does not
support multi-streamed backups for a NetBackup for SAP snapshot policy that
uses NAS.
If you want to use a SnapVault storage unit, make sure the storage unit is
configured before you start to configure the NAS snapshot policy.
For more information about NAS snapshot and SnapVault, see the NetBackup
Snapshot Client Administrators Guide.
To configure a NAS snapshot policy 1 2 3 Open the policy you want to configure. Click on the Attributes tab. Select the SAP policy type. Figure 5-5 on page 103 shows the interface to use when you define a NAS snapshot policy.
103
Figure 5-5
NAS snapshot policy interface
Select the policy type Select appropriate storage unit or storage unit group
Click Perform snapshot backups Click Retain snapshots for instant recovery Click Perform off-host backup
Click Use data mover and specify Network Attached Storage
Decide on a storage unit. a If you do not want to use a SnapVault storage unit, from the Policy storage unit list, select an appropriate non-SnapVault storage unit. Although the policy cannot run without a specified storage unit, NetBackup does not use the storage unit for NAS snapshot backups. NetBackup creates the snapshot on disk regardless of which storage unit you select. NetBackup for SAP uses the policy storage unit for backups of the profile and the configuration files. (These files that are backed up as part of brbackup phase 2). You can override this storage unit in the Application Backup schedule. If you want to use a SnapVault storage unit, make sure you have defined a disk storage unit. Select the disk storage unit you have configured for SnapVault in the Policy storage unit list.
5 6 7
Select Perform snapshot backups and Retain snapshots for instant recovery. Select Perform off-host backup and Use data mover. From the pull-down menu under Use data mover, select Network Attached Storage. When the policy runs, NetBackup automatically selects the NAS_Snapshot method for creating the snapshot. As an alternative, you can manually select the NAS_Snapshot method using the Advanced Snapshot Options dialog from the policy display. For information about the Maximum Snapshots (Instant Recovery only) parameter, see the policy configuration chapter of the NetBackup Snapshot Client Administrators Guide. Click the Schedules tab. Click New. Configure both an Automatic Backup schedule and an Application Backup schedule, as follows:

8 9
The Automatic Backup schedule is for the database files. In the Destination panel, under Instant recovery, select Snapshots only. This suppresses NetBackups default behavior, which is to copy the snapshot to a storage unit. If you use SnapVault, the level you specify in the Retention field determines the retention period for the SnapVault copies on the SnapVault secondary. The Application Backup schedule is for the archived redo logs and the control files. If you use SnapVault, override the policy storage unit and specify a storage unit that is appropriate for the control files and archive logs.
10 Click the Clients tab. Specify clients to be backed up by this policy. 11 Click the Backup Selections tab. Specify a backup template or script. For information about using templates and scripts with a NetBackup for Oracle with Snapshot Client policy, see Additional snapshot client configuration information on page 113. 12 Configure other attributes and add any additional schedules and backup selections.
NetBackup for SAP with Snapshot Client Restoring data from a snapshot backup
105
Restoring data from a snapshot backup
The following sections describe how to restore files, volumes, and file systems from a snapshot backup.
Restoring individual files

Data that was backed up with Snapshot Client methods is restored in the same way as data that was backed up without Snapshot Client methods. You can use the procedure in Performing a restore on page 72 to restore data from a snapshot backup. Use this procedure for the files that were backed up with, or without, instant recovery enabled. In all cases, NetBackup determines the files that were backed up, and it initiates a corresponding restore request to the database agent. If instant recovery is enabled, NetBackup attempts to restore the file by using the unique restore methods available with the instant recovery feature. The type of restore method that NetBackup uses depends on your environment and the type of backup performed. If NetBackup is unable to use any of the instant recovery methods, it restores the file in the typical manner. Data is copied from the snapshot to the primary file system. For information on the instant recovery methods that NetBackup uses, see the NetBackup Snapshot Client Administrators Guide.
Restoring volumes and file systems using snapshot rollback

You can request that an entire volume or an entire file system be restored from an instant recovery Snapshot backup. This type of a restore is called a point in time rollback. All the data in the snapshot is restored; single file restore is not available in a rollback. You can perform a snapshot rollback from an instant recovery backup that was made with the following methods:

NAS_Snapshot VxFS_Checkpoint snapshot vxvm snapshot FlashSnap snapshots
The NetBackup Snapshot Client Administrators Guide contains more information on snapshot rollbacks.
106 NetBackup for SAP with Snapshot Client Restoring data from a snapshot backup
The following considerations are relevant for NetBackup for SAP restores:

Snapshot rollback overwrites the entire volume. With NetBackup for SAP, snapshot rollback always performs file verification. The agent checks for the following:

The requested files (number and names) are identical to those in the snapshot
The primary volume does not contain any files that were created after the snapshot was made
If verification fails, the rollback aborts with 249.
Snapshot rollback should be used with database files only. Control files and archive redo logs should exist on different file systems or volumes.
To specify a snapshot rollback restore

When you restore BACKINT-based backups with brrestore, set the following environment variable in the script or on command line:
SAP_RESTORE=rollback
When you restore RMAN-based backups with brrestore, add this entry in initSID.sap file:
rman_send = "'NB_ORA_PC_RESTORE=rollback'"
Notes on restores
An SAP database instance generally contains three instances of control files. These reside in the following data and archive log directories:
/saparch/cntrl/cntrlSID.dbf
/sapdata1/cntrl/cntrlSID.dbf
/sapdata2/cntrl/cntrlSID.dbf
If the data files in directories sapdata1 and sapdata2 are on one volume, a snapshot of this volume contains these control files. However, at the time of the restore, brrestore provides only data files for restore and not control files. This is a problem when using the instant recovery with rollback method. For the rollback method, the files in the snapshot and the files in the restore file list should match. In this case, the files do not match, so instant recovery rollback restores method fail. To avoid this problem, move the control files under locations sapdata1 and sapdata2 to some other location after you install your SAP database instance. First stop the database, then move the control files to different locations, adapt the profile file or spfile accordingly, and restart the database.
NetBackup for SAP with Snapshot Client Configuring block-level incremental backups
107
Notes on SnapVault restores

When a Point in Time Rollback restore is selected from a SnapVault backup, the entire subvolume (qtree) is restored to a new subvolume (qtree) on the primary host. The restore does not overwrite the existing subvolume. File verification is not performed. The format of the new subvolume name is as follows:
mountpointname_restore.timestamp
For example: subvol1_restore.2005.05.19.10h49m04s To use the restored and new subvolume 1 2 3 4 Unmount the original subvolume, which is the subvolume that the restore process did not overwrite. Rename the original subvolume. Rename the new subvolume with the name of the original. Mount the new subvolume on the client. Use the ALTER DATABASE RENAME DATAFILE command to point to the restored data file on the newly created subvolume.
Restoring volumes and file systems using block-level restore

This method requires the original primary data file to be present at the time of restore. The brrestore command deletes database files before restores to avoid permission problems. You can suppress this action by setting an environment variable. For example, use: BR_NFD = 1 or brrestore command parameter -NFD.
Troubleshooting
If the rollback restore fails, it might be because the database still has a file open. Shut down and restart the database to try to correct this problem.
Configuring block-level incremental backups

If only a small portion of a database changes on a daily basis, full database backups are costly in terms of time and media. The block-level incremental (BLI) backup interface extends the capabilities of NetBackup to back up only changed data blocks of Oracle database files. A database BLI backup is done at the file system block level, which means only changed blocks are backed up. Changed files are not backed up. VxFS Storage Checkpoint facility identifies changed blocks in real time. BLI backup does not need to search the entire database for the modified blocks. BLI backup saves
108 NetBackup for SAP with Snapshot Client Configuring block-level incremental backups
time, decreases the amount of backup media that is required, and significantly reduces CPU and network overhead during backups. In addition, BLI backup allows more frequent backups, so backup images are more up-to-date. BLI backup is particularly useful for any large databases that are sized in terms of hundreds of gigabytes or terabytes. Using most traditional methods for database backup, any change in the databaseno matter how smallrequires that the entire database is backed up. Using BLI backup, only modified data blocks need to be backed up.
How does BLI work?

NetBackup supports BLI full backups and BLI incremental backups of Oracle databases. BLI backup supports two types incremental backups: differential and cumulative. Full, differential incremental, and cumulative incremental backups are specified as part of the backup schedule. When performing an Oracle restore, NetBackup restores an appropriate full backup, then it applies the changed blocks from the incremental backups. Restoring any of the incremental backup images requires NetBackup to restore the last full backup image and all the subsequent incremental backups until the specified incremental backup image is restored. NetBackup performs this restore process automatically, and it is completely transparent. The media that stored the last full backup and the subsequent incremental backups must be available, or the restore cannot proceed. Note that restoring a file rewrites all blocks in that file. The first subsequent differential incremental backup and all subsequent cumulative incremental backups back up all the blocks in the restored file. After restoring an entire database, the first subsequent backup results in a full backup. The restore destination can be a VxFS, UFS (Solaris), JFS (AIX), or HFS (HP-UX) file system. The destination VxFS file system does not need to support the Storage Checkpoint feature to restore files, but a VxFS file system with the Storage Checkpoint feature is needed to perform BLI backups of the restored data. This section uses the following terms to describe BLI backups:

Full Backup. A backup in which NetBackup backs up the entire database file, not just data blocks changed since the last full or incremental backup. Cumulative BLI Backup. This is a backup of all the data blocks of database files that changed since the last full backup. A cumulative BLI backup image contains only the data blocks of database files that changed since the last full backup, but a cumulative BLI backup can reduce the number of incremental backup images that must be applied to a restore operation. This speeds up the restore process.
109
Differential BLI backup. This is a backup in which NetBackup performs a backup of only those data blocks of database files that changed since the last backup of any type (full, cumulative incremental, or differential incremental backup) was performed.
When NetBackup initiates full database backups, followed by BLI backups, it creates, manages, and uses the appropriate Storage Checkpoints of the Oracle data file file systems. These Storage Checkpoints identify and maintain a list of modified blocks.
Storage Checkpoint
The BLI backup methodology uses the Storage Checkpoint facility in the Veritas File System (VxFS) available through the Storage Foundation for Oracle. The VxFS Storage Checkpoint facility keeps track of data blocks modified by the database since the last backup. NetBackup with BLI backup leverages this facility to back up only changed blocks, not the entire database, for an incremental backup. VxFS Storage Checkpoint is a disk- and I/O-efficient snapshot of file systems. A Storage Checkpoint provides a consistent, stable view of a file system at the instant when the file system was snapped or checkpointed. Instead of making a physically separate copy of the file system, a Storage Checkpoint identifies and maintains only changed file system blocks, saving disk space and significantly reducing I/O overhead. By keeping track of changed blocks, the VxFS Storage Checkpoint enables BLI backups. VxFS Storage Checkpoint facility provides a consistent view of file systems, allowing BLI backup to freeze the database image during database backups. The Storage Checkpoint operation is similar to the snapshot file system mechanism. However, unlike a snapshot, the Storage Checkpoint persists after a system reboot. Also, the Storage Checkpoint operation is totally transparent to administrators. The Checkpoint image is managed and available only through NetBackup or through the VxDBA utility for database backup available with the Veritas Storage Foundation for Oracle. For more information on Storage Checkpoints, see the Veritas Storage Foundation for Oracle Database Administrators Guide. You can take a Storage Checkpoint while the database is online or offline. To take a Storage Checkpoint while the database is online, you must enable archive log mode. During the creation of the Storage Checkpoint, all tablespaces are placed in backup mode.
Nodata Storage Checkpoint

The Nodata Storage Checkpoint sets a bit to indicate that a block has changed. When using Nodata Storage Checkpoints, the data files are left in backup mode for the duration of the backup. The amount of redo logs generated depends on the number of changes made during the backup. To support BLI backup, the VxFS file systems need extra disk space to keep track of the block change information. The space required depends on the database workload while the backup is running. For Nodata Storage Checkpoints, the additional space required by each file system is about 1% of the file system size. The default option used by NetBackup for SAP with Snapshot Client for snapshot backups is to use Fulldata Storage Checkpoint. By using this option, the NetBackup for SAP agent keeps Oracle data files in backup mode only for the time needed to create a Storage Checkpoint.
Fulldata Storage Checkpoint

The Fulldata Storage Checkpoint makes a copy of the original data block before making a change. When using Fulldata Storage Checkpoints, the tablespaces and data files are in backup mode for only a few seconds while the Storage Checkpoint is created, so the extra archived redo log space used is very small. Space in the file system, however, is needed to keep a copy of the original block of data that was changed. If the workload is light during the backup or if the backup window is relatively short (such as for incremental backups), an additional 10% of the file system size is usually sufficient. If the database has a heavy workload while a full backup is running, the file systems might require more space. While archive log mode is required when the database is online, this mode provides the best recoverability for taking offline Storage Checkpoints, too.
Storage Checkpoint configuration on the client

By default, the NetBackup for SAP with Snapshot Client for proxy BLI backups uses the Fulldata Storage Checkpoint. When Fulldata Storage Checkpoint is in effect, the NetBackup for SAP agent keeps the SAP Oracle data files in backup mode only for the time needed to create a Storage Checkpoint. To change the default option to use Nodata Storage Checkpoint, a user must create the following file, which can remain empty: /usr/openv/netbackup/ext/db_ext/NODATA_CKPT_PROXY
If the agent finds this file during run time, it uses Nodata Storage Checkpoint, and it keeps the data files in backup mode for the duration of the backup.
111
Configuration requirements
Before configuring BLI backups, make sure your configuration meets the following requirements:

NetBackup for SAP is installed, licensed, and configured. NetBackup Snapshot Client is installed and configured, and the license key for this option has been registered. Veritas Storage Foundation for Oracle must be installed and configured. Veritas File System must have Storage Checkpoint licensed.
For more information on requirements, see the NetBackup Snapshot Client Administrators Guide.
Configuring policies for BLI backups

This section explains how to configure BLI backups for SAP policies.
BLI backups do not back up all database objects. Your backup configuration
must ensure that the entire database can be successfully restored. Include
policies to perform snapshot and standard backups.
To configure a policy for BLI backups, configure the following:
The BLI backup method on the policy attributes dialog box. An Automatic Backup schedule to perform full and incremental file-based backups of the data files. An Application Backup schedule to back up profile and configuration files. These files are backed up during brbackup phase 2.
The following procedure describes how to configure a NetBackup for SAP policy with BLI backups. To configure a policy for BLI backups 1 2 3 4 5 6 Open the policy you want to configure. Click the Attributes tab. From the Policy Type list, choose SAP. Select a Policy storage unit. Select Perform block level incremental backups. To configure schedules, click the Schedules tab. Database profile and configuration files are backed up in brbackup phase 2. These files are backed up as a standard backup. To perform a whole
database backup, which automatically includes backing up the profile and configuration files, configure the following:

One or more automatic backup schedules to perform proxy BLI backups of the data files. An Application Backup schedule type to back up the control files and archive logs.
7 8
On the Clients tab, specify clients to be backed up with this policy. On the Backup Selections tab, specify the template or script.
Types of BLI backups

Proxy BLI backups are performed by Automatic Full Backup, Automatic Differential Incremental Backup, and Automatic Cumulative Incremental Backup schedules. NetBackup for SAP supports BLI backups only through backint. If you attempt to perform a BLI backup through RMAN proxy, the agent issues the following message:
BLIB with RMAN proxy is not a valid use case. Perform BLIB
through backint.
NetBackup for SAP checks that a full backup has been performed before proceeding with an incremental backup. If the NetBackup scheduler or user initiates an incremental backup, and NetBackup for SAP finds no record of a full backup using the same policy, it performs a full backup. To ensure that it has a proper set of images to restore, NetBackup performs a full backup when it encounters the following situations:

If NetBackup does not have a valid full backup image for the same policy in its database. This can occur, for example, if images were expired. If a new file was added to or deleted from the list of files for an incremental backup. If the number of backup streams specified has changed from the previous backup.
NetBackup for SAP always initiates a full backup under these conditions, even if you want to perform an incremental backup.
NetBackup for SAP with Snapshot Client Additional snapshot client configuration information
113
Additional snapshot client configuration information

The following sections contain the additional configuration information that you need to configure the Netbackup for SAP snapshot client. The topics in these sections include backup types, schedule properties, scripts, and environment variables.
Backup types
The backup types available on the Schedules tab of the policy play a different role for NetBackup for SAP with Snapshot Client backups. The following list explains these roles: Backup Type
Application Backup
Description
The Application Backup schedule enables user-controlled NetBackup operations from the client. This schedule type allows operations the client initiates and operations an automatic schedule initiates from the NetBackup master server. NetBackup uses the Application Backup schedule when the SAP user starts a backup manually. Configure at least one Application Backup schedule for each SAP policy. By default, an Application Backup is configured automatically. NetBackup for SAP uses the Application Backup schedule to back up the profile files that are backed up in brbackup phase 2.
Automatic Full Backup
An Automatic Full Backup schedule specifies the dates and times on which NetBackup is to start backups. Backups commence by running the SAP scripts automatically in the order they appear in the file list. If there is more than one client in the SAP policy, NetBackup for SAP runs the SAP scripts on each client. You must configure the Automatic Full Backup schedule in order for Snapshot Client methods to back up Oracle data files. In a differential incremental backup NetBackup for SAP backs up all data blocks that changed since the most recent full or incremental backup. This type of backup can be used with the Snapshot Client BLI method.
Automatic Differential Incremental Backup
114 NetBackup for SAP with Snapshot Client Additional snapshot client configuration information
Backup Type
Automatic Cumulative Incremental Backup
Description
In a cumulative incremental backup, NetBackup for SAP backs up all data blocks that changed since the most recent full backup. This type of backup can be used with the Snapshot Client BLI method or for RMAN stream-based incrementals. Cumulative incremental backups reduce the work that is needed for a restore. You only need one cumulative incremental backup from any particular level at restore time. However, cumulative backups typically require more space and time than differential incremental backups. Cumulative backups duplicate the data that was captured in previous backups at same level.
Backup scripts
NetBackup for SAP installs sample scripts in the following location:
/usr/openv/netbackup/ext/db_ext/sap/samples/sap_oracle
You can use some of the sample scripts as they are, or with a little modification, you can use them to perform snapshot backups. The scripts are as follows:

sap_online_backup. This script sets environment variables and calls brbackup with the appropriate options to perform online backups of the Oracle database through backint. sap_rman_backup. By default, this script performs offline backups of the Oracle database through RMAN. You can use this script to perform online snapshot backups of Oracle through RMAN proxy. Change the brbackup commands in this script to read as follows:
if [ $SAP_FULL -eq 1 ]; then

CMD_LINE="$SAP_ENV brbackup -d rman_util -t online -m full -c"
elif [ $SAP_CINC -eq 1 ]; then
CMD_LINE="$SAP_ENV brbackup -d rman_util -t online -m incr -c"
fi
The following section explains how to configure RMAN to perform proxy backups.
Additional configuration that is required for brbackup using RMAN proxy

If you want to perform backups by using brbackup through RMAN proxy, add following lines in the initSID.sap file:
rman_proxy = yes rman_send = "'NB_ORA_PC_SCHED=auto_sched_name'"
NetBackup for SAP with Snapshot Client Additional snapshot client configuration information
115
Intermixing RMAN stream and RMAN proxy backups

You can intermix the split-mirror full backups that use RMAN proxy with the standard incremental backups that use RMAN stream methods. Use RMAN proxy file-based backups for weekly full backups using snapshot methods. Use RMAN stream-based incremental backups for daily backups. To intermix backup methods, perform the following additional configuration procedure. To configure an intermixed split-mirror backup method 1 2 Copy initSID.sap to the init_fullSID.sap and initI_incrSID.sap files. Edit the init_fullSID.sap and initI_incrSID.sap files as follows:

Specify the rman_parms parameter. Set the NB_ORA_SAP environment variable to the initSID.utl path.
In the init_fullSID.sap file.

Enable the rman_proxy flag. Set the following, where auto_sched is the name of the automatic schedule:
rman_send = "'NB_ORA_PC_SCHED=auto_sched'"
4 5
if [ then elif then
Copy following sample script to a different location on your client: Open the script using your favorite editor and modify the if..elif..fi condition as follows:
/usr/openv/netbackup/ext/db_ext/sap/samples/sap_oracle/sap_rman_backup
$SAP_FULL -eq 1 ]
CMD_LINE="$SAP_ENV brbackup -d rman_util -t offline -p initFullSID.sap -m full -c"
[ $SAP_CINC -eq 1 ]
CMD_LINE="$SAP_ENV brbackup -d rman_util -t offline -p initIncrSID.sap -m incr -c"
Specify the script from step 4 on page 115 in the backup selection of your NetBackup for SAP policy
Performing user-directed backups

For scheduled backups, the Netbackup scheduler automatically exports or sets all the environment variables and system settings necessary to run the backups. However, if a user wants to initiate backups, certain environment variables need to be set. A user can initiate a backup in one of the following ways:

By running the brbackup command from the command line. By running a script that contains the brbackup command.
116 NetBackup for SAP with Snapshot Client Additional configuration required for Network Attached Storage (NAS)
If you want to enable user-initiated backups, set the following in your environment:

Set the following environment variable: SAP_SNC_SCHED=schedule_name_of_backup_type_to_perform

Set the schedule parameter in the initSID.utl file to Application Backup schedule. Netbackup for SAP uses this schedule for backing up control files, configuration files, and archive redo log files. Additionally, if you plan to run the sap_rman_backup script from the command line, export the following before you run the script: SAP_FULL = 1 (for performing full backups) SAP_CINC = 1 (for performing cumulative incremental backups)
Additional configuration required for Network Attached Storage (NAS)

BACKINT backups with NAS
Keep all database datafiles, online redo logs and all copies of control files on the NAS. Other database files including Oracle executables, configuration files (e.g. SAPBACKUP directory, initCER.utl) and the archive redo logs should be under the local file system.
Online backups
Use the BR_CNTRL_DIR environment variable to define the control file location for brbackup. The control file should be located on the NAS. (By default brbackup makes a copy of the control file in the SAPBACKUP directory, which is on the local file system. brbackup then provides that copy for backup).
Example
bash# export BR_CNTRL_DIR=/oracle/CER/cntrl_loc
Where /oracle/CER/cntrl_loc should be on the NAS. It should not be located where the actual control file resides.
Offline backups
No special configuration is required.
NetBackup for SAP with Snapshot Client Additional configuration required for Network Attached Storage (NAS)
117
RMAN proxy backups with NAS

Keep all database datafiles on the NAS. Other database files should be located on the local file system. (These files include the online redo logs, control files, archive redo logs, Oracle executables, and the configuration files.) No special configuration is required for either online or offline backups.
118 NetBackup for SAP with Snapshot Client Additional configuration required for Network Attached Storage (NAS)
Chapter


Configuration on page 119 Creating a backup medium on page 120 Using NetBackup for SAP on a MaxDB database to perform backups and restores on page 121
This chapter describes how to use NetBackup for SAP and describes the differences between using an Oracle versus a MaxDB database with NetBackup for SAP. For more information about MaxDB databases, see your MaxDB documentation. Note: NetBackup documentation uses the terms media or medium to refer to removable media tape and optical disk cartridges in a storage unit. NetBackup writes a backup file to a storage medium. MaxDB database documentation, however, uses the term backup medium to include the named pipes and other entities needed for performing backups. This manual uses the term backup medium when referring to backing up MaxDB database files.
Configuration
To configure NetBackup for SAP in a MaxDB database environment, follow the directions in Configuration on page 39. No additional steps are required, but because Modifying the configuration files on page 54 contains information for both Oracle and MaxDB database environments, follow only the instructions in that section that pertain to MaxDB databases.
120 NetBackup for SAP on MaxDB databases Creating a backup medium
MaxDB databases require you to create a backup medium. For information on how to do this, see Creating a backup medium on page 120.
Creating a backup medium

As part of the configuration process, also create at least one backup medium. Do
this before you perform any backups.
MaxDB databases require at least one backup medium before a backup or restore
can be performed. This section shows how to create a backup medium by
entering commands.
To create a backup medium
Use the DBM CLI interface and enter the following commands:
OS_prompt% dbmcli -d database_name -u usr,passwd

dbmcli> medium_put medium_name medium_path PIPE backup_type
where
database_name Name of the SAP database usr passwd medium_name MaxDB user name. MaxDB password. Name of the backup medium. The first 4 characters must be BACK. The medium_name must be in format BACKname. For example, BACKData. Full path to the named pipe. For example, /export/home/medium1.
Specify one of the following:

medium_path
backup_type
DATA for a full data backup PAGES for an incremental data backup LOG for a log backup
NetBackup for SAP on MaxDB databases Using NetBackup for SAP on a MaxDB database to perform backups and restores
121
Using NetBackup for SAP on a MaxDB database to perform backups and restores
The NetBackup for SAP on a MaxDB database does not include the SAP backup and restore tools. You can initiate backup and restore operations through the MaxDB administrative interface when you invoke one of the following interfaces:

DBM GUI DBM CLI Web DBM
For example, when you issue a backup command using the MaxDB administrative interface through the DBM CLI, the following occurs: 1 2 3 4 The DBM CLI communicates with the MaxDB server, which creates one or more named pipes. The MaxDB server streams the data from the MaxDB instance to the named pipes. The MaxDB server calls NetBackup for SAP with a list of named pipes. NetBackup for SAP reads named pipes and sends data to NetBackup.
In the case of a restore, the process is the same except that data goes the other way.
Performing a backup
The following procedure shows how to perform a backup. To perform a backup 1 2 3 Make sure that you have modified the proper configuration files and created a backup medium. Type the following command to start a utility session: dbmcli> util_connect
Type the following command to initiate the backup: dbmcli> backup_start medium_name backup_type
where:
medium_name backup_type Name of the backup medium. Specify either DATA, PAGES, or LOG.
122 NetBackup for SAP on MaxDB databases Using NetBackup for SAP on a MaxDB database to perform backups and restores
Performing a query
Prior to performing a restore, use the following procedure to query backup information and to obtain a listing of backup information. This information is needed for a restore. To perform a query

Type the following commands to obtain the backup identifier:
dbmcli> backup_ext_ids_get medium_name database_name server

dbmcli> backup_ext_ids_list
where:
medium_name database_name server Name of the backup medium. Name of the SAP database. Name of the server that hosts the MaxDB database.
To perform a restore 1 2 Use the procedure in To perform a query on page 122 to obtain the external backup identification information. Type the following command to initiate the restore: where:
medium_name backup_type BID Name of the backup medium.
Specify either DATA, PAGES, or LOG.
The backup identifier. This information is returned when you
perform a query.
dbmcli> recover_start medium_name backup_type ExternalBackupId "BID"
Performing backups and restores using parallel medium groups

Note: Parallel backups are optional only for data backups. Parallel backups and restores are used to improve backup and restore performance.

You can combine individual backup mediums to form parallel mediums. Parallel mediums allow you to implement multiplexing. When parallel
NetBackup for SAP on MaxDB databases Using NetBackup for SAP on a MaxDB database to perform backups and restores
123
mediums are used for backup, the MaxDB database passes two or more named pipes to NetBackup for SAP. NetBackup for SAP starts as many backup streams as there are named pipes. It processes each named pipe independently from the rest of the named pipes in the backup job.

Even if a backup is done in parallel, you can perform a restore of that data in either parallel or sequential mode. In other words, parallel backups do not require parallel restores. When the MaxDB database requests a parallel restore by listing multiple named pipes in an input file, NetBackup for SAP processes each pipe independently from the rest of the named pipes. Note that the MaxDB database requires that the number of media in a group of parallel media equal the number of media used during backup.
124 NetBackup for SAP on MaxDB databases Using NetBackup for SAP on a MaxDB database to perform backups and restores
Chapter
Troubleshooting

Setting the debug level on page 125 NetBackup reports on page 125 sapdba logs and messages (Oracle-based SAP environments only) on page 127 Minimizing timeout failures on large database restores on page 129
This chapter explains the processes and resources that can help you troubleshoot NetBackup for SAP. These resources include the logs and reports that NetBackup, NetBackup for SAP, and the SAP tools provide. These reports are useful for finding errors associated with those applications.
Setting the debug level

You can control the amount of information written to the debugging logs in the /usr/openv/netbackup/logs/ directories by changing the debug level. Typically, the default value of 0 is sufficient. However, Technical Support might ask you to set the value higher when a problem is being analyzed. You can set a debug level to a value ranging from 0 to 5. A level of 5 provides the most detail. To enable detailed logging

Enable detailed logging by entering the following line in the bp.conf file:
VERBOSE = 5
NetBackup reports
The NetBackup server and client software allow you to enable detailed debugging logs. The information in these log files can help you troubleshoot problems that occur outside of either the database agent or the SAP tools.
126 Troubleshooting NetBackup reports
Note the following with regard to these logs:

These logs do not reveal errors that occur when SAP tools is running unless those errors also affect NetBackup. SAP might (or might not) write to the NetBackup logs for errors in the application. Your best sources for SAP error information are the logs provided by SAP. Generally, each debug log corresponds to a NetBackup process and executable.
For information about the debugging log files, see the NetBackup Troubleshooting Guide and the /usr/openv/netbackup/logs/README.debug file.
Enabling logging
To enable the database agent logs
1 Create the following directories on the client:
/usr/openv/netbackup/logs/bpbackup
/usr/openv/netbackup/logs/bpbkar
/usr/openv/netbackup/logs/bphdb
/usr/openv/netbackup/logs/bprestore
/usr/openv/netbackup/logs/tar
/usr/openv/netbackup/logs/backint
For example:
cd /usr/openv/netbackup/logs
mkdir bphdb
(Conditional) If you are running NetBackup for SAP on Oracle with RMAN, create the following additional directory:
/usr/openv/netbackup/logs/dbclient
Set the access permissions to 777 on these log directories. For example:
chmod 777 bphdb
Enable logging for the nbpem, nbjm, and nbrb scheduling processes, which use unified logging. NetBackup writes unified logs to /usr/openv/logs. You do not need to create log directories for processes that use unified logging. For information on using logs and reports, see the NetBackup Troubleshooting Guide.
Accessing the log files

The following sections describe the logs created when you create the log directories. Use a text editor to view the contents of the logs.
Troubleshooting sapdba logs and messages (Oracle-based SAP environments only)
127
bphdb directory on the client

The /usr/openv/netbackup/logs/bphdb directory contains the following types of logs: sap_stdout.mmddyy
Unless redirected elsewhere, NetBackup writes SAP script output to this file. sap_stderr.mmddyy
Unless redirected elsewhere, NetBackup writes SAP script errors to this file. mmddyy
bphdb is the NetBackup database backup binary. This log contains debugging information for the bphdb process. NetBackup for SAP uses this client process for SAP script execution. It is invoked when an automatic backup schedule is run.
backint directory on the client

The /usr/openv/netbackup/logs/backint directory contains the following execution log: mmddyy
This log contains debugging information and execution status for the SAP NetBackup client processes linked to the library program provided with NetBackup for SAP.
NetBackup server reports

NetBackup provides other reports that are useful in isolating problems. One such report is All Logs Entries on the server. For information on server reports, see the NetBackup Administrators Guide.
sapdba logs and messages (Oracle-based SAP environments only)

The SAP tools log provides information on SAP operations. You can check the log files to determine the ultimate success or failure of database backups and restores. You can view the backup and restore logs in the following ways:

Through the following sapdba menu options: Show>Cleanup and Show log files>profiles.
128 Troubleshooting sapdba logs and messages (Oracle-based SAP environments only)
In the directories for brbackup and brrestore log information and brarchive log information.
Backup and restore log files

The following directory contains log files for different types of backups and restores: $SAPDATA_HOME/sapbackup
The files in this directory are named according to the following pattern:

The summary log file is named backSID.log, where SID is the unique name for the Oracle database instance. The detail log files are named encoded_timestamp.xyz, where:
encoded_timestamp A timestamp used in each detail log name that guarantees a unique file name. xyz for backup logs: x y z xyz for restore logs: xyz xyz xyz rsb represents restore backup files. rsa represents restore archive files. rsf represents restore individual files. a represents all. p represents partial. n represents online. f represents offline. f represents utility_file_backup
Archive log files

The following directory contains log files for different types of archive activities: $SAPDATA_HOME/saparch
The files in this directory are named according to a pattern. The encoded_timestamp is a timestamp used in each detail log name that guarantees a unique file name. The file suffixes differentiate the different types of archive logs, as follows: File name
encoded_timestamp.sve encoded_timestamp.svd
Meaning
Original saved. Original saved and deleted.
Troubleshooting Minimizing timeout failures on large database restores
129
File name
encoded_timestamp.cpy encoded_timestamp.cpd encoded_timestamp.dcp encoded_timestamp.dsv
Meaning
Original copied/saved a second time. Original copied/saved a second time and deleted. Deleted that were saved twice. Deleted that were saved.
Minimizing timeout failures on large database restores

Large database restores sometimes fail when multiple restore sessions compete for resources. In this situation, a restore session can be delayed while waiting for media or device access. If the delay is too long, the restore session times out. Use the following procedures to minimize session timeouts and to allow the restores to complete successfully. To minimize database session timeouts 1 2 In the NetBackup administration console, expand NetBackup Management > Host Properties > Clients Set the Client read timeout property to a large value. The default for the Client read timeout setting is 300 seconds (5 minutes). For database agent clients, increase the value significantly from the value recommended in the NetBackup Administrators Guide, Volume 1. For example, change this setting to 30-60 minutes to minimize timeout errors. Click OK for each client.
To minimize loading and unloading of tapes You can minimize excessive unloading and reloading of tapes between multistreamed backups by making changes on the NetBackup media server.

In the /usr/openv/netbackup/bp.conf file on the NetBackup media server, add the following options:

MEDIA_UNMOUNT_DELAY. MEDIA_REQUEST_DELAY. Use this variable only with non-robotic drives, such as tape stackers.
130 Troubleshooting Minimizing timeout failures on large database restores
Appendix
backint command line

The NetBackup for SAP backint interface communicates instructions from the SAP tools to NetBackup. The backint interface implements the SAP systems BC-BRI BACKINT Interface specification. Note: Symantec recommends that you use the backint command only with guidance from a technical support staff member. The backint interface performs the following functions:

The backup function. The backup function of the backint interface supports and defines the SAP brbackup and brarchive tools to NetBackup. brbackup and brarchive communicate with the backint interface through an in_file and an out_file parameter. The in_file parameter includes a list of files to be backed up or archived. The out_file parameter reports the status for each file and assigns a backup ID (BID) to each file. In the event of a partial backup, this function can identify successfully backed up files to the user. The restore function. The restore function of the backint interface supports and defines the brrestore tool to NetBackup. It communicates with the backint interface through the in_file parameter and out_file parameter. The in_file parameter includes a list of files to be restored through NetBackup. It also includes the BID assigned during the backup function. The out_file parameter contains the status of the restore for each file. When the NetBackup restore operation is complete, the restore function lists successfully restored files. It also lists BIDs used during the operation. The BID is assigned by NetBackup during the backup function. It can identify one or more backup runs, a single file backup, or a group of files. During a backup function, the BID is submitted to the out_file parameter. During the restore and inquiry functions, the BID can only be set in the in_file parameter.
132
If the BID is not set, the restore function uses the BID of the last backup. As an option, this function can also include a list of directories into which files will be restored.

The inquiry function. The inquiry function supports and defines the sapdba tool to NetBackup. sapdba uses the in_file parameter and the out_file parameter to collect backup information. The in_file parameter contains optional BIDs and file names. If only a #NULL is received on the in_file parameter, a list of BIDs is generated to the out_file parameter. If a BID is received, a list of files belonging to the BID is generated. If a file name is entered along with the #NULL, a list of BIDs containing that file is listed.
The backint command line uses the following syntax:

backint -u user_id -f function [-t type] -p par_file [-i in_file] [-o out_file]
The following list shows the backint command options. As noted in this list, some options are required and others are optional. Option
-u user_id
Arguments and purpose

Required. UID for backup utility user. No default.
-f function Required. It defines a key value that performs different functions between SAP and NetBackup. Specify one of the following arguments:

backup - This argument supports and defines brbackup and brarchive to NetBackup. If backup is specified, NetBackup backs up SAP. restore - This argument supports and defines brrestore to NetBackup. If restore is specified, NetBackup restores SAP. inquiry - This argument supports and defines sapdba to NetBackup. sapdba uses this argument when a recovery is performed to get backup information for NetBackup.
-t type
Optional. It defines the backup type, the backup of individual files, and character special devices. If no type is specified, the default value of file is used. Specify one of the following arguments:

file - Defines when to perform a backup, restore, and inquiry function with data files and special character devices. Backups from directories are not supported. Default. file_online - Allows brbackup to set tablespace into #BEGIN/#END backup mode when a related file backup takes place. It is used for online backups only. The architecture is based on three control files defined in the -p par_file parameter.
133
Option
Arguments and purpose
-p par_file Required. It is a text file that contains comments, parameters (required and optional), and parameter values. These parameters determine the backup and restore procedure between NetBackup and the SAP tools. The following list explains the components of par_file:

A pound character (#) in column one denotes a comment. Any other character in column one is considered valid. All required parameters must be specified with a valid value before the NetBackup for SAP backint interface can execute correctly. You can comment out an optional parameter by placing a # in column one. If optional parameters are specified, they must have valid values for the NetBackup for SAP backint interface to run correctly. If an invalid parameter name is found, the NetBackup for SAP backint interface reports a warning message and continues.
The SAP tools parameter file specifies the location of this par_file. For an example file, see the following: /usr/openv/netbackup/ext/db_ext/sap/scripts/initSAP.utl
For information on input file contents, see Parameters used in initSID.utl on page 143. -i in_file Optional. Specifies a text file, the contents of which can vary, depending on the NetBackup for SAP backint interface function initiated. If this option is not specified, the content of this file is data from standard input. For information on input file contents, refer to backint -i in_file contents on page 135.
-o out_file Optional. Specifies a text file that contains process messages for a function. If this option is not specified, the output is written to standard output. For information on output file contents, refer to backint -o out_file contents on page 137.
134
Appendix
backint -i in_file contents

This appendix explains how to create a backint input file. You specify the name of this input file as the argument to the backint commands -i in_file option. The input file consists of one or more directive lines that specify how to perform a backup, restore, or inquiry. The input file format differs depending on the function you want backint to initiate and on the underlying database. The following table shows the directives you can include in in_file and indicates the databases that use them. Directive
Directives for an input file that requests a backup: file pipe #PIPE special_file size Directives for an input file that requests a restore: backup_id file [dest_dir] #NULL file [dest_dir] backup_id pipe [dest_name] #NULL pipe [dest_name] Directives for an input file that performs an inquiry: #NULL backup_id #NULL file #NULL pipe Oracle and MaxDB Oracle and MaxDB Oracle MaxDB Oracle Oracle MaxDB MaxDB Oracle MaxDB Oracle
Underlying database
136
Directive
backup_id file backup_id pipe
Underlying database
Oracle MaxDB
Specify the following for the variables in the in_file: Variable

file
Specification
The full path name of the file that you are backing up, restoring, or inquiring about. A named pipe. Specify the keyword #PIPE after the pipe name. The name of a special file, such as a raw device file. The file size as specified to the Oracle database. The BID, or backup identifier, as generated by NetBackup. The name of a directory or folder to which the restore is written. The name of a pipe to which the restore is written.
pipe special_file size backup_id dest_dir dest_name
If you use the #NULL keyword, backint uses the most recent version of the file or pipe.
Appendix
backint -o out_file contents

This appendix contains the following topics:

Information returned for a backup on page 137 Information returned for a restore on page 137 Information returned for an inquiry on page 138
When the backint command finishes, it writes an output file to the file specified by the -o out_file option on its command line. The contents of the output text file change depending on the function backint performed. This appendix explains the backint output returned from a backup, restore, or inquiry request.
Information returned for a backup

If a backup completes successfully, the output file includes the following:

The backup ID (BID) assigned to the backup by NetBackup. The files, pipes, directories, or folders backed up and their sizes.
If a backup function fails, the output file lists the files or pipes that it could not back up.
Information returned for a restore

If a restore completes successfully, the output file entry includes the following:

The BID. The files or pipes restored.
138 Information returned for an inquiry
If a restore function fails, the output file lists the files and pipes not found. It also lists the files and pipes that were not successfully restored.
Information returned for an inquiry

If an inquiry completes successfully, the output file entry includes the following:

The BID. The files or pipes backed up.
Appendix
Environment variables
The NetBackup for SAP backint interface recognizes the following environment variables: Environment variable Purpose
$SAP_CLIENT Sets the name of the NetBackup client. It can be used to override the current client and perform an alternate restore to a different client. This variable is the same as the client parameter in the initSID.utl file and the CLIENT_NAME option in the NetBackup bp.conf file. Sets the number of simultaneous bpbackup/bprestore operations the NetBackup for SAP backint interface can execute. This environment variable is the same as the drives parameter in the initSID.utl file. Sets the name of the NetBackup policy. You can use this policy to define different types of database backups. You can use one policy type to perform offline database backups and another policy type to perform archive log backups. This environment variable is the same as the policy parameter in the initSID.utl file and the BPBACKUP_POLICY option in the NetBackup bp.conf file. Set this environment variable to disaster while running disaster recovery using BRRECOVER. If the initDBSID.sap file is not present, BRRECOVER calls BACKINT without the -p initDBSID.utl parameter. If Netbackup for SAP is called without the util file parameter, then it expects that the SAP_RECOVERY environment variable is set to disaster. Set this environment variable to rollback to specify a snapshot rollback restore from BACKINT-based backups.
$SAP_DRIVES
$SAP_POLICY
$SAP_RECOVERY
$SAP_RESTORE
140
Environment variable Purpose

$SAP_SCHED Sets the name of the SAP backup policy schedule. This schedule provides an easy way to switch to a different schedule for each SAP database backup. This environment variable is the same as the schedule parameter in the initSID.utl file and the BPBACKUP_SCHED option in the NetBackup bp.conf file. Sets the name of the SAP backup policy schedule. This schedule is used to perform file-based snapshot and off-host backups of the datafiles in brbackup phase 1. The following types of schedules can be used for this type of backup: Automatic Full, Automatic Differential Incremental, or Automatic Cumulative Incremental. Sets the name of the NetBackup server. It can be used to override the current server and perform a backup to an alternative server. This environment variable is the same as the server parameter in the initSID.utl file and the SERVER option in the NetBackup bp.conf file.
$SAP_SNC_SCHED
$SAP_SERVER
Appendix
bp.conf file
You can specify parameters in several places. In the case of conflicts, the order of precedence is as follows: Setting
Environment variables
Precedence
Highest precedence. Overrides values in initSID.utl and in the bp.conf file. Medium precedence. Values in environment variables override values specified in this file, but values in this file override those in the bp.conf file. Lowest precedence. Values in environment variables and in initSID.utl override values specified in the bp.conf file.
initSID.util file
/usr/openv/netbackup/bp.conf file
The following list shows the variable names and definitions you can use in the bp.conf file: Variable
$SERVER
Meaning
Specifies the NetBackup server. This option is the same as the $SAP_SERVER environment variable and the server parameter in the initSID.util file. Specifies the NetBackup client. This option is the same as the $SAP_CLIENT environment variable and the client parameter in the initSID.util file. Specifies the NetBackup policy. This option is the same as the $SAP_POLICY environment variable and the policy parameter in the initSID.util file.
$CLIENT_NAME
$BPBACKUP_POLICY
142
Variable
$BPBACKUP_SCHED
Meaning
Specifies the NetBackup schedule. This option is the same as the $SAP_SCHED environment variable and the schedule parameter in the initSID.util file.
For more information on bp.conf, see the NetBackup Administrators Guide, Volume II.
Appendix
Parameters used in initSID.utl

This appendix includes the following topics:

Parameter summary on page 143 Parameters on page 145
This appendix shows the parameters you can specify in the initSID.utl configuration file. The software passes these parameters to the backint interface through its -p parfile option. Unless otherwise noted, the parameters in this appendix section apply to the following environments:

NetBackup for SAP on Oracle databases without RMAN NetBackup for SAP on Oracle databases with RMAN NetBackup for SAP on MaxDB databases
Where necessary, the parameter descriptions in this appendix indicate whether they apply to only one or two of these environments. In addition, because not all parameters are useful when restoring NetBackup for SAP 6.5 images, the parameter descriptions indicate this.
Parameter summary
The following list summarizes the parameters and the database environments that support them: Parameter name
backint_dir backup_stream_buffersize
Underlying database and usage notes

Oracle without RMAN MaxDB
144 Parameter summary
Parameter name
bplist_filter

Oracle without RMAN Oracle with RMAN MaxDB Use only to restore images backed up with a NetBackup for SAP release prior to 6.0.
client
Oracle without RMAN Oracle with RMAN MaxDB
custom_sort_file drives inquire_query_period
Oracle without RMAN Oracle without RMAN Oracle without RMAN Oracle with RMAN MaxDB
master_time_offset
media_notify_script
Use only to restore images backed up with a NetBackup for SAP release prior to 6.0. Oracle without RMAN Oracle with RMAN MaxDB
policy
policy2
restore_filter
Use only to restore images backed up with a NetBackup for SAP release prior to 6.0. MaxDB Oracle without RMAN Oracle with RMAN MaxDB
restore_stream_buffersize retry_backup
145 Parameters
Parameter name
schedule

schedule2
server
sleep
Use only to restore images backed up with a NetBackup for SAP release prior to 6.0. Oracle without RMAN Oracle without RMAN Use only to restore images backed up with a NetBackup for SAP release prior to 6.0.
sort_backup_type sort_restore_type
switch_list switch_log switch_sem
Oracle without RMAN Oracle without RMAN Oracle without RMAN
Parameters
The following sections describe the individual parameters.
backint_dir work_directory
Note: Not applicable in MaxDB database environments or in Oracle database environments that use RMAN. Set this parameter only if you have old backups performed with NetBackup 3.2. It must be set to a public directory. The NetBackup for SAP backint interface uses this directory for work space. NetBackup for SAP looks for the backint.times file and searches it for previously performed backups (using NetBackup for SAP 3.2).
146 Parameters
The NetBackup for SAP 4.5 and later releases do not use the backint.times file to store information about new backups.
backup_stream_buffersize size
This parameter specifies the buffer size, in bytes, for stream-based backups. NetBackup receives data from MaxDB through the stream (pipe). When MaxDB passes the data to NetBackup, it uses this buffer size. Also see the restore_stream_buffersize parameter.
bplist_filter script_path
Note: Use this parameter only if you are restoring backup images created with a release of NetBackup for SAP prior to 6.0. This parameter resolves linked file paths on an inquire.
Use this parameter only on rare occasions. As with the restore_filter, all of
the following cases must exist before this parameter is used:
Oracle table spaces use file paths. The directory paths to the Oracle table spaces are linked paths. The linked directory paths do not exist at restore time.
The value for this option must be a fully qualified path name to a script with the
right file permission. Test the script before implementing. The following is an
example of an entry:
bplist_filter /usr/openv/netbackup/ext/db_ext/sap/scripts\
/bplist_restore_filter
The script must have an input parameter and output parameter and be able to modify the contents of a text file. The script is responsible for converting absolute directory paths into linked directory paths. This is just the opposite of restore_filter. The following is an example of this script:
#!/bin/sh # this shell is used to change some logically linked files # during a restore # /oracle/sap/sapdata/sapdata1 to /oracle/product/7.0.16/sapdata1 # /oracle/sap/sapdata/sapdata2 to /oracle/product/7.0.16/sapdata2 # /oracle/sap/sapdata/sapdata3 to /oracle/product/7.0.16/sapdata3 # /oracle/sap/sapdata/sapdata4 to /oracle/product/7.0.16/sapdata4 # /oracle/sap/sapdata/sapdata5 to /oracle/product/7.0.16/sapdata5 # /oracle/sap/sapdata/sapdata6 to /oracle/product/7.0.16/sapdata6 sed -e s/\oracle\sap\sapdata\sapdata1/\oracle\product\7.0.16\sapdata1/
147 Parameters
s/\oracle\sap\sapdata\sapdata2/\oracle\product\7.0.16\sapdata2/ s/\oracle\sap\sapdata\sapdata3/\oracle\product\7.0.16\sapdata3/ s/\oracle\sap\sapdata\sapdata4/\oracle\product\7.0.16\sapdata4/ s/\oracle\sap\sapdata\sapdata5/\oracle\product\7.0.16\sapdata5/ s/\oracle\sap\sapdata\sapdata6/\oracle\product\7.0.16\sapdata6\/ $1 > $2
client client_machine_name
This parameter specifies the machine that contains the NetBackup client software, a database, and an SAP environment. In some cases the server and client machine are the same machine. The following is an example:
client saturn
If the NetBackup for SAP backint interface finds the $SAP_CLIENT environment variable, the $SAP_CLIENT environment variable value overrides the client parameter value. If the client parameter is not specified, and there is no environment variable, then the client parameter value defaults to the specification for the CLIENT_NAME option in the NetBackup bp.conf file. If the value is not specified in the NetBackup bp.conf file, the NetBackup for SAP backint interface uses the value returned by the gethostname()library function.
custom_sort_file file_path
Note: Not applicable in MaxDB database environments or in Oracle database environments that use RMAN. Specify this parameter only when the sort_backup_type or the sort_restore_type parameters are set to custom. When custom is specified, set the custom_sort_file parameter to a valid file. The file_path value must be a full path name to a custom sort file that an end user created, and it must have public permissions. The following is an example argument to the custom_sort_file parameter:
/usr/openv/dbext/ext/db_ext/sap/scripts/sap_custom_sort_file
The custom sort file must include two fields. The first field groups a set of files into a particular bpbackup job. The second field is a file path name that maps the SAP backup file list to a group ID. The following is an example of a custom sort file:
1 1 1 1 1 /oracle/sap/sapdata1/btabd_1/btabd.data1
/oracle/sap/sapdata2/btabi_1/btabi.data1
/oracle/sap/sapdata2/clud_1/clud.data1
/oracle/sap/sapdata1/ddicd_1/ddicd.data1
/oracle/sap/sapdata5/ddici_1/ddici.data1
148 Parameters
1 1 1 1 1 1
/oracle/sap/sapdata4/el30cd_1/EL30cd.data1
/oracle/sap/sapdata1/el30ci_1/el30ci.data1
/oracle/sap/sapdata6/es30cd_1/es30cd.data1
/oracle/sap/sapdata2/poold_1/poold.data1
/oracle/sap/sapdata1/pooli_1/pooli.data1
/oracle/sap/sapdata4/protd_1/protd.data1
1 2 2 2 2 2 2 2 2 2 2 2 2 2
/dev/rdsk/c0t4d0s6
/oracle/sap/sapdata1/roll_1/roll.data1
/oracle/sap/sapdata2/sourced_1/sourced.data1
/oracle/sap/sapdata3/stabd_1/stabd.data1
/oracle/sap/sapdata2/stabi_2/stabi.data2
/oracle/sap/sapdata1/temp_1/temp.data1
/oracle/sap/sapdata4/user1d_1/user1d.data1
/oracle/sap/sapdata2/user1i_1/user1i.data1
/oracle/sap/sapdata1/system_1/system.data1
/oracle/sap/saplog1/log_g1_m1/log1_m1.dbf
/oracle/sap/dbs/cntrlSAP.dbf
Based on the preceding custom sort file, if SAP submits the entire file list to be backed up, there would be two bpbackup jobs running at the same time. The first job includes all the files that have a 1 in the first field. The second job includes all the files that have a 2 in the first field. The following is a list of jobs and associated files:
Backup and restore job 1:

/oracle/sap/sapdata1/btabd_1/btabd.data1
/dev/rdsk/c0t4d0s6

149 Parameters
drives number_of_drives
Note: Not applicable in MaxDB database environments or in Oracle database environments that use RMAN. This parameter specifies the number of bpbackup and bprestore commands to run. To maximize write performance to a storage unit, set the drives value to the number of storage units multiplied by the multiplex value per schedule. Based on the number of drives specified, the NetBackup for SAP backint interface simultaneously runs the same number of bpbackup and bprestore commands. If, for example, multiplexing is set to 4 and there are two available tape drives, set the drives parameter to 8 (4 X 2). The NetBackup for SAP backint interface runs eight bpbackup/bprestore jobs at the same time with four data streams going to each tape. The drives parameter should be set to the following rule:
drives = Number_of_drives_per_policy X MPX_value_in_schedule
The drives parameter value must not exceed the set maximum jobs per client global attribute. The following is an example entry:
drives 5
If the NetBackup for SAP backint interface finds the $SAP_DRIVES environment variable, the $SAP_DRIVES environment variable value overrides the drives parameter value. If the drives parameter is not specified and there is no environment variable, then the NetBackup for SAP backint interface exits with an error.
inquiry_query_period months
In the case of #NULL based inquiry queries, NetBackup for SAP restricts the catalog search to the last six months by default. You can use this parameter to specify a different query period. Specify an integer value for months. For example, if you want to set the query to the last 10 months, set this parameter as follows:
inquiry_query_period 10
150 Parameters
master_time_offset minutes
This parameter restores old backups if there was a time difference between the master and client machines. Use this option only in the following circumstances:

For restoring files backed up with NetBackup release 3.0 or older software. When the date and times are out of sync between the server and client machines.
The parameter value, specified in minutes, is subtracted from the start time and added to the end time for a restore or inquire. The following is an example of an entry:
master_time_offset 3
media_notify_script script_path
Note: Use this parameter only if you are restoring backup images created with a release of NetBackup for SAP prior to 6.0. This parameter calls a script when a Waiting mount is entered in a bpbackup/bprestore log. You can use this parameter to send a message that requests a tape mount to an SAP user. For script_path, specify the full path name to a script. The script must have 755 file permissions. Test the script before implementation. The following is an example entry:
media_notify_script /oracle/sap/sapscripts/sap_media_notify
If the message is encountered and this parameter is specified, then the following commands are executed from the NetBackup for SAP backint interface:
MEDIA_ID=A001;export MEDIA_ID NETBACKUP_SERVER=saturn;export NETBACKUP_SERVER
/oracle/sap/sapscripts/sap_media_notify
policy policy_name
This parameter specifies the name of an SAP policy defined in NetBackup. The SAP policy must have an Application Backup schedule defined in order for the NetBackup for SAP backint interface to work. The following is an example entry:
policy sap_nb
If the NetBackup for SAP backint interface finds the $SAP_POLICY environment variable, the $SAP_POLICY environment variable value overrides the policy parameter value. If the policy parameter is not specified, and there is no environment variable, then the policy parameter value defaults to the specification for the BPBACKUP_POLICY option in the NetBackup bp.conf
151 Parameters
file. By default, if BPBACKUP_POLICY is not specified in any NetBackup bp.conf file, NetBackup uses the first active SAP policy type it finds for the client with an Application Backup schedule.
policy2 policy_name
This parameter specifies the name of a policy to be used for the secondary SAP backup. A secondary backup is performed for each SAP database backup on files that are needed to track SAP backup information. You can use this option to save the backup information on a different media. If policy2 is not specified and schedule2 is specified, then NetBackup uses the value specified for the policy parameter.
restore_filter script_path
Note: Use this parameter only if you are restoring backup images created with a release of NetBackup for SAP prior to 6.0. This parameter resolves linked file paths on a restore.
Use this parameter only on rare occasions. The following cases must exist before
this parameter is used:
Oracle table spaces use file paths. The directory paths to the Oracle table spaces are linked paths. The linked directory paths do not exist at restore time.
The value for this parameter must be a fully qualified file path name to a script
with the right permissions. Test the script before implementation. The following
is an example of an entry:
restore_filter /usr/openv/netbackup/ext/db_ext/sap/\
scripts/sap_restore_filter
The script must have an input parameter and an output parameter. It must be able to modify the contents of a text file. The script converts linked directory paths into absolute directory paths. The following is an example of this script:
#!/bin/sh
# this shell is used to change # during a restore
# /oracle/sap/sapdata/sapdata1 # /oracle/sap/sapdata/sapdata2 # /oracle/sap/sapdata/sapdata3 # /oracle/sap/sapdata/sapdata4 # /oracle/sap/sapdata/sapdata5 # /oracle/sap/sapdata/sapdata6 sed -e
some logically linked files
to to to to to to /oracle/product/7.0.16/sapdata1
/oracle/product/7.0.16/sapdata2
152 Parameters
s/\oracle\sap\sapdata\sapdata1/\oracle\product\7.0.16\sapdata1/ s/\oracle\sap\sapdata\sapdata2/\oracle\product\7.0.16\sapdata2/ s/\oracle\sap\sapdata\sapdata3/\oracle\product\7.0.16\sapdata3/ s/\oracle\sap\sapdata\sapdata4/\oracle\product\7.0.16\sapdata4/ s/\oracle\sap\sapdata\sapdata5/\oracle\product\7.0.16\sapdata5/ s/\oracle\sap\sapdata\sapdata6/\oracle\product\7.0.16\sapdata6\/ $1 > $2
restore_stream_buffersize size
This parameter specifies the buffer size, in bytes, for stream-based restores. MaxDB receives data from NetBackup through the stream (pipe). When MaxDB receives the data from NetBackup and copies it to the pipe, it uses this buffer size. For more information, see the backup_stream_buffersize parameter.
retry_backup number_of_retries
This parameter specifies the number of retries for a failed backup. When specified, backint retries a failed bpbackup job the specified number of times. For example:
retry_backup 2
schedule schedule_name
This parameter specifies the name of an Application Backup schedule associated with an SAP policy type. The schedule can define aspects of the backup such as how long NetBackup retains images, maximum multiplexing per drive, storage unit, and volume pool. The following is an example entry:
schedule sap_full_backup
If the NetBackup for SAP backint interface finds the $SAP_SCHED environment variable, the $SAP_SCHED environment variable value overrides the schedule parameter value. If the schedule parameter is not specified and there is no environment variable, then the schedule parameter value defaults to the BPBACKUP_SCHED option in the NetBackup bp.conf file. If BPBACKUP_SCHED is not specified in the NetBackup bp.conf file, NetBackup uses the first Application Backup schedule it finds in the first active SAP policy.
schedule2 schedule_name
This parameter specifies name of an Application Backup schedule to be used for the secondary SAP backup. If it is not specified, the schedule parameter value is used. For each SAP backup, NetBackup performs two individual backups. The first backup backs up database data. The second backup backs up log files needed to track SAP backup information. You can use this parameter to save SAP log files
153 Parameters
to a different media. This can make it easier to restore a database. You can also use this option to save the backup information to a different volume pool. The following is an example entry:
schedule2 sap_backup_information
server server_name
This parameter specifies the name of the NetBackup master server. The NetBackup master server is the name of the machine that provides most of the administration and control for NetBackup operations. It contains the NetBackup database. The following is an example entry:
server jupiter
If the NetBackup for SAP backint interface finds a $SAP_SERVER environment variable, the $SAP_SERVER environment variable value overrides the server parameter value. If the server parameter is not specified, and there is no environment variable, the server parameter value defaults to the specification for the SERVER option specified in the NetBackup bp.conf file.
sleep seconds
Note: Use this parameter only if you are restoring backup images created with a release of NetBackup for SAP prior to 6.0. This parameter specifies a sleep time to monitor the bpbackup or bprestore logs. If it is not specified, NetBackup uses a default value of five seconds. When the NetBackup for SAP backint interface is called, a number of bpbackup and bprestore commands can be running at the same time. The NetBackup for SAP backint interface monitors each command and writes to the file that is specified on the -o out_file parameter. In some cases, bpbackup and bprestore information is not displayed because of the monitoring cycle. Therefore, this option is used mainly when debugging. The following is an example entry:
sleep 3
sort_backup_type value
Note: Not applicable in MaxDB database environments or in Oracle database environments that use RMAN. This parameter specifies one of four different backup sort parameter values: custom, device, drive, or size (default).
154 Parameters
The following sections describe each of these parameters.
sort_backup_type custom
Specifies that a customized sort file be used.

If sort_backup_type custom is specified, also specify the
custom_sort_file parameter with a file path. For more information, see
custom_sort_file file_path on page 147.
sort_backup_type device
Specifies that NetBackup create jobs based on a files device ID. Because this parameter overrides the drives parameter, the number of storage units specified in the intSID.utl file is not used. For example, if there are 12 files requested for backup, and they reside on two different devices (X and Y), then two jobs are forked. The first job contains all the files associated with device X, and the second job contains all the files on device Y. The following example shows how jobs are created when device is specified:

Input file list from SAP (brbackup, sapdba):

/oracle/sap/sapdata1/btabd_1/btabd.data1 /oracle/sap/sapdata2/btabi_1/btabi.data1 /oracle/sap/sapdata2/clud_1/clud.data1 /oracle/sap/sapdata1/ddicd_1/ddicd.data1 /oracle/sap/sapdata5/ddici_1/ddici.data1 /oracle/sap/sapdata4/el30cd_1/EL30cd.data1 /oracle/sap/sapdata1/el30ci_1/el30ci.data1 /oracle/sap/sapdata6/es30cd_1/es30cd.data1 /oracle/sap/sapdata2/poold_1/poold.data1 /oracle/sap/sapdata1/pooli_1/pooli.data1 /oracle/sap/sapdata4/protd_1/protd.data1
/dev/rdsk/c0t4d0s6 11812864
Backup job 1 (all have the device ID x):

/oracle/sap/sapdata1/btabd_1/btabd.data1
Backup job 2 (all have the same device ID y):

/dev/rdsk/c0t4d0s6 11812864
155 Parameters
Note: The implementation is based on the st_dev value from the stat() function. This identifies a file partition.
sort_backup_type drive
Specifies that NetBackup create jobs based on the number of simultaneous backup jobs specified by the drives parameter in the initSID.utl file. For example, if there are three tape drives and 10 SAP files, the following distribution occurs:
Input file list from SAP:




sort_backup_type size (default)
This is the default value for the sort_backup_type parameter.

If sort_backup_type size is specified, NetBackup creates jobs based upon
the number of drives specified in the initSID.utl file. Each file being backed
up is associated with a backup job based on size.
For example, if three tape drives are specified, the files are divided evenly into
three bpbackup jobs based on size. So, if there are 25 input files from SAP and
three tape drives, then three bpbackup jobs would be running at the same
time with the following files in each job:
156 Parameters
Input file list from SAP (brbackup, sapdba):

/oracle/sap/sapdata1/btabd_1/btabd.data1 /oracle/sap/sapdata2/btabi_1/btabi.data1 /oracle/sap/sapdata2/clud_1/clud.data1 /oracle/sap/sapdata1/ddicd_1/ddicd.data1 /oracle/sap/sapdata5/ddici_1/ddici.data1 /oracle/sap/sapdata4/el30cd_1/EL30cd.data1 /oracle/sap/sapdata1/el30ci_1/el30ci.data1 /oracle/sap/sapdata6/es30cd_1/es30cd.data1 /oracle/sap/sapdata2/poold_1/poold.data1 /oracle/sap/sapdata1/pooli_1/pooli.data1 /oracle/sap/sapdata4/protd_1/protd.data1 /dev/rdsk/c0t4d0s6 11812864 /oracle/sap/sapdata1/roll_1/roll.data1 /oracle/sap/sapdata2/sourced_1/sourced.data1 /oracle/sap/sapdata3/stabd_1/stabd.data1 /oracle/sap/sapdata2/stabi_2/stabi.data2 /oracle/sap/sapdata1/temp_1/temp.data1 /oracle/sap/sapdata4/user1d_1/user1d.data1 /oracle/sap/sapdata2/user1i_1/user1i.data1 /oracle/sap/sapdata1/system_1/system.data1 /oracle/sap/saplog1/log_g1_m1/log1_m1.dbf /oracle/sap/saplog1/log_g2_m1/log2_m1.dbf /oracle/sap/saplog1/log_g3_m1/log3_m1.dbf /oracle/sap/saplog1/log_g4_m1/log4_m1.dbf
Backup job 1:
/name=/oracle/sap/sapdata1/roll_1/roll.data1
name=/oracle/sap/sapdata1/temp_1/temp.data1
name=/oracle/sap/sapdata1/ddicd_1/ddicd.data1
name=/oracle/sap/sapdata1/el30ci_1/el30ci.data1
name=/oracle/sap/saplog1/log_g4_m1/log4_m1.dbf
size= 36708352: size= 10493952: size= 5251072: size= 5251072: size= 5243392: Total=62947840
file file file file file

Backup job 2:
name=/oracle/sap/sapdata1/system_1/system.data1
name=/oracle/sap/sapdata2/btabi_1/btabi.data1
name=/oracle/sap/sapdata5/ddici_1/ddici.data1
name=/oracle/sap/sapdata6/es30cd_1/es30cd.data1
name=/oracle/sap/sapdata2/poold_1/poold.data1
name=/oracle/sap/sapdata3/stabd_1/stabd.data1
name=/oracle/sap/sapdata1/pooli_1/pooli.data1
name=/oracle/sap/sapdata2/user1i_1/user1i.data1
name=/oracle/sap/dbs/cntrlSAP.dbf
size= 15736832: size= 5251072: size= 5251072: size= 5251072: size= 5251072: size= 5251072: size= 5251072: size= 5251072: size= 5243392: size= 231936: Total=57969664
file file file file file file file file file file

Backup job 3:
size= 11812864: file name=/dev/rdsk/c0t4d0s6

size= 5251072: file name=/oracle/sap/sapdata2/clud_1/clud.data
size= 5251072: file name=/oracle/sap/sapdata4/el30cd_1/EL30cd.data1
157 Parameters
size= 5251072: file size= 5251072: file size= 5251072: file size= 5251072: file size= 5251072: file size= 5243392: file size= 5243392: file Total=59057152
name=/oracle/sap/sapdata4/protd_1/protd.data1
name=/oracle/sap/sapdata2/sourced_1/sourced.data1
name=/oracle/sap/sapdata2/stabi_2/stabi.data2
name=/oracle/sap/sapdata4/user1d_1/user1d.data1
name=/oracle/sap/sapdata1/btabd_1/btabd.data1
The number of drives specified does not have to equal the number of physical storage units. The number of drives correlates to the number of simultaneous bpbackup jobs run by the NetBackup for SAP backint interface. For example, if you have 10 SAP files and three tape drives, you can specify 10 drives in the initSID.utl file. This creates 10 bpbackup jobs with one file for each bpbackup job. Netbackup handles all of the job scheduling. Initially, three bpbackup jobs are active and the other seven jobs are queued. You can increase the number of active jobs and data throughput by increasing the multiplex value for the policy.
sort_restore_type value
Note: Use this parameter only if you are restoring backup images created with a release of NetBackup for SAP prior to 6.0. Not applicable in MaxDB database environments or in Oracle database environments that use RMAN. This parameter specifies one of three different restore sort options: custom,
drive, or image (default).
The following sections describe the possible parameter values.
sort_restore_type custom
Specifies that a customized sort file be used.

If sort_restore_type custom is specified, also specify the
custom_sort_file parameter with a file path. For more information, see
custom_sort_file file_path on page 147.
sort_restore_type drive
Specifies that NetBackup create jobs based on the number of storage units specified in the drives parameter in the initSID.utl file. For example, if there are three tape drives and 10 SAP files, the following distribution occurs:
158 Parameters
Input file list from SAP:




sort_restore_type image (default)
Specifies that backint create groups of files based on their backup image
numbers and fork a bprestore for each group. This is the default behavior
used if the sort_restore_type parameter is not set in the intSID.utl file.
For example, if nine files were backed up by two bpbackup jobs, each file is
associated with one of two backup image IDs. If all nine files are restored, then
there are two bprestore jobs forked by the NetBackup for SAP backint
interface, one job for each image. The files are grouped the way they were
backed up. The following is an example of a restore.
Input file list from SAP (brrestore, sapdba):
Image 1:
Image 2:
Restore job 1:
159 Parameters
Restore job 2:
Note: Restore forks another job for raw partition files if they are grouped with regular files.
switch_list control_file_path
Note: Not applicable in MaxDB database environments or in Oracle database environments that use RMAN. This parameter specifies a control file that communicates between the NetBackup for SAP backint interface and brbackup for online backups. A switch list file is created every time brbackup wants to back up a file or when it wants to indicate that a backup is finished. The switch_list parameter must specify a file path in the following location: $SAPDATA_HOME/sapbackup/.switch.lis The following is an example of a valid entry: switch_list /oracle/sap/sapbackup/.switch.lis
switch_log control_file_path
Note: Not applicable in MaxDB database environments or in Oracle database environments that use RMAN. This parameter specifies a control file that communicates between the NetBackup for SAP backint interface and brbackup. After the switch semaphore file has been deleted, the NetBackup for SAP backint interface opens and reads the switch log file, created by brbackup, to determine if the process is successful. The switch_log parameter must specify a file path in the following location: $SAPDATA_HOME/sapbackup/.switch.log
160 Parameters
The following is an example of a valid entry: switch_list /oracle/sap/sapbackup/.switch.log
switch_sem control_file_path
Note: Not applicable in MaxDB database environments or in Oracle database environments that use RMAN. This parameter specifies a control file that communicates between the NetBackup for SAP backint interface and brbackup. After the switch list file has been created and closed, the NetBackup for SAP backint interface creates the switch semaphore file and waits until it is deleted by brbackup. The switch_sem parameter must specify a file path in the following location: $SAPDATA_HOME/sapbackup/.switch.sem The following is an example of a valid entry: switch_list /oracle/sap/sapbackup/.switch.sem
Appendix
Using NetBackup for SAP to back up SAPDB


Creating backup environment configuration files on page 162 Defining a backup medium in SAPDB on page 165 Performing a backup on page 165 Performing a restore on page 166
You can use NetBackup for SAP to back up the SAPDB RDBMS. SAPDB relies on an additional adapter program to communicate with NetBackup for SAP. The adapter program is part of the SAPDB distribution. To back up the SAPDB RDBMS, perform the additional configuration tasks that this appendix describes. Follow the NetBackup for SAP directions in Configuration on page 39 to create a policy for SAPDB backups, and then follow the directions in this appendix to perform the extra configuration steps. Note: As of NetBackup for SAP release 6.0, Symantec does not recommend using the information in this appendix to create backups. Use the newer procedures for backing up and restoring database files that are described in the main sections of this manual. However, if you have backups that were created with a NetBackup for SAP software release prior to 6.0, follow the procedure in Performing a restore on page 166 to restore those files.
162 Creating backup environment configuration files
Creating backup environment configuration files
In order to configure the backup environment to use NetBackup for SAP to back up SAPDB, you create the following files on the NetBackup for SAP (SAPDB) client:

The backint for SAPDB configuration file. The adapter program configuration file. The NetBackup for SAP configuration file, initSID.utl.
backint for SAPDB configuration file

The backint for SAPDB configuration file provides information about the adapter program to SAPDB. Set the BSI_ENV environment variable to point to the name and location of this file. The configuration file can contain the following parameters: Parameter
BACKINT absolute_path/file_name
Description
Absolute path and name of the backint program. Absolute path and name of the standard input file. Absolute path and name of the standard output file. Absolute path and name of the standard error output file. Absolute path and name of the configuration file of the backint for SAPDB program. Time, in seconds, that the database manager waits for the end of a started backint for SAPDB process if the action is successful. Optional. Time, in seconds, that the database manager waits for the end of a started backint for SAPDB process if errors occur. Optional. Absolute path to the run directory of the source database. Optional.
INPUT absolute_path/file_name
OUTPUT absolute_path/file_name
ERROROUTPUT absolute_path/file_name
PARAMETERFILE absolute_path/file_name
TIMEOUT_SUCCESS number
TIMEOUT_FAILURE number
ORIGINAL_RUNDIRECTORY absolute_path
For a detailed description of these parameters, see the SAPDB documentation,

available on www.sapdb.org.
The following is an example of a backint for SAPDB configuration file with the
minimum configuration specified:
BACKINT /export/home/sapdb/depend/bin/backint
INPUT /export/home/sapdb/logs/backint.in
OUTPUT /export/home/sapdb/logs/backint.out
ERROROUTPUT /export/home/sapdb/logs/backint.err
PARAMETERFILE /export/home/sapdb/indep_data/wrk/adapter.config
The PARAMETERFILE specifies the name and location of the adapter program configuration file described in Adapter program configuration file on page 163.
Adapter program configuration file

The configuration file for the adapter program specifies to the adapter program the location of the NetBackup for SAP (backint for Oracle) software. It also specifies parameters to use when communicating with NetBackup for SAP. Specify the name and location of the adapter program configuration file as the argument to PARAMETERFILE in the backint for SAPDB configuration file. For information on the SAPDB configuration file, see backint for SAPDB configuration file on page 162. You can include the following parameters in the adapter program file: Parameter Description
STAGING AREA: absolute_path/file_name size [KB|MB|GB] Absolute path and size of a temporary file. FILES PER BACKINT CALL: number Maximum number of temporary files that are to be processed by backint for Oracle concurrently. Optional. Absolute path and name of the backint for Oracle program.
BACKINT: absolute_path/file_name
Parameter
PARAMETERFILE OF BACKINT: absolute_path/file_name
Description
Absolute path and name of the configuration file for the backint for Oracle program. Absolute path and name of the backup history file. Absolute path and name of the standard input file. Absolute path and name of the standard output file. Absolute path and name of the standard error output file. Maximum waiting time, in seconds, between creating a temporary file and starting to save it by using backint for Oracle. Optional. Specifies whether the SAPDB adapter program ignores the closing slash (/) of an absolute directory name for backint for Oracle. Optional. Value of the BI_CALLER environment variable. Optional.
HISTORY FILE: absolute_path/file_name
INPUTFILE FOR BACKINT: absolute_path/file_name
OUTPUT FILE FOR BACKINT: absolute_path/file_name
ERRORFILE FOR BACKINT: absolute_path/file_name
MAXIMAL DELAY OF BACKINT CALL: number
OMIT LAST DIRECTORY DELIMITER ON RESTORE: YES | NO
BI_CALLER_VALUE: value
For a detailed description of these parameters, see the SAPDB documentation, at

www.sapdb.org.
The following is an example of a file with the minimum configuration specified:
165 Defining a backup medium in SAPDB
BACKINT: /usr/openv/netbackup/bin/backint
PARAMETERFILE OF BACKINT: /export/home/sapdb/data/wrk/initSID.utl
HISTORY FILE: /export/home/sapdb/logs/BackintHistory
INPUTFILE FOR BACKINT: /export/home/sapdb/logs/backintOracle.in
OUTPUTFILE FOR BACKINT: /export/home/sapdb/logs/backintOracle.out
ERRORFILE FOR BACKINT: /export/home/sapdb/logs/backintOracle.err
NetBackup for SAP configuration file, initSID.utl

The initSID.utl file includes the NetBackup for SAP parameters. This file is the NetBackup for SAP configuration file, and it is named on the argument to the PARAMETERFILE OF BACKINT parameter, described in Adapter program configuration file on page 163. For more information, see Modifying the initSID.utl file on page 55.
Defining a backup medium in SAPDB

Prior to running a backup, create at least one backup medium per backup type (complete, incremental) in SAPDB. When using backint for Oracle, the name of the backup medium created must begin with BACK. The type of backup medium must be PIPE. To create a backup medium 1 Enter command mode.
For example:
dbmcli -d MYSAP -u dbm,dbm
Create the backup medium.
For example:
dbmcli on MYSAP>medium_put BACKORA /home/sapdb/medium PIPE DATA 0 8
Performing a backup
When backing up SAPDB, include the backup medium you created. The example in Defining a backup medium in SAPDB on page 165 created a backup medium called BACKORA. The example in this section uses that sample backup medium. To run a backup 1 Initiate a utility session.
For example:
dbmcli on MYSAP>util_connect
Initiate the backup.
166 Performing a restore
For example: dbmcli on MYSAP>backup_start BACKORA DATA

You can also start the backup from the DBM GUI. For more information about the DBM GUI and configuring external backup tools, refer to the SAPDB documentation at www.sapdb.org.
Use the following procedure to restore files. To perform a restore
Enter the following commands:

dbmcli> OK
dbmcli> OK
END
list of dbmcli> backup_ext_ids_get BACK
backup_ext_ids_list
EBIDS
recover_start BACKORA ExternalBackupId "EBID"
where EBID is the backup identifier. This information is returned in the

list of EBIDS when you perform a query.
Appendix
Configuring split mirror backups

This appendix includes the following topics:

Local-host snapshot method: nbu_snap (Solaris SPARC platform only) on page 167 Local-host snapshot method: VxVM (Solaris SPARC, HP-UX, Windows 2000/2003) on page 169 Local-host snapshot method: VxFS_Checkpoint on page 170 Offhost alternate client: flashsnap method on page 170 Offhost alternate client: VVR method (Solaris SPARC, HP-UX) on page 172 Hardware array-based snapshot method: Hitachi Shadow Image, EMC TimeFinder, HP Business Copy on page 175
This appendix describes how to configure split mirror backups by using NetBackup for SAP. Some of the configuration methods are platform-specific.
Local-host snapshot method: nbu_snap (Solaris SPARC platform only)

The following sections describe requirements and configuration methods.
Requirements
On the production database host, install NetBackup Client, NetBackup Snapshot Client, and NetBackup for SAP.
168 Local-host snapshot method: nbu_snap (Solaris SPARC platform only)
Configuration
The nbu_snap snapshot method is for Solaris (SPARC) clients only. It is for making copy-on-write snapshots for SAP Oracle databases that reside in UFS or Veritas file systems (VxFS). For the nbu_snap methods, you must identify a cache device to be used by the copy-on-write process. The cache device is a raw disk partition, either a logical volume or physical disk. It stores the portions of the clients data that the incoming write requests change while the copy-on-write is in progress. Depending on how the policy is configured, you can identify a cache device in several ways. For example, you can specify the raw partition when using the Snapshot policy Configuration wizard to create an Snapshot Client policy. If you manually select the snapshot method on the Advanced Snapshot Options dialog box, you have the following options for specifying the raw cache partition:

Use Host Properties > Clients > Client Properties dialog box > UNIX Client > Client Settings to specify the raw partition in the default cache device path for snapshots field. This setting applies to the client in all policies. In the Advanced Snapshot Options dialog box, specify the cache device path value field. This cache setting applies to all clients in the current policy and overrides the cache setting in the client settings dialog box.
For the cache device, do not select an active partition containing valuable data. Any data in that partition is lost when the snapshot is complete. Specify the raw partition as the full path name of either the character special device file or the block device file. For example:

Solaris (SPARC) raw partition: /dev/rdsk/c2t0d3s3 Or

/dev/dsk/c2t0d3s3
VxVM volume: /dev/vx/rdsk/diskgroup_1/volume_3 or

/dev/vx/dsk/diskgroup_1/volume_3
Note: Do not specify wildcards (such as /dev/rdsk/c2*) as paths. The cache partition must be unmounted and must reside on the same host as the snapshot source (the clients data to back up). The partition must have enough space to hold all the writes to the partition that can occur during the backup. Note that backups during off-peak periods normally require a smaller cache than a backup during peak activity. For more information, see the NetBackup 6.0 Snapshot Client System Administrators Guide.
169 Local-host snapshot method: VxVM (Solaris SPARC, HP-UX, Windows 2000/2003)
Local-host snapshot method: VxVM (Solaris SPARC, HP-UX, Windows 2000/2003)

The following sections describe requirements and configuration methods.
Requirements
Install and configure the following on the production database host:

Install NetBackup Client, NetBackup Snapshot Client, and NetBackup for SAP agent Configure the production database (Oracle) You can install NetBackup master server on a separate host
Configuration
Use the following procedure to configure. To configure the local host snapshot method 1 Attach the external disk D1 to the primary client (production database host) and create a VM disk group using the following command: Create a volume in primary disk D using the following command: Add a DCO log to the volume using the following command: Enable FastResync on the volume using the following command: Create a VxFS file system on this volume and mount it using the following commands:
root@primary# vxdg init diskgroup [cds=on|off] diskname=devicename
2 3 4 5
root@primary# vxassist -g diskgroup make volume size
root@primary# vxassist -g diskgroup addlog volume logtype=dco
root@primary# vxvol -g diskgroup set fastresync=on volume
root@primary# mkfs -F vxfs /dev/vx/rdsk/diskgroup/volume

root@primary# mount -F vxfs /dev/vx/dsk/diskgroup/volume mnt
6 7
Create the SAP production database on this volume. Start the snapshot for the data volume in the primary client using the following command:
root@primary# vxassist -g diskgroup -b snapstart volume
170 Local-host snapshot method: VxFS_Checkpoint
Local-host snapshot method: VxFS_Checkpoint
The requirements on the production host listed in configuring BLI backup section apply for the VxFS_Checkpoint method. See Configuring block-level incremental backups on page 107. Configure the Oracle database in the Veritas File System (VxFS) in the production host.
Offhost alternate client: flashsnap method

Figure H-1 on page 170 shows a typical configuration. Figure H-1 Typical SAP split mirror offhost backup using flashsnap
Alternate client offhost
Production database host
Snapshot
Automatic tape changer
Oracle database Primary disk
Mirror disk
Backup media
Requirements

Install NetBackup Client, NetBackup Snapshot Client, and the NetBackup for SAP agent Configure the production database (Oracle) You can install the NetBackup master server on a separate host
Install the following on the alternate client (offhost):
171 Offhost alternate client: flashsnap method
Install NetBackup Client and NetBackup Snapshot Client. The NetBackup for SAP Agent is not required. The NetBackup master server. You can install this on the same host or on separate host to which backup media will be attached. User and group identification numbers (UIDs and GIDs) associated with the files to be backed up must be available on the alternate backup client.
Configuration
Use the following procedure to configure. To configure the local host snapshot method 1 Attach the external disk D1 to the primary client (production database host) and create a VM disk group using the following command: Create a volume in primary disk D using the following command: Add a DCO log to the volume using the following command: Enable FastResync on the volume using the following command: Create a VxFS file system on this volume and mount it using the following commands:
2 3 4 5
root@primary# vxassist -g diskgroup addlog volume logtype=dco
root@primary# vxvol -g diskgroup set fastresync=on volume

6 7 8
Create the SAP production database on this volume. Connect the external mirror disk D2 to the primary client and the alternate client, so the disk is accessible to both hosts. Start the snapshot for the data volume in the primary client using the following command:
root@primary# vxassist -g diskgroup -b snapstart volume
Based on this flashsnap configuration, the typical flow during the Snapshot Client backup for SAP is as follows: 1 2 3 The database shuts down or the tablespaces are put in backup mode in the production host. The alternate client offhost takes the snapshot of the production database from primary disk D1 to mirror disk D2. The production database in primary disk D1 is created online.
172 Offhost alternate client: VVR method (Solaris SPARC, HP-UX)
4 5
The mirror disk D2 is split to perform backup from the snapshot to the backup media. The snapshot from the mirror disk D2 is then joined back to the volume in primary disk D1.
Offhost alternate client: VVR method (Solaris SPARC, HP-UX)

Figure H-2 on page 172 shows a typical system configuration. Figure H-2 Typical SAP split mirror offhost backup using VVR
Alternate client offhost
Production database host
Replicated database Snapshot Oracle database Primary disk Primary disk Mirror disk
Automatic tape changer
Backup media
Requirements

Install NetBackup Client, NetBackup Snapshot Client, and the NetBackup for SAP agent Configure the production database (Oracle) You can install the NetBackup master server on a separate host
Install the following on the alternate client (offhost):
Install NetBackup Client and NetBackup Snapshot Client. The NetBackup for SAP Agent is not required. The NetBackup media server. You can install this on the same host or on separate host to which backup media will be attached.
Configuration
The following procedures describe how to configure both the volume replicator primary and the volume replicator secondary. To configure the volume replicator primary (production database host) 1 Attach the external primary disk D1 to the volume replicator primary, and create a VM disk group using the following command: Create a data volume in primary disk D1 using the following command: By default, it creates two copies that require two disks in one group. To override the default, enter the following command:
root@primary # vxassist -g diskgroup addlog volume logtype=dcm nlog=1
Create the VxFS file system on this volume and mount it using the following commands:

4 5
Create the SAP production database on this volume. Create a storage replicator log (SRL) volume in primary disk D1 using the following command:
root@primary# vxassist -g diskgroup make volume_srl size
To configure the volume replicator secondary (alternate client offhost) Note: The names of the disk group and volumes must be same as on the primary host. 1 Attach the external replication disk D2 to the volume replicator secondary and create the VM disk group using the following command: Create a data volume in replication disk D2 using the following command: By default, it creates two copies that require two disks in one group. To override the default, enter the following command:
root@secondary# vxassist -g diskgroup addlog volume logtype=dcm nlog=1
root@secondary# vxdg init diskgroup [cds=on|off] diskname=devicename
root@secondary # vxassist -g diskgroup make volume size
Create a storage replicator log (SRL) volume in the replication disk D2 using the following command: On the volume replicator primary (production database host), create the primary replicated volume group (RVG) specifying the data volume(s), and SRL volume using the following command: Ensure that authentication can complete. Before adding a new secondary host (using addsec) or overwriting data on a remote host (using syncvol), vradmin performs some authentication by checking that the /etc/vx/vras/.rdg file on the remote host contains an entry for the primary disk group ID. The vradmin addsec or syncvol command fails if the /etc/vx/vras/.rdg file on the remote host does not have such an entry.

root@secondary# vxassist -g diskgroup make volume_srl size
root@primary# vradmin -g diskgroup createpri rvg_name data_volumes(s) srl_volume
Add the primary disk group ID to the /etc/vx/vras/.rdg file on the remote host. To find disk group ID, run the vxprint -l diskgroup_name command on the primary. Ensure that the /etc/hosts file has entries of primary and secondary host names in both hosts.
Add the secondary RVG to form the replicated data set (RDS) using the following command: Start replication between the volume replicator primary and secondary using the following command: Attach the external mirror disk D3 to the alternate client for taking snapshot mirror. On the volume replicator secondary (alternate client offhost), start the snap for the data volume using the following command:
root@primary# vradmin -g diskgroup addsec rvg_name primary_hostname secondary_hostname
root@primary# vradmin -g group_1 -a startrep v1_rvg
8 9
root@secondary# vxassist g diskgroup -b snapstart volume
Based on this VVR configuration, the typical flow during the Snapshot Client backup for SAP: 1 2 3 4 The database shuts down or tablespaces are put in backup mode in the production host. Replication is stopped between primary disk D1 and replication disk D2. The alternate client offhost takes the snapshot of the replication database from disk D2 to mirror disk D3. The production database in primary disk D1 is created online.
175 Hardware array-based snapshot method: Hitachi Shadow Image, EMC TimeFinder, HP Business Copy
5 6 7 8
The mirror disk D3 is split to perform backup from the snapshot to the backup media. The snapshot from the mirror disk D3 is then joined back to the volume in replication disk D2. Then the storage replication log (SRL) resync happens in primary disk D1 and secondary disk D2. Finally, replication resumes.
Hardware array-based snapshot method: Hitachi Shadow Image, EMC TimeFinder, HP Business Copy
Ensure that the vendor-related library files are installed in the following directory: /usr/lib.
176 Hardware array-based snapshot method: Hitachi Shadow Image, EMC TimeFinder, HP Business Copy
Appendix
Differences in NetBackup for SAP in release 6.x

Support for the following parameters of the initSID.utl file has been discontinued in NetBackup for SAP since release 6.0.
policy_log, sched_log, and second_secondary_archive.

These parameters were used to specify a policy, schedule, and for a flag for creating a second backup copy of an archive log. Refer to the alternate methods for performing a second backup of an archive log. See Performing an archive on page 70.
fail_backup
This parameter was used to stop the backup process immediately when an error occurred.
check_directory_flag
This parameter was used to allow a directory backup. If a directory was encountered, NetBackup for SAP flagged an error and stopped the backup. Support for this parameter was removed to comply with SAP certification requirements.
178
Index
A
alternate client restore
see redirected restore
Application Backup schedule
backup window 44
configuring 44
overview 44, 45
retention 44
archives, creating 70
automatic backup
create scripts 51
schedule
manual backup
schedules, configuring 45
Automatic Full Backup schedule 46
with Snapshot Client 99
Automatic Incremental Backup schedule 46
B
backint interface
command line 132
defined 131
input file 135
linking with NetBackup for SAP 34
parameter file 133
restore process 72
role in backup process 66
sequence of operation 15
technical overview 14
theory of operation 131
BACKINT parameter 59, 60
backint_dir parameter 145
Backup ID
see BID
backup medium
configuring 120
defined 119
Backup Selections list
adding selections 49
overview 48
backup_dev_type parameter 57
backup_stream_buffersize parameter 146 backups also see automatic backup automatic (configuring scripts) 51
manual 62
offline 67
online 70
output file contents 137
pre-6.0 165
scripts for backup operations 51
when using MaxDB 121
BID
generation process 66
returned on backup 137
bp.conf
administrator 129
repository for script parameters 53, 141
bpdbm daemon 30
bphdb
log 127
role in backups and restores 15
role in offline backups 51
bplist_filter parameter 146
bpplclients command 23, 30
brarchive command
example script 51
installation directory 34
overview 14, 18
using 70
brbackup command
backint parameter file 159
example script 51
install directory 34
multiplexing 40
overview 14, 18
sequence of operation 15
use in online backup 70
using to start a backup 66
using without sapdba 70
brconnect command 34
brrestore command
installation directory 34
180
overview 14, 18
using 72
brtools command 34
bsi.env file
overview 54
parameters 60
procedure for modifying 59
drives parameter 40, 55, 62, 149
E
environment variables 54, 140
ERROROUTPUT parameter 59, 60
export command 51
C
client list for installation 27
client parameter 55, 147
client read timeout property 129
cluster software prerequisites 23
cluster_config script 23, 31, 33
commands
backint 132
bpplclients 23, 30
brarchive 14, 18, 34, 51, 70
brbackup 14, 15, 18, 34, 40, 51, 70
brconnect 34
brrestore 14, 18, 34, 72
brtools 34
export 51
get_license_key 24, 32
initbpdbm 30
install_dbext 29, 33
sapdba 34
stopsap R3 67
su 52
update_dbclients 23, 27, 31
compatibility information 21
configuration
database debug level 125
Media Manager 22
custom_sort_file parameter 147
F
FlashSnap snapshots 105
Fulldata Storage Checkpoint 110
G
get_license_key command 24, 32
initbpdbm command 30
initSID.sap file
Oracle substitution characters 58
script parameters 53
initSID.utl file effect on Maximum Jobs per Client parameter 40
Oracle substitution characters 56
overview 54
parameter summary 143
script parameters 53
specifying a schedule name in 44
INPUT parameter 59, 60
inquiry_query_period parameter 149
install script 25, 32
install_dbext command 29, 33
installation
database software prerequsites 22
local 31
platform compatibility 21
prerequisites 21
prerequisites in a cluster 23
remote 23
requirements for NetBackup software 22
D
daemons, see processes
database software prerequisites for installation 22
debug logs
accessing 126
enabling 125
in /usr/openv/netbackup/logs 126
troubleshooting with log files 125
debugging level 125
directory
repository for commands 34
J
Java interface 40
181
L
licensing information 24, 32
local installation procedure 31
log files
enabling 126
sapdba utility 127
M
manual backups, see backups
master_time_offset parameter 150
MaxDB database
administrative interface 14
backup script 51
bsi.env file 54
configuration 119
configuration files 54
SAP parameter file 54
technical overview 13, 19
terminology 11
maximum jobs per client 40
Media Manager
configuring backup media 22
media, defined 119
media_notify_script parameter 150
medium, defined 119
multiple copies feature 47
multiplexing
overview 12
testing multiple drives 62
with MaxDB 122
multi-streamed backups 129
initSID.sap file 54
SAP parameter file 54
SAP profile file 54
SAP tools support 11
substitution characters 56, 58
technical overview 13, 15
with RMAN
backup script 51
linking with the SBT library 35
without RMAN
backup script 51
linking with backint 34
ORIGINAL_RUNDIRECTORY parameter 61
OUTPUT parameter 59, 60
P
parameter file
initSID.sap 53
initSID.utl 53
PARAMETERFILE parameter 59, 60
parameters
BACKINT 59, 60
backint_dir 145
backup_dev_type 57
backup_stream_buffersize 146
bplist_filter 146
client 55, 147
custom_sort_file 147
drives 40, 55, 62, 149
ERROROUTPUT 59, 60
INPUT 59, 60
inquiry_query_period 149
master_time_offset 150
media_notify_script 150
ORIGINAL_RUNDIRECTORY 61
OUTPUT 59, 60
PARAMETERFILE 59, 60
policy 55, 150
policy2 151
restore_filter 151
restore_stream_buffersize 152
retry_backup 152
rman_parms 58
schedule 55, 152
schedule2 152
server 55, 153
sleep 153
N
NAS Snapshot 102
configuring a policy for 102
NAS_Snapshot 105
NAS_Snapshot method 104
nbjm scheduling process 126
nbpem scheduling process 126
nbrb scheduling process 126
Nodata Storage Checkpoint 110
O
offline backups 67
online backups 70
Oracle database
configuration files 54
182
sort_backup_type 153
sort_restore_type 157
switch_list 55, 159
switch_log 55, 159
switch_sem 55, 160
TIMEOUT_FAILURE 61
TIMEOUT_SUCCESS 60
util_par_file 55, 57
platform compatibility 21
point in time rollback 105
policy configuration
adding clients 48
attributes 42
backup selections list 48
for databases 41
for Snapshot Client 99, 111
overview 41
schedules 43
testing 62
policy parameter 55, 150
policy2 parameter 151
processes
bpdbm 30
bphdb 51
log files for NetBackup processes 126
scheduling (nbpem, nbjm, nbrb) 126
RMAN see Oracle database

rman_parms parameter 58
robust logging 126
S
SAP DB database backing up and restoring 161
pre-6.0 backups and restores 161
terminology 11
SAP tools, see sapdba
SAP_CLIENT environment variable 139
SAP_DRIVES environment variable 139
sap_maxdb_backup script 51
sap_offline_backup script 51
sap_online_backup script 51
SAP_POLICY environment variable 139
sap_redo_log script 51
sap_rman_backup script 51
SAP_SCHED environment variable 140
SAP_SERVER environment variable 140
sapdba
backup process 67
command 34
databases that sapdba supports 11
defined 18
examples 67
offline backup 67
restore process 72
utility log 127
schedule parameter 55, 152
schedule2 parameter 152
schedules
adding 43
frequency 46
properties 46
retention 47
types of schedules 43
scripts
backup 51
cluster_config 23, 31, 33
examples 50
install 25, 32
restore 51
su command 52
type of operation 51
usage caution 51
server parameter 55, 153
R
recovery manager, see Oracle database
redirected restore 72
remote folder button 50
remote installation procedure 23
reports
All Log Entries report 127
NetBackup server reports 127
reports See also log files
restore_filter parameter 151
restore_stream_buffersize parameter 152
restores
output file contents 137
pre-6.0 166
snapshot rollback 105
using sapdba 72
with MaxDB 122
with Oracle 72
with Snapshot Client methods 105, 107
retention period
for frequency-based schedules 47
retry_backup parameter 152
183
skipped clients 27 sleep parameter 153 snapshot backup 97, 99, 105 Snapshot Client Block-level Incremental backup configuring a policy 111 overview 107 configuring policies 99 instant recovery configuration requirements 98 policy configuration 99 restore method 105 offhost backup
configuration 97
configuring 101
snapshot backup configuration 97 configuration requirements 98 database objects included 99 policy configuration 99 restore method 105 snapshot rollback 105 SnapVault 107 sort_backup_type parameter 153 sort_restore_type parameter 157 Storage Checkpoint 109 switch_list parameter 55, 159 switch_log parameter 55, 159 switch_sem parameter 55, 160
vxvm snapshot 105
W
Windows interface 40
T
testing policy configuration 62 timeout failures, minimizing 129 TIMEOUT_FAILURE parameter 61 TIMEOUT_SUCCESS parameter 60 transaction logs see archive logs
U
unified logging 126 update_dbclients command 23, 27, 31 utl_par_file parameter 55 utl_par_file parameters 57
V
Veritas Storage Foundation 111 VxFS_Checkpoint snapshot 105
184

290217

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

290217

Uploaded by

Copyright:

Available Formats

Veritas NetBackup for SAP Administrators Guide

for UNIX and Linux

Veritas NetBackup for SAP Administrators Guide

Third-party legal notices

Licensing and registration

Installing the agent

Files to configure ......................................................................................... 54

Using NetBackup for SAP

NetBackup for SAP with Snapshot Client

Configuring snapshot backups ..........................................................................97

NetBackup for SAP on MaxDB databases

Appendix A Appendix B Appendix C

backint command line backint -i in_file contents backint -o out_file contents

Information returned for a backup ................................................................. 137

Appendix D Appendix E Appendix F

Environment variables bp.conf file Parameters used in initSID.utl

Parameter summary .......................................................................................... 143

Using NetBackup for SAP to back up SAPDB

backint for SAPDB configuration file ..................................................162

Configuring split mirror backups

Differences in NetBackup for SAP in release 6.x

12 Introduction NetBackup for SAP features

NetBackup for SAP features

Table 1-1 Feature

NetBackup for SAP features and descriptions Description

Introduction NetBackup for SAP overview

Table 1-1 Feature

NetBackup for SAP features and descriptions (continued) Description

NetBackup for SAP overview

14 Introduction NetBackup for SAP overview

NetBackup for SAP environment on an Oracle or MaxDB database

Additional required NetBackup software: NetBackup client

Introduction NetBackup for SAP overview

SAP tools or MaxDB administrative interface (DBM CLI)

NetBackup for SAP backint

NetBackup XBSA API

bphdb NetBackup client

NetBackup master server Scheduler NetBackup

NetBackup for SAP on Oracle databases

16 Introduction NetBackup for SAP overview

Using NetBackup for SAP on Oracle databases without RMAN

SAP environment Oracle database

Using NetBackup for SAP on Oracle databases with RMAN

Introduction NetBackup for SAP overview

Oracle server libobk (liborasap) (NetBackup for Oracle)

Control files Profiles Log files

18 Introduction NetBackup for SAP overview

SAP tools overview

SAP tools software Function

Introduction NetBackup for SAP overview

NetBackup for SAP on MaxDB databases

NetBackup for SAP (backint)

20 Introduction NetBackup for SAP overview

Installing the agent

Verifying the installation prerequisites

Operating system and platform compatibility

22 Installing the agent Verifying the installation prerequisites

The NetBackup server software is installed and operational on the

Installing the agent Installing NetBackup for SAP

The NetBackup server software is installed and configured to work in a

Run commands such as bpplclients and update_dbclients from the

Installing NetBackup for SAP

Remote installation of NetBackup for SAP