on 07-01-2009 10:36 PM
We have been running SAP for 11 years and ran annual disaster recovery exercises with success.
Have recently moved our SAP solution to new OS/DB platform Windows 2003 w/ MS SQL Server. The responsibility of performing the DR exercise has shifted from the Basis team to our Infrastructure team.
Going thru some large growing pains shifting the disaster recovery exercise and execution. We cannot be unique here so was wondering if anyone has a skeletal script that they'd be willing to share showing the steps taken to restore / lay down their SAP solution (preferably a dual stack ABAP/java -- eg one of the following ECC/PI/BI) during a disaster recovery exercise (cold site)
Hope this makes sense -- latest in-house testing of process (pre DR exercise to be performed at cold site) is showing that there's some fundamental things missing (eg environment variables, <sid>adm user for DB)
Thank you in advance
Doreen
Without knowing how your system is set up it's hard to tell.
Just keep in mind that "renaming" Windows instances (such as hostname changes) are not as easy as on Unix based platforms.
What have you been trying and what are your problems?
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not sure exactly what you mean by "how we are setup" -- are SAP environment variables and userid's located in a configurable area based on "how we are setup"?
Thought those would be fundamental items recovered when restoring a server/system; assuming we are running Windows Server 2003 w/MS SQL Server 2005 DB and NW 7.0?
We are running MSCS and replicated enqueue -- BUT in a DR scenario, we're not planning for MSCS
We are not trying to change server / hostnames as that wouldn't occur during a disaster scenario.
Doreen
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.