Re: TDP for ERP (SAP R/3 on Oracle)
Answer 1. Depends on your method of backup. If you are using the RMAN extension of brbackup, then I believe the anwer would be yes... the RMAN catalog. By default (using backint) the logs are stored in the sapbackup and saparch directories. The summary logs have the names back.log and arch.log respectively. The detail logs for each backup is also stored with these files. Answer 2. This is a very deep subject. I will summarize our methods: First the backup strategy: We have three levels of backups: OS boot tape, Flatfiles backup, ERP database backup. After each database backup, we run a flatfiles backup (dsmc i) to capture all the non-database files that have been updated by the database backup. The OS backup is performed once per month. Disaster Recovery strategy: First boot the system, and lay down the OS with the OS tape. Then restore the entire flatfiles backup (select "replace" and "if newer" options). Since the flatfiles backup included all the files required for the database restore, it usually goes smoothly. If for some reason the log files, control files, etc have not restored, we can restore them from the database backup with: brrestore ?d util_file ?b2 "#NULL" ?m $SAPDATA_HOME/sapbackup/back.log (You need to be in the appropriate (ie sapbackup) directory). and repeat the above command for the following files (changing to the appropriate directories as necessary): $SAPDATA_HOME/sapbackup/. $SAPDATA_HOME/sapreorg/struct.log $SAPDATA_HOME/sapreorg/reorg.log $ORACLE_HOME/dbs/init.ora $ORACLE_HOME/dbs/init.sap $ORACLE_HOME/dbs/init.dba $ORACLE_HOME/dbs/init.utl $SAPDATA_HOME/saparch/arch.log $SAPDATA_HOME/saparch/. (Look in the "back.log" or "arch.log" to find the proper coded timestamp file to restore) The last restore is our database files. We restore them with: brrestore ?c ?b . -m ?p init.sap (type = full or all depending on the type of backup) This last step can be run from the sapdba menus if you choose as they offer more detailed help as you restore. Hope this helps. Our processes worked as recently as March during on-site DR tests. Janusz Wiszniowski To: [EMAIL PROTECTED] Subject: TDP for ERP (SAP R/3 on Oracle) Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 04/21/2004 05:29 AM Please respond to "ADSM: Dist Stor Manager" Hello ! I have two questions, 1. Has anyone of you know, where TDP for ERP (SAP R/3 on Oracle) saves informations about backups it made (datafiles, redeologs, versions etc.). Is it in RMAN Catalog (control file of database) or in some flat files, which resides in SAP directories. 2. How can I restore SAP in case of full system crash (Disaster Recovery of SAP R/3). What informations should I h
Re: TDP for ERP (SAP R/3 on Oracle)
This is documented (somewhere) in SAP's BRBACKUP, BRRESTORE, and BRARCHIVE documentation. There is also a good bit of information in the TDP/R3 manual. The backup information is kept in /oracle//sapbackup/back.log as pointers to the /oracle//sapbackup/.anf, .aff, and .pnf files with the detailed backup information. Redo log information is tracked in /oracle//saparch/arch.log as pinters to the /oracle//saparch/.svd files with the detail. These files are all saved as part of the last 8 files saved on any backup (SAP calls this group of 8 files the 'protocol' files). To restore the database in a D/R situation: 1) rebuild or recover the host system. 2) restore the SAP and Oracle executables 3) restore the protocol files for the backup and archive files 4) restore the SAP/Oracle database 5) restore any off-line redo log files required 6) Use Oracle to do a roll-forward recovery You will want to use two separate management classes for the archiveing of the redo logs, so that they can be put on separate tapes; this should ensure that you have at least one usable copy of each redo log. We quit using sapdba for this process some time back -- we use the br-tools directly from the command line. (And ALL of this requires that you've recovered your TSM server first!) >From our documentation: Create a list of all archPRD.log files su - oraprd backint -p /oracle/PRD/backint/initPRD.utl -f inquire > /tmp/list (You will not be prompted but enter the following data) #NULL /oracle/PRD/saparch/archPRD.log ^D when the prompt returns vi /tmp/list goto the bottom of the file you should see output similar to: #BACKUP SAPPRD9B04162101 /oracle/PRD/saparch/archPRD.log #BACKUP SAPPRD9B04162034 /oracle/PRD/saparch/archPRD.log #BACKUP SAPPRD9B04161522 /oracle/PRD/saparch/archPRD.log Restore the most current archPRD.log file that backint can find. Some of the archPRD.log files will be unavailable because they were not moved offsite at the time the tape were pulled. Starting at the top of the file and working down, repeat the following procedure until a file it retrieved. su - oraprd cd /oracle/PRD/saparch backint -p /oracle/PRD/backint/initPRD.utl -f restore There will be a display that looks similar to the following: Please enter the records: Format: BackupIDFilename or #NULL Filename or BackupIDFilename Path or #NULL Filename Path (Press ENTER after each filename. Press CTRL-D to finish the list.) SAPPRD /oracle/PRD/saparch/archPRD.log where is the coded stamp from the list above. Press CTRL-D to finish the list. After pressing to finish, the most current copy of the archPRD.log will be restored. Restore the most current backPRD.log file that backint can find su - oraprd cd /oracle/PRD/sapbackup backint -p /oracle/PRD/backint/initPRD.utl -f restore There will be a display that looks similar to the following: Please enter the records: Format: BackupIDFilename or #NULL Filename or BackupIDFilename Path or #NULL Filename Path (Press ENTER after each filename. Press CTRL-D to finish the list.) #NULL /oracle/PRD/sapbackup/backPRD.log (press enter) Press CTRL-D to finish the list. After pressing to finish, the most current copy of the backPRD.log will be restored. Determine the backup to use. During a real DR the most current backup, offline or online, will be used. During a DR test, the test objectives will state what type of backup and what date is to be used. su - oraprd cd /oracle/PRD/sapbackup tail -100 backPRD.log This will produce a listing similar to: bddzorjp anf 2000-11-12 19.01.01 2000-11-12 21.51.43 0 ... ALL online util_file-- bddztper anf 2000-11-13 19.01.01 2000-11-13 21.58.23 0 ... ALL online util_file-- bddzymzs anf 2000-11-14 19.01.00 2000-11-14 22.01.33 0 ... ALL online util_file-- bdeadkuv anf 2000-11-15 19.01.01 2000-11-15 22.04.41 0 ... ALL online util_file-- bdeaiipw anf 2000-11-16 19.01.00 2000-11-16 22.16.28 0 ... ALL online util_file-- bdeangkz anf 2000-11-17 19.01.01 2000-11-17 22.30.12 0 ... ALL online util_file-- bdeatewi aff 2000-11-19 00.01.00 2000-11-19 02.55.40 0 ... ALL offline_force util_file-- bdeaxcbc anf 2000-11-19 19.01.00 2000-11-19 22.07.30 0 ... ALL online util_file-- The first field (bdeaxcbc) is the coded timestamp of the Backup. This is what uniquely identifies the backup to SAP. The second field is the fid, anf for online or aff for offline. The third field is the start time of the backup, the fourth field is the end time of the backup, the fifth field
