Disaster Recovery in SAP ERP2005-SR1 ABAP- MSSQL.

Hello.
I am in the process of create a DR server for our SAP ERP2005-SR1 running in SQL2000 with a latest SP patch. This DR server (standby server) is going to have the same SID as my production system, but on a difference host with a difference IP address. I am planning to use a domain installation method to install this DR server. Could someone please provide me with the following information:
1. Can this be done with same <SYSID> but on the difference host, difference IP address but using domain installation method under Netweaver 2004s environment???
2. I am going to use the same <sysid>adm account to perform the same installation, is it possible???
3. Do I need to shutdown production system while I install SAP ERP 2005 on my DR server????
I hope someone could help me with the answer or provide me with the reference documentation on this issue.
Thanks in advance.
PL.

Hello Phuong,
Did similar thing for other purposes...
1. Can this be done with same <SYSID> but on the difference host, difference IP address but using domain installation method under Netweaver 2004s environment???
yes
2. I am going to use the same <sysid>adm account to perform the same installation, is it possible???
<domain>/administrator works. Not sure of <sysid>adm.
3. Do I need to shutdown production system while I install SAP ERP 2005 on my DR server????
Should not have to.
It is a lot of things to consider for a full DR solution. I would start with a Sandbox system before doing anything on PRD...
Best regards,
Victor

Similar Messages

Disaster Recovery For SAP ECC 6.0 On Oracle

Hi All,
This is our infrastructure
Windows 2003 Server
SAP ECC 6.0
Oracle 10
Legato Networker Client / Library
Actually our Backup Strategy is to do an Online Backup Every Night from monday to saturday. We want to test our backup by doing a Restore. We are assuming a complete loss of the system including hardware.
What we do:
1. Install the SAP System on a new host with the same hardware characteristic of the source system.
2. Install & Configure the legato utility.
3. Copy the E:\oracle\MIS\sapbackup\ directory from the source system to the test system.
4. Them we put the database in mount mode.
5. Execute the command: brrestore -b bdyxwoqv.fnf -m full (bdyxwoqv.fnf-> Full Online Backup that was executed without problems).
It gives the following errors:
BR0386E File 'F:\ORACLE\MIS\SAPDATA2\SR3_10\SR3.DATA10' reported as not found by
backup utility
BR0386E File 'F:\ORACLE\MIS\SAPDATA3\SR3700_9\SR3700.DATA9' reported as not foun
d by backup utility
BR0280I BRRESTORE time stamp: 2008-10-01 17.45.19
BR0279E Return code from 'backint -u MIS -f restore -i E:\oracle\MIS\sapbackup\.
rdyybrzp.lst -t file -p E:\oracle\MIS\102\database\initMIS.utl': 2
BR0374E 0 of 63 files restored by backup utility
BR0280I BRRESTORE time stamp: 2008-10-01 17.45.19
BR0231E Backup utility call failed
BR0406I End of file restore: rdyybrzp.rsb 2008-10-01 17.45.19
BR0280I BRRESTORE time stamp: 2008-10-01 17.45.19
BR0404I BRRESTORE terminated with errors
Since this is a new SAP system it never will find the SAPDATA files because they where on the source system and this is a new test system.
We found the following note:
96848 Disaster recovery for SAP R/3 on Oracle
But this note is for SAP R/3 no for SAP ECC!
It explain that you have to install your SAP system with the System Copy Method (is this the only way??).
2.) Installation of the R/3 System
The installation of SAP software contains the software installation of the database. The initial SAP database should be created again but the SAP data should not be loaded.
Install the SAP system with the Oracle-specific system copy method, which is based on backup/restore. This method is described in the system copy guide for your Product/Release. Refer to Note 659509 for products that are based on Web AS.
3.) Modification of the installation
Above all, you must take into account the mounted file systems at the time of the loss. If necessary create new SAPDATA directories (mount points). These generally identify a disk or a logical storage area (logical volume).
Are we working in the right way? maybe there is a formal procedure to do a Restore from an Online backup when you complete loss your system.
Please some tips.
Best Regards,
Erick Ilarraza

