Pre/Post Requisites for Backup and Restore

Pre-Requisites:
  • Inform Backup Team
  • Check Required Disk/Tape Volume and Recall
  • Perform a Final Backup of Existing target System
  • Capture User Directory entries
  • Capture Client and System Change Settings
  • Capture RFC Connections
  • Capture Logical Systems
  • Capture DB13 Schedule
  • Export Users
  • Export Printers
  • Make Backup Copies of SAP Profiles
  • Capture Active License information
  • Transport Import History
  • Remove the system from CUA
  • Identify successful backup in source to be used for restore
  • Notify Operations of System being down
  • Set Downtime in Nagios
DB ACTIVITIES:
Make Changes in the initBWQ.utl and initBWQ.sap
Legato client is installed on BWQ server and backint.exe has been copied from BWP to BWQ
Remove Precalculation Servers from BWQ
Export Oracle ControlFile
BWQ – Stop SAP and Oracle
BWQ – Clean-up the datafiles in the SAPDATA’s
Copy the  backupfileXXXX.anf from source to target
Start the brrestore
Perform recovery steps and see database is in open state
Put BWQ database in to NOARCHIVELOG mode
Recreate PSAPTEMP tablespace
Reset Oracle System user
Post Requisites:
  • Configure SAP with 0 background Processes
  • Start SAP
  • Disable all RFC Destinations by adding .old to them
  • Suspend all background by running report BTCTRNS1 in SE38
  • Clear all entries from transaction SMQ1 and SMQ2
  • Run SM58 to reorganize
  • Revert no. of Background Processes to normal and restart SAP
  • Run Sick
  • CheckDB
  • Run procedures/scripts in note 547464 to rebuild NOLOGGING Indexes
  • In SM35, delete batch input sessions
  • Apply SAP License
  • Report SAP_INFOCUBE_INDEXES_REPAIR from se38
  • Run SPAD -> Utilities -> For Output Devices -> Assign Server , Set values as:- Output Device = *,Old Spool Server = *, set New Spool Server .Display List,and Convert (check the comment)
  • Add the entries to the services file
  • Run RZ12 to adjust RFC groups. Delete any entries that still exist from the source system
  • Create Logon Groups
  • Delete SecureStorage as per note 1532825
  • Work Bench Organizer Reconfiguration ( reinstall as db copy )
  • Configure TMS
  • Client Configuration from SCC4
  • Delete Source System Profiles and import profiles of active server
  • Configure operation modes
  • Delete Update Failures
  • Scot Setting
  • Reorganize spool
  • Configure Profiles initBWQ.utl and initBWQ.sap  for backups (change client back)
  • Take an online + archive  backup
  • Delete invalid background control objects
  • Logon to client 310 and run BDLS from BWP310 to BWQ310
  • Source System Connectivity – DAVID WILL DO THIS
  • Follow activities as per scenario A1 in OSS note 886102
  • As per OSS note 518426, change settings in txn RSSGPCLA
  • In txn FILE, check and adjust physical path for BW_OLAP_CACHE, BW_OLAP_CACHE_SPAN
  • Check size of PSAPTEMP
  • Confirm that oracle alert logs have been checked and no errors exist.
  • Request David to reschedule background jobs by running BTCTRNS2
  • Request David to fix disabled RFCs as needed and to establish source system connection
  • Add BWQ back into CUA and syncronize users
  • Add Precalculation Servers
  • Notify Operations to start monitoring
  • End Downtime in Nagios

Comments

Post a Comment

Popular posts from this blog

ENQUEUE WORK PROCESS

It is used to lock and unlock the Objects during an update.These locks are displayed in SM12 and Held for longer hours until the transaction is committed or rollback.These locks are issued from a lock table which resides in the main memory of the instance where enqueue process is created/located. Enque Processes are configured by parameter rdisp/wp_no_enq=1. Generally One Enque Process for instance is sufficient,more then one is required in a massive update system. The Lock table size on the memory ranges between 4mb to 100 MB(200 MB in the Net weaver 7.3 Systems ) It is defined by parameter enque/table_size=4 to 200 MB. For 4mb of enqueue table size, the Number of lock/owners/objects/arguments can be restricted up to 3715. Enqueue Flow: User submits the Request for an Update. The Dialog or Background Process Handles the Request Dia or BTC Processes communicates with Enqueue Process and obtains a lock on the record so that no other user has to write access to that r...
Read more

SPOOL WORK PROCESS

Spool Process: It is the Only Process that is used to output the documents to a Printer, fax, email etc.. Spool Work Processes are created by using parameter risp/wp_no_spo=1 it is possible to configure more than one spool work process based on available resources. Spool Process Work Flow: User Submits the request to print a Document. The Dialog Process handles the request and print directly or schedules to print in the background.The Print requests are stored in the TemSe(Temporary Sequential Files) Temporary Sequential Files are stored either at File System or at database Level which is defined by parameter rspo/store_location. rspo/store_location=”G” or ‘DB’ G means global directory stores the TEMSE in /usr/sap/SID/SYS/global db mean the Tables TST01 and TST03.(TST01 Contains Print Attributes and TST03 Contains the Spool Data to be Printed) Due to Spool in DB the DB Size Increases, as a Result, the backup time increases and Tapes may not fit with the data for S...
Read more

DIALOG PROCESS

Dialog Process: It is the only process that is used to communicate with end users Interactively using Classic GUI or Through RFC or through Http Protocol. The Average Response Time for each dialog step is 600 ms.it is displayed through ST03n Each Process can execute up to a maximum runtime of 600 seconds.if any process goes beyond this time an additional time of 60 seconds is given and the process is timed out.(ST22)(it is not mandatory to allocate additional 60 seconds Each Process Serves 5-10 users.(Calculated based on ST07) Each Process Requires 75mb to 300 mb Memory Each Process can Handle the requests that are initiated for background, spool & update and update them in temporary tables. Dialog Process is not restricted to a User and Users are not restricted to a process which is referred as process multiplexing Parameters to configure dialog processes is rdisp/wp_no_dia There should be at least minimum two dialog processes and maximum up to 100 processes. The ...
Read more