Ansicht
Dokumentation
05765 - Disaster Recovery only using backup tapes for an AS/400 SAP system
Vendor Master (General Section) BAL_S_LOG - Application Log: Log header dataThis documentation is copyright by SAP AG.
Disaster Recovery only using backup tapes for an AS/400 SAP system
This is our RESTORE process which mirrors/compliments our BACKUP processThis assumes you are starting with an empty iSeries
You must have FULL SYSTEM SAVE (GO SAVE 21) from last O/S upgrade or CUME apply
Also, most recent SAP nightly SAVE
These instructions do not include a full point in time recovery (using
receivers)
This HAS NOT been 100% tested (yet) - but very close
RESTORE STEPS
ï§ Restore all IBM LIC & Operating System - Using tape backup from last âGo
SAVE Option 21â â Follow Instructions named
These instructions assume that you are starting with an AS/400 which minimally
has the LIC & Operating System installed; the steps below will restore all
objects necessary for the Production SAP DB.
AS/400 PROFILE PASSWORDS
0Make sure all SAP AS/400 PROFILE PASSWORDS on BOX match the rest of the
landscape
CLEAR EXISTING SAP DATA LIBRARY
0Signon Backup Box as QSECOFR & GIVE â*ALLOBJâ AUTHORITY TO <SID>OFR
0Signon as <SID>OFR
0Issue a SBMJOB for command CLRLIB R3<SID>DATA
RESTORE IFS INFRASTRUCTURE
SEQUENCE #1 ON NIGHTLY SAVE TAPE
0SBMJOB CMD(RST DEV('/QSYS.LIB/TAP01.DEVD') OBJ(('/sapmnt/trans/config')
('/sapmnt/<SID>') ('/usr/sap/<SID>')) OUTPUT(*PRINT) ENDOPT(*UNLOAD)
INFTYPE(*ALL) ALWOBJDIF(*ALL)) JOB(IFSSAP<SID>) JOBQ(QSYSNOMAX) HOLD(*YES)
RESTORE IFS INFRASTRUCTURE
SEQUENCE #1 ON NIGHTLY BOX /SAPMNT/TRANS SAVE TAPE
0SBMJOB CMD(RST DEV('/QSYS.LIB/TAP01.DEVD') OBJ(('/sapmnt/trans'))
OUTPUT(*PRINT) ENDOPT(*UNLOAD) INFTYPE(*ALL) ALWOBJDIF(*ALL)) JOB(RSTSAPMNT)
JOBQ(QSYSNOMAX) HOLD(*YES)
RESTORE MISC LIBRARIES (if needed)
SAVED NIGHTLY from BOX
SEQUENCE #2 ON NIGHTLY SAVE TAPE - LIBRARY BHCFTP
0SBMJOB CMD(RSTLIB SAVLIB(BHCFTP) DEV(TAP01) ENDOPT(*LEAVE) MBROPT(*ALL)
ALWOBJDIF(*ALL) OUTPUT(*PRINT)) JOB(RSTBHCFTP) JOBQ(QBATCH)
SEQUENCE #3 ON NIGHTLY SAVE TAPE - LIBRARY BHCMGTDB1
0SBMJOB CMD(RSTLIB SAVLIB(BHCMGTDB1) DEV(TAP01) ENDOPT(*LEAVE) MBROPT(*ALL)
ALWOBJDIF(*ALL) OUTPUT(*PRINT)) JOB(RSTBHCMGT) JOBQ(QBATCH)
SEQUENCE #4 ON NIGHTLY SAVE TAPE - LIBRARY BHCTEMP
0SBMJOB CMD(RSTLIB SAVLIB(BHCTEMP) DEV(TAP01) ENDOPT(*LEAVE) MBROPT(*ALL)
ALWOBJDIF(*ALL) OUTPUT(*PRINT)) JOB(RSTBHCTMP) JOBQ(QBATCH)
SEQUENCE #5 ON NIGHTLY SAVE TAPE - LIBRARY QGPL
0SBMJOB CMD(RSTLIB SAVLIB(QGPL) DEV(TAP01) ENDOPT(*LEAVE) MBROPT(*ALL)
ALWOBJDIF(*ALL) OUTPUT(*PRINT)) JOB(RSTQGPL) JOBQ(QBATCH)
CREATE LIBRARY FOR SAP JOURNAL RECEIVERS
CREATE LIBRARY R3<SID>JRN
0The only objects contained in library R3<SID>JRN are the journal receivers;
therefore just CRTLIB R3<SID>JRN; CHGOBJOWN QSYS/R3<SID>JRN LIB NEWOWN(R3OWNER)
â authority should be R3OWNER=*ALL ; *PUBLIC=*EXCLUDE
RESTORE SAP LIBRARIES which are SAVED NIGHTLY from BOX
SEQUENCE #6 ON NIGHTLY SAVE TAPE - LIBRARY KERNEL R3P00<nnn>
0SBMJOB CMD(RSTLIB SAVLIB(R3P00<nnn>) DEV(TAP01) ENDOPT(*LEAVE) MBROPT(*ALL)
ALWOBJDIF(*ALL) OUTPUT(*PRINT)) JOB(RSTKERNEL) JOBQ(QBATCH)
SEQUENCE #7 ON NIGHTLY SAVE TAPE - LIBRARY R3<SID>400
0SBMJOB CMD(RSTLIB SAVLIB(R3<SID>400) DEV(TAP01) ENDOPT(*LEAVE) MBROPT(*ALL)
ALWOBJDIF(*ALL) OUTPUT(*PRINT)) JOB(RST<SID>400) JOBQ(QBATCH)
SEQUENCE #8 ON NIGHTLY SAVE TAPE - LIBRARY R3WRK00
0SBMJOB CMD(RSTLIB SAVLIB(R3WRK00) DEV(TAP01) ENDOPT(*LEAVE) MBROPT(*ALL)
ALWOBJDIF(*ALL) OUTPUT(*PRINT)) JOB(RSTWRK00) JOBQ(QBATCH)
SEQUENCE #9 ON NIGHTLY SAVE TAPE - LIBRARY R3400
0SBMJOB CMD(RSTLIB SAVLIB(R3400) DEV(TAP01) ENDOPT(*LEAVE) MBROPT(*ALL)
ALWOBJDIF(*ALL) OUTPUT(*PRINT)) JOB(RSTR3400) JOBQ(QBATCH)
SEQUENCE #10 ON NIGHTLY SAVE TAPE - LIBRARY R3<SID>DATA
0SBMJOB CMD(RSTLIB SAVLIB(R3<SID>DATA) DEV(TAP01) ENDOPT(*REWIND) MBROPT(*ALL)
ALWOBJDIF(*ALL) OUTPUT(*PRINT)) JOB(R3<SID>DATA) JOBQ(QBATCH)
MISC TASKS
GET A FRESH RECEIVER ATTACHED
0CHGJRN JRN(R3<SID>DATA/QSQJRN) JRNRCV(*GEN)
CHANGE SAP DATA AREA TO REFLECT PROPER BOXNAME
0CHGDTAARA DTAARA(R3<SID>400/R3_00) VALUE(DVEBMGS<BOX>)
CLEANUP KERNEL AUTHORITIES
0As QSECOFR
0CHGOBJOWN OBJ(R3P00<nnn>) OBJTYPE(*LIB) NEWOWN(R3OWNER)
0CALL PGM(R3P00<nnn>/FIXR3OWNS) PARM(R3P00nnn *ALL) No single quotes around parm
0As <SID>OFR
0ADDLIBLE LIB(<kernel_lib>)
0APYR3KRN SID(<SID>) KRNLIB(R3P00<nnn>)
TRANSPORT INFRASTRUCTURE
0Make sure /usr/sap/trans is a symbolic link to /sapmnt/trans â if not addlnk
'/sapmnt/trans' '/usr/sap/trans'
START SAP
0STARTSAP
Doreen Anderson
Ball Horticultural Company
dandersoZb...
(630) 231-3600 x3214
-----Original Message-----
From: mattmilne [mailto:mattmilneZe...]
Sent: Tuesday, April 16, 2002 1:54 PM
To: DoNotReply@consolut.eu
Subject: Disaster Recovery only using backup tapes for an AS/400
SAP system
Hi
Some of the group have asked me about how a company recovers their
SAP system from just backup tapes. So I want to start a thread on
disaster recovery. i.e. what do you do when all you have left is a
SAVR3SYS backup (or just the libraries and IFS directories on tape)
and a virgin AS/400 with no SAP installed and no SAP install disks.
It is probably fairly easy to get 4.6c install disks quickly but many
sites are are at earlier releases and may not be able to wait for 3.x
or early 4.x install CD's. If they are available then one could do a
scratch install and then a database copy.
So lets assume that we have an as/400 with no trace of SAP and a full
SAVR3SYS backup (or equivalent)including
/usr/sap/<sid> IFS files
R3<sid>data lib
Kernel lib
R3<sid>400 lib
R3WRK<instance number>
R3QTEMP lib
R3SYS lib
R3400 lib ( only holds SAPOSCOL objects)
We can create the JRN lib and ignore the SQL package libraries. We
can set up the TMS later.
My thought would be that you would have to load these libraries and
directories. Then CFGTCP to set up the TCP-IP configuration to the
SAP standard, probably make the machine look like the (now deceased)
original box. Volker and Jim Doll have given some information about
what is required to set the TCP-IP services.
And then run
CRTR3USR user(*INST) sid(xxx) instance(nn)
where xxx is your <sid> and nn is your instance number
and then run
CRTR3INST sid(xxx)
to create the system objects.
Has anyone had to go through this exercise in real life ?
Given some of the stuff happening in the world right now it does no
harm to have a "worst case plan" on file somewhere.
Matt Milne
Freelance SAP AS/400 BASIS consultant
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Your use of consolut is subject to http://www.consolut.net
Durban Tours - Südafrika Safari
ROGBILLS - Synchronize billing plans rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
Length: 8194 Date: 20240329 Time: 072836 sap01-206 ( 3 ms )