Skip to Content
avatar image
Former Member

Disaster Recovery in Windows 2003/Cluster, SQL 2000 and R3

Hi,

Can someone share experience/knowledge of disaster recovery scenarios in MSCS/SQL Server/SAP. One of our customer has R3/SQL Server2000/Win 2003 (Cluster).

We would like to evaluate best possible options for the Disaster Recovery which are supported by SAP.

We have thought about

1. Log shipping

2. Standby Database

3. Restore backup on new cluster

4. Homogeneous System copy.

We do not want to go for first two and would like to explore on 3rd and 4th option.

Any links to documents/blogs will be helpful.

Thanks,

Manoj

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Best Answer
    Sep 16, 2009 at 12:54 PM

    > We would like to evaluate best possible options for the Disaster Recovery which are supported by SAP.

    > 1. Log shipping

    > 2. Standby Database

    > 3. Restore backup on new cluster

    > 4. Homogeneous System copy.

    >

    > We do not want to go for first two and would like to explore on 3rd and 4th option.

    3 and 4 are technically the same, you install a new system and restore the database.

    The question is: what is the requirement from you client (how much downtime etc.)?

    Markus

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hello, I'm doing a "Plant ECC6 to do a test disatre / Recovery.

      During the installation, I would use the same <sidadm> existing as it is in the PRD.

      If I tell you to install it during the same <sidadm> it will overwrite what already exists, or do I just enter the password of existing <sidadm>?

      Regards

      Guilhermino

  • avatar image
    Former Member
    Sep 17, 2009 at 04:47 PM

    We use our QA system as our DR point... as our QA environment is in another location and it is an exact replica of what we would need. Both QA and PRD are a Win 2003 EE R2 x64 2 node cluster. We then could just restore the database from tape and then do a SID change. The do some fun DNS stuff and we're done. Basically it just allows you to get around having to reinstall everything.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Markus Doehr
      The question is: what is your goal and how much time do you have?

      Prepare exact replica image of production server from backup. We are in simulation stage so we have enough time to set-up the process. But in case of disaster we want to spend as much as less possible time on the recovery.

      Are you intending to build a DR cluster or do you just want to build up a (single) system so people can work?

      We are planning to build as is scenario from backups/tapes/ASR disk (Whatever required) but if this does not work then we may need to opt for single system in DR situation. Any suggestions are most welcome.

  • avatar image
    Former Member
    May 28, 2010 at 02:42 PM

    Hi Manoj,

    For our clustered system we use two logical steps for the recovery (in a DR 'data center blown away' scenario). First we restore the two cluster nodes using disk images of those nodes (using a software package like Acronis). Then we create new storage from the SAN side, assign that storage to two nodes, restore that SAN storage, and/or restore from a DB backup.

    I don't know if that is helpful but that is the scenario we use for a restore.

    J. Haynes

    Add comment
    10|10000 characters needed characters exceeded