First, you need a duplicate physical landscape as the production. Depending on the landscape, this could take anywhere from a month to sometimes 1/4 year. This includes storage, storage design, physical server procurement, etc. Better thing to do is, make this your TEST environment. This way, your TEST environment has the same hardware, making for more accurate stress testing results and this environment will always be HOT and you won't have to deal with any COLD server surprises.
Second, you need to make a list of technologies. SAP ABAP, SAP JAVA, O/S, Database, external application dependencies. VPN? SAP Frame Relay? Etc. You need to think of SAP as a whole.
Third, you need to scope out the DR project. Meaning, does all required business interface needs to failover at well? What about up / down stream systems? I suggest that you limit your scope to SAP only for your first exercise.
Fourth, test the failover. Try it on the test system or sandbox, make sure what you are doing works.
For database, especially large data bases, make sure primary and DR site has enough WAN bandwidth for proper log shipping. Create a log shipping alert if necessary - nothing is worst than a real disaster then realizing that your DR site is 12 hours out-of-sync.
For SAP application, try looking into virtualizing the instance names. Renaming physical servers is complicated, but remapping WINS/DNS is not.
For the DR here inhouse, overall planning took about 6 months. This includes server builds. We are on our 5th year performing the DR procedures, on our real life production environment. Every year we learn something - as it is a constant learning process.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.