Difference between revisions of "Recovery as Normal Files(SAP R3)"
| Line 37: | Line 37: | ||
===Step 2=== | ===Step 2=== | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Copy/Move the other files(data file, control file) to the SAP R3 client under a folder with the name of a backup id without the extension. | Copy/Move the other files(data file, control file) to the SAP R3 client under a folder with the name of a backup id without the extension. | ||
| Line 93: | Line 69: | ||
| + | ===Step 3=== | ||
| + | |||
| + | Edit the file and update the backup_dev_type to disk under PARAMETERS section. | ||
| + | |||
| + | {| class="wikitable" style="padding-left: auto; color:#FFFFFF; background-color: black; width: 600px; FONT-FAMILY:monospace,monospace; LINE-HEIGHT:15px; white-space: pre-wrap; | ||
| + | | | ||
| + | BR0101I Parameters | ||
| + | |||
| + | Name Value | ||
| + | |||
| + | oracle_sid TS2 | ||
| + | oracle_home /oracle/TS2/112_64 | ||
| + | oracle_profile /oracle/TS2/112_64/dbs/initTS2.ora | ||
| + | sapdata_home /oracle/TS2 | ||
| + | sap_profile /oracle/TS2/112_64/dbs/initTS2.sap | ||
| + | backup_mode PSAPSR3 | ||
| + | backup_type offline | ||
| + | backup_dev_type util_file | ||
| + | system_info orats2/orats2 sap-ora Linux 3.12.49-11-default #1 SMP Wed Nov 11 20:52:43 UTC 2015 (8d714a0) x86_64 | ||
| + | oracle_info TS2 11.2.0.3.0 8192 32 1836601 sap-ora UTF8 UTF8 1850097416 &TS2 | ||
| + | sap_info 740 SAPSR3 | ||
| + | |} | ||
| + | |||
| + | |||
| + | |||
| + | ===Step 4=== | ||
| − | |||
Modify the #SAVED path in the backup id file pointing to the location where your restored files are. | Modify the #SAVED path in the backup id file pointing to the location where your restored files are. | ||
e.g. In our case the files are in /oracle/TS2/sapbackup/bezoagvv/ , so we replaced the path under #SAVED to the path where our files are i.e. /oracle/TS2/sapbackup/bezoagvv/ | e.g. In our case the files are in /oracle/TS2/sapbackup/bezoagvv/ , so we replaced the path under #SAVED to the path where our files are i.e. /oracle/TS2/sapbackup/bezoagvv/ | ||
| Line 113: | Line 114: | ||
| − | ===Step | + | ===Step 5=== |
Run brrestore on SAP Oracle Client and feed it the backup id file. Command is : brrestore -b <backup id> -d disk | Run brrestore on SAP Oracle Client and feed it the backup id file. Command is : brrestore -b <backup id> -d disk | ||
where d is to read the data from disk. | where d is to read the data from disk. | ||
Revision as of 14:34, 5 July 2021
Below documentation shows how to restore SAP R3 data after it has been recovered as normal files using steps as shown in Recovery as Normal Files . Please recover the SAP R3 data files, control file and backup id file as shown below. Once you have the files, please follow the steps to restore.
|
sap-ora:orats2 62> ls -ltr total 22445512 -rw-r--r-- 1 orats2 dba 18605 Oct 22 16:16 bezoagvv.anf -rw-r--r-- 1 orats2 dba 2097160192 Oct 21 10:51 sr3.data1 -rw-r--r-- 1 orats2 dba 2097160192 Oct 21 10:57 sr3.data2 -rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:04 sr3.data3 -rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:10 sr3.data4 -rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:17 sr3.data5 -rw-r--r-- 1 orats2 dba 1614815232 Oct 21 11:23 sr3.data6 -rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:30 sr3740.data1 -rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:37 sr3740.data2 -rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:44 sr3740.data3 -rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:50 sr3740.data4 -rw-r--r-- 1 orats2 dba 1059069952 Oct 21 11:53 sr3740.data5 -rw-r--r-- 1 orats2 dba 20979712 Oct 21 11:53 sr3usr.data1 -rw-r--r-- 1 orats2 dba 734011392 Oct 21 11:55 undo.data1 -rw-r--r-- 1 orats2 dba 209723392 Oct 21 11:56 sysaux.data1 -rw-r--r-- 1 orats2 dba 450895872 Oct 21 11:57 system.data1 -rw-r--r-- 1 orats2 dba 20267008 Oct 21 11:57 cntrlTS2.dbf |
Step 1
Copy/Move the backup id file (file with extension of .anf or .pff ) to default SAP backup location on the SAP R3 server.
i.e. /oracle/<SID>/sapbackup
e.g. bezoagvv.anf is the backup id file in our case and we have restored it to our sapbackup location which is /oracle/TS2/sapbackup/bezoagvv.pff
Step 2
Copy/Move the other files(data file, control file) to the SAP R3 client under a folder with the name of a backup id without the extension.
e.g. We have created a folder under /oracle/TS2/sapbackup named bezoagvv. And we have copied the files already there as shown below.
|
sap-ora:orats2 66> pwd /oracle/TS2/sapbackup sap-ora:orats2 67> cd bezoagvv/ sap-ora:orats2 68> ls -ltr total 22445512 -rw-r--r-- 1 orats2 dba 2097160192 Oct 21 10:51 sr3.data1 -rw-r--r-- 1 orats2 dba 2097160192 Oct 21 10:57 sr3.data2 -rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:04 sr3.data3 -rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:10 sr3.data4 -rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:17 sr3.data5 -rw-r--r-- 1 orats2 dba 1614815232 Oct 21 11:23 sr3.data6 -rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:30 sr3740.data1 -rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:37 sr3740.data2 -rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:44 sr3740.data3 -rw-r--r-- 1 orats2 dba 2097160192 Oct 21 11:50 sr3740.data4 -rw-r--r-- 1 orats2 dba 1059069952 Oct 21 11:53 sr3740.data5 -rw-r--r-- 1 orats2 dba 20979712 Oct 21 11:53 sr3usr.data1 -rw-r--r-- 1 orats2 dba 734011392 Oct 21 11:55 undo.data1 -rw-r--r-- 1 orats2 dba 209723392 Oct 21 11:56 sysaux.data1 -rw-r--r-- 1 orats2 dba 450895872 Oct 21 11:57 system.data1 -rw-r--r-- 1 orats2 dba 20267008 Oct 21 11:57 cntrlTS2.dbf -rw-r--r-- 1 orats2 dba 18605 Oct 22 16:16 bezoagvv.anf |
Step 3
Edit the file and update the backup_dev_type to disk under PARAMETERS section.
|
BR0101I Parameters Name Value oracle_sid TS2 oracle_home /oracle/TS2/112_64 oracle_profile /oracle/TS2/112_64/dbs/initTS2.ora sapdata_home /oracle/TS2 sap_profile /oracle/TS2/112_64/dbs/initTS2.sap backup_mode PSAPSR3 backup_type offline backup_dev_type util_file system_info orats2/orats2 sap-ora Linux 3.12.49-11-default #1 SMP Wed Nov 11 20:52:43 UTC 2015 (8d714a0) x86_64 oracle_info TS2 11.2.0.3.0 8192 32 1836601 sap-ora UTF8 UTF8 1850097416 &TS2 sap_info 740 SAPSR3 |
Step 4
Modify the #SAVED path in the backup id file pointing to the location where your restored files are. e.g. In our case the files are in /oracle/TS2/sapbackup/bezoagvv/ , so we replaced the path under #SAVED to the path where our files are i.e. /oracle/TS2/sapbackup/bezoagvv/
|
BR0280I BRBACKUP time stamp: 2018-10-09 16.59.21
|
 |
