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

Similar Messages

Advice on best way to setup Disaster Recovery for SOA Suite 10.1.3.4

Hi Everyone,
I need some advice on the best way to setup Disaster Recovery for a SOA Suite 10.1.3.4 install deploying JSF/ADF OC4J applications.
The way we are trying to do it at the moment is manually copy the "applications" and "applications-deployments" folders for the OC4J application on the production server, then compress and ship the files across to the DR application server nightly. (We don't require high availability).
In the event of a disaster we then extract the files and copy to the OC4J instance (pre-created and configured) on the DR server. Unfortunately to date we haven't been able to reliably setup a DR application (seem to mostly get 404 errors etc), even though the OC4J application has its connection pool resolved to the DR database and is showing as "up" in the ASConsole.
My question is, is there a more "native" way to do what we are trying to do. We do not have Enterprise version of SOA Suite or 11g database so any advanced recovery features are not an option. The setup is also stand alone, i.e. we are not using clustering or RAC etc.
Any ideas would be really helpful.
Thanks,
Leigh.
PS we are also running the production apps server with Oracle Application server 10g 10.1.2.3.0 as the HTTP apache server (with Forms, Reports and Discoverer deployed) and the SOA Suite 10.1.3 applications use the 10.1.2 HTTP server via the HTTP to AJP bridge. So the 10.1.3 OC4J instance is configured to use AJP on port range 12501 - 12600.

For enterprise solutions, AS Guard would work.
http://download.oracle.com/docs/cd/B25221_04/core.1013/b15977/disasrecov.htm#sthref303
However, since advanced recovery options are not available (as you said), then what you are doing should not be too bad.
AMN

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

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

What is the quickest to upgrade disaster recovery system to NW04s in MSCS?

Hi,
I have an issue which I need assistance from SAP/Windows 2003 experts.
Hope you can share your opinion on an SAP upgrade issue we're grappling with.
Objective : Upgrade our SAP Bank Analyzer disaster recovery environment from NW04 to NW04s SR2, to be same as production. Both production and disaster recovery (DR) run under two node WIN2003 Enterprise MSCS. The SAP CI usually runs on node A and Oracle 10g runs on node B.
The Oracle software, parameters, database files and the SAP folder \usr\sap are already matching. These files and folders are on EMC mirrored disks, so this will be automatically synchronized from production status.
Therefore I believe it is only the SAP software components on the local hard disks - binaries, DLLs, registry, DCOM, environment variable etc, that need to be upgraded on the two DR machines.
For your information, the current SAP 6.40 instance, Oracle 10g instance, MSCS failover capability are all working in the DR environment as we just did an exercise a month ago to prove this.
 Disaster Recovery Environment :
On shared drives that are synchronized between prod and DR : SAP folder \usr\sap including the kernel binaries, Oracle parameter files, database datafiles, redologs, sapbackup etc.
Issue : What is the quickest and reliable method to achieve the objective? Other than the SAP kernel binaries and profiles, I'm not certain what other related components are updated/replaced that are stored locally on each of the clustered machine.
There are three different approaches we can think of :
1) Repeat the whole NW04s upgrade process in the DR environment. This takes several days. The exposure of not having a disaster recovery environment for several days is a minus.
 or
2) Un-install the SAP CI and MSCS definitions. Synchronise the DR shared disks from production to have the upgraded production NW04s database contents and SAP folder \usr\sap.
Use SAPINST to re-install either traditional CI or ASCS option 'System Copy". And then re-create the MSCS definitions for SAP CI using SAPINST again.
The disadvantage is I can't trial this in any other of our environments. Also, we want to run with the traditional CI instead of ASCS until early next year for other reasons. So we would have to reverse the ASCS back to traditional CI with this method, by reversing the steps in OSS NOTE 101190 "Splitting CI after upgrade to 700".
 or
3) Somehow identify all the SAP components that are stored locally on each machine (eg. environment variables, registry settings, DCOM definitions, DLL in various folders). Then just copy them from Production to DR machines or recreate them. I'm not confident of identifying the local SAP components. And I have not been able to find any good OSS NOTEs or forum threads on this topic. The most helpful OSS NOTE I can find is 112266 point 13 and 19.
Thanks for any input.
Benny Kwan

See:
* https://support.mozilla.com/kb/Form+autocomplete
* Firefox > Preferences > Privacy > History: "Remember search and form history"
* Autofill Forms: https://addons.mozilla.org/firefox/addon/autofill-forms/

