nmsapag_30

8/9/2019 nmsapag_30

1/150

NetWorker

Module for SAP R/3with Oracle

Release 3.0

Multiplatform Version

Administrators Guide

8/9/2019 nmsapag_30

2/150

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, Administrators GuideDecember 2003

01-8565-3.0

LEGATO and the LEGATO logo are registered trademarks, and LEGATO NetWorker, NetWorker, Co-StandbyServer, RepliStor,SnapShotServer, QuikStartz, AlphaStor, ClientPak, Xtender, XtenderSolutions, DiskXtender, ApplicationXtender, ArchiveXtender,EmailXtender, and EmailXaminer are trademarks or registered trademarks of LEGATO Software, a division of EMC. This is 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 Corporation

Fujitsu /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 Corporation

NetFORCE /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.

8/9/2019 nmsapag_30

3/150

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 NOTPROCEED WITH THEINSTALLATION 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 PROCEEDING

WITH 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 ANDDOCUMENTATION, ANDPROOF 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 ISNOT A PREREQUISITETO THE VALIDITY OR ENFORCEABILITY OF THIS EULA ANDNO SOLICITATION OF ANY SUCH WRITTEN APPROVAL BY OR ON BEHALF OFLEGATO SHALL BE CONSTRUEDAS AN INFERENCE TO THECONTRARY. 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.1Authorization Code: means the unique code provided to Licensee byLegatofor permanent activation of the Software. TheAuthorization 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.2Documentation: Documentation: means the user reference materialson any media, provided by Legato for use with the Software.

1.3 Enabler Code: means thecode providedby Legatofor activation of theSoftware.

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

1.5Software: means the object code copy of the software program

provided 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.1Ownership 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.3Administration 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 programsin no wayimplies a license from Legatoand 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.1Grant. 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 the

Software temporarily in case of computer system malfunction. TheSoftwaremay belicensed: (a) on a per copyor per seat basis, on a physicalor virtual machine, (b)based upon thenumber ofmailboxes or thenumberof 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 Softwareor any portion or copyof it. Licensee may

not 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.2Copies. 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.3Restrictions on use. Licensee shall not, and shall not aid, abet, orpermitany thirdpartyto: (i)decompile, disassemble,or otherwisereverse

