Nmsapag 30

NetWorker
Module for SAP R/3 with Oracle
Release 3.0
Multiplatform Version
Administrators Guide
Copyright 2003, LEGATO Software, a division of EMC. All rights reserved. This product may be covered by one or more of the
following patents: U.S. 5,359,713; 5,519,853; 5,649,152; 5,799,141; 5,812,748; 5,835,953; 5,978,565; 6,073,222; 6,085,298; 6,145,089;
6,308,283; 6,324,654; 6,338,126; 6,397,307. Other U.S. and international patents pending.
LEGATO NetWorker Module for SAP R/3 with Oracle, Release 3.0, Multiplatform Version, Administrators Guide
December 2003
01-8565-3.0
LEGATO and the LEGATO logo are registered trademarks, and LEGATO NetWorker, NetWorker, Co-StandbyServer, RepliStor,
SnapShotServer, QuikStartz, AlphaStor, ClientPak, Xtender, XtenderSolutions, DiskXtender, ApplicationXtender, ArchiveXtender,
EmailXtender, and EmailXaminer are trademarks or registered trademarks of LEGATO Software, a division of EMC. This is a
nonexhaustive list of LEGATO trademarks, and other trademarks may be the property of their respective owners.
The following may be trademarks or registered trademarks of the companies identified next to them, and may be used in this
document for identification purposes only.
Acrobat, Adobe / Adobe Systems, Inc.
Apple, Macintosh / Apple Computer, Inc.
Caldera Systems, SCO, SCO OpenServer, UnixWare / Caldera, Inc.
TELEform / Cardiff
Check Point, FireWall-1 / Check Point Software Technologies, Ltd.
Unicenter / Computer Associates International, Inc.
Access Logix, Celerra, Centera, CLARiiON, EMC, EMC2, MirrorView, Navisphere, SnapView, SRDF, Symmetrix, Symmetrix DMX,
TimeFinder / EMC Corporation
Fujitsu / Fujitsu, Ltd.
Hewlett-Packard, HP, HP-UX, HP Tru64, HP TruCluster, OpenVMS, ProLiant / Hewlett-Packard Company
AIX, DB2, DB2 Universal Database, Domino, DYNIX, DYNIXptx, IBM, Informix, Lotus, Lotus Notes, OS/2, PTX, ptx/ADMIN, Raid
Plus, ServeRAID, Sequent, Symmetry, Tivoli, / IBM Corporation
InstallShield / InstallShield Software Corporation
Intel, Itanium / Intel Corporation
Linux / Linus Torvalds
Active Directory, Microsoft, MS-DOS, Outlook, SQL Server, Windows, Windows NT / Microsoft Corporation
Netscape, Netscape Navigator / Netscape Communications Corporation
Data ONTAP, NetApp, NetCache, Network Appliance, SnapMirror, SnapRestore / Network Appliance, Inc.
IntraNetWare, NetWare, Novell / Novell, Inc.
Oracle, Oracle8i, Oracle9i / Oracle Corporation
NetFORCE / Procom Technology, Inc.
DLTtape / Quantum Corporation
Red Hat / Red Hat, Inc.
R/3, SAP / SAP AG
IRIX, OpenVault, SGI / Silicon Graphics, Inc.
SPARC / SPARC International, Inc.a
ACSLS, REELbackup, StorageTek / Storage Technology Corporation
Solaris, Solstice Backup, Sun, SunOS, Sun StorEdge, Ultra / Sun Microsystems, Inc.
SuSE / SuSE, Inc.
Sybase / Sybase, Inc.
Turbolinux / Turbolinux, Inc.
Unicode / Unicode, Inc.
VERITAS, VERITAS File System/ VERITAS Software Corporation
WumpusWare / WumpusWare, LLC
UNIX / X/Open Company Ltdb
Notes:
a. Products bearing SPARC trademarks are based on an architecture developed by Sun Microsystems, Inc.
b. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd.
All other brand or product names may be trademarks or registered trademarks of their respective owners.
Legato Software
A Division of EMC Corporation
End-User License Agreement
THIS PRODUCT CONTAINS CERTAIN COMPUTER PROGRAMS AND OTHER PROPRIETARY MATERIAL, THE USE OF WHICH IS SUBJECT TO
THIS END-USER LICENSE AGREEMENT (THE "EULA"). DO NOT PROCEED WITH THE INSTALLATION OF THIS PRODUCT UNTIL YOU (LATER
DEFINED AS LICENSEE) HAVE READ THIS EULA AND AGREE TO BE BOUND BY AND BECOME A PARTY TO THIS EULA. BY PROCEEDING
WITH THE INSTALLATION OF THIS PRODUCT (OR AUTHORIZING ANY OTHER PERSON TO DO SO), YOU AND YOUR COMPANY ACCEPT
THIS EULA AND YOU REPRESENT THAT YOU ARE AUTHORIZED TO DO SO. IF YOU ARE ACCESSING THE PRODUCT ELECTRONICALLY
INDICATE YOUR ACCEPTANCE OF THESE TERMS BY SELECTING THE "ACCEPT" BUTTON AT THE END OF THE EULA. IF YOU DO NOT
AGREE TO THE TERMS OF THIS EULA, YOU MAY RETURN THIS PRODUCT, ALL MEDIA AND DOCUMENTATION, AND PROOF OF PAYMENT,
TO THE PLACE YOU OBTAINED THEM FOR A FULL REFUND WITHIN THIRTY (30) DAYS OF FIRST ACQUIRING THIS PRODUCT OR, IF THE
PRODUCT IS ACCESSED ELECTRONICALLY, SELECT THE "DECLINE" BUTTON AT THE END OF THIS EULA AND RETURN PROOF OF
PAYMENT IN ACCORDANCE WITH THE ABOVE REFERENCED RETURN/REFUND PROCESS. WRITTEN APPROVAL IS NOT A PREREQUISITE
TO THE VALIDITY OR ENFORCEABILITY OF THIS EULA AND NO SOLICITATION OF ANY SUCH WRITTEN APPROVAL BY OR ON BEHALF OF
LEGATO SHALL BE CONSTRUED AS AN INFERENCE TO THE CONTRARY. IF YOU HAVE ORDERED THIS PRODUCT, LEGATO'S ACCEPTANCE
IS EXPRESSLY CONDITIONAL ON YOUR ASSENT TO THESE TERMS TO THE EXCLUSION OF ALL OTHER TERMS; IF THESE TERMS ARE
CONSIDERED AN OFFER BY LEGATO, ACCEPTANCE IS EXPRESSLY LIMITED TO THESE TERMS.
1. DEFINITIONS
1.1 Authorization Code: means the unique code provided to Licensee by
Legato for permanent activation of the Software. The Authorization Code
is provided to Licensee once the Enabler Code is registered with Legato.
The Authorization Code may be tied to a unique machine ID code
supplied by Licensee.
1.2 Documentation: Documentation: means the user reference materials
on any media, provided by Legato for use with the Software.
1.3 Enabler Code: means the code provided by Legato for activation of the
Software.
1.4 Licensee: means the person or entity acquiring this License or for
whom this License was acquired.
1.5 Software: means the object code copy of the software program
provided to You in association with this EULA, together with the
associated original media and all accompanying Documentation, and
together with all Updates that may be provided by Legato to You from
time to time.
2. OWNERSHIP AND ADMINISTRATION OF SOFTWARE
2.1 Ownership and Title. As between the parties, Legato, and its
licensors, own and shall retain all right, title, and interest in and to: (i) the
Software including all intellectual property rights embodied therein; (ii)
all of the service marks, trademarks, trade names, or any other
designations associated with the Software; and (iii) all copyrights, patent
rights, trade secret rights, and other proprietary rights relating to the
Software.
2.2 Software Activation. Legato employs Enabler Codes and
Authorization Codes that enable the use of the Software. The Software is
shipped in a Media Kit which consists of object code software on
CD-ROM and an Enabler Code for initial activation of the Software or the
Software and Enabler Code may be delivered electronically. Once Legato
receives confirmation from Licensee that the Software is installed with the
correct Enabler Code, and is provided with the host ID information,
Legato will provide the Authorization Code to Licensee. Legato
administers the generation and distribution of Enabler and Authorization
Codes, which administration may be modified by Legato from time to
time.
2.3 Administration of Software. Legato may include on the media with
the Software additional computer programs which are not currently
licensed for use by Licensee and to which the Enabler Code or
Authorization code will not permit access. Inclusion of such additional
computer programs in no way implies a license from Legato and access or
use of such programs is strictly prohibited unless Licensee procures the
right to use any such program and the applicable Enabler Code is
provided thereto.
3. LICENSE GRANT
3.1 Grant. Legato grants to Licensee a non-exclusive, nontransferable,
non-sublicensable, perpetual (unless terminated in accordance with the
provisions of this EULA), license (the License) to (i) use the Software
installed in accordance with the Documentation and only on the licensed
computer(s) solely for its own internal operations; and (ii) move the
Software temporarily in case of computer system malfunction. The
Software may be licensed: (a) on a per copy or per seat basis, on a physical
or virtual machine, (b) based upon the number of mailboxes or the number
of non-concurrent users for which it may be used, or (c) based upon data
volumes it supports. The License granted under this EULA does not
constitute a sale of the Software or any portion or copy of it. Licensee may
not use the Software on more than one computer system unless otherwise
specifically authorized by an explicit Software product, or additional
licenses for additional computers are purchased. Rights not expressly
granted are reserved by Legato.
3.2 Copies. Licensee may make copies of the Software provided that any
such copy is: (i) created as an essential step in utilization of the Software
as licensed and is used in no other manner; or (ii) used for archival
purposes. All trademark and copyright notices must be reproduced and
included on such copies. Licensee may not make any other copies of the
Software.
3.3 Restrictions on use. Licensee shall not, and shall not aid, abet, or
permit any third party to: (i) decompile, disassemble, or otherwise reverse
engineer or attempt to reconstruct or discover any source code or
underlying ideas or algorithms of the Software by any means whatsoever;
(ii) remove any identification, copyright, or other notices from the
Software; (iii) provide, lease, lend, use for timesharing or service bureau
purposes; (iv) create a derivative work of any part of the Software; or (v)
develop methods to enable unauthorized parties to use the Software. If EC
law is applicable, the restrictions in Section 3.3 (i) are limited so that they
prohibit such activity only to the maximum extent such activity may be
prohibited without violating the EC Directive on the legal protection of
computer programs. Notwithstanding the foregoing, prior to
decompiling, disassembling, or otherwise reverse engineering any of the
Software, Licensee shall request Legato in writing, to provide Licensee
with such information or assistance and Licensee shall refrain from
decompiling, disassembling, or otherwise reverse engineering any of the
Software unless Legato cannot or has not complied with such request in a
commercially reasonable amount of time.
3.4 Purchase Orders. Nothing contained in any purchase order,
acknowledgment, or invoice shall in any way modify the terms or add any
additional terms or conditions to this EULA.
3.5 Updates. This section applies if the Software acquired is an update to
the original Software (the Update). An Update does not constitute a
legally licensed copy of the Software unless purchased as an Update to a
previously licensed version of the same Software. The Update may only
be used in accordance with the provisions of this EULA. The Update,
together with the original Software, constitutes one (1) legally licensed
copy of the Software.
3.6 Evaluation License. This Section applies if the Software is being used
for an initial thirty (30) day evaluation period. The license is valid only for
a period of thirty (30) days from the delivery of the Software, and is
designed to allow Licensee the right to evaluate the Software during such
period. In the event that Licensee desires to continue to license the
Software, Licensee must purchase a license to the Software. Upon such
purchase, Licensee will be provided with an Enabler Code in accordance
with Section 2.2 above. In the event Licensee determines not to purchase
a license for the Software at the end of such thirty (30) day evaluation
period, then Licensees rights under this EULA shall terminate
automatically and Licensee shall promptly return to Legato or destroy all
copies of the Software and so certify to Legato.
3.7 General Public License ("GPL"). The Software may include one or
more components which are derived from software subject to a General
Public License. Any such components are licensed exclusively under the
applicable GPL and not under this EULA.
4. MAINTENANCE AND SUPPORT

4.1 Legato has no obligation to provide support, maintenance, upgrades,
modifications, or new releases under this EULA. Legato may provide
such services under separate EULA.
5. LIMITED WARRANTY
8.3 Effect of Termination. Upon termination of this EULA, Licensee

agrees to cease all use of the Software and to return to Legato or destroy
the Software and all Documentation and related materials in Licensee's
possession, and so certify to Legato. Except for the License granted herein
and as expressly provided herein, the terms of this EULA shall survive
termination.
5.1 Media and Documentation. Legato warrants that if the media or

documentation are damaged or physically defective at the time of delivery
of the first copy of the Software to Licensee and if defective or damaged
product is returned to Legato (postage prepaid) within thirty (30) days
thereafter, then Legato will provide Licensee with replacements at no cost.
9. MISCELLANEOUS
5.2 Limited Software Warranty. Subject to the conditions and limitations

of liability stated herein, Legato warrants for a period of thirty (30) days
from the delivery of the first copy of the Software to Licensee that the
Software, as delivered, will materially conform to Legatos then current
published Documentation for the Software. This warranty covers only
problems reported to Legato during the warranty period. For customers
outside of the United States, this Limited Software Warranty shall be
construed to limit the warranty to the minimum warranty required by law.
9.2 Government Restricted Rights. Any Software which is acquired

directly or indirectly for or on behalf of the United States of America, its
agencies and/or instrumentalities ("U.S. Government"), is provided with
Restricted Rights. Use, duplication, or disclosure by the U.S. Government
is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights
in Technical Data and Computer Software clause at DFARS 252.227-7013
or subparagraphs (c)(1) and (2) of the Commercial Computer Software Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is
Legato Software, a division of EMC Corporation, 2350 W. El Camino Real,
Mountain View, CA 94040. The Software is a commercial software
product, licensed on the open market at market prices, and was developed
entirely at private expense and without the use of any government funds.
5.3 Remedies. The remedies available to Licensee hereunder for any such
Software which does not perform as set out herein shall be either repair or
replacement, or, if such remedy is not practicable in Legatos opinion,
refund of the license fees paid by Licensee upon a return of all copies of the
Software to Legato. In the event of a refund this EULA shall terminate
immediately without notice with respect to such Software.
6. WARRANTY DISCLAIMER
6.1 Warranty Disclaimer. EXCEPT FOR THE LIMITED WARRANTY
PROVIDED IN SECTION 5 ABOVE, ALL SOFTWARE IS PROVIDED "AS
IS". LEGATO AND ITS LICENSORS MAKE NO WARRANTIES WITH
RESPECT TO ANY SOFTWARE AND DISCLAIMS ALL STATUTORY OR
IMPLIED WARRANTIES, INCLUDING WITHOUT LIMITATION
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR ARISING FROM A COURSE OF DEALING OR USAGE
OF TRADE AND ANY WARRANTIES OF NONINFRINGEMENT.
LEGATO DOES NOT WARRANT THAT THE SOFTWARE WILL MEET
ANY REQUIREMENTS OR THAT THE OPERATION OF SOFTWARE
WILL BE UNINTERRUPTED OR ERROR FREE. ANY LIABILITY OF
LEGATO WITH RESPECT TO THE SOFTWARE OR THE
PERFORMANCE THEREOF UNDER ANY WARRANTY, NEGLIGENCE,
STRICT LIABILITY OR OTHER THEORY WILL BE LIMITED
EXCLUSIVELY TO THE REMEDIES SPECIFIED IN SECTION 5.3
ABOVE. Some jurisdictions do not allow the exclusion of implied
warranties or limitations on how long an implied warranty may last, so
the above limitations may not be applicable.
7. LIMITATION OF LIABILITY
7.1 Limitation of Liability. EXCEPT FOR BODILY INJURY, LEGATO
(AND ITS LICENSORS) WILL NOT BE LIABLE OR RESPONSIBLE WITH
RESPECT TO THE SUBJECT MATTER OF THIS EULA UNDER ANY
CONTRACT, NEGLIGENCE, STRICT LIABILITY, OR OTHER LEGAL
OR EQUITABLE THEORY FOR: (I) ANY INDIRECT, SPECIAL,
INCIDENTAL OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED
AND WHETHER OR NOT ADVISED IN ADVANCE OF THE
POSSIBILITY OF SUCH DAMAGES; OR (II) DAMAGES FOR LOST
PROFITS OR LOST DATA; OR (III) COST OF PROCUREMENT OF
SUBSTITUTE GOODS, TECHNOLOGY, SERVICES, OR RIGHTS; OR (IV)
FOR AMOUNTS IN EXCESS OF THOSE RECEIVED BY LEGATO FOR
THE PARTICULAR LEGATO SOFTWARE THAT CAUSED THE
LIABILITY . Because some jurisdictions do not allow the exclusion or
limitation of incidental or consequential damages, Legato's liability in
such jurisdictions shall be limited to the extent permitted by law.
8. TERM AND TERMINATION
8.1 Term. The term of this EULA is perpetual unless terminated in
accordance with its provisions.
8.2 Termination. Legato may terminate this EULA, without notice, upon
Licensee's breach of any of the provisions hereof.
9.1 Governing Law. This EULA shall be governed by the laws of the
Commonwealth of Massachusetts, without regard to the principles of
conflict of laws or the United Nations Convention on Contracts for the
International Sale of Goods.
9.3 Export and Import Controls. Regardless of any disclosure made by

Licensee to Legato of an ultimate destination of the Products, Licensee
may not directly or indirectly export or transfer any portion of the
Software, or any system containing a portion of the Software, to anyone
outside the United States (including further export if Licensee took
delivery outside the U.S.) without first complying with any export or
import controls that may be imposed on the Software by the U.S.
Government or any country or organization of nations within whose
jurisdiction Licensee operates or does business. Licensee shall at all times
strictly comply with all such laws, regulations, and orders, and agrees to
commit no act which, directly or indirectly, would violate any such law,
regulation or order.
9.4 Assignment. This EULA may not be assigned or transferred by
Licensee without the prior written consent of Legato, which shall not be
unreasonably withheld. Legato may assign or otherwise transfer any or
all of its rights and obligations under this EULA upon notice to Licensee.
9.5 Sole Remedy and Allocation of Risk. Licensee's sole and exclusive
remedies are set forth in this EULA. This EULA defines a mutually
agreed-upon allocation of risk, and the License price reflects such
allocation of risk.
9.6 Equitable Relief. The parties agree that a breach of this EULA
adversely affecting Legato's intellectual property rights in the Software
may cause irreparable injury to Legato for which monetary damages may
not be an adequate remedy and Legato shall be entitled to equitable relief
in addition to any remedies it may have hereunder or at law.
9.7 No Waiver. Failure by either party to enforce any provision of this
EULA will not be deemed a waiver of future enforcement of that or any
other provision, nor will any single or partial exercise of any right or
power hereunder preclude further exercise of any other right hereunder.
9.8 Severability. If for any reason a court of competent jurisdiction finds
any provision of this EULA, or portion thereof, to be unenforceable, that
provision of the EULA will be enforced to the maximum extent
permissible so as to effect the intent of the parties, and the remainder of
this EULA will continue in full force and effect.
10. ENTIRE EULA
10.1 This EULA sets forth the entire understanding and EULA between the
parties and may be amended only in a writing signed by authorized
representatives of both parties. No vendor, distributor, reseller, dealer,
retailer, sales person, or other person is authorized by Legato to modify
this EULA or to make any warranty, representation, or promise which is
different than, or in addition to, the warranties, representations, or
promises made in this EULA. No pre-printed purchase order terms shall
in any way modify, replace or supersede the terms of this EULA.
Contents
Preface ......................................................................................................... 11.
Audience.......................................................................................................................... 11.
Product Documentation ................................................................................................... 11.
Conventions..................................................................................................................... 12.
Information and Services................................................................................................. 13.
General Information .................................................................................................. 13.
Technical Support ..................................................................................................... 13.
Licensing and Registration........................................................................................ 14.
Customer Feedback ........................................................................................................ 14.
Chapter 1: Introduction............................................................................... 15.

Importance of Backing Up Mission-Critical Data ............................................................. 15.
Naming Conventions Used in This Guide........................................................................ 16.
Basic Network Configuration ........................................................................................... 16.
Summary of Features ...................................................................................................... 17.
NetWorker Server Software Features ....................................................................... 18.
NetWorker Module Software Features...................................................................... 18.
BRTools Software Features ...................................................................................... 18.
Oracle RMAN Software Features.............................................................................. 19.
Legato PowerSnap Features .................................................................................... 19.
Summary of Components and Settings........................................................................... 20.
NetWorker Server Components ................................................................................ 20.
NetWorker Module Components............................................................................... 20.
NetWorker Client Settings......................................................................................... 22.
SAP Components...................................................................................................... 22.
Oracle Components .................................................................................................. 23.
PowerSnap Components .......................................................................................... 23.
LEGATO NetWorker Module for SAP R/3 with Oracle, Release 3.0, Multiplatform Version
Contents
Summary of Processes ....................................................................................................24.

Backup with SAPDBA or brbackup............................................................................24.
Backup with RMAN....................................................................................................25.
Restore with SAPDBA or brrestore ...........................................................................26.
Restore with RMAN ...................................................................................................26.
Related Documentation....................................................................................................27.
Chapter 2: Basic Software Configuration..................................................29.

Task 1: Configure the Environment..................................................................................30.
Task 2: Configure the NetWorker Resources ..................................................................31.
Task 3: Configure the NetWorker Module Parameters ....................................................33.
Task 4: Configure the Backup and Restore Utility ...........................................................42.
Example: Configuring backint as the Backup and Restore Utility .......................42.
Example: Configuring RMAN as the Backup and Restore Utility ........................43.
Task 5: Configure a Backup of Cluster Data....................................................................44.
Chapter 3: Manual Backups........................................................................45.

About Manual Backups ....................................................................................................45.
Performing an Offline Manual Backup .............................................................................46.
How to Perform an Offline Backup ............................................................................46.
Performing an Online Manual Backup .............................................................................47.
How to Perform an Online Backup ............................................................................48.
Backing Up the Client File Indexes and Bootstrap...........................................................49.
Reviewing Backup Session Reports ................................................................................50.
Chapter 4: Scheduled Backups ..................................................................53.

Task 1: Test Basic Settings..............................................................................................53.
Task 2: Configure the Client Resource ............................................................................54.
Task 3: Encrypt the User Name and Password ...............................................................57.
Task 4: Configure the Scheduled Backup Configuration File...........................................58.
Reviewing Backup Session Reports ................................................................................63.
Contents
Chapter 5: Cloning Save Sets .................................................................... 65.

Clone Command Syntax and Options ............................................................................. 65.
Monitoring the Cloning Process....................................................................................... 67.
Chapter 6: Restoring Data .......................................................................... 69.

Reviewing Save Sets....................................................................................................... 69.
Expiration of Save Sets............................................................................................. 70.
Performing Restores........................................................................................................ 70.
How to Restore a Database or Database Object ...................................................... 71.
Restoring SAP R/3 with Oracle Cluster Data .................................................................. 72.
Reviewing Restore Session Reports ............................................................................... 72.
Chapter 7: PowerSnap Backups and Restores ........................................ 75.

