Legato NetWo 爀欀攀爀䴀漀搀甀氀攀昀漀爀ਠSAP R/3 with O 爀 …

NetWorker™

Module for SAP R/3® with Oracle®

Release 3.0Multiplatform Version

Administrator’s Guide

Copyright © 2003, LEGATO Software, a division of EMC. All rights reserved. This product may be covered by one or more of thefollowing 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, Administrator’s Guide

December 200301-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 anonexhaustive 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 thisdocument for identification purposes only.Acrobat, Adobe / Adobe Systems, Inc.Apple, Macintosh / Apple Computer, Inc.Caldera Systems, SCO, SCO OpenServer, UnixWare / Caldera, Inc.TELEform / CardiffCheck 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 CorporationFujitsu / Fujitsu, Ltd.Hewlett-Packard, HP, HP-UX, HP Tru64, HP TruCluster, OpenVMS, ProLiant / Hewlett-Packard CompanyAIX, DB2, DB2 Universal Database, Domino, DYNIX, DYNIXptx, IBM, Informix, Lotus, Lotus Notes, OS/2, PTX, ptx/ADMIN, RaidPlus, ServeRAID, Sequent, Symmetry, Tivoli, / IBM CorporationInstallShield / InstallShield Software CorporationIntel, Itanium / Intel CorporationLinux / Linus TorvaldsActive Directory, Microsoft, MS-DOS, Outlook, SQL Server, Windows, Windows NT / Microsoft CorporationNetscape, Netscape Navigator / Netscape Communications CorporationData ONTAP, NetApp, NetCache, Network Appliance, SnapMirror, SnapRestore / Network Appliance, Inc.IntraNetWare, NetWare, Novell / Novell, Inc.Oracle, Oracle8i, Oracle9i / Oracle CorporationNetFORCE / Procom Technology, Inc.DLTtape / Quantum CorporationRed Hat / Red Hat, Inc.R/3, SAP / SAP AGIRIX, OpenVault, SGI / Silicon Graphics, Inc.SPARC / SPARC International, Inc.a

ACSLS, REELbackup, StorageTek / Storage Technology CorporationSolaris, 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 CorporationWumpusWare / WumpusWare, LLCUNIX / 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 SoftwareA Division of EMC Corporation

End-User License AgreementTHIS PRODUCT CONTAINS CERTAIN COMPUTER PROGRAMS AND OTHER PROPRIETARY MATERIAL, THE USE OF WHICH IS SUBJECT TOTHIS END-USER LICENSE AGREEMENT (THE "EULA"). DO NOT PROCEED WITH THE INSTALLATION OF THIS PRODUCT UNTIL YOU (LATERDEFINED AS LICENSEE) HAVE READ THIS EULA AND AGREE TO BE BOUND BY AND BECOME A PARTY TO THIS EULA. BY PROCEEDINGWITH THE INSTALLATION OF THIS PRODUCT (OR AUTHORIZING ANY OTHER PERSON TO DO SO), YOU AND YOUR COMPANY ACCEPTTHIS EULA AND YOU REPRESENT THAT YOU ARE AUTHORIZED TO DO SO. IF YOU ARE ACCESSING THE PRODUCT ELECTRONICALLYINDICATE YOUR ACCEPTANCE OF THESE TERMS BY SELECTING THE "ACCEPT" BUTTON AT THE END OF THE EULA. IF YOU DO NOTAGREE 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 THEPRODUCT IS ACCESSED ELECTRONICALLY, SELECT THE "DECLINE" BUTTON AT THE END OF THIS EULA AND RETURN PROOF OFPAYMENT IN ACCORDANCE WITH THE ABOVE REFERENCED RETURN/REFUND PROCESS. WRITTEN APPROVAL IS NOT A PREREQUISITETO THE VALIDITY OR ENFORCEABILITY OF THIS EULA AND NO SOLICITATION OF ANY SUCH WRITTEN APPROVAL BY OR ON BEHALF OFLEGATO SHALL BE CONSTRUED AS AN INFERENCE TO THE CONTRARY. IF YOU HAVE ORDERED THIS PRODUCT, LEGATO'S ACCEPTANCEIS EXPRESSLY CONDITIONAL ON YOUR ASSENT TO THESE TERMS TO THE EXCLUSION OF ALL OTHER TERMS; IF THESE TERMS ARECONSIDERED AN OFFER BY LEGATO, ACCEPTANCE IS EXPRESSLY LIMITED TO THESE TERMS.

1. DEFINITIONS

1.1 Authorization Code: means the unique code provided to Licensee byLegato for permanent activation of the Software. The Authorization Codeis provided to Licensee once the Enabler Code is registered with Legato.The Authorization Code may be tied to a unique machine ID codesupplied by Licensee.

1.2 Documentation: Documentation: means the user reference materialson any media, provided by Legato for use with the Software.

1.3 Enabler Code: means the code provided by Legato for activation of theSoftware.

1.4 Licensee: means the person or entity acquiring this License or forwhom this License was acquired.

1.5 Software: means the object code copy of the software programprovided to You in association with this EULA, together with theassociated original media and all accompanying Documentation, andtogether with all Updates that may be provided by Legato to You fromtime to time.

2. OWNERSHIP AND ADMINISTRATION OF SOFTWARE

2.1 Ownership and Title. As between the parties, Legato, and itslicensors, own and shall retain all right, title, and interest in and to: (i) theSoftware including all intellectual property rights embodied therein; (ii)all of the service marks, trademarks, trade names, or any otherdesignations associated with the Software; and (iii) all copyrights, patentrights, trade secret rights, and other proprietary rights relating to theSoftware.

2.2 Software Activation. Legato employs Enabler Codes andAuthorization Codes that enable the use of the Software. The Software isshipped in a ”Media Kit” which consists of object code software onCD-ROM and an Enabler Code for initial activation of the Software or theSoftware and Enabler Code may be delivered electronically. Once Legatoreceives confirmation from Licensee that the Software is installed with thecorrect Enabler Code, and is provided with the host ID information,Legato will provide the Authorization Code to Licensee. Legatoadministers the generation and distribution of Enabler and AuthorizationCodes, which administration may be modified by Legato from time totime.

2.3 Administration of Software. Legato may include on the media withthe Software additional computer programs which are not currentlylicensed for use by Licensee and to which the Enabler Code orAuthorization code will not permit access. Inclusion of such additionalcomputer programs in no way implies a license from Legato and access oruse of such programs is strictly prohibited unless Licensee procures theright to use any such program and the applicable Enabler Code isprovided thereto.

3. LICENSE GRANT

3.1 Grant. Legato grants to Licensee a non-exclusive, nontransferable,non-sublicensable, perpetual (unless terminated in accordance with theprovisions of this EULA), license (the “License”) to (i) use the Softwareinstalled in accordance with the Documentation and only on the licensedcomputer(s) solely for its own internal operations; and (ii) move theSoftware temporarily in case of computer system malfunction. TheSoftware may be licensed: (a) on a per copy or per seat basis, on a physicalor virtual machine, (b) based upon the number of mailboxes or the numberof non-concurrent users for which it may be used, or (c) based upon data

volumes it supports. The License granted under this EULA does notconstitute a sale of the Software or any portion or copy of it. Licensee maynot use the Software on more than one computer system unless otherwisespecifically authorized by an explicit Software product, or additionallicenses for additional computers are purchased. Rights not expresslygranted are reserved by Legato.

3.2 Copies. Licensee may make copies of the Software provided that anysuch copy is: (i) created as an essential step in utilization of the Softwareas licensed and is used in no other manner; or (ii) used for archivalpurposes. All trademark and copyright notices must be reproduced andincluded on such copies. Licensee may not make any other copies of theSoftware.

3.3 Restrictions on use. Licensee shall not, and shall not aid, abet, orpermit any third party to: (i) decompile, disassemble, or otherwise reverseengineer or attempt to reconstruct or discover any source code orunderlying ideas or algorithms of the Software by any means whatsoever;(ii) remove any identification, copyright, or other notices from theSoftware; (iii) provide, lease, lend, use for timesharing or service bureaupurposes; (iv) create a derivative work of any part of the Software; or (v)develop methods to enable unauthorized parties to use the Software. If EClaw is applicable, the restrictions in Section 3.3 (i) are limited so that theyprohibit such activity only to the maximum extent such activity may beprohibited without violating the EC Directive on the legal protection ofcomputer programs. Notwithstanding the foregoing, prior todecompiling, disassembling, or otherwise reverse engineering any of theSoftware, Licensee shall request Legato in writing, to provide Licenseewith such information or assistance and Licensee shall refrain fromdecompiling, disassembling, or otherwise reverse engineering any of theSoftware unless Legato cannot or has not complied with such request in acommercially 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 anyadditional terms or conditions to this EULA.

3.5 Updates. This section applies if the Software acquired is an update tothe original Software (the “Update”). An Update does not constitute alegally licensed copy of the Software unless purchased as an Update to apreviously licensed version of the same Software. The Update may onlybe used in accordance with the provisions of this EULA. The Update,together with the original Software, constitutes one (1) legally licensedcopy of the Software.

3.6 Evaluation License. This Section applies if the Software is being usedfor an initial thirty (30) day evaluation period. The license is valid only fora period of thirty (30) days from the delivery of the Software, and isdesigned to allow Licensee the right to evaluate the Software during suchperiod. In the event that Licensee desires to continue to license theSoftware, Licensee must purchase a license to the Software. Upon suchpurchase, Licensee will be provided with an Enabler Code in accordancewith Section 2.2 above. In the event Licensee determines not to purchasea license for the Software at the end of such thirty (30) day evaluationperiod, then Licensee’s rights under this EULA shall terminateautomatically and Licensee shall promptly return to Legato or destroy allcopies of the Software and so certify to Legato.

3.7 General Public License ("GPL"). The Software may include one ormore components which are derived from software subject to a GeneralPublic License. Any such components are licensed exclusively under theapplicable 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 providesuch services under separate EULA.

5. LIMITED WARRANTY

5.1 Media and Documentation. Legato warrants that if the media ordocumentation are damaged or physically defective at the time of deliveryof the first copy of the Software to Licensee and if defective or damagedproduct is returned to Legato (postage prepaid) within thirty (30) daysthereafter, then Legato will provide Licensee with replacements at no cost.

5.2 Limited Software Warranty. Subject to the conditions and limitationsof liability stated herein, Legato warrants for a period of thirty (30) daysfrom the delivery of the first copy of the Software to Licensee that theSoftware, as delivered, will materially conform to Legato’s then currentpublished Documentation for the Software. This warranty covers onlyproblems reported to Legato during the warranty period. For customersoutside of the United States, this Limited Software Warranty shall beconstrued to limit the warranty to the minimum warranty required by law.

5.3 Remedies. The remedies available to Licensee hereunder for any suchSoftware which does not perform as set out herein shall be either repair orreplacement, or, if such remedy is not practicable in Legato’s opinion,refund of the license fees paid by Licensee upon a return of all copies of theSoftware to Legato. In the event of a refund this EULA shall terminateimmediately without notice with respect to such Software.

6. WARRANTY DISCLAIMER

6.1 Warranty Disclaimer. EXCEPT FOR THE LIMITED WARRANTYPROVIDED IN SECTION 5 ABOVE, ALL SOFTWARE IS PROVIDED "ASIS". LEGATO AND ITS LICENSORS MAKE NO WARRANTIES WITHRESPECT TO ANY SOFTWARE AND DISCLAIMS ALL STATUTORY ORIMPLIED WARRANTIES, INCLUDING WITHOUT LIMITATIONWARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE, OR ARISING FROM A COURSE OF DEALING OR USAGEOF TRADE AND ANY WARRANTIES OF NONINFRINGEMENT.LEGATO DOES NOT WARRANT THAT THE SOFTWARE WILL MEETANY REQUIREMENTS OR THAT THE OPERATION OF SOFTWAREWILL BE UNINTERRUPTED OR ERROR FREE. ANY LIABILITY OFLEGATO WITH RESPECT TO THE SOFTWARE OR THEPERFORMANCE THEREOF UNDER ANY WARRANTY, NEGLIGENCE,STRICT LIABILITY OR OTHER THEORY WILL BE LIMITEDEXCLUSIVELY TO THE REMEDIES SPECIFIED IN SECTION 5.3ABOVE. Some jurisdictions do not allow the exclusion of impliedwarranties or limitations on how long an implied warranty may last, sothe 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 WITHRESPECT TO THE SUBJECT MATTER OF THIS EULA UNDER ANYCONTRACT, NEGLIGENCE, STRICT LIABILITY, OR OTHER LEGALOR EQUITABLE THEORY FOR: (I) ANY INDIRECT, SPECIAL,INCIDENTAL OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSEDAND WHETHER OR NOT ADVISED IN ADVANCE OF THEPOSSIBILITY OF SUCH DAMAGES; OR (II) DAMAGES FOR LOSTPROFITS OR LOST DATA; OR (III) COST OF PROCUREMENT OFSUBSTITUTE GOODS, TECHNOLOGY, SERVICES, OR RIGHTS; OR (IV)FOR AMOUNTS IN EXCESS OF THOSE RECEIVED BY LEGATO FORTHE PARTICULAR LEGATO SOFTWARE THAT CAUSED THELIABILITY . Because some jurisdictions do not allow the exclusion orlimitation of incidental or consequential damages, Legato's liability insuch 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 inaccordance with its provisions.

8.2 Termination. Legato may terminate this EULA, without notice, uponLicensee's breach of any of the provisions hereof.

8.3 Effect of Termination. Upon termination of this EULA, Licenseeagrees to cease all use of the Software and to return to Legato or destroythe Software and all Documentation and related materials in Licensee'spossession, and so certify to Legato. Except for the License granted hereinand as expressly provided herein, the terms of this EULA shall survivetermination.

9. MISCELLANEOUS

9.1 Governing Law. This EULA shall be governed by the laws of theCommonwealth of Massachusetts, without regard to the principles ofconflict of laws or the United Nations Convention on Contracts for theInternational Sale of Goods.

9.2 Government Restricted Rights. Any Software which is acquireddirectly or indirectly for or on behalf of the United States of America, itsagencies and/or instrumentalities ("U.S. Government"), is provided withRestricted Rights. Use, duplication, or disclosure by the U.S. Governmentis subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rightsin Technical Data and Computer Software clause at DFARS 252.227-7013or subparagraphs (c)(1) and (2) of the Commercial Computer Software -Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer isLegato Software, a division of EMC Corporation, 2350 W. El Camino Real,Mountain View, CA 94040. The Software is a commercial softwareproduct, licensed on the open market at market prices, and was developedentirely at private expense and without the use of any government funds.

9.3 Export and Import Controls. Regardless of any disclosure made byLicensee to Legato of an ultimate destination of the Products, Licenseemay not directly or indirectly export or transfer any portion of theSoftware, or any system containing a portion of the Software, to anyoneoutside the United States (including further export if Licensee tookdelivery outside the U.S.) without first complying with any export orimport controls that may be imposed on the Software by the U.S.Government or any country or organization of nations within whosejurisdiction Licensee operates or does business. Licensee shall at all timesstrictly comply with all such laws, regulations, and orders, and agrees tocommit 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 byLicensee without the prior written consent of Legato, which shall not beunreasonably withheld. Legato may assign or otherwise transfer any orall of its rights and obligations under this EULA upon notice to Licensee.

9.5 Sole Remedy and Allocation of Risk. Licensee's sole and exclusiveremedies are set forth in this EULA. This EULA defines a mutuallyagreed-upon allocation of risk, and the License price reflects suchallocation of risk.

9.6 Equitable Relief. The parties agree that a breach of this EULAadversely affecting Legato's intellectual property rights in the Softwaremay cause irreparable injury to Legato for which monetary damages maynot be an adequate remedy and Legato shall be entitled to equitable reliefin addition to any remedies it may have hereunder or at law.

9.7 No Waiver. Failure by either party to enforce any provision of thisEULA will not be deemed a waiver of future enforcement of that or anyother provision, nor will any single or partial exercise of any right orpower hereunder preclude further exercise of any other right hereunder.

9.8 Severability. If for any reason a court of competent jurisdiction findsany provision of this EULA, or portion thereof, to be unenforceable, thatprovision of the EULA will be enforced to the maximum extentpermissible so as to effect the intent of the parties, and the remainder ofthis EULA will continue in full force and effect.

10. ENTIRE EULA

10.1 This EULA sets forth the entire understanding and EULA between theparties and may be amended only in a writing signed by authorizedrepresentatives of both parties. No vendor, distributor, reseller, dealer,retailer, sales person, or other person is authorized by Legato to modifythis EULA or to make any warranty, representation, or promise which isdifferent than, or in addition to, the warranties, representations, orpromises made in this EULA. No pre-printed purchase order terms shallin any way modify, replace or supersede the terms of this EULA.

LEGATO NetWorker Module for SAP R/3 with Oracle, Release 3.0, Multiplatform VersionAdministrator’s Guide 5

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 VersionAdministrator’s Guide

Contents

6

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

8

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 LegatoNetWorker® Module for SAP R/3 with Oracle software (referred to in thisguide as simply the NetWorker® Module software).

Install this multiplatform NetWorker Module software on the supportedUNIX, Linux, or Microsoft Windows server and clients before using theinformation presented in this guide. For installation instructions, refer to theLEGATO NetWorker Module Installation Guide for installation instructions.

Post-release information is contained in the Release Supplement for thisproduct. This document is available is available at www.legato.com. Refer to theweb site periodically to view the latest Release Supplement.

AudienceThe information in this guide is intended for system administrators who areresponsible for installing software and maintaining the servers and clients ona network. Operators who monitor the daily backups may also find thismanual useful.

Product DocumentationFor a complete list of documentation related to this product, see <insert x-refhere>. Most of the documents are in Adobe Acrobat Portable DocumentFormat (PDF), and can be viewed by downloading and installing the AdobeAcrobat Reader. The Reader is available in the /viewers/acroread directory on theLEGATO® Documentation Suite CD-ROM, or directly from Adobe. To installand use the Reader on the preferred platform, refer to the instructions in theCD-ROM’s /viewers/acroread/readme.txt file or at the Adobe web site.


Conventions

12

ConventionsThis document uses the following typographic conventions and symbols tomake information easier to access and understand.

Convention Indicates Example

boldface Names of line commands,daemons, options,programs, or scripts

The nsradmin command starts thecommand line version of the NetWorkerAdministrator program.

italic in text Pathnames, filenames,computer names, new termsdefined in the Glossary orwithin the chapter, oremphasized words

Displayed messages are also written to/nsr/logs/daemon.log.

