You are on page 1of 44

MaxDB Database Backup and Recovery White Paper

Creating Backup Environment Variable and Configuration Files..................................... 2 Environment Variable................................................................................................................. 2 Backint Configuration File ......................................................................................................... 4 Backint Parameter File................................................................................................................ 5 NetBackup MaxDB Configuration File ...................................................................................... 6 Defining Backup Medium in MaxDB ................................................................................ 6 Creating Medium from the Command Line................................................................................ 6 Creating Medium from the MaxDB GUI.................................................................................... 7 Creating a MaxDB Backup Policy ................................................................................. 12 Performing a Backup of a MaxDB Database................................................................. 12 Running Backups from the Command Prompt......................................................................... 12 Running Backups from the NetBackup Administrative Console ............................................. 12 Script information ................................................................................................................. 12 Automating Backups via NetBackup Scheduling................................................................. 13 Manually Initiating Backups from the NetBackup Administrative Console ........................ 14 Performing a Restore of a MaxDB Database ................................................................ 14 Restoring a database from the command prompt ..................................................................... 15 Collecting Media IDs............................................................................................................ 15 Executing Database Restore ................................................................................................. 15 Restoring a Database From the MaxDB GUI ........................................................................... 17 Restoring Databases to a New Database Name and/or Database Server .................... 17 Configure NetBackup Security for Alternate Client Restores.................................................. 17 No.Restrictions...................................................................................................................... 17 Peername............................................................................................................................... 18 Create MaxDB database for recovery....................................................................................... 18 Move MaxDB Backup History Files to New Database Directory............................................ 28 Execute Restore ........................................................................................................................ 28 Troubleshooting ............................................................................................................ 34 Error if BSI_ENV does not point to the right file or file is missing......................................... 34 Error if Backint config file does not point to the right parameter file ...................................... 34 Error if Backint config file points to wrong backint.exe (the NBU backint) ........................... 35 Error if backint parameter file points to the wrong NetBackup configuration file................... 37 Error if the backint parameter file points to the wrong backint.exe file ................................... 37 Error if wrong backup medium name is used. .......................................................................... 38 Error if staging area is omitted from parameter file ................................................................. 38 Errors if restore is attempted with an expired NetBackup image ............................................. 39 Script errors............................................................................................................................... 40 Synchronizing Expired NetBackup Images with the MaxDB Backup History........................ 40 Switching the Operating System ................................................................................... 43 Web Database Interface................................................................................................ 43

VERITAS Software

Page 1 of 44

Creating Backup Environment Variable and Configuration Files
After installing MaxDB (originally SAPDB) and the NetBackup for MaxDB Database Extension, there are three files to create, and an environment variable to set.

Environment Variable
Create the environment variable in Windows by right-clicking on My Computer and selecting Properties.

From the Advanced tab, click on the Environment Variables button.

VERITAS Software

Page 2 of 44

Create a new System variable called “BSI_ENV”. The value of this variable is the location and name of the Backint configuration file.

VERITAS Software

Page 3 of 44

Backint Configuration File
The backint configuration file may have any name, and may be placed in any directory. Its name and location, however, must be exactly as specified in the BSI_ENV variable. The file is composedof a combination of variables and their associated values, separated by a space. Possible variables in the backint configuration file are: Parameter BACKINT <absolute_path>\<file_name> INPUT <absolute_path>\<file_name> OUTPUT <absolute_path>\<file_name> ERROROUTPUT <absolute_path>\<file_name> PARAMETERFILE <absolute_path>\<file_name> TIMEOUT_SUCCESS <number> TIMEOUT_FAILURE <number> ORIGINAL_RUNDIRECTORY <absolute_path> Description Absolute path and name of the backint program that is installed with MaxDB Absolute path and name of the standard input file Absolute path and name of the standard output file Absolute path and name of the standard error output file Absolute path and name of the configuration file of the backint for MaxDB program Time in seconds that the Database Manager waits for the end of the started Backint for MaxDB if action is successful Time in seconds that the Database Manager waits for the end of the started backint for MaxDB if errors occur Absolute path of the run directory of the source database

For a detailed description of these parameters, see the MaxDB documentation, available at http://www.mysql.com/products/maxdb/. The backint configuration file must contain the variables BACKINT, INPUT, OUTPUT, ERROROUTPUT, and PARAMETERFILE. The following is an example of a file with the minimum configuration specified:
BACKINT c:\sdb\7500\bin\backint.exe INPUT c:\veritas\netbackup\dbext\sap\backint.input OUTPUT c:\veritas\netbackup\dbext\sap\backint.output ERROROUTPUT c:\veritas\netbackup\dbext\sap\backint.error PARAMETERFILE c:\veritas\netbackup\dbext\sap\backint_parameter.txt

Please be aware, the backint information is the absolute path and name of the backint executable which is installed by MaxDB, NOT the one installed by Veritas.

VERITAS Software

Page 4 of 44

Similar to the backint configuration file. the backint parameter file consists of a series of variables and their values. Its name and location is defined in the backint configuration file with the PARAMETERFILE variable. see the MaxDB documentation. OUTPUTFILE FOR BACKINT. Value of the environment variable BI_CALLER For a detailed description of these parameters.mysql. VERITAS Software Page 5 of 44 . The possible variables for the backint parameter file are as follows: Parameter STAGING AREA: <absolute_path>\<file_name> <size>[KB|MB|GB] FILES PER BACKINT CALL: <number> BACKINT: <absolute_path>\<file_name> PARAMETERFILE OF BACKINT:<absolute_path>\<file_name> HISTORY FILE: <absolute_path>\<file_name> INPUTFILE FOR BACKINT: <absolute_path>\<file_name> OUTPUT FILE FOR BACKINT:<absolute_path>\<file_name> ERRORFILE FOR BACKINT: <absolute_path>\<file_name> MAXIMAL DELAY OF BACKINT CALL: <number> OMIT LAST DIRECTORY DELIMITER ON RESTORE: <YES | NO> BI_CALLER_VALUE: <value> Description Absolute path and size of a temporary file Maximum number of temporary files that are to be processed by backint Absolute path and name of the backint executable installed by NetBackup Absolute path and name of the configuration file for the backint Absolute path and name of the backup history Absolute path and name of the standard input file Absolute path and name of the standard output file Absolute path and name of the standard error output file Maximum waiting time in seconds between creating a temporary file and starting to save it by using backint Specifies whether the SAPDB adapter program ignores the closing slash (\) of an absolute directory name for backint. INPUTFILE FOR BACKINT. The backint parameter file must contain the variables BACKINT.txt” and is located in the c:\ veritas\netbackup\dbext\sap directory.com/products/maxdb/. the backint parameter file may have any name. The difference is these variables are separated from their values with a colon.Backint Parameter File Like the backint configuration file. PARAMETERFILE OF BACKINT. the backint parameter file is called “backint_parameter. and may be placed in any directory. available at http://www. HISTORY FILE. ERRORFILE FOR BACKINT. Using the above example of a backint configuration file.