engineer or attempt to reconstruct or discover any source code orunderlying ideas or algorithms of the Software by anymeanswhatsoever;(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 enableunauthorized parties to usethe Software. IfEClaw 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 the

Software unless Legato cannot or has not complied with such request in acommercially reasonable amount of time.

3.4Purchase Orders. Nothing contained in any purchase order,acknowledgment,or invoice shall in anyway modifythe terms or addanyadditional terms or conditions to this EULA.

3.5Updates. 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 only

be 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.6Evaluation License. This Section applies if the Software is being usedforan initial thirty(30)day evaluation period. Thelicense 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 Licensees 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.7General Public License ("GPL"). The Software may include one or

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

8/9/2019 nmsapag_30

4/150

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.1Media and Documentation. Legato warrants that if the media or

documentation aredamagedor physically defective at the timeof 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 Legatowill provide Licensee with replacements at no cost.

5.2Limited 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 Legatos 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 beconstruedto limit thewarrantyto the minimum warranty required by law.

5.3 Remedies. The remedies availableto Licensee hereunder for anysuchSoftware which does not perform as set outhereinshall be either repair orreplacement, or, if such remedy is not practicable in Legatos opinion,refundof thelicense fees paid by Licensee upon a returnof allcopies 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.1Warranty Disclaimer. EXCEPT FOR THE LIMITED WARRANTYPROVIDED IN SECTION 5 ABOVE,ALL SOFTWAREIS PROVIDED "ASIS". LEGATO AND ITS LICENSORS MAKE NO WARRANTIES WITHRESPECT TO ANY SOFTWARE AND DISCLAIMS ALL STATUTORY ORIMPLIED WARRANTIES, INCLUDING WITHOUT LIMITATIONWARRANTIESOF MERCHANTABILITY, FITNESS FOR A PARTICULAR

PURPOSE, 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 ANYWARRANTY, 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.1Limitation of Liability. EXCEPT FOR BODILY INJURY, LEGATO(AND ITSLICENSORS)WILLNOT BE LIABLEOR RESPONSIBLEWITHRESPECT TO THE SUBJECT MATTER OF THIS EULA UNDER ANYCONTRACT, NEGLIGENCE, STRICT LIABILITY, OR OTHER LEGALOR EQUITABLE THEORY FOR: (I) ANY INDIRECT, SPECIAL,INCIDENTAL OR CONSEQUENTIALDAMAGES,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 or

limitation of incidental or consequential damages, Legato's liability insuch jurisdictions shall be limited to the extent permitted by law.

8.TERM AND TERMINATION

8.1Term. The term of this EULA is perpetual unless terminated inaccordance with its provisions.

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

8.3Effect 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, andso certify to Legato. Except forthe License granted hereinand as expressly provided herein, the terms of this EULA shall survivetermination.

9.MISCELLANEOUS

9.1Governing 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.2Government 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 isLegatoSoftware, a division of EMCCorporation, 2350 W. El Camino Real,

Mountain View, CA 94040. The Software is a commercial softwareproduct, licensed on theopen market at marketprices, andwas developedentirely at private expense and without the use of any government funds.

9.3Export 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 whose

jurisdiction Licensee operates or does business. Licensee shall at all timesstrictly comply with all such laws, regulations, and orders, and agrees to

commit no act which, directly or indirectly, would violate any such law,regulation or order.

9.4Assignment. 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.5Sole 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.6Equitable Relief. The parties agree that a breach of this EULAadversely affecting Legato's intellectual property rights in the Softwaremay cause irreparable injuryto 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.7No 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.8Severability. 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 theentire understanding andEULAbetween 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.

8/9/2019 nmsapag_30

5/150

LEGATO NetWorker Module for SAP R/3 with Oracle, Release 3.0, Multiplatform Version

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

8/9/2019 nmsapag_30

6/150



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.

8/9/2019 nmsapag_30

7/150

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.

8/9/2019 nmsapag_30

8/150



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.

8/9/2019 nmsapag_30

9/150

Contents



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

Index........................................................................................................... 143.

8/9/2019 nmsapag_30

10/150



Contents

10

8/9/2019 nmsapag_30

11/150



Preface

This guide provides information on how to configure and manage the LegatoNetWorkerModule for SAP R/3 with Oracle software (referred to in thisguide as simply the NetWorkerModule software).

Install this multiplatform NetWorker Module software on the supportedUNIX, Linux, or Microsoft Windows server and clients before using the

information presented in this guide. For installation instructions, refer to theLEGATO NetWorker Module Installation Guidefor 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. Most of the documents are in Adobe Acrobat Portable DocumentFormat (PDF), and can be viewed by downloading and installing the AdobeAcrobat Reader. TheReader is available in the/viewers/acroread directory on theLEGATODocumentation Suite CD-ROM, or directly from Adobe. To installand use the Reader on the preferred platform, refer to the instructions in the

CD-ROMs/viewers/acroread/readme.txtfile or at the Adobe web site.

8/9/2019 nmsapag_30

12/150



Conventions

12

Conventions

This 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

Thensradmincommand starts thecommand line version of the NetWorkerAdministrator program.

italicin 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, inc:\page le.sys.

italicincommand line

A variable that must beprovided in the command

line

nwadmin -s server_name

fixed-width Examples and informationdisplayed on the screen

media waiting: recover waiting for

8mm 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 theno_verifyoption withextreme caution.

8/9/2019 nmsapag_30

13/150

8/9/2019 nmsapag_30

14/150



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 Feedback

LEGATO 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 the

Comments 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 during

product 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]
http://www.legato.com/http://www.legato.com/http://www.legato.com/http://www.legato.com/http://www.legato.com/http://www.legato.com/http://www.legato.com/

8/9/2019 nmsapag_30

15/150



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 PowerSnapsoftware,which is required for snapshot backups.

This chapter contains the following sections:

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

"Naming Conventions Used in This Guide" on page 16

"Basic Network Configuration" on page 16

"Summary of Features" on page 17

"Summary of Components and Settings" on page 20

"Summary of Processes" on page 24

"Related Documentation" on page 27

Importance of Backing Up Mission-Critical Data

It is important to back up computer systems to protect them from the loss 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.

8/9/2019 nmsapag_30

16/150



1

Naming Conventions Used in This Guide

16

Naming Conventions Used in This Guide

Table 1 on page 16lists special terms that are used in this guide.

Basic Network Configuration