Hi Eric,
Thanks a lot for your reply, I will follow the Note 96848 Disaster recovery for SAP R/3 on ORACLE point 5.
5.) Restore profile and log files, as you sayed in case of disaster we will lost our "source" system.
On the other hand to configure the legato client we take care of the name of the server, we configured the .sap, .cfg and .utl files so in theory the restore will be done on the new test system since we run the brrestore command from that system.
Officially there is not a documentation from SAP to do a Restore from a Online Backup with SAP ECC, SAP Netweaver (ABAP / ABAP + Java). You only have the 96848 note??? I found the following information:
http://help.sap.com/saphelp_nw70/helpdata/en/65/cade3bd0c8545ee10000000a114084/frameset.htm
But there is not a official procedure like a System Copy Guide or Installation Guide.
Best Regards,
Erick Ilarraza

Disaster Recovery Test

Hi,
Can anybody please guide, who'll play the major role in "Disaster Recovery Test"
like functional / basis / abap etc,,,

Hello Mahesh
Everybody has to play a major role , first Basis has to take action then abaper and then for testing Functional people required to put their effort.here is brief excerpt from an article regarding "Disaster recovery for SAP".
It will give all of us an idea about Disater recovery.
When you have your SAP system installed, you don't have a disaster recovery solution.
"SAP has standard methodologies for doing backups and restoring the SAP environment, but there's nothing built into their application that specifically targets disaster recovery,"
In other words, SAP tells you very explicitly what you need to protect, but you're on your own in figuring out how to make it happen. It is common practice among third-party solution providers to ask about disaster recovery, but if you're doing your own thing it is important to be aware of the need for a disaster recovery solution.
Outsourcing vs. building a secondary site:
There are two ways to go about setting up your disaster recovery solution: Outsource or build your own secondary site. Outsourcing may be more convenient and less expensive, especially for smaller companies on a tight budget. Simply approach the outsourcing company with your needs, and they will pretty much take it from there. Graap likens it to an insurance policy, where you pay a premium on an ongoing basis for the security.
If you decide to outsource, ask colleagues for recommendations and spend some time researching prices, which can vary a lot. But make sure the outsourcer can step up to the plate in the unlikely event that you need their services.
Building your own secondary site requires a larger investment up front but the leaves you in full control of your contingency plans rather than be at the mercy of an outsourcing company. If your outsourcing provider falls through for some reason -- such as being in the same disaster zone as your main office during an earthquake for example -- you're in trouble. When building your own site, you can prepare for more scenarios and place it far enough away from your main office.
High availability vs. cost:
Specialists say one of the most important questions to consider is availability and how quickly you need to get your systems back online. The difference between getting back online in 10 minutes or three days could be millions of dollars, so you want to make sure you get just the right solution for your company.
Around-the-clock availability will require mirroring content across two sites in real-time. This enables you to do an instant failover with little or no downtime, rather than force you to physically move from the office to a backup site with a stack of tapes.
Regardless of whether you outsource or set up your own site, a high availability solution is expensive.
"But if that is what it takes to keep your business from going under, it's worth every penny of it".
An added benefit of having a high availability solution is that you can avoid maintenance downtime by working on one server while letting the other handle all traffic. In theory, this leaves a window of risk, but most maintenance tasks, such as backups, can be cancelled if need be.
One consideration for mirroring data is the bandwidth to the secondary site. Replicating data in real-time requires enough capacity to handle it without hitches. Also, a secondary site will require the same disk space as your regular servers. You can probably get away with a smaller and cheaper system, but you still need enough storage space to match your primary servers.
Whatever the choice for disaster recovery, it is vital that both the technology and the business departments know about the plan ahead of time.
Testing your solution:
Ok, so you have a disaster recovery solution in place. Great, you're home free, right? Not quite. It must be tested continuously it to make sure it works in real life. Sometimes management can be reluctant to spend the money for a real test, or perhaps there are pressing deadlines to keep but it should be tested one or two times a year.
Many people who build good plans let them sit collecting dust for years, at which point half the key people in the plan have left or changed positions.Update the names, phone numbers and other vital information frequently and test them, he said. It is for the same reason you do fire drills: When the real thing strikes, there's no room for error.
In testing, consider different scenarios and the physical steps needed to get the data center up and running. For example, many disaster recovery solutions require at least parts of a staff to get on a plane and physically move to the secondary location. But September 11 showed how that is not easy when all planes are grounded.
Costly but vital:
Disaster recovery is not cheap, and it requires lots of testing to stay current, but it could save your critical data.
"Any customer who makes an investment in SAP is purchasing an enterprise-class application, and as such really should have this level of protection for their business". "I can't imagine why anybody would not have an interest in disaster recovery."
Regards
Yogesh