Requirements .................................................................................................................. 76.
Supported Environments........................................................................................... 76.
Required Software Components ............................................................................... 76.
Types of PowerSnap Backups ........................................................................................ 77.
Instant Backup .......................................................................................................... 78.
Live Backup............................................................................................................... 78.
Immediate Live Backup ...................................................................................... 78.
Deferred Live Backup ......................................................................................... 79.
Types of PowerSnap Restores........................................................................................ 79.
Instant Restore.......................................................................................................... 80.
Rollback .................................................................................................................... 80.
Restore from Secondary Storage.............................................................................. 80.
PowerSnap Backup and Restore Data Flows ................................................................. 81.
Quick Start....................................................................................................................... 83.
PowerSnap Software Configuration Roadmap................................................................ 86.
Configuring NetWorker Resources for PowerSnap ......................................................... 87.
Configuring the NetWorker Snapshot Pool Resource............................................... 87.
Contents
Configuring the NetWorker Snapshot Policy Resource .............................................87.

Configuring the NetWorker Group Resource.............................................................87.
Configuring the NetWorker Client Resource .............................................................88.
Setting the PowerSnap Parameters.................................................................................89.
Setting Variables in the PowerSnap Configuration File ...................................................93.
PowerSnap Use of Equivalent NetWorker Module Parameters ................................95.
Invoking PowerSnap Backup Processes .........................................................................96.
Instant Backup Processes .........................................................................................96.
Immediate Live Backup Processes ...........................................................................99.
Deferred Live Backup Processes ............................................................................102.
Querying PowerSnap Backup Records..........................................................................104.
Invoking PowerSnap Restore Processes.......................................................................105.
Instant Restore and Rollback Processes.................................................................105.
Restore from Secondary Storage Processes ..........................................................107.
Appendix A: Commonly Used Command Options for brbackup,

brarchive, and brrestore............................................................................109.
Syntax and Options for brbackup and brarchive Commands.........................................110.
Syntax and Options for brrestore Command..................................................................113.
Appendix B: Environment Variables for RMAN ......................................115.

Setting the Environment Variables.................................................................................115.
Environment Variable Definitions ...................................................................................116.
Appendix C: Troubleshooting .................................................................123.

Verifying the Release Information ..................................................................................123.
Generating Diagnostic Logs...........................................................................................124.
Backup and Restore Problems ......................................................................................124.
Regular Session Error Messages ..................................................................................126.
Fatal Error Messages.....................................................................................................129.
Contents
Glossary ..................................................................................................... 135.

Index ........................................................................................................... 143.
Contents
10
Preface
This guide provides information on how to configure and manage the Legato
NetWorker Module for SAP R/3 with Oracle software (referred to in this
guide as simply the NetWorker Module software).
Install this multiplatform NetWorker Module software on the supported
UNIX, Linux, or Microsoft Windows server and clients before using the
information presented in this guide. For installation instructions, refer to the
LEGATO NetWorker Module Installation Guide for installation instructions.
Post-release information is contained in the Release Supplement for this
product. This document is available is available at www.legato.com. Refer to the
web site periodically to view the latest Release Supplement.
Audience
The information in this guide is intended for system administrators who are
responsible for installing software and maintaining the servers and clients on
a network. Operators who monitor the daily backups may also find this
manual useful.
Product Documentation
For a complete list of documentation related to this product, see <insert x-ref
here>. Most of the documents are in Adobe Acrobat Portable Document
Format (PDF), and can be viewed by downloading and installing the Adobe
Acrobat Reader. The Reader is available in the /viewers/acroread directory on the
LEGATO Documentation Suite CD-ROM, or directly from Adobe. To install
and use the Reader on the preferred platform, refer to the instructions in the
CD-ROMs /viewers/acroread/readme.txt file or at the Adobe web site.
11
Conventions
Conventions
This document uses the following typographic conventions and symbols to
make information easier to access and understand.
Convention
Indicates
Example
boldface
Names of line commands,

daemons, options,
programs, or scripts
The nsradmin command starts the

command line version of the NetWorker
Administrator program.
italic in text
Pathnames, filenames,
computer names, new terms
defined in the Glossary or
within the chapter, or
emphasized words
Displayed messages are also written to

/nsr/logs/daemon.log.
italic in
command line
A variable that must be

provided in the command
line
nwadmin -s server_name
fixed-width
Examples and information

displayed on the screen
media waiting: recover waiting for

8mm 5GB tape volume name
The specifications are created, one for each

swap file, in c:\pagefile.sys.
fixed-width, Commands and options that nsr_shutdown -a

boldface
must be entered exactly as
shown
Menu_Name>
Command
A path or an order to follow Volume>Change Mode>Appendable

for making selections in the
user interface
Important:
Information that must be

read and followed to ensure
successful backup and
Important: Use the no_verify option with
recovery of data
extreme caution.
12
Preface
Information and Services

LEGATO offers a variety of methods (including e-mail, telephone, and fax
support) to obtain company, product, and technical information.
General Information
The LEGATO web site provides most of the information that customers might
need, including technical bulletins and binary patches from its FTP site. For
specific sales or training needs, e-mail or call LEGATO.
Service or Resource
Company
Technical Binary and Product
Bulletins Patches Information Training
www.legato.com
Yes
Yes
ftp.legato.com
(log in as anonymous)
Yes
Yes
LEGATO Sales
(650) 210-7000 (option 1)
sales@legato.com
Yes
Yes
Yes
LEGATO Education
Services
(650) 842-9357
training@legato.com
Yes
Technical Support
The LEGATO web site provides contact information, software patches,
technical documentation, and information about available support programs.
Customers with an active support agreement have access to the LEGATO

integrated product knowledge base. Help with software issues is also
available through Technical Support.
Customers without an active support agreement can contact Support Sales
and Renewal to purchase annual software update subscriptions, or
technical support services for per-update/per-incident assistance.
13
Licensing and Registration

To license and register products, go to the licensing web site at www.legato.com.
To change contact information, transfer licenses, or ask questions about
licensing, contact LEGATO by using one of the following methods.
Contact
Telephone number
(650) 812 6000 (option 3, option 2)a

+31 23 554 8881b
Fax number
(650) 745-1477a
+31 23 554 8808b
E-mail
licensing@legato.coma
licensingemea@legato.comb
a. Contact information for the Americas, Asia, and the Pacific.

b. Contact information for Europe, the Middle East, and Africa.
Customer Feedback
LEGATO welcomes comments and suggestions about software features, the
installation procedure, and its documentation.
14
To comment on a particular guide, complete the Comments form at

www.legato.com. Navigate to the documentation page and click the
Comments link beside the name of the guide. All comments are reviewed
and acted upon, usually within one business day.
To help improve our documentation in general, complete a brief survey at
www.legato.com. Navigate to the documentation page and click the link to
the survey.
To provide other suggestions and comments, send e-mail to
feedback@legato.com. Although LEGATO cannot respond personally to
every request, all comments and suggestions are considered during
product design.
Chapter 1: Introduction
This chapter describes the main features and components of the Legato
NetWorker Module for SAP R/3 with Oracle, and the associated NetWorker,
SAP, and Oracle systems. It also describes the Legato PowerSnap software,
which is required for snapshot backups.
This chapter contains the following sections:
"Importance of Backing Up Mission-Critical Data" on page 15

"Naming Conventions Used in This Guide" on page 16
"Basic Network Configuration" on page 16
"Summary of Features" on page 17
"Summary of Components and Settings" on page 20
"Summary of Processes" on page 24
"Related Documentation" on page 27
Importance of Backing Up Mission-Critical Data

It is important to back up computer systems to protect them from the loss of
valuable data. In a network environment, where users depend on shared data
and the amount of data continuously grows, the need to manage data becomes
crucial.
A viable backup strategy includes regular backups of databases and archive
logs. Without archive logs, you can recover a database only to the time of its
last full backup.
15
Naming Conventions Used in This Guide
Naming Conventions Used in This Guide

Table 1 on page 16 lists special terms that are used in this guide.
Table 1. Naming Conventions Used in This Guide

Term
Description or Usage
BRTools
SAP R/3 backup utilities, specifically the brbackup,

brrestore, and brarchive programs.
NetWorker Module
software
The shortened form, used throughout this guide, for

the complete name, Legato NetWorker Module for
SAP R/3 with Oracle, release 3.0 software.
<ORACLE_SID>
The name of the Oracle database instance that you

want to back up, usually the argument for the
brbackup or brarchive -u option.
restore and recover
This guide follows Oracle terminology, which

distinguishes between restoring and recovering a
database.
Restore means to retrieve individual datafiles from
backup media and store the files on disk.
Recover means to apply the redo log to make the
database consistent.
This usage is unlike NetWorker terminology, which
uses recover for all data retrieval activities (as
distinguished from the UNIX restore command).
Basic Network Configuration

This section describes a network configuration for regular backup and
recovery services when using the NetWorker Module software.
Note: For information on snapshot backup and restore with PowerSnap, see
"Chapter 7: PowerSnap Backups and Restores" on page 75
A basic backup and recovery network can be configured as follows:
16
The NetWorker storage management server has NetWorker server

software installed.
A backup storage device is either attached to the NetWorker server or on
a separate NetWorker storage node server.
Each database server has NetWorker client software, NetWorker Module

software, SAP software, and Oracle database software installed.
Each Networker client, including each database server, has Networker
client software installed.
Figure 1 on page 17 shows a sample configuration with the NetWorker server

software and the database server software on separate computers.
Figure 1. NetWorker Server and the Database Server on Separate Systems
NetWorker Server
Database Server
SAP R/3 Server

Oracle database
NetWorker Module
NetWorker Client
Windows Client without database

Windows NetWorker Client
UNIX Client without database

UNIX NetWorker Client
Summary of Features
This section describes the features of the related NetWorker server and client
software, NetWorker Module software, SAP R/3 software, and optional
Oracle RMAN software that work together to provide storage management
services. For a summary of software components, see "Summary of
Components and Settings" on page 20.
17
NetWorker Server Software Features
NetWorker Server Software Features

The Legato NetWorker software provides data storage management services
that protect and help manage data across an entire network.
The main NetWorker server software features that work in conjunction with
the NetWorker Module software include:
Save group, pool, and client configuration

Backup scheduling
Authorization
Online index maintenance (client file index and media database)
NetWorker Module Software Features

The NetWorker Module for SAP R/3 with Oracle software is an add-on
module for NetWorker client software that provides a backup and restore
interface between the SAP BRTools program and the NetWorker server. The
main component of the NetWorker Module is the backint program, which
provides backup, inquiry, and restore processes for all Oracle and SAP R/3
files.
The NetWorker Module software enables you to perform the following
operations for SAP R/3 data on Oracle databases:
Manual backups
Scheduled backups
Inquiry of backed up data
Restores of backed up data
Automated media management
Snapshot backup and recovery
Sapclone
BRTools Software Features

Backup, restore, and inquiry of SAP R/3 databases on Oracle is provided
through the following SAP R/3 features:
18
BRTools (comprised of the brbackup, brrestore, brarchive, and other

utilities).
SAP database administration (SAPDBA) utility, a menu-driven interface
to BRTools.
Invoking the brbackup command directly or from the SAPDBA Backup

Database screen passes the following data to backint for backup:
Oracle datafiles
Control files
Any existing profiles or specified files
SAP internal catalogs for backup sessions
Invoking the brarchive command directly or from the SAPDBA Backup

Archive Logs screen passes the offline redo logs to backint for backup.
Oracle RMAN Software Features

The NetWorker Module software supports SAP R/3s use of Oracles Recovery
Manager (RMAN) backup and restore utility, which is available with Oracle8
or later databases. Use of RMAN with the NetWorker Module is optional, and
you can continue to use the NetWorker Modules backint program as the sole
backup and restore tool. If you want to use RMAN to back up Oracle
databases, you must still use backint to back up SAP R/3 configuration files,
logs, and other files. For a description of RMAN features, refer to Oracle
documentation.
Legato PowerSnap Features

NetWorker backups use the PowerSnap functionality to create a snapshot
(point-in-time copy) of a group of files or filesystems that belong to a client.
The snapshot serves as an instant backup, which can then be either immediately
backed up to a traditional storage medium, such as tape, or backed up at a later
backup session. Many instant backups can be performed in a single day, thus
reducing the exposure to data loss.
Instant backups protect only against logical failures. To protect against
physical failures, the snapshot must be backed up to a traditional storage
medium.
Whether or not a backup uses the PowerSnap features is determined by Client,
Group, and Policy resource configurations.
19
Summary of Components and Settings
Summary of Components and Settings

This section summarizes the user-configurable components and basic settings
of the various products used with the NetWorker Module, and how they work
with their associated binary executable files to provide storage management
services. These components are described in the following topics:
"NetWorker Server Components" on page 20

"NetWorker Module Components" on page 20
"NetWorker Client Settings" on page 22
"SAP Components" on page 22
"Oracle Components" on page 23
"PowerSnap Components" on page 23
NetWorker Server Components

The NetWorker Administrator program is a graphical user interface. This
NetWorker Server component is used to configure NetWorker resources, such
as Client, Group, and Pool. For details, refer to the Legato NetWorker
NetWorker Module Components

Table 2 on page 20 lists the NetWorker Module components.
Table 2. NetWorker Module Components (Part 1 of 2)
Component
Type
Description
backint
Binary
executable
This backup, restore, and inquiry program

provides an interface to SAP BRTools. It uses
configurations from the init<ORACLE_SID>.utl file.
init.utl
Configuration This is the sample configuration file for the backint

file
program and is to be used as a template. Copy this
file and name it init<ORACLE_SID>.utl, where
<ORACLE_SID> is the name of the Oracle database
instance that is to be backed up. Use the copy and
save the original.
20
Table 2. NetWorker Module Components (Part 2 of 2)

Component
Type
Description
log files
log files
Log files used for the NetWorker Module software.

The default location by operating system is as
follows:
(UNIX): /nsr/applogs
(Windows): C:\Program files\Legato\nsr\applogs
nsrsapsv
Binary
executable
The scheduled backup program, which invokes the

appropriate BRTools executables. It uses
configurations from the nsrsapsv.cfg template file, or
renamed copy of this file. Specify this file as the
backup command in the NetWorker Client
resource.
nsrsapsv.cfg
Configuration The sample configuration file for the nsrsapsv

file
program. Copy the sample template file and save
the original.
nsrsapadm
Binary
executable
Administrative program for nsrsapsv operations;

encrypts logon information (os_usr_passwd or
oracle_usr_passwd, depending on authorization
method) for the user performing a scheduled
backup.
sapclone
Binary
executable
The save set cloning program. Provides an interface

to the NetWorker nsrclone program.
21
NetWorker Client Settings
NetWorker Client Settings

Table 3 on page 22 lists the main NetWorker Client resource attributes used
with the NetWorker Module software. For a complete description of
NetWorker Client resource attributes, refer to the Legato NetWorker
Administrators Guide.
Table 3. NetWorker Client Resource Settings Used by the NetWorker Module Software
Attribute
Description
Backup command
Specifies the command used for scheduled backups, including

parameters and configuration file. For example:
nsrsapsv -f /nsr/res/nsrsapsv.cfg
Save Set
Normally specified as backint:<ORACLE_SID>.

For PowerSnap usage, this attribute must be specified.
For all other usage, this attribute is only informational, because
the nsrsapsv.cfg file determines the ORACLE_SID parameter.
SAP Components
Table 4 on page 22 lists the SAP software components used with the
NetWorker Module software.
Table 4. SAP Components Used by the NetWorker Module Software
Component
Type
Description
BRTools
Binary
executables
SAP R/3 backup utilities, specifically the

brbackup, brrestore, and brarchive programs
(equivalent to NetWorker client save, recover,
nsrinfo, and mminfo programs). Invoked by
nsrsapsv, SAPDBA, or command line.
SAPDBA
Binary
executable
Menu-driven interface to BRTools for backup,

restore, and inquiry-related operations.
init<ORACLE_SID>.sap
Configuration The SAP configuration file. Relevant parameters

file
specify whether to use the backint program or
RMAN for backup, inquire, and restore sessions.
22
Oracle Components
Table 5 on page 23 lists the Oracle software components used with the
Table 5. Oracle Components Used by the NetWorker Module Software

Component
Type
Description
RMAN
Binary
executable
Oracle utility for performing backups and restores of

the Oracle database, using the rman_parms parameter.
To enable RMAN, set the backup_dev_type parameter in
the init<ORACLE_SID>.sap file to rman_utl.
rman_parms
Parameter
Optional parameter in the init<ORACLE_SID>.sap file.

Used to specify environment variables for an RMAN
backup or restore with the NetWorker Module.
PowerSnap Components
The NetWorker Module software components that are used specifically to
enable and configure PowerSnap features are listed in Table 6 on page 23.
Table 6. PowerSnap Components Used by the NetWorker Module Software
Component
Type
Description
init.utl
Configuration The init<ORACLE_SID>.utl configuration file for the

File
backint program. The parameters within this file that
are specific to PowerSnap are those with the ps_
prefix.
nmsapps.cfg
(example name)
Configuration User-defined PowerSnap configuration file, in which

File
the PowerSnap parameters are set.
ps_opaque_pfilename
Parameter
Parameter in the init<ORACLE_SID>.utl file that

specifies the complete file pathname for the
user-defined PowerSnap configuration file, for
example:
On UNIX: /nsr/res/nmsapps.cfg
On Windows:
C:\Program Files\Legato\nsr\res\nmsapp.cfg
23
Summary of Processes
Summary of Processes
The NetWorker Module software provides storage management services that
connect NetWorker functionality to SAP R/3 servers running Oracle
databases. The backup and restore processes can be initiated from the
following interfaces:
SAPDBA menu-driven interface

BRTools: brbackup, brarchive, or brrestore commands
NetWorker Modules nsrsapsv command, used for scheduled backups
Additionally, Oracles RMAN can be invoked through these interfaces to back

up and restore Oracle databases.
Note: PowerSnap backups must be initiated through the nsrsapsv scheduled
backup program, and are not supported for manual backups.
Backup with SAPDBA or brbackup

When a backup is initiated from SAPDBA or the brbackup program on the
SAP R/3 server running Oracle, brbackup sends a request to the backint
program. The backint program runs two or more times, as required, to back
up the requested Oracle datafiles, control files, online redo logs, and profiles.
It sends all the data and process information in parallel streams to the
NetWorker server. The data stream is backed up on storage media or a
NetWorker storage node, and NetWorker software creates entries in the client
file index and media database. The final results of the backup are recorded in
a log file, backint<ORACLE_SID>.log, on the SAP R/3 server running Oracle.
Figure 2 on page 25 shows how the NetWorker services, processes, and
programs interact during a backup.
24
Figure 2. NetWorker and Database Interaction during a Backup

NetWorker Client
SAP R/3 on Oracle Server
brbackup
(SAPDBA)
NetWorker Server
Client File
Media
Index
Database
Storage
Medium
nsrindexd
nsrmmdbd
backint
nsrmmd
data
backint (save)
nsrd
inter-process communication
Backup with RMAN

When the Oracle RMAN utility (available with Oracle8 or later) is used to back
up an Oracle database, the process is similar to backup that uses SAPDBA,
except brbackup sends requests to both RMAN and backint. The following
occurs as a result:
1. RMAN backs up the Oracle datafiles.
2. The backint backs up the configuration files, logs, and other flat files that
are specific to SAP.
25
Restore with SAPDBA or brrestore
Restore with SAPDBA or brrestore

When a restore is initiated from SAPDBA or the brrestore program on the SAP
R/3 server running Oracle, brrestore sends a restore request to the backint
program. The backint program browses the NetWorker servers client file
index and restores the specified files in a parallel stream from the NetWorker
server to the SAP R/3 server running Oracle.
Figure 3 on page 26 shows how NetWorker services, processes, and programs

interact during a restore.
Figure 3. NetWorker and Database Interaction during a Restore
NetWorker Client
SAP R/3 on Oracle Server
brrestore
(SAPDBA)
NetWorker Server
Client File
Media
Index
Database
Storage
Medium
nsrindexd
nsrmmdbd
backint
nsrmmd
data
backint (recover)
nsrd
inter-process communication
Restore with RMAN

If RMAN is used to restore the Oracle database, RMAN restores the Oracle
database datafiles only. If you also want to restore the configuration files, logs,
and other flat files that are specific to SAP R/3, you must manually restore
them by using any of the following:
26
The backint program

The NetWorker recover program
BRTools with appropriate command line parameters.
Related Documentation
For further information on the Legato NetWorker Module for SAP R/3 with
Oracle, refer to the following related documentation:
Legato NetWorker Module for SAP R/3 with Oracle, Release 3.0, UNIX, Linux,
and Microsoft Windows Version, Installation Guide
and Microsoft Windows Version, Release Supplement
NetWorker PowerSnap Module Installation and Administrators Guide
appropriate for your implementation
Legato NetWorker Administrators Guide appropriate for your
implementation
UNIX man pages
NetWorker Command Reference Guide
Legato Software Compatibility Guide
27
Related Documentation
28
Chapter 2: Basic Software Configuration
This chapter provides basic configuration instructions for the NetWorker

Module and other supporting software required for backup, recovery, and
inquiry of SAP R/3 with Oracle data and other files. Unless otherwise noted,
the configurations described in this chapter apply to both manual and
scheduled backups.
This chapter describes the following tasks that need to be performed, although
not necessarily in this order:
"Task 1: Configure the Environment" on page 30

"Task 2: Configure the NetWorker Resources" on page 31
"Task 3: Configure the NetWorker Module Parameters" on page 33
"Task 4: Configure the Backup and Restore Utility" on page 42
"Task 5: Configure a Backup of Cluster Data" on page 44
More specific configurations are covered in later chapters:
"Chapter 3: Manual Backups" on page 45

"Chapter 4: Scheduled Backups" on page 53
"Chapter 5: Cloning Save Sets" on page 65
"Chapter 6: Restoring Data" on page 69
"Chapter 7: PowerSnap Backups and Restores" on page 75
29
Task 1: Configure the Environment
Task 1: Configure the Environment

Use the following steps to configure the environment for the NetWorker
Module software:
1. Install and enable the NetWorker Module on each Oracle database server
with SAP R/3 that requires backup and recovery services. For
instructions, refer to the Legato NetWorker Module for SAP R/3 with Oracle,
Release 3.0, Installation Guide.
2. Set the PATH environment variable for the Oracle user to point to the
location of the NetWorker client executables, which is typically as follows:
On UNIX: /nsr/bin
On Windows: C:\Program Files\Legato\nsr\bin
3. Ensure the backint executable binary file is in the same directory as

BRTools. On UNIX, set the owner of backint to root.
4. If you need to restore to raw device files on UNIX, set the uid bit on for the
backint program by entering the following command:
chmod 4755 backint
5. For NetWorker 7.x, ensure that the SAP backup user is listed in the User
Groups, and has the following privileges:
Monitor NetWorker processes
Back up local data
Recover local data
To verify these settings, run NetWorker Administrator (nwadmin) on the
server:
On UNIX: Select User Groups from the Customize menu.
On Windows: Click the User Groups button, right-click the SAP
backup user and select Edit.
30
Task 2: Configure the NetWorker Resources

The NetWorker resources reside on the NetWorker server and are configured
using the NetWorker Administrator program.
Table 7 provides resource configuration details that are specific to the
Table 7. NetWorker Resources (Part 1 of 2)
Resource
Comments
Client
Specifies the NetWorker Client resources for each SAP R/3 server
running Oracle that requires backup, restore, and inquiry operations.
Browse and Retention settings in the Client resource are ignored.

Instead, a value must be set in the expiration parameter in the
NetWorker Modules parameter file, init<ORACLE_SID>.utl. See the
listing for "expiration" on page 36.
For scheduled backups, the Remote User and Password attribute may
need to be specified in the Client resource for certain Windows
configurations, and setting them is recommended. On UNIX, these
attributes do not need to be specified in the Client resource. For all
systems, the user name and password must be encrypted, see "Task 3:
Encrypt the User Name and Password" on page 57.
For details on setting the Save Set and Backup Command attributes,
which are specific for scheduled backups, see Table 10 on page 54.
Group
Specifies a set of clients to start backing up data at a specified time.