This section describes a network configuration for regular backup andrecovery services when using the NetWorker Module software.

Note: For information onsnapshotbackup 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 thebrbackup,brrestore, andbrarchiveprograms.

NetWorker Modulesoftware

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

The name of the Oracle database instance that youwant to back up, usually the argument for thebrbackuporbrarchive -uoption.

restore and recover This guide follows Oracle terminology, whichdistinguishes between restoring and recovering adatabase.Restoremeans to retrieve individual datafiles from

backup media and store the files on disk.Recovermeans to apply theredo logto make the

database consistent.

This usage is unlike NetWorker terminology, whichusesrecoverforalldata retrieval activities (asdistinguished from the UNIXrestorecommand).

8/9/2019 nmsapag_30

17/150




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 Module

NetWorker Client

NetWorker Server

8/9/2019 nmsapag_30

18/150



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

main component of the NetWorker Module is thebackintprogram, 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 thebrbackup,brrestore,brarchive, and otherutilities).

SAP database administration (SAPDBA) utility, a menu-driven interface

to BRTools.

8/9/2019 nmsapag_30

19/150




1

19

Invoking thebrbackupcommand directly or from the SAPDBA BackupDatabase screen passes the following data tobackintfor backup:

Oracle datafiles

Control files

Any existing profiles or specified files

SAP internal catalogs for backup sessions

Invoking thebrarchivecommand directly or from the SAPDBA BackupArchive Logs screen passes the offline redo logs tobackintfor backup.

Oracle RMAN Software Features

The NetWorker Module software supports SAPR/3s use of Oracles 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 Modulesbackint program as the sole

backup and restore tool. If you want to use RMAN to back up Oracle

databases, you must still usebackintto 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 asnapshot

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

8/9/2019 nmsapag_30

20/150



1

Summary of Components and Settings

20

Summary of Components and Settings

This 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 theLegato NetWorker


NetWorker Module Components

Table 2 on page 20lists 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 theinit.utl file.

init.utl Configurationfile

This is the sample configuration file for thebackintprogram and is to be used as a template. Copy thisfile and name itinit.utl, where is the name of the Oracle databaseinstance that is to be backed up. Use the copy andsave the original.

8/9/2019 nmsapag_30

21/150




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 les\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 the

backup command in the NetWorker Clientresource.

nsrsapsv.cfg Configuration

file

The sample configuration file for thensrsapsv

program. Copy the sample template file and savethe original.

nsrsapadm Binaryexecutable

Administrative program fornsrsapsvoperations;encrypts logon information (os_usr_passwdororacle_usr_passwd, depending on authorizationmethod) for the user performing a scheduled

backup.

sapclone Binaryexecutable

The save set cloning program. Provides an interfaceto the NetWorkernsrcloneprogram.

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


8/9/2019 nmsapag_30

22/150



1

NetWorker Client Settings

22

NetWorker Client Settings

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

Administrators Guide.

SAP Components

Table 4 on page 22lists 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 asbackint:. For PowerSnap usage, this attribute must be specified. For all other usage, this attribute is only informational, because

thensrsapsv.cfgfile 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, andbrarchiveprograms(equivalent to NetWorker clientsave,recover,nsrinfo, andmminfoprograms). Invoked bynsrsapsv, SAPDBA, or command line.

SAPDBA Binaryexecutable

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

init.sap Configurationfile

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

8/9/2019 nmsapag_30

23/150




1

23

Oracle Components

Table 5 on page 23lists 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 Binary

executable

Oracle utility for performing backups and restores of

the Oracle database, using therman_parmsparameter.To enable RMAN, set thebackup_dev_typeparameter intheinit.sapfile torman_utl.

rman_parms Parameter Optional parameter in the init.sapfile.Used to specify environment variables for an RMAN

backup or restore with the NetWorker Module.

Table 6. PowerSnap Components Used by the NetWorker Module Software


init.utl ConfigurationFile

Theinit.utl configuration file for thebackint program. The parameters within this file thatare specific to PowerSnap are those with theps_prefix.

nmsapps.cfg(example name)

ConfigurationFile

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

ps_opaque_pfilename Parameter Parameter in theinit.utlfile 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

S f P

8/9/2019 nmsapag_30

24/150



1

Summary of Processes

24

Summary of Processes

The 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, orbrrestorecommands