The specifications are created, one for eachswap file, in c:\pagefile.sys.

italic incommand line

A variable that must beprovided in the commandline

nwadmin -s server_name

fixed-width Examples and informationdisplayed on the screen

media waiting: recover waiting for8mm 5GB tape volume name

fixed-width,boldface

Commands and options thatmust be entered exactly asshown

nsr_shutdown -a

Menu_Name>Command

A path or an order to followfor making selections in theuser interface

Volume>Change Mode>Appendable

Important: Information that must beread and followed to ensuresuccessful backup andrecovery of data

Important: Use the no_verify option withextreme caution.

Preface


Information and ServicesLEGATO offers a variety of methods (including e-mail, telephone, and faxsupport) to obtain company, product, and technical information.

General Information

The LEGATO web site provides most of the information that customers mightneed, including technical bulletins and binary patches from its FTP site. Forspecific sales or training needs, e-mail or call LEGATO.

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 LEGATOintegrated product knowledge base. Help with software issues is alsoavailable through Technical Support.

• Customers without an active support agreement can contact Support Salesand Renewal to purchase annual software update subscriptions, ortechnical support services for per-update/per-incident assistance.

Service or ResourceTechnicalBulletins

BinaryPatches

Companyand ProductInformation Training

www.legato.com Yes Yes Yes Yes

ftp.legato.com(log in as anonymous)

Yes Yes

LEGATO Sales(650) 210-7000 (option 1)[email protected]

Yes

LEGATO EducationServices(650) [email protected]

Yes

http://www.legato.com


Licensing and Registration

14

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 aboutlicensing, contact LEGATO by using one of the following methods.

Customer FeedbackLEGATO welcomes comments and suggestions about software features, theinstallation procedure, and its documentation.

• To comment on a particular guide, complete the Comments form atwww.legato.com. Navigate to the documentation page and click theComments link beside the name of the guide. All comments are reviewedand acted upon, usually within one business day.

• To help improve our documentation in general, complete a brief survey atwww.legato.com. Navigate to the documentation page and click the link tothe survey.

• To provide other suggestions and comments, send e-mail [email protected]. Although LEGATO cannot respond personally toevery request, all comments and suggestions are considered duringproduct design.

Licensing and Registration Contact

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

+31 23 554 8881b

a. Contact information for the Americas, Asia, and the Pacific.b. Contact information for Europe, the Middle East, and Africa.

Fax number (650) 745-1477a

+31 23 554 8808b

E-mail [email protected]

[email protected]





Chapter 1: Introduction

This chapter describes the main features and components of the LegatoNetWorker 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 DataIt is important to back up computer systems to protect them from the loss ofvaluable data. In a network environment, where users depend on shared dataand the amount of data continuously grows, the need to manage data becomescrucial.

A viable backup strategy includes regular backups of databases and archivelogs. Without archive logs, you can recover a database only to the time of itslast full backup.


1

Naming Conventions Used in This Guide

16

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

Basic Network ConfigurationThis section describes a network configuration for regular backup andrecovery 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:

• The NetWorker storage management server has NetWorker serversoftware installed.

• A backup storage device is either attached to the NetWorker server or ona separate NetWorker storage node server.

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 Modulesoftware

The shortened form, used throughout this guide, forthe complete name, Legato NetWorker Module forSAP R/3 with Oracle, release 3.0 software.

<ORACLE_SID> The name of the Oracle database instance that youwant to back up, usually the argument for thebrbackup or brarchive -u option.

restore and recover This guide follows Oracle terminology, whichdistinguishes between restoring and recovering adatabase.• 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, whichuses recover for all data retrieval activities (asdistinguished from the UNIX restore command).



1

17

• Each database server has NetWorker client software, NetWorker Modulesoftware, SAP software, and Oracle database software installed.

• Each Networker client, including each database server, has Networkerclient software installed.

Figure 1 on page 17 shows a sample configuration with the NetWorker serversoftware and the database server software on separate computers.

Figure 1. NetWorker Server and the Database Server on Separate Systems

Summary of FeaturesThis section describes the features of the related NetWorker server and clientsoftware, NetWorker Module software, SAP R/3 software, and optionalOracle RMAN software that work together to provide storage managementservices. For a summary of software components, see "Summary ofComponents and Settings" on page 20.

Windows Client without databaseWindows NetWorker Client

UNIX Client without databaseUNIX NetWorker Client

Database Server

SAP R/3 ServerOracle database

NetWorker ModuleNetWorker Client

NetWorker Server


1

NetWorker Server Software Features

18

NetWorker Server Software Features

The Legato NetWorker software provides data storage management servicesthat protect and help manage data across an entire network.

The main NetWorker server software features that work in conjunction withthe 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-onmodule for NetWorker client software that provides a backup and restoreinterface between the SAP BRTools program and the NetWorker server. Themain component of the NetWorker Module is the backint program, whichprovides backup, inquiry, and restore processes for all Oracle and SAP R/3files.

The NetWorker Module software enables you to perform the followingoperations 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 providedthrough the following SAP R/3 features:

• BRTools (comprised of the brbackup, brrestore, brarchive, and otherutilities).

• SAP database administration (SAPDBA) utility, a menu-driven interfaceto BRTools.



1

19

Invoking the brbackup command directly or from the SAPDBA BackupDatabase 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 BackupArchive Logs screen passes the offline redo logs to backint for backup.

Oracle RMAN Software Features

The NetWorker Module software supports SAP R/3’s use of Oracle’s RecoveryManager (RMAN) backup and restore utility, which is available with Oracle8or later databases. Use of RMAN with the NetWorker Module is optional, andyou can continue to use the NetWorker Module’s backint program as the solebackup and restore tool. If you want to use RMAN to back up Oracledatabases, 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 Oracledocumentation.

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 immediatelybacked up to a traditional storage medium, such as tape, or backed up at a laterbackup session. Many instant backups can be performed in a single day, thusreducing the exposure to data loss.

Instant backups protect only against logical failures. To protect againstphysical failures, the snapshot must be backed up to a traditional storagemedium.

Whether or not a backup uses the PowerSnap features is determined by Client,Group, and Policy resource configurations.


1

Summary of Components and Settings

20

Summary of Components and SettingsThis section summarizes the user-configurable components and basic settingsof the various products used with the NetWorker Module, and how they workwith their associated binary executable files to provide storage managementservices. 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. ThisNetWorker Server component is used to configure NetWorker resources, suchas Client, Group, and Pool. For details, refer to the Legato NetWorkerAdministrator’s Guide

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 Binaryexecutable

This backup, restore, and inquiry programprovides an interface to SAP BRTools. It usesconfigurations from the init<ORACLE_SID>.utl file.

init.utl Configurationfile

This is the sample configuration file for the backintprogram and is to be used as a template. Copy thisfile and name it init<ORACLE_SID>.utl, where<ORACLE_SID> is the name of the Oracle databaseinstance that is to be backed up. Use the copy andsave the original.



1

21

log files log files Log files used for the NetWorker Module software.The default location by operating system is asfollows:(UNIX): /nsr/applogs(Windows): C:\Program files\Legato\nsr\applogs

nsrsapsv Binaryexecutable

The scheduled backup program, which invokes theappropriate BRTools executables. It usesconfigurations from the nsrsapsv.cfg template file, orrenamed copy of this file. Specify this file as thebackup command in the NetWorker Clientresource.

nsrsapsv.cfg Configurationfile

The sample configuration file for the nsrsapsvprogram. Copy the sample template file and savethe original.

nsrsapadm Binaryexecutable

Administrative program for nsrsapsv operations;encrypts logon information (os_usr_passwd ororacle_usr_passwd, depending on authorizationmethod) for the user performing a scheduledbackup.

sapclone Binaryexecutable

The save set cloning program. Provides an interfaceto the NetWorker nsrclone program.

Table 2. NetWorker Module Components (Part 2 of 2)



1

NetWorker Client Settings

22

NetWorker Client Settings

Table 3 on page 22 lists the main NetWorker Client resource attributes usedwith the NetWorker Module software. For a complete description ofNetWorker Client resource attributes, refer to the Legato NetWorkerAdministrator’s Guide.

SAP Components

Table 4 on page 22 lists the SAP software components used with theNetWorker Module software.

Table 3. NetWorker Client Resource Settings Used by the NetWorker Module Software

Attribute Description

Backup command Specifies the command used for scheduled backups, includingparameters 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.

Table 4. SAP Components Used by the NetWorker Module Software


BRTools Binaryexecutables

SAP R/3 backup utilities, specifically thebrbackup, brrestore, and brarchive programs(equivalent to NetWorker client save, recover,nsrinfo, and mminfo programs). Invoked bynsrsapsv, SAPDBA, or command line.

SAPDBA Binaryexecutable

Menu-driven interface to BRTools for backup,restore, and inquiry-related operations.

init<ORACLE_SID>.sap Configurationfile

The SAP configuration file. Relevant parametersspecify whether to use the backint program orRMAN for backup, inquire, and restore sessions.



1

23

Oracle Components

Table 5 on page 23 lists the Oracle software components used with theNetWorker Module software.

PowerSnap Components

The NetWorker Module software components that are used specifically toenable and configure PowerSnap features are listed in Table 6 on page 23.

Table 5. Oracle Components Used by the NetWorker Module Software


RMAN Binaryexecutable

Oracle utility for performing backups and restores ofthe Oracle database, using the rman_parms parameter.To enable RMAN, set the backup_dev_type parameter inthe 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 RMANbackup or restore with the NetWorker Module.

Table 6. PowerSnap Components Used by the NetWorker Module Software


init.utl ConfigurationFile

The init<ORACLE_SID>.utl configuration file for thebackint program. The parameters within this file thatare specific to PowerSnap are those with the ps_prefix.

nmsapps.cfg(example name)

ConfigurationFile

User-defined PowerSnap configuration file, in whichthe PowerSnap parameters are set.

ps_opaque_pfilename Parameter Parameter in the init<ORACLE_SID>.utl file thatspecifies the complete file pathname for theuser-defined PowerSnap configuration file, forexample:• On UNIX: /nsr/res/nmsapps.cfg• On Windows:

C:\Program Files\Legato\nsr\res\nmsapp.cfg


1

Summary of Processes

24

Summary of ProcessesThe NetWorker Module software provides storage management services thatconnect NetWorker functionality to SAP R/3 servers running Oracledatabases. The backup and restore processes can be initiated from thefollowing interfaces:

• SAPDBA menu-driven interface• BRTools: brbackup, brarchive, or brrestore commands• NetWorker Module’s nsrsapsv command, used for scheduled backups

Additionally, Oracle’s RMAN can be invoked through these interfaces to backup and restore Oracle databases.

Note: PowerSnap backups must be initiated through the nsrsapsv scheduledbackup 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 theSAP R/3 server running Oracle, brbackup sends a request to the backintprogram. The backint program runs two or more times, as required, to backup the requested Oracle datafiles, control files, online redo logs, and profiles.It sends all the data and process information in parallel streams to theNetWorker server. The data stream is backed up on storage media or aNetWorker storage node, and NetWorker software creates entries in the clientfile index and media database. The final results of the backup are recorded ina 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, andprograms interact during a backup.



1

25

Figure 2. NetWorker and Database Interaction during a Backup

Backup with RMAN

When the Oracle RMAN utility (available with Oracle8 or later) is used to backup an Oracle database, the process is similar to backup that uses SAPDBA,except brbackup sends requests to both RMAN and backint. The followingoccurs as a result:

1. RMAN backs up the Oracle datafiles.

2. The backint backs up the configuration files, logs, and other flat files thatare specific to SAP.

SAP R/3 on Oracle Server

backint (save)

nsrmmdbd

nsrmmd

Client FileIndex

MediaDatabase

NetWorker Client NetWorker Server StorageMedium

nsrd

nsrindexd

backint

brbackup(SAPDBA)

inter-process communication

data


1

Restore with SAPDBA or brrestore

26

Restore with SAPDBA or brrestore

When a restore is initiated from SAPDBA or the brrestore program on the SAPR/3 server running Oracle, brrestore sends a restore request to the backintprogram. The backint program browses the NetWorker server’s client fileindex and restores the specified files in a parallel stream from the NetWorkerserver to the SAP R/3 server running Oracle.

Figure 3 on page 26 shows how NetWorker services, processes, and programsinteract during a restore.

Figure 3. NetWorker and Database Interaction during a Restore

Restore with RMAN

If RMAN is used to restore the Oracle database, RMAN restores the Oracledatabase 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 restorethem by using any of the following:

• The backint program• The NetWorker recover program• BRTools with appropriate command line parameters.

SAP R/3 on Oracle Server

backint (recover)

nsrmmdbd

nsrmmd

Client FileIndex

MediaDatabase

NetWorker Client NetWorker Server StorageMedium

nsrd

nsrindexd

backint

brrestore(SAPDBA)

inter-process communication

data



1

27

Related DocumentationFor further information on the Legato NetWorker Module for SAP R/3 withOracle, 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

• Legato NetWorker Module for SAP R/3 with Oracle, Release 3.0, UNIX, Linux,and Microsoft Windows Version, Release Supplement

• NetWorker PowerSnap Module Installation and Administrator’s Guideappropriate for your implementation

• Legato NetWorker Administrator’s Guide appropriate for yourimplementation

• UNIX man pages• NetWorker Command Reference Guide

• Legato Software Compatibility Guide


1

Related Documentation

28


Chapter 2: Basic Software Configuration

This chapter provides basic configuration instructions for the NetWorkerModule and other supporting software required for backup, recovery, andinquiry of SAP R/3 with Oracle data and other files. Unless otherwise noted,the configurations described in this chapter apply to both manual andscheduled backups.

This chapter describes the following tasks that need to be performed, althoughnot 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


2

Task 1: Configure the Environment

30

Task 1: Configure the EnvironmentUse the following steps to configure the environment for the NetWorkerModule software:

1. Install and enable the NetWorker Module on each Oracle database serverwith SAP R/3 that requires backup and recovery services. Forinstructions, 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 thelocation 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 asBRTools. 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 thebackint program by entering the following command:

chmod 4755 backint

5. For NetWorker 7.x, ensure that the SAP backup user is listed in the UserGroups, and has the following privileges:

• Monitor NetWorker processes• Back up local data• Recover local dataTo verify these settings, run NetWorker Administrator (nwadmin) on theserver:• 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.



2

31

Task 2: Configure the NetWorker ResourcesThe NetWorker resources reside on the NetWorker server and are configuredusing the NetWorker Administrator program.

Table 7 provides resource configuration details that are specific to theNetWorker Module software.

Table 7. NetWorker Resources (Part 1 of 2)

Resource Comments

Client Specifies the NetWorker Client resources for each SAP R/3 serverrunning 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 theNetWorker Module’s parameter file, init<ORACLE_SID>.utl. See thelisting for "expiration" on page 36.

For scheduled backups, the Remote User and Password attribute mayneed to be specified in the Client resource for certain Windowsconfigurations, and setting them is recommended. On UNIX, theseattributes do not need to be specified in the Client resource. For allsystems, 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 NetWorkerModule’s 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 backupdata. 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 Module’s

parameter file, init<ORACLE_SID>.utl.


2

Task 2: Configure the NetWorker Resources

32

For more information on configuring the NetWorker resources, refer to theNetWorker Online Help or the Legato NetWorker Administrator’s Guide.

Schedule Specifies the days of the week or month when scheduled backups runs.

Server Defines the NetWorker server to be used for backup, restore, andinquiry 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 theOracle server or cluster client. The value should match or be greaterthan the parallelism setting found in the NetWorker Module’sparameter file, init<ORACLE_SID>.utl, see "parallelism" on page 38.

• Ensure that a Device resource is configured for each Oracle storagedevice used for backup and restore operations. Each device mustcontain a labeled and mounted volume.

• When performing manual backups, ensure the Manual Saves attributeis set to Enabled.

It is not necessary to specify the SAP backup user in the Administratorattribute.

Table 7. NetWorker Resources (Part 2 of 2)

Resource Comments



2

33

Task 3: Configure the NetWorker Module ParametersDuring backup, restore, or inquire sessions, the NetWorker Module programuses the parameter settings specified (or the default values if not specified)from the init<ORACLE_SID>.utl parameter file. These parameter settingsprovide client, server, pool, group, expiration and other values to the backintprogram.

Important: The names for the server, group, client, and pool specified in theparameter file must match the corresponding resource settings defined on theNetWorker server. An error results if there is a mismatch.

To set a parameter in the init<ORACLE_SID>.utl parameter file, use thefollowing format:

parameter=value

Refer to the following rules when setting parameters:

• Uncomment and modify as necessary all parameters to be used inbackup, restore, or inquire operations.

• Use lowercase parameter names and values.

For descriptions and default values for NetWorker Module parameters, seeTable 8 on page 34.


2

Task 3: Configure the NetWorker Module Parameters

34

For specific instructions on configuring data clusters, see "Task 5: Configure aBackup 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 Descriptioncolumn for defaultlocation on UNIX orWindows

Specifies the full pathname of the log file forrunning 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 Descriptioncolumn for defaultlocation on UNIX orWindows

Specifies the full pathname of the backint log filefor running the brbackup and brrestorecommands.

Default location on UNIX:/nsr/applogs/backint<ORACLE_SID>.log

Default location on Windows:C:\Program Files\Legato\nsr\applogs\backint<ORACLE_SID>.log

Note: To specify a separate log file to usespecifically for restores, modify this parameterbefore running brrestore. Alternatively, thebackint_log parameter can be specified in aninit<ORACLE_SID>_restore.utl file, which can bereferenced from the util_par_file parameter in theinit<ORACLE_SID>_restore.sap file, for example:

brrestore -p init<ORACLE_SID>_restore.sap

backint_tmpdir See Descriptioncolumn for defaultlocation on UNIX orWindows

Specifies the directory name of the backinttemporary files.

Default location on UNIX:/nsr/applogs/

Default location on Windows:C:\Program Files\Legato\nsr\applogs\



2

35

checksum No Specifies whether to perform cyclic redundancychecking (CRC) on restores.

Setting this parameter to Yes excludes using thecompress and encrypt parameters, which shouldbe set to No. If more than one of these parametersis set to Yes, the priority order is: compress,checksum, encrypt.

client Local host Specifies the NetWorker client hostname to use forthe client file index for the current backup.

If you are using the NetWorker Module to back upa virtual cluster client, set this value to the virtualnode name.

During cluster restores, this parameter specifiesthe name of the client with the client file index forthe backup to be restored. For example, to restoredata to a host named saturn using the backup froma host named mars, set this parameter to mars sothat the client file indexes for mars are used.