Datafiles Mismatch in production & disaster recovery server

Datafiles Mismatch in production & disaster recovery server though everything in sync
We performed all the necessary prerequisites & processes related to DRS switchover successfully also our DRS server is constantly updated through logs application in mount state whan we opened DRS database in mount state it opened successfully however when we issued command
Recover database
It dumped with foll errors:
ora-01122 database file 162 failed verification check
ora-01110 data file 162 </oracle/R3P/sapdata7/r3p*****.data>
ora-01251 unknown file header version read for file 162
as I do not remember the exact name now
However upon comparing the same file at production(which was now in shutdown state) the file sizes were mismatching so we went ahead to copy the datafile from production to DRS in database shutdown state at DRS through RCP utitlity of AIX 5.3 since our Operating system is AIX 5.3
Though this remote copy was success
we again started database in mount state & issued command
Recover database
But still it dump the same error but now for another datafile in DRS
I mean I would appreciate if somebody could point out that despite our DRS was constantly being updated through our Production in terms of continuous log application before this activity logs were sync in both the systems also origlos,mirrorlogs & controlfiles were pulled from production system as it is infact the whole structure was as replica of production system , then why did datafile sizes mismatch??
Details
SAP version :- 4.7
WAS :- 620
Database :- Oracle 9.2
Operating system :- AIX 5.3

I am in a process of DR Planning.
My present setup :
O/S : HP-UX 11.31
SAP ECC 6
Oracle 10g Database.
I know about dataguard and i have implemnted same on our other application but not for SAP.
I have ame doubts and I request you to please guide me for the same.
1. SAP License key -- it required hardware key. So will i have to generate license key another hardware key i.e. for machine where standby database.
2. Database on standby site will be in manage recovery mode. Will I have to make any changes or any other file realted to SAP on standby host ? (some i know such as I upgrade SAP kernal, same i have to upgrade at standby host)
Will you give me some link related to document for DR

Disaster Recovery from tape library!

Hi,
I am using oracle 10g and Backup Exec 12 as the media management software. How do i perform the disaster recovery. My entire scenario is like this:
Server A has the DB (Database).
Configured Backup Exec with RMAN and took full DB backup along with autobackup of controlfile to the tape.
Server A crashes and is unusable.
Installs Oracle on server B and needs to restore the DB on this new server.
I know the DBID of the DB but how to configure RMAN to work with Backup Exec, so that I can restore the db from the tape library?
When you configure the RMAN integration with Backup Exec, it finds the database running on the server and will perform the integration. But in my case, since the database does not exist, how will the Backup Exec agent configure the integration?
How do we go about the restoration to Server B in this case?
Thanks!

Hi!
I am still not able to restore the db. The scenario is like:
Took a full database backup to tape from server A with controlfile autoconfig
Trying to restore the db on server B. The following is the script used to restore.
connect target /
set dbid=152417844;
startup nomount;
run
+{+
allocate channel sbt1 type 'sbt_tape';
SEND 'BSA_SERVICE_HOST=ipaddress,NBBSA_TOTAL_STREAMS=1';
set controlfile autobackup format for device type 'sbt_tape' to 'cf_%F';
restore spfile from autobackup;
restore controlfile from autobackup;
alter database mount;
restore database;
recover database;
release channel sbt1;
+}+
alter database open resetlogs;
When i try to restore, the output is:
channel sbt1: looking for autobackup on day: 20090624
channel sbt1: looking for autobackup on day: 20090623
channel sbt1: looking for autobackup on day: 20090622
channel sbt1: looking for autobackup on day: 20090621
channel sbt1: looking for autobackup on day: 20090620
channel sbt1: looking for autobackup on day: 20090619
channel sbt1: looking for autobackup on day: 20090618
channel sbt1: no autobackup in 7 days found
released channel: sbt1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 06/24/2009 11:19:28
RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
Please advice!
Edited by: Libra DBA on Jun 24, 2009 1:39 PM

Disaster Recovery Soltuion