NetWorker Modulesnsrsapsvcommand, used for scheduled backups

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

Note: PowerSnap backups must be initiated through thensrsapsvscheduledbackup program, and are not supported for manual backups.

Backup with SAPDBA or brbackup

When a backup is initiated from SAPDBA or thebrbackupprogram on theSAP R/3 server running Oracle,brbackupsends a request to thebackintprogram. Thebackintprogram 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 client

file index and media database. The final results of the backup are recorded ina log file,backint.log, on the SAP R/3 server running Oracle.

Figure 2 on page 25shows how the NetWorker services, processes, andprograms interact during a backup.


8/9/2019 nmsapag_30

25/150




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,exceptbrbackupsends requests to both RMAN andbackint. The followingoccurs as a result:

1. RMAN backs up the Oracle datafiles.

2. Thebackintbacks 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

Restore with SAPDBA or brrestore

8/9/2019 nmsapag_30

26/150



1


26


When a restore is initiated from SAPDBA or the brrestore program on the SAPR/3 server running Oracle,brrestoresends a restore request to thebackintprogram. Thebackintprogram browses the NetWorker servers 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 RMANIf 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:

Thebackintprogram

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


8/9/2019 nmsapag_30

27/150




1

27

Related Documentation

For 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 Administrators Guide

appropriate for your implementation Legato NetWorker Administrators Guide appropriate for your

implementation

UNIX man pages

NetWorker Command Reference Guide

Legato Software Compatibility Guide

Related Documentation

8/9/2019 nmsapag_30

28/150



1

28

8/9/2019 nmsapag_30

29/150



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 tobothmanual 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

Task 1: Configure the Environment

8/9/2019 nmsapag_30

30/150



2

30

Task 1: Configure the Environment

Use 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 theLegato NetWorker Module for SAP R/3 with Oracle,Release 3.0, Installation Guide.

2. Set the PATH environment variable for the Oracle user to point to the

location of the NetWorker client executables, which is typically as follows:

On UNIX:/nsr/bin

On Windows:C:\Program Files\Legato\nsr\bin

3. Ensure thebackintexecutable binary file is in the same directory asBRTools. On UNIX, set the owner ofbackint toroot.

4. If you need to restore to raw device files on UNIX, set the uid bit on for the

backintprogram 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 SAPbackup user and select Edit.


8/9/2019 nmsapag_30

31/150



2

31

Task 2: Configure the NetWorker Resources

The NetWorker resources reside on the NetWorker server and are configuredusing the NetWorker Administrator program.

Table 7provides 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 valuemustbe set in theexpirationparameter in theNetWorker Modules parameter file,init.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 NetWorkerModules parameter file,init.utl, see the listing for"group" on page 36.

Pool Specifies the medium volumes in each pool to receive specific backup

data. When configuring the Pool resource, complete the following: Leave the Save Sets attribute blank; the NetWorker Module program

sets this attribute during each backup session. Once a pool is created, specify its name in the NetWorker Modules

parameter file,init.utl.

Task 2: Configure the NetWorker Resources

8/9/2019 nmsapag_30

32/150



2

32

For more information on configuring the NetWorker resources, refer to theNetWorker Online Help or theLegato NetWorker Administrators 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 Modulesparameter file,init.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 attribute

is 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


8/9/2019 nmsapag_30

33/150



2

33

Task 3: Configure the NetWorker Module Parameters

During backup, restore, or inquire sessions, the NetWorker Module programuses the parameter settings specified (or the default values if not specified)from theinit.utlparameter file. These parameter settingsprovide client, server, pool, group, expiration and other values to thebackintprogram.

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 theinit.utlparameter 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.

8/9/2019 nmsapag_30

34/150

8/9/2019 nmsapag_30

35/150


8/9/2019 nmsapag_30

36/150



2

36

encrypt No Specifies whether to encrypt the backup data.

Setting this parameter to Yes excludes the use ofcompress and checksum parameters, which should

be 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 doesnot

override the NetWorker server-side Clientresource settingsunlessit specifies a longer

period of time.

The value must usensr_getdate format, forexample:

expiration =2 Weeks

group Default Specifies the backup Group resource that is usedby the NetWorkersaveprogram. 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 thebackint log file. If the valueis set to 0,allbackup logs will be saved in the logfile. See also the "backint_log"parameter on page34.