Note: The group name must be the same as defined in the NetWorker
Modules parameter file, init<ORACLE_SID>.utl, see the listing for
"group" on page 36.
Pool
Specifies the medium volumes in each pool to receive specific backup

data. When configuring the Pool resource, complete the following:
Leave the Save Sets attribute blank; the NetWorker Module program
sets this attribute during each backup session.
Once a pool is created, specify its name in the NetWorker Modules
parameter file, init<ORACLE_SID>.utl.
31
Task 2: Configure the NetWorker Resources
Table 7. NetWorker Resources (Part 2 of 2)

Resource
Comments
Schedule
Specifies the days of the week or month when scheduled backups runs.
Server
Defines the NetWorker server to be used for backup, restore, and

inquiry operations.
When configuring the Server resource, check for the following:
Ensure that the Parallelism attribute is equal to or greater than the
number of save streams being sent to the NetWorker server by the
Oracle server or cluster client. The value should match or be greater
than the parallelism setting found in the NetWorker Modules
parameter file, init<ORACLE_SID>.utl, see "parallelism" on page 38.
Ensure that a Device resource is configured for each Oracle storage
device used for backup and restore operations. Each device must
contain a labeled and mounted volume.
When performing manual backups, ensure the Manual Saves attribute
is set to Enabled.
It is not necessary to specify the SAP backup user in the Administrator

attribute.
For more information on configuring the NetWorker resources, refer to the
NetWorker Online Help or the Legato NetWorker Administrators Guide.
32
Task 3: Configure the NetWorker Module Parameters

During backup, restore, or inquire sessions, the NetWorker Module program
uses the parameter settings specified (or the default values if not specified)
from the init<ORACLE_SID>.utl parameter file. These parameter settings
provide client, server, pool, group, expiration and other values to the backint
program.
Important: The names for the server, group, client, and pool specified in the
parameter file must match the corresponding resource settings defined on the
NetWorker server. An error results if there is a mismatch.
To set a parameter in the init<ORACLE_SID>.utl parameter file, use the

following format:
parameter=value
Refer to the following rules when setting parameters:
Uncomment and modify as necessary all parameters to be used in

backup, restore, or inquire operations.
Use lowercase parameter names and values.
For descriptions and default values for NetWorker Module parameters, see
Table 8 on page 34.
33
For specific instructions on configuring data clusters, see "Task 5: Configure a

Backup of Cluster Data" on page 44.
Table 8. Parameters for the NetWorker Module init<ORACLE_SID>.utl File (Part 1 of 8)
Parameter
Default
Description
arch_backint_log
See Description
column for default
location on UNIX or
Windows
Specifies the full pathname of the log file for

running the brarchive command.
Default location on UNIX:

/nsr/applogs/arch_backint<ORACLE_SID>.log
Default location on Windows:

C:\Program Files\Legato\nsr\applogs\
arch_backint<ORACLE_SID>.log
backint_log
See Description
column for default
location on UNIX or
Windows
Specifies the full pathname of the backint log file

for running the brbackup and brrestore
commands.
/nsr/applogs/backint<ORACLE_SID>.log
backint<ORACLE_SID>.log
Note: To specify a separate log file to use
specifically for restores, modify this parameter
before running brrestore. Alternatively, the
backint_log parameter can be specified in an
init<ORACLE_SID>_restore.utl file, which can be
referenced from the util_par_file parameter in the
init<ORACLE_SID>_restore.sap file, for example:
brrestore -p init<ORACLE_SID>_restore.sap
backint_tmpdir
See Description
column for default
location on UNIX or
Windows
Specifies the directory name of the backint

temporary files.
/nsr/applogs/
34

Parameter
Default
Description
checksum
No
Specifies whether to perform cyclic redundancy

checking (CRC) on restores.
Setting this parameter to Yes excludes using the
compress and encrypt parameters, which should
be set to No. If more than one of these parameters
is set to Yes, the priority order is: compress,
checksum, encrypt.
client
Local host
Specifies the NetWorker client hostname to use for

the client file index for the current backup.
If you are using the NetWorker Module to back up
a virtual cluster client, set this value to the virtual
node name.
During cluster restores, this parameter specifies
the name of the client with the client file index for
the backup to be restored. For example, to restore
data to a host named saturn using the backup from
a host named mars, set this parameter to mars so
that the client file indexes for mars are used.
compress
No
Compresses data during a backup before the data

is passed over the network or written to tape,
which can speed up the backup process.
Compression increases CPU usage on the SAP R/3
server running Oracle, but reduces the amount of
data sent to the NetWorker server.
Setting this parameter to Yes excludes the use of
checksum and encrypt parameters, which should
checksum, encrypt.
35

Parameter
Default
Description
encrypt
No
Specifies whether to encrypt the backup data.

Setting this parameter to Yes excludes the use of
compress and checksum parameters, which should
checksum, encrypt.
2
expiration
2 Weeks
For all backups, the expiration parameter sets both

the browse and retention periods.
For NetWorker 7.x, this parameter overrides the
NetWorker server-side Client resource settings.
For NetWorker 6.x this parameter does not
override the NetWorker server-side Client
resource settings unless it specifies a longer
period of time.
The value must use nsr_getdate format, for
example:
expiration = 2 Weeks
group
Default
Specifies the backup Group resource that is used

by the NetWorker save program. If not specified,
the Default group is used. To assign a value, set the
parameter, for example:
group = SAPBackup
Note: The group name must match the
corresponding group attribute in the NetWorker
Client resource, see "Group" on page 31.
level_full
Yes
Specifies that a full backup is always performed.

For SAP data, do not change this setting from Yes.
max_logs
Specifies the maximum number of backint session

logs to be saved in the backint log file. If the value
is set to 0, all backup logs will be saved in the log
file. See also the "backint_log" parameter on page
34.
36

Parameter
Default
Description
notify_done
Not specified
UNIX only. Executed at the completion of a backup

or restore session. Uncomment the option and
replace mailx with the name of the command line
e-mail utility to be used as an alert when the
backint program has completed its activity, for
example:
notify_done = mailx -s backint done
root
notify_error
Not specified
UNIX only. Executed at the completion of a failed

backup or restore session. Uncomment the option
and replace mailx with the name of the command
line e-mail utility to be used as an alert if the
backint program encounters any errors during its
activity, for example:
notify_error = mailx -s backint error
root
notify_start
Not specified
UNIX only. Executed at the beginning of a backup

or restore session. Uncomment the option and
replace mailx with the name of the command line
e-mail utility to be used as an alert when the
backint program begins its activity, for example:
notify_start = mailx -s backint start
root
notify_success
Not specified
UNIX only. Executed at the completion of a

successful backup or restore session. Uncomment
the option and replace mailx with the name of the
command line e-mail utility to be used as an alert
when the backint program has successfully
completed its activity, for example:
notify_success = mailx -s backint
success root
37

Parameter
Default
Description
parallelism
Specifies the number of save sets or save streams to

send simultaneously to the NetWorker server.
Typically, this setting should be equal to the sum of
the "target sessions" for all of the devices dedicated
to the NetWorker Module.
Ensure that the NetWorker server is configured to

support this parallelism value or greater, see the
listing for "Server" on page 32.
Note: The Parallelism value will be reduced if it is
greater than the value of the save sets parameter,
provided the ss_group_by_fs parameter is set to
No or not set.
38

Parameter
Default
Description
pool
Default
Specifies the NetWorker media Pool resource,

(defined in the NetWorker server), that receives
backup data from the SAP R/3 server that is
running Oracle. If not specified, the Default pool is
used.
To use a pool other than the Default, uncomment
this parameter and set it equal to the name of the
pool, for example:
pool = SAPData
To use multiple pools to separate data:
1. Create separate init<ORACLE_SID>.utl
parameter files.
2. Use the -r option to specify the parameter
filename to use at the command line when
using brbackup or brarchive.
For example, a pool named ARCHData is used
specifically for archive logs. You can create a
separate parameter file for archive logs, named for
example archiveC11.utl, and set the pool attribute
equal to ARCHData. To use this pool to back up the
archive logs, you would enter the following
command at the command line:
brarchive -u sys/admin -d util_file -r
archiveC11.utl -m all -s save
prev_bk_restore
No
UNIX only. Specifies whether to restore the

previous backup if the required backup cannot be
found, when the query_index parameter is set to
No.
query_index
No
UNIX only (Windows is always Yes). Specifies

whether to query the NetWorker server indexes for
validation of the requested files and backup IDs
before a restore begins. If set to No, the query does
not occur.
39

Parameter
Default
Description
raw_dir
Not specified
Specifies the directory for raw disk partitions. Any

files below these directories are considered to be
raw disk partitions. Do not set the /dev or /devices
directories for raw partitions. They are already
treated as raw devices. To specify the directory,
uncomment this option, and use a semicolon (;) to
separate the directory paths, for example:
raw_dir = /oracle/data;/sap/data;/lotus/data
retry_count
Specifies the number of times that a failed backup

is attempted for each save set. Any integer greater
than 0 is allowed.
savesets
20
To distribute the backup load, a clients files can be

divided among several save sets, as specified by
this value. If the value is equal to or greater than
the number of database files, then a separate save
set is made for each file. If the value is smaller than
the number of database files, then a save set may
contain more than one file.
This value is ignored if the ss_group_by_fs
parameter is set to Yes.
sem_timeout
30
Sets the amount of time, in minutes, that backint

waits for brbackup or brconnect to remove the
semaphore file. If the semaphore file is not deleted,
backint exits with an error at the end of this
timeout period.
server
Local Host
The hostname of the NetWorker server that the

NetWorker Module uses for backup, restore, and
inquiry sessions, for example:
server = prelude
Note: The server name must match the server
attribute specified in the NetWorker Server
resource. If the server parameter is not specified,
then the NetWorker Module backs up data to the
local host.
40

Parameter
Default
Description
ss_group_by_fs
No
If set to Yes, the savesets parameter is ignored and

save sets are grouped by filesystem instead of file
size. This more efficient grouping of files can
improve performance of scheduled backups, index
lookups, and restore times.
ss_size_max
Specifies maximum save set size in megabytes. If

not set, or set to zero, then size is unrestricted.
ssNameFormat
Old
Sets the naming convention for save sets.

If set to Old, then the name for all save sets is
backint:<ORACLE_SID>.
If set to New, then the save set name for each
session differs according to the files being
backed up. It uses the format
backint:<ORACLE_SID>:<full path of the first
filename in the save set>.
If you set each save set to store one file, then a
value of New simplifies the process of browsing
the media database. The media database will
shows each filename as part of the save set name.
Note: If set to New, the NetWorker recover -S
command cannot be used to restore the database,
however the brrestore command can be used.
verbose
No
Provides more detailed information in the log file

from save and recover operations.
41
Task 4: Configure the Backup and Restore Utility
Task 4: Configure the Backup and Restore Utility

Depending on your configuration needs and preferences, you can perform
backups, restores, and inquiries of SAP R/3 data using the SAP BRTools with
or without use of Oracles RMAN utility. The following examples describe a
simple configuration of each of the cases of use with the NetWorker Module.
For the SAP BRTools, see "Example: Configuring backint as the Backup
and Restore Utility" on page 42.
For the Oracle RMAN utility, see "Example: Configuring RMAN as the
Backup and Restore Utility" on page 43.
Example: Configuring backint as the Backup and Restore Utility

The following example describes a simple configuration of BRTools
(specifically the SAPDBA interface and the brbackup, brarchive, and
brrestore commands) to use the backint program for backup, restore, and
inquiry operations. For complete instructions, refer to the appropriate SAP
documentation.
1. With a text editor, open the SAP initialization file, init<ORACLE_SID>.sap,
which is typically located in the following directory:
On Windows: %ORACLE_HOME%\DATABASE
On UNIX: $ORACLE_HOME/dbs
2. Set the backup_dev_type parameter to use the backint program by entering

one of the following:
# backup device type
backup_dev_type = util_file
backup_dev_type = util_file_online
3. Set the util_par_file parameter to point to the NetWorker Modules
parameter file, init<ORACLE_SID>.utl, as follows:
On UNIX or Linux:
# backup utility parameter file
util_par_file = ?/dbs/init<ORACLE_SID>.utl
where ? = $ORACLE_HOME
42
On Microsoft Windows:
# backup utility parameter file
util_par_file = ?\database\init<ORACLE_SID>.utl
where ? = %ORACLE_HOME%
For details on the NetWorker Module parameter file, see "Task 3: Configure
the NetWorker Module Parameters" on page 33.
2
Example: Configuring RMAN as the Backup and Restore Utility
The following example describes a simple configuration of Oracles RMAN
utility (available with Oracle8 or later databases), which works with the
BRTools utilities, for backup, restore, and inquiry operations. For complete
instructions, refer to the appropriate SAP documentation.
1. With a text editor, open the SAP initialization file, init<ORACLE_SID>.sap,
On Microsoft Windows: %ORACLE_HOME%\DATABASE

On UNIX: $ORACLE_HOME/dbs
2. Set the backup_dev_type parameter to use the RMAN utility by entering the
following:
# backup device type
backup_dev_type = rman_util
3. Uncomment the line for the rman_parms parameter and set it to include
each NetWorker software-specific (NSR_*) environment variable that is
appropriate for your backup, restore, and inquiry sessions.
For a list of these environment variables, see Table 21 on page 116. The
environment variable names must be uppercase and use the following
syntax:
rman_parms="ENV=(<var1>=<value>, <var2>=<value>, ...)"
For example:
rman_parms="ENV=(NSR_SERVER=server_name,
NSR_DATA_VOLUME_POOL=pool_name)"
43
Task 5: Configure a Backup of Cluster Data
Task 5: Configure a Backup of Cluster Data

Note: If you are not using a cluster configuration, ignore this task.
The NetWorker Module backs up all Oracle data residing on private disks in a
cluster, or only shared Oracle data residing on a virtual client in a cluster.
To configure a backup of cluster data on SAP R/3 with Oracle systems:
1. Ensure that the NetWorker Module is installed on both physical nodes of
the cluster, but only on the private disks of the nodes. For details on
installing the NetWorker Module, refer to the Legato NetWorker Module for
SAP R/3 with Oracle Installation Guide.
2. Ensure that a NetWorker Client resource is created for each physical node
and for the virtual node.
3. Configure the NetWorker Module parameter file (init<ORACLE_SID>.utl)
with the appropriate client parameter setting for the type of backup you
want:
To back up Oracle data located on a private disk, use the physical

node name as the client name.
To back up Oracle data located on a shared disk that belongs to a
virtual system, use the network name associated with the virtual
system as the client name.
For details on the NetWorker Modules client parameter settings, see
"client" on page 35.
44
Chapter 3: Manual Backups
This chapter describes how to configure and perform manual backups of

either online or offline Oracle database instances residing on a SAP R/3 server
running Oracle. It assumes that you have properly configured the basic
settings for manual backups, described in "Chapter 2: Basic Software
Configuration" on page 29.
This chapter includes the following sections:
"About Manual Backups" on page 45

"Performing an Offline Manual Backup" on page 46
"Performing an Online Manual Backup" on page 47
"Backing Up the Client File Indexes and Bootstrap" on page 49
"Reviewing Backup Session Reports" on page 50
About Manual Backups

You can use the following to perform manual backups:
The SAPDBA menu interface

The brbackup or brarchive command
Oracles RMAN utility, invoked through either SAPDBA or the brbackup
or brarchive command
Each of these methods uses the NetWorker Modules backint program.

Note: PowerSnap operations are not supported for manual backups, and must
be initiated through the nsrsapsv scheduled backup program. For details, see
"Chapter 7: PowerSnap Backups and Restores" on page 75.
45
Performing an Offline Manual Backup
Important: Manual backups do not automatically back up the NetWorker

servers client file index database and the bootstrap save set. Regular backups of
these components are needed to ensure adequate protection for disaster
recovery. For details, see "Backing Up the Client File Indexes and Bootstrap"
on page 49
Performing an Offline Manual Backup

Perform offline backups when network traffic is low, typically in the evenings
or on weekends, because the SAP R/3 services and the Oracle database
instance are not available to users during the backups.
Before you begin an offline backup, ensure the following:
The backup parameters are set in the NetWorker Modules

init<ORACLE_SID>.utl file. For details on configuring backup
parameters, see "Task 3: Configure the NetWorker Module Parameters"
on page 33.
The parameters for the backup device type (backup_dev_type) and backup
utility parameter file (util_par_file) are set in the SAP utilities profile,
init<ORACLE_SID>.sap. For details on configuring the utilities profile,
see "Task 4: Configure the Backup and Restore Utility" on page 42.
The NetWorker server, the SAP R/3 server running Oracle, and the
NetWorker Remote Exec services are all running.
How to Perform an Offline Backup

For complete instructions on how to perform an offline backup, refer to the
following:
46
To perform an offline backup using the SAPDBA menu interface or the

brbackup or brarchive command, refer to the appropriate SAP
documentation.
To perform an offline backup using the RMAN utility, refer to the
appropriate Oracle documentation.
The following is an example of an offline backup using the brbackup

command:
1. Enter the following command:
brbackup -m all -t offline [-d util_file]
The -m all option specifies that the backup mode is to back up the
entire Oracle database instance.
The -t offline option specifies that the backup type is offline.
The (optional) -d util_file option specifies that the NetWorker
Module is to be used for the backup.
For more information on the available brbackup command options,
see "Appendix A: Commonly Used Command Options for brbackup,
brarchive, and brrestore" on page 109.
With this brbackup command, the Oracle database instance is backed up
to the NetWorker server.
2. Back up the client file indexes and bootstrap. For instructions, see "Backing
Up the Client File Indexes and Bootstrap" on page 49.
Performing an Online Manual Backup

An online backup allows users to continue using SAP R/3 services and Oracle
database instances while the Oracle tablespaces on the SAP R/3 server are
being backed up.
Before you begin an online backup, ensure the following:
The backup parameters are set in the NetWorker Modules

init<ORACLE_SID>.utl file. For details on configuring the backup
parameters, see "Task 3: Configure the NetWorker Module Parameters"
on page 33.
The parameters for the backup device type (backup_dev_type) and
backup utility parameter file (util_par_file) are set in the SAP utilities
profile, init<ORACLE_SID>.sap. For details on configuring the utilities
profile, see "Task 4: Configure the Backup and Restore Utility" on page 42.
The NetWorker server, the SAP R/3 server running Oracle, and the
NetWorker Remote Exec services are all running.
The Oracle database instance is in ARCHIVELOG mode. To set an Oracle
database instance to ARCHIVELOG mode, refer to the appropriate
Oracle manual.
47
Performing an Online Manual Backup
How to Perform an Online Backup

For complete instructions on how to perform an online backup, refer to the
following:
To perform an online backup using the SAPDBA menu interface or the

brbackup or brarchive command, refer to the appropriate SAP
documentation.
To perform an online backup using the RMAN utility, refer to the
appropriate Oracle documentation.
The following is a simple example of an online backup using the brbackup

command:
1. Enter the following command:
brbackup -m backup_objects -t online [-d util_file_online]
The -m backup_objects option specifies the objects to be backed up,

where backup_objects is a tablespace, file ID, file ID range, or object list.
The -t online option specifies that the backup type is online.
The (optional) -d util_file_online option specifies that the
NetWorker Module is to be used for the online backup.
For more information on the available brbackup command options,
see "Appendix A: Commonly Used Command Options for brbackup,
With this brbackup command, the selected objects are backed up to the
NetWorker server.
2. Enter the following command to back up the archive redo logs:
brarchive
For more information on the available brarchive command options, see
"Appendix A: Commonly Used Command Options for brbackup,
Note: Archive redo logs are required for an online backup. Without redo
logs, you can recover a database only to the time of its last full backup.
3. Back up the client file indexes and bootstrap. For instructions, see "Backing
Up the Client File Indexes and Bootstrap" on page 49.
48
Backing Up the Client File Indexes and Bootstrap

Unlike scheduled backups, manual backups do not automatically back up the
client file indexes and the NetWorker servers bootstrap file. If you do not
perform regular scheduled backups, you need to protect this vital information
following a manual backup.
Important: The client file indexes and bootstrap record are required for
restoring the data to a database system in the event of a disaster, such as a disk
failure.
To back up the client file indexes and NetWorker server bootstrap file, and
apply browse and retention policies to the client file indexes:
1. Include the client in a Group resource, which you must define in both the
NetWorker Administrator program and the init<ORACLE_SID>.utl file.
(A Group resource can be created even for a single client.) This ensures
that browse and retention policies are applied to the client file indexes
when the savegrp command is entered in step 2.
For more information on how to configure a Group resource with the
NetWorker Administrator program, refer to the Legato NetWorker
Administrators Guide.
Note: If the client is not included in a Group resource, you must perform
step 3 as an additional step to manually run the nsrim command.
2. On the NetWorker server, log in as the root user (UNIX) or administrator
(Windows), and enter the following savegrp command:
savegrp -O -c client_name
where:
-O saves the clients index files and the associated NetWorker
servers bootstrap without backing up the clients database files.
-c client_name specifies the hostname of the SAP R/3 server running
Oracle whose index files are to be backed up.
For more information on the savegrp command, refer to the Legato
NetWorker Command Reference Guide.
49
Reviewing Backup Session Reports
3. If the client is not included in a Group resource (see step 1), apply browse
and retention policies to the client index files by entering the following
nsrim command:
nsrim -c client_name
where -c client_name specifies the hostname of the SAP R/3 server running
Oracle whose index is to be backed up.
For more information on the nsrim command, refer to the Legato
NetWorker Command Reference Guide.
Important: Applying browse and retention policies to SAP R/3 backups

avoids the problems of client file indexes using large amounts of hard drive
space and slow index queries.
3
During backup, the NetWorker Module appends a backup session report to a
log file on each SAP R/3 server running Oracle where the NetWorker Module
resides. This file can be viewed with any text editor.
The default location for all logs is:
On Microsoft Windows: C:\Program Files\Legato\nsr\applogs

On UNIX or Linux: /nsr/applogs
Logs can be written to a different location, using a different name, as specified