Hi Everyone,
In the case of Production system unavailable, by the destruction like due to fire or water floods, to avoid the system down-time for couple of days/weeks. We are planning to go for Disaster Recovery solution.
We are planning to go with this solution for our production systems like EHP4 for SAP ERP 6.0/NW 7.01, Solution Manager 7.0 EHP1 systems.
Our landscape was configured in Distributed systems (CI+DB), OS:Win2003 and DB: MS SQL Server 2005.
My doubts are as follows.
1.) I am not able to find any document for DR solution, can anyone guide me where can I find the Documents releated to DR Solution
2.) In the DR Solution Systems as well we need to connect to SAP or not? I mean for remote support or RFC Connections and etc?
3.) Where can I find the Best Practices for DR? I have gone through the Best Practices but not able to find the proper things related to DR.
4.) Can anyone guide me the correct procedure or steps for the DR solution to follow?
I'm planning to do like these OS intallation, DB installation then SAP Installation then copy the Back-up of Production system to Back-up system (DR solution system).
Thanks and Regards
Pavan

Hello Pavan,
I have found the following documentation about Disaster recovery:
http://help.sap.com/saphelp_erp2004/helpdata/en/6b/bd91381182d910e10000009b38f8cf/
frameset.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/f2/31ad5c810c11d288ec0000e8200722/
frameset.htm
Also the following notes:
437160 : MS Disaster Recovery Articles for MS SQL Server
965908 : SQL Server Database Mirroring and SAP Applications
741289 : Profile parameters of the J2EE Engine are lost
(This Note indicate parameters which must be maintained in
the instance profile)
193816 : Restore with SQL Server
799058 : Setting Up Microsoft SQL Server 2005
I hope this information helps you.
Regards,
Blanca

Disaster Recovery - HPSU8

We currently are running HPSU 8.3 and have been tasked with developing a good disaster recovery plan should the server fail. We have purchased a new server that's identical to the production server. Does Hyperion have documentation/recomnedations for restoring HPSU 8 to another server. We are backing up the entire production server nightly. If anyone can point me in the right direction for this I'd appreciate it. I called support, but they just directed me to e-support and told me I should be able to find documentation online but I have been unable to locate this information so i was hoping someone may be able to assist me. Thanks, Bob Cook REZ1

Exactly, the attached doc regarding HANA standby means for high availibility not disaster recovery. if the entire data center goes belly up, there will be no shared disk available. I talked with a few folks from SAP BI area. It seems to me that at this point the best way to handle HANA disaster recovery is manual:
1. Back up HANA to local backup system (storage or tapes) at regular interval (e.g. nightly) and ship (ftp/ship etc.) the back up to DR site.
2. Back up HANA log more frequently (e.g. hourly) and ship the log backups to DR site.
In the event of a DR, the backups shipped to the DR site will be used to restore a HANA DR system. Of course, nomal DR practice still applies, such as, use of virtual names everywhere, change DNS entries, etc. to make the resumption of DR processing at DR site seamless ...
This is very similar to the very early days of RDBMS DR practice. I expect SAP will make the HANA DR less painful by implementing something similar to modern days RDBMS DR solution (e.g. database mirroring, standby db, replication, etc.) in the future.

Disaster recovery question

Your forum was recommended for my question/issue
We have two semi-annual disaster recovery tests annually. The pre-test process is composed of restoring the Disaster Recovery Client from the Production client, and allowing one set of users to perform their process procedures on the DRS server, while the other users continue normal business operations on the PRD server.
Earlier this year we upgraded from SAP 4.0b --> 4.7c.
During our first disaster recovery test this year users received a message 'change and transport system not configured' . They were able to continue master data updates, even though they received the message.
We would like to have a real disaster recovery test where we switch from the production system to the disaster recovery system (DRS) and continue our business operations from that server (DRS)(located in another state).
What must be done to perform this switchover/switchback process between the two clients once the test is completed?

If I interpreted you correctly: you want to bring up a DR-copy of the PRD system on another server. Then let a limited number of users test this one while all other users continue normal operation on the PRD server.
Be aware that it is pretty dangerous to have both servers running at the same time
You're main concern will be to isolate the DR system from the PRD system and interfacing systems !!!
The result will not be 100% correct:
- it will not be possible to test all interfaces - thus not all business functionality...
the main obstacle with failover systems is interfaces.
- you will not be able to see if the DR system can handle the load
you will not see if the server and/or infrastructure is sufficient
P.S. Remember that the interfacing go both ways.
- You want someone to reach the system - as such you will need to open access into the DR system...
but - you will want "only a limited number of users" to do it.. as such you must play around with SAP logon and/or DNS/IP addresses.
- You do NOT want the DR system to update the PRD system (or send out info to any other partners)
as such - you must restrict outbound traffic from the DR system.
If you do not know what/where to isolate... then rip out the network cable and place the users next to the server

Advice on SAP B1 Disaster Recovery

Similar Messages

Maybe you are looking for