Table 8. Parameters for the NetWorker Module init.utl File (Part 3 of 8)

Parameter Default Description


8/9/2019 nmsapag_30

37/150



2

37

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

notify_done = mailx-s backint doneroot

notify_error Not specified UNIX only. Executed at the completion of afailedbackup or restore session. Uncomment the optionand replacemailxwith the name of the commandline e-mail utility to be used as an alert if thebackintprogram encounters any errors during its

activity, for example:

notify_error = mailx-s backint errorroot

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

notify_start = mailx-s backint startroot

notify_success Not specified UNIX only. Executed at the completion of asuccessfulbackup or restore session. Uncommentthe option and replacemailxwith the name of the

command line e-mail utility to be used as an alertwhen thebackintprogram has successfullycompleted its activity, for example:

notify_success = mailx-s backintsuccess root




8/9/2019 nmsapag_30

38/150



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 to

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




8/9/2019 nmsapag_30

39/150



2

39

pool Default Specifies the NetWorker media Pool resource,(defined in the NetWorker server), that receives

backup 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, uncomment

this parameter and set it equal to the name of thepool, for example:

pool = SAPData

To use multiple pools to separate data:1. Create separateinit.utl

parameter files.2. Use the-roption to specify the parameter

filename to use at the command line whenusingbrbackuporbrarchive.

For example, a pool namedARCHDatais usedspecifically for archive logs. You can create aseparate parameter file for archive logs, named forexamplearchiveC11.utl, and set the pool attributeequal toARCHData. To use this pool to back up the

archive 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 to

No.

query_index No UNIX only (Windows is always Yes). Specifieswhether to query the NetWorker server indexes forvalidation of the requested files and backup IDs

before a restore begins. If set to No, the query doesnotoccur.




8/9/2019 nmsapag_30

40/150



2

40

raw_dir Not specified Specifies the directory for raw disk partitions. Anyfiles below these directories are considered to beraw disk partitions. Donotset the/devor/devicesdirectories for raw partitions. They are alreadytreated as raw devices. To specify the directory,uncomment this option, and use a semicolon (;) to

separate the directory paths, for example:raw_dir =/oracle/data;/sap/data;/lotus/data

retry_count 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 clients files can be

divided 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 thess_group_by_fsparameter is set to Yes.

sem_timeout 30 Sets the amount of time, in minutes, thatbackintwaits forbrbackuporbrconnectto remove thesemaphore file. If the semaphore file isnot deleted,backintexits with an error at the end of thistimeout period.

server Local Host The hostname of the NetWorker server that the

NetWorker 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 isnotspecified,then the NetWorker Module backs up data to the

local host.



8/9/2019 nmsapag_30

41/150

Task 4: Configure the Backup and Restore Utility

8/9/2019 nmsapag_30

42/150



2

42

Task 4: Configure the Backup and Restore Utility

Depending 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 Oracles 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 the

Backup and Restore Utility" on page 43.

Example: Configuring backint as the Backup and Restore Utility

The following example describes a simple configuration of BRTools(specifically the SAPDBA interface and thebrbackup,brarchive, andbrrestorecommands) to use thebackintprogram for backup, restore, andinquiry operations. For complete instructions, refer to the appropriate SAPdocumentation.

1. With a text editor, open the SAP initialization file, init.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_ le

backup_dev_type = util_file_online

3. Set theutil_par_ leparameter to point to the NetWorker Modulesparameter file,init.utl,as follows:

On UNIX or Linux:

#backup utility parameter file

util_par_file = ?/dbs/init.utl

where ?= $ORACLE_HOME


8/9/2019 nmsapag_30

43/150



2

43

On Microsoft Windows:

#backup utility parameter file

util_par_file = ?\database\init.utl

where ?= %ORACLE_HOME%

For details on the NetWorker Module parameter file, see"Task 3: Con gurethe NetWorker Module Parameters" on page 33.

Example: Configuring RMAN as the Backup and Restore Utility

The following example describes a simple configuration of Oracles 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.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 therman_parmsparameter 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 following

syntax:rman_parms="ENV=(=, =, ...)"

For example:

rman_parms="ENV=(NSR_SERVER=server_name,NSR_DATA_VOLUME_POOL=pool_name)"

8/9/2019 nmsapag_30

44/150

8/9/2019 nmsapag_30

45/150



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 Backups

You can use the following to perform manual backups:

The SAPDBA menu interface

Thebrbackuporbrarchivecommand

Oracles RMAN utility, invoked through either SAPDBA or the brbackuporbrarchivecommand

Each of these methods uses the NetWorker Modulesbackintprogram.

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

Performing an Offline Manual Backup

8/9/2019 nmsapag_30

46/150



3

46

Important: Manual backups donotautomatically back up the NetWorkerservers client le 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 Backup

Perform 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 Modulesinit.utlfile. For details on configuring backupparameters, see "Task 3: Configure the NetWorker Module Parameters"on page 33.

The parameters for thebackup device type(backup_dev_type)and backuputility parameter file (util_par_file) are set in the SAP utilities profile,init.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 thebrbackuporbrarchivecommand, refer to the appropriate SAPdocumentation.

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


Th f ll i i l f ffli b k i th b b k

8/9/2019 nmsapag_30

47/150



3

47

The following is an example of an offline backup using thebrbackupcommand:

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 offl ine option specifies that the backup type is offline.

The (optional)-d util_ leoption specifies that the NetWorker

Module is to be used for the backup. For more information on the availablebrbackupcommand options,see "Appendix A: Commonly Used Command Options for brbackup,

brarchive, and brrestore" on page 109.

With thisbrbackup command, the Oracle database instance is backed upto the NetWorker server.

2. Back up the client file indexes and bootstrap. For instructions, see "Backing

Up the Client File Indexes and Bootstrap" on page 49.

Performing an Online Manual Backup

An online backup allows users to continue using SAP R/3 services and Oracledatabase instances while the Oracle tablespaces on the SAP R/3 server are

being backed up.

Before you begin an online backup, ensure the following:

The backup parameters are set in the NetWorker Modulesinit.utlfile. 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 utilities

profile,init.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 inARCHIVELOG mode. To set an Oracledatabase instance to ARCHIVELOG mode, refer to the appropriateOracle manual.

Performing an Online Manual Backup

How to Perform an Online Backup

8/9/2019 nmsapag_30

48/150



3

48

How to Perform an Online Backup

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

following:

To perform an online backup using the SAPDBA menu interface or thebrbackuporbrarchivecommand, 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 thebrbackupcommand:

1. Enter the following command:

brbackup -m backup_objects-t online [-d util_file_online]

The-mbackup_objectsoption specifies the objects to be backed up,wherebackup_objectsis 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_ le_onlineoption specifies that theNetWorker Module is to be used for the online backup.

For more information on the availablebrbackupcommand options,see "Appendix A: Commonly Used Command Options for brbackup,


With thisbrbackupcommand, 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 availablebrarchive command options, see"Appendix A: Commonly Used Command Options for brbackup,


Note: Archive redo logs are required for an online backup. Without redo

logs, you can recover a database only to the time of its last full backup.

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


Backing Up the Client File Indexes and Bootstrap

8/9/2019 nmsapag_30

49/150



3

49

Backing Up the Client File Indexes and Bootstrap

Unlike scheduled backups, manual backups donot automatically back up theclient file indexes and the NetWorker servers 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 disk

failure.

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 inboththeNetWorker Administrator program and theinit.utlfile.

(A Group resource can be created even for a single client.) This ensuresthat browse and retention policies are applied to the client file indexeswhen thesavegrp command is entered in step 2.

For more information on how to configure a Group resource with theNetWorker Administrator program, refer to theLegato NetWorker

Administrators Guide.

Note: If the client isnotincluded in a Group resource, you must perform

step 3as an additional step to manually run thensrimcommand.

2. On the NetWorker server, log in as the root user (UNIX) or administrator(Windows), and enter the followingsavegrpcommand:

savegrp -O -c client_name

where:

-Osaves the clients index files and the associated NetWorker

servers bootstrapwithoutbacking up the clients database files. -cclient_name specifies the hostname of the SAP R/3 server running

Oracle whose index files are to be backed up.

For more information on thesavegrpcommand, refer to theLegatoNetWorker Command Reference Guide.

Reviewing Backup Session Reports

3. If the client is not included in a Group resource (see step 1), apply browse

8/9/2019 nmsapag_30

50/150



3

50

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

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 thensrim command, refer to theLegatoNetWorker 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 can

be made verbose by setting the verbose parameter. See "verbose" on page 41.

Most NetWorker

Documents

nmsapag_30