Disaster recovery - Oracle

Hello!
Is there some simple step-by-step guide for disaster recovery of Enterprise 4.7, WAS 620, Oracle?
I am trying to create a disaster recovery scenario for our production based on DB13 backup and brrestore (I am doing backup to disk). The backup works fine and I have got the new machine to play with restore.
I am not very experienced BC and here's how my unsuccessfull try went on:
1. Installed the new SAP system on the "playground" machine with the file structure same as on production (the system was installed properly, I was able to log-on)
2. Stopped the new system and its database
3. messed a little with init<DBID>.sap until brrestore went on
4. brrestore-ed from the backed-up production files (the entire 'sapbackup' folder):
brrestore -b bdrfydrx.and -m full
; the brrestore run successfully and the files on the new system were replaced by the backed-up production files.
5. Attempted to run SAP: the processes were green for about 1 minute; however, I wasn't able to log on, and then the disp+work died (went not yellow, but rather grey)
6. Stopped the services
7. Replaced kernel with the production kernel (copied the entire 'usr' folder, shared the 'usr\sap' folder as saploc and sapmnt)
8. Attempt to start the services - it got even worse: the SAP<SAPSID>_<SYSNO> service wouldn't start. The popup says that the service returns no error, but it's rather a Windows or internal service error.
And now I'm stuck. Please help! The SAP notes on this matter (such as 96848 - Disaster recovery for SAP R/3 on Oracle) have endless iterations of reference notes, and are not very tutorial-organized. The Installation Guide "Homogeneous and Heterogeneous System Copy..." includes only copy based on running SAPinst to export the database, not on backup/restore.
Is there something better?
Thanks in advance!
Kind regards,
Igor
P.S. If I survive, I promise to write a "restore for dummies" weblog on this.

Hello,
Here is the guide:
http://help.sap.com/saphelp_nw04s/helpdata/en/72/96d34c435c3c4ca5894749ef1435ac/frameset.htm
Also,
I thought after you restroed the brrestore backup, you need to recover you database by restoring all your redo log files to the target server and issuing the command in sqlplus:
recover database until cancel auto;
Can you paste your alert log ?
Regards,
Siddhesh

Disaster recovery in ECC6 ABAP plus Java

Hi all,
This is my first experience working with ECC6 ABAP plus Java. The normal backup we do using brbackup is taking the backup of the ABAP database and the J2EE information too. There is also a front end of the J2EE install. If we try to just restore the database to another system the J2EE front end will not communicate with the J2EE instance in the database as they are different.
Now the question is how to back it up and restore it. The backup we are doing at this point is good for local database recovery but if our Operating system dies for some reason then what would be the form of recovery.
In short I need to know if we can do the front end J2EE backup as well along with the whole database backup containing ABAP and Java and do the recovery on some other system to test the disaster recovery scenario.
If there is no solution then system export is an option thats having all the information of the DB and the front end too... but its not always possible to do the system export as it takes too long.
Please advise.
Thanks.

follow http://help.sap.com/saphelp_nw2004s/helpdata/en/e6/e8f4167f79414c883ed37464773824/frameset.htm in this Backing up and Restoring AS Java for AS-Java.
Cheers,
-Sunil

SAP NetWeaver 7.01 SR1 ABAP Trial Version Installation Fails