log INPUTFILE FOR BACKINT: c:\veritas\netbackup\dbext\sap\backintoracle. the NetBackup configuration file may have any name. NetBackup MaxDB Configuration File Like the previous files. “switch_log”.sem switch_log C:\sdb\data\wrk\DEMO\switch. It must contain the variables “switch_list”.out ERRORFILE FOR BACKINT: c:\veritas\netbackup\dbext\sap\backintoracle. and execute the following command to connect to the database: dbmcli -d <database> -u <user_id>.utl”. The following is an example of a file with the minimum configuration specified: switch_list C:\sdb\data\wrk\DEMO\switch.<password> By default. at least one backup medium per backup type (complete. “switch_sem”. incremental) must be created. The backup medium type must be “PIPE” and the backup medium name must begin with the word “BACK”.err STAGING AREA: C:\VERITAS\NetBackup\DbExt\SAP\stage1 100 MB REMEMBER – The variables and their values must be separated with a colon (:).utl HISTORY FILE: c:\veritas\netbackup\dbext\sap\backinthistory.exe PARAMETERFILE OF BACKINT: C:\VERITAS\NetBackup\DbExt\SAP\initDEMO. the command is: dbmcli -d DEMO -u dbm. and is located in the C:\VERITAS\NetBackup\DbExt\SAP\ directory. the user ID and password are set to “dbm”.dbm VERITAS Software Page 6 of 44 .exe binary. Its name and location is defined with the PARAMETERFILE OF BACKINT variable in the Backint parameter file. Creating Medium from the Command Line From a command prompt. Backup medium can be created either from the command line or from within the MaxDB Database Manager GUI. the file in this case is called “initDEMO.utl”. and is found in the <install_path>\VERITAS\NetBackup\DbExt\SAP\samples directory. So for a database called “DEMO”. change to the directory containing the dbmcli. Following the above sample file as an example.in OUTPUTFILE FOR BACKINT: c:\veritas\netbackup\dbext\sap\backintoracle.The following is an example of a file with the minimum configuration specified: BACKINT: c:\veritas\netbackup\bin\backint.log policy maxdb_hot_backup Defining Backup Medium in MaxDB In order to run backups. and may be placed in any directory.list switch_sem C:\sdb\data\wrk\DEMO\switch. A sample configuration file is included with NetBackup. and is named “initSAP. and may require “policy”.

com/products/maxdb/ Creating Medium from the MaxDB GUI To create medium for NetBackup using the MaxDB GUI. and selecting Backup under database options. start by opening the interface. VERITAS Software Page 7 of 44 . the command is: medium_put BACKDEMO \\. to create a medium called BACKDEMO for full backups in a database called DEMO. and then Backup Medium.\pipe\DEMO PIPE PAGES 0 8 For more information on the medium_put command and creating backup medium.This establishes a connection to the database. run the command: medium_put <medium_name> \\. From this prompt. available at http://www. and opens the “dbmcli on <database>“ command prompt. the command is: medium_put BACKDEMOINCR \\.\pipe\DEMO PIPE DATA 0 8 To create a medium called BACKDEMOINCR for incremental backups in a database called DEMO. see the MaxDB documentation.mysql.\pipe\<database> PIPE <backup_type> <size> <block_size> For example.

and select “New Medium”.In the Backup Medium window. right click on an empty part of the window. VERITAS Software Page 8 of 44 .