Note: Please note that this method will overwrite the existing data files. In case you want to avoid overwrite #FILE section of the backupid file could be modified. Please follow the SAP documentation for more details on this. |
Step 5
Run brrestore on SAP Oracle Client and feed it the backup id file. Command is : brrestore -b <backup id> -d disk where d is to read the data from disk. It has to be run under the database user.
e.g. In our case we ran the command as below. brrestore -b bezoagvv.anf -d disk
You would this warning if you have chose to overwrite the existing data files and other notifications as per your selections.
|
BR0428W File /oracle/TS2/sapdata2/sr3_1/sr3.data1 will be overwritten BR0428W File /oracle/TS2/sapdata2/sr3_2/sr3.data2 will be overwritten BR0428W File /oracle/TS2/sapdata2/sr3_3/sr3.data3 will be overwritten BR0428W File /oracle/TS2/sapdata2/sr3_4/sr3.data4 will be overwritten BR0428W File /oracle/TS2/sapdata2/sr3_5/sr3.data5 will be overwritten BR0428W File /oracle/TS2/sapdata2/sr3_6/sr3.data6 will be overwritten BR0428W File /oracle/TS2/sapdata3/sr3740_1/sr3740.data1 will be overwritten BR0428W File /oracle/TS2/sapdata3/sr3740_2/sr3740.data2 will be overwritten BR0428W File /oracle/TS2/sapdata3/sr3740_3/sr3740.data3 will be overwritten BR0428W File /oracle/TS2/sapdata3/sr3740_4/sr3740.data4 will be overwritten BR0428W File /oracle/TS2/sapdata3/sr3740_5/sr3740.data5 will be overwritten BR0428W File /oracle/TS2/sapdata4/sr3usr_1/sr3usr.data1 will be overwritten BR0428W File /oracle/TS2/sapdata1/undo_1/undo.data1 will be overwritten BR0428W File /oracle/TS2/sapdata1/sysaux_1/sysaux.data1 will be overwritten BR0428W File /oracle/TS2/sapdata1/system_1/system.data1 will be overwritten BR0280I BRRESTORE time stamp: 2020-10-30 15.26.10 BR0407I Restore of database: TS2 BR0408I BRRESTORE action ID: rffaewrc BR0409I BRRESTORE function ID: rsb BR0449I Restore mode: ALL BR0419I Files will be restored from backup: bezoagvv.anf 2018-10-09 16.43.11 BR0416I 15 files found to restore, total size 21900.117 MB BR0424I Files will not be decompressed BR0421I Restore device type: disk BR0420I Files will be restored from directory: /oracle/TS2/sapbackup/bezoagvv R0280I BRRESTORE time stamp: 2020-10-30 15.26.10 BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRRESTORE: c BR0280I BRRESTORE time stamp: 2020-10-30 15.27.08 BR0257I Your reply: 'c' BR0259I Program execution will be continued... BR0351I Restoring /oracle/TS2/sapdata2/sr3_1/sr3.data1 BR0355I from /oracle/TS2/sapbackup/bezoagvv/sr3.data1 ... |
A successful restore would give notifications like below.
|
BR0351I Restoring /oracle/TS2/sapdata2/sr3_1/sr3.data1 BR0355I from /oracle/TS2/sapbackup/bezoagvv/sr3.data1 ...
BR0280I BRRESTORE time stamp: 2020-10-30 15.27.57 BR0418I 1 of 15 files restored - 2000.008 of 21900.117 MB done BR0204I Percentage done: 9.13%, estimated end time: 15:36 BR0001I *****_____________________________________________ |