Hello,
While doing SAP NetWeaver 7.01 SR1 ABAP Trial Version Installation, I am getting below error message:
~
An error occurred while processing option SAP NetWeaver 7.0 SR1 including Enhancement Package 1 > SAP Application Server ABAP > MaxDB > Central System > Central System( Last error reported by the step :
The subkey 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BlackICE' does not exist on the 'localhost' host.). You can now:
Choose Retry to repeat the current step.
Choose View Log to get more information about the error.
Stop the option and continue with it later.
Log files are written to C:\Program Files/sapinst_instdir/NW701/AS-ABAP/ADA/CENTRAL/.
~
I have checked regedt32 and found the entry 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BlackICE' which is having detail (Default) REG_SZ (Value not set). When I double click on (Default) it says "Can not edit: Error reading the value's content"
~
In Services, "BlackICE" service is "Started" and Statup Type is "Automatic" and Logon As "Local System".
I have Microsoft Windows XP Professional Version 2002 Service Pack 2 and 3 GB RAM. I am using user which is part of "Administrator" group.
Can someone help what could be the issue and how I can resolve it so that can complete the Installation.
Appreciate your great help.

Hi Pedro,
could you fix the error?
I'm installing and I have the same problem.
An error occurred while processing option SAP NetWeaver 7.0 SR1 including Enhancement Package 1 > SAP Application Server ABAP > MaxDB > Central System > Central System( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.). You can now:
Choose Retry to repeat the current step.
Choose View Log to get more information about the error.
Stop the option and continue with it later.
Log files are written to C:\Archivos de programa/sapinst_instdir/NW701/AS-ABAP/ADA/CENTRAL/.
Thanks.
Anibal

Planning Disaster Recovery Site for SAP ERP ECC 6.0

Dear All,
I am planning for DR ( Disaster Recovery ) Site. Our current environment is
Production Site
OS        : AIX 5.3
DB        : IBM DB2      version 8.2
SAP      : SAP ERP 6.0 ECC 6
Disaster Recovery Site
OS        : AIX 6.1
DB        : IBM DB2      version 9.5
SAP      : SAP ERP 6.0 ECC 6
I have following confusion in planning the solution.
1 - If I export the data at db level from production site and import that data in DR Site ... than DR Site will be equivalent to Production Site or not.
2 - if answer of point 1 is yes then for SAP DR ... HADR is the best solution or there is any other better solution exist.
regards
Syed Saifuddin

Hello Syed,
If you export from the prod db and import into the disastor recover db then they will be the same provided that SAP environment is all the same. I would recommend that you update the prod side to the same db2 release and fixpack level as soon as possible though as 9.5 (or even better 9.7) has some advanced features that make administration alot easier and save much space.
HADR would be the best setup for disaster recovery in db6 environment.
Check the following documentation which should answer most of your queries.
SAP Note 960843 # DB6:Installation SA MP
"High Availability and Disaster Recovery Options for DB2 on Linux, UNIX,
and Windows"
http://www.redbooks.ibm.com/redbooks/pdfs/sg247363.pdf
"Data Recovery and High Availability Guide and Reference"
http://publibfp.boulder.ibm.com/epubs/pdf/c1042280.pdf
Please update if questions remain unanswered.
Regards,
Paul

Disaster Recovery server for SAP and HACMP Cluster script for SAP ECC 6.0

Hi,
I need document for Disaster Recovery server for SAP? I have to configure the DR Server If you have, please share this document if possible.
Have you any cluster script ( HACMP Cluster script for SAP ECC 6.0 ) ?
Thanks & Regards,

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>?

SAP Solution Manager SR1 with MSSQL on W2K3 IA32 - Problem with Kernel

Hello,
we are implementing a sandbox in order to test the SAP Solution Manager 4.0 SR1 with MSSQL on W2K3 IA32. Therefore we ordered the installation CD for the above mentioned configuration. Instead of getting the SAP NETWEAVER Kernel SR1 we got SR2. Now we have the problem, that the installation program SAPINST is requesting the SR1- Kernel.
Unforunately the SR1-Kernel seems no longer available in the download section.
It would be fine to get a suggestion how to solve the problem.
Thanks
Best regards
Ralf Richter ([email protected])

Hi Andreas,
thanks for the hint, I have already checked the LABEL.ASC. I have no LABEL.ASC-Key for the SAP Netweaver 2004s SR1, so it would be a possibilty to substitue this key. But neverhteless, I think, there should be another official procedure in order to use the SR2 instead of the old SR1. I have contacted Klaus Billing at SAP as recommended in the OSS Note 918078. Best regards. Ralf R.

SAP Netweaver 7.10 Disaster Recovery

Hi all,
I was testing some disaster recovery procedure for one of my SAP systems which has an Oracle 10g backend and is installed on RHEL 5.4 64bit
Practically I backed up and restored all the directories:
/usr/sap/*
/sapmnt/*
/oracle/<SID>/* (only directories containing binaries and log directories)
passwd, shadow, group and gshadow files (so SAP users and groups have the same configs and ids)
home directories of users <sid>adm and ora<mvd>
hostnames also are identical
And after that through the HP DataProtector SAP agent I restored the database and all the archived logs.
I have arranged to start the Database but when trying to restart sap instance the /startsap_DVEBMGS10.log file gives the following:
(3960) Local: rm -f ms.sapMVD_DVEBMGS10
(3961) Local: ln -s -f /usr/sap/MVD/DVEBMGS10/exe/msg_server ms.sapMVD_DVEBMGS10
(3962) Local: rm -f dw.sapMVD_DVEBMGS10
(3963) Local: ln -s -f /usr/sap/MVD/DVEBMGS10/exe/dispwork dw.sapMVD_DVEBMGS10+
(3964) Local: rm -f co.sapMVD_DVEBMGS10
(3965) Local: ln -s -f /usr/sap/MVD/DVEBMGS10/exe/rslgcoll co.sapMVD_DVEBMGS10
(3966) Local: rm -f se.sapMVD_DVEBMGS10
(3967) Local: ln -s -f /usr/sap/MVD/DVEBMGS10/exe/rslgsend se.sapMVD_DVEBMGS10
(3968) Local: rm -f ig.sapMVD_DVEBMGS10
(3969) Local: ln -s -f /usr/sap/MVD/DVEBMGS10/exe/igswd_mt ig.sapMVD_DVEBMGS10
Starting Programs
18.11.2010 18:08:46
ShmDetach
OK
(3973) Starting: local ms.sapMVD_DVEBMGS10 pf=/usr/sap/MVD/SYS/profile/MVD_DVEBM                                                                                GS10_devserver
(3974) Starting: local dw.sapMVD_DVEBMGS10 pf=/usr/sap/MVD/SYS/profile/MVD_DVEBM                                                                                GS10_devserver
(3975) Starting: local co.sapMVD_DVEBMGS10 pf=/usr/sap/MVD/SYS/profile/MVD_DVEBM                                                                                GS10_devserver -F
(3976) Starting: local se.sapMVD_DVEBMGS10 pf=/usr/sap/MVD/SYS/profile/MVD_DVEBM                                                                                GS10_devserver -F
(3977) Starting: local ig.sapMVD_DVEBMGS10 -mode=profile pf=/usr/sap/MVD/SYS/pro                                                                                file/MVD_DVEBMGS10_devserver
(3946) Waiting for Child Processes to terminate.
(3946) **** 2010/11/18 18:08:46 Child 3973 terminated with Status 0 . ****
(3973) **** 2010/11/18 18:08:46 No RestartProgram command for program 0 ****
(3946) **** 2010/11/18 18:08:59 Child 3974 died due to Signal 11 . ****
(3974) **** 2010/11/18 18:08:59 No RestartProgram command for program 1 ****
Instance on host devserver started
Just to mention that in terms of memory the original machine has 8GB of RAM and 16 logical CPU meanwhile the virtual machine where I am trying to perform the restore has only 2GB and 2 logical CPU
Please help because I am kind of stuck.
Best Regards,
Drini

Hello,
I had forgotten to replicate the /etc/services file to the new machine.
Now the log files display only failure for the dispatcher process
Execute Pre-Startup Commands
(18842) Local: /usr/sap/MVD/SYS/exe/run/sapcpe pf=/usr/sap/MVD/SYS/profile/MVD_DVEBMGS10_devserver
(18852) Local: /usr/sap/MVD/SYS/exe/run/sapcpe pf=/usr/sap/MVD/SYS/profile/MVD_DVEBMGS10_devserver list:/usr/sap/MVD/SYS/exe/run/sapcrypto.lst
(18854) Local: /usr/sap/MVD/DVEBMGS10/exe/sapmscsa pf=/usr/sap/MVD/SYS/profile/MVD_DVEBMGS10_devserver -n
/usr/sap/MVD/DVEBMGS10/exe/sapmscsa: SCSA is attached and useable.
/usr/sap/MVD/DVEBMGS10/exe/sapmscsa: finished.
(18855) Local: rm -f ms.sapMVD_DVEBMGS10
(18856) Local: ln -s -f /usr/sap/MVD/DVEBMGS10/exe/msg_server ms.sapMVD_DVEBMGS10
(18857) Local: rm -f dw.sapMVD_DVEBMGS10
(18858) Local: ln -s -f /usr/sap/MVD/DVEBMGS10/exe/dispwork dw.sapMVD_DVEBMGS10+
(18859) Local: rm -f co.sapMVD_DVEBMGS10
(18860) Local: ln -s -f /usr/sap/MVD/DVEBMGS10/exe/rslgcoll co.sapMVD_DVEBMGS10
(18861) Local: rm -f se.sapMVD_DVEBMGS10
(18862) Local: ln -s -f /usr/sap/MVD/DVEBMGS10/exe/rslgsend se.sapMVD_DVEBMGS10
(18863) Local: rm -f ig.sapMVD_DVEBMGS10
(18864) Local: ln -s -f /usr/sap/MVD/DVEBMGS10/exe/igswd_mt ig.sapMVD_DVEBMGS10
Starting Programs
19.11.2010 10:16:30
ShmDetach
OK
(18867) Starting: local ms.sapMVD_DVEBMGS10 pf=/usr/sap/MVD/SYS/profile/MVD_DVEBMGS10_devserver
(18868) Starting: local dw.sapMVD_DVEBMGS10 pf=/usr/sap/MVD/SYS/profile/MVD_DVEBMGS10_devserver
(18869) Starting: local co.sapMVD_DVEBMGS10 pf=/usr/sap/MVD/SYS/profile/MVD_DVEBMGS10_devserver -F
(18870) Starting: local se.sapMVD_DVEBMGS10 pf=/usr/sap/MVD/SYS/profile/MVD_DVEBMGS10_devserver -F
(18871) Starting: local ig.sapMVD_DVEBMGS10 -mode=profile pf=/usr/sap/MVD/SYS/profile/MVD_DVEBMGS10_devserver
(18841) Waiting for Child Processes to terminate.
(18841) **** 2010/11/19 10:16:31 Child 18868 terminated with Status 1 . ****
(18868) **** 2010/11/19 10:16:31 No RestartProgram command for program 1 ****
Instance on host devserver started

Advice on SAP B1 Disaster Recovery

Dear All,
We are a SAP B1 Customer and are in the process to apply a Disaster Recovery Plan. For that we need advice how to take Application Back Up, how will that backup be restored on the back up server and what is the good configuration for the Back Up Machine.
Your advice shall be appreciated.
Regards,
Faisal Baloch

Hi,
It is very difficult to summarize the answer for your questions. SO, I suggest to read the book disaster recovery. Here is the book title:
Pro SQL Server Disaster Recovery (DR)
Author : Janes Luetkehoelter
Publisher: Apress
You can use the book to implement DR. The book also answers your questions.
JimM

SAP XI 3.0 Disaster recovery procedure

Hi,
Can someone provide me with a disaster recovery procedure for XI 3.0?
I always thought a normal online backup/restore procedure + recovery redologs + file system backup/restore would be sufficient but there's an internal discussion in our team that more is required for a consistent DR procedure.
Eg: what about XI interfaces? How preventing that a processed file is not processed twice? Etc....
We are running on Oracle 10.2.0.4, XI 3.0 SP 21
Thanks for helping me out.
BR
Bert

Hi,
Prepare a list of activities to be performed before and after the DR.
1.Before bringing down the actual system,you may have to stop the related jobs,stop sending Idocs to the XI system,lock the RFC users so that no more Idocs will be sent.Process all the messages and monitor them end to end before bringing down the actual system.Also,check the queues and see if they are all clear.
2.Once the DR system is up,the RFC destinations should be configured correctly to point to the target.You can then do the testing of interfaces in the DR system after activating the Communication channels.
3.Once the testing is complete and the actual system bought up,you will have to do the health check,check the RFC destinations,unlock RFC users and monitor end to end to see if the messages are flowing through successfully.
In order to avoid errors like processing the file twice,you may have to stop all the Communication channels in the Actual system before bringing them down.After the testing in the DR system is complete,you can unlock the RFC users and restart the channels so that the new messages coming in will be processed.
Hope this helps.
Thanks and Regards,
Induja

Disaster Recovery Plan for SAP BW

Dear All,
We are planning for robust Disaster Recovery Site for BW . We have similar R3 & BIW servers at DR site at different location and data is being copied every 3 Hrs.
R3 & BIW at DR site is exact replica of primary site. When primary site is down DR site will act as a primary. In that case we might face data loading issue from DR R3 to DR BW because of source system change. If we change the source system then we loose data consistency and might need initialisation. We are looking for the solution which will involve less efforts to up the system.
Does anyone has done this or overcome this situation ?
Regards,
Manish

Hi Raman,
We are doing disaster recovery test for both ECC and BW systems so whole PR system switched to DR system for some time and then back to PR system. so in that case what precautions we need to take from BW side?
Thanks
Bhavin

Is anyone doing disaster recovery for a J2EE application?

We generally use database log shipping to maintain a standby database for our ABAP instances. We can successfully fail over our production application to our disaster recovery site with no real issues. With the J2EE instances (EP, ESS/MSS, BI, etc), we have a few concerns:
hostname cannot change, without going through a system copy procedure, so we would have to keep the hostnames in DR the same. (for example, ref: oss note 757692 - changing hostname is not supported)
fully qualified domain name - from what I understand, there are potentially issues with changing the fqdn, for example SSO certificates, BSPs, XI has issues, etc.
we can't keep both hostname and fqdn the same between DR and production, or we could never do a DR test.
Has anyone implemented disaster recovery for any SAP J2EE application that has run into these concerns and addressed them? Input would be greatly appreciated regarding how you addressed these issues, or how you architected your disaster recovery implementation.
Regards,
David Hull
The Walt Disney Company

I haven't done this personally, but I do have some experience with these issues in different HA environments.
To your first point: You can change the hostname, note 757692 tells you exactly how to do it. However like the note says, "Changing the name of a host server in a production system is not automatically supported by SAP." When it says "supported by SAP" I think it means SAP the company, not SAP's software. So I would contact SAP to see if this configuration would be covered under your service agreement. Then you have to think about whether you want to do something that isn't "officially supported" by SAP. Also I'm sure you'll need some kind of additional licensing for the DR systems as their hardware keys will de different.
To your second point: As for SSO certs (SAP Login Tickets), I think they should still work as long as the SID and client number of the issuing system remain the same. I don't think they are hostname or fqdn dependant. For BSPs I would think they would still work as long as they use relative paths rather than absolute paths. And for XI... I have no idea what kind of issues may arise, I'm not an XI guy.
Again, I haven't done what you're describing myself. This is just based on my HA experiences.
Hope this helps a little,
Glenn

Welcome to the SQL Server Disaster Recovery and Availability Forum

(Edited 8/14/2009 to correct links - Paul)
Hello everyone and welcome to the SQL Server Disaster Recovery and Availability forum. The goal of this Forum is to offer a gathering place for SQL Server users to discuss:
Using backup and restore
Using DBCC, including interpreting output from CHECKDB and related commands
Diagnosing and recovering from hardware issues
Planning/executing a disaster recovery and/or high-availability strategy, including choosing technologies to use
The forum will have Microsoft experts in all these areas and so we should be able to answer any question. Hopefully everyone on the forum will contribute not only questions, but opinions and answers as well. I’m looking forward to seeing this becoming a vibrant forum.
This post has information to help you understand what questions to post here, and where to post questions about other technologies as well as some tips to help you find answers to your questions more quickly and how to ask a good question. See you in the group!
Paul Randal
Lead Program Manager, SQL Storage Engine and SQL Express
Be a good citizen of the Forum
When an answer resolves your problem, please mark the thread as Answered. This makes it easier for others to find the solution to this problem when they search for it later. If you find a post particularly helpful, click the link indicating that it was helpful
What to post in this forum
It seems obvious, but this forum is for discussion and questions around disaster recovery and availability using SQL Server. When you want to discuss something that is specific to those areas, this is the place to be. There are several other forums related to specific technologies you may be interested in, so if your question falls into one of these areas where there is a better batch of experts to answer your question, we’ll just move your post to that Forum so those experts can answer. Any alerts you set up will move with the post, so you’ll still get notification. Here are a few of the other forums that you might find interesting:
SQL Server Setup & Upgrade – This is where to ask all your setup and upgrade related questions. (http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/threads)
Database Mirroring – This is the best place to ask Database Mirroring how-to questions. (http://social.msdn.microsoft.com/Forums/en-US/sqldatabasemirroring/threads)
SQL Server Replication – If you’ve already decided to use Replication, check out this forum. (http://social.msdn.microsoft.com/Forums/en-US/sqlreplication/threads)
SQL Server Database Engine – Great forum for general information about engine issues such as performance, FTS, etc. (http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/threads)
How to find your answer faster
There is a wealth of information already available to help you answer your questions. Finding an answer via a few quick searches is much quicker than posting a question and waiting for an answer. Here are some great places to start your research:
SQL Server 2005 Books Onlinne
Search it online at http://msdn2.microsoft.com
Download the full version of the BOL from here
Microsoft Support Knowledge Base:
Search it online at http://support.microsoft.com
Search the SQL Storage Engine PM Team Blog:
The blog is located at https://blogs.msdn.com/sqlserverstorageengine/default.aspx
Search other SQL Forums and Web Sites:
MSN Search: http://www.bing.com/
Or use your favorite search engine
How to ask a good question
Make sure to give all the pertinent information that people will need to answer your question. Questions like “I got an IO error, any ideas?” or “What’s the best technology for me to use?” will likely go unanswered, or at best just result in a request for more information. Here are some ideas of what to include:
For the “I got an IO error, any ideas?” scenario:
The exact error message. (The SQL Errorlog and Windows Event Logs can be a rich source of information. See the section on error logs below.)
What were you doing when you got the error message?
When did this start happening?
Any troubleshooting you’ve already done. (e.g. “I’ve already checked all the firmware and it’s up-to-date” or "I've run SQLIOStress and everything looks OK" or "I ran DBCC CHECKDB and the output is <blah>")
Any unusual occurrences before the error occurred (e.g. someone tripped the power switch, a disk in a RAID5 array died)
If relevant, the output from ‘DBCC CHECKDB (yourdbname) WITH ALL_ERRORMSGS, NO_INFOMSGS’
The SQL Server version and service pack level
For the “What’s the best technology for me to use?” scenario:
What exactly are you trying to do? Enable local hardware redundancy? Geo-clustering? Instance-level failover? Minimize downtime during recovery from IO errors with a single-system?
What are the SLAs (Service Level Agreements) you must meet? (e.g. an uptime percentage requirement, a minimum data-loss in the event of a disaster requirement, a maximum downtime in the event of a disaster requirement)
What hardware restrictions do you have? (e.g. “I’m limited to a single system” or “I have several worldwide mirror sites but the size of the pipe between them is limited to X Mbps”)
What kind of workload does you application have? (or is it a mixture of applications consolidated on a single server, each with different SLAs) How much transaction log volume is generated?
What kind of regular maintenance does your workload demand that you perform (e.g. “the update pattern of my main table is such that fragmentation increases in the clustered index, slowing down the most common queries so there’s a need to perform some fragmentation removal regularly”)
Finding the Logs
You will often find more information about an error by looking in the Error and Event logs. There are two sets of logs that are interesting:
SQL Error Log: default location: C:\Program Files\Microsoft SQL Server\MSSQL.#\MSSQL\LOG (Note: The # changes depending on the ID number for the installed Instance. This is 1 for the first installation of SQL Server, but if you have mulitple instances, you will need to determine the ID number you’re working with. See the BOL for more information about Instance ID numbers.)
Windows Event Log: Go to the Event Viewer in the Administrative Tools section of the Start Menu. The System event log will show details of IO subsystem problems. The Application event log will show details of SQL Server problems.

hi,I have a question on sql database high availability. I have tried using database mirroring, where I am using sql standard edition, in this database mirroring of synchronous mode is the only option available, and it is giving problem, like sql time out errors on my applicatons since i had put in the database mirroring, as asynchronous is only available on enterprise version, is there any suggestions on this. thanks ---vijay

Disaster Recovery in SAP ERP2005-SR1 ABAP- MSSQL.

Similar Messages

Maybe you are looking for