Please note the only valid media type for log backups are files. or the backup medium cannot be used by NetBackup. specify a backup type of “Complete” for full backups. VERITAS Software Page 9 of 44 . cannot be performed with NetBackup. and as such.In the resulting dialog box. Under “Device Type”. be sure to select “Pipe”. or “Incremental” for incremental backups.

) • Autoloader: Specify this option to use a tape device with an autoloader feature. (This does not appear to be relevant to NetBackup.) For detailed information on these options.com/products/maxdb/ VERITAS Software Page 10 of 44 . (This does not appear to be relevant to NetBackup. (It is unknown if this applies to a device type of PIPE.mysql.) • Overwrite: Allows the backup to overwrite the medium. you can specify • Size: Specify the size of the backup medium (It is unknown if this applies to a device type of PIPE.Finally.) • Blocksize: Select the “Blocksize” option to allow the backup to write in blocks of up to eight pages. (This may allow for performance enhancement.) • OS Command: Allows operating system commands to be run when running backups to tape. contact MaxDB support or review the MaxDB web page at http://www. the name must begin with the word “BACK” On the Extended tab.

Veritas Support recommends leaving these options set to their default. the window looks like the following: VERITAS Software Page 11 of 44 . After creating the backup medium.

Connect to the database with the command dbmcli -d <database> -u <user_id>. issue the backup command.veritas. Then.support. Performing a Backup of a MaxDB Database Backups may be run either from the command prompt. on pages 19 through 28 (for Windows master servers) or pages 32 through 42 (for Unix master servers) Please refer to this guide for the setup of the MaxDB policy.com/docs/268101. Running Backups from the Command Prompt 1. The script’s basic format is as follows: dbmcli -u <user_ID>. dbmcli on DEMO> util_connect 3. Additionally a utility session must be started before running a backup. When running a backup of MaxDB. and “backup_start <medium> <backup_type>” launches the backup. The backup script needs to perform three functions: connect to the database. the command is: dbmcli on DEMO> backup_start BACKDEMO DATA Running Backups from the NetBackup Administrative Console Script information In order to automate backups of MaxDB databases or initiate a backup from the master server.<password>“ starts the utility session.<password> -d <database>“ connects the user to the database.<password>. “uUTL <user_ID>. VERITAS Software Page 12 of 44 . backup_start <medium_name> <backup_type>. Finally.<password> backup_start <medium> <backup_type> The “dbmcli -u <user_ID>.Creating a MaxDB Backup Policy Creation of policies is covered in the VERITAS NetBackup 5. Please note the script information is different. the command issued must include the name of the backup medium. and then backup the database. or from within the NetBackup administration console as either scheduled or manually initiated backups.com/products/maxdb/.dbm 2.htm.mysql. For a database “DEMO”: dbmcli -d DEMO -u dbm. from the database command prompt.<password> -d <database> -uUTL <user_ID>. and is outlined later in this guide. start a utility session with the “util_connect” command. a backup script must be created and listed in the MaxDB backup policy. start a utility session.1 for SAP System Administrator’s Guide for Windows. For a medium named “BACKDEMO” which is of a type “Complete”. found at http://seer. To learn more about utility sessions refer to MaxDB documentation at http://www.

the Automatic Backup schedule should be open from 6 to 8 PM on Monday. an Application Backup schedule and an Automatic Backup schedule. the file may be used in a NetBackup policy. This schedule creates a window in which backups can run.mysql. So. and not modifying it. to have the backup run once a week on Monday nights between 6 and 8 PM. not when the backup will actually run. seven days a week. For more information on MaxDB scripting options.cmd extension. VERITAS Software Page 13 of 44 . The other type of backup schedule is the Automatic Backup schedule.com/products/maxdb/ Automating Backups via NetBackup Scheduling NetBackup MaxDB policies must have two schedules. contact MaxDB support or review the MaxDB web page at http://www. By entering this information into a file with a .dbm -d DEMO -uUTL dbm.dbm backup_start BACKDEMO DATA This is the only line required in the backup script. for example. and is open 24 hours a day. NOTE: To change the retention level of the MaxDB backup. if the user and password are still set to the default (dbm. and the backup medium for full backups is called BACKDEMO”.For example. the command to start the backup would be: dbmcli -u dbm. change the retention of the Application Backup schedule. dbm). The Application Backup schedule is created by default when a MaxDB policy is created. which is the schedule which actually initiates the automatic backup. Changes to this schedule can cause the backups to fail with a status 199. Operation not allowed during this time period. the database is called “DEMO”. Veritas support recommends leaving this schedule alone.

it must first be transferred to the OFFLINE operational state and then to the ADMIN operational state. and users can log on. Standby instances cannot accept any connections. to manually initiate a backup from the master server.Manually Initiating Backups from the NetBackup Administrative Console Once the policy is created. If the database instance is in the ONLINE operational state. right click on the policy. The database instance is only available for database administration work. and specify “Manual Backup”. Performing a Restore of a MaxDB Database Database restores can be initiated from either the command line or the MaxDB GUI. They are constantly in a restart state. when recovering a database. open the NetBackup Administrative Console. The database instance is not running. it must be in the operational state ADMIN. and find the MaxDB policy. For standby instances in hot standby systems only. Please note per the MaxDB documentation. Operational State ONLINE STANDBY ADMIN OFFLINE Meaning The database instance has been started. VERITAS Software Page 14 of 44 . This initiates the manual backup. Then.

First. specifying the medium to use. From the “dbmcli on <database>“ prompt. the restore command is issued. when recovering a database. Then. NOTE: Per the MaxDB documentation. Display the available media IDs. Connect to the database with the dbmcli command (dbmcli -d <database> -u <user_id>.dbm dbmcli on DEMO> backup_ext_ids_get <medium_name> <db_name> <server_name> OK dbmcli on DEMO>backup_ext_ids_list OK END AVAILABLE|DEMO NS1088526040 \\. dbmcli -d DEMO -u dbm.dbm 2. a listing of the available media IDs is collected. and a medium called “BACKDEMO”. execute the command “backup_ext_ids_list”.\pipe\DEMO|DATA MIGRATION|2004-06-29 11:20:32| MIGRATION|2004-06-29 14:17:58| Executing Database Restore After collecting the media IDs available for database restore.\pipe\DEMO|DATA AVAILABLE|DEMO NS1088536685 \\. execute the “backup_ext_ids_get” command with the following switches: backup_ext_ids_get <medium_name> <db_name> <server_name> So. Collecting Media IDs Collecting media IDs is done with the “backup_ext_ids_get” command. for a server called “Server_MaxDB” with a database called “DEMO”. the restore is performed from the command line after establishing a utility session.Restoring a database from the command prompt Restores from the command line are a two-step process. dbmcli on DEMO> backup_ext_ids_list The series of commands looks like the following: dbmcli -d DEMO -u dbm. 1. media IDs are displayed with the “backup_ext_ids_list” command. it must be in the operational state ADMIN. the command would be: dbmcli on DEMO> backup_ext_ids_get BACKDEMO DEMO Server_MaxDB 3. Action Desired Stopping the Database Instance Transferring to the ADMIN Operational State Transferring to the OFFLINE Operational State Transferring to the ONLINE Operational State Transferring to the STANDBY Operational State Command issued db_stop db_admin db_offline db_online db_standby VERITAS Software Page 15 of 44 .<password>).

dbmcli on DEMO> util_connect The restore command is “recover_start”.0 Build 014-123-073-298 Pages Transferred 240 Pages Left 0 Volumes 1 Medianame BACKDEMO Location \\. the ID string needs to be enclosed in quotation marks.After placing the database into an ADMIN status. and the backup media ID.\pipe\DEMO” OK Returncode 0 Date 20040630 Time 00133545 Server server. A successful restore displays something similar to the following: dbmcli on DEMO>recover_start BACKDEMO DATA ExternalBackupId “DEMO NS1088526040 \ \. the command is “util_connect”. from the dbmcli on <database> command prompt. the command issued is: dbmcli on DEMO> recover_start BACKDEMO DATA ExternalBackupId “DEMO NS1088526040 \\.\pipe\DEMO” NOTE: Since the media ID name contains a space.domain.5.domain. The sequence is as follows: recover_start <medium> <type> ExternalBackupId <BID> Using the above listing.com:DEMO_20040616_155125 Max Used Data Page 0 VERITAS Software Page 16 of 44 . and the backup medium name “BACKDEMO”. and requires the backup medium name.\pipe\DEMO Errortext Label DAT_00022 Is Consistent true First LOG Page 1098 Last LOG Page DB Stamp 1 Date 20040629 DB Stamp 1 Time 00112032 DB Stamp 2 Date DB Stamp 2 Time Page Count 224 Devices Used 1 Database ID server. the type of backup which was performed.com Database DEMO Kernel Version Kernel 7.

the database cannot be restored.Restrictions Use of the No. A brief overview is shown below.Restrictions or peername) Create instance for recovery Create backup medium that matches original backup medium Start instance in ADMIN state Copy over dbm.Restoring a Database From the MaxDB GUI MaxDB databases can also be restored from the MaxDB Database Manager GUI using backups taken by NetBackup. dbm. start instance Recovery successful. No.Restrictions” file. dbm. create an empty file called “No. Configure NetBackup Security for Alternate Client Restores To allow one client to restore databases from another client.mdf files from original instance. To allow this. dbm.ebf. NOTE: Do not add a suffix to the files created in the altnames directory. It is important to know the name of the original backup medium.ebf. dbm. under “Execute Restore” in the “Restoring Databases to a New Database Name and/or Database Server” section. Overview: Configure NetBackup security for alternate client restores. or the use of peername file is required. (No.Restrictions file allows any client to perform an alternate client restore of any clients’ data. Without this information. The procedure and screen images are the same as those shown later in the guide.Restrictions” in the directory path <install_path>\NetBackup\db\altnames\ on the master server (in the /usr/openv/netbackup/db/altnames directory on a Unix master server). with details following. Please refer to those images for assistance restoring a database using the MaxDB GUI.knl.knl. VERITAS Software Page 17 of 44 . Restoring Databases to a New Database Name and/or Database Server Restoring a database to either a new database name or to a new database server (alternate client restore or redirected restore) requires several steps be completed or the restore will fail to execute. either the use of the “No.mdf files from source db to new instance Start recovery wizard Select initialize instance Select backup set to restore Start restore When successful. and have copies of dbm.

of a type PIPE called BACKDEMO in the new database. be sure to create a backup medium. For example. ready for recovery. the database must be placed in ADMIN status. if the administrator wanted the client Freddie to restore files which were backed up by another client Oscar. If the backup medium for the original database was BACKDEMO. in the recovery database. Additionally. 1. Start by clicking on the “Create” to create a new database instance VERITAS Software Page 18 of 44 . where peername is the name of the client which can access files backed up by a different server. a backup medium must be created which has the same name as the source database. this procedure places the database into an ADMIN state. The following series of screen captures shows the step-by-step procedure to create a database for recovery. then it would be necessary to create the following file on the master server: <install_path>\NetBackup\db\altnames\freddie Create MaxDB database for recovery Like the standard database restore. when creating a database for an alternate client restore. using the wizard in the MaxDB GUI. By default.Peername Allowing a single client to perform redirected restores is enabled by the creation of an empty file peername in the <install_path>\NetBackup\db\altnames\ directory of the master server.

Click “Next” to continue. Click on “Next” to continue on the installation wizard 3. This example uses the “Blank” template. VERITAS Software Page 19 of 44 .2. Select the template desired for creation of the database.

Provide a database name (in this example. and click on “Next”. VERITAS Software Page 20 of 44 . A port number is unnecessary. 5. Click “Next” to continue. RECOVER is used). If there is more than one version of MaxDB installed. select the version to use.4.

the start database service automatically was not selected. As necessary. Click “Next” to continue.6. VERITAS Software Page 21 of 44 . The default is dbm. Click “Next” to continue. In this example. 7. it is possible to change that option. however. In this example. select the startup option for the database. dbm. on this screen. Create the database manager user name and password. the default was accepted.

9. Click “Next” to continue. the default values were used. The default is OLTP.8. Click “Next” to continue. VERITAS Software Page 22 of 44 . For this example. This screen allows the user to specify the instance type. modify the initialization parameters. If necessary.

In this example. the defaults were accepted. VERITAS Software Page 23 of 44 . Click “Next” to continue. Adjust them if necessary. The next two screens show the database instance parameters.10.

11. the volumes for the database are setup. Click “Next” to continue. In the next three images. VERITAS Software Page 24 of 44 .

VERITAS Software Page 25 of 44 .

Please notice how this is setup in the screen captures. the source database was called “DEMO” and the backup medium in the database was “BACKDEMO”. Here is where it is necessary to fill in the information about the backup medium from the original (source) database.12. information about the backup medium needs to be entered. At this point. Click “Next” to continue. VERITAS Software Page 26 of 44 . In this example.

click “Start” to create the database instance. 14.13. VERITAS Software Page 27 of 44 . Click “Next” to continue. On the “Create Database Instance” interface. Finally. be sure to select the option “Create instance for recovery”.

knl. as there are additional steps necessary in order to successfully restore the database. dbm. VERITAS Software Page 28 of 44 . the database is ready for restore and recovery. The following screen captures show the step-by-step procedure to restore and recover the database using the MaxDB GUI. For example. and dbm. and the backup history files are moved to the appropriate directory. and find the following three files: dbm. these files need to be copied from the original database directory structure to the new database directory structure.ebf. Please note do NOT click on “Next”. the GUI displays the instance is successfully created. Go to the <install_path>\sdb\data\wrk\<source> directory. When finished. copy the dbm. when creating a database for recovery. Move MaxDB Backup History Files to New Database Directory There are three files in each MaxDB database which contain information about the backup history. Execute Restore Once the database instance is created for recovery and in an ADMIN status.knl. These files need to be copied to the <install_path>\sdb\data\wrk\<recovery> directory. dbm. As such.ebf files from the <install_path>\sdb\data\wrk\DEMO directory into the <install_path>\sdb\data\wrk\RECOVER directory. dbm. and prompts to click “Next” to start the recovery process.mdf.15.mdf. if the original database is called “DEMO” and the recovery database is called “RECOVER”.

2. VERITAS Software Page 29 of 44 .1. selecting the “Recovery Wizard”. and under the “Recovery” section. This launches the Recovery Wizard. Click on “Next” to continue. Begin by selecting the database.

Click on “Next” to continue. On the “Restore Database Instance” screen. Click on “Next” to continue. Select the option to restore a specified backup from history. VERITAS Software Page 30 of 44 . This allows the restore to overwrite the existing database information. be sure to select the option to initialize the database before restore.3. 4.

Confirm this is correct. Specify the backup to restore. and click on “Start” to begin the restore.5. 6. MaxDB retrieves a list of available backups. VERITAS Software Page 31 of 44 . and click on “Next” to continue. MaxDB requests confirmation the correct medium was selected. and indicates the name of the medium. and if logs are required.

The restore starts.7. 8. and displays the amount of data transferred. Click on “Yes” to start the restore. VERITAS Software Page 32 of 44 . MaxDB requests confirmation to initialize the database in the recovery process.

MaxDB confirms the database was successfully restarted. 10. Click on “Restart” to restart the database. When the restore is finished successfully. the interface provides an option to restart the database. Click “Close” to finish the recovery.9. VERITAS Software Page 33 of 44 .

Constructed the following reply: ERR -24927. Can not read the Backint for MaxDB configuration file.txt is missing or unreadable. As such.txt is missing or unreadable. Error if Backint config file does not point to the right parameter file NetBackup Error: Status 29 . there is no Veritas backint log directory. The MaxDB log file is the dbm.ebp file.ERR_TOOLCHK: external backup tool not found The file C:\VERITAS\NetBackup\DbExt\SAP\backint_config. 2004-07-07 09:40:06 Checking existence and configuration of Backint for MaxDB. This can occur because the permissions of the command do not allow it to be executed. The backint log file (created by placing a “backint” folder in the <install_path>\veritas\netbackup\logs directory) logs information regarding the NetBackup side of the backup and restore. or there is lack of system resources such as memory and swap space.ebp log file shows the following: 2004-07-07 09:40:06 Using environment variable 'TEMP' with value 'C:\DOCUME~1\user\LOCALS~1\Temp' as directory for temporary files and pipes. and the dbm. one created by MaxDB. there are two general files to review.failed trying to exec a command.txt' as path of the configuration file of Backint for MaxDB. Check failed. Have encountered error -24927: The file C:\VERITAS\NetBackup\DbExt\SAP\backint_config. A command could not be executed. one created by NetBackup. Error if BSI_ENV does not point to the right file or file is missing NetBackup Error: Status 29 . This can occur because the permissions of the command do not allow it to be executed. Using connection to Backint for MaxDB Interface. Using environment variable 'BSI_ENV' with value 'C:\VERITAS\NetBackup\DbExt\SAP\backint_config. it should be observed nearly all MaxDB database backups fail with a Status 29. A command could not be executed. located in the <install_path>\sdb\data\wrk\<database_name> directory. If the BSI_ENV environment variable is not pointing to the correct file. or there is lack of system resources such as memory and swap space.failed trying to exec a command. Additionally. VERITAS Software Page 34 of 44 . This file captures information about what occurs on the MaxDB side of the backup and restore. it is generally necessary to collect log files in order to properly assess the problem and recommend an appropriate solution.Troubleshooting In troubleshooting MaxDB backups and restores.

If the backint configuration file points to the incorrect backint.failed trying to exec a command.2708] <2> backint_process_parm_file: param_variable = BACKINT: : param_value = c:\veritas\netbackup\bin\backint. there is no Veritas backint log directory. This can occur because the permissions of the command do not allow it to be executed. In the Veritas backint log file. Error if Backint config file points to wrong backint.2708] <2> backint_process_parm_file: param_variable = HISTORY : param_value = FILE: 09:51:31.utl 09:51:31.235 [2572.235 [2572. or is improperly specified. the following lines appear: 09:51:31.235 [2572.2708] <8> backint_process_parm_file: WARNING: unknown parameter: STAGING AREA: C:\VERITAS\NetBackup\DbExt\SAP\stage1 100 MB VERITAS Software Page 35 of 44 .235 [2572.235 [2572.Begin of error output of Backint for MaxDB (c:\veritas\netbackup\dbext\sap\backint.err 09:51:31. 2004-07-07 09:44:07 Could not open the parameter file.2708] <8> backint_process_parm_file: WARNING: unknown parameter: OUTPUTFILE FOR BACKINT: c:\veritas\netbackup\dbext\sap\backintoracle.2708] <2> backint_process_parm_file: param_variable = OUTPUTFILE : param_value = FOR 09:51:31.exe 09:51:31.235 [2572. or there is lack of system resources such as memory and swap space.2708] <2> backint_process_parm_file: param_variable = INPUTFILE : param_value = FOR 09:51:31.2708] <8> backint_process_parm_file: WARNING: unknown parameter: PARAMETERFILE OF BACKINT: C:\VERITAS\NetBackup\DbExt\SAP\initDEMO.If the backint configuration file does not exist.2708] <8> backint_process_parm_file: WARNING: unknown parameter: BACKINT: c:\veritas\netbackup\bin\backint.txt' does not exists.exe file (the NetBackup backint versus the MaxDB backint).2708] <2> backint_process_parm_file: param_variable = PARAMETERFILE : param_value = OF 09:51:31.235 [2572.log 09:51:31.2708] <8> backint_process_parm_file: WARNING: unknown parameter: HISTORY FILE: c:\veritas\netbackup\dbext\sap\backinthistory.2708] <2> backint_process_parm_file: param_variable = ERRORFILE : param_value = FOR 09:51:31.235 [2572.exe (the NBU backint) NetBackup Error: Status 29 .exe 09:51:31. A command could not be executed. and the following error message is found near the end of the dbm.error)---------2004-07-07 09:44:07 The file 'c:\veritas\netbackup\dbext\sap\backint_parameter.235 [2572.in 09:51:31.235 [2572.ebp log file: 2004-07-07 09:44:07 ---------. and a dbm.ebp log file.2708] <8> backint_process_parm_file: WARNING: unknown parameter: INPUTFILE FOR BACKINT: c:\veritas\netbackup\dbext\sap\backintoracle.2708] <8> backint_process_parm_file: WARNING: unknown parameter: ERRORFILE FOR BACKINT: c:\veritas\netbackup\dbext\sap\backintoracle.235 [2572.235 [2572.out 09:51:31.235 [2572. there is both a backint log (for Veritas).

2708] <16> backint_process_parm_file: ERROR: switch_list missing from parameter file c:\veritas\netbackup\dbext\sap\backint_parameter.output)---------2004-07-07 09:53:48 WARNING: unknown parameter: BACKINT: c:\veritas\netbackup\bin\backint.235 [2572.in 2004-07-07 09:53:48 2004-07-07 09:53:48 WARNING: unknown parameter: OUTPUTFILE FOR BACKINT: c:\veritas\netbackup\dbext\sap\backintoracle.235 [2572.235 [2572. setting policy = washburn_max_db 09:51:31.2708] <4> backint_process_parm_file: INFO .2708] <16> backint_process_parm_file: ERROR: switch_sem missing from parameter file c:\veritas\netbackup\dbext\sap\backint_parameter.2708] <2> backint_process_parm_file: param_variable = STAGING : param_value = AREA: 09:51:31.txt 09:51:31.txt 2004-07-07 09:53:49 default drives value = 1 VERITAS Software Page 36 of 44 .09:51:31.235 [2572.235 [2572.ebp log file: 2004-07-07 09:53:48 2004-07-07 09:53:48 Cleaning up.235 [2572.txt Similar messages appear in the dbm.235 [2572. 2004-07-07 09:53:48 Copying output of Backint for MaxDB to this file.2708] <2> backint_process_parm_file: param_variable = STAGING : param_value = AREA: 09:51:31.2708] <8> backint_process_parm_file: WARNING: unknown parameter: STAGING AREA: C:\VERITAS\NetBackup\DbExt\SAP\stage2 100 MB 09:51:31.Found SAP_SERVER environment variable.err 2004-07-07 09:53:48 2004-07-07 09:53:49 WARNING: unknown parameter: STAGING AREA: C:\VERITAS\NetBackup\DbExt\SAP\stage1 100 MB 2004-07-07 09:53:49 2004-07-07 09:53:49 WARNING: unknown parameter: STAGING AREA: C:\VERITAS\NetBackup\DbExt\SAP\stage2 100 MB 2004-07-07 09:53:49 WARNING: drives value missing from parameter file c:\veritas\netbackup\dbext\sap\backint_parameter.235 [2572. 2004-07-07 09:53:48 ---------.txt 09:51:31.exe 2004-07-07 09:53:48 2004-07-07 09:53:48 WARNING: unknown parameter: PARAMETERFILE OF BACKINT: C:\VERITAS\NetBackup\DbExt\SAP\initDEMO.2708] <2> backint_process_parm_file: working dir = C:\VERITAS\NetBackup\Logs\user_ops\sap 09:51:31.235 [2572.utl 2004-07-07 09:53:48 2004-07-07 09:53:48 WARNING: unknown parameter: HISTORY FILE: c:\veritas\netbackup\dbext\sap\backinthistory.235 [2572. setting server = washburn 09:51:31.235 [2572.Found SAP_CLIENT environment variable.2708] <16> backint_process_parm_file: default drives value = 1 09:51:31.2708] <4> backint_process_parm_file: INFO .2708] <16> backint_process_parm_file: WARNING: drives value missing from parameter file c:\veritas\netbackup\dbext\sap\backint_parameter.Begin of output of Backint for MaxDB (c:\veritas\netbackup\dbext\sap\backint.out 2004-07-07 09:53:48 2004-07-07 09:53:48 WARNING: unknown parameter: ERRORFILE FOR BACKINT: c:\veritas\netbackup\dbext\sap\backintoracle.log 2004-07-07 09:53:48 2004-07-07 09:53:48 WARNING: unknown parameter: INPUTFILE FOR BACKINT: c:\veritas\netbackup\dbext\sap\backintoracle.txt 09:51:31.2708] <16> backint_process_parm_file: ERROR: switch_log missing from parameter file c:\veritas\netbackup\dbext\sap\backint_parameter.235 [2572.2708] <4> backint_process_parm_file: INFO .Found SAP_POLICY environment variable. setting client = washburn 09:51:31.

This can occur because the permissions of the command do not allow it to be executed. Error if the backint parameter file points to the wrong backint.473 [2816.ebp log file.utl file 2004-07-07 09:53:49 WARNING: default sort_backup_type to <size> for restore 2004-07-07 09:53:49 ERROR: incorrect format or option in .utl file (-p) In the dbm.txt 2004-07-07 09:53:49 ERROR: switch_sem missing from parameter file c:\veritas\netbackup\dbext\sap\backint_parameter. This can occur because the permissions of the command do not allow it to be executed. In the Veritas backint log file. This indicates the parameter file is specified incorrectly.failed trying to exec a command.End of output of Backint for MaxDB (c:\veritas\netbackup\dbext\sap\backint.utl -i c:\veritas\netbackup\dbext\sap\backintoracle.2004-07-07 09:53:49 ERROR: switch_list missing from parameter file c:\veritas\netbackup\dbext\sap\backint_parameter. Backint for Oracle ended at 2004-07-07 10:09:09 with return code 2.1388] <16> c:\veritas\netbackup\bin\backint. and a dbm. or there is lack of system resources such as memory and swap space.txt 2004-07-07 09:53:49 ERROR: switch_log missing from parameter file c:\veritas\netbackup\dbext\sap\backint_parameter.output)---------- The key to this series of error messages is the “Unknown parameter” error messages. or there is lack of system resources such as memory and swap space. Backint for Oracle output: ERROR: couldn't open param_file: C:\VERITAS\NetBackup\DbExt\SAP\initDEMO.1: ERROR: incorrect format or option in . This indicates the wrong backint is in use.473 [2816.utl Backint for Oracle output: ERROR: incorrect format or option in .utl 10:08:57.utl file (p) 2004-07-07 09:53:49 2004-07-07 09:53:49 ---------. the following lines appear: 10:08:57.exe -u DEMO -f backup -t file -p C:\\VERITAS\NetBackup\DbExt\SAP\initDEMO. VERITAS Software Page 37 of 44 .exe 5.ebp log file. A command could not be executed. as the NetBackup backint file does not recognize these parameters. similar messages appear: The key to this error message is the inability of the backint process to open the parameter file (ERROR: couldn't open param_file).exe file NetBackup Error: Status 29 .in -c' . Error if backint parameter file points to the wrong NetBackup configuration file NetBackup Error: Status 29 .utl file (-p) Calling 'c:\veritas\netbackup\bin\backint. A command could not be executed. There is both a backint log (for Veritas).1388] <16> backint_process_parm_file: ERROR: couldn't open param_file: C:\ VERITAS\NetBackup\DbExt\SAP\initDEMO.txt 2004-07-07 09:53:49 WARNING: sort_backup_type not specified in .failed trying to exec a command.

Begin of error output of Backint for MaxDB (c:\veritas\netbackup\dbext\sap\backint. there is the following message: 2004-07-07 10:19:09 0x0000056c ERR -24920 DBM ERR_BACKUPOP: backup operation was unsuccessful 0x0000056c ERR -24920 DBM The backup tool failed with 2 as sum of exit codes. there is no Veritas backint log file generated.2004-07-07 10:43:41 A review of the MaxDB website indicates this error message occurs when the backup failed due to a problem with the database or the backup tool. In the dbm. This can occur because the permissions of the command do not allow it to be executed.failed trying to exec a command. A command could not be executed. or there is lack of system resources such as memory and swap space. In this case. 2004-07-07 10:22:19 0x00000a8c 0 DBM command backup_start BACKDEMO_WRONG DATA 2004-07-07 10:22:19 0x00000a8c ERR -24985 DBM ERR_MENOTFOUND: medium not found 2004-07-07 10:22:23 0x000001ac 0 DBM command backup_start BACKDEMO_WRONG DATA 2004-07-07 10:22:23 0x000001ac ERR -24985 DBM ERR_MENOTFOUND: medium not found The “medium not found” message is the key to this issue. The database request was canceled and ended with error -903. In the dbm.In this case. or there is lack of system resources such as memory and swap space. neither the Veritas backint nor the dbm. While this error message appears to be somewhat generic.prt file. the following error is observed: 2004-07-07 10:43:40 Have encountered error -24920: 2004-07-07 10:43:41 The backup tool failed with 2 as sum of exit codes. In the dbm. there is no Veritas backint log file generated. This can occur because the permissions of the command do not allow it to be executed. The database request was canceled and ended with error -903. as that eliminates one known cause of the error message.ebp file). (found in same location as the dbm. A command could not be executed.error)---------2004-07-07 10:19:08 The path of Backint for Oracle is not defined in the parameter file.ebp log file. In this case. Error if staging area is omitted from parameter file NetBackup Error: Status 29 .ebp log files are generated.ebp log file. VERITAS Software Page 38 of 44 . Error if wrong backup medium name is used. checking the staging area is a good first step in the troubleshooting process. This indicates either the path for the Veritas backint is not defined. the following message is observed: 2004-07-07 10:19:08 ---------. however. or defined incorrectly.failed trying to exec a command. NetBackup Error: Status 29 .

VERITAS Software Page 39 of 44 .0 09:31:32. If a restore is attempted.0 To correct this. and Restore GUI to determine what backup sets are available. use the NetBackup Backup.ebp file. In the Veritas backint log file.2004-08-23 09:32:54 2004-08-23 09:32:54 Constructed the following reply: 2004-08-23 09:32:54 ERR 2004-08-23 09:32:54 -24920. and the following is observed: The job does not display in the NetBackup Administration Console in the Activity Monitor The job shows the following error in the MaxDB Database Manager GUI: In the dbm.ERR_BACKUPOP: backup operation was unsuccessful 2004-08-23 09:32:54 The backup tool failed with 2 as sum of exit codes.998 [476.998 [476.0 09:31:32. 2004-08-23 09:32:54 Have encountered error -24920: 2004-08-23 09:32:54 The backup tool failed with 2 as sum of exit codes.2108] <4> backint_do_inquire: #NOTFOUND C:\apps\VERITAS\NetBackup\DbExt\SAP\stage1.998 [476. The database request was canceled and ended with error -903. The database request was canceled and ended with error -903. Then see the “Synchronizing Expired NetBackup Images with the MaxDB Backup History “section of this documentation for assistance in correcting the mismatched information. Archive. the following message is observed: 2004-08-23 09:32:54 2004-08-23 09:32:54 Filling reply buffer.2108] <4> backint_do_inquire: #NOTFOUND C:\apps\VERITAS\NetBackup\DbExt\SAP\stage1. This presents a potential problem where images which have expired within NetBackup show as available in the MaxDB Database Manager GUI. and rerun the restore.2108] <16> backint_do_inquire: ERROR: Netbackup cannot find inquiry request for backup id: NS1092618550.Errors if restore is attempted with an expired NetBackup image There is a known issue within MaxDB where the backup images never “expire” and drop out of the backup history window in the Database Manager GUI.2108] <16> backint_do_inquire: ERROR: Netbackup cannot find inquiry request for backup id: NS1091408775. file: C:\apps\VERITAS\NetBackup\DbExt\SAP\stage1. a series of message similar to the following appear: 09:31:32. file: C:\apps\VERITAS\NetBackup\DbExt\SAP\stage1. the restore fails.0 09:31:32.998 [476.

Synchronizing Expired NetBackup Images with the MaxDB Backup History At this point in time. there is no way within MaxDB to expire a backup image. if the utility session is not initiated. In order to maintain consistent information in both MaxDB and NetBackup. support recommends breaking down the script. present a potential issue of a backup image being expired in NetBackup. but still showing as available in MaxDB.Script errors Errors in the backup script (or . or if the wrong database name is specified in the script.cmd file) are more difficult to troubleshoot. This does. VERITAS Software Page 40 of 44 . If the user IDs or passwords are incorrect. Status code 29. In general. and confirming each section of the script can be executed successfully from the command line. and not NetBackup.ebp nor Veritas backint log files are created. it is necessary to manually “synch-up” the backup history of MaxDB and NetBackup. Please note this is a limitation of MaxDB. and remove it from the MaxDB backup history. however. the backup will fail. as neither dbm.

This brings up a window similar to the following: The only backup set NetBackup has in its catalog is a backup from 17 August 2004. Then click on the Select for Restore button. VERITAS Software Page 41 of 44 .Begin by opening the Backup. and specify a policy type of SAP. and setting the master and client server names correctly. Archive and Restore GUI on the MaxDB server.

To correct this. while the NetBackup GUI shows only one. In this case. This is a text file. This brings up a window similar to the following: In this example. open the MaxDB Database Manager GUI. and select the Backup History option for the correct database.knl file must be manually edited. the dbm.knl file is located in the c:\sdb\data\wrk\DEMO directory. The contents of the file look like the following: 40EC2363000D|DAT_00034|SAVE WARM|2004-07-07 11:22:59|2004-07-07 11:22:59|2004-07-07 11:22:59|2004-07-07 11:23:02| 1126| |NO |BACKDEMO | 240| 1| 0| | 40F562EC0002|DAT_00035|SAVE WARM|2004-07-14 11:44:28|2004-07-14 11:44:28|2004-07-14 11:44:29|2004-07-14 11:44:32| 1163| |NO |BACKDEMO | 248| 1| 0| | 410459E70002|DAT_00036|SAVE WARM|2004-07-25 20:09:59|2004-07-25 20:09:59|2004-07-25 20:10:01|2004-07-25 20:10:02| 1172| |NO |BACKDEMO | 248| 1| 0| | 410D937F0002|DAT_00040|SAVE WARM|2004-08-01 20:06:07|2004-08-01 20:06:07|2004-08-01 20:06:07|2004-08-01 20:06:11| 1191| |NO |BACKDEMO | 248| 1| 0| | 4120092F0002|DAT_00041|SAVE WARM|2004-08-15 20:09:03|2004-08-15 20:09:03|2004-08-15 20:09:04|2004-08-15 20:09:07| 1201| |NO |BACKDEMO | 248| 1| 0| | VERITAS Software Page 42 of 44 . six backup jobs show as available for restore. since the database is the DEMO database. and can be opened with any text editor.knl file is located in the <install_path>\data\wrk\<database> directory.Next. the dbm. The dbm.

knl file which do not have a corresponding backup set in the NetBackup GUI. This means a backup created on the operating system Microsoft Windows may be restored to the same operating system or to Linux. A backup created on Linux may be restored to the same operating system or to Microsoft Windows. Web Database Interface One of the options which can be installed with MaxDB is the WebDBM interface which allows the databases to be administered from a web browser. Treat this sort of restore in the same manner as any other alternate client restore. and remove any lines from the dbm. and contains the following entries: Browsable=0 DefaultDocument=index. enter the following command: net start sapdbwww stop sapdbwww To stop the Web Server at the command prompt. if desired. lines in the dbm. the date and time of the backup are clearly indicated. In the above examples. which contains the backup information from the 17 August 2004 backup.types Port=9999 The values and their associated value data are: Browsable: Determines if the contents of the directories under DocumentRoot are visible using a browser.knl file above would need to be removed EXCEPT the last line. VERITAS Software Page 43 of 44 . it is possible to switch from Microsoft Windows to Linux and vice versa. Compare the information in the NetBackup GUI to the information in the file. enter the following command: net Information about the configuration of the web server portion of MaxDB is found in the registry path HKEY_LOCAL_MACHINE\ SOFTWARE\SAP\SAP DBTech\WebAgent75\HTTP. Switching the Operating System When restoring.4122422A0003|DAT_00042|SAVE WARM|2004-08-17 12:36:42|2004-08-17 12:36:42|2004-08-17 12:36:42|2004-08-17 12:36:45| 1202| |NO |BACKDEMO | 248| 1| 0| | Note in the fourth section. 0: The contents are not visible 1: The contents are visible DefaultDocument: Used to change the start page of the web server.html DocumentRoot=<independent_program_path>\web\Documents LogDirectory=<independent_program_path>\web\Log LogRequests=1 MaxThreads=10 MimeTypeFile=<independent_program_path>\web\config\mime. start the web server service (SAP DB WWW) • • To start the Web Server at the command prompt. After downloading and installing WebDBM software on MaxDB server.

log. Port: Allows the administrator to change the port address for the Web Server. 1: HTTP accesses are logged. MaxThreads: Determines the maximum number of threads which can be used to process access to the Web Server. 0: HTTP accesses are not logged. When the Web Server is started. VERITAS Software Page 44 of 44 . MimeTypeFile: Defines the MIME type file. LogDirectory: If LogRequest is set so that HTTP accesses are logged. the threads are also started as a thread pool. if necessary. accesses to the MaxDB Web Server are logged in the files httperr.DocumentRoot: Changes the path for the root directory of the web pages. These log files are written in the directory specified in LogDirectory. if necessary. LogRequests: Determines if the HTTP accesses are logged.log and httpreq. if desired.