in the backint_log, arch_backint_log, or backint_tmpdir parameters. Logs can
be made verbose by setting the verbose parameter. See "verbose" on page 41.
Most NetWorker Module logs can be found by searching for
nsr/applogs/*backint*, nsr/applogs/*sap*, or nsr/applogs/*SAP*.
The default format for the backup reports log filename is as follows:
backint<ORACLE_SID>.log
At the end of each operation in the report, there is a statement of the number
of successfully completed files out of the total number of files.
50
Table 9 on page 51 lists the attributes recorded in a backup, restore, or inquire

session report.
Table 9. Report Attributes for Backup and Restore Sessions
(Part 1 of 2)
Attribute
Description
#BACKUP <backup_id>
<file>
Indicates the ID and filename from a successful

inquiry function.
#ERROR <file>
or
#NOTFOUND <file>
Indicates an unsuccessful backup, restore, or

inquire function and the intended file.
#RESTORED <backup_id> Indicates the ID and filename for each successful

<file>
restore function.
#SAVED <backup_id>
<file>
Indicates the ID and file name for each successful

backup function.
Files
Indicates the number of files to be backed up or

restored in this backup or restore session.
Input File
Indicates the name of the input file containing all

files that backint is requested to back up or
restore. Each requested file is listed under the
message, "Reading input file."
Local Host
Indicates the SAP R/3 server running Oracle that

is associated with the report.
n of m files saved
n of m files restored
n of m files reported
Indicates the number of files (n) successfully

saved, restored, or reported by the NetWorker
program out of the total number of files (m, see
"Files" attribute) intended for the backup or
restore operation.
Backups list two records, one for data and one for
profiles.
Number of Symlinks
(UNIX only)
Indicates the total number of symbolic links

found in the files listed in the Input File.
51
Table 9. Report Attributes for Backup and Restore Sessions

(Part 2 of 2)
52
Attribute
Description
Parallelism
Indicates the parallelism setting that backint uses

when either passing save sets to the NetWorker
server for backup or receiving save sets for
restore.
Params File
Indicates the init<ORACLE_SID>.utl parameter

file that backint uses for backup, restore, or
inquiry of the SAP R/3 with Oracle data.
Processing Parameter
File
Indicates the parameter that backint uses during

the backup, restore, or inquire process. For details
on the NetWorker Module parameters, see
"Task 3: Configure the NetWorker Module
Parameters" on page 33.
Savesets/Sessions
Indicates the number of save sets that backint

sends to the NetWorker server.
Starting
Indicates the backup or restore command, which

is followed by a list of the files that were or were
not successfully backed up or recovered in each
session.
Symlink
(UNIX only)
Specifies the location of a symbolic link associated

with the file backed up or restored. The most
common symbolic link is between the /oracle and
/mnt/oracle directories. During backup, this link is
backed up so that upon recovery the link is
resolved.
User
Indicates the database ID (ORACLE_SID)

associated with the database instance. BRTools
passes this value to backint.
Chapter 4: Scheduled Backups
This chapter describes how to configure scheduled backups of SAP R/3

servers running Oracle. It includes the following sections, which describe
tasks that should be performed in sequence:
"Task 1: Test Basic Settings" on page 53

"Task 2: Configure the Client Resource" on page 54
"Task 3: Encrypt the User Name and Password" on page 57
"Task 4: Configure the Scheduled Backup Configuration File" on page 58
"Reviewing Backup Session Reports" on page 63
Task 1: Test Basic Settings

Before configuring scheduled backups, test the network connections and basic
software settings by performing a successful manual SAP R/3 with Oracle
backup.
For basic settings, see "Chapter 2: Basic Software Configuration" on

page 29.
For manual backup instructions, see "Chapter 3: Manual Backups" on
page 45.
53
Task 2: Configure the Client Resource

Use the NetWorker Administrator program on the NetWorker server to
configure the Client resource for each SAP R/3 server running Oracle to be
scheduled for backup.
For general Client resource settings for the NetWorker Module, review
the listings for "Client" on page 31.
For Client resource settings that are specific to scheduled backups, see
Table 10 on page 54.
All other settings for scheduled backups must be specified in the
NetWorker Modules parameter file and the scheduled backup
configuration file. For more information, see the following:
"Task 3: Configure the NetWorker Module Parameters" on page 33
"Task 4: Configure the Scheduled Backup Configuration File" on
page 58.
Important: Settings in the NetWorker Modules parameter file override any

corresponding settings (including default settings) in the NetWorker Client
resource.
For a complete description of Client resource settings, refer to the Legato

NetWorker Administrators Guide.
Table 10. Client Resource Settings for Scheduled Backups (Part 1 of 2)
Attribute
Description
Save Set
Ensure that the save set name includes the backint

command and is defined in the following format:
backint:ORACLE_SID
For non-PowerSnap usage, this attribute is only
informational, because the nsrsapsv.cfg file determines the
ORACLE_SID parameter. For PowerSnap usage, this
attribute must be specified.
54
Table 10. Client Resource Settings for Scheduled Backups (Part 2 of 2)

Attribute
Description
Backup
Command
Enter the nsrsapsv command in this attribute, with the

-f option and the configuration filename:
nsrsapsv -f filename
where filename is the full pathname of the scheduled
backup configuration file (for example,
/nsr/res/nsrsapsv.cfg). For information on the scheduled
backup configuration file, see "Task 4: Configure the
Scheduled Backup Configuration File" on page 58.
Note: Because the Backup Command attribute is limited to
64 characters, store scheduled backup configuration files in
the following default path:
C:\Program Files\Legato\nsr\res\nsrsapsv.cfg
On UNIX or Linux: /nsr/res/nsrsapsv.cfg
Remote User
On Windows systems only, enter the SAP users operating

system username.
Password
On Windows systems only, enter the password for the

Remote User attribute.
Figure 4 on page 56 provides an example showing part of a Client resource

configuration in the NetWorker Administrator program on a UNIX system.
Note the sample values in the Save Set and Backup Command fields.
55
Figure 4. Example Client Resource on UNIX Systems
56
Figure 5 on page 57 provides an example of a Client resource configuration in

the NetWorker Administrator program on a Windows operating system. Note
the sample values in the Save Set and Backup Command fields.
Figure 5. Example Client Resource on Windows Systems
4
Task 3: Encrypt the User Name and Password
The SAP users operating system username and password and the SAP users
Oracle username and password must be encrypted in the NetWorker
Modules scheduled backup configuration file, nsrsapsv.cfg (or a copy of this
file).
Note: Use a copy of the nsrsapsv.cfg file, and preserve the original file.
To encrypt the SAP users operating system username and password and the
SAP users Oracle username and password:
1. Enter the following at the command line:
nsrsapadm -c filename
where filename is the full pathname of the scheduled backup configuration
file (nsrsapsv.cfg or a copy of this file).
2. Follow the prompt instructions.
57
Task 4: Configure the Scheduled Backup Configuration File

The NetWorker Modules scheduled backup configuration file, named
nsrsapsv.cfg (included with the installation), is a text file that contains
parameters required by the NetWorker nsrsapsv scheduled backup program.
Note: Use a copy of the nsrsapsv.cfg file, and preserve the original file.
Among other things, the nsrsapsv.cfg configuration file is used to:
Identify the SAP Oracle database to be backed up.

Specify the BRTools command used for the scheduled backups.
Encrypt user credentials for logging in to the SAP R/3 server and
connecting to Oracle.
Configure system specific environment variables.
To use this configuration file, its full pathname must be specified in the Backup
Command attribute of the Client resource (see "Backup Command" on
page 55).
Uncomment any parameters in the configuration file that you want to use in
the backup. To set a parameter, use the following format:
parameter = value
Important: Use full pathnames for parameters that specify a path or filename.
Oracle special characters such as ? are not supported. Also environment
variables such as $ORACLE_HOME and %ORACLE_HOME% are not
supported.
58
Table 11 on page 59 lists the parameters and values for the scheduled backup
configuration file, nsrsapsv.cfg, or a copy of this file.
Table 11. Parameters for the NetWorker Module Scheduled Backup Configuration File
(Part 1 of 5)
Parameter
Value
Any name_path=value pair This parameter is used to append values to any environment
variable named name_path (for example, LD_LIBRARY_PATH).
If an environment variable with this name already exists, then
the parameter value listed here is appended to the existing
value for the environment variable.
If an environment variable with this name does not exist, then it
is created.
For example:
LD_LIBRARY_PATH=/export/home/oracle/product/8.1.5/
lib:/usr/openwin/lib
Notes:
For AIX, you must add LIBPATH to the path.
For Tru64, you must add SHLIB_PATH to the path.
This parameter is optional.

Any name=value pair
This parameter is used to add any environment variable named

name. If the environment variable specified by name already exists,
then it is overwritten. For example:
BR_TRACE=1
BR_TRACE is set to 1 in the environment, which instructs
brbackup or brarchive to print out additional trace information.
59
(Part 2 of 5)
Parameter
Value
BR_EXEC
This parameter specifies the brbackup or brarchive command,

with any options that nsrsapsv uses.
Note: Do not use the -u option, which identifies the user name and
password of the Oracle database administrator. Instead, the user
name and password should be encrypted by using the nsrsapadm
-c filename command (see "Task 3: Encrypt the User Name and
Password" on page 57).
For example:
BR_EXEC=brbackup
This is a required parameter.
HOMEDRIVE
Windows only. This parameter specifies the drive name where

Windows system files reside. You can verify this setting by
entering set homedrive in a command window.
For example:
HOMEDRIVE=C:
NLS_LANG
Format the value of this parameter as follows:

LANGUAGE_TERRITORY.CHARACTERSET
For example:
NLS_LANG=AMERICAN_AMERICA.US7ASCII
For more information about this parameter, refer to the Oracle
documentation.
ORACLE_BIN
This parameter specifies the location of the Oracle binaries. The

specified path is appended to the PATH environment variable so
that all Oracle binaries can be found, if needed.
This parameter is required only if the Oracle binaries are not in the
default location, $ORACLE_HOME/bin.
60
(Part 3 of 5)
Parameter
Value
ORACLE_HOME
Set this parameter to the installation path for the Oracle server
software for ORACLE_SID. Use the full pathname.
For example:
ORACLE_HOME=/export/home/oracle/product/8.1.5
ORACLE_SID
This parameter identifies the system identification (SID) for the

Oracle instance to be backed up.
If this parameter is specified, then its value is used for the
Oracle SID.
If the parameter is not specified, then the Oracle SID is derived
from the save set name in the NetWorker Administrators Client
resource for this client.
For example, if the save set name is backint:SAP and you do not
specify ORACLE_SID in the scheduled backup configuration file,
then SAP is used for the Oracle SID.
For example:
ORACLE_SID=SAP
ORACLE_USR_PASSWD This parameter contains the SAP users encrypted Oracle user
name and password. The nsrsapadm -c command creates this
parameter (see "Task 3: Encrypt the User Name and Password" on
page 57).
Do not manually add or edit this parameter; use the nsrsapadm -c
command instead.
OS_USR_PASSWD
This parameter contains the SAP users operating system

username and password. The nsrsapadm -c command creates this
parameter (see "Task 3: Encrypt the User Name and Password" on
page 57).
Do not manually add or edit this parameter; use the nsrsapadm -c
command instead.
61
(Part 4 of 5)
Parameter
Value
PATH
This parameter is used to add more search paths to the PATH

environment variable. The specified value is appended to the
PATH environment variable. You may specify multiple search
paths, using either one of the following methods:
PATH=d:\dir1;d:\dir2;d:\dir1\dir2\dir3
PATH=d:\dir1
PATH=d:\dir2
PATH=d:\dir1\dir2\dir3
SAP_BIN
This parameter specifies the path to the location of the BRTools

binary files. This should also be where the backint (UNIX) or
backint.exe (Windows) executable resides, after it is manually
moved to this location following installation of the NetWorker
Module. This path is added to the PATH environment variable so
that the BRTools binaries and backint can be found.
For example:
SAP_BIN=/usr/sap/SAP/SYS/exe/run
SAP-specific
environment variables:
SAPARCH
SAPREORG
SAPTRACE
SAPCHECK
Windows platforms only. The SAP-specific environment variables

are required for brbackup to run properly on Windows. They are
normally set in the SAP environment on Windows.
For example:
SAPARCH=d:\orant\CER\saparch
SAPREORG=d:\orant\CER\sapreorg
SAPTRACE=d:\orant\CER\saptrace
SAPCHECK=d:\orant\CER\sapcheck
These parameters are required only if they are not set on the
Windows system or need to be overwritten.
62
(Part 5 of 5)
Parameter
Value
SAPBACKUP
This parameter indicates the directory to store backup logs.

BRTools uses this directory to store temporary or log files.
For Windows systems, this is a required parameter.
For UNIX systems, the default value is
$ORACLE_HOME/sapbackup.
SAPDATA_HOME
This parameter specifies the root directory for SAP datafiles. For
details, refer to the SAP documentation.

During a backup session, several reports are written to log files on each SAP
R/3 server running Oracle where the NetWorker Module resides.
Each time the nsrsapsv program is called, a log file is created with the
name nsrsapsv.<process_id>_<ORACLE_SID>, for example,
nsrsapsv.359_CER.
The backint program saves a backup report in the backint log file. The
default log filename is backint <ORACLE_SID>.log.
These log files can be viewed with any text editor. The default location for all
logs is:

The default format for the backint log filename is as follows:

backint <ORACLE_SID>.log
Logs can be written to a different location, using different names, as specified
in the backint_log, arch_backint_log, or backint_tmpdir parameters. For
information on these parameters, see Table 8 on page 34. Logs can be made
verbose by setting the verbose parameter. See "verbose" on page 41.
For a list of backup and restore session report attributes, see Table 9 on page 51.
63
64
Chapter 5: Cloning Save Sets
Cloning is the NetWorker process used to make an exact copy of saved data
(save sets) from a storage volume to a clone volume. You can clone individual
save sets or the entire contents of a storage volume. The cloned volumes are
indistinguishable from the original, except that the volume labels are different.
NetWorker software indexes and tracks clones in both the client file index and
the media database. The NetWorker Module for SAP R/3 with Oracle software
uses the sapclone command to clone save sets.
"Clone Command Syntax and Options" on page 65

"Monitoring the Cloning Process" on page 67
Clone Command Syntax and Options

Save sets generated for the Oracle database ID, ORACLE_SID, using the
NetWorker Module can be cloned by running the sapclone command from
either the NetWorker server or the SAP R/3 server running Oracle. The
sapclone command works with nsrclone to write the cloned data to the
default clone pool, or to a specified clone volume whose pool type is "clone."
Use the following syntax for the sapclone command:
sapclone [-a] [-b pool] [-c client] [-n] [-s server] -u user
Command options in brackets ([ ]) are optional; only the -u option is
mandatory.
Table 12 on page 66 lists the options to use with the sapclone command.
65
Clone Command Syntax and Options
Table 12. The sapclone Options (Part 1 of 2)

Option
Description
Example
-a
Clones all of a clients save sets. If this

option is not specified, the NetWorker
Module only clones save sets created in
the last 24 hours.
sapclone -a -u mikeERC
-b pool
Specifies the pool to which the cloned

save sets are sent. If this option is not
specified, the save sets are sent to the
Default clone pool.
sapclone -b SAPClone -u mikeERC
-c client
Identifies the name of the client whose sapclone -c saturn -u mikeERC

backed up data should be cloned.
NetWorker software uses the client file
index for the specified client to find and
clone the clients data.
Use this option for cloning data backed
up from a cluster. For example, you may
want to set this option to the name of the
clusters virtual node.
-n
Tests the cloning operation on a clients

save sets. When this option is specified,
the cloning operation is not initiated.
sapclone -n -u mikeERC
The example performs a trial cloning

process on the save sets created by
backint in the last 24 hours, with none of
the data being stored onto volumes of a
clone pool.
66
Chapter 5: Cloning Save Sets
Table 12. The sapclone Options (Part 2 of 2)

Option
Description
Example
-s server
Specifies the NetWorker server to which sapclone -s mars -u mikeERC

to clone. You need this option only if one
of the following conditions is true:
You want to clone to a NetWorker
server other than the default server
You enter the sapclone command on a
SAP R/3 server running Oracle.
-u user
Mandatory option. Specifies the ID of

sapclone -u mikeERC
the Oracle database, whose save sets are
to be cloned.
Monitoring the Cloning Process

To enable monitoring of the cloning process, the NetWorker server displays
messages in the NetWorker Administrator program for each save set that is
cloned. Because the cloning process only clones complete save sets, additional
volumes are requested if a save set spans multiple volumes.
Messages generated during the cloning process appear on screen and are
recorded in the NetWorker messages log file in the following location:
On Microsoft Windows C:\Program Files\Legato\nsr\logs

On UNIX or Linux /nsr/logs
For more information on the NetWorker Module and NetWorker error

messages, see "Appendix C: Troubleshooting" on page 123.
67
Monitoring the Cloning Process
68
Chapter 6: Restoring Data
This chapter describes how to restore data that was backed up by the
NetWorker Module. It includes the following sections:
"Reviewing Save Sets" on page 69

"Performing Restores" on page 70
"Restoring SAP R/3 with Oracle Cluster Data" on page 72
"Reviewing Restore Session Reports" on page 72
Note: In the event of a disaster, such as disk failure, refer also to the Legato
NetWorker Disaster Recovery Guide.
Reviewing Save Sets

To review NetWorker save sets in the NetWorker Administrator program:
On UNIX, select Indexes from the Client menu to open the Indexes
window.
On Windows, select the Indexes tab.
Select an entry to review. Each entry displays the ID assigned to the save set,
the number and size of the file, and the date and level of the backup session.
69
Expiration of Save Sets
Expiration of Save Sets

For every client save set backed up, the NetWorker server stores two sets of
records:
One or more records are written to the online client file index for the client
computer and its save set. These records are maintained until the browse
policy for the save set expires.
One record is written to the online media database for the location of the
save sets data on a specific storage media. This record is maintained until
the retention policy for the save set expires.
The expiration for the browse and retention policies must be set in the
NetWorker Modules parameter file. For details, see "Task 3: Configure the
NetWorker Module Parameters" on page 33.
Once the browse and retention policies expire, the backup media is eligible for
recycling and can be overwritten. Until the media is actually overwritten
(relabeled), the data from the media can be restored by using the scanner
command on the NetWorker server.
For a complete description of how NetWorker software uses browse and
retention policies to track data, refer to the Legato NetWorker Administrators
Guide.
Performing Restores
If a SAP R/3 server running Oracle was backed up by using the NetWorker
Module software, then you can restore data to the server by using either the
SAPDBA interface or the brrestore command directly. If a backup was done
with RMAN, then the restore should also be done with RMAN. For
information on restoring with RMAN, refer to the appropriate Oracle
documentation.
A full restore of an entire Oracle database instance restores database files,

redo logs, and control files.
A restore of a single database object, such as a tablespace or datafile,
restores the object you specify, and does not restore redo logs and control
files.
Note: Restore options used with either SAPDBA or the brrestore command
overwrite any corresponding settings in the SAP R/3 initialization file,
init<ORACLE_SID>.sap. For information on using the initialization file, see
"Task 4: Configure the Backup and Restore Utility" on page 42.
70
Important: The brrestore program, whether invoked directly from the

command line or from the SAPDBA interface, first deletes all the original files
to be restored before calling backint to restore the files. If brrestore is unable
to invoke backint for any reason, the original files are lost. Perform an inquiry
of the backup first, before performing a restore.
An alternative is to restore the files to another location, and preserve the
original files. Use the -m parameter, and specify the restore destination, as
follows:
brrestore -m tablespace_name=restore_directory
For more information on restoring to a different location, refer to the
appropriate SAP documentation.
How to Restore a Database or Database Object

To restore an entire database instance or a single database object using either
the SAPDBA interface or the brrestore command:
1. Ensure that the NetWorker server, the SAP R/3 server running Oracle, and
the NetWorker Remote Exec services are running.
2. Shut down the Oracle database instance (for a full restore), or take the
database objects you are restoring offline (for restore of a single database
object).
3. Ensure that either utl_file or rman_utl is configured as the backup device
type in the SAP initialization file, init<ORACLE_SID>.sap. For details, see
"Task 4: Configure the Backup and Restore Utility" on page 42.
4. Ensure that the appropriate NetWorker server, client, and parallelism
settings are configured in the NetWorker Modules
init<ORACLE_SID>.utl file. For details, see "Task 3: Configure the
5. Ensure that the backup you want to restore exists using either SAPDBA or
the brrestore inquire function as follows:
brrestore -verify
71
Restoring SAP R/3 with Oracle Cluster Data
6. Depending on the type of restore you are performing and your restore
method, do one of the following:
To restore an entire database instance:

If using the SAPDBA interface, in the Restore/Recovery window,
select Full Restore.
If using the command line, enter the brrestore command with the
-m full option. See "Syntax and Options for brrestore Command"
on page 113.
To restore a single database object:
If using the SAPDBA interface, in the Restore/Recovery window,
select Restore One Tablespace or Restore Individual Files.
If using the command line, enter the brrestore command with the
-m option to specify a tablespace, file ID, or file ID range. See
"Syntax and Options for brrestore Command" on page 113.
7. For details on applying the applicable redo logs to recover the database,
refer to the related SAP R/3 and Oracle documentation.
For more details on using the SAPDBA interface or the brrestore command,
refer to the appropriate SAP documentation.
Restoring SAP R/3 with Oracle Cluster Data

Restoring data backed up from private disks in a cluster node is similar to
restoring data on a system that is not part of a cluster.
To restore data from a shared disk of a virtual client, set the NetWorker
Modules client parameter to restore files to the virtual client, where the files
originated during the backup. For more information on this parameter, see
"client" on page 35.
Reviewing Restore Session Reports

During restore, the NetWorker Module appends a restore session report to a
log file on each SAP R/3 server running Oracle where the NetWorker Module
resides. This file can be viewed with any text editor.
The default location for all logs is:
72

The default format for the restore reports log filename is as follows:
backint <ORACLE_SID>.log
Logs can be written to a different location using different names, as specified
in the backint_log, arch_backint_log, or backint_tmpdir parameters. For
information on these parameters, see Table 8 on page 34.
For a list of restore session report attributes, see Table 9 on page 51.
73
Reviewing Restore Session Reports
74
Chapter 7: PowerSnap Backups and Restores
This chapter describes how to configure and run PowerSnap backups and
restores of SAP R/3 with Oracle data on supported primary storage devices.
"Requirements" on page 76
"Types of PowerSnap Backups" on page 77
"Types of PowerSnap Restores" on page 79
"PowerSnap Backup and Restore Data Flows" on page 81
"Quick Start" on page 83
"PowerSnap Software Configuration Roadmap" on page 86
"Configuring NetWorker Resources for PowerSnap" on page 87
"Setting the PowerSnap Parameters" on page 89
"Setting Variables in the PowerSnap Configuration File" on page 93
"Invoking PowerSnap Backup Processes" on page 96
"Querying PowerSnap Backup Records" on page 104
"Invoking PowerSnap Restore Processes" on page 105
75
Requirements
Requirements
This section describes the types of environments and software required to use
the PowerSnap features of the NetWorker Module for SAP R/3 with Oracle
software.
Supported Environments
PowerSnap provides continuous point-in-time (PIT), snapshot-based
(immediate live backup) protection and availability of SAP R/3 with Oracle data
on supported primary storage platforms.
To use the PowerSnap features, the NetWorker Module must be used in
conjunction with the Legato NetWorker PowerSnap Module. The PowerSnap
Module creates the snapshots, and the NetWorker Module stores the snapshot
data.
PowerSnap backups must use servers, clients, or storage nodes on supported
platforms only. The supported types of primary storage platforms include, but
are not limited to the following:
EMC CLARiiON
IBM FAStT
STK D Series
Sun StorEdge Availability Suite
For a complete list of supported platforms, refer to the Legato NetWorker

Module for SAP R/3 with Oracle Release Supplement.
The Oracle control file and all SAP directories, except sapdata<n>, should not
be located on a snap volume. For some snapshot platforms, such as STK D
Series or IBM FAStT, this is mandatory. Refer to your snapshot vendor and
corresponding NetWorker PowerSnap documentation.
Note: PowerSnap release 1.0 modules support scheduled backups only.
Manual (client-initiated) backups are not supported.
Required Software Components

PowerSnap backup and restore of SAP R/3 with Oracle data and files require
the following software components:
76
SAP R/3 with Oracle server, which contains BRTools

BRTools or SAPDBA (on the Oracle server)
NetWorker server
NetWorker client (installed on the SAP R/3 with Oracle server and the
PowerSnap client host)
NetWorker Module for SAP R/3 with Oracle software (installed on the
SAP R/3 with Oracle server)
NetWorker PowerSnap Module appropriate for your system (installed on
the SAP R/3 with Oracle server and PowerSnap client host and any data
mover host)
Note: Any PowerSnap client host or data mover host that manages the
secondary storage should have NetWorker storage node software
installed.
For details on the installation requirements, refer to the following:
and Microsoft Windows Version, Installation Guide.
NetWorker PowerSnap Module Installation and Administrators Guide for the
primary storage system.
Types of PowerSnap Backups

This NetWorker Module, in conjunction with the appropriate PowerSnap
Module, supports the types of PowerSnap for SAP R/3 with Oracle backups
summarized in Table 13 on page 77:
Table 13. Summary of Supported PowerSnap Backup Types
Backup Type
Snapshot
Retention
Location of Stored
Data
"Instant Backup" see page 78
Permanent
Snapshot only
"Immediate Live Backup" see page 78 Temporary
Secondary storage
(tape) only
"Deferred Live Backup" see page 79
Both snapshot and

secondary storage
Permanent
The PowerSnap backup type is configured by the Snapshot Policy attribute in

the NetWorker Backup Group, see "Configuring the NetWorker Group
Resource" on page 87.
77
Instant Backup
Instant Backup
An instant backup creates a permanent point-in-time (PIT) copy, or snapshot, of
SAP R/3 with Oracle data. This copy is then stored on the primary storage
system where it is available to the NetWorker Module for performing instant
restores or rollbacks. Instant backups can be scheduled to occur many times in
a single day, with little impact to the SAP R/3 with Oracle Server or network.
A group of SAP R/3 with Oracle datafiles in the snapshot is referred to as a
snap set. The snapshot policy must be configured to control the lifecycle of the
snap set. This policy specifies the frequency of instant backups and how long
snapshots are retained before being recycled. For more information, see
"Configuring the NetWorker Snapshot Policy Resource" on page 87.
Important: Instant backups protect against logical failures only. To protect

against physical media failures, the snapshot must be backed up to secondary
storage, such as tape.
For functional details of an instant backup, see "Instant Backup Processes" on

page 96.
Live Backup
A live backup (also known as "snapshot rollover" or "rollover to tape" backup)
is a tape backup of a previously-created snapshot. This NetWorker Module
supports two types of live backup: immediate live backup, and deferred live
backup.
Immediate Live Backup

Immediate live backup (also known as "serverless snapshot backup" or
"snapshot-based backup") is a process by which a temporary snapshot is
created, and immediately backed up to secondary storage such as tape. The
snapshot is then automatically deleted from the primary storage (and not
available to the NetWorker Module for performing instant restores or
rollbacks).
78
Deferred Live Backup

Deferred live backup is a process by which a permanent snapshot, created on the
primary storage system by an instant backup, is backed up to secondary
(conventional) storage, such as tape. The permanent snapshot is retained on the
primary storage (and available to the NetWorker Module for performing
instant restores or rollbacks) for the period specified by either of the following:
Snapshot expiration policy

Retain SnapShots attribute of the SnapShot Policy for the clients Group
resource.
The Group Snapshot Policy must be configured to enable live backups. For
more information, see "Configuring the NetWorker Snapshot Policy Resource"
on page 87.
Note: A PowerSnap client host that is separate from the Oracle Server host can
be used to move the snapshot to the conventional storage medium such as
tape. The use of a PowerSnap client as a secondary host reduces the demand
on the Oracle Server. The PowerSnap client can be a NetWorker storage node.
For functional details on live backups, see the following:
"Immediate Live Backup Processes" on page 99

"Deferred Live Backup Processes" on page 102
Types of PowerSnap Restores

This NetWorker Module, in conjunction with the appropriate PowerSnap
Module, supports the types of PowerSnap for SAP R/3 with Oracle restores
described in Table 14 on page 79.
Table 14. Summary of Supported PowerSnap Restore Types
Restore Type
Data Retrieved From:
"Instant Restore" see page 80
Mounted snapshot
"Rollback" see page 80
Unmounted snapshot, entirely

restored to source location
"Restore from Secondary Storage" see Secondary storage (no snapshot

page 80
available)
79
Instant Restore
The restore type is specified in the RESTORE_TYPE_ORDER variable in the

user-defined PowerSnap configuration file. See "Setting Variables in the
PowerSnap Configuration File" on page 93.
Instant Restore
An instant restore is the process by which a snapshot that was created by an
instant backup is mounted. This enables its saved data to be retrieved. A
minimal amount of time is required for this type of restore.
For functional details of instant restores, see "Instant Restore and Rollback
Processes" on page 105.
Rollback
A rollback restores the entire snapshot to the source location by using the
hardwares particular capabilities. Relocation during rollbacks is not currently
supported by PowerSnap. To determine if a rollback is supported on a specific
type of hardware, refer to the appropriate NetWorker PowerSnap Module
Installation and Administrators Guide.
Important: Rollbacks are potentially destructive because they overwrite the

entire contents of a snapshot unit, such as a volume or disk.
For functional details of rollbacks, see "Instant Restore and Rollback Processes"
on page 105.
Restore from Secondary Storage

A restore from secondary storage is the process by which a snapshot that was
saved to the secondary storage system is restored from the secondary storage.
The PowerSnap Module software essentially uses the NetWorker recover
program, to retrieve the data.
For functional details on restores from secondary storage, see "Restore from
Secondary Storage Processes" on page 107.
80
PowerSnap Backup and Restore Data Flows

The backup and restore strategy requires knowledge of how the Oracle and
Legato software components all work together, see "Required Software
Components" on page 76.
During a PowerSnap backup of SAP R/3 with Oracle data, the SAP R/3 with
Oracle Server processes interact indirectly with the NetWorker server through
the NetWorker Module and PowerSnap Module software.
1. The SAP brbackup program invokes the NetWorker Module software,
which then communicates with the PowerSnap module.
2. On the SAP R/3 with Oracle server host, the PowerSnap Module takes a
point-in-time snapshot of the Oracle data on the primary storage.
3. If a live backup is performed, the PowerSnap Module moves the SAP R/3
with Oracle data from the snapshot on the primary storage to the
NetWorker server or storage node.
4. The NetWorker server or storage node then stores the Oracle data on the
secondary storage, such as a tape.
5. At the end of the PowerSnap backup, the NetWorker server updates the
online client and media indexes with information about the backup.
For more information about NetWorker server and NetWorker client
programs and services, refer to the Legato NetWorker Administrators Guide.
Data flow and intraprocess communication for SAP R/3 with Oracle
PowerSnap backup and restore is illustrated in Figure 6 on page 82.
For functional details on backup and restore process, see the following topics:
"Invoking PowerSnap Backup Processes" on page 96

"Invoking PowerSnap Restore Processes" on page 105
81
PowerSnap Backup and Restore Data Flows
Figure 6. NetWorker Module PowerSnap Backup and Restore Data Flow

SAP R/3 with
Oracle Server Host
PowerSnap Client
(NetWorker Storage Node)
NetWorker
Server
NetWorker
Client
data
BRTools/
SAP R/3
with Oracle
process
NetWorker
Module
for SAP R/3
with Oracle
NetWorker
Client
PowerSnap
Module
PowerSnap
Module
NetWorker
Server
Storage
Medium
SAP R/3 with
Oracle Datafiles
Point-in-Time Copy
of SAP R/3 with
Oracle Datafiles
Primary Storage
82
Quick Start
The following steps describe typical settings to enable and use the NetWorker
Modules PowerSnap features for backup and restore. To customize your
configuration, use this information in conjunction with more specialized
information described in "PowerSnap Software Configuration Roadmap" on
page 86.
Note: Before running the test included in this procedure, back up the test
database. Test on a nonproduction database.
To configure and test the PowerSnap features for a typical configuration:
1. Ensure that the NetWorker Group to which the NetWorker Module
belongs has the proper PowerSnap attribute settings, as listed in Table 15
on page 83.
Table 15. Backup Groups PowerSnap Attributes
Attribute
Setting
Snapshot
True
Snapshot Policy
Serverless is recommended for this testing. If needed,

daily or other customized policies can be used later.
Snapshot Pool
Selecting a Pool resource dedicated to storing snapshot

operation metadata is recommended. File type volume
devices are strongly recommended over tape.
Start Time
Must be set in relation to the Number of Snapshots

attribute for the snapshot policy:
(Interval x Number of Snapshots) must be less than or
equal to (24:00 h - Start Time).
Interval
Must be set in relation to the Number of Snapshots

attribute for the snapshot policy.
83
Quick Start
2. Modify the NetWorker Modules init<ORACLE_SID>.utl file to enable the

PowerSnap parameters and variables.
A typical and recommended configuration is as follows:
ps_backup_mode = yes
ps_archive_mode = no
ps_restore_mode = yes
ps_inquire_mode = yes
ps_exclude_backup_bi_run_nums = 2
ps_exclude_archive_bi_run_nums = 1;2
ps_exclude_backup_paths = (leave blank)
ps_exclude_archive_paths = (leave blank)
ps_ps_before_nonps = yes
ps_group_objs = yes
ps_opaque_pfilename = /nsr/res/nmsapps.cfg
Descriptions of these parameters are listed in Table 16 on page 89.
3. Create and edit the PowerSnap configuration file by using an appropriate
filepath and name, for example:
On UNIX: /nsr/res/nmsapps.cfg
On Microsoft Windows: C:\Program Files\Legato\nsr\res\nmsapps.cfg
Include any parameters required or intended for use with the installed
PowerSnap Module, for example:
NSR_SNAP_TYPE = sunii
NSR_PS_DEBUG_LEVEL = 9
NSR_VERBOSE = true
Debug level is intended for technical support diagnostics only. For more
information on the nmsapps.cfg files contents, refer to the NetWorker
PowerSnap Module Installation and Administrators Guide.
4. Test the clients group snapshot settings by invoking the savegrp
command.
a. From the NetWorker server nwadmin program, open the Group

resource.
b. In the Autostart attribute, select Enabled.
c. In the Start Time attribute, enter a time that is one or two minutes
later than the current time.
d. Click Apply, or invoke the savegrp command from the command
prompt as follows:
savegrp -c clientname grpname
84
The backup test is successful if the backint log reports the following
message:
n of n PS files reported
where n is the number of files requested that reside on a PowerSnap disk.
Note: If you encounter a problem, check the NetWorker Modules backint
log file for PowerSnap related messages. Some common problems include:
The target file is not managed by the PowerSnap Module.

The PowerSnap Module daemon or service, nsrpsd, is not running.
The PowerSnap powersnap.res configuration file needs to be modified.
The ps_xxx_mode or ps_exclude_xxx parameter (where xxx is
specified as described in Table 16 on page 89) is set to exclude a file
from PowerSnap processing.
The ps_opaque_pfilename file needs to be modified.
For further troubleshooting, enable the following parameters in the
init<ORACLE_SID>.utl file to generate diagnostic logs for Technical
Support:
debug_level = 9
nsr_debug_msg = yes
verbose = yes
To obtain PowerSnap logs, also specify the following in the

ps_opaque_pfilename file:
NSR_PS_DEBUG_LEVEL=9.
To obtain more detailed SAP_PS_ERROR error and related messages,
re-run your test.
5. Run a pre-restore inquiry with the following command:

brrestore -verify
6. Test a restore with the following command:
brrestore
The restore test is successful if a backint log reports the following
message:
n of n PS files reported
where n is the number of files requested that reside on a PowerSnap disk.
85
PowerSnap Software Configuration Roadmap
PowerSnap Software Configuration Roadmap

Before you configure the PowerSnap features, ensure that both the NetWorker
Module for SAP R/3 with Oracle and the required PowerSnap Module
software are installed according to the instructions in the following
documentation:
Legato NetWorker Module for SAP R/3 with Oracle Installation Guide
NetWorker PowerSnap Module Installation and Administrators Guide
(Refer to the PowerSnap Module version for the primary storage system.)
To configure the PowerSnap features, complete the following sets of

procedures:
1. Use the instructions in "Chapter 2: Basic Software Configuration" to
configure the NetWorker Server, Client, Device, and other resources.
2. For live SAP R/3 with Oracle backups, configure a Device resource for
each secondary storage device (such as a tape) to be used during backups.
The devices must be mounted.
3. Configure the SAP R/3 with Oracle database layout to position the
datafiles on the primary storage supported by the specific PowerSnap
Module.
4. Use the instructions in "Chapter 4: Scheduled Backups" to configure the
basic scheduled backup.
5. Complete the procedure: "Configuring NetWorker Resources for
PowerSnap" on page 87.
6. Complete the procedure: "Setting the PowerSnap Parameters" on page 89.
7. Complete the procedure: "Setting Variables in the PowerSnap
Configuration File" on page 93.
86
Configuring NetWorker Resources for PowerSnap

Configure the following NetWorker resources as described in this section:
SnapShot Pool resource

SnapShot Policy resource
Group resource
Client resource
Configuring the NetWorker Snapshot Pool Resource

Configure a separate snapshot pool to support PowerSnap for SAP R/3 with
Oracle backups. The PowerSnap Module stores the metadata from the
snapshot in this pool. Use the same configuration method as for a regular
NetWorker Module for SAP R/3 with Oracle backup. However, the specified
backup device should be a file or advanced file type.
Specify the pool name in the Snapshot Pool attribute of the NetWorker Group
resource as described in "Configuring the NetWorker Group Resource" on
page 87.
For more information on configuring this extra pool, refer to the appropriate
NetWorker PowerSnap Module Installation and Administrators Guide.
Configuring the NetWorker Snapshot Policy Resource

A NetWorker snapshot policy must be configured to perform either instant or
live PowerSnap for SAP R/3 with Oracle backups. You can either specify a
preconfigured policy, or create a new one.
Configure a NetWorker Snapshot Policy resource by using the instructions in
the appropriate NetWorker PowerSnap Module Installation and Administrators
Guide.
7
Configuring the NetWorker Group Resource
For PowerSnap for SAP R/3 with Oracle backups, configure a NetWorker
Group resource by using the instructions in the appropriate NetWorker
87
Configuring the NetWorker Client Resource
Configuring the NetWorker Client Resource

The basic NetWorker Client resource for the NetWorker Module for SAP R/3
with Oracle is configured according to the settings described in "Task 2:
Configure the Client Resource" on page 54.
Only members of a NetWorker user group with the Change Security Settings
privilege can set the Remote Access attribute in the Client resource.
The Browse Policy attribute in the Client resource, which is superseded by the
init<ORACLE_SID>.utl expiration parameter, applies only to the NetWorker
client file index entries for these types of backups:
Backups that reside on secondary storage (live backups).

Backups not performed by the PowerSnap Module.
The Retention Policy attribute in the Client resource, which is superseded by

the init<ORACLE_SID>.utl expiration parameter, applies only to the
NetWorker media database entries for these types of backups:
Live backups.
Backups not performed by the PowerSnap Module.
The life cycle of a snapshot (instant backup) is governed by the snapshot policy
specified in the clients Group resource.
88
Setting the PowerSnap Parameters

PowerSnap parameters are set in the NetWorker Module for SAP R/3 with
Oracle init<ORACLE_SID>.utl file. These settings assume that the PowerSnap
Module is installed and licensed.
Descriptions of the PowerSnap parameters for the NetWorker Module for SAP
R/3 with Oracle are listed in Table 16 on page 89.
Table 16. PowerSnap Parameters in init<ORACLE_SID>.utl File (Part 1 of 4)
PowerSnap Parameter
Default
Value Description
ps_backup_mode
No
ps_archive_mode
Each of these PowerSnap functional modes is

enabled if set to Yes.
Normally, all the modes are set together to
either all Yes or all No, except
ps_archive_mode=no and all others =yes. Do
not use any other settings except for diagnostic
purposes.
ps_restore_mode
ps_inquire_mode
PowerSnap save sets are named using the

following format: backint:<SID>:PS:.
ps_opaque_pfilename
Null
Absolute pathname of a backint parameter file

that passes values to the PowerSnap module.
For details, refer to the appropriate PowerSnap
module documentation. This setting is
mandatory if the PowerSnap functional mode
parameters are enabled.
PowerSnap parameters are specified in this
parameter file in "x = y" lines, for example:
NSR_SNAP_TYPE = sunii
89
PowerSnap Parameter
Default
Value Description
ps_exclude_backup_bi_run_nums Null
ps_exclude_archive_bi_run_nums
Specifies which backint runs are to be excluded

from PowerSnap processing (typically run
number 2). Parameter files, SAP backup catalog
files, and other files that do not benefit from
PowerSnap processing can be backed up by
conventional processing without PowerSnap,
thereby saving valuable snapshot disk
resources.
Specify a value of one or more valid backint
run numbers to exclude, each separated by a
semicolon (;).
Important! The following starting values are
strongly recommended:
ps_exclude_backup_bi_run_nums=2
ps_exclude_archive_bi_run_nums=1;2
Each brbackup or brarchive session invokes
multiple backint processes sequentially, for
example run number 1 followed by run number
2. If run 2 is excluded, then run 1 backs up the
database datafiles exclusively by using
PowerSnap, and run 2 forces files that do not
benefit from PowerSnap processing, to be
backed up by conventional processing without
PowerSnap.
90
PowerSnap Parameter
Default
Value Description
ps_exclude_backup_paths
Null
ps_exclude_archive_paths
Specifies individual PowerSnap files to exclude

from PowerSnap processing, but to back up
with conventional non-snapshot processing
instead. PowerSnap files are those on a
snapshot-capable file system that NetWorker is
aware of.
Valid values are any full path string, including
standard wildcard characters. Use values that
are based on the actual filenames that BRTools
passes to backint.
Note:
On Windows systems, support of wildcard
characters is limited, and a single trailing *
denotes simple case-insensitive prefix
matching. Thus X:\DB01\FOO.DBF will be
excluded from PowerSnap backups if the
parameter is set to a value of:
X:\*, or X:\db*, or X:\DB01\*
On UNIX systems, wildcard support follows
standard shell support for full file pathnames.
For example the file /db01/foo.dbf is excluded if
the parameter is set to a value of:
/db01/foo.*, or /db??/*.dbf,
but not excluded if set to /db*.
Specify one or more valid, full pathnames, each
separated by a semicolon (;).
Whenever possible, preference should be given
to setting the ps_exclude_xxx_bi_run_nums
parameters instead of using these parameters.
91
PowerSnap Parameter
Default
Value Description
ps_ps_before_nonps
Yes
Specifies whether to perform all PowerSnap

processing before conventional processing
without PowerSnap. This helps prevent
potential resource conflicts.
Setting this value to No enables concurrent
processing of all files set for backup, archive, or
restore.
Note: The No value is not recommended and is
done at the users own discretion.
ps_group_objs
Yes
Specifies whether to group all session files for

each PowerSnap operation, such as prepare or
sync, snapshot or split, save or restore, or
postpare.
Setting this value to Yes improves the
NetWorker Module performance for certain
database disk or filesystem configurations,
particularly if large numbers of files are
processed by BRTools and PowerSnap with
util_file_online.
However, grouping files also reduces the
potential parallelism for certain backup and
restore suboperations, which in turn can reduce
performance.
Setting this value to Yes is also intended for use
with BRTools 6.10 and later, offline and
util_file_online, for example:
brbackup -t offline -d util_file_online
92
Setting Variables in the PowerSnap Configuration File

The PowerSnap parameters that do not directly belong to the NetWorker
Module for SAP R/3 with Oracle program must be set as variables in a
user-defined PowerSnap configuration file, for example: nmsapps.cfg. This file
must be specified by its complete file pathname in the ps_opaque_pfilename
parameter in the init<ORACLE_SID>.utl file.
The configuration file must list a separate line for each variable setting by
using the following format:
var_name=var_value
where:
var_name is the variable name, such as RESTORE_TYPE_ORDER.

var_value is the variable value, such as pit.
Commonly-used PowerSnap environment variables are listed in Table 17 on

page 93. For a complete list, refer to the appropriate NetWorker PowerSnap
Module Installation and Administrators Guide.
PowerSnap variables that have settings equivalent to NetWorker Module
parameters are listed separately in Table 18 on page 95.
Table 17. Commonly-Used PowerSnap Module Environment Variables (Part 1 of 2)
PowerSnap Variables
Description
Default and Valid Values
NSR_DATA_MOVER
Mandatory if the PowerSnap

backup uses a live backup host
different from the PowerSnap
client host (NSR_CLIENT).
Specifies the hostname of the
PowerSnap backup host.
Local host (default).

The valid hostname of the
secondary live backup host.
NSR_MAX_STREAMS
Optional. Specifies the

maximum number of restore
streams.
NSR_PS_DEBUG_LEVEL Optional. PowerSnap debug

level.
Note: The NSR_CLIENT

PowerSnap variable must always
be set to the original brbackup or
brarchive host,
init<ORACLE_SID>.utl client
value.
Defaults to the parallelism
value set in the
init<ORACLE_SID>.utl file, or
its default value of 8.
An integer value.
Valid values are 0 to 9. Default
value is 1.
93
Setting Variables in the PowerSnap Configuration File
Table 17. Commonly-Used PowerSnap Module Environment Variables (Part 2 of 2)

PowerSnap Variables
Description
NSR_PS_SAVE_
PARALLELISM
Defaults to the parallelism

Optional. Specifies the
value set in the
maximum number of
concurrent save streams on the init<ORACLE_SID>.utl file, or
its default value of 8.
PowerSnap client host.
An integer value.
NSR_SNAP_TYPE
Optional. Specifies snapshot

platforms and releases, when
multiple snapshot platforms
are used.
Value should be a concatenated

string, delimited by a colon (:), for
example:
Emctimefinder 4.5.6:EmcClarion
1.2.3:LSIMetaStor 3.4.5
RESTORE_TYPE_ORDER Optional. Specifies the type of

restore to be performed.
One or more of the following

values, with each value delimited
from the others by a colon(:):
pit - Specifies an instant
(point-in-time) restore.
conventional - Specifies a
restore from secondary storage
media.
rollback - Specifies a rollback
restore from a PIT copy.
Note: If multiple values are

specified, each type of restore
is attempted, in the order
specified, until a restore
operation is successful.
The default value is

pit:conventional
Note: For the NetWorker Module,
a rollback operation aborts if one
of the following occurs:
If brrestore file relocation is
specified.
If nonrequested files exist in the
brrestore-requested filesystems.
(These files could become
corrupted after a rollback.)
94
PowerSnap Use of Equivalent NetWorker Module Parameters

Some parameters used by PowerSnap are the same as those used in
conventional backup and restore operations and are inherited from the
init<ORACLE_SID>.utl file. Normally, these equivalent parameters should not
be specified as variables in the PowerSnap configuration file. See Table 18 on
page 95.
Table 18. PowerSnap Use of Equivalent NetWorker Module Parameters
PowerSnap variables in the
ps_opaque_pfilename parameter
Equivalent parameter in the

init<ORACLE_SID>.utl file
NSR_CLIENT
client (must match if NSR_CLIENT is used)
NSR_SERVER
server (must match if NSR_SERVER is used)
NSR_GROUP
group (must match if NSR_GROUP is used)
NSR_SAVESET_EXPIRATION
expiration
NSR_COMPRESSION
compress
NSR_ENCRYPTION
encrypt
NSR_CHECKSUM
checksum
NSR_PS_SAVE_PARALLELISM
parallelism
NSR_MAX_STREAMS
parallelism
NSR_DATA_VOLUME_POOL
pool
95
Invoking PowerSnap Backup Processes
Invoking PowerSnap Backup Processes

A PowerSnap for SAP R/3 with Oracle backup is started by automatically or
manually invoking the scheduled NetWorker backup group on the NetWorker
server. For information on how to invoke a scheduled backup, refer to the
NetWorker PowerSnap Module Installation and Administrators Guide.
Note: A PowerSnap backup should not be started by directly invoking the
client-side BRTools commands or SAPDBA.
There are three types of scheduled PowerSnap backup processes, which are
summarized in the following sections:
"Instant Backup Processes" on page 96

"Immediate Live Backup Processes" on page 99
"Deferred Live Backup Processes" on page 102
Instant Backup Processes

An instant backup creates a permanent snapshot copy of SAP R/3 with Oracle
data that is retained on the primary storage system, where it is available to the
NetWorker Module for performing instant restores or rollbacks. An instant
backup is performed as follows:
1. At the backup start time, the main NetWorker service, nsrd, invokes the
savegrp program to start the groups backup.
2. The savegrp program requests that the NetWorker client-side service,
nsrexecd, on the SAP R/3 with Oracle Server host run the savefs program
to validate the client.
3. If the savefs program succeeds, the savegrp program starts the
PowerSnap program, nsrsnap, on the SAP R/3 with Oracle Server host.
Otherwise, the backup fails.
4. If an existing snapshot needs to be removed (for example, it is due to be
recycled according to the snapshot policy), the nsrsnap program invokes
the nsrsnapck program, which removes both the snapshot from the
storage system and the corresponding NetWorker file and media index
entries. File and media index entries are removed only if the snapshot was
not backed up to tape.
Note: If the existing snapshot was not backed up to tape, there will be
invalid records in the BRTools sapbackup catalog that do not correspond
to any file index entries for the snapshots, because they were deleted by
nsrsnapck processing. A subsequent brrestore attempt, without prior
96
verification, results in an expected "#NOT FOUND" message for all

requested files. Run the brrestore -verify command before running
Snapshot Policies that do not back up to tape.
This message does not appear if you run brrestore for either of the
following:
The most recent backup.
An earlier backup that had its snapshot backed up to the tape.
5. The nsrsnap program contacts the nsrexecd service, which starts the
nsrsapsv program for the scheduled backup.
6. The nsrsapsv program sets the required environment variables and
invokes the brbackup or brarchive program.
7. The brbackup or brarchive program starts the NetWorker Modules
backint program for the SAP R/3 with Oracle backup.
8. The backint program contacts the PowerSnap master program, nsrpsd, to
perform the instant backup.
PowerSnap processes create the snapshot that comprises the backup.

The nsrmmd service stores metadata (used only by the PowerSnap
Module) about the snapshot on the media configured for the
snapshot pool, typically on a file or disk type device.
The nsrmmd service records tracking information about the
point-in-time metadata in the NetWorker media database by using
the nsrmmdbd service.
The nsrindexd service records tracking information about each file
name in the NetWorker client file index. The client index contains one
entry per datafile.
BRTools records the backup entry in its sapbackup catalog.
9. The brbackup or brarchive program calls the NetWorker Module a

second time to invoke backup processes for non-datafiles, for example
init<ORACLE_SID>.sap, that do not benefit from PowerSnap processing.
This extra backup is configured to be a conventional backup without
PowerSnap by the following setting in the init<ORACLE_SID>.utl
parameter file:
ps_exclude_xxx_bi_run_nums = 2
where xxx is backup or archive. For configuration details, see Table 16 on
page 89.
97
Instant Backup Processes
10. If the Snapshot Policy resource specifies that the snapshot must be copied
to secondary storage, the nsrsnap program performs the steps in
"Deferred Live Backup Processes" on page 102.
Note: The snapshot is not deleted from the primary storage.
11. The savegrp program backs up the NetWorker server bootstrap and SAP
R/3 with Oracle client file indexes.
Figure 7 on page 98 shows how the Oracle Server and NetWorker processes
interact during a scheduled instant backup.
Figure 7. Scheduled Instant Backup Processes
SAP R/3 with
Oracle Server
(NetWorker Client)
PowerSnap Client
NetWorker
Server
Primary Storage
SAP R/3
Point-in-Time Copy
with Oracle
of SAP R/3 with
Datafiles
Oracle Datafiles
Client File Index
data
tracking
information
green fill
indicates
NetWorker
Module
elements
PowerSnap
processes
PowerSnap
processes
nsrindexd
Media Database
backint
brbackup
or brarchive
nsrsapsv
nsrpsd
nsrexecd
violet fill
indicates
PowerSnap
elements
white fill
indicates
NetWorker
and Oracle
elements
nsrsnap
nsrsnapck
nsrmmd
nsrmmdbd
Snapshot
Pool Media
nsrexecd
nsrd
savegrp
interprocess communication
savefs
Start
Here
98
Immediate Live Backup Processes

An immediate live backup creates a temporary snapshot copy of the SAP R/3
with Oracle data on the primary storage, which is then immediately backed up
to secondary storage, such as tape. The snapshot is then automatically deleted
from the primary storage, and is not available for instant restores or rollbacks.
This process involves the following sequence:
Note: The first seven steps are the same as those in "Instant Backup Processes"
on page 96.
1. At the backup start time, the main NetWorker service, nsrd, invokes the
savegrp program to start the groups backup.
2. The savegrp program requests that the NetWorker client-side service,
nsrexecd, on the SAP R/3 with Oracle Server host run the savefs program
to validate the client.
3. If the savefs program succeeds, the savegrp program starts the
PowerSnap program, nsrsnap, on the SAP R/3 with Oracle Server host.
Otherwise, the backup fails.
4. If an existing snapshot needs to be removed (for example, it is due to be
recycled according to the snapshot policy), the nsrsnap program invokes
the nsrsnapck program, which removes both the snapshot from the
storage system and the corresponding NetWorker file and media index
entries. File and media index entries are removed only if the snapshot was
not backed up to tape.
Note: If the existing snapshot was not backed up to tape, there will be
invalid records in the BRTools sapbackup catalog that do not correspond
to any file index entries for the snapshots, because they were deleted by
nsrsnapck processing. A subsequent brrestore attempt, without prior
verification, results in an expected "#NOT FOUND" message for all
requested files. Run the brrestore -verify command before running
Snapshot Policies that do not back up to tape.
This message does not appear if you run brrestore for either of the
following:
The most recent backup.
An earlier backup that had its snapshot backed up to the tape.
5. The nsrsnap program contacts the nsrexecd service, which starts the
nsrsapsv program for the scheduled backup.
6. The nsrsapsv program sets the required environment variables and
invokes the brbackup or brarchive program.
99
Immediate Live Backup Processes
7. The brbackup or brarchive program starts the NetWorker Modules

backint program for the SAP R/3 with Oracle backup.
8. The backint program contacts the PowerSnap master program, nsrpsd, to
perform the immediate live backup.
PowerSnap processes create the snapshot, move the data to

secondary storage, and then delete the snapshot from the primary
storage.
The nsrmmd service records tracking information about the
secondary storage save sets in the NetWorker media database by
using the nsrmmdbd service.
The nsrindexd service records tracking information for each backup
piece name and for each stored operating system datafile in the
NetWorker client file index. The client index contains two entries per
datafile.
BRTools records the backup entry in its sapbackup catalog.
9. The brbackup or brarchive program calls the NetWorker Module a second

time to back up backup processes for non-data files, for example
init<ORACLE_SID>.sap, that do not benefit from PowerSnap processing.
This extra backup is configured to be a conventional backup without
PowerSnap by the following setting in the init<ORACLE_SID>.utl
parameter file:
ps_exclude_xxx_bi_run_nums = 2
where xxx is backup or archive. For configuration details, see Table 16 on
page 89.
10. The savegrp program backs up the NetWorker server bootstrap and
Oracle client file indexes.
Figure 8 on page 101 shows how the Oracle server and NetWorker processes
interact during a scheduled immediate live backup.
100
Figure 8. Scheduled Immediate Live Backup

SAP R/3 with
Oracle Server
(NetWorker Client)
PowerSnap Client
NetWorker
Server
Primary Storage
SAP R/3
Point-in-Time Copy
with Oracle
of SAP R/3 with
Datafiles
Oracle Datafiles
Client File Index
data
green fill
indicates
NetWorker
Module
elements
tracking
information
PowerSnap
processes
nsrsapsv
nsrpsd
nsrexecd
violet fill
indicates
PowerSnap
elements
white fill
indicates
NetWorker
and Oracle
elements
nsrmmd
Secondary
Storage Meduim
nsrsnap
nsrsnapck
nsrindexd
Media Database
backint
brbackup
or brarchive
PowerSnap
processes
nsrd
savegrp
nsrexecd
savefs
nsrmmdbd
Start
Here
101
Deferred Live Backup Processes
Deferred Live Backup Processes

A deferred live backup creates a permanent snapshot copy of the SAP R/3 with
Oracle data on the primary storage system, which is then backed up to
secondary storage system, such as tape. The snapshot is retained on the
primary storage for the period specified by either of these snapshot policy
attributes for the clients Group resource:
SnapShot Expiration Policy

Retain Snapshots
A scheduled, deferred live backup can be run in one of the following ways:
Automatically as part of a scheduled NetWorker Module backup.

Manually by using the nsrsnapadmin command.
The Backup Snapshots attribute of the Snapshot Policy resource specifies the
preferred method. For more information, refer to the appropriate NetWorker
A scheduled deferred live backup uses the following process:
1. The nsrsnap or nsrsnapadmin program invokes the PowerSnap processes
to copy the snapshot to secondary storage.
Note: The snapshot is not deleted from the primary storage.
2. The nsrmmd service records tracking information about the deferred live
backup in the NetWorker media database by using the nsrmmdbd service.
3. The nsrindexd service records tracking information for each stored
operating system datafile in the NetWorker client file index.
interact during a scheduled deferred live backup.
102
Figure 9. Scheduled Deferred Live Backup

SAP R/3 with
Oracle Server
(NetWorker Client)
PowerSnap Client
NetWorker
Server
Primary Storage
SAP R/3
Point-in-Time Copy
with Oracle
of SAP R/3 with
Datafiles
Oracle Datafiles
Client File Index
Start
Here
tracking
information
interprocess
communication
PowerSnap
processes
nsrindexd
data
nsrsnap (at end

of savegrp) or
nsrsnapadmin
violet fill
indicates
PowerSnap
elements
nsrexecd
white fill
indicates
NetWorker
elements
Media Database
nsrmmd
nsrmmdbd
Secondary
Storage Meduim
103
Querying PowerSnap Backup Records
Querying PowerSnap Backup Records

The NetWorker server records information about each backup in its online
indexes. The index entry for a NetWorker Module for SAP R/3 with Oracle
PowerSnap backup is stored in the NetWorker client file index for the SAP R/3
with Oracle Server host, under the new "saporacle" namespace (instead of the
"backup" namespace, which is used for regular NetWorker Module for SAP
R/3 with Oracle backups).
For NetWorker release 7.1 or later, you can query the online NetWorker
indexes by using the NetWorker commands, nsrinfo and mminfo.
To query the NetWorker client file index, enter the nsrinfo command.
This displays BRTools file BIDs, for example:
nsrinfo [-v] -n saporacle -s NetWorker_server client
where client is your SAP R/3 with Oracle server hostname.
To query the NetWorker media database, enter the mminfo command.
For example:
mminfo [-v] [-N backint:<ORALCE_SID>:PS:] -s
NetWorker_server -c client
where client is your SAP R/3 with Oracle server hostname.
NetWorker Module for SAP R/3 with Oracle PowerSnap save sets all have the
following save set format:
backint:<ORACLE_SID>:PS:
Note: The mminfo command does not display BRTools BIDs or save times for
files that were backed up with the PowerSnap Module.
For more information on these NetWorker commands, refer to the NetWorker
Command Reference Guide and the UNIX man pages.
104
Invoking PowerSnap Restore Processes

NetWorker Module for SAP R/3 with Oracle restores are performed with
either the brrestore command or the SAPDBA interface, each of which
ultimately calls the NetWorker Modules backint program. For PowerSnap
restores, the backint program interacts with both the PowerSnap and
NetWorker Modules.
For descriptions of the processes involved, see the following:
"Instant Restore and Rollback Processes" on page 105

"Restore from Secondary Storage Processes" on page 107
Instant Restore and Rollback Processes

Both instant restores and rollbacks use the permanent snapshot created by an
instant backup or as part of a deferred live backup.
For an instant restore, the snapshot copy is mounted and the files are
copied as needed.
For a rollback, the entire snapshot is moved to the source destination by
using the appropriate commands for the specific platform.
Instant restores and rollbacks use the following process:

1. The NetWorker Modules backint program verifies the existence of the
requested files versions through the nsrindexd service.
2. The backint program contacts the PowerSnap master program, nsrpsd, on
the Oracle Server host.
3. The nsrpsd program works with other PowerSnap and NetWorker
programs to access the instant backup copy on the primary storage or
retrieve the data from secondary storage, and perform the restore
operation.
PowerSnap processes retrieve the snapshot metadata stored on the

device associated with the snapshot pool by using the nsrmmd and
nsrmmdbd processes.
PowerSnap processes do one of the following, depending on the

RESTORE_TYPE_ORDER setting, see Table 17 on page 93:
For an instant restore, mount the snapshot and copy the files into
a destination requested by the NetWorker Module.
For a rollback, execute the command (specific to the primary
storage system) to move the entire snapshot unit into the source
destination.
105
Instant Restore and Rollback Processes
Once the required SAP R/3 with Oracle files are restored, a database
administrator can complete the standard SAP R/3 with Oracle database
recovery.
Figure 10 on page 106 shows how the Oracle server and NetWorker processes
interact during an instant restore or rollback.
Figure 10. Instant Restore or Rollback
SAP R/3 with
Oracle Server
(NetWorker Client)
PowerSnap Client
NetWorker
Server
Primary Storage
SAP R/3
Point-in-Time Copy of
with Oracle
SAP R/3 with Oracle
Datafiles
Datafiles
Client File Index
data
(for details on
data flow, see
description)
Start
Here
tracking
information
brrestore/
brrecover
PowerSnap
module
PowerSnap
module
nsrindexd
backint
nsrexecd
green fill
indicates
NetWorker
Module
elements
Media Database
nsrpsd
nsrexecd
violet fill
indicates
PowerSnap
elements
white fill
indicates
NetWorker
and Oracle
elements
nsrmmd
nsrmmdbd
SnapShot
Pool Media
nsrd
106
Restore from Secondary Storage Processes

A restore of a PowerSnap backup from secondary storage uses the following
process:
1. The NetWorker Modules backint program verifies the existence of the
requested files versions through the nsrindexd service.
2. The backint program contacts the PowerSnap master program, nsrpsd, on
the Oracle Server host.
3. The nsrpsd program works with other PowerSnap and NetWorker
programs to retrieve the data from secondary storage, and perform the
restore operation.
PowerSnap processes restore the files (save sets) into a destination
requested by the NetWorker Module. The processes use the nsrmmd and
nsrmmdbd programs to do the following:
Determine which media contain the requested save sets.
Read the backup volumes.
4. Once the required SAP R/3 with Oracle files are restored from the backup
volumes, a database administrator can complete the standard SAP R/3
with Oracle database recovery.
interact during a restore from secondary storage.
107
Restore from Secondary Storage Processes
Figure 11. Restore from Secondary Storage

SAP R/3 with
Oracle Server
(NetWorker Client)
PowerSnap Client
NetWorker
Server
Primary Storage
Oracle
Datafiles
Client File Index
Start
Here
data
tracking
information
brrestore/
brrecover
PowerSnap
module
nsrindexd
backint
nsrpsd
nsrexecd
green fill
indicates
NetWorker
Module
elements
violet fill
indicates
PowerSnap
elements
white fill
indicates
NetWorker
and Oracle
elements
nsrmmd
Media Database
Secondary
Storage
nsrmmdbd
nsrd
108
Appendix A: Commonly Used Command

Options for brbackup, brarchive, and brrestore
This appendix provides sample syntax and options for the SAP R/3 Release
4.6B brbackup, brarchive, and brrestore commands, which are commonly
used for NetWorker Module operations. For a complete listing of the syntax
and options used with the brbackup, brarchive, and brrestore commands,
refer to the appropriate SAP documentation.
Note: The commands can be used from any command prompt.
This appendix includes the following sections:
"Syntax and Options for brbackup and brarchive Commands" on

page 110
"Syntax and Options for brrestore Command" on page 113
109
Syntax and Options for brbackup and brarchive Commands

The NetWorker Module uses the following brbackup command syntax and
options:
brbackup [-c force][-d {util_file|util_file_online}]

[-m {all|tablespace_name|file_ID|file_ID_range}]
[-p profile][-q check][-r parameter_file]
[-t {online|offline|offline_force|offline_standby}]
[-u user/password]
Command options in brackets ([ ]) are optional. At least one of the command
options in braces ({ }) must be included in the command.
The NetWorker Module uses the following brarchive syntax and options:
brarchive [-c force][-d {util_file|util_file_online}][-f stop]
[-m delay_time][-p profile][-q check][-r parameter_file][-s save]
[-u user/password]
Table 19 on page 110 lists the options available with the brbackup and
brarchive commands.
Table 19. The brbackup and brarchive Command Options (Part 1 of 3)
Option
Description
-c force
Suppresses most of the confirmation messages that

interrupt the backup process.
-d util_file | util_file_online Specifies that the NetWorker Module is used for

the backup or archive process. This option is not
required because it is set during configuration (see
"Task 4: Configure the Backup and Restore Utility"
on page 42.)
110
-f stop
Instructs brarchive to wait for the next offline redo

log file written by Oracle, and then send it to
backint for archiving.
-m all
Sends the entire database to backint for backup.
-m tablespace_name
Sends a single tablespace to backint for backup.
Appendix A: Commonly Used Command Options for brbackup, brarchive, and brrestore

Option
Description
-m file_ID
Sends a datafile with an associated Oracle file ID to

backint for backup. The following file ID formats
are acceptable:
Specify control files as ID 0.
Specify online redo log files as the following ID:
0 group_number
where group_number is the group number
associated with the redo log files.
Specify all online redo log files as ID 00.
-m file_ID_range
Sends datafiles within a specified Oracle file ID

range to backint for backup.
-m delay_time
Specifies the delay time between Oracle creating

the offline redo log file and sending datafiles to the
database in standby mode.
-p profile
Specifies a profile other than the default,

init<ORACLE_SID>.sap. The nondefault profile
used for BRTools must specify the settings outlined
in "Task 4: Configure the Backup and Restore
Utility" on page 42.
-r parameter_file
Specifies the parameter file that the NetWorker

Module uses during the backup or archive process.
This option is required only if you have created
additional parameter files. Otherwise, this option
is not required, because init<ORACLE_SID>.utl is
set as the default parameter file during
configuration. For details on setting the default
parameters, see "Task 3: Configure the NetWorker
Module Parameters" on page 33.
-s saveset
Specifies the number of members in save sets (1, 2,

3, 4, tablespace, or all).
111
112
Option
Description
-t online
Instructs brbackup and the NetWorker Module to

perform an online backup of the Oracle database.
To reduce the number of redo logs that Oracle
generates, use this option with the -d util_file_online
option.
-t offline
Specifies to brbackup and the NetWorker Module

that the Oracle database is shut down.
-t offline_force
Instructs the SAP R/3 system to shut down the

Oracle database immediately and tell brbackup to
send data to backint for backup.
-t offline_standby
Instructs the SAP R/3 system that the database in

standby mode is ready for backup.
-u user/password
Specifies the Oracle database administrators user

name and password.
Appendix A: Commonly Used Command Options for brbackup, brarchive, and brrestore
Syntax and Options for brrestore Command

The NetWorker Module uses the following brrestore syntax and options:
brrestore [-c force][-d {util_file|util_file_online}]

[-m {all|full|table_space_name|file_ID|file_ID_range|generic_path}]
[-p profile][-q check][-r parameter_file]
Command options in brackets ([ ]) are optional. At least one of the command
options in braces ({ }) must be included in the command.
Table 20 on page 113 lists the options available with the brrestore command.
Table 20. The brrestore Command Line Options (Part 1 of 2)
Option
Description
-c force
Suppresses most of the confirmation messages that

interrupt the restore process.
-d util_file | util_file_online Specifies that the NetWorker Module is used for

the restore process. This option is not required
because it is set during configuration (see "Task 4:
Configure the Backup and Restore Utility" on
page 42).
-d util_file_online
-m all
Requests the backint program to restore all

tablespaces and associated files.
-m full
Requests the backint program to restore the entire

database instance.
-m table_space_name
Requests the backint program to restore a single

tablespace.
113
Syntax and Options for brrestore Command
Table 20. The brrestore Command Line Options (Part 2 of 2)
Option
Description
-m file_ID
Requests the backint program to restore a datafile

with an associated Oracle file ID. The following file
ID formats are acceptable:
Specify control files as ID 0.
Specify online redo log files as the following ID:
0 group_number
where group_number is the group number
associated with the redo log files.
Specify all online redo log files as ID 00.
-m file_ID_range
Requests the backint program to restore datafiles

within a specified Oracle file ID range.
-m generic_path
Requests the backint program to restore all the

datafiles whose names start with that full path. The
path must contain at least the SAPDATA_HOME
directory and an additional generic specification
(for example, sapdata<n> ).
If the generic path is a directory, you can also
restore one or more files from this directory by
additionally specifying one or more filenames.
114
-p profile
Specifies a profile other than the default

init<ORACLE_SID>.sap profile. A nondefault
profile must specify the settings outlined in "Task
4: Configure the Backup and Restore Utility" on
page 42.
-r parameter_file
Specifies the parameter file that the NetWorker

Module uses during the restore process. This
option is required only if you have created
additional parameter files. Otherwise, this option
is not required, because init<ORACLE_SID>.utl is
set as the default parameter file during
configuration. For details on setting the default
parameters, see "Task 3: Configure the NetWorker
Appendix B: Environment Variables for RMAN
To configure the RMAN utility for backup and restore, NetWorker software
uses specific NSR_* environment variables that are described in this appendix.
This appendix contains the following sections:
"Setting the Environment Variables" on page 115

"Environment Variable Definitions" on page 116
Setting the Environment Variables

The environment variables are set with the rman_parms parameter in the SAP
initialization file (also called the utilities profile), init<ORACLE_SID>.sap,
On Microsoft Windows: %ORACLE_HOME%\DATABASE

On UniX or Linux: $ORACLE_HOME/dbs
For instructions on configuring the RMAN utility for the NetWorker Module,
see "Configuring RMAN as the Backup and Restore Utility" on page 43.
115
Environment Variable Definitions

Table 21 on page 116 lists all the NSR_* environment variables that can be used
with the NetWorker Module.
Table 21. NSR_* Environment Variables (Part 1 of 6)
Variable
Description
NSR_BROWSE
Not recommended. This variable from

release 3.5 of the NetWorker Module
for Oracle has been replaced by the
NSR_SAVESET_BROWSE variable.
If this variable is used, its

value is assigned to the
NSR_SAVESET_BROWSE
variable.
NSR_CHECKSUM
FALSE (default) = The

Optional. Specifies whether or not
NetWorker software
the NetWorker software performs
performs no
checksumming on the backup data.
checksumming.
TRUE = The NetWorker
software performs
checksumming.
NSR_CLIENT
Recommended for a backup of Oracle The physical host on which

the session runs (default).
running on a cluster, Oracle Parallel
A valid NetWorker client
Server (OPS), or Real Application
hostname.
cluster (RAC) system.
Recommended for all restores.
Specifies the NetWorker Client
resource to use for a backup or
restore session.
Might be needed for disaster
recovery.
NSR_COMPRESSION
116

compression on the backup data.

NetWorker software
performs no compression.
software performs
compression.

Variable
Description
The most appropriate pool,

selected by the NetWorker
server (default).
Specifies the name of the volume
A valid NetWorker pool
pool to use for the Oracle backup,
name.
including a duplexed Oracle backup. The name must be different
from the name used by
In the case of proxy backups,
another NSR_DATA_
specifies the volume pool for live
VOLUME_POOL* variable.
backups only (backups to secondary
storage only).
NSR_DATA_VOLUME_ Mandatory if using set duplex

POOL
command (set to 1, 2, 3, or 4).
Note: For a scheduled backup, the

NSR_DATA_VOLUME_POOL
setting takes precedence over any
pool associated with the scheduled
backup group.
POOL1
command (set to 2, 3, or 4).
pool to use for a duplexed Oracle
backup.

POOL2
command (set to 3 or 4).
backup.

POOL3
command (set to 4).
backup.
Undefined (default).
name.
The name must be different
another NSR_DATA_
name.
another NSR_DATA_
name.
another NSR_DATA_
117

Variable
Description
NSR_DEBUG_FILE
Optional. Enables debugging by

specifying the complete pathname
of the log file on the Oracle Server
that receives debugging information
during a proxy or nonproxy backup
or restore.
The valid pathname of the
debug file to use on the
Oracle Server.
Note: If undefined, no
debugging information is
generated. If a file with the
Only used for debugging of the
specified pathname cannot be
NetWorker Module for Oracle
media management library (MML). created, debugging
information is either directed
to the default location or not
generated.
NSR_DEBUG_LEVEL
0 (default) = Only
Optional. Controls the amount of
operational messages are
debugging information that the
written for the sbtread(),
NetWorker Module for Oracle
sbtwrite(), and sbtpcstatus()
writes to the debug log file, which is
functions. No entry or exit
specified by NSR_DEBUG_FILE.
messages are written for
The debug level limits only the
the functions.
amount of debug information
1 = Only entry and exit
generated by the three functions
messages are written for
sbtread(), sbtwrite(), and
the sbtread(), sbtwrite(),
sbtpcstatus()that are called most
and sbtpcstatus() functions.
often during backups and restores.
No operational messages
All the debug messages for other
are written for the
functions are always written to the
functions.
log file, regardless of the debug
3 = All debug messages for
level.
all the functions are written
to the log file.
NSR_ENCRYPTION

encryption on the backup data.
118

NetWorker software
performs no encryption.
software performs
encryption.

Variable
Description
NSR_GROUP
Optional. Use for a manual backup only.

Specifies the NetWorker group to
use for a backup session. Used by
the NetWorker server to select the
volume pool for the manual backup.
Default group (default).

A valid NetWorker backup
group name.
Note: Do not set this variable for a

scheduled backup.
Note: A NetWorker Group

resource must be configured
for the specified backup
group.
NSR_NO_BUSY_
ERRORS

Optional. Specifies whether a
scheduled backup waits for
scheduled backup fails immediately
the NetWorker server to
when the NetWorker server is busy
accept the connection.
or waits for the NetWorker server to
TRUE = The scheduled

accept the connection.
backup fails immediately
Note: For proxy Oracle backups, this when the NetWorker server
variable is always set to FALSE.
is busy.
NSR_NWPATH
Mandatory when removing a backup The platform-specific

default location of the
from the NetWorker server if both:
NetWorker client binaries
The nsrmm binary is in a
(default).
nondefault location; and
The /nsr/res/nwora.res file does not A valid pathname of the
nsrmm binary directory, for
contain the correct location of the
example, /usr/local/bin.
NetWorker client binaries.a
Specifies the complete pathname of
the directory containing the nsrmm
binary.
NSR_PROXY_PFILE
Supported only for a proxy Oracle

backup or restore.
Mandatory if setting PowerSnap
variables in a configuration file.
A valid pathname of the
configuration file.
Note: If undefined or an
invalid pathname, variable
Specifies the complete pathname of settings in the preferred
a configuration file that contains
configuration file are ignored.
PowerSnap variable settings for a
proxy Oracle backup or restore.
119

Variable
Description
NSR_SAVESET_
BROWSE
Mandatory if setting a nondefault

browse policy for a manual Oracle
backup with NetWorker server 6.x
or later.
The most appropriate

policy for the client, as
server (default).
A valid date in
Specifies the date when the entry for
nsr_getdate(3) format.
the backup is to be removed from
the NetWorker client file index.
Note: This variable has an effect only
for an Oracle backup with
NetWorker server 6.x or later. For a
scheduled Oracle backup with
NetWorker server 6.x or later, this
variable overrides the Browse Policy
attribute setting in the NetWorker
Client resource.
If this variable is used, its
value is assigned to the
NSR_SAVESET_RETENTIO
N variable.
NSR_SAVESET_
EXPIRATION
Not recommended. This variable from

release 3.5 of the NetWorker Module
for Oracle has been replaced by the
NSR_SAVESET_RETENTION
variable.
NSR_SAVESET_
RETENTION
The most appropriate

Mandatory if setting a nondefault
policy for the client, as
retention policy for a manual Oracle
backup with NetWorker server 6.x
server (default).
or later.
A valid date in
Specifies the date when the save set
nsr_getdate(3) format.
becomes recyclable.
Note: This variable has an effect only
for an Oracle backup with
NetWorker server 6.x or later. For a
scheduled Oracle backup with
NetWorker server 6.x or later, this
variable overrides the Retention
Policy attribute setting in the
NetWorker Client resource.
120

Variable
Description
NSR_SERVER
Mandatory for a manual backup if the The local physical host

(default).
NetWorker server host is different
A valid NetWorker server
from the Oracle Server host.
name.
Recommended for a local manual
backup.
Specifies the hostname of the
NetWorker server to perform the
Oracle backup.
a. Instead of setting the NSR_NWPATH variable in the RMAN script, a line containing NSR_NWPATH=nsrmm_dirpath
can be added to the /nsr/res/nwora.res file, where nsrmm_dirpath is the complete pathname of the directory containing
the NetWorker nsrmm program. For example: NSR_NWPATH=/opt/networker/bin
121
122
Appendix C: Troubleshooting
This appendix contains troubleshooting tips and NetWorker Module error

messages. It also provides suggestions to help diagnose and fix problems with
the NetWorker Module during backup and restore sessions.
This appendix includes the following sections:
"Verifying the Release Information" on page 123

"Generating Diagnostic Logs" on page 124
"Backup and Restore Problems" on page 124
"Regular Session Error Messages" on page 126
"Fatal Error Messages" on page 129
Verifying the Release Information

When making queries or requests to Customer Support, provide specific
information for the NetWorker Module you are using.
To verify the release information for your NetWorker Module installation, use
the appropriate command or procedure as follows:
On UNIX, enter the following command as the root user:

what filenm | more
where filenm is the name of a NetWorker Module binary file, for example
backint or nsrsapsv.
123
Generating Diagnostic Logs
On Linux, enter the following command as the root user:

strings filenm | grep "@(#)"
where filenm is the name of a NetWorker Module binary file, for example
backint or nsrsapsv.
a. Locate the NetWorker Module binary file, for example backint.exe or
nsrsapsv.exe.
b. Right-click the file, and select Properties.
c. In the Properties window, select the Version tab to display the release
information.
Generating Diagnostic Logs

To generate backint diagnostic logs, set the following values in your
init<ORACLE_SID>.utl file:
debug_level = 9
nsr_debug_msg = yes
verbose = yes
Note: Debug level is intended for testing and technical support diagnostics
only.
Backup and Restore Problems

Table 22 on page 124 provides guidelines for solving problems that may occur
during a NetWorker Module backup or restore process.
Table 22. NetWorker Module Backup or Restore Problems (Part 1 of 3)
Problem
Possible Reason or Solution
Data is not being backed up to the

NetWorker server.
Ensure that the SAP initialization file,

init<ORACLE_SID>.sap, is configured to use the
NetWorker Module. For information, see
"Task 4: Configure the Backup and Restore
Utility" on page 42.
124

Problem
Data is not being backed up using the

settings in the Client resource on the
NetWorker server.
During a backup, the NetWorker Module does

not use most of the settings in the Client
resource, except for the save set name and
backup schedule. The client settings must be
specified in the init<ORACLE_SID>.utl file on
the SAP R/3 server running Oracle. For
information, see "Task 3: Configure the
The bootstrap notification report was not

Bootstrap notification reports are not generated
printed to the printer specified in the Group after a manual NetWorker Module backup. To
resource on the NetWorker Module server. generate a bootstrap notification report, see
"Backing Up the Client File Indexes and
Bootstrap" on page 49.
Online backup of an Oracle tablespace is
taking a long time.
Oracle creates more online redo logs during an

online backup than during an offline backup.
This might prolong the online backup.
Following a backup, the parallelism setting

in the backint<ORACLE_SID>.log is
different from the setting in the parameter
file init<ORACLE_SID>.utl.
The parallelism setting is adjusted by backint

during the backup session depending on other
parameters, for example, when the number of
files within the backup session is lower than the
server parallelism setting.
A specified backup of an Oracle directory

failed.
The NetWorker Module does not support

backing up directories. Specify each database
object within the directory to back up and then
perform the backup.
You are unable to view the files backed up Ensure that the SAP users operating system
to the NetWorker server from the SAPDBA authorization has the appropriate permission to
program on the SAP R/3 server running
access the NetWorker server.
Oracle.
125
Regular Session Error Messages

Problem
You are unable to restore the most recent

version of the file that was backed up.
When a restore is initiated within a certain time

frame that expired or otherwise is not available,
brrestore restores files from previous backups,
depending on whether the prev_bk_restore
parameter is set to Yes. For more information,
see "prev_bk_restore" on page 39.
Ensure that the SAP users operating system
authorization has the appropriate permission to
access the NetWorker server.

This section discusses error messages that may occur during a backup, restore,
or inquire session, but which do not prevent the session from continuing.
Table 23 on page 126 indicates possible error messages that might appear in
the backint<ORACLE_SID>.log file.
Table 23. NetWorker Module Regular Session Error Messages (Part 1 of 3)
Error Message
Description
Solution
Error when sending

out e-mail
The NetWorker Module

could not write a
notification to the
command line mail utility
specified in the error
message.
Notification is supported only on

UNIX. Check the usage of the notify
parameters in the
init<ORACLE_SID>.utl file. See
"Task 3: Configure the NetWorker
Error: filename is not a The backint program does

regular file, raw
not support the file type
partition, or
(such as a symbolic link or
directory.
a named pipe).
Check the filename to see what type

of file is being backed up. If
brbackup is requesting backup of
special files, contact SAP support.
126

Error Message
Description
Solution
Error: save symlinks During the process of

had errors
saving symbolic links,
backint ran out of
memory and could no
longer add symbolic links
to its list.
This situation is unlikely to occur.

The computer may be low on
memory, or the program may
contain a logic error. If this situation
recurs, contact Legato Technical
Support.
The files requested in the

input file do not match the
SAP R/3 backint
specification. Valid file
specifications include:
#NULL is specified for a
backup ID, with or
without a filename
A filename is specified
with a backup ID.
A backup ID is specified
without a filename
Check the backup input file

generated by brbackup. If the input
file generated appears to be the
wrong format, contact SAP support.
Error: unexpected
inquire case.
Ignoring, use format Uncommented text in the

param=value
init<ORACLE_SID>.utl
parameter file does not
conform to param =
value and is ignored.
Lookup failed on
filename (backup_ID)
The backint program was

trying to look up a
filename and/or backup
ID in the client file index,
but the attempt to query
the index failed. The next
message should explain
why the index query
failed.
Pathname nothing found The specified file was not

in index
found in the NetWorker
client file index.
For information on setting the

parameters in the
init<ORACLE_SID>.utl file, see
"Task 3: Configure the NetWorker
Check the error message to
determine why the attempt to query
the index failed. If this message does
not explain the problem, and future
inquire or restore requests fail,
contact Legato Technical Support.
Ensure that the file was actually

backed up in a previous run of
backint. If brbackup specifies
filenames that were never backed
up, check the SAP R/3 installation.
127

Error Message
Description
Solution
Process_ID File filename

not found in index,
no attempt to recover
will be made
The NetWorker software

did not save the filename
specified for recovery and
the filename does not
appear in the client file
index.
Check the filename specified to see

if the name is correct. Check
previous backups to determine
whether the file was actually saved
in a previous backup.
Unable to build
command line.
The backint command

was unable to build a
command line for a
subprocess because the
program ran out of
memory.
This situation is unlikely to occur.

The computer may be low on
memory, or the program may
contain a logic error. If this situation
recurs, contact Legato Technical
Support.
Unable to find pid

process ID in list of
files
The backint program is

checking the status of a
subprocess that was
created to save individual
files. However, the
subprocess ID does not
match any of the expected
process IDs.
Check the rest of the messages from

the backup process to ensure that
everything was saved. In particular,
check for the message x of y files
saved at time. If all of the files were
not saved, retry the backup.
Unable to query with The backint program was

savetime and
trying to find a file in the
filename both absent client file index, but
neither the save time nor
the filename were
provided.
Check the input file to see if any file

information is specified incorrectly.
If this situation persists, contact
Legato Technical Support.
Warning: Unknown
parameter,
parameter_name
128
The parameter indicated is For valid parameters, see "Task 3:

not a valid NetWorker
Configure the NetWorker Module
Module parameter.
Parameters" on page 33.
Fatal Error Messages

This section discusses fatal error messages and provides information as to why
a particular backup, restore, or inquire session fails.
Table 24 on page 129 indicates any fatal error messages that begin with the
following line:
Backint exiting at time_stamp with fatal error
Table 24. NetWorker Module Fatal Error Messages (Part 1 of 6)
Error Message
Description
BACKUP: Bad input One of the lines in the input file had
line: line
a bad format. There should be only
one or two specifications on each
input line (filename and size, if it is
a special file).
Solution
Check the input file brbackup
generated to make sure it has the
correct format. If not, and this
error keeps occurring, contact
SAP technical support.
Bad function on
input line,
function
The function indicated cannot be

performed as it is either an invalid
function or you are attempting to
use unsupported options.
The NetWorker Module can only

be invoked through the
SAPDBA program or associated
commands. For information on
supported functions refer to the
-f option in SAPs BC-BRI
BACKINT Interface for Oracle
documentation.
Can not reopen

filename as stderr
The backint program was unable to Check the permissions on the file
open a log file for writing.
listed in the message, as well as
the permissions on the directory.
Cannot connect to The backint program was unable to Ensure that the correct
server: error
connect to the NetWorker server to NetWorker server is specified.
start reading the media database.
Check the log file to see if any
other messages refer to this
problem.
Cannot start
session with
server: error
The backint program was unable to Ensure that the correct

start reading the media database on NetWorker server is specified.
the NetWorker server.
problem.
129

Error Message
Description
Checking for
deletion of
semaphore file:
error
The existence of the semaphore file Check to see if the .switch.sem file
could not be confirmed because of a is still in the SAPBACKUP
system error.
directory. If so, delete it before
running the SAP R/3 backup
again.
Creating
directive file:
error
The directive file for NetWorker

software to use cannot be created.
This directive file is created so the
NetWorker software can process
files with the correct attributes.
Check the directory where the

directive file is being created,
specified by the backint_tmpdir
parameter in the NetWorker
Modules parameter file, to
ensure files can write to it.
Error: Too many

symlinks
There are too many symbolic links

to save (more than 100).
If the list of database files to be

backed up contains more than
100 symbolic links, consider
restructuring the directories to
eliminate the extra symbolic
links.
File was filename,

lstat error
The NetWorker Module tried to get Check the file to see that it exists
information for a symbolic link that and is a valid symbolic link.
does not exist or the NetWorker
Module cannot access because
permission is denied.
Improperly
formatted backup
id: backup ID
The backup ID is incorrect. It

should specify either a number or
the word #NULL.
Check the input file brrestore

generated to ensure that it has
the correct format. If not, and
this error keeps occurring,
contact SAP technical support.
INQUIRE: Bad
input line: line
One of the lines in the input file had

one or two specifications on each
input line (backup ID or #NULL an
optional filename).

Interrupted...
backint exiting
The NetWorker Module backint

This error usually occurs due to
program was interrupted during a a keyboard error.
backup, restore, or inquire session.
130
Solution

Error Message
Description
Solution
Non-recursive
directory backup
is not supported
at this time
You have attempted to back up a

Select specific database objects to
directory. The backup of directories back up from the SAPDBA
is not supported.
program and restart the backup
process.
Not enough save

sets, please
increase savesets
setting in .utl
file
The number or size of the save sets Increase the number of save sets.
to be backed up exceeds the current or the maximum save set size.
settings for the number of save sets To configure the parameter for
allowed or the maximum save set
the number of save sets, see
size allowed.
"savesets" on page 40.
To configure the parameter for
maximum save set size, see
"ss_size_max" on page 41.
Opening input
file: error
The input file, which lists all files to Ensure that the input file exists
be backed up or restored, could not and is readable.
be opened. It may not exist, or it
may not have read permissions.
Opening output
file: error
The output file could not be opened Check the permissions on the
for the reason specified.
output file and directory, and
check for sufficient disk space to
create a new file.
Opening parameter Unable to open the backint

file
parameter file,
init<ORACLE_SID>.utl.
Opening switch
list file for
online backup:
error
When performing an online

backup, backint tries to open a file
to communicate with brbackup.
This file could not be opened for the
reason given.
Attempt to open the parameter

file for backint in any text editor.
If you are unable to open the
parameter file, replace it with
the original file from the
NetWorker Module CD.
Check to see if the .switch.lis file
exists in the SAPBACKUP
directory. If so, check the
permissions on this file.
Normally, the NetWorker
Module deletes and re-creates
this file for every tablespace to
be switched into backup mode.
131

Error Message
Description
Solution
Opening switch
log file for
online backup:
error

backup, backint expects brbackup
to provide a log file of the
tablespaces that were switched into
or out of backup mode.
Check to see if the .switch.log file

is still in the SAPBACKUP
directory. If so, delete it before
running the SAP R/3 backup
again.
Opening switch
semaphore file
for online
backup: error

backup, backint tries to open a file
to communicate with brbackup.
This file could not be opened for the
reason given.
Check to see if the .switch.sem file

exists in the SAPBACKUP
directory. If so, check this files
permissions. Normally, the
NetWorker Module deletes and
re-creates this file for every
tablespace to be switched into
backup mode.
ORACLE_HOME not
set.
The ORACLE_HOME environment Set the ORACLE_HOME

variable must be set.
environment variable to the
correct directory.
recover_start:
The backint program was unable to Ensure that the correct
cannot connect to connect to the NetWorker server to NetWorker server is specified.
server server_name start the recovery process.
problem.
RESTORE: Bad
input line: line
One of the lines in the input file had

two or three specifications on each
input line (backup ID or #NULL, a
filename, and an optional
destination directory).
SAPBACKUP must be The SAPBACKUP environment

set for online
variable must be set to a valid
backups.
directory for an online backup. This
directory is used to hold the switch
log and switch list files on
Windows.
132

generated to make sure it has the
correct format. If not, and this
error keeps occurring, contact
SAP technical support.
Set the SAPBACKUP
environment variable to a valid
directory (such as:
%ORACLE_HOME%\
<ORACLE_SID>\sapbackup on
Windows).

Error Message
Description
Semaphore file
not deleted in time backup, the SAP R/3 module was
seconds
waiting for the switch semaphore
file to be deleted. After waiting
some number of seconds, the switch
semaphore file still was not deleted.
Solution
If brbackup appears to be
running properly but just slowly,
you can increase the
sem_timeout setting in
init<ORACLE_SID>.utl.
stating file:
error
The filename given in the input file Check the file to see if it exists
does not exist, or it may be
and has read permissions.
inaccessible.
Switch log file

indicates an
error.
The brconnect program indicated

in the switch log file that there was
an error switching one of the
tablespaces into or out of backup
status. This is considered a fatal
error in the backint specification.
Investigate the error messages in

the switch log file to determine
the problem. Check the SAP R/3
installation or the SAP R/3
documentation to determine the
problem.
This eval copy

has expired
The evaluation version of the

NetWorker Module has expired.
Contact Legato Sales to obtain a

permanent enabler.
For instructions on entering the
enabler code, refer to the Legato
NetWorker Module for SAP R/3
with Oracle Installation Guide.
Unable to
allocate memory
for struct
fileinfo
The backint program ran out of

space when it tried to allocate
memory for a block of file
information.
Check the memory usage on the

computer. You may need to
reboot the computer if it is
running low on memory. If the
input file is excessively large,
check to make sure SAPDBA is
providing a valid list of files.
Unable to
allocate memory:
error
The backint program was unable to Check the memory usage on the
allocate memory.
computer. You may need to
reboot the computer if it is
running low on memory.
133
Error Message
Description
Solution
Unable to change
to root: error
In a cluster environment on UNIX, Ensure the user has proper

the program was unable to change permission to log on as root.
its real and effective user IDs to
root.
Unable to execute The backint process could not

Ensure that the backint binary is
child backint
execute a subprocess to back up an installed in the directory from
process.
individual save set.
which SAPDBA, brbackup, or
brrestore is run. Check the log
file for any other messages
which may help pinpoint the
problem.
Unable to open
The output file could not be opened Check the permissions on the
output file: error because of the error specified.
output file and directory, and
check for sufficient disk space to
create a new file.
Usage error
An unsupported option was

For parameters accepted by
included in the backint command. backint, refer to SAPs BC-BRI
BACKINT Interface for Oracle
documentation.
Use absolute path The filename given in the input file

name for: filename
was not an absolute pathname. The
file cannot be restored or inquired
without having the full pathname.

waitchild (name)
failed: error
The program could not properly

receive the exit code from a
subprocess. It is possible that the
subprocess did not start correctly.
Check any prior error messages

to determine whether a
subprocess failed, and if so, why.
Warning, empty
input file
The input file that contains the list

of files to be backed up or restored
is empty.
Ensure that you have selected

database objects for backup or
restore.
134
Glossary
This glossary contains terms and definitions found in this manual. Most of the
terms are specific to Legato NetWorker Module for SAP R/3 with Oracle
products.
?
The Oracle placeholder for the main directory of the

Oracle database instance identified as $ORACLE_HOME.
See init<ORACLE_SID>.utl.
archive
The process by which NetWorker software backs up

directories or files to an archive volume and then grooms
them to free disk space. When data is archived, it is written
to one or more storage volumes and then marked so that it
is never subject to automatic recycling. You can delete the
archived files from the client, thus freeing disk space.
archived redo log
An archived copy of a filled online Oracle redo log. You

can optionally configure an Oracle database to archive
copies of the online redo logs after they fill. An archived
redo log preserves older redo log data for recovery
operations while the preallocated online redo log files are
reused to store the most current database changes. See redo
log.
ARCHIVELOG mode
Setting the Oracle database to this mode enables archiving

of the online redo logs.
135
Glossary
136
authentication method
A security method that enables high confidence in the

identity of users, clients, and servers in distributed
environments. The NetWorker Module software allows
two methods of authenticating identity:
Database authentication uses the SAP R/3 or Oracle
system user name, as designated by the database
administrator for the clients Oracle database. This user
name and its password must be encrypted in the
scheduled backup configuration file.
External or enterprise authentication applies a user name
that is derived from either the save set name entered in
the Client resource or the ORACLE_SID parameter set in
the scheduled backup configuration file.
backint
The interface the NetWorker Module software uses to

connect the NetWorker software with the SAP BRTools.
The backint program enables backups, restores, or
inquiries on the associated Oracle databases.
backup device type
The backup device type to which the SAP BRTools

program sends data. When this attribute is set to util_file,
BRTools uses the NetWorker Module utility file.
bootstrap
A save set that is essential for the NetWorker disaster

recovery procedures. It is composed of three components
that reside on the NetWorker server: the media database, the
resource database, and the server index.
brarchive
The SAP BRTools program that sends requests to the

NetWorker Module to back up Oracle database archive
logs.
brbackup

NetWorker Module to back up Oracle data files, control
files, redo logs, and tablespaces.
browse policy
A policy that determines how long entries for backup data

remain in the client file index.
brrestore

NetWorker Module to restore Oracle data to the Oracle
server.
Glossary
A set of SAP tools used to back up and recover SAP R/3

data in an Oracle database. The tools are: brbackup,
brarchive, and brrestore.
client file index
A database of information the NetWorker server maintains

that tracks every database object, file, or filesystem backed
up. The NetWorker server maintains a single client file
index for each client computer.
clone
The NetWorker process used to make an exact copy of

saved data (save sets). NetWorker software indexes and
tracks clones in both the client file index and the media
database. The NetWorker Module for SAP R/3 with Oracle
software uses the sapclone command to clone save sets.
clone volume
A duplicated volume belonging to a clone pool.

NetWorker software can track four types of volumes:
backup, archive, backup clone, and archive clone. Save
sets of different types may not be intermixed on one
volume.
cluster
Two or more nodes that are connected and appear to

network users as a single highly available system. A
highly available system allows the application services to
continue despite most hardware or software failures.
cold Oracle backup
See offline backup.
database authentication
See authentication method.
DBA
An abbreviation for database administrator. The person

normally responsible for installing, configuring, and
maintaining Oracle database systems.
deferred live backup
See live backup.
device
A storage unit that reads from and writes to storage

volumes. A storage unit can be a tape device, optical drive,
autochanger, or file connected to the server or storage
node.
directed recovery
A recovery method used to recover data that originated on

one computer and re-create it on another computer.
137
Glossary
BRTools
Glossary
directive
An instruction that directs NetWorker software to take

special actions on a given set of files for a specified client
during a backup.
enabler code
A special code provided by Legato that activates the

software. The enabler code that unlocks the base features
for software you purchase is referred to as a base enabler.
Enabler codes for additional features or products (for
example, autochanger support) are referred to as add-on
enablers.
external or enterprise
authentication
See authentication method.
file index
See client file index.
filesystem
1. A file tree located on a specific disk partition or other

mount point.
2. The entire set of all files.
3. A method of storing files.
138
hot Oracle backup
See online backup.
immediate live backup
See live backup.
init<ORACLE_SID>.sap
The SAP initialization file used to set the parameters the

SAP BRTools program uses during backup, restore, and
archive sessions.
init<ORACLE_SID>.utl
The NetWorker Module parameter file that specifies the

parameters the backint command uses during backup,
restore, and archive sessions.
instance
See Oracle instance.
instant backup
A permanent point-in-time copy, or snapshot, of SAP R/3

with Oracle data that is stored as a backup on the primary
storage system.
instant restore
The process by which the snapshot that was created on the

primary storage system with an instant backup is
mounted and its saved data is retrieved as needed.
Glossary
The license code that enables you to run a feature or

product.
live backup
A live backup (also known as a "PIT rollover" or "rollover

to tape" backup) is a tape backup of a previously-created
snapshot. The NetWorker Module for SAP R/3 with
Oracle supports the following two types of live backup:
Immediate live backup (also known as "serverless
snapshot backup" or "snapshot-based backup") is a
process by which a temporary snapshot is created, and
immediately backed up to secondary storage such as
tape. The snapshot is then automatically deleted from the
primary storage.
Deferred live backup is a process by which a permanent
snapshot, created on the primary storage system, is
backed up to secondary storage such as tape. The
snapshot is retained on the primary storage for a
specified period of time.
manual backup
An unscheduled backup that a user requests from the

NetWorker client side. A manual backup does not
generate a bootstrap save set.
media database
A database that contains indexed entries about the storage

volume location and the life cycle status of all data and
volumes the NetWorker server manages.
offline backup
A backup of Oracle database objects performed while the

corresponding Oracle instance is shut down and
unavailable to users.
online backup
A backup of Oracle database objects performed while the

corresponding Oracle instance is running and available to
users.
online indexes
The databases located on the NetWorker server that

contain all the information pertaining to the client backups
(client file index) and backup volumes (media database).
Oracle instance
The combination of Oracle processes and shared memory

that is created each time a database starts up.
Oracle user
The user of an Oracle database.
139
Glossary
license enabler
Glossary
ORACLE_SID
The system ID of the Oracle database instance.
parameter
A variable used to identify the specific values or options to

be used by associated commands.
pathname
A set of instructions to the operating system for accessing

a file.
An absolute pathname indicates how to find a file starting
from the root directory and working down the directory
tree.
A relative pathname indicates how to find the file starting
from where you are now.
PIT copy
Point-in-time copy, which generally means a permanently

retained snapshot of data created with a PowerSnap
Module. A snapshot results in one or more PITs being
created nearly simultaneously with the option to back
these up to tape.
RDBMS
An abbreviation for Relational Database Management

System, which refers to the primary architecture that the
Oracle database uses.
recover
NetWorker software: The command used to browse the

server index and to recover files from a backup volume to
a clients disk (a process in Oracle known as "restore").
Oracle: The datafile recovery method that uses Oracle
commands to apply archived redo logs and online redo
logs to make the database consistent.
140
Recovery Manager
See RMAN.
redo log
The online log of an Oracle database, consisting of at least

two redo log files (separate from the datafiles) that record
all changes made in the database. See also archived redo log.
resource database
A database that contains information about each of the

configured backup servers resources.
restore
The process of retrieving individual files from backup

media and storing the files on disk.
Glossary
An abbreviation for Recovery Manager, the Oracle utility

that acts as an intelligent interface to Oracle databases and
works with third-party media management products,
such as NetWorker Modules, to back up and restore Oracle
database objects.
rollback restore
The process by which the entire snapshot, created on the

primary storage system by an instant backup, is restored
to the source location by using the hardwares particular
capabilities.
rollover to tape
See live backup.
root
The UNIX superuser account (with user name root and

user ID). By extension, the privileged system-maintenance
login on any operating system.
sapclone
The NetWorker Module command used to create a

duplicate copy of the data (save sets) backed up using the
SAPDBA
The SAP R/3 database administration utility that

simplifies the administrative tasks related to Oracle
databases, including backup and restore operations. This
utility can be used to call brbackup, brrestore, and
brarchive programs.
save set
A group of files or a filesystem from a single client

computer backed up to storage media.
save set ID
A unique identification number that NetWorker software

assigns to a save set.
save set status
The NetWorker attribute that indicates whether a given

save set is restorable, recoverable, or recyclable. The save
set status also indicates whether the save set has been
successfully backed up.
secondary storage
restore
The process by which a snapshot that was backed up to

secondary storage by a live backup is restored by using the
traditional NetWorker recover program.
141
Glossary
RMAN
Glossary
142
server index
A database containing information about the NetWorker

server's files that have been backed up during scheduled
backups. Also known as the NetWorker servers client file
index.
SID
An Oracle abbreviation for system identifier, a unique

name for an Oracle database instance. This value is
typically set in an ORACLE_SID environment variable.
snap set
The group of datafiles included in any given snapshot

copy, the lifecycle of which is specified in the Snapshot
Policy.
snapshot
A point-in-time copy of a filesystem or partition.
ssid
See save set ID.
tablespace
An Oracle database structure comprising one or more

datafiles.
Index
<ORACLE_SID>, description
16
A
alert, backup completion 37
arch_backint_log parameter 34
archive logs 39
archive redo logs 48
ARCHIVELOG mode 47
attempts, retry backup 40
B
backint
backup process 24
command 20, 45
description 18, 20
parameter file 33
restore process 26
setting ownership of 30
backint_log parameter 34
backint_tmpdir parameter 34
backup
bootstrap file 49
client file index 49
client settings 54
command 55
command attribute 22
completion notification 37
deferred live 79, 102
diagram 25
group 36
immediate live 78, 99
instant 78, 96
live 78, 99
manual 45
offline manual 46
online manual 4748
PowerSnap manual 102
PowerSnap records 104
PowerSnap types of 77
processes 24, 96
with RMAN 25
with SAPDBA 24
rollover 78, 99
save sets grouped by filesystem
scheduled 53
serverless snapshot 78
session log 50, 63
session report 50, 63
snapshot-based 78
backup_dev_type parameter 42
bootstrap file, backing up 49
bootstrap, NetWorker 98, 100
BR_EXEC 60
brarchive 97, 99
command 22, 109
description 22
difference from brbackup 19
manual backup 109
supported options 109
syntax 109
brbackup 97, 99, 109
command 22, 109
description 22
difference from brarchive 19
offline backup 47
online backup 48
syntax 109
browse naming format 41
browse policy 70
expiration 36
for manual backup 49
brrestore 26, 105
command 22, 105
description 22
usage 113
BRTools 22
configuring 42
See also SAPDBA
41
143
Index
C-D
Index
C
checksum parameter 35
client
configuring 31, 54
expiration parameter 36
NetWorker, configuring 54
parameter 35
resource 31
save set location 70
settings in parameter file 54
client file index
backup 49
database 49
Client resource 54
configuration 54
parameter 35
client resource
PowerSnap 88
cloning
messages 67
monitoring 67
save sets 65
syntax of sapclone 65
cluster
data, cloning 66
data, restoring 72
command
backint 20, 45
backup 55
brarchive 22, 109
brbackup 22, 109
brrestore 22, 105
mminfo 104
nsrim 50
nsrinfo 104
nsrsapsv 21, 55
nsrsnapadmin 102
sapclone 65
savefs 96, 99
savegrp 49, 96, 99
scanner 70
components
description 20
NetWorker client 22
NetWorker Module 20
144
Oracle 23
PowerSnap 23
SAP R/3 22
user-configurable 20
compress parameter 35
configuration
BRTools 42
NetWorker client 54
NetWorker for PowerSnap 87
NetWorker Module environment 30
PowerSnap 86
SAPDBA 42
configuration file
init<ORACLE_SID>.sap 22, 4243
init<ORACLE_SID>.utl 20, 23, 33, 84, 93
init<ORACLE_SID>.utl for PowerSnap 89
nmsapps.cfg 23, 84, 93
nsrsapsv.cfg 21, 55, 58
cyclic redundancy checking 35
D
data
backing up 2425, 45, 53
expiration 70
recovering 16
restoring 26, 69
data flow description
backup 24
PowerSnap 81
restore 26
database
instance, restoring 70, 113
server, description 17
datafile, restoring by ID 114
debug level 124
deferred live backup 79, 102
description
backup and restore processes
components 20
features 17
NetWorker Module 18
NetWorker server 18
RMAN 19
SAP R/3 18
SAPDBA 18, 22
diagnose problems 123
24
Index
E-L
diagnostic logs 124

disaster recovery files 49
disk failure 49
distributing backup load 40
F
failure notification 37
features
description 17
Index
encrypt parameter 36
encryption, SAP user for OS and Oracle 57
environment variables
mandatory 117, 119121
NSR_BROWSE 116
NSR_CHECKSUM 95, 116
NSR_CLIENT 95, 116
NSR_COMPRESSION 95, 116
NSR_DATA_MOVER 93
NSR_DATA_VOLUME_POOL 95, 117
NSR_DEBUG_FILE 118
NSR_DEBUG_LEVEL 118
NSR_ENCRYPTION 95, 118
NSR_GROUP 95, 119
NSR_MAX_STREAMS 93, 95
NSR_NO_BUSY_ERRORS 119
NSR_NWPATH 119
NSR_PROXY_PFILE 119
NSR_PS_DEBUG_LEVEL 93
NSR_PS_SAVE_PARALLELISM 9495
NSR_SAVESET_BROWSE 120
NSR_SAVESET_EXPIRATION 95, 120
NSR_SAVESET_RETENTION 120
NSR_SERVER 95, 121
NSR_SNAP_TYPE 94
RESTORE_TYPE_ORDER 94
used with RMAN 43, 115
error messages 123
fatal 129
nonfatal 126
errors notification, enabling 37
expiration of data 70
expiration parameter 31, 36
NetWorker Module 18
NetWorker server 18
Oracle, with 19
PowerSnap 19
RMAN, with 19
SAP R/3, with 18
SAPDBA, with 18
files backed up, number of 51
files requested for backup 51
filesystem
group save sets by 41
full restore 70
G
group parameter 36
group resource for PowerSnap 87
group save sets by filesystem 41
H
hostname, NetWorker server
40
I
ID range, restoring by 114
ID, restore by 114
immediate live backup 78, 99
index entries, query parameter 39
init<ORACLE_SID>.sap file
description 22
enabling SAPDBA or brbackup 42
enabling SAPDBA or RMAN 43
specifying different profile 114
init<ORACLE_SID>.utl file 20, 93
equivalent parameters for PowerSnap 95
parameters 33
parameters for PowerSnap 23, 84, 89
input file report 51
instant backup 78, 96
instant restore 80, 105
L
level_full parameter
36
145
Index
Index
M-N
live backup 78, 99

location of save set data 70
logs
arch_backint_log parameter 34
archive redo 48
backint_log parameter 34
backint_tmpdir parameter 34
backup session reports 50, 63
restore 72
verbose setting 41
save sets 41
NetWorker
bootstrap backup 98, 100
client
components 22
configuration 54
name 35
media database service, nsrmmdbd
M
mailx utility 37
mandatory environment variables
117, 119
121
manual backup 45
backup session reports 50, 63
bootstrap 46, 49
client file indexes 49
command line options 109
offline 46
online 47
using brarchive command 46, 48
using brbackup command 46, 48
with SAPDBA 46, 48
max_logs parameter 36
maximum size of save sets 41
media database records 70
messages
cloning 67
notify_done 37
notify_error 37
notify_start 37
notify_success 37
mminfo 104
monitoring
backups 50, 63
cloning 67
restores 72
N
naming
conventions 16
save set format 41
146
97, 100,
102
save set records 70
server
components 20
features 18
hostname 40
NetWorker Module
components 20
environment 30
example network 16
features 18
parameter file 84
restoring with 113
nmsapps.cfg file 23, 84, 93
notify_done message 37
notify_error message 37
notify_start message 37
notify_success message 37
NSR_BROWSE 116
NSR_CLIENT 95, 116
NSR_DATA_MOVER 93
NSR_DEBUG_FILE 118
NSR_DEBUG_LEVEL 118
NSR_GROUP 95, 119
NSR_NWPATH 119
NSR_PROXY_PFILE 119
NSR_SERVER 95, 121
NSR_SNAP_TYPE 94
Index
O-P
O
offline manual backup 46
online manual backup 4748
options
brarchive 109
brbackup 109
brrestore 113
sapclone command 65
Oracle
components used 23
features used 19
user 30
ORACLE_SID 61
P
parallelism, setting 38
parameter
arch_backint_log 34
backint_log 34
backint_tmpdir 34
backup_dev_type 42
BR_EXEC 60
checksum 35
Client resource 35
compress 35
encrypt 36
equivalents to PowerSnap variables 95

expiration 36
group 36
level_full 36
max_logs 36
notify_done 37
notify_error 37
notify_start 37
notify_success 37
ORACLE_SID 61
parallelism 38
pool 39
PowerSnap 89
prev_bk_restore 39
ps_archive_mode 89
ps_backup_mode 89
ps_exclude_backup_bi_run_nums 9092
ps_group_objs 92
ps_opaque_pfilename 23, 93
query_index 39
raw_dir 40
retry_count 40
rman_parms 43
savesets 40
sem_timeout 40
server resource 40
ss_group_by_fs 41
ss_size_max 41
ssnameformat 41
verbose logs 41
parameter file
changing 114
parameters
for brarchive 109
for brbackup 109
NetWorker Module 33
Password for Remote User (Windows) 55
password of SAP user 57
PATH variable, setting 30
physical media failures 78
PIT copy 78
point-in-time copy 78
policies, expiration 36, 70
pool
multiple 39
parameter 39
selection 36
147
Index
nsrexecd service 96, 99

nsrim command 50
nsrindexd service 97, 100, 102, 107
nsrinfo command 104
nsrmmdbd service 97, 100, 102
nsrpsd program 85, 107
nsrsapadm, description 21
nsrsapsv
command 21, 55
configuration file 58
description 21
program 97, 99
nsrsapsv.cfg file
configuration 58
description 21
enabling 55
nsrsnapadmin command 102
Index
Index
Q-R
settings 39
PowerSnap
attribute settings 83
backup processes 96
backup records 104
backups and restores 75
client resource 88
components 23
configuration 86
configuration file 23, 84, 93
data flow descriptions 81
features 19
getting started 83
group resource 87
instant backup 78, 96
instant restore 80, 105
invoking a restore 105
invoking backups 96
live backup 78, 99
Module 76
nsrpsd daemon 85
parameter file 23
parameter settings 89
ps_opaque_pfilename file 85
requirements 76
restore from secondary storage 80, 107
restore processes 105
rollback restore 80, 105
rollover backup 78, 99
Snapshot Policy resource 87
Snapshot Pool resource 87
types of backups 77
types of restore 79
variables 23
PowerSnap Module 84
prev_bk_restore parameter 39
problems, backup or restore 124
processes, NetWorker Module 24
profile, using different for restore 114
program
brarchive 97, 99
brbackup 97, 99
nsrd 96, 99
nsrexecd 96, 99
nsrindexd 97, 100, 102
nsrmmdbd 97, 100, 102
nsrsapsv 97, 99
148
savefs 96, 99
savegrp 96, 99
ps_archive_mode 89
ps_backup_mode 89
ps_exclude_archive_bi_run_nums 90
ps_exclude_archive_paths 91
ps_exclude_backup_bi_run_nums 90
ps_exclude_backup_paths 91
ps_group_objs 92
ps_inquire_mode 89
ps_opaque_pfilename 89
ps_opaque_pfilename file 85
ps_opaque_pfilename parameter 23, 93
ps_ps_before_nonps 92
ps_restore_mode 89
Q
query
PowerSnap backup records
query_index parameter 39
104
R
raw directories 40
raw_dir parameter 40
recover, description 16
Recovery Manager 19
See also RMAN
related documentation 27
release information, verifying 123
Remote Exec services 4647
Remote User (Windows) 55
report, backup session 50, 63
requirements
PowerSnap 76
resources, NetWorker 31, 36
client 54
configuring 31
group 31
pool
and pool parameter 31, 39
configuring 31
schedule 32
server 32
restore
Index
S-S
root, setting owner to
30
S
SAP R/3
components 22
features 18
initialization file 4243
sapclone
command 65
description 21
options 66
syntax 65
SAPDBA 24
backup process 24
components 22
configuring 42
description 22
features 18
restore process 26
utilities 18
save
bootstrap file 49
command 40
save sets
cloning 65
description 54
expiry 70
maximum size parameter 41
naming 41
parameter 40
setting 22
viewing 69
save streams, setting 38
savefs command 96, 99
savegrp command 49, 96, 99
savesets parameter 40
scanner command 70
scheduled backup
configuration file 55, 5758
tasks 53
sem_timeout parameter 40
semaphore file 40
server resource parameter 40
serverless snapshot backup 78
Index
a single tablespace 113

all tablespaces 113
brrestore, syntax 113
by datafile ID 114
by ID range 114
cluster data 72
command line options 113
data 69
description 16
diagram 26
entire database instance 70, 113
from secondary storage 80, 107
full 70
instant 80, 105
monitoring 72
options, syntax 113
parameter file used for setting 114
PowerSnap 79
previous backup if not found 39
process described 24
processes 105
reviewing report log 72
rollback 80, 105
single database object 70
using a different profile 114
using NetWorker Module 113
restore messages, suppress 113
restore process
with RMAN 26
with SAPDBA 26
retention policy
expiration 70
manual backup 49
retry_count, setting 40
reviewing
backups 50, 63
restore logs 72
RMAN 23
backup process 25
enabling 43
environment variables 43, 115
features with 19
restore process 26
rman_parms parameter 23, 43
rollback restore 80, 105
rollover backup 78, 99
149
Index
Index
T-V
service
nsrd 96, 99
nsrexecd 96, 99
nsrindexd 97, 100, 102
nsrmmdbd 97, 100, 102
setting backint ownership 30
single database object, restoring 70
single tablespace, restoring 113
snap set 78
snapshot 78, 96
Snapshot Policy resource 87
Snapshot Pool resource 87
snapshot-based backup 78
special terms 16
ss_group_by_fs parameter 41
ss_size_max parameter 41
ssnameformat parameter 41
starting attribute 52
suppress restore messages 113
symlink attribute 52

NSR_DEBUG_FILE 118
NSR_DEBUG_LEVEL 118
NSR_GROUP 95, 119
NSR_NWPATH 119
NSR_PROXY_PFILE 119
NSR_SERVER 95, 121
NSR_SNAP_TYPE 94
PowerSnap 23, 93
verbose logs parameter 41
viewing save sets 69
virtual node 35
T
tablespaces, restoring 113
temporary files directory 34
testing 124
timeout period 40
troubleshooting tips 123
U
uid bit 30
user encryption, SAP 52
user-configurable components
username of SAP user 57
20
V
validation of server indexes 39
variables
mandatory 117, 119121
NSR_BROWSE 116
NSR_CLIENT 95, 116
NSR_DATA_MOVER 93
150

Nmsapag 30

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Nmsapag 30

Caricato da

Copyright:

Formati disponibili

NetWorker

Module for SAP R/3 with Oracle

4. MAINTENANCE AND SUPPORT

8.3 Effect of Termination. Upon termination of this EULA, Licensee

5.1 Media and Documentation. Legato warrants that if the media or

5.2 Limited Software Warranty. Subject to the conditions and limitations

9.2 Government Restricted Rights. Any Software which is acquired

9.3 Export and Import Controls. Regardless of any disclosure made by

Chapter 1: Introduction............................................................................... 15.

Summary of Processes ....................................................................................................24.

Chapter 2: Basic Software Configuration..................................................29.

Chapter 3: Manual Backups........................................................................45.

Chapter 4: Scheduled Backups ..................................................................53.

Chapter 5: Cloning Save Sets .................................................................... 65.

Chapter 6: Restoring Data .......................................................................... 69.

Chapter 7: PowerSnap Backups and Restores ........................................ 75.

Configuring the NetWorker Snapshot Policy Resource .............................................87.

Appendix A: Commonly Used Command Options for brbackup,

Appendix B: Environment Variables for RMAN ......................................115.

Appendix C: Troubleshooting .................................................................123.

Glossary ..................................................................................................... 135.

Names of line commands,

The nsradmin command starts the

Displayed messages are also written to

A variable that must be

Examples and information

media waiting: recover waiting for

The specifications are created, one for each

fixed-width, Commands and options that nsr_shutdown -a

A path or an order to follow Volume>Change Mode>Appendable

Information that must be

Information and Services

Customers with an active support agreement have access to the LEGATO

Licensing and Registration

Licensing and Registration

(650) 812 6000 (option 3, option 2)a

a. Contact information for the Americas, Asia, and the Pacific.

To comment on a particular guide, complete the Comments form at

"Importance of Backing Up Mission-Critical Data" on page 15

Importance of Backing Up Mission-Critical Data

Naming Conventions Used in This Guide

Naming Conventions Used in This Guide

Table 1. Naming Conventions Used in This Guide

SAP R/3 backup utilities, specifically the brbackup,

The shortened form, used throughout this guide, for

The name of the Oracle database instance that you

restore and recover

This guide follows Oracle terminology, which

Basic Network Configuration

The NetWorker storage management server has NetWorker server

Each database server has NetWorker client software, NetWorker Module

Figure 1 on page 17 shows a sample configuration with the NetWorker server

SAP R/3 Server

Windows Client without database

UNIX Client without database

NetWorker Server Software Features

NetWorker Server Software Features

Save group, pool, and client configuration

NetWorker Module Software Features

BRTools Software Features

BRTools (comprised of the brbackup, brrestore, brarchive, and other

Invoking the brbackup command directly or from the SAPDBA Backup

Invoking the brarchive command directly or from the SAPDBA Backup