compress No Compresses data during a backup before the datais passed over the network or written to tape,which can speed up the backup process.Compression increases CPU usage on the SAP R/3server running Oracle, but reduces the amount ofdata sent to the NetWorker server.

Setting this parameter to Yes excludes the use ofchecksum and encrypt parameters, which shouldbe set to No. If more than one of these parametersis set to Yes, the priority order is: compress,checksum, encrypt.




2


36

encrypt No Specifies whether to encrypt the backup data.

Setting this parameter to Yes excludes the use ofcompress and checksum parameters, which shouldbe set to No. If more than one of these parametersis set to Yes, the priority order is: compress,checksum, encrypt.

expiration 2 Weeks For all backups, the expiration parameter sets boththe 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 Clientresource settings unless it specifies a longerperiod of time.

The value must use nsr_getdate format, forexample:

expiration = 2 Weeks

group Default Specifies the backup Group resource that is usedby the NetWorker save program. If not specified,the Default group is used. To assign a value, set theparameter, for example:

group = SAPBackup

Note: The group name must match thecorresponding group attribute in the NetWorkerClient 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 0 Specifies the maximum number of backint sessionlogs to be saved in the backint log file. If the valueis set to 0, all backup logs will be saved in the logfile. See also the "backint_log" parameter on page34.





2

37

notify_done Not specified UNIX only. Executed at the completion of a backupor restore session. Uncomment the option andreplace mailx with the name of the command linee-mail utility to be used as an alert when thebackint program has completed its activity, forexample:

notify_done = mailx -s ’backint done’root

notify_error Not specified UNIX only. Executed at the completion of a failedbackup or restore session. Uncomment the optionand replace mailx with the name of the commandline e-mail utility to be used as an alert if thebackint program encounters any errors during itsactivity, for example:

notify_error = mailx -s ’backint error’root

notify_start Not specified UNIX only. Executed at the beginning of a backupor restore session. Uncomment the option andreplace mailx with the name of the command linee-mail utility to be used as an alert when thebackint program begins its activity, for example:

notify_start = mailx -s ’backint start’root

notify_success Not specified UNIX only. Executed at the completion of asuccessful backup or restore session. Uncommentthe option and replace mailx with the name of thecommand line e-mail utility to be used as an alertwhen the backint program has successfullycompleted its activity, for example:

notify_success = mailx -s ’backintsuccess’ root




2


38

parallelism 8 Specifies the number of save sets or save streams tosend simultaneously to the NetWorker server.Typically, this setting should be equal to the sum ofthe "target sessions" for all of the devices dedicatedto the NetWorker Module.

Ensure that the NetWorker server is configured tosupport this parallelism value or greater, see thelisting for "Server" on page 32.

Note: The Parallelism value will be reduced if it isgreater than the value of the save sets parameter,provided the ss_group_by_fs parameter is set toNo or not set.





2

39

pool Default Specifies the NetWorker media Pool resource,(defined in the NetWorker server), that receivesbackup data from the SAP R/3 server that isrunning Oracle. If not specified, the Default pool isused.

To use a pool other than the Default, uncommentthis parameter and set it equal to the name of thepool, 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 whenusing brbackup or brarchive.

For example, a pool named ARCHData is usedspecifically for archive logs. You can create aseparate parameter file for archive logs, named forexample archiveC11.utl, and set the pool attributeequal to ARCHData. To use this pool to back up thearchive logs, you would enter the followingcommand at the command line:

brarchive -u sys/admin -d util_file -rarchiveC11.utl -m all -s save

prev_bk_restore No UNIX only. Specifies whether to restore theprevious backup if the required backup cannot befound, when the query_index parameter is set toNo.

query_index No UNIX only (Windows is always Yes). Specifieswhether to query the NetWorker server indexes forvalidation of the requested files and backup IDsbefore a restore begins. If set to No, the query doesnot occur.




2


40

raw_dir Not specified Specifies the directory for raw disk partitions. Anyfiles below these directories are considered to beraw disk partitions. Do not set the /dev or /devicesdirectories for raw partitions. They are alreadytreated as raw devices. To specify the directory,uncomment this option, and use a semicolon (;) toseparate the directory paths, for example:

raw_dir = /oracle/data;/sap/data;/lotus/data

retry_count 0 Specifies the number of times that a failed backupis attempted for each save set. Any integer greaterthan 0 is allowed.

savesets 20 To distribute the backup load, a client’s files can bedivided among several save sets, as specified bythis value. If the value is equal to or greater thanthe number of database files, then a separate saveset is made for each file. If the value is smaller thanthe number of database files, then a save set maycontain more than one file.

This value is ignored if the ss_group_by_fsparameter is set to Yes.

sem_timeout 30 Sets the amount of time, in minutes, that backintwaits for brbackup or brconnect to remove thesemaphore file. If the semaphore file is not deleted,backint exits with an error at the end of thistimeout period.

server Local Host The hostname of the NetWorker server that theNetWorker Module uses for backup, restore, andinquiry sessions, for example:

server = prelude

Note: The server name must match the serverattribute specified in the NetWorker Serverresource. If the server parameter is not specified,then the NetWorker Module backs up data to thelocal host.





2

41

ss_group_by_fs No If set to Yes, the savesets parameter is ignored andsave sets are grouped by filesystem instead of filesize. This more efficient grouping of files canimprove performance of scheduled backups, indexlookups, and restore times.

ss_size_max 0 Specifies maximum save set size in megabytes. Ifnot 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 beingbacked up. It uses the formatbackint:<ORACLE_SID>:<full path of the firstfilename in the save set>.

If you set each save set to store one file, then avalue of New simplifies the process of browsingthe media database. The media database willshows each filename as part of the save set name.

Note: If set to New, the NetWorker recover -Scommand cannot be used to restore the database,however the brrestore command can be used.

verbose No Provides more detailed information in the log filefrom save and recover operations.




2

Task 4: Configure the Backup and Restore Utility

42

Task 4: Configure the Backup and Restore UtilityDepending on your configuration needs and preferences, you can performbackups, restores, and inquiries of SAP R/3 data using the SAP BRTools withor without use of Oracle’s RMAN utility. The following examples describe asimple configuration of each of the cases of use with the NetWorker Module.

• For the SAP BRTools, see "Example: Configuring backint as the Backupand Restore Utility" on page 42.

• For the Oracle RMAN utility, see "Example: Configuring RMAN as theBackup 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, andbrrestore commands) to use the backint program for backup, restore, andinquiry operations. For complete instructions, refer to the appropriate SAPdocumentation.

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 enteringone 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 Module’sparameter 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



2

43

• 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: Configurethe NetWorker Module Parameters" on page 33.

Example: Configuring RMAN as the Backup and Restore Utility

The following example describes a simple configuration of Oracle’s RMANutility (available with Oracle8 or later databases), which works with theBRTools utilities, for backup, restore, and inquiry operations. For completeinstructions, 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 Microsoft Windows: %ORACLE_HOME%\DATABASE

• On UNIX: $ORACLE_HOME/dbs

2. Set the backup_dev_type parameter to use the RMAN utility by entering thefollowing:

# backup device type

backup_dev_type = rman_util

3. Uncomment the line for the rman_parms parameter and set it to includeeach NetWorker software-specific (NSR_*) environment variable that isappropriate for your backup, restore, and inquiry sessions.

For a list of these environment variables, see Table 21 on page 116. Theenvironment variable names must be uppercase and use the followingsyntax:rman_parms="ENV=(<var1>=<value>, <var2>=<value>, ...)"

For example:rman_parms="ENV=(NSR_SERVER=server_name,NSR_DATA_VOLUME_POOL=pool_name)"


2

Task 5: Configure a Backup of Cluster Data

44

Task 5: Configure a Backup of Cluster DataNote: If you are not using a cluster configuration, ignore this task.

The NetWorker Module backs up all Oracle data residing on private disks in acluster, 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 ofthe cluster, but only on the private disks of the nodes. For details oninstalling the NetWorker Module, refer to the Legato NetWorker Module forSAP R/3 with Oracle Installation Guide.

2. Ensure that a NetWorker Client resource is created for each physical nodeand 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 youwant:

• To back up Oracle data located on a private disk, use the physicalnode name as the client name.

• To back up Oracle data located on a shared disk that belongs to avirtual system, use the network name associated with the virtualsystem as the client name.

For details on the NetWorker Module’s client parameter settings, see"client" on page 35.


Chapter 3: Manual Backups

This chapter describes how to configure and perform manual backups ofeither online or offline Oracle database instances residing on a SAP R/3 serverrunning Oracle. It assumes that you have properly configured the basicsettings for manual backups, described in "Chapter 2: Basic SoftwareConfiguration" 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 BackupsYou can use the following to perform manual backups:

• The SAPDBA menu interface• The brbackup or brarchive command• Oracle’s RMAN utility, invoked through either SAPDBA or the brbackup

or brarchive command

Each of these methods uses the NetWorker Module’s backint program.

Note: PowerSnap operations are not supported for manual backups, and mustbe initiated through the nsrsapsv scheduled backup program. For details, see"Chapter 7: PowerSnap Backups and Restores" on page 75.


3

Performing an Offline Manual Backup

46

Important: Manual backups do not automatically back up the NetWorkerserver’s client file index database and the bootstrap save set. Regular backups ofthese components are needed to ensure adequate protection for disasterrecovery. For details, see "Backing Up the Client File Indexes and Bootstrap"on page 49

Performing an Offline Manual BackupPerform offline backups when network traffic is low, typically in the eveningsor on weekends, because the SAP R/3 services and the Oracle databaseinstance 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 Module’sinit<ORACLE_SID>.utl file. For details on configuring backupparameters, see "Task 3: Configure the NetWorker Module Parameters"on page 33.

• The parameters for the backup device type (backup_dev_type) and backuputility 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 theNetWorker Remote Exec services are all running.

How to Perform an Offline Backup

For complete instructions on how to perform an offline backup, refer to thefollowing:

• To perform an offline backup using the SAPDBA menu interface or thebrbackup or brarchive command, refer to the appropriate SAPdocumentation.

• To perform an offline backup using the RMAN utility, refer to theappropriate Oracle documentation.



3

47

The following is an example of an offline backup using the brbackupcommand:

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 theentire 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 upto the NetWorker server.

2. Back up the client file indexes and bootstrap. For instructions, see "BackingUp the Client File Indexes and Bootstrap" on page 49.

Performing an Online Manual BackupAn online backup allows users to continue using SAP R/3 services and Oracledatabase instances while the Oracle tablespaces on the SAP R/3 server arebeing backed up.

Before you begin an online backup, ensure the following:

• The backup parameters are set in the NetWorker Module’sinit<ORACLE_SID>.utl file. For details on configuring the backupparameters, see "Task 3: Configure the NetWorker Module Parameters"on page 33.

• The parameters for the backup device type (backup_dev_type) andbackup utility parameter file (util_par_file) are set in the SAP utilitiesprofile, init<ORACLE_SID>.sap. For details on configuring the utilitiesprofile, see "Task 4: Configure the Backup and Restore Utility" on page 42.

• The NetWorker server, the SAP R/3 server running Oracle, and theNetWorker Remote Exec services are all running.

• The Oracle database instance is in ARCHIVELOG mode. To set an Oracledatabase instance to ARCHIVELOG mode, refer to the appropriateOracle manual.


3

Performing an Online Manual Backup

48

How to Perform an Online Backup

For complete instructions on how to perform an online backup, refer to thefollowing:

• To perform an online backup using the SAPDBA menu interface or thebrbackup or brarchive command, refer to the appropriate SAPdocumentation.

• To perform an online backup using the RMAN utility, refer to theappropriate Oracle documentation.

The following is a simple example of an online backup using the brbackupcommand:

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,brarchive, and brrestore" on page 109.

With this brbackup command, the selected objects are backed up to theNetWorker 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,brarchive, and brrestore" on page 109.

Note: Archive redo logs are required for an online backup. Without redologs, 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 "BackingUp the Client File Indexes and Bootstrap" on page 49.



3

49

Backing Up the Client File Indexes and BootstrapUnlike scheduled backups, manual backups do not automatically back up theclient file indexes and the NetWorker server’s bootstrap file. If you do notperform regular scheduled backups, you need to protect this vital informationfollowing a manual backup.

Important: The client file indexes and bootstrap record are required forrestoring the data to a database system in the event of a disaster, such as a diskfailure.

To back up the client file indexes and NetWorker server bootstrap file, andapply browse and retention policies to the client file indexes:

1. Include the client in a Group resource, which you must define in both theNetWorker Administrator program and the init<ORACLE_SID>.utl file.(A Group resource can be created even for a single client.) This ensuresthat browse and retention policies are applied to the client file indexeswhen the savegrp command is entered in step 2.

For more information on how to configure a Group resource with theNetWorker Administrator program, refer to the Legato NetWorkerAdministrator’s Guide.

Note: If the client is not included in a Group resource, you must performstep 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 client’s index files and the associated NetWorker

server’s bootstrap without backing up the client’s 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 LegatoNetWorker Command Reference Guide.


3

Reviewing Backup Session Reports

50

3. If the client is not included in a Group resource (see step 1), apply browseand retention policies to the client index files by entering the followingnsrim command:

nsrim -c client_name

where -c client_name specifies the hostname of the SAP R/3 server runningOracle whose index is to be backed up.For more information on the nsrim command, refer to the LegatoNetWorker Command Reference Guide.

Important: Applying browse and retention policies to SAP R/3 backupsavoids the problems of client file indexes using large amounts of hard drivespace and slow index queries.

Reviewing Backup Session ReportsDuring backup, the NetWorker Module appends a backup session report to alog file on each SAP R/3 server running Oracle where the NetWorker Moduleresides. 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 specifiedin the backint_log, arch_backint_log, or backint_tmpdir parameters. Logs canbe made verbose by setting the verbose parameter. See "verbose" on page 41.

