Quest NetVault Backup Plug-in for SAP R/3 Backint

Transcription

1 Quest NetVault Backup Plug-in for SAP R/3 Backint version 5.0 User s Guide SBG EN-01 11/30/11

2 2011 Quest Software, Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser s personal use without the written permission of Quest Software, Inc. Disclaimer The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document. If you have any questions regarding your potential use of this material, contact: Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA legal@quest.com For regional and international office information, refer to the web site ( Trademarks Quest, Quest Software, the Quest Software logo, and NetVault are trademarks and registered trademarks of Quest Software, Inc. in the United States of America and other countries. For a complete list of Quest Software s trademarks, see Other trademarks and registered trademarks are property of their respective owners. Patents This product is protected by U.S. Patents # 7,814,260; 7,913,043; and 7,979,650. Protected by Japanese, E.U., French, and UK patents and , and German patent DE Additional patents pending.

3 Table of Contents Chapter 1: Introducing Quest NetVault Backup Plug-in for SAP R/3 Backint 5 Quest NetVault Backup Plug-in for SAP R/3 Backint At a Glance... 5 Target Audience... 6 About Quest Software Contacting Quest Software Quest Support... 6 Chapter 2: Installing and Removing Plug-in for SAP R/3 Backint 7 Installation Prerequisites Establishing the Proper Tape Format... 8 Reviewing the Recommended Configuration Installing Plug-in for SAP R/3 Backint Removing the Plug-in for SAP R/3 Backint Chapter 3: Configuring the Plug-in for SAP R/3 Backint 15 Configuring the Plug-in Chapter 4: Backing Up Data 19 Backing Up Data Backing Up Data from a Different OS Chapter 5: Restoring Data 23 Restoring Data An Overview Viewing Backed Up Data in the NVBU Console... 23

4 4 Table of Contents Restoring to a Different Target Machine...24 Appendix A: Issuing SAP R/3 Backint Commands 27 Commands An Overview...27 Issuing Commands...27 Accessing Help...28 Command Table...28 Parameter Table Important Notes Input Variables...32 Output Variables...33 Appendix B: Troubleshooting 35 Troubleshooting...35

5 Quest NetVault Backup Plug-in for SAP R/3 Backint User s Guide 5 Chapter 2: INTRODUCING QUEST NETVAULT BACKUP PLUG-IN FOR SAP R/3 BACKINT Quest NetVault Backup Plug-in for SAP R/3 Backint At a Glance Target Audience About Quest Software Contacting Quest Software Quest Support Quest NetVault Backup Plug-in for SAP R/3 Backint At a Glance The Quest NetVault Backup (NVBU) Plug-in for SAP R/3 Backint (Plug-in for SAP R/3 Backint) increases application availability by providing fast, online backup of SAP R/3 databases in Linux/UNIX- and Windows-based environments. This plug-in supports such important features as hot backup, integration with SAP R/3 tools, parallel backup support, and selectable backup operations. The following storage-management facilities are available with the Plug-in for SAP R/3 Backint: Hot Backup With the Plug-in for SAP R/3 Backint used in conjunction with SAP R/3 tools, user databases remain online and fully accessible during backup operations, which minimizes downtime for users. Seamless Integration into SAP R/3 tools The Plug-in for SAP R/3 Backint seamlessly integrates with existing SAP R/3 tools, which lets you execute backups directly from SAP R/3. Supports Raw Data Backup In UNIX environments, you can back up raw data, including device, buffered files, and pipes. Command Line Interface You can submit jobs using a console or command line interface. Most of the extensive features provided by NVBU backup jobs are supported when using SAP R/3 Backint command line options and parameter files. Parallel Backup Support You can split backups into multiple jobs for parallel execution and load balancing.

6 6 Chapter 2 Introducing Quest NetVault Backup Plug-in for SAP R/3 Backint Selectable Backup Operations With the Plug-in for SAP R/3 Backint, you can back up only what is needed. Using a command line interface, you can specify individual files and directories, or back up an entire system Target Audience The majority of operations used with the Plug-in for SAP R/3 Backint require SAP R/3 Backint administrator skills, including the initial configuration and backup and recovery operations About Quest Software Quest Software simplifies and reduces the cost of managing IT for more than 100,000 customers worldwide. Quest s innovative solutions make solving the toughest IT management problems easier, enabling customers to save time and money across physical, virtual, and cloud environments. For more information about Quest, go to Contacting Quest Software Mail: Web site: info@quest.com Quest Software, Inc. World Headquarter 5 Polaris Way Aliso Viejo, CA USA For regional and international office information, refer to the web site Quest Support Quest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to SupportLink, Quest Support s self-service portal. Visit SupportLink at From SupportLink, you can: Retrieve thousands of solutions from the online Knowledge Base. Download the latest releases and service packs. Create, update, and review support cases. For a detailed explanation of support programs, online services, contact information, policies. and procedures, view the Global Support Guide. This guide is available at:

7 Quest NetVault Backup Plug-in for SAP R/3 Backint User s Guide 7 Chapter 3: INSTALLING AND REMOVING PLUG-IN FOR SAP R/3 BACKINT Installation Prerequisites Establishing the Proper Tape Format Reviewing the Recommended Configuration Installing Plug-in for SAP R/3 Backint Removing the Plug-in for SAP R/3 Backint Installation Prerequisites Before installing the Plug-in for SAP R/3 Backint, make sure that the following software is installed and configured: NVBU Server/Client Software At a minimum, the Client version of NVBU software must be installed on the machine hosting the SAP Backint R/3 database. For an example of a suitable environment, see Reviewing the Recommended Configuration on page 12. SAP R/3 Backint Software This database software must be installed and properly configured on the machine serving as the SAP R/3 Backint server. Client added to the NVBU Server for access If the machine that hosts the targeted SAP R/3 Backint database is not the NVBU Server, this machine must be added to the NVBU Server as an NVBU Client. For more information, refer to the Quest NetVault Backup Administrator s Guide. Homogeneous tape-format requirement This issue potentially affects those using the Plug-in for SAP R/3 Backint to back up clients that use various operating systems (OSs); for example, a UNIX-based NVBU Server with Windows-based NVBU Clients, a Windows-based client backed up to a device attached to another NVBU Client that is running UNIX, and so on. By default, media contained in a drive controlled by an NVBU machine will be established with the tape format required by that machine s OS (that is, UNIXbased would be CPIO, while a Windows-based machine would be MTF). When using the Plug-in for SAP R/3 Backint, the tape format of the target backup media must match the prevalent tape format for each particular OS. Specifically, a CPIO tape format must be used to perform a Plug-in for

8 8 Chapter 3 Installing and Removing Plug-in for SAP R/3 Backint SAP R/3 Backint backup of a UNIX-based NVBU Client, and an MTF tape format must be used with a Windows-based Client. For details on verifying and setting the proper tape format, see Establishing the Proper Tape Format on page 8. If the tape format of the media does not match the tape format of the OS as described earlier, issues will occur depending on the version of the plug-in used: Plug-in for SAP R/3 Backint v2.x The backup of the target client will report successful completion. However, when a restore is initiated, it will fail. Plug-in for SAP R/3 Backint 3.x This version of the plug-in will fail at the time of backup, and report the failure Establishing the Proper Tape Format If an NVBU Client that is to serve as a backup/restore target for the plug-in is running an OS that differs from the machine that is administering the backup device, the proper media format must be established. The following sections illustrate the steps required to accomplish this a Figure 3-1: Tape format for selected media Phase 1: Determining the Tape Format in Use To determine the tape format in use for an available piece of backup media, perform the following steps: 1. Determine the required media format for the target backup client: Client running Linux/UNIX-based OS CPIO tape format Client running Windows-based OS MTF tape format 2. From the NVBU Console running on the NVBU Server, open the NVBU Media Management window (via either of the toolbar buttons or by clicking Administration > Media Management). 3. In the Media list, locate the applicable piece of media, right-click it, and select Properties from the pop-up menu. The Tape Format field on the Media Properties dialog displays the format of the media in use.

9 Quest NetVault Backup Plug-in for SAP R/3 Backint User s Guide 9 4. Do one of the following: If the total amount of data selected for a backup will require more than one piece of media, you must set up a Media Group that contains enough media to accommodate the backup. Continue to the next section, Phase 2: Setting Up the Proper Media. If a selected piece of media exists that matches the required format for the target NVBU Client (that is, CPIO for Linux/UNIX-based clients or MTF for Windows-based clients), note its applicable Media Label information. This will be required when generating the backup job. If no media exists with the required OS-specific formatting, you must either use new media and establish the correct format, or blank, re-label, and reset the format of existing media. If so, continue to the next section, Phase 2: Setting Up the Proper Media b Phase 2: Setting Up the Proper Media If no media matching the required format was found or a larger amount of media of a different format is required for a backup, Quest Software recommends that you create a new Media Group. After it is created, you can set up a Target Set that includes this Media Group, and set it as the target of a backup job. To create a Media Group that contains the applicable format of media, perform the following steps: 1. From the library device that is to serve as the target of the backup, ensure that media is available, and complete the following: Using new media Remove any existing media, and replace it with the new media. Reusing existing media Ensure that any media that is to be reused does not contain any necessary backup data. If it does, remove it, and replace it with media that is either new or that can be safely reused 2. From the NVBU Console running on the NVBU Server, open the NVBU Device Management window (via either of the toolbar buttons or by clicking Administration > Device Management). The Devices tab lists the various devices that have been previously added for use. 3. On the Devices tab, which lists the various devices that have been previously added for use, locate the library that contains the media to be used. 4. On the selected library, locate a piece of media that you want to include in the Media Group, and then perform one of the following: Reusing media Right-click the piece of media, and select Blank from the pop-up menu. When the confirmation dialog appears, click OK to continue. The media will be processed and labelled as BLANK.

10 10 Chapter 3 Installing and Removing Plug-in for SAP R/3 Backint Figure 3-2: Media Properties dialog Using new media Continue to Step Right-click the piece of media, and select Properties from the pop-up menu. 6. On the Media Properties dialog, enter the applicable information: Media Label Quest Software recommends that you select the barcode value from the list. However, you can select a different label or manually enter one of your own. A label can contain alphanumeric and nonalphanumeric characters, but it cannot include non-english characters. Group Label Enter a name to establish a new group specific to this media. To facilitate recognition, Quest Software strongly recommends that you include the tape format in the name. Note: A media or group label can contain alphanumeric and nonalphnumeric characters, but it cannot include non-english characters. These labels are caseinsensitive (NVBU does not distinguish between upper- and lowercase letters). Additionally, there is no restriction on length. However, the combined display range for the labels is 100 characters. Tape Format Select the applicable tape format. The format selected should match the OS on the machine that is to serve as a Plug-in for SAP R/3 Backint backup target (that is, CPIO for Linux/UNIX-based Clients and MTF for Windows-based Clients). 7. To apply these changes, click OK. 8. On the selected library in the Devices tab, locate the next piece of media to include in the group, and then perform one of the following: Reusing media Right-click the piece of media, and select Blank from the pop-up menu. When the confirmation dialog appears, click OK to continue. The media will be processed and labelled as BLANK. Using New Media Continue to Step Right-click the piece of media, and select Properties from the pop-up menu.

11 Quest NetVault Backup Plug-in for SAP R/3 Backint User s Guide 11 Figure 3-3: Virtual library device on Windowsbased NVBU Server with its media format changed and allocated to media group 10.On the Media Properties dialog, enter the applicable information: Media Label Quest Software recommends that you select the barcode value from the list. However, you can select a different label, or manually enter one of your own. Group Label Select the Group Label created in Step 6. Tape Format Select the same tape format selected for the previous piece of media (as outlined in Step 6). 11.To apply these changes, click OK. 12.Repeat Step 8 through Step 11 for each additional piece of media that is to be included in the Media Group. Important: If you are using a standalone drive as a target for backups, you can follow this same procedure to establish the proper tape format. However, you only need to complete Step 1 through Step 7, and you can ignore references to Group Label. After you are finished, note the Media Label assigned to the media in use in the drive.

12 12 Chapter 3 Installing and Removing Plug-in for SAP R/3 Backint Reviewing the Recommended Configuration While you can set up a single machine as both the NVBU Server and the SAP R/3 Backint server (that is, all software installation and configuration requirements are performed on a single machine), Quest Software recommends that these two entities exist on separate machines. The following table displays an ideal set up for use with the Plug-in for SAP R/3 Backint, including the software and configuration requirements to establish this type of environment. Network Connection SAP R/3 Backint Server Machine Software Installed/Configuration SAP R/3 Backint software NVBU Server/Client software Plug-in for SAP R/3 Backint NVBU Server Machine Software Installed/Configuration NVBU Server software Plug-in for SAP R/3 Backint SAP R/3 Backint Server added as an NVBU Client (For details on adding a Client machine to the NVBU Server, refer to the Quest NetVault Backup Administrator s Guide.) Media format established The proper tape format to accommodate NVBU Clients running a different OS (if applicable). Important: Sample images and procedures throughout this guide assume that this two-machine environment is in place and all configuration requirements have been met.

13 Quest NetVault Backup Plug-in for SAP R/3 Backint User s Guide Installing Plug-in for SAP R/3 Backint Figure 3-4: Install Software selected To install the Plug-in for SAP R/3 Backint, perform the following steps. 1. From the NVBU Console running on the NVBU Server, open the NVBU Client Management window (via either of the toolbar buttons or by clicking Administration > Client Management). 2. On the Clients tab, locate the machine that contains the SAP R/3 Backint database, right-click it, and select Install Software from the pop-up menu. 3. On the dialog that appears, navigate to the location of the.npk installation file for the Plug-in for SAP R/3 Backint (for example, the Quest NetVault Backup Plug-in Installation CD or the directory to which the file was downloaded from Quest Software s web site). Based on the operating system (OS) in use, the path for this software may vary on the installation CD. 4. Select the file entitled bkixxxx.npk (where xxxx represents the platform and version number), and click Open. The installation process will occur automatically. 5. When the Install Software dialog appears that indicates the software was successfully installed, click OK to dismiss it.

14 14 Chapter 3 Installing and Removing Plug-in for SAP R/3 Backint Important: The Plug-in for SAP R/3 Backint must exist on the NVBU Server, regardless of the configuration in use. Therefore, if you are using a single machine configuration, installation is complete. If you are using the recommended Client-Server configuration, you must repeat the installation process, this time installing the plug-in on the NVBU Server. The plug-in installation file is dependent on the OS in use. The same installation file cannot be used for different OSs. Therefore, if you are using the recommended configuration and the NVBU Server and SAP R/3 Backint server are each running a different OS, the proper installation files must be obtained and used (that is, from the plug-in installation CD or from Quest Software s web site) Removing the Plug-in for SAP R/3 Backint Figure 3-5: Remove Software dialog To remove the plug-in, perform the following steps. 1. From the NVBU Console running on the NVBU Server, open the NVBU Client Management window (via either of the toolbar buttons or by clicking Administration > Client Management). 2. On the Clients tab, right-click the machine that houses the Plug-in for SAP R/ 3 Backint, and select Remove Software from the pop-up menu. 3. On the Remove Software dialog, select the Plug-in for SAP R/3 Backint item, and click Remove. 4. When the next Remove Software dialog appears, click OK to proceed (or Cancel to abort). 5. When the confirmation message appears that indicates the software was removed, click OK to close the dialog and return to the NVBU Client Management window.

15 Quest NetVault Backup Plug-in for SAP R/3 Backint User s Guide 15 Chapter 4: CONFIGURING THE PLUG-IN FOR SAP R/3 BACKINT Configuring the Plug-in Configuring the Plug-in Figure 4-1: Select Configure Before the plug-in can be used, certain configuration settings must be applied, including the name of the NVBU Server that performs the backup. To set these options, perform the following steps: 1. From the NVBU Console running on the NVBU Server, open the NVBU Backup window (via either of the toolbar buttons or by clicking Operations > Backup). A list of NVBU Clients is displayed on the Selections tab. 2. Locate the NVBU Client that contains the Plug-in for SAP R/3 Backint, and open it to display a list of plug-ins installed on the machine. To open any node on the Selections tab, do either of the following: Double-click the node. Right-click the node, and select Open from the pop-up menu. 3. Locate Plug-in for SAP R/3 Backint (that is, the item entitled Backint ) in the list, right-click it, and select Configure from the pop-up menu.

16 16 Chapter 4 Configuring the Plug-in for SAP R/3 Backint Figure 4-2: Configure dialog The Configure dialog appears. 4. Complete the applicable fields: Server name Enter the name of the NVBU Server in this field. This is the NVBU name for the server with device control that will be used to process backups. Job Start Timeout (secs) Specify the time, in seconds, that NVBU should wait before abandoning its attempts to connect to the NVBU Server. Backup directory contents By default, if a directory name is specified instead of a file, the directory contents are not backed up. If you want the files in the specified directory included in the backup, select this check box. Important: Even if this option is selected, subdirectories contained in the directory specified will not be backed up. To back up subdirectories, include the -r switch at the command line when initiating a backup. Split backup sub-jobs by volume To group jobs that back up files from more than one volume into volume-based subjobs, select this check box. Use network compression To compress data prior to transmitting it over a network, select this check box. When the data reaches its destination, it will be decompressed.

17 Quest NetVault Backup Plug-in for SAP R/3 Backint User s Guide 17 Important: With this option selected, backups might take longer to complete. Mass open for File-online To open all files for backup simultaneously, select this check box. When you initiate a backup at the command line, include the -t switch for the file_online command. Backup sub-job count Enter the maximum number of subjobs that any given job can have. NVBU will size the subjobs equally. For example, if the data being backed up is 5 gigabytes (GB) and the Backup subjob count is 10, each subjob would be approximately 500 megabytes (MB). Important: This option functions only if the Split backup sub-jobs by volume option is cleared. Maximum restore sub-jobs Use this option to specify the maximum number of subjobs (usually running off separate media) that a restore job is allowed to use. If set to 1, a backup spanning multiple pieces of media can only be restored from each item of media in turn. Restore to overwrite newer files If you need to overwrite existing files that have a more recent modification date, select this check box. Important: If this option is not selected and older files exist in the backup data, NVBU will note errors in the NVBU Logs during a restore and the restore might fail. Restore to create backup of existing files To create a backup copy of an existing file with a different extension prior to completing a restore, select this check box. Important: By default, a restore does not back up existing files before overwriting them. Therefore, without this item selected, existing files are overwritten. Restore to restore original timestamps If you want the timestamps on restored data reset to what they were when the files were backed up, select this check box. Default Parameter File Enter the path to the applicable SAP Backint R/3 parameter file that will be used as a reference point for commands issued from a terminal session (that is, for backup and restore operations). Important: For more information on the use of parameter files, refer to the relevant SAP R/3 Backint documentation. If a Backint command is issued from a terminal prompt using the -p <par_file> argument, the parameter file specified as the <par_file> will be used instead of the file entered in the Default Parameter File field.

18 18 Chapter 4 Configuring the Plug-in for SAP R/3 Backint

19 Quest NetVault Backup Plug-in for SAP R/3 Backint User s Guide 19 Chapter 5: BACKING UP DATA Backing Up Data Backing Up Data from a Different OS Backing Up Data Backing up SAP R/3 Backint database information is performed via a terminal session; it is not performed using the NVBU Console. To back up data, perform the following steps: 1. Start the Plug-in for SAP R/3 Backint by running the backint binary file on each machine on which the plug-in is installed. This file is located in the following directory (where... represents the path to the installation of NVBU):.../netvault/bin/backint Important: If necessary, review the relevant OS-related documentation for details on running a binary file. 2. To continue the backup process, use one of the following methods: Issue individual commands from a terminal session This method provides the most control, as individual commands are issued for each step of the backup process. Use this type of backup to perform immediate backups of specified data. Generate a script file Create a script file that contains the applicable commands for a complete backup procedure, and then run the script as required. This works well for scheduling backups to occur later or for multiple backups that require the same series of commands. Important: For more information on the commands available for use with this plug-in, see Issuing SAP R/3 Backint Commands on page 27. This document does not provide instructions on how to generate a backup script file. Quest Software recommends that you only use generated-script backups if you have experience in generating scripts for the environment that you are using. 3. After you have initiated a backup job from a terminal session, monitor the backup job progress and log entries via the NVBU Jobs and NVBU Logs windows.

20 20 Chapter 5 Backing Up Data For details on accessing these windows and their use, refer to the Quest NetVault Backup Administrator s Guide Backing Up Data from a Different OS Figure 5-1: MID option As noted earlier, if a targeted client is running an OS different from the machine administering the targeted backup device, the tape format must match what is supported for the client system s OS. Prior to conducting a backup, make sure that you have completed the steps outlined in Establishing the Proper Tape Format on page 8. Because backups are conducted via commands issued from a terminal session, you must create a Target Set that calls the Media Group that you created and then save the Target Set on the NVBU Server. When you execute a backup, you will call this Target Set. To create the Target Set, perform the following steps: 1. From the NVBU Console running on the NVBU Server, open the NVBU Backup window (via either of the toolbar buttons or by clicking Operations > Backup). 2. In the NVBU Backup window, select the Target tab. 3. In the Media Options section, select the applicable options: MID If a piece of media existed in the target device that met the tapeformat requirement or if you are using a standalone tape device, select this option, and then select the required piece of media based on its Media Label. Figure 5-2: Group Label option Group Label If a Group Label was established, select this option, and then select the group that you created.

21 Quest NetVault Backup Plug-in for SAP R/3 Backint User s Guide At the bottom of the Target tab, click Save As. 5. On the Save Backup Target Set dialog, enter an applicable name for this set in the first text field. Important: Ensure that the name used is in a format that will be supported for entry from a terminal session on the OS in use (for example, use short names and use underscores _ in place of spaces). Quest Software also strongly recommends that you specify a name that is easy to remember. Figure 5-3: Name displayed 6. To save your changes and return to the Target tab, click OK. The set is created and saved, and the name appears in the Target Set field. (Make note of this name for later use.)

22 22 Chapter 5 Backing Up Data

23 Quest NetVault Backup Plug-in for SAP R/3 Backint User s Guide 23 Chapter 6: RESTORING DATA Restoring Data An Overview Viewing Backed Up Data in the NVBU Console Restoring to a Different Target Machine Restoring Data An Overview In the same manner as a backup, restore operations are controlled through the use of commands issued from a terminal session. For more information, see Backing Up Data on page Viewing Backed Up Data in the NVBU Console Unlike the backup process, the restore process lets you use the NVBU Console to view data that was backed up. Although you cannot select items and launch a restore job, you can browse and examine what was included in a backup. To view data, perform the following steps: 1. From the NVBU Console, launch the NVBU Restore window (via either of the toolbar buttons or by clicking Operations > Restore). A list of NVBU Clients that have been the target of successful backup jobs is displayed on the Selections tab. 2. Locate the NVBU Client that is configured as the SAP R/3 Backint Server, and open it to display a list of the plug-ins that have been used to back up data. To open any node on the Selections tab, do either of the following: Double-click the node. Right-click the node, and select Open from the pop-up menu. 3. Locate the Plug-in for SAP R/3 Backint in the list (that is, the one entitled Backint ), and open it to display the backup savesets created with the plugin. Each saveset is labeled with its given Job Title followed by its backup type and the time that the backup was performed.

24 24 Chapter 6 Restoring Data Figure 6-1: Backup saveset opened for browsing 4. Open the applicable backup saveset to reveal its contents. 5. For use in the restore process from the terminal session, note the names of the database files that were included in the backup Restoring to a Different Target Machine The Plug-in for SAP R/3 Backint lets you restore backed up data to a different NVBU Client (that is, another SAP R/3 Backint machine). To accomplish this, perform the following steps: 1. Make sure that the following prerequisites are met: NVBU ver. 7.1.x (or later) and the Plug-in for SAP R/3 Backint ver. 3.1 (or later) are installed At a minimum, these versions of software must be installed on the SAP R/3 Backint Server and the intended relocation client (the new target). Important: This functionality is only supported for backups performed with version 3.1 (or later) of the Plug-in for SAP R/3 Backint. Partition structure and/or directory layout duplicated The partition structure established as the SAP R/3 Backint specification on the original backup target must be duplicated on the new target. If you intend to

25 Quest NetVault Backup Plug-in for SAP R/3 Backint User s Guide 25 restore data to a different directory structure, you can use the -i <in_file> argument. New target added as an NVBU Client You must add the new target machine to the NVBU Server as an NVBU Client. For more information, refer to the Quest NetVault Backup Administrator s Guide. 2. Use a terminal session to restore the data, and include the Target client <target client name> argument in the restore request s syntax. For example, if you were restoring data from an original backup of an NVBU Client entitled SAP_Client_1 to an NVBU Client named SAP_Client_2, you would include the following syntax along with the other restore commands in the -p command: Target client SAP_Client_2 Important: As noted earlier, additional syntax is required along with the -p command to initiate a restore request successfully. For more information, see Issuing SAP R/3 Backint Commands on page 27.

26 26 Chapter 6 Restoring Data

27 Quest NetVault Backup Plug-in for SAP R/3 Backint User s Guide 27 Appendix A: ISSUING SAP R/3 BACKINT COMMANDS Commands An Overview Issuing Commands Accessing Help Command Table Parameter Table Important Notes Input Variables Output Variables A.1.0 Commands An Overview This section offers brief instructions on how to issue basic Plug-in for SAP R/3 Backint commands from a terminal prompt to perform backup and restore operations. It also includes tables that provide details on the various commands that are available for use, as well as the parameters and variables that can accompany the commands. A.2.0 Issuing Commands To issue commands, perform the following steps: 1. Based on the operation to be performed (backup versus restore), make sure that all prerequisites have been met (for more information, see Backing Up Data on page 19 and Restoring Data on page 23). 2. From the NVBU Server, initiate a terminal session. 3. Preface all commands used to initiate SAP R/3 Backint backup and restore operations with the backint command. 4. Follow this with the applicable commands, based on the operation that you are performing, and include the function, any desired parameters, and the names of the input, output, and job title. For more information, see the subsequent tables. 5. With all desired values input, press the Enter key to start the job.

28 28 Appendix A Issuing SAP R/3 Backint Commands A.3.0 Accessing Help To access the help system from a terminal-session prompt, perform the following steps: 1. Navigate to the...netvault/bin directory. 2. Issue one of the following commands: backint -? backint --help Figure A-1: Example of help system offered from terminal session prompt A.4.0 Command Table The following table describes the commands available for use with the Plug-in for SAP R/3 Backint. Command Description Default/No entry -u <user_id> Backup utility user. To attach a user ID to a backup, use this option with the backup operation. When you use this option with inquire or restore operations, only the contents of backups made with an identical ID (or no ID) are listed or restored. No user ID

29 Quest NetVault Backup Plug-in for SAP R/3 Backint User s Guide 29 Command Description Default/No entry -t <type> Backup type (file, file_online). Backint requests permission to start each file, and informs SAP when each file is completed. This enables SAP to switch the tablespace to BEGIN/END BACKUP mode only when the backup of the related files takes place. file No such interactive mode occurs between NVBU and SAP. file_online Used only for online backups. -f <function> Type or operation (backup, restore, inquire). backup Defines a backup request, including all the files specified in a list. Backint will indicate which files have, or have not, been backed up successfully. restore Requests that a list of files, specified in a list, are restored. Backint will indicate which files have, or have not, been successfully restored. inquire Provides information on what files exist in the backup, and in which savesets they are located. -p <par_file> Name of the file that contains the parameters that determine the backup procedure. For a description of the available options, see Parameter Table on page 30. -i <in_file> Path name of the file that defines the objects of the function (backup, restore, or inquire). If this parameter is not set, data is read from the standard input. -o <out_file> Path name of the file where Backint will write the result of the function (backup, restore, or inquire). If this parameter is not set, the messages are written to standard output. file backup Default parameter file (if specified in the Default Parameter File field of the Configure dialog for this plug-in; for more information, see Configuring the Plug-in for SAP R/ 3 Backint on page 15). STDIN STDOUT

30 30 Appendix A Issuing SAP R/3 Backint Commands Command Description Default/No entry -T <title> The Job Title given to the NVBU backup or restore job. Command line backup/restore -r Recurse directories. FALSE -c Unattended mode (no interaction possible). Attended mode A.5.0 Parameter Table The following table describes options that you can use in conjunction with an SAP R/3 Backint parameter file. These options are used with the -p argument in the command syntax, and can be used in either of the following ways: With the -p <par_file> command (where <par_file> represents the applicable parameter file name) In this case, you can use a parameter file other than the default. With the -p command alone (without naming a parameter file) In this case, the default parameter file specified in the Configure dialog is used. The following table lists the available options, valid entries, and default values used. Important: The equal sign (=) is the only valid separator that you can use with values in a parameter file (for example, -p client = Client1 ). This applies to both the manual entry of the -p command from a terminal session and in an existing parameter file (that is, one called out via the -p <parameter file name> command or the one established as the default in the Configure dialog). Option Value to be Entered Default Advanced options set <Advanced options set name> n/a auto label media true false TRUE backup by volume true false TRUE backup directories true false FALSE backup job count <Sort count> 1 Backup Life <# days weeks years>

31 Quest NetVault Backup Plug-in for SAP R/3 Backint User s Guide 31 Option Value to be Entered Default Backup target set <name of backup target set> Important: If you are backing up data from a client that uses a different OS from the machine that controls the backup device, you must enter the target set created in the process described in Backing Up Data from a Different OS on page 20. For more information, also see Establishing the Proper Tape Format on page 8. client <NVBU Client name> n/a device <device name> [,<device name>[,...]] <local machine> dont reuse media true false FALSE Duplicate true false FALSE Duplicate schedule set <set name of schedule set to be used> Immediate Duplicate target set <set name of target set to be used> Any Device file online mass open true false FALSE first on media true false FALSE Group label <name of tape group> n/a max restore jobs <subjob count> 1 MID <tape label> n/a Migrate true false FALSE Migration Life <# days weeks years> n/a minimum space on media <space in MB> n/a Network compression true false FALSE Post script <name of script file> n/a Post script args <user arguments for postscript> n/a Pre script <name of script file> n/a Pre script args <user arguments for prescript> n/a recurse directories true false FALSE Restore backup true false FALSE Restore overwrite true false FALSE Restore timestamps true false TRUE reuse media never any by_group Never n/a

32 32 Appendix A Issuing SAP R/3 Backint Commands Option Value to be Entered Default Target client <name of target NVBU Client> <Local Client> title <job title> Command Line verify true false FALSE A.5.1 A.6.0 Important Notes Note the following information regarding use of parameters: You only need to enter the -p argument once in the command syntax. You can then follow it with as many of the commands listed in the previous table as desired. For those entries that list a default entry, you do not have to enter a value if the default is the desired outcome. However, any option that shows n/a as its default must have a value entered; otherwise, the option will be ignored. For Plug-in for SAP R/3 Backint version 1.4 and later, the default values listed in the preceding table can be overridden through the default parameter file identified in the Configure dialog. For more information, see Configuring the Plug-in for SAP R/3 Backint on page 15. You can issue a Backint command that includes the -p <parameter file name> argument. In this case, the specified parameter file and its default values is used instead of the file specified in the Configure dialog. Input Variables The Input variable used along with the Backint command (that is, whether in a file specified by the -i <in_file> option, or using standard input) is dependent on the desired function (that is, backup, restore or inquire ) and is described in the following table: Function backup inquire Input Format Full path names of files to be backed up. One file per line. <SSID> [<file>] <SSID> is either the saveset ID that contains the file, or #NULL if all savesets are to be searched. <file> is the full path name of the file to list. If omitted, the complete contents of the specified saveset will be output.

33 Quest NetVault Backup Plug-in for SAP R/3 Backint User s Guide 33 Function restore Input Format <SSID> <file> [<relocate>] <SSID> is the saveset ID that contains the file to be restored. This will have been output by Backint at the time the backup was made. You can also determine it by using the inquire function, or by using the NVBU Console Restore window to list the Backint backups. If <SSID> is #NULL, the most recent <file> from the latest saveset is restored. <file> is the full path name of the file to be restored. <relocate> If present, the name of the directory to write the file to. This can be used if the original location is no longer available or active. A.7.0 Output Variables The Output variable is entered along with the Backint command (that is, specified by the -o <out_file> option or to standard output if not supplied), is dependent on the desired function (that is, backup, restore, or inquire), and is described in the following table: Function backup restore inquire Output Format <result> <SSID> <filename> There will be one line of the preceding format for each file specified in the input list. <result> will be #SAVED if the file was successfully written to the backup, or #ERROR if the file could not be written. You can use the NVBU Logs window to determine the reason for the failure. <SSID> is the saveset ID that the file was written to. If the result was <ERROR>, none will be given. <filename> is the file name, as specified in the input list. <result> <SSID> <filename> There will be one line of the preceding format for each file specified in the input list. <result> will be #RESTORED if the file was successfully restored, or #ERROR if the file could not be restored. You can use the NVBU Logs window to determine the reason for the failure. <SSID> is the saveset ID that the file was written to. If the result was <ERROR>, none will be given. <filename> is the file name, as specified in the input list. <result> <SSID> <filename> There will be at least one line of the preceding format for each line of the input list. <result> will be #BACKUP for each file on backup matching the requested criteria, or #NOTFOUND if no matches were found. <SSID> is the saveset ID that the file was written to. If the result was <ERROR>, none will be given. <filename>> is the file name, as specified in the input list.

34 34 Appendix A Issuing SAP R/3 Backint Commands

35 Quest NetVault Backup Plug-in for SAP R/3 Backint User s Guide 35 Appendix B: TROUBLESHOOTING Troubleshooting B.1.0 Troubleshooting The following table describes commonly encountered problems and possible solutions. In cases where an error occurs and is not described in this table, view the job log to extract the SAP R/3 Backint error number, and then refer to the relevant SAP documentation for the resolution. Error Message Failed to add backup record Failed to write index of backup to the database These messages indicate that the selected data was actually backed up, but the job s index information was not properly added by NVBU to its database. Without this index information, the data cannot be properly restored. Explanation Method 1: Access the Device Management window of the NVBU Console, and perform a scan of the media targeted by the job (that is, by right-clicking a the target media and selecting Scan from the pop-up menu). NVBU stores index information for backup jobs in two locations: in the NVDB and on the media targeted by the backup. Performing this scan adds the index information to the NVDB. To verify this, open the NVBU Restore window and locate the specific job. If you can browse it and set up a restore job, the scan process has corrected the problem. Method 2: If the previous method failed, you must run the backup job again.

36 36 Appendix B Troubleshooting