Most NetWorker Module logs can be found by searching fornsr/applogs/*backint*, nsr/applogs/*sap*, or nsr/applogs/*SAP*.

The default format for the backup report’s log filename is as follows:

backint<ORACLE_SID>.log

At the end of each operation in the report, there is a statement of the numberof successfully completed files out of the total number of files.



3

51

Table 9 on page 51 lists the attributes recorded in a backup, restore, or inquiresession report.

Table 9. Report Attributes for Backup and Restore Sessions (Part 1 of 2)


#BACKUP <backup_id><file>

Indicates the ID and filename from a successfulinquiry function.

#ERROR <file>or#NOTFOUND <file>

Indicates an unsuccessful backup, restore, orinquire function and the intended file.

#RESTORED <backup_id><file>

Indicates the ID and filename for each successfulrestore function.

#SAVED <backup_id><file>

Indicates the ID and file name for each successfulbackup function.

Files Indicates the number of files to be backed up orrestored in this backup or restore session.

Input File Indicates the name of the input file containing allfiles that backint is requested to back up orrestore. Each requested file is listed under themessage, "Reading input file."

Local Host Indicates the SAP R/3 server running Oracle thatis associated with the report.

n of m files savedn of m files restoredn of m files reported

Indicates the number of files (n) successfullysaved, restored, or reported by the NetWorkerprogram out of the total number of files (m, see"Files" attribute) intended for the backup orrestore operation.

Backups list two records, one for data and one forprofiles.

Number of Symlinks(UNIX only)

Indicates the total number of symbolic linksfound in the files listed in the Input File.


3


52

Parallelism Indicates the parallelism setting that backint useswhen either passing save sets to the NetWorkerserver for backup or receiving save sets forrestore.

Params File Indicates the init<ORACLE_SID>.utl parameterfile that backint uses for backup, restore, orinquiry of the SAP R/3 with Oracle data.

Processing ParameterFile

Indicates the parameter that backint uses duringthe backup, restore, or inquire process. For detailson the NetWorker Module parameters, see"Task 3: Configure the NetWorker ModuleParameters" on page 33.

Savesets/Sessions Indicates the number of save sets that backintsends to the NetWorker server.

Starting Indicates the backup or restore command, whichis followed by a list of the files that were or werenot successfully backed up or recovered in eachsession.

Symlink(UNIX only)

Specifies the location of a symbolic link associatedwith the file backed up or restored. The mostcommon symbolic link is between the /oracle and/mnt/oracle directories. During backup, this link isbacked up so that upon recovery the link isresolved.

User Indicates the database ID (ORACLE_SID)associated with the database instance. BRToolspasses this value to backint.

Table 9. Report Attributes for Backup and Restore Sessions (Part 2 of 2)



Chapter 4: Scheduled Backups

This chapter describes how to configure scheduled backups of SAP R/3servers running Oracle. It includes the following sections, which describetasks 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 SettingsBefore configuring scheduled backups, test the network connections and basicsoftware settings by performing a successful manual SAP R/3 with Oraclebackup.

• For basic settings, see "Chapter 2: Basic Software Configuration" onpage 29.

• For manual backup instructions, see "Chapter 3: Manual Backups" onpage 45.


4

Task 2: Configure the Client Resource

54

Task 2: Configure the Client ResourceUse the NetWorker Administrator program on the NetWorker server toconfigure the Client resource for each SAP R/3 server running Oracle to bescheduled for backup.

• For general Client resource settings for the NetWorker Module, reviewthe listings for "Client" on page 31.

• For Client resource settings that are specific to scheduled backups, seeTable 10 on page 54.

• All other settings for scheduled backups must be specified in theNetWorker Module’s parameter file and the scheduled backupconfiguration 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 Module’s parameter file override anycorresponding settings (including default settings) in the NetWorker Clientresource.

For a complete description of Client resource settings, refer to the LegatoNetWorker Administrators Guide.

Table 10. Client Resource Settings for Scheduled Backups (Part 1 of 2)


Save Set Ensure that the save set name includes the backintcommand and is defined in the following format:

backint:ORACLE_SID

For non-PowerSnap usage, this attribute is onlyinformational, because the nsrsapsv.cfg file determines theORACLE_SID parameter. For PowerSnap usage, thisattribute must be specified.



4

55

Figure 4 on page 56 provides an example showing part of a Client resourceconfiguration in the NetWorker Administrator program on a UNIX system.Note the sample values in the Save Set and Backup Command fields.

BackupCommand

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 scheduledbackup configuration file (for example,/nsr/res/nsrsapsv.cfg). For information on the scheduledbackup configuration file, see "Task 4: Configure theScheduled Backup Configuration File" on page 58.

Note: Because the Backup Command attribute is limited to64 characters, store scheduled backup configuration files inthe following default path:

On Microsoft Windows: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 user’s operatingsystem username.

Password On Windows systems only, enter the password for theRemote User attribute.

Table 10. Client Resource Settings for Scheduled Backups (Part 2 of 2)



4

Task 2: Configure the Client Resource

56

Figure 4. Example Client Resource on UNIX Systems



4

57

Figure 5 on page 57 provides an example of a Client resource configuration inthe NetWorker Administrator program on a Windows operating system. Notethe sample values in the Save Set and Backup Command fields.

Figure 5. Example Client Resource on Windows Systems

Task 3: Encrypt the User Name and PasswordThe SAP user’s operating system username and password and the SAP user’sOracle username and password must be encrypted in the NetWorkerModule’s scheduled backup configuration file, nsrsapsv.cfg (or a copy of thisfile).

Note: Use a copy of the nsrsapsv.cfg file, and preserve the original file.

To encrypt the SAP user’s operating system username and password and theSAP user’s 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 configurationfile (nsrsapsv.cfg or a copy of this file).

2. Follow the prompt instructions.


4

Task 4: Configure the Scheduled Backup Configuration File

58

Task 4: Configure the Scheduled Backup Configuration FileThe NetWorker Module’s scheduled backup configuration file, namednsrsapsv.cfg (included with the installation), is a text file that containsparameters 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 BackupCommand attribute of the Client resource (see "Backup Command" onpage 55).

Uncomment any parameters in the configuration file that you want to use inthe 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 environmentvariables such as $ORACLE_HOME and %ORACLE_HOME% are notsupported.



4

59

Table 11 on page 59 lists the parameters and values for the scheduled backupconfiguration 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 environmentvariable 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 existingvalue for the environment variable.

• If an environment variable with this name does not exist, then itis 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 namedname. 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 instructsbrbackup or brarchive to print out additional trace information.



4


60

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 andpassword of the Oracle database administrator. Instead, the username and password should be encrypted by using the nsrsapadm-c filename command (see "Task 3: Encrypt the User Name andPassword" on page 57).

For example:

BR_EXEC=brbackup

This is a required parameter.

HOMEDRIVE Windows only. This parameter specifies the drive name whereWindows system files reside. You can verify this setting byentering 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 Oracledocumentation.


ORACLE_BIN This parameter specifies the location of the Oracle binaries. Thespecified path is appended to the PATH environment variable sothat all Oracle binaries can be found, if needed.

This parameter is required only if the Oracle binaries are not in thedefault location, $ORACLE_HOME/bin.


Parameter Value



4

61

ORACLE_HOME Set this parameter to the installation path for the Oracle serversoftware 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 theOracle 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 Administrator’s Clientresource for this client.

For example, if the save set name is backint:SAP and you do notspecify 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 user’s encrypted Oracle username and password. The nsrsapadm -c command creates thisparameter (see "Task 3: Encrypt the User Name and Password" onpage 57).

Do not manually add or edit this parameter; use the nsrsapadm -ccommand instead.

OS_USR_PASSWD This parameter contains the SAP user’s operating systemusername and password. The nsrsapadm -c command creates thisparameter (see "Task 3: Encrypt the User Name and Password" onpage 57).

Do not manually add or edit this parameter; use the nsrsapadm -ccommand instead.


Parameter Value


4


62

PATH This parameter is used to add more search paths to the PATHenvironment variable. The specified value is appended to thePATH environment variable. You may specify multiple searchpaths, using either one of the following methods:• PATH=d:\dir1;d:\dir2;d:\dir1\dir2\dir3• PATH=d:\dir1PATH=d:\dir2PATH=d:\dir1\dir2\dir3


SAP_BIN This parameter specifies the path to the location of the BRToolsbinary files. This should also be where the backint (UNIX) orbackint.exe (Windows) executable resides, after it is manuallymoved to this location following installation of the NetWorkerModule. This path is added to the PATH environment variable sothat the BRTools binaries and backint can be found.

For example:

SAP_BIN=/usr/sap/SAP/SYS/exe/run


SAP-specificenvironment variables:SAPARCHSAPREORGSAPTRACESAPCHECK

Windows platforms only. The SAP-specific environment variablesare required for brbackup to run properly on Windows. They arenormally 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 theWindows system or need to be overwritten.


Parameter Value



4

63

Reviewing Backup Session ReportsDuring a backup session, several reports are written to log files on each SAPR/3 server running Oracle where the NetWorker Module resides.

• Each time the nsrsapsv program is called, a log file is created with thename nsrsapsv.<process_id>_<ORACLE_SID>, for example,nsrsapsv.359_CER.

• The backint program saves a backup report in the backint log file. Thedefault log filename is backint <ORACLE_SID>.log.

These log files can be viewed with any text editor. The default location for alllogs 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 specifiedin the backint_log, arch_backint_log, or backint_tmpdir parameters. Forinformation on these parameters, see Table 8 on page 34. Logs can be madeverbose 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.

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. Fordetails, refer to the SAP documentation.


Parameter Value


4


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 individualsave sets or the entire contents of a storage volume. The cloned volumes areindistinguishable from the original, except that the volume labels are different.NetWorker software indexes and tracks clones in both the client file index andthe media database. The NetWorker Module for SAP R/3 with Oracle softwareuses 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 OptionsSave sets generated for the Oracle database ID, ORACLE_SID, using theNetWorker Module can be cloned by running the sapclone command fromeither the NetWorker server or the SAP R/3 server running Oracle. Thesapclone command works with nsrclone to write the cloned data to thedefault 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 ismandatory.

Table 12 on page 66 lists the options to use with the sapclone command.


5

Clone Command Syntax and Options

66

Table 12. The sapclone Options (Part 1 of 2)

Option Description Example

-a Clones all of a client’s save sets. If thisoption is not specified, the NetWorkerModule only clones save sets created inthe last 24 hours.

sapclone -a -u mikeERC

-b pool Specifies the pool to which the clonedsave sets are sent. If this option is notspecified, the save sets are sent to theDefault clone pool.

sapclone -b SAPClone -u mikeERC

-c client Identifies the name of the client whosebacked up data should be cloned.NetWorker software uses the client fileindex for the specified client to find andclone the client’s data.

Use this option for cloning data backedup from a cluster. For example, you maywant to set this option to the name of thecluster’s virtual node.

sapclone -c saturn -u mikeERC

-n Tests the cloning operation on a client’ssave sets. When this option is specified,the cloning operation is not initiated.

The example performs a trial cloningprocess on the save sets created bybackint in the last 24 hours, with none ofthe data being stored onto volumes of aclone pool.

sapclone -n -u mikeERC


Chapter 5: Cloning Save Sets

5

67

Monitoring the Cloning ProcessTo enable monitoring of the cloning process, the NetWorker server displaysmessages in the NetWorker Administrator program for each save set that iscloned. Because the cloning process only clones complete save sets, additionalvolumes are requested if a save set spans multiple volumes.

Messages generated during the cloning process appear on screen and arerecorded 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 errormessages, see "Appendix C: Troubleshooting" on page 123.

-s server Specifies the NetWorker server to whichto clone. You need this option only if oneof 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.

sapclone -s mars -u mikeERC

-u user Mandatory option. Specifies the ID ofthe Oracle database, whose save sets areto be cloned.

sapclone -u mikeERC

Table 12. The sapclone Options (Part 2 of 2)

Option Description Example


5

Monitoring the Cloning Process

68


Chapter 6: Restoring Data

This chapter describes how to restore data that was backed up by theNetWorker 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 LegatoNetWorker Disaster Recovery Guide.

Reviewing Save SetsTo review NetWorker save sets in the NetWorker Administrator program:

• On UNIX, select Indexes from the Client menu to open the Indexeswindow.

• 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.


6

Expiration of Save Sets

70

Expiration of Save Sets

For every client save set backed up, the NetWorker server stores two sets ofrecords:

• One or more records are written to the online client file index for the clientcomputer and its save set. These records are maintained until the browsepolicy for the save set expires.

• One record is written to the online media database for the location of thesave set’s data on a specific storage media. This record is maintained untilthe retention policy for the save set expires.

The expiration for the browse and retention policies must be set in theNetWorker Module’s parameter file. For details, see "Task 3: Configure theNetWorker Module Parameters" on page 33.

Once the browse and retention policies expire, the backup media is eligible forrecycling and can be overwritten. Until the media is actually overwritten(relabeled), the data from the media can be restored by using the scannercommand on the NetWorker server.

For a complete description of how NetWorker software uses browse andretention policies to track data, refer to the Legato NetWorker Administrator’sGuide.

Performing RestoresIf a SAP R/3 server running Oracle was backed up by using the NetWorkerModule software, then you can restore data to the server by using either theSAPDBA interface or the brrestore command directly. If a backup was donewith RMAN, then the restore should also be done with RMAN. Forinformation on restoring with RMAN, refer to the appropriate Oracledocumentation.

• 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 controlfiles.

Note: Restore options used with either SAPDBA or the brrestore commandoverwrite 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.



6

71

Important: The brrestore program, whether invoked directly from thecommand line or from the SAPDBA interface, first deletes all the original filesto be restored before calling backint to restore the files. If brrestore is unableto invoke backint for any reason, the original files are lost. Perform an inquiryof the backup first, before performing a restore.

An alternative is to restore the files to another location, and preserve theoriginal files. Use the -m parameter, and specify the restore destination, asfollows:

brrestore -m tablespace_name=restore_directory

For more information on restoring to a different location, refer to theappropriate SAP documentation.

How to Restore a Database or Database Object

To restore an entire database instance or a single database object using eitherthe SAPDBA interface or the brrestore command:

1. Ensure that the NetWorker server, the SAP R/3 server running Oracle, andthe NetWorker Remote Exec services are running.

2. Shut down the Oracle database instance (for a full restore), or take thedatabase objects you are restoring offline (for restore of a single databaseobject).

3. Ensure that either utl_file or rman_utl is configured as the backup devicetype 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 parallelismsettings are configured in the NetWorker Module’sinit<ORACLE_SID>.utl file. For details, see "Task 3: Configure theNetWorker Module Parameters" on page 33.

5. Ensure that the backup you want to restore exists using either SAPDBA orthe brrestore inquire function as follows:

brrestore -verify


6

Restoring SAP R/3 with Oracle Cluster Data

72

6. Depending on the type of restore you are performing and your restoremethod, 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 DataRestoring data backed up from private disks in a cluster node is similar torestoring data on a system that is not part of a cluster.

To restore data from a shared disk of a virtual client, set the NetWorkerModule’s client parameter to restore files to the virtual client, where the filesoriginated during the backup. For more information on this parameter, see"client" on page 35.

Reviewing Restore Session ReportsDuring restore, the NetWorker Module appends a restore session report to alog file on each SAP R/3 server running Oracle where the NetWorker Moduleresides. This file can be viewed with any text editor.

The default location for all logs is:





6

73

The default format for the restore report’s log filename is as follows:

backint <ORACLE_SID>.log

Logs can be written to a different location using different names, as specifiedin the backint_log, arch_backint_log, or backint_tmpdir parameters. Forinformation on these parameters, see Table 8 on page 34.

For a list of restore session report attributes, see Table 9 on page 51.


6

Reviewing Restore Session Reports

74


Chapter 7: PowerSnap Backups and Restores

This chapter describes how to configure and run PowerSnap backups andrestores 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


7

Requirements

76

RequirementsThis section describes the types of environments and software required to usethe PowerSnap features of the NetWorker Module for SAP R/3 with Oraclesoftware.

Supported Environments

PowerSnap provides continuous point-in-time (PIT), snapshot-based(immediate live backup) protection and availability of SAP R/3 with Oracle dataon supported primary storage platforms.

To use the PowerSnap features, the NetWorker Module must be used inconjunction with the Legato NetWorker PowerSnap Module. The PowerSnapModule creates the snapshots, and the NetWorker Module stores the snapshotdata.

PowerSnap backups must use servers, clients, or storage nodes on supportedplatforms only. The supported types of primary storage platforms include, butare 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 NetWorkerModule for SAP R/3 with Oracle Release Supplement.

The Oracle control file and all SAP directories, except sapdata<n>, should notbe located on a snap volume. For some snapshot platforms, such as STK DSeries or IBM FAStT, this is mandatory. Refer to your snapshot vendor andcorresponding 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 requirethe following software components:

• SAP R/3 with Oracle server, which contains BRTools• BRTools or SAPDBA (on the Oracle server)• NetWorker server



7

77

• NetWorker client (installed on the SAP R/3 with Oracle server and thePowerSnap client host)

• NetWorker Module for SAP R/3 with Oracle software (installed on theSAP R/3 with Oracle server)

• NetWorker PowerSnap Module appropriate for your system (installed onthe SAP R/3 with Oracle server and PowerSnap client host and any datamover host)

Note: Any PowerSnap client host or data mover host that manages thesecondary storage should have NetWorker storage node softwareinstalled.

For details on the installation requirements, refer to the following:

• Legato NetWorker Module for SAP R/3 with Oracle, Release 3.0, UNIX, Linux,and Microsoft Windows Version, Installation Guide.

• NetWorker PowerSnap Module Installation and Administrator’s Guide for theprimary storage system.

Types of PowerSnap BackupsThis NetWorker Module, in conjunction with the appropriate PowerSnapModule, supports the types of PowerSnap for SAP R/3 with Oracle backupssummarized in Table 13 on page 77:

The PowerSnap backup type is configured by the Snapshot Policy attribute inthe NetWorker Backup Group, see "Configuring the NetWorker GroupResource" on page 87.

Table 13. Summary of Supported PowerSnap Backup Types

Backup TypeSnapshotRetention

Location of StoredData

"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 Permanent Both snapshot andsecondary storage


7

Instant Backup

78

Instant Backup

An instant backup creates a permanent point-in-time (PIT) copy, or snapshot, ofSAP R/3 with Oracle data. This copy is then stored on the primary storagesystem where it is available to the NetWorker Module for performing instantrestores or rollbacks. Instant backups can be scheduled to occur many times ina 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 asnap set. The snapshot policy must be configured to control the lifecycle of thesnap set. This policy specifies the frequency of instant backups and how longsnapshots 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 protectagainst physical media failures, the snapshot must be backed up to secondarystorage, such as tape.

For functional details of an instant backup, see "Instant Backup Processes" onpage 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 Modulesupports two types of live backup: immediate live backup, and deferred livebackup.

Immediate Live Backup

Immediate live backup (also known as "serverless snapshot backup" or"snapshot-based backup") is a process by which a temporary snapshot iscreated, and immediately backed up to secondary storage such as tape. Thesnapshot is then automatically deleted from the primary storage (and notavailable to the NetWorker Module for performing instant restores orrollbacks).



7

79

Deferred Live Backup

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

• Snapshot expiration policy• Retain SnapShots attribute of the SnapShot Policy for the client’s Group

resource.

The Group Snapshot Policy must be configured to enable live backups. Formore information, see "Configuring the NetWorker Snapshot Policy Resource"on page 87.

Note: A PowerSnap client host that is separate from the Oracle Server host canbe used to move the snapshot to the conventional storage medium such astape. The use of a PowerSnap client as a secondary host reduces the demandon 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 RestoresThis NetWorker Module, in conjunction with the appropriate PowerSnapModule, supports the types of PowerSnap for SAP R/3 with Oracle restoresdescribed 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, entirelyrestored to source location

"Restore from Secondary Storage" seepage 80

Secondary storage (no snapshotavailable)


7

Instant Restore

80

The restore type is specified in the RESTORE_TYPE_ORDER variable in theuser-defined PowerSnap configuration file. See "Setting Variables in thePowerSnap Configuration File" on page 93.

Instant Restore

An instant restore is the process by which a snapshot that was created by aninstant backup is mounted. This enables its saved data to be retrieved. Aminimal amount of time is required for this type of restore.

For functional details of instant restores, see "Instant Restore and RollbackProcesses" on page 105.

Rollback

A rollback restores the entire snapshot to the source location by using thehardware’s particular capabilities. Relocation during rollbacks is not currentlysupported by PowerSnap. To determine if a rollback is supported on a specifictype of hardware, refer to the appropriate NetWorker PowerSnap ModuleInstallation and Administrator’s Guide.

Important: Rollbacks are potentially destructive because they overwrite theentire 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 wassaved to the secondary storage system is restored from the secondary storage.The PowerSnap Module software essentially uses the NetWorker recoverprogram, to retrieve the data.

For functional details on restores from secondary storage, see "Restore fromSecondary Storage Processes" on page 107.



7

81

PowerSnap Backup and Restore Data FlowsThe backup and restore strategy requires knowledge of how the Oracle andLegato software components all work together, see "Required SoftwareComponents" on page 76.

During a PowerSnap backup of SAP R/3 with Oracle data, the SAP R/3 withOracle Server processes interact indirectly with the NetWorker server throughthe 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 apoint-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/3with Oracle data from the snapshot on the primary storage to theNetWorker server or storage node.

4. The NetWorker server or storage node then stores the Oracle data on thesecondary storage, such as a tape.

5. At the end of the PowerSnap backup, the NetWorker server updates theonline client and media indexes with information about the backup.

For more information about NetWorker server and NetWorker clientprograms and services, refer to the Legato NetWorker Administrator’s Guide.

Data flow and intraprocess communication for SAP R/3 with OraclePowerSnap 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


7

PowerSnap Backup and Restore Data Flows

82

Figure 6. NetWorker Module PowerSnap Backup and Restore Data Flow

NetWorkerClient

SAP R/3 withOracle Server Host

PowerSnap Client(NetWorker Storage Node)

NetWorkerServer

NetWorkerClient

PowerSnapModule

StorageMedium

SAP R/3 withOracle Datafiles

Point-in-Time Copyof SAP R/3 withOracle Datafiles

PowerSnapModule

NetWorkerServer

Primary Storage

NetWorkerModule

for SAP R/3with Oracle

BRTools/SAP R/3

with Oracle process

data



7

83

Quick StartThe following steps describe typical settings to enable and use the NetWorkerModule’s PowerSnap features for backup and restore. To customize yourconfiguration, use this information in conjunction with more specializedinformation described in "PowerSnap Software Configuration Roadmap" onpage 86.

Note: Before running the test included in this procedure, back up the testdatabase. 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 Modulebelongs has the proper PowerSnap attribute settings, as listed in Table 15on page 83.

Table 15. Backup Group’s 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 snapshotoperation metadata is recommended. File type volumedevices are strongly recommended over tape.

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

Interval Must be set in relation to the Number of Snapshotsattribute for the snapshot policy.


7

Quick Start

84

2. Modify the NetWorker Module’s init<ORACLE_SID>.utl file to enable thePowerSnap parameters and variables.

A typical and recommended configuration is as follows:ps_backup_mode = yesps_archive_mode = nops_restore_mode = yesps_inquire_mode = yesps_exclude_backup_bi_run_nums = 2ps_exclude_archive_bi_run_nums = 1;2ps_exclude_backup_paths = (leave blank)ps_exclude_archive_paths = (leave blank)ps_ps_before_nonps = yesps_group_objs = yesps_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 appropriatefilepath 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 installedPowerSnap Module, for example:NSR_SNAP_TYPE = suniiNSR_PS_DEBUG_LEVEL = 9NSR_VERBOSE = true

Debug level is intended for technical support diagnostics only. For moreinformation on the nmsapps.cfg file’s contents, refer to the NetWorkerPowerSnap Module Installation and Administrator’s Guide.

4. Test the client’s group snapshot settings by invoking the savegrpcommand.

a. From the NetWorker server nwadmin program, open the Groupresource.

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



7

85

The backup test is successful if the backint log reports the followingmessage: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 Module’s backintlog 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 filefrom PowerSnap processing.

• The ps_opaque_pfilename file needs to be modified.For further troubleshooting, enable the following parameters in theinit<ORACLE_SID>.utl file to generate diagnostic logs for TechnicalSupport:debug_level = 9nsr_debug_msg = yesverbose = yes

• To obtain PowerSnap logs, also specify the following in theps_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 followingmessage:n of n PS files reported

where n is the number of files requested that reside on a PowerSnap disk.


7

PowerSnap Software Configuration Roadmap

86

PowerSnap Software Configuration RoadmapBefore you configure the PowerSnap features, ensure that both the NetWorkerModule for SAP R/3 with Oracle and the required PowerSnap Modulesoftware are installed according to the instructions in the followingdocumentation:

• Legato NetWorker Module for SAP R/3 with Oracle Installation Guide

• NetWorker PowerSnap Module Installation and Administrator’s Guide(Refer to the PowerSnap Module version for the primary storage system.)

To configure the PowerSnap features, complete the following sets ofprocedures:

1. Use the instructions in "Chapter 2: Basic Software Configuration" toconfigure the NetWorker Server, Client, Device, and other resources.

2. For live SAP R/3 with Oracle backups, configure a Device resource foreach 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 thedatafiles on the primary storage supported by the specific PowerSnapModule.

4. Use the instructions in "Chapter 4: Scheduled Backups" to configure thebasic scheduled backup.

5. Complete the procedure: "Configuring NetWorker Resources forPowerSnap" on page 87.

6. Complete the procedure: "Setting the PowerSnap Parameters" on page 89.

7. Complete the procedure: "Setting Variables in the PowerSnapConfiguration File" on page 93.



7

87

Configuring NetWorker Resources for PowerSnapConfigure 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 withOracle backups. The PowerSnap Module stores the metadata from thesnapshot in this pool. Use the same configuration method as for a regularNetWorker Module for SAP R/3 with Oracle backup. However, the specifiedbackup device should be a file or advanced file type.

Specify the pool name in the Snapshot Pool attribute of the NetWorker Groupresource as described in "Configuring the NetWorker Group Resource" onpage 87.

For more information on configuring this extra pool, refer to the appropriateNetWorker PowerSnap Module Installation and Administrator’s Guide.

Configuring the NetWorker Snapshot Policy Resource

A NetWorker snapshot policy must be configured to perform either instant orlive PowerSnap for SAP R/3 with Oracle backups. You can either specify apreconfigured policy, or create a new one.

Configure a NetWorker Snapshot Policy resource by using the instructions inthe appropriate NetWorker PowerSnap Module Installation and Administrator’sGuide.

Configuring the NetWorker Group Resource

For PowerSnap for SAP R/3 with Oracle backups, configure a NetWorkerGroup resource by using the instructions in the appropriate NetWorkerPowerSnap Module Installation and Administrator’s Guide.


7

Configuring the NetWorker Client Resource

88

Configuring the NetWorker Client Resource

The basic NetWorker Client resource for the NetWorker Module for SAP R/3with 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 Settingsprivilege can set the Remote Access attribute in the Client resource.

The Browse Policy attribute in the Client resource, which is superseded by theinit<ORACLE_SID>.utl expiration parameter, applies only to the NetWorkerclient 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 bythe init<ORACLE_SID>.utl expiration parameter, applies only to theNetWorker 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 policyspecified in the client’s Group resource.



7

89

Setting the PowerSnap ParametersPowerSnap parameters are set in the NetWorker Module for SAP R/3 withOracle init<ORACLE_SID>.utl file. These settings assume that the PowerSnapModule is installed and licensed.

Descriptions of the PowerSnap parameters for the NetWorker Module for SAPR/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 ParameterDefaultValue Description

ps_backup_mode No Each of these PowerSnap functional modes isenabled if set to Yes.

Normally, all the modes are set together toeither all Yes or all No, exceptps_archive_mode=no and all others =yes. Donot use any other settings except for diagnosticpurposes.

PowerSnap save sets are named using thefollowing format: backint:<SID>:PS:.

ps_archive_mode

ps_restore_mode

ps_inquire_mode

ps_opaque_pfilename Null Absolute pathname of a backint parameter filethat passes values to the PowerSnap module.For details, refer to the appropriate PowerSnapmodule documentation. This setting ismandatory if the PowerSnap functional modeparameters are enabled.

PowerSnap parameters are specified in thisparameter file in "x = y" lines, for example:

NSR_SNAP_TYPE = sunii


7

Setting the PowerSnap Parameters

90

ps_exclude_backup_bi_run_nums Null Specifies which backint runs are to be excludedfrom PowerSnap processing (typically runnumber 2). Parameter files, SAP backup catalogfiles, and other files that do not benefit fromPowerSnap processing can be backed up byconventional processing without PowerSnap,thereby saving valuable snapshot diskresources.

Specify a value of one or more valid backintrun numbers to exclude, each separated by asemicolon (;).

Important! The following starting values arestrongly recommended:ps_exclude_backup_bi_run_nums=2ps_exclude_archive_bi_run_nums=1;2

Each brbackup or brarchive session invokesmultiple backint processes sequentially, forexample run number 1 followed by run number2. If run 2 is excluded, then run 1 backs up thedatabase datafiles exclusively by usingPowerSnap, and run 2 forces files that do notbenefit from PowerSnap processing, to bebacked up by conventional processing withoutPowerSnap.

ps_exclude_archive_bi_run_nums





7

91

ps_exclude_backup_paths Null Specifies individual PowerSnap files to excludefrom PowerSnap processing, but to back upwith conventional non-snapshot processinginstead. PowerSnap files are those on asnapshot-capable file system that NetWorker isaware of.

Valid values are any full path string, includingstandard wildcard characters. Use values thatare based on the actual filenames that BRToolspasses to backint.

Note:• On Windows systems, support of wildcard

characters is limited, and a single trailing *denotes simple case-insensitive prefixmatching. Thus X:\DB01\FOO.DBF will beexcluded from PowerSnap backups if theparameter is set to a value of:X:\*, or X:\db*, or X:\DB01\*

• On UNIX systems, wildcard support followsstandard shell support for full file pathnames.For example the file /db01/foo.dbf is excluded ifthe 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, eachseparated by a semicolon (;).

Whenever possible, preference should be givento setting the ps_exclude_xxx_bi_run_numsparameters instead of using these parameters.

ps_exclude_archive_paths




7

Setting the PowerSnap Parameters

92

ps_ps_before_nonps Yes Specifies whether to perform all PowerSnapprocessing before conventional processingwithout PowerSnap. This helps preventpotential resource conflicts.

Setting this value to No enables concurrentprocessing of all files set for backup, archive, orrestore.

Note: The No value is not recommended and isdone at the user’s own discretion.

ps_group_objs Yes Specifies whether to group all session files foreach PowerSnap operation, such as prepare orsync, snapshot or split, save or restore, orpostpare.

Setting this value to Yes improves theNetWorker Module performance for certaindatabase disk or filesystem configurations,particularly if large numbers of files areprocessed by BRTools and PowerSnap withutil_file_online.

However, grouping files also reduces thepotential parallelism for certain backup andrestore suboperations, which in turn can reduceperformance.

Setting this value to Yes is also intended for usewith BRTools 6.10 and later, offline andutil_file_online, for example:

brbackup -t offline -d util_file_online





7

93

Setting Variables in the PowerSnap Configuration FileThe PowerSnap parameters that do not directly belong to the NetWorkerModule for SAP R/3 with Oracle program must be set as variables in auser-defined PowerSnap configuration file, for example: nmsapps.cfg. This filemust be specified by its complete file pathname in the ps_opaque_pfilenameparameter in the init<ORACLE_SID>.utl file.

The configuration file must list a separate line for each variable setting byusing 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 onpage 93. For a complete list, refer to the appropriate NetWorker PowerSnapModule Installation and Administrator’s Guide.

PowerSnap variables that have settings equivalent to NetWorker Moduleparameters 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 PowerSnapbackup uses a live backup hostdifferent from the PowerSnapclient host (NSR_CLIENT).Specifies the hostname of thePowerSnap backup host.

• Local host (default).• The valid hostname of the

secondary live backup host.

Note: The NSR_CLIENTPowerSnap variable must alwaysbe set to the original brbackup orbrarchive host,init<ORACLE_SID>.utl clientvalue.

NSR_MAX_STREAMS Optional. Specifies themaximum number of restorestreams.

• Defaults to the parallelismvalue set in theinit<ORACLE_SID>.utl file, orits default value of 8.

• An integer value.

NSR_PS_DEBUG_LEVEL Optional. PowerSnap debuglevel.

Valid values are 0 to 9. Defaultvalue is 1.


7

Setting Variables in the PowerSnap Configuration File

94

NSR_PS_SAVE_PARALLELISM

Optional. Specifies themaximum number ofconcurrent save streams on thePowerSnap client host.

• Defaults to the parallelismvalue set in theinit<ORACLE_SID>.utl file, orits default value of 8.

• An integer value.

NSR_SNAP_TYPE Optional. Specifies snapshotplatforms and releases, whenmultiple snapshot platformsare used.

Value should be a concatenatedstring, delimited by a colon (:), forexample:Emctimefinder 4.5.6:EmcClarion1.2.3:LSIMetaStor 3.4.5

RESTORE_TYPE_ORDER Optional. Specifies the type ofrestore to be performed.

Note: If multiple values arespecified, each type of restoreis attempted, in the orderspecified, until a restoreoperation is successful.

One or more of the followingvalues, with each value delimitedfrom the others by a colon(:):• pit - Specifies an instant

(point-in-time) restore.• conventional - Specifies a

restore from secondary storagemedia.

• rollback - Specifies a rollbackrestore from a PIT copy.

The default value ispit:conventional

Note: For the NetWorker Module,a rollback operation aborts if oneof the following occurs:• If brrestore file relocation is

specified.• If nonrequested files exist in the

brrestore-requested filesystems.(These files could becomecorrupted after a rollback.)

Table 17. Commonly-Used PowerSnap Module Environment Variables (Part 2 of 2)

PowerSnap Variables Description Default and Valid Values



7

95

PowerSnap Use of Equivalent NetWorker Module Parameters

Some parameters used by PowerSnap are the same as those used inconventional backup and restore operations and are inherited from theinit<ORACLE_SID>.utl file. Normally, these equivalent parameters should notbe specified as variables in the PowerSnap configuration file. See Table 18 onpage 95.

Table 18. PowerSnap Use of Equivalent NetWorker Module Parameters

PowerSnap variables in theps_opaque_pfilename parameter

Equivalent parameter in theinit<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


7

Invoking PowerSnap Backup Processes

96

Invoking PowerSnap Backup ProcessesA PowerSnap for SAP R/3 with Oracle backup is started by automatically ormanually invoking the scheduled NetWorker backup group on the NetWorkerserver. For information on how to invoke a scheduled backup, refer to theNetWorker PowerSnap Module Installation and Administrator’s Guide.

Note: A PowerSnap backup should not be started by directly invoking theclient-side BRTools commands or SAPDBA.

There are three types of scheduled PowerSnap backup processes, which aresummarized 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 Oracledata that is retained on the primary storage system, where it is available to theNetWorker Module for performing instant restores or rollbacks. An instantbackup is performed as follows:

1. At the backup start time, the main NetWorker service, nsrd, invokes thesavegrp program to start the group’s 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 programto validate the client.

3. If the savefs program succeeds, the savegrp program starts thePowerSnap 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 berecycled according to the snapshot policy), the nsrsnap program invokesthe nsrsnapck program, which removes both the snapshot from thestorage system and the corresponding NetWorker file and media indexentries. File and media index entries are removed only if the snapshot wasnot backed up to tape.

Note: If the existing snapshot was not backed up to tape, there will beinvalid records in the BRTools sapbackup catalog that do not correspondto any file index entries for the snapshots, because they were deleted bynsrsnapck processing. A subsequent brrestore attempt, without prior



7

97

verification, results in an expected "#NOT FOUND" message for allrequested files. Run the brrestore -verify command before runningSnapshot Policies that do not back up to tape.

This message does not appear if you run brrestore for either of thefollowing:• 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 thensrsapsv program for the scheduled backup.

6. The nsrsapsv program sets the required environment variables andinvokes the brbackup or brarchive program.

7. The brbackup or brarchive program starts the NetWorker Module’sbackint program for the SAP R/3 with Oracle backup.

8. The backint program contacts the PowerSnap master program, nsrpsd, toperform 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 thesnapshot pool, typically on a file or disk type device.

• The nsrmmd service records tracking information about thepoint-in-time metadata in the NetWorker media database by usingthe nsrmmdbd service.

• The nsrindexd service records tracking information about each filename in the NetWorker client file index. The client index contains oneentry per datafile.

• BRTools records the backup entry in its sapbackup catalog.

9. The brbackup or brarchive program calls the NetWorker Module asecond time to invoke backup processes for non-datafiles, for exampleinit<ORACLE_SID>.sap, that do not benefit from PowerSnap processing.This extra backup is configured to be a conventional backup withoutPowerSnap by the following setting in the init<ORACLE_SID>.utlparameter file:

ps_exclude_xxx_bi_run_nums = 2

where xxx is backup or archive. For configuration details, see Table 16 onpage 89.


7

Instant Backup Processes

98

10. If the Snapshot Policy resource specifies that the snapshot must be copiedto 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 SAPR/3 with Oracle client file indexes.

Figure 7 on page 98 shows how the Oracle Server and NetWorker processesinteract during a scheduled instant backup.

Figure 7. Scheduled Instant Backup Processes

SAP R/3 withOracle Server

(NetWorker Client)PowerSnap Client

(NetWorker Storage Node)NetWorker

Server

SnapshotPool Media

nsrmmdbd

Media Database

Client File Index

interprocess communication

backint

nsrindexd

nsrexecd nsrmmd

trackinginformation

brbackupor brarchive

savegrp

nsrsnap nsrd

Primary StorageSAP R/3

with OracleDatafiles


data

PowerSnapprocesses

PowerSnapprocesses

nsrpsd

nsrexecdnsrsnapck

savefs

nsrsapsv

green fillindicates

NetWorkerModule

elements

violet fillindicates

PowerSnapelements

white fillindicates

NetWorkerand Oracleelements

StartHere



7

99

Immediate Live Backup Processes

An immediate live backup creates a temporary snapshot copy of the SAP R/3with Oracle data on the primary storage, which is then immediately backed upto secondary storage, such as tape. The snapshot is then automatically deletedfrom 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 thesavegrp program to start the group’s 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 programto validate the client.

3. If the savefs program succeeds, the savegrp program starts thePowerSnap 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 berecycled according to the snapshot policy), the nsrsnap program invokesthe nsrsnapck program, which removes both the snapshot from thestorage system and the corresponding NetWorker file and media indexentries. File and media index entries are removed only if the snapshot wasnot backed up to tape.

Note: If the existing snapshot was not backed up to tape, there will beinvalid records in the BRTools sapbackup catalog that do not correspondto any file index entries for the snapshots, because they were deleted bynsrsnapck processing. A subsequent brrestore attempt, without priorverification, results in an expected "#NOT FOUND" message for allrequested files. Run the brrestore -verify command before runningSnapshot Policies that do not back up to tape.

This message does not appear if you run brrestore for either of thefollowing:• 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 thensrsapsv program for the scheduled backup.

6. The nsrsapsv program sets the required environment variables andinvokes the brbackup or brarchive program.


7

Immediate Live Backup Processes

100

7. The brbackup or brarchive program starts the NetWorker Module’sbackint program for the SAP R/3 with Oracle backup.

8. The backint program contacts the PowerSnap master program, nsrpsd, toperform the immediate live backup.

• PowerSnap processes create the snapshot, move the data tosecondary storage, and then delete the snapshot from the primarystorage.

• The nsrmmd service records tracking information about thesecondary storage save sets in the NetWorker media database byusing the nsrmmdbd service.

• The nsrindexd service records tracking information for each backuppiece name and for each stored operating system datafile in theNetWorker client file index. The client index contains two entries perdatafile.

• BRTools records the backup entry in its sapbackup catalog.

9. The brbackup or brarchive program calls the NetWorker Module a secondtime to back up backup processes for non-data files, for exampleinit<ORACLE_SID>.sap, that do not benefit from PowerSnap processing.This extra backup is configured to be a conventional backup withoutPowerSnap by the following setting in the init<ORACLE_SID>.utlparameter file:

ps_exclude_xxx_bi_run_nums = 2

where xxx is backup or archive. For configuration details, see Table 16 onpage 89.

10. The savegrp program backs up the NetWorker server bootstrap andOracle client file indexes.

Figure 8 on page 101 shows how the Oracle server and NetWorker processesinteract during a scheduled immediate live backup.



7

101

Figure 8. Scheduled Immediate Live Backup




Server

SecondaryStorage Meduim

nsrmmdbd

Media Database

Client File Index


backint

nsrindexd

nsrexecd nsrmmd

trackinginformation

brbackupor brarchive

savegrp

nsrsnap nsrd




data

PowerSnapprocesses

PowerSnapprocesses

nsrpsd

nsrexecdnsrsnapck

savefs

nsrsapsv

green fillindicates

NetWorkerModule

elements


PowerSnapelements

white fillindicates


StartHere


7

Deferred Live Backup Processes

102

Deferred Live Backup Processes

A deferred live backup creates a permanent snapshot copy of the SAP R/3 withOracle data on the primary storage system, which is then backed up tosecondary storage system, such as tape. The snapshot is retained on theprimary storage for the period specified by either of these snapshot policyattributes for the client’s 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 thepreferred method. For more information, refer to the appropriate NetWorkerPowerSnap Module Installation and Administrator’s Guide.

A scheduled deferred live backup uses the following process:

1. The nsrsnap or nsrsnapadmin program invokes the PowerSnap processesto 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 livebackup in the NetWorker media database by using the nsrmmdbd service.

3. The nsrindexd service records tracking information for each storedoperating system datafile in the NetWorker client file index.

Figure 9 on page 103 shows how the Oracle Server and NetWorker processesinteract during a scheduled deferred live backup.



7

103

Figure 9. Scheduled Deferred Live Backup




Server

SecondaryStorage Meduim

nsrmmdbd

Media Database

Client File Index

interprocesscommunication

nsrindexd

nsrexecd nsrmmd

trackinginformation




datansrsnap (at endof savegrp) ornsrsnapadmin

PowerSnapprocesses


PowerSnapelements

white fillindicates

NetWorkerelements

StartHere


7

Querying PowerSnap Backup Records

104

Querying PowerSnap Backup RecordsThe NetWorker server records information about each backup in its onlineindexes. The index entry for a NetWorker Module for SAP R/3 with OraclePowerSnap backup is stored in the NetWorker client file index for the SAP R/3with Oracle Server host, under the new "saporacle" namespace (instead of the"backup" namespace, which is used for regular NetWorker Module for SAPR/3 with Oracle backups).

For NetWorker release 7.1 or later, you can query the online NetWorkerindexes 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:] -sNetWorker_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 thefollowing save set format:

backint:<ORACLE_SID>:PS:

Note: The mminfo command does not display BRTools BIDs or save times forfiles that were backed up with the PowerSnap Module.

For more information on these NetWorker commands, refer to the NetWorkerCommand Reference Guide and the UNIX man pages.



7

105

Invoking PowerSnap Restore ProcessesNetWorker Module for SAP R/3 with Oracle restores are performed witheither the brrestore command or the SAPDBA interface, each of whichultimately calls the NetWorker Module’s backint program. For PowerSnaprestores, the backint program interacts with both the PowerSnap andNetWorker 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 aninstant backup or as part of a deferred live backup.

• For an instant restore, the snapshot copy is mounted and the files arecopied as needed.

• For a rollback, the entire snapshot is moved to the source destination byusing the appropriate commands for the specific platform.

Instant restores and rollbacks use the following process:

1. The NetWorker Module’s backint program verifies the existence of therequested files’ versions through the nsrindexd service.

2. The backint program contacts the PowerSnap master program, nsrpsd, onthe Oracle Server host.

3. The nsrpsd program works with other PowerSnap and NetWorkerprograms to access the instant backup copy on the primary storage orretrieve the data from secondary storage, and perform the restoreoperation.

• PowerSnap processes retrieve the snapshot metadata stored on thedevice associated with the snapshot pool by using the nsrmmd andnsrmmdbd processes.

• PowerSnap processes do one of the following, depending on theRESTORE_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 sourcedestination.


7

Instant Restore and Rollback Processes

106

Once the required SAP R/3 with Oracle files are restored, a databaseadministrator can complete the standard SAP R/3 with Oracle databaserecovery.

Figure 10 on page 106 shows how the Oracle server and NetWorker processesinteract during an instant restore or rollback.

Figure 10. Instant Restore or Rollback




Server

SnapShotPool Media

nsrmmdbd

Media Database

Client File Index


nsrindexd

nsrmmd

trackinginformation

nsrd



Point-in-Time Copy of SAP R/3 with Oracle

Datafiles

data (for details ondata flow, seedescription)

PowerSnapmodule

nsrpsd

nsrexecd

green fillindicates

NetWorkerModule elements


PowerSnapelements

white fillindicates


PowerSnapmodule

nsrexecd

backint

brrestore/brrecover

StartHere



7

107

Restore from Secondary Storage Processes

A restore of a PowerSnap backup from secondary storage uses the followingprocess:

1. The NetWorker Module’s backint program verifies the existence of therequested files’ versions through the nsrindexd service.

2. The backint program contacts the PowerSnap master program, nsrpsd, onthe Oracle Server host.

3. The nsrpsd program works with other PowerSnap and NetWorkerprograms to retrieve the data from secondary storage, and perform therestore operation.

PowerSnap processes restore the files (save sets) into a destinationrequested by the NetWorker Module. The processes use the nsrmmd andnsrmmdbd 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 backupvolumes, a database administrator can complete the standard SAP R/3with Oracle database recovery.

Figure 11 on page 108 shows how the Oracle Server and NetWorker processesinteract during a restore from secondary storage.


7

Restore from Secondary Storage Processes

108

Figure 11. Restore from Secondary Storage




ServerPrimary Storage

OracleDatafiles

SecondaryStorage nsrmmdbd

Media Database

Client File Index


backint

nsrindexd

nsrmmd

trackinginformation

nsrd

data

nsrpsd

nsrexecd

green fillindicates

NetWorkerModule

elements


PowerSnapelements

white fillindicates


brrestore/brrecover

PowerSnapmodule

StartHere


Appendix A: Commonly Used CommandOptions for brbackup, brarchive, and brrestore

This appendix provides sample syntax and options for the SAP R/3 Release4.6B brbackup, brarchive, and brrestore commands, which are commonlyused for NetWorker Module operations. For a complete listing of the syntaxand 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" onpage 110

• "Syntax and Options for brrestore Command" on page 113


A

Syntax and Options for brbackup and brarchive Commands

110

Syntax and Options for brbackup and brarchive CommandsThe NetWorker Module uses the following brbackup command syntax andoptions:

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 commandoptions 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 andbrarchive commands.

Table 19. The brbackup and brarchive Command Options (Part 1 of 3)

Option Description

-c force Suppresses most of the confirmation messages thatinterrupt the backup process.

-d util_file | util_file_online Specifies that the NetWorker Module is used forthe backup or archive process. This option is notrequired because it is set during configuration (see"Task 4: Configure the Backup and Restore Utility"on page 42.)

-f stop Instructs brarchive to wait for the next offline redolog file written by Oracle, and then send it tobackint 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

A

111

-m file_ID Sends a datafile with an associated Oracle file ID tobackint for backup. The following file ID formatsare 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 numberassociated 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 IDrange to backint for backup.

-m delay_time Specifies the delay time between Oracle creatingthe offline redo log file and sending datafiles to thedatabase in standby mode.

-p profile Specifies a profile other than the default,init<ORACLE_SID>.sap. The nondefault profileused for BRTools must specify the settings outlinedin "Task 4: Configure the Backup and RestoreUtility" on page 42.

-r parameter_file Specifies the parameter file that the NetWorkerModule uses during the backup or archive process.This option is required only if you have createdadditional parameter files. Otherwise, this optionis not required, because init<ORACLE_SID>.utl isset as the default parameter file duringconfiguration. For details on setting the defaultparameters, see "Task 3: Configure the NetWorkerModule Parameters" on page 33.

-s saveset Specifies the number of members in save sets (1, 2,3, 4, tablespace, or all).


Option Description


A

Syntax and Options for brbackup and brarchive Commands

112

-t online Instructs brbackup and the NetWorker Module toperform an online backup of the Oracle database.To reduce the number of redo logs that Oraclegenerates, use this option with the -d util_file_onlineoption.

-t offline Specifies to brbackup and the NetWorker Modulethat the Oracle database is shut down.

-t offline_force Instructs the SAP R/3 system to shut down theOracle database immediately and tell brbackup tosend data to backint for backup.

-t offline_standby Instructs the SAP R/3 system that the database instandby mode is ready for backup.

-u user/password Specifies the Oracle database administrator’s username and password.


Option Description


Appendix A: Commonly Used Command Options for brbackup, brarchive, and brrestore

A

113

Syntax and Options for brrestore CommandThe 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 commandoptions 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 thatinterrupt the restore process.

-d util_file | util_file_online Specifies that the NetWorker Module is used forthe restore process. This option is not requiredbecause it is set during configuration (see "Task 4:Configure the Backup and Restore Utility" onpage 42).

-d util_file_online

-m all Requests the backint program to restore alltablespaces and associated files.

-m full Requests the backint program to restore the entiredatabase instance.

-m table_space_name Requests the backint program to restore a singletablespace.


A

Syntax and Options for brrestore Command

114

-m file_ID Requests the backint program to restore a datafilewith an associated Oracle file ID. The following fileID 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 numberassociated with the redo log files.

• Specify all online redo log files as ID 00.

-m file_ID_range Requests the backint program to restore datafileswithin a specified Oracle file ID range.

-m generic_path Requests the backint program to restore all thedatafiles whose names start with that full path. Thepath must contain at least the SAPDATA_HOMEdirectory and an additional generic specification(for example, sapdata<n> ).

If the generic path is a directory, you can alsorestore one or more files from this directory byadditionally specifying one or more filenames.

-p profile Specifies a profile other than the defaultinit<ORACLE_SID>.sap profile. A nondefaultprofile must specify the settings outlined in "Task4: Configure the Backup and Restore Utility" onpage 42.

-r parameter_file Specifies the parameter file that the NetWorkerModule uses during the restore process. Thisoption is required only if you have createdadditional parameter files. Otherwise, this optionis not required, because init<ORACLE_SID>.utl isset as the default parameter file duringconfiguration. For details on setting the defaultparameters, see "Task 3: Configure the NetWorkerModule Parameters" on page 33.

Table 20. The brrestore Command Line Options (Part 2 of 2)

Option Description


Appendix B: Environment Variables for RMAN

To configure the RMAN utility for backup and restore, NetWorker softwareuses 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 VariablesThe environment variables are set with the rman_parms parameter in the SAPinitialization file (also called the utilities profile), init<ORACLE_SID>.sap,which is typically located in the following directory:

• 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.


B

Environment Variable Definitions

116

Environment Variable DefinitionsTable 21 on page 116 lists all the NSR_* environment variables that can be usedwith the NetWorker Module.

Table 21. NSR_* Environment Variables (Part 1 of 6)

Variable Description Default and Valid Values

NSR_BROWSE Not recommended. This variable fromrelease 3.5 of the NetWorker Modulefor Oracle has been replaced by theNSR_SAVESET_BROWSE variable.

If this variable is used, itsvalue is assigned to theNSR_SAVESET_BROWSEvariable.

NSR_CHECKSUM Optional. Specifies whether or notthe NetWorker software performschecksumming on the backup data.

• FALSE (default) = TheNetWorker softwareperforms nochecksumming.

• TRUE = The NetWorkersoftware performschecksumming.

NSR_CLIENT Recommended for a backup of Oraclerunning on a cluster, Oracle ParallelServer (OPS), or Real Applicationcluster (RAC) system.

Recommended for all restores.

Specifies the NetWorker Clientresource to use for a backup orrestore session.

Might be needed for disasterrecovery.

• The physical host on whichthe session runs (default).

• A valid NetWorker clienthostname.

NSR_COMPRESSION Optional. Specifies whether or notthe NetWorker software performscompression on the backup data.

• FALSE (default) = TheNetWorker softwareperforms no compression.

• TRUE = The NetWorkersoftware performscompression.



B

117

NSR_DATA_VOLUME_POOL

Mandatory if using set duplexcommand (set to 1, 2, 3, or 4).

Specifies the name of the volumepool to use for the Oracle backup,including a duplexed Oracle backup.

In the case of proxy backups,specifies the volume pool for livebackups only (backups to secondarystorage only).

Note: For a scheduled backup, theNSR_DATA_VOLUME_POOLsetting takes precedence over anypool associated with the scheduledbackup group.

• The most appropriate pool,selected by the NetWorkerserver (default).

• A valid NetWorker poolname.

• The name must be differentfrom the name used byanother NSR_DATA_VOLUME_POOL* variable.

NSR_DATA_VOLUME_POOL1

Mandatory if using set duplexcommand (set to 2, 3, or 4).

Specifies the name of the volumepool to use for a duplexed Oraclebackup.

• Undefined (default).• A valid NetWorker pool

name.• The name must be different

from the name used byanother NSR_DATA_VOLUME_POOL* variable.


Mandatory if using set duplexcommand (set to 3 or 4).






Mandatory if using set duplexcommand (set to 4).








B


118

NSR_DEBUG_FILE Optional. Enables debugging byspecifying the complete pathnameof the log file on the Oracle Serverthat receives debugging informationduring a proxy or nonproxy backupor restore.

Only used for debugging of theNetWorker Module for Oraclemedia management library (MML).

• Undefined (default).• The valid pathname of the

debug file to use on theOracle Server.

Note: If undefined, nodebugging information isgenerated. If a file with thespecified pathname cannot becreated, debugginginformation is either directedto the default location or notgenerated.

NSR_DEBUG_LEVEL Optional. Controls the amount ofdebugging information that theNetWorker Module for Oraclewrites to the debug log file, which isspecified by NSR_DEBUG_FILE.

The debug level limits only theamount of debug informationgenerated by the three functions—sbtread(), sbtwrite(), andsbtpcstatus()—that are called mostoften during backups and restores.All the debug messages for otherfunctions are always written to thelog file, regardless of the debuglevel.

• 0 (default) = Onlyoperational messages arewritten for the sbtread(),sbtwrite(), and sbtpcstatus()functions. No entry or exitmessages are written forthe functions.

• 1 = Only entry and exitmessages are written forthe sbtread(), sbtwrite(),and sbtpcstatus() functions.No operational messagesare written for thefunctions.

• 3 = All debug messages forall the functions are writtento the log file.

NSR_ENCRYPTION Optional. Specifies whether or notthe NetWorker software performsencryption on the backup data.

• FALSE (default) = TheNetWorker softwareperforms no encryption.

• TRUE = The NetWorkersoftware performsencryption.





B

119

NSR_GROUP Optional. Use for a manual backup only.Specifies the NetWorker group touse for a backup session. Used bythe NetWorker server to select thevolume pool for the manual backup.

Note: Do not set this variable for ascheduled backup.

• Default group (default).• A valid NetWorker backup

group name.

Note: A NetWorker Groupresource must be configuredfor the specified backupgroup.

NSR_NO_BUSY_ERRORS

Optional. Specifies whether ascheduled backup fails immediatelywhen the NetWorker server is busyor waits for the NetWorker server toaccept the connection.

Note: For proxy Oracle backups, thisvariable is always set to FALSE.

• FALSE (default) = Thescheduled backup waits forthe NetWorker server toaccept the connection.

• TRUE = The scheduledbackup fails immediatelywhen the NetWorker serveris busy.

NSR_NWPATH Mandatory when removing a backupfrom the NetWorker server if both:• The nsrmm binary is in a

nondefault location; and• The /nsr/res/nwora.res file does not

contain the correct location of theNetWorker client binaries.a

Specifies the complete pathname ofthe directory containing the nsrmmbinary.

• The platform-specificdefault location of theNetWorker client binaries(default).

• A valid pathname of thensrmm binary directory, forexample, /usr/local/bin.

NSR_PROXY_PFILE Supported only for a proxy Oraclebackup or restore.

Mandatory if setting PowerSnapvariables in a configuration file.

Specifies the complete pathname ofa configuration file that containsPowerSnap variable settings for aproxy Oracle backup or restore.

• Undefined (default).• A valid pathname of the

configuration file.

Note: If undefined or aninvalid pathname, variablesettings in the preferredconfiguration file are ignored.




B


120

NSR_SAVESET_BROWSE

Mandatory if setting a nondefaultbrowse policy for a manual Oraclebackup with NetWorker server 6.xor later.

Specifies the date when the entry forthe backup is to be removed fromthe NetWorker client file index.

Note: This variable has an effect onlyfor an Oracle backup withNetWorker server 6.x or later. For ascheduled Oracle backup withNetWorker server 6.x or later, thisvariable overrides the Browse Policyattribute setting in the NetWorkerClient resource.

• The most appropriatepolicy for the client, asselected by the NetWorkerserver (default).

• A valid date innsr_getdate(3) format.

NSR_SAVESET_EXPIRATION

Not recommended. This variable fromrelease 3.5 of the NetWorker Modulefor Oracle has been replaced by theNSR_SAVESET_RETENTIONvariable.

If this variable is used, itsvalue is assigned to theNSR_SAVESET_RETENTION variable.

NSR_SAVESET_RETENTION

Mandatory if setting a nondefaultretention policy for a manual Oraclebackup with NetWorker server 6.xor later.

Specifies the date when the save setbecomes recyclable.

Note: This variable has an effect onlyfor an Oracle backup withNetWorker server 6.x or later. For ascheduled Oracle backup withNetWorker server 6.x or later, thisvariable overrides the RetentionPolicy attribute setting in theNetWorker Client resource.

• The most appropriatepolicy for the client, asselected by the NetWorkerserver (default).

• A valid date innsr_getdate(3) format.





B

121

NSR_SERVER Mandatory for a manual backup if theNetWorker server host is differentfrom the Oracle Server host.

Recommended for a local manualbackup.

Specifies the hostname of theNetWorker server to perform theOracle backup.

• The local physical host(default).

• A valid NetWorker servername.

a. Instead of setting the NSR_NWPATH variable in the RMAN script, a line containing NSR_NWPATH=nsrmm_dirpathcan be added to the /nsr/res/nwora.res file, where nsrmm_dirpath is the complete pathname of the directory containingthe NetWorker nsrmm program. For example: NSR_NWPATH=/opt/networker/bin




B


122


Appendix C: Troubleshooting

This appendix contains troubleshooting tips and NetWorker Module errormessages. It also provides suggestions to help diagnose and fix problems withthe 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 InformationWhen making queries or requests to Customer Support, provide specificinformation for the NetWorker Module you are using.

To verify the release information for your NetWorker Module installation, usethe 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 examplebackint or nsrsapsv.


C

Generating Diagnostic Logs

124

• 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 examplebackint or nsrsapsv.

• On Microsoft Windows: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 LogsTo generate backint diagnostic logs, set the following values in yourinit<ORACLE_SID>.utl file:

debug_level = 9nsr_debug_msg = yesverbose = yes

Note: Debug level is intended for testing and technical support diagnosticsonly.

Backup and Restore ProblemsTable 22 on page 124 provides guidelines for solving problems that may occurduring 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 theNetWorker server.

Ensure that the SAP initialization file,init<ORACLE_SID>.sap, is configured to use theNetWorker Module. For information, see"Task 4: Configure the Backup and RestoreUtility" on page 42.



C

125

Data is not being backed up using thesettings in the Client resource on theNetWorker server.

During a backup, the NetWorker Module doesnot use most of the settings in the Clientresource, except for the save set name andbackup schedule. The client settings must bespecified in the init<ORACLE_SID>.utl file onthe SAP R/3 server running Oracle. Forinformation, see "Task 3: Configure theNetWorker Module Parameters" on page 33.

The bootstrap notification report was notprinted to the printer specified in the Groupresource on the NetWorker Module server.

Bootstrap notification reports are not generatedafter a manual NetWorker Module backup. Togenerate a bootstrap notification report, see"Backing Up the Client File Indexes andBootstrap" on page 49.

Online backup of an Oracle tablespace istaking a long time.

Oracle creates more online redo logs during anonline backup than during an offline backup.This might prolong the online backup.

Following a backup, the parallelism settingin the backint<ORACLE_SID>.log isdifferent from the setting in the parameterfile init<ORACLE_SID>.utl.

The parallelism setting is adjusted by backintduring the backup session depending on otherparameters, for example, when the number offiles within the backup session is lower than theserver parallelism setting.

A specified backup of an Oracle directoryfailed.

The NetWorker Module does not supportbacking up directories. Specify each databaseobject within the directory to back up and thenperform the backup.

You are unable to view the files backed upto the NetWorker server from the SAPDBAprogram on the SAP R/3 server runningOracle.

Ensure that the SAP user’s operating systemauthorization has the appropriate permission toaccess the NetWorker server.




C

Regular Session Error Messages

126

Regular Session Error MessagesThis 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 inthe backint<ORACLE_SID>.log file.

You are unable to restore the most recentversion of the file that was backed up.

When a restore is initiated within a certain timeframe that expired or otherwise is not available,brrestore restores files from previous backups,depending on whether the prev_bk_restoreparameter is set to Yes. For more information,see "prev_bk_restore" on page 39.

Ensure that the SAP user’s operating systemauthorization has the appropriate permission toaccess the NetWorker server.

Table 23. NetWorker Module Regular Session Error Messages (Part 1 of 3)

Error Message Description Solution

Error when sendingout e-mail

The NetWorker Modulecould not write anotification to thecommand line mail utilityspecified in the errormessage.

Notification is supported only onUNIX. Check the usage of the notifyparameters in theinit<ORACLE_SID>.utl file. See"Task 3: Configure the NetWorkerModule Parameters" on page 33.

Error: filenameis not aregular file, rawpartition, ordirectory.

The backint program doesnot support the file type(such as a symbolic link ora named pipe).

Check the filename to see what typeof file is being backed up. Ifbrbackup is requesting backup ofspecial files, contact SAP support.





C

127

Error: save symlinkshad errors

During the process ofsaving symbolic links,backint ran out ofmemory and could nolonger add symbolic linksto its list.

This situation is unlikely to occur.The computer may be low onmemory, or the program maycontain a logic error. If this situationrecurs, contact Legato TechnicalSupport.

Error: unexpectedinquire case.

The files requested in theinput file do not match theSAP R/3 backintspecification. Valid filespecifications include:• #NULL is specified for a

backup ID, with orwithout a filename

• A filename is specifiedwith a backup ID.

• A backup ID is specifiedwithout a filename

Check the backup input filegenerated by brbackup. If the inputfile generated appears to be thewrong format, contact SAP support.

Ignoring, use formatparam=value

Uncommented text in theinit<ORACLE_SID>.utlparameter file does notconform to “param =value” and is ignored.

For information on setting theparameters in theinit<ORACLE_SID>.utl file, see"Task 3: Configure the NetWorkerModule Parameters" on page 33.

Lookup failed onfilename (backup_ID)

The backint program wastrying to look up afilename and/or backupID in the client file index,but the attempt to querythe index failed. The nextmessage should explainwhy the index queryfailed.

Check the error message todetermine why the attempt to querythe index failed. If this message doesnot explain the problem, and futureinquire or restore requests fail,contact Legato Technical Support.

Pathnamenothing foundin index

The specified file was notfound in the NetWorkerclient file index.

Ensure that the file was actuallybacked up in a previous run ofbackint. If brbackup specifiesfilenames that were never backedup, check the SAP R/3 installation.




C

Regular Session Error Messages

128

Process_ID File filenamenot found in index,no attempt to recoverwill be made

The NetWorker softwaredid not save the filenamespecified for recovery andthe filename does notappear in the client fileindex.

Check the filename specified to seeif the name is correct. Checkprevious backups to determinewhether the file was actually savedin a previous backup.

Unable to buildcommand line.

The backint commandwas unable to build acommand line for asubprocess because theprogram ran out ofmemory.

This situation is unlikely to occur.The computer may be low onmemory, or the program maycontain a logic error. If this situationrecurs, contact Legato TechnicalSupport.

Unable to find pidprocess ID in list offiles

The backint program ischecking the status of asubprocess that wascreated to save individualfiles. However, thesubprocess ID does notmatch any of the expectedprocess IDs.

Check the rest of the messages fromthe backup process to ensure thateverything was saved. In particular,check for the message “x of y filessaved at time.” If all of the files werenot saved, retry the backup.

Unable to query withsavetime andfilename both absent

The backint program wastrying to find a file in theclient file index, butneither the save time northe filename wereprovided.

Check the input file to see if any fileinformation is specified incorrectly.If this situation persists, contactLegato Technical Support.

Warning: Unknownparameter,parameter_name

The parameter indicated isnot a valid NetWorkerModule parameter.

For valid parameters, see "Task 3:Configure the NetWorker ModuleParameters" on page 33.





C

129

Fatal Error MessagesThis section discusses fatal error messages and provides information as to whya particular backup, restore, or inquire session fails.

Table 24 on page 129 indicates any fatal error messages that begin with thefollowing line:

Backint exiting at time_stamp with fatal error

Table 24. NetWorker Module Fatal Error Messages (Part 1 of 6)


BACKUP: Bad inputline: line

One of the lines in the input file hada bad format. There should be onlyone or two specifications on eachinput line (filename and size, if it isa special file).

Check the input file brbackupgenerated to make sure it has thecorrect format. If not, and thiserror keeps occurring, contactSAP technical support.

Bad function oninput line,function

The function indicated cannot beperformed as it is either an invalidfunction or you are attempting touse unsupported options.

The NetWorker Module can onlybe invoked through theSAPDBA program or associatedcommands. For information onsupported functions refer to the-f option in SAP’s BC-BRIBACKINT Interface for Oracledocumentation.

Can not reopenfilename as stderr

The backint program was unable toopen a log file for writing.

Check the permissions on the filelisted in the message, as well asthe permissions on the directory.

Cannot connect toserver: error

The backint program was unable toconnect to the NetWorker server tostart reading the media database.

Ensure that the correctNetWorker server is specified.Check the log file to see if anyother messages refer to thisproblem.

Cannot startsession withserver: error

The backint program was unable tostart reading the media database onthe NetWorker server.



C

Fatal Error Messages

130

Checking fordeletion ofsemaphore file:error

The existence of the semaphore filecould not be confirmed because of asystem error.

Check to see if the .switch.sem fileis still in the SAPBACKUPdirectory. If so, delete it beforerunning the SAP R/3 backupagain.

Creatingdirective file:error

The directive file for NetWorkersoftware to use cannot be created.This directive file is created so theNetWorker software can processfiles with the correct attributes.

Check the directory where thedirective file is being created,specified by the backint_tmpdirparameter in the NetWorkerModule’s parameter file, toensure files can write to it.

Error: Too manysymlinks

There are too many symbolic linksto save (more than 100).

If the list of database files to bebacked up contains more than100 symbolic links, considerrestructuring the directories toeliminate the extra symboliclinks.

File was filename,lstat error

The NetWorker Module tried to getinformation for a symbolic link thatdoes not exist or the NetWorkerModule cannot access becausepermission is denied.

Check the file to see that it existsand is a valid symbolic link.

Improperlyformatted backupid: backup ID

The backup ID is incorrect. Itshould specify either a number orthe word #NULL.

Check the input file brrestoregenerated to ensure that it hasthe correct format. If not, andthis error keeps occurring,contact SAP technical support.

INQUIRE: Badinput line: line

One of the lines in the input file hada bad format. There should be onlyone or two specifications on eachinput line (backup ID or #NULL anoptional filename).


Interrupted...backint exiting

The NetWorker Module backintprogram was interrupted during abackup, restore, or inquire session.

This error usually occurs due toa keyboard error.





C

131

Non-recursivedirectory backupis not supportedat this time

You have attempted to back up adirectory. The backup of directoriesis not supported.

Select specific database objects toback up from the SAPDBAprogram and restart the backupprocess.

Not enough savesets, pleaseincrease savesetssetting in .utlfile

The number or size of the save setsto be backed up exceeds the currentsettings for the number of save setsallowed or the maximum save setsize allowed.

Increase the number of save sets.or the maximum save set size.• To configure the parameter for

the number of save sets, see"savesets" on page 40.

• To configure the parameter formaximum save set size, see"ss_size_max" on page 41.

Opening inputfile: error

The input file, which lists all files tobe backed up or restored, could notbe opened. It may not exist, or itmay not have read permissions.

Ensure that the input file existsand is readable.

Opening outputfile: error

The output file could not be openedfor the reason specified.

Check the permissions on theoutput file and directory, andcheck for sufficient disk space tocreate a new file.

Opening parameterfile

Unable to open the backintparameter file,init<ORACLE_SID>.utl.

Attempt to open the parameterfile for backint in any text editor.If you are unable to open theparameter file, replace it withthe original file from theNetWorker Module CD.

Opening switchlist file foronline backup:error

When performing an onlinebackup, backint tries to open a fileto communicate with brbackup.This file could not be opened for thereason given.

Check to see if the .switch.lis fileexists in the SAPBACKUPdirectory. If so, check thepermissions on this file.Normally, the NetWorkerModule deletes and re-createsthis file for every tablespace tobe switched into backup mode.




C


132

Opening switchlog file foronline backup:error

When performing an onlinebackup, backint expects brbackupto provide a log file of thetablespaces that were switched intoor out of backup mode.

Check to see if the .switch.log fileis still in the SAPBACKUPdirectory. If so, delete it beforerunning the SAP R/3 backupagain.

Opening switchsemaphore filefor onlinebackup: error

When performing an onlinebackup, backint tries to open a fileto communicate with brbackup.This file could not be opened for thereason given.

Check to see if the .switch.sem fileexists in the SAPBACKUPdirectory. If so, check this file’spermissions. Normally, theNetWorker Module deletes andre-creates this file for everytablespace to be switched intobackup mode.

ORACLE_HOME notset.

The ORACLE_HOME environmentvariable must be set.

Set the ORACLE_HOMEenvironment variable to thecorrect directory.

recover_start:cannot connect toserver server_name

The backint program was unable toconnect to the NetWorker server tostart the recovery process.


RESTORE: Badinput line: line

One of the lines in the input file hada bad format. There should be onlytwo or three specifications on eachinput line (backup ID or #NULL, afilename, and an optionaldestination directory).

Check the input file brrestoregenerated to make sure it has thecorrect format. If not, and thiserror keeps occurring, contactSAP technical support.

SAPBACKUP must beset for onlinebackups.

The SAPBACKUP environmentvariable must be set to a validdirectory for an online backup. Thisdirectory is used to hold the switchlog and switch list files onWindows.

Set the SAPBACKUPenvironment variable to a validdirectory (such as:%ORACLE_HOME%\<ORACLE_SID>\sapbackup onWindows).





C

133

Semaphore filenot deleted in timeseconds

When performing an onlinebackup, the SAP R/3 module waswaiting for the switch semaphorefile to be deleted. After waitingsome number of seconds, the switchsemaphore file still was not deleted.

If brbackup appears to berunning properly but just slowly,you can increase thesem_timeout setting ininit<ORACLE_SID>.utl.

stat’ing file:error

The filename given in the input filedoes not exist, or it may beinaccessible.

Check the file to see if it existsand has read permissions.

Switch log fileindicates anerror.

The brconnect program indicatedin the switch log file that there wasan error switching one of thetablespaces into or out of backupstatus. This is considered a fatalerror in the backint specification.

Investigate the error messages inthe switch log file to determinethe problem. Check the SAP R/3installation or the SAP R/3documentation to determine theproblem.

This eval copyhas expired

The evaluation version of theNetWorker Module has expired.

Contact Legato Sales to obtain apermanent enabler.

For instructions on entering theenabler code, refer to the LegatoNetWorker Module for SAP R/3with Oracle Installation Guide.

Unable toallocate memoryfor structfileinfo

The backint program ran out ofspace when it tried to allocatememory for a block of fileinformation.

Check the memory usage on thecomputer. You may need toreboot the computer if it isrunning low on memory. If theinput file is excessively large,check to make sure SAPDBA isproviding a valid list of files.

Unable toallocate memory:error

The backint program was unable toallocate memory.

Check the memory usage on thecomputer. You may need toreboot the computer if it isrunning low on memory.




C


134

Unable to changeto root: error

In a cluster environment on UNIX,the program was unable to changeits real and effective user IDs toroot.

Ensure the user has properpermission to log on as root.

Unable to executechild backintprocess.

The backint process could notexecute a subprocess to back up anindividual save set.

Ensure that the backint binary isinstalled in the directory fromwhich SAPDBA, brbackup, orbrrestore is run. Check the logfile for any other messageswhich may help pinpoint theproblem.

Unable to openoutput file: error

The output file could not be openedbecause of the error specified.

Check the permissions on theoutput file and directory, andcheck for sufficient disk space tocreate a new file.

Usage error An unsupported option wasincluded in the backint command.

For parameters accepted bybackint, refer to SAP’s BC-BRIBACKINT Interface for Oracledocumentation.

Use absolute pathname for: filename

The filename given in the input filewas not an absolute pathname. Thefile cannot be restored or inquiredwithout having the full pathname.


waitchild (name)failed: error

The program could not properlyreceive the exit code from asubprocess. It is possible that thesubprocess did not start correctly.

Check any prior error messagesto determine whether asubprocess failed, and if so, why.

Warning, emptyinput file

The input file that contains the listof files to be backed up or restoredis empty.

Ensure that you have selecteddatabase objects for backup orrestore.




Glossary

This glossary contains terms and definitions found in this manual. Most of theterms are specific to Legato NetWorker Module for SAP R/3 with Oracleproducts.

? The Oracle placeholder for the main directory of theOracle database instance identified as $ORACLE_HOME.See init<ORACLE_SID>.utl.

archive The process by which NetWorker software backs updirectories or files to an archive volume and then groomsthem to free disk space. When data is archived, it is writtento one or more storage volumes and then marked so that itis never subject to automatic recycling. You can delete thearchived files from the client, thus freeing disk space.

archived redo log An archived copy of a filled online Oracle redo log. Youcan optionally configure an Oracle database to archivecopies of the online redo logs after they fill. An archivedredo log preserves older redo log data for recoveryoperations while the preallocated online redo log files arereused to store the most current database changes. See redolog.

ARCHIVELOG mode Setting the Oracle database to this mode enables archivingof the online redo logs.

LEGATO NetWorker Module for SAP R/3 with Oracle, Release 3.0, Multiplatform VersionAdministrator’s Guide136

Glo

ssar

y authentication method A security method that enables high confidence in theidentity of users, clients, and servers in distributedenvironments. The NetWorker Module software allowstwo methods of authenticating identity:• Database authentication uses the SAP R/3 or Oracle

system user name, as designated by the databaseadministrator for the client’s Oracle database. This username and its password must be encrypted in thescheduled backup configuration file.

• External or enterprise authentication applies a user namethat is derived from either the save set name entered inthe Client resource or the ORACLE_SID parameter set inthe scheduled backup configuration file.

backint The interface the NetWorker Module software uses toconnect the NetWorker software with the SAP BRTools.The backint program enables backups, restores, orinquiries on the associated Oracle databases.

backup device type The backup device type to which the SAP BRToolsprogram 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 disasterrecovery procedures. It is composed of three componentsthat reside on the NetWorker server: the media database, theresource database, and the server index.

brarchive The SAP BRTools program that sends requests to theNetWorker Module to back up Oracle database archivelogs.

brbackup The SAP BRTools program that sends requests to theNetWorker Module to back up Oracle data files, controlfiles, redo logs, and tablespaces.

browse policy A policy that determines how long entries for backup dataremain in the client file index.

brrestore The SAP BRTools program that sends requests to theNetWorker Module to restore Oracle data to the Oracleserver.


Glossary

137

Glo

ssary

BRTools A set of SAP tools used to back up and recover SAP R/3data in an Oracle database. The tools are: brbackup,brarchive, and brrestore.

client file index A database of information the NetWorker server maintainsthat tracks every database object, file, or filesystem backedup. The NetWorker server maintains a single client fileindex for each client computer.

clone The NetWorker process used to make an exact copy ofsaved data (save sets). NetWorker software indexes andtracks clones in both the client file index and the mediadatabase. The NetWorker Module for SAP R/3 with Oraclesoftware 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. Savesets of different types may not be intermixed on onevolume.

cluster Two or more nodes that are connected and appear tonetwork users as a single highly available system. Ahighly available system allows the application services tocontinue despite most hardware or software failures.

cold Oracle backup See offline backup.

database authentication See authentication method.

DBA An abbreviation for database administrator. The personnormally responsible for installing, configuring, andmaintaining Oracle database systems.

deferred live backup See live backup.

device A storage unit that reads from and writes to storagevolumes. A storage unit can be a tape device, optical drive,autochanger, or file connected to the server or storagenode.

directed recovery A recovery method used to recover data that originated onone computer and re-create it on another computer.


Glo

ssar

y directive An instruction that directs NetWorker software to takespecial actions on a given set of files for a specified clientduring a backup.

enabler code A special code provided by Legato that activates thesoftware. The enabler code that unlocks the base featuresfor software you purchase is referred to as a base enabler.Enabler codes for additional features or products (forexample, autochanger support) are referred to as add-onenablers.

external or enterpriseauthentication

See authentication method.

file index See client file index.

filesystem 1. A file tree located on a specific disk partition or othermount point.

2. The entire set of all files.

3. A method of storing files.

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 theSAP BRTools program uses during backup, restore, andarchive sessions.

init<ORACLE_SID>.utl The NetWorker Module parameter file that specifies theparameters 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/3with Oracle data that is stored as a backup on the primarystorage system.

instant restore The process by which the snapshot that was created on theprimary storage system with an instant backup ismounted and its saved data is retrieved as needed.


Glossary

139

Glo

ssary

license enabler The license code that enables you to run a feature orproduct.

live backup A live backup (also known as a "PIT rollover" or "rolloverto tape" backup) is a tape backup of a previously-createdsnapshot. The NetWorker Module for SAP R/3 withOracle supports the following two types of live backup:• Immediate live backup (also known as "serverless

snapshot backup" or "snapshot-based backup") is aprocess by which a temporary snapshot is created, andimmediately backed up to secondary storage such astape. The snapshot is then automatically deleted from theprimary storage.

• Deferred live backup is a process by which a permanentsnapshot, created on the primary storage system, isbacked up to secondary storage such as tape. Thesnapshot is retained on the primary storage for aspecified period of time.

manual backup An unscheduled backup that a user requests from theNetWorker client side. A manual backup does notgenerate a bootstrap save set.

media database A database that contains indexed entries about the storagevolume location and the life cycle status of all data andvolumes the NetWorker server manages.

offline backup A backup of Oracle database objects performed while thecorresponding Oracle instance is shut down andunavailable to users.

online backup A backup of Oracle database objects performed while thecorresponding Oracle instance is running and available tousers.

online indexes The databases located on the NetWorker server thatcontain 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 memorythat is created each time a database starts up.

Oracle user The user of an Oracle database.


Glo

ssar

y ORACLE_SID The system ID of the Oracle database instance.

parameter A variable used to identify the specific values or options tobe used by associated commands.

pathname A set of instructions to the operating system for accessinga file.• An absolute pathname indicates how to find a file starting

from the root directory and working down the directorytree.

• A relative pathname indicates how to find the file startingfrom where you are now.

PIT copy Point-in-time copy, which generally means a permanentlyretained snapshot of data created with a PowerSnapModule. A snapshot results in one or more PITs beingcreated nearly simultaneously with the option to backthese up to tape.

RDBMS An abbreviation for Relational Database ManagementSystem, which refers to the primary architecture that theOracle database uses.

recover NetWorker software: The command used to browse theserver index and to recover files from a backup volume toa client’s disk (a process in Oracle known as "restore").

Oracle: The datafile recovery method that uses Oraclecommands to apply archived redo logs and online redologs to make the database consistent.

Recovery Manager See RMAN.

redo log The online log of an Oracle database, consisting of at leasttwo redo log files (separate from the datafiles) that recordall changes made in the database. See also archived redo log.

resource database A database that contains information about each of theconfigured backup server’s resources.

restore The process of retrieving individual files from backupmedia and storing the files on disk.


Glossary

141

Glo

ssary

RMAN An abbreviation for Recovery Manager, the Oracle utilitythat acts as an intelligent interface to Oracle databases andworks with third-party media management products,such as NetWorker Modules, to back up and restore Oracledatabase objects.

rollback restore The process by which the entire snapshot, created on theprimary storage system by an instant backup, is restoredto the source location by using the hardware’s particularcapabilities.

rollover to tape See live backup.

root The UNIX superuser account (with user name “root” anduser ID). By extension, the privileged system-maintenancelogin on any operating system.

sapclone The NetWorker Module command used to create aduplicate copy of the data (save sets) backed up using theNetWorker Module software.

SAPDBA The SAP R/3 database administration utility thatsimplifies the administrative tasks related to Oracledatabases, including backup and restore operations. Thisutility can be used to call brbackup, brrestore, andbrarchive programs.

save set A group of files or a filesystem from a single clientcomputer backed up to storage media.

save set ID A unique identification number that NetWorker softwareassigns to a save set.

save set status The NetWorker attribute that indicates whether a givensave set is restorable, recoverable, or recyclable. The saveset status also indicates whether the save set has beensuccessfully backed up.

secondary storagerestore

The process by which a snapshot that was backed up tosecondary storage by a live backup is restored by using thetraditional NetWorker recover program.


Glo

ssar

y server index A database containing information about the NetWorkerserver's files that have been backed up during scheduledbackups. Also known as the NetWorker server’s client fileindex.

SID An Oracle abbreviation for system identifier, a uniquename for an Oracle database instance. This value istypically set in an ORACLE_SID environment variable.

snap set The group of datafiles included in any given snapshotcopy, the lifecycle of which is specified in the SnapshotPolicy.

snapshot A point-in-time copy of a filesystem or partition.

ssid See save set ID.

tablespace An Oracle database structure comprising one or moredatafiles.


Index

<ORACLE_SID>, description 16

A

alert, backup completion 37arch_backint_log parameter 34archive logs 39archive redo logs 48ARCHIVELOG mode 47attempts, retry backup 40

B

backintbackup process 24command 20, 45description 18, 20parameter file 33restore process 26setting ownership of 30

backint_log parameter 34backint_tmpdir parameter 34backup

archive redo logs 48bootstrap file 49client file index 49client settings 54command 55command attribute 22completion notification 37deferred live 79, 102diagram 25group 36immediate live 78, 99instant 78, 96live 78, 99manual 45offline manual 46online manual 47–48PowerSnap manual 102PowerSnap records 104

PowerSnap types of 77processes 24, 96

with RMAN 25with SAPDBA 24

rollover 78, 99save sets grouped by filesystem 41scheduled 53serverless snapshot 78session log 50, 63session report 50, 63snapshot-based 78

backup_dev_type parameter 42bootstrap file, backing up 49bootstrap, NetWorker 98, 100BR_EXEC 60brarchive 97, 99

command 22, 109description 22difference from brbackup 19manual backup 109supported options 109syntax 109

brbackup 97, 99, 109command 22, 109description 22difference from brarchive 19offline backup 47online backup 48supported options 109syntax 109

browse naming format 41browse policy 70

expiration 36for manual backup 49

brrestore 26, 105command 22, 105description 22supported options 113usage 113

BRTools 22configuring 42See also SAPDBA

IndexC - D

Ind

ex


C

checksum parameter 35client

configuring 31, 54expiration parameter 36NetWorker, configuring 54parameter 35resource 31save set location 70settings in parameter file 54

client file indexbackup 49database 49

Client resource 54configuration 54parameter 35

client resourcePowerSnap 88

cloningmessages 67monitoring 67save sets 65syntax of sapclone 65

clusterclient file index 35data, cloning 66data, restoring 72

commandbackint 20, 45backup 55brarchive 22, 109brbackup 22, 109brrestore 22, 105mminfo 104nsrim 50nsrinfo 104nsrsapsv 21, 55nsrsnapadmin 102sapclone 65savefs 96, 99savegrp 49, 96, 99scanner 70

componentsdescription 20NetWorker client 22NetWorker Module 20

Oracle 23PowerSnap 23SAP R/3 22user-configurable 20

compress parameter 35configuration

BRTools 42NetWorker client 54NetWorker for PowerSnap 87NetWorker Module environment 30PowerSnap 86SAPDBA 42

configuration fileinit<ORACLE_SID>.sap 22, 42–43init<ORACLE_SID>.utl 20, 23, 33, 84, 93init<ORACLE_SID>.utl for PowerSnap 89nmsapps.cfg 23, 84, 93nsrsapsv.cfg 21, 55, 58

cyclic redundancy checking 35

D

databacking up 24–25, 45, 53expiration 70recovering 16restoring 26, 69

data flow descriptionbackup 24PowerSnap 81restore 26

databaseinstance, restoring 70, 113server, description 17

datafile, restoring by ID 114debug level 124deferred live backup 79, 102description

backup and restore processes 24components 20features 17NetWorker Module 18NetWorker server 18RMAN 19SAP R/3 18SAPDBA 18, 22

diagnose problems 123

IndexE - L

Ind

ex


diagnostic logs 124disaster recovery files 49disk failure 49distributing backup load 40

E

encrypt parameter 36encryption, SAP user for OS and Oracle 57environment variables

mandatory 117, 119–121NSR_BROWSE 116NSR_CHECKSUM 95, 116NSR_CLIENT 95, 116NSR_COMPRESSION 95, 116NSR_DATA_MOVER 93NSR_DATA_VOLUME_POOL 95, 117NSR_DEBUG_FILE 118NSR_DEBUG_LEVEL 118NSR_ENCRYPTION 95, 118NSR_GROUP 95, 119NSR_MAX_STREAMS 93, 95NSR_NO_BUSY_ERRORS 119NSR_NWPATH 119NSR_PROXY_PFILE 119NSR_PS_DEBUG_LEVEL 93NSR_PS_SAVE_PARALLELISM 94–95NSR_SAVESET_BROWSE 120NSR_SAVESET_EXPIRATION 95, 120NSR_SAVESET_RETENTION 120NSR_SERVER 95, 121NSR_SNAP_TYPE 94RESTORE_TYPE_ORDER 94used with RMAN 43, 115

error messages 123fatal 129nonfatal 126

errors notification, enabling 37expiration of data 70expiration parameter 31, 36

F

failure notification 37features

description 17

NetWorker Module 18NetWorker server 18Oracle, with 19PowerSnap 19RMAN, with 19SAP R/3, with 18SAPDBA, with 18

files backed up, number of 51files requested for backup 51filesystem

group save sets by 41full restore 70

G

group parameter 36group resource for PowerSnap 87group save sets by filesystem 41

H

hostname, NetWorker server 40

I

ID range, restoring by 114ID, restore by 114immediate live backup 78, 99index entries, query parameter 39init<ORACLE_SID>.sap file

description 22enabling SAPDBA or brbackup 42enabling SAPDBA or RMAN 43specifying different profile 114

init<ORACLE_SID>.utl file 20, 93equivalent parameters for PowerSnap 95parameters 33parameters for PowerSnap 23, 84, 89

input file report 51instant backup 78, 96instant restore 80, 105

L

level_full parameter 36

IndexM - N

Ind

ex


live backup 78, 99location of save set data 70logs

arch_backint_log parameter 34archive redo 48backint_log parameter 34backint_tmpdir parameter 34backup session reports 50, 63restore 72verbose setting 41

M

mailx utility 37mandatory environment variables 117, 119–

121manual backup 45

backup session reports 50, 63bootstrap 46, 49client file indexes 49command line options 109offline 46online 47using brarchive command 46, 48using brbackup command 46, 48with SAPDBA 46, 48

max_logs parameter 36maximum size of save sets 41media database records 70messages

cloning 67notify_done 37notify_error 37notify_start 37notify_success 37

mminfo 104monitoring

backups 50, 63cloning 67restores 72

N

namingconventions 16save set format 41

save sets 41NetWorker

bootstrap backup 98, 100client

components 22configuration 54name 35

media database service, nsrmmdbd 97, 100,102

save set records 70server

components 20features 18hostname 40

NetWorker Modulecomponents 20environment 30example network 16features 18parameter file 84restoring with 113

nmsapps.cfg file 23, 84, 93notify_done message 37notify_error message 37notify_start message 37notify_success message 37NSR_BROWSE 116NSR_CHECKSUM 95, 116NSR_CLIENT 95, 116NSR_COMPRESSION 95, 116NSR_DATA_MOVER 93NSR_DATA_VOLUME_POOL 95, 117NSR_DEBUG_FILE 118NSR_DEBUG_LEVEL 118NSR_ENCRYPTION 95, 118NSR_GROUP 95, 119NSR_MAX_STREAMS 93, 95NSR_NO_BUSY_ERRORS 119NSR_NWPATH 119NSR_PROXY_PFILE 119NSR_PS_DEBUG_LEVEL 93NSR_PS_SAVE_PARALLELISM 94–95NSR_SAVESET_BROWSE 120NSR_SAVESET_EXPIRATION 95, 120NSR_SAVESET_RETENTION 120NSR_SERVER 95, 121NSR_SNAP_TYPE 94

IndexO - P

Ind

ex


nsrexecd service 96, 99nsrim command 50nsrindexd service 97, 100, 102, 107nsrinfo command 104nsrmmdbd service 97, 100, 102nsrpsd program 85, 107nsrsapadm, description 21nsrsapsv

command 21, 55configuration file 58description 21program 97, 99

nsrsapsv.cfg fileconfiguration 58description 21enabling 55

nsrsnapadmin command 102

O

offline manual backup 46online manual backup 47–48options

brarchive 109brbackup 109brrestore 113sapclone command 65

Oraclecomponents used 23features used 19user 30

ORACLE_SID 61

P

parallelism, setting 38parameter

arch_backint_log 34backint_log 34backint_tmpdir 34backup_dev_type 42BR_EXEC 60checksum 35Client resource 35compress 35encrypt 36

equivalents to PowerSnap variables 95expiration 36group 36level_full 36max_logs 36notify_done 37notify_error 37notify_start 37notify_success 37ORACLE_SID 61parallelism 38pool 39PowerSnap 89prev_bk_restore 39ps_archive_mode 89ps_backup_mode 89ps_exclude_backup_bi_run_nums 90–92ps_group_objs 92ps_opaque_pfilename 23, 93query_index 39raw_dir 40retry_count 40rman_parms 43savesets 40sem_timeout 40server resource 40ss_group_by_fs 41ss_size_max 41ssnameformat 41verbose logs 41

parameter filechanging 114

parametersfor brarchive 109for brbackup 109NetWorker Module 33

Password for Remote User (Windows) 55password of SAP user 57PATH variable, setting 30physical media failures 78PIT copy 78point-in-time copy 78policies, expiration 36, 70pool

multiple 39parameter 39selection 36

IndexQ - R

Ind

ex


settings 39PowerSnap

attribute settings 83backup processes 96backup records 104backups and restores 75client resource 88components 23configuration 86configuration file 23, 84, 93data flow descriptions 81features 19getting started 83group resource 87instant backup 78, 96instant restore 80, 105invoking a restore 105invoking backups 96live backup 78, 99Module 76nsrpsd daemon 85parameter file 23parameter settings 89ps_opaque_pfilename file 85requirements 76restore from secondary storage 80, 107restore processes 105rollback restore 80, 105rollover backup 78, 99Snapshot Policy resource 87Snapshot Pool resource 87types of backups 77types of restore 79variables 23

PowerSnap Module 84prev_bk_restore parameter 39problems, backup or restore 124processes, NetWorker Module 24profile, using different for restore 114program

brarchive 97, 99brbackup 97, 99nsrd 96, 99nsrexecd 96, 99nsrindexd 97, 100, 102nsrmmdbd 97, 100, 102nsrsapsv 97, 99

savefs 96, 99savegrp 96, 99

ps_archive_mode 89ps_backup_mode 89ps_exclude_archive_bi_run_nums 90ps_exclude_archive_paths 91ps_exclude_backup_bi_run_nums 90ps_exclude_backup_paths 91ps_group_objs 92ps_inquire_mode 89ps_opaque_pfilename 89ps_opaque_pfilename file 85ps_opaque_pfilename parameter 23, 93ps_ps_before_nonps 92ps_restore_mode 89

Q

queryPowerSnap backup records 104

query_index parameter 39

R

raw directories 40raw_dir parameter 40recover, description 16Recovery Manager 19

See also RMANrelated documentation 27release information, verifying 123Remote Exec services 46–47Remote User (Windows) 55report, backup session 50, 63requirements

PowerSnap 76resources, NetWorker 31, 36

client 54configuring 31group 31pool

and pool parameter 31, 39configuring 31

schedule 32server 32

restore

IndexS - S

Ind

ex


a single tablespace 113all tablespaces 113brrestore, syntax 113by datafile ID 114by ID range 114cluster data 72command line options 113data 69description 16diagram 26entire database instance 70, 113from secondary storage 80, 107full 70instant 80, 105monitoring 72options, syntax 113parameter file used for setting 114PowerSnap 79previous backup if not found 39process described 24processes 105reviewing report log 72rollback 80, 105single database object 70using a different profile 114using NetWorker Module 113

restore messages, suppress 113restore process

with RMAN 26with SAPDBA 26

RESTORE_TYPE_ORDER 94retention policy

expiration 70manual backup 49

retry_count, setting 40reviewing

backups 50, 63restore logs 72

RMAN 23backup process 25enabling 43environment variables 43, 115features with 19restore process 26rman_parms parameter 23, 43

rollback restore 80, 105rollover backup 78, 99

root, setting owner to 30

S

SAP R/3components 22features 18initialization file 42–43

sapclonecommand 65description 21options 66syntax 65

SAPDBA 24backup process 24components 22configuring 42description 22features 18restore process 26utilities 18

savearchive redo logs 48bootstrap file 49client file index 49command 40

save setscloning 65description 54expiry 70maximum size parameter 41naming 41parameter 40setting 22viewing 69

save streams, setting 38savefs command 96, 99savegrp command 49, 96, 99savesets parameter 40scanner command 70scheduled backup

configuration file 55, 57–58tasks 53

sem_timeout parameter 40semaphore file 40server resource parameter 40serverless snapshot backup 78

IndexT - V

Ind

ex


servicensrd 96, 99nsrexecd 96, 99nsrindexd 97, 100, 102nsrmmdbd 97, 100, 102

setting backint ownership 30single database object, restoring 70single tablespace, restoring 113snap set 78snapshot 78, 96Snapshot Policy resource 87Snapshot Pool resource 87snapshot-based backup 78special terms 16ss_group_by_fs parameter 41ss_size_max parameter 41ssnameformat parameter 41starting attribute 52suppress restore messages 113symlink attribute 52

T

tablespaces, restoring 113temporary files directory 34testing 124timeout period 40troubleshooting tips 123

U

uid bit 30user encryption, SAP 52user-configurable components 20username of SAP user 57

V

validation of server indexes 39variables

mandatory 117, 119–121NSR_BROWSE 116NSR_CHECKSUM 95, 116NSR_CLIENT 95, 116NSR_COMPRESSION 95, 116NSR_DATA_MOVER 93

NSR_DATA_VOLUME_POOL 95, 117NSR_DEBUG_FILE 118NSR_DEBUG_LEVEL 118NSR_ENCRYPTION 95, 118NSR_GROUP 95, 119NSR_MAX_STREAMS 93, 95NSR_NO_BUSY_ERRORS 119NSR_NWPATH 119NSR_PROXY_PFILE 119NSR_PS_DEBUG_LEVEL 93NSR_PS_SAVE_PARALLELISM 94–95NSR_SAVESET_BROWSE 120NSR_SAVESET_EXPIRATION 95, 120NSR_SAVESET_RETENTION 120NSR_SERVER 95, 121NSR_SNAP_TYPE 94PowerSnap 23, 93RESTORE_TYPE_ORDER 94

verbose logs parameter 41viewing save sets 69virtual node 35

Documents

Legato NetWo 爀欀攀爀 䴀漀搀甀氀攀 昀漀爀ਠSAP R/3 with O 爀 …

Legato NetWo 爀欀攀爀䴀漀搀甀氀攀昀漀爀ਠSAP R/3 with O 爀 …