BPC Disaster recovery procedure

Hello Experts,
Iu2019m setting up a disuster recovery for our BPC 5.1 and I need a 2sn opinion on my approachu2026
We have a production multi-server environment running SQL Server 2005 and WEB/App server (2 servers). Our DR environment is multi-server as well: database and WEB/App.
I am going to setup SQL Server Database mirroring for all BPC database, have OLAP database backed up on production and restored on DR and have robocopy of BPC folders between production and DR.
So, generally speaking, if I failover BPC database to DR and re-point end-users to DR application server it should work. Am I right or I am missing something?
Thanks in advance,
Akim

Yes but the biggest part of time it will be the restore of OLAP and reprocess of database.
So if you would like to have mirroring then it is not problem you can do that but that's means another layer of maintenance and also you have to be carefully because mirroring is creating sometimes delay into source database.
Yes it will work if you redirect the user to new environment. Usually it is the DNS alias used for this.
I will precise one more time that you have to be sure that you are processing the appset before to give user access into new sistem.
Also make sure you are doing mirroring also for table tblappsetaccess for database appserver.
But only for this table (this is necessary for security). Or you can process the security (all teams) instead to do mirroring for that table.
Kind Regards
Sorin Radulescu

Similar Messages

  • 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

  • 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

  • BPC Database Recovery Instructions

    Hi Experts,
    We are using BPC 7.5 Microsoft version with multiserver environment having BPC Application Server on one machine and using Shared Database server located on other machine, we have configured a database Instance for BPC databases on shared database server.
    We have gone through SAP Note u201C1455212 - Best practices for BPC MS backupu201D and as per u201CBacking up Microsoft SQL Server databases and filesu201D section of this note we are taking full database backup daily for the BPC instance and tlog backup in every 4 hours.
    We would like to know the instructions to migrate our BPC DB/OLAP/RS to different server in a DR (disaster recovery) scenario or rebuilt DB/OLAP/RS server with the help of backup files.
    Please Advice.
    Thanks & Regards,
    Rohit

    Hi Rohit
    You can follow some of the suggestions outlined in the following thread
    [Re: BPC Disaster Recovery]
    Kind Regards
    Daniel

  • 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

  • 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 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 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).
    <u><b>What must be done to perform this switchover/switchback process between the two clients once the test is completed</b></u>?

    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

  • Disaster Recovery Plan

    We're running xMII 11.5 SP3 in a three-tiered centralized server environment (Development, Staging and Production).  We plan on having a project up and running in production by October 1.  Before we do so, however, we need to develop a disaster recovery plan in the event of a failure of our production server.  Our staging server is in a different city and we plan on using it as our temporary production server.
    Does anyone have any recommendations on putting together a disaster recovery plan for this scenario?
    Thanks!

    Dave,
    Good to see you active on the forums, hope all is well...
    As for disaster recovery the procedures will follow along similar to your roll out plan, where content is moved from Dev -> Staging -> Prod.  The main difference will be that you will have to reconfigure the xMII system.  In 11.5 this is all file based XML files in the following directories:
    <Drive>:\Lighthammer\Illuminator\conf
    <Drive>:\Lighthammer\Illuminator\sysconf
    <Drive>:\Lighthammer\Illuminator\properties
    <Drive>:\Lighthammer\Security\*
    <Drive>:\Lighthammer\Xacute\Configuration
    These are the main ones, there may be others depending on your development specifics.
    Hope this helps.
    -Sam

  • Disaster Recovery on another Sun Server

    I have a question in regards to disaster recovery of Sun servers. We have a client that hosting applications within Sun T platform which utilizes LDOM configuration. These boxes host around five guests.
    Currently we use a software called EMC HomeBase(http://www.emc.com/backup-and-recovery/homebase/homebase.htm) to enhance our DR recovery by profiling the Sun box and transmitting that profile to our DR vendor. DR vendor in turn with help from EMC will install the OS, patch level and apply that profile to setup the system with NIC information, file systems and other components so we would only
    need to restore our data from NETBACKUP and don't do any system recovery.
    Unfortunately, EMC does not support LDOMs nor containers. Now my question is if Sun has a way around this? Please note that the servers will be different models at DR. for example T5220 to a T5440 or V890 to V490.

    It'd be rather easy to manually install same LDOM configuration on DR site... all EMC seems to be doing is getting the profile & then someone is creating setup manually...
    Anyways... here you go:
    Backup & Recovery of guest domain
    Archive and backup the guest domain configuration:
    ldm list-constraints -x <ldom> > <ldom>.xml
    Backup the guest domains over the network with backup software as regular server
    Restore the guest domain configuration, assuming that your VSW and VDS resources are available:
    ldm add-domain -i <ldom>.xml
    Make sure that you have enough VCPU, MAU, and Memory to boot your guest domain.
    Jumpstart guest domain and install backup client. Restore data from backup.
    Backup LDOM configuration
    You can take the backup of the configuration using "ldm add-spconfig saveconfigurtion" command which will store in SP of the server.
    For taking the backup of the individual domain use "ldm ls-constrants >> filename.xml" it will give the xml output just redirect it to a file.
    While creating the domain again use "ldm create ldomname -f filename.xml"
    You can not create control domain by the above procedure we hve to configure manualy or even if your control domain crashed install new OS and install LDOM Manager in the Base OS create /etc/hostname.vsw0 & vsw1 files poweroff the server from SP. set bootmode config=saveconfiguration
    How to backup the primary domain
    Backup the LDM db files in: /var/opt/SUNWldm
    Archive and backup the primary domain configuration:
    ldm list-constraints -x primary > primary.xml
    Backup the primary domains over the network with backup software as regular server.
    How to recover primary domain
    Update firmware
    Install backup client & LDM software
    Restore /var/opt/SUNWldm
    Start up LDM services
    If all goes well, the LDM config will be read and you will be in initial configuration mode. Save the config to the hypervisor and
    reboot. If not, parse the primary.xml file to recreate the primary domain configuration, save config, and reboot.
    Restore guest domain configs and data. Then bring up guest domains.

  • Disaster Recovery scenario for MSCS Production system.

    Hi
    Our production system is on win2008/sql2008 MSCS. We decided to install a disaster recovery system. We will use a database replication software. If we have a standalone production system, not a MSCS system, i know that i can install Disaster Recory system with same SID and hostname and i don't need any homogeneous system copy procedure to switch to DR system. But in our scenario, we have many hostname (sap cluster group, sql cluster group, hostnames of nodes... etc.).
    How can i install my DR system (which hostname.. etc.) to make our DR scenario easy?
    Best Regards...

    You May have trouble with RFC connections:
    So, one possible solution is, your new server name(Host name) should be your message server name to minimise the trouble and you have to maintain this for all RFC connections (to Prod ECC system) to virtual host which could be message server.
    If I could think if any other possible issues, I will update.
    Krishna

  • Disaster Recovery Plan for BW Production

    Hello Experts,
    We at IP are trying to evaluate and institute a sound and
    cost-effective disaster recovery plan for the BW production system.
    In this regard, we would like to hear from you(or from your infrastructure folks) about the experience(s) at
    client sites of such scenarios for BW.
    We are specifically interested in knowing answers to:
    1. Do you have currently have Disaster Recovery Plan for BW Production?.
    2. How large is your BW production database?
    3. Is the alternate server being replicated real time or using tapes or ......?
    4. What are your target service levels?
    5. Location specifics or any other pertinent info.
    Any input is highly appreciated.
    Thanks in advance,
    Kumar Gudiseva.
    Edited by: Kumar Gudiseva on Jan 9, 2008 3:35 PM

    Hi,
    The disaster recovery strategy should include a backup and restore plan that determines which data should be backed up and the procedures that will be used to recover it.
    Please check these links:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/001ef297-9bbf-2910-bbaa-babedc1b01ca
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6efca1a6-0301-0010-6f9d-82cf87340e45
    /people/nicholas.holshouser/blog/2006/09/07/the-square-root-of-an-it-disaster-is-recovery
    Hope it helps.
    Regards,
    Mona

  • SQL Server 2005 High Availability and Disaster Recovery options

    Hi, We are are working on a High Availability & Disaster Recovery Planning solution for an application database which is on SQL Server 2005. What different options have we got to implement this for SQL Server 2005 and after we have everything setup how
    do we test the failover is working?
    Thanks in advance.........
    Ione

    DR : Disaster recovery is the best option for the business to minimize their data loss and downtime. The SQL server has a number of native options. But, everything is depends upon your recovery time objective RTO and recovery point objective RPO.
    1. Data center disaster
    Geo Clustering
    2. Server(Host)/Drive (Except shared drive) disaster
    Clustering
    3. Database/Drive disaster     
    Database mirroring
    Log shipping
    Replication
    Log shipping
    Log shipping is the process of automating the full database backup and transaction log on a production server and then automatically restores them on to the secondary (standby) server.
    Log shipping will work either Full or Bulk logged recovery model.
    You can also configure log shipping in the single SQL instance.
    The Stand by database can be either restoring or read only (standby).
    The manual fail over is required to bring the database online.
    Some data can be lost (15 minutes).
    Peer-to-Peer Transactional Replication
    Peer-to-peer transactional replication is designed for applications that might read or might modify the data in any database that participates in replication. Additionally, if any servers that host the databases are unavailable, you can modify the application
    to route traffic to the remaining servers. The remaining servers contain same copies of the data.
    Clustering
    Clustering is a combination of one or more servers it will automatically allow one physical server to take over the tasks of another physical server that has failed. Its not a real disaster recovery solution because if the shared drive unavailable we cannot
    bring the database to online.
    Clustering is best option it provides a minimum downtime (like 5 minutes) and data loss in case any data center (Geo) or server failure.
    Clustering needs extra hardware/server and it’s more expensive.
    Database mirroring
    Database mirroring introduced in 2005 onwards. Database Mirroring maintain an exact copy of a database on a different server. It has automatic fail over option and mainly helps to increase the database availability too.
    Database mirroring only works FULL recovery model.
    This needs two instances.
    Mirror database always in restoring state.
    http://msdn.microsoft.com/en-us/library/ms151196%28v=sql.90%29.aspx
    http://blogs.technet.com/b/wbaer/archive/2008/04/19/high-availability-and-disaster-recovery-with-microsoft-sql-server-2005-database-mirroring-and-microsoft-sql-server-2005-log-shipping-for-microsoft-sharepoint-products-and-technologies.aspx
    http://www.slideshare.net/rajib_kundu/disaster-recovery-in-sql-server
    HADR Considerations
    Need to Understand the business motivations and regulatory requirements that are driving the customer's HA/DR requirements. Understand how your customer categorizes the workload from an HA/DR perspective. There is likely to be an alignment between the needs
    and categorization.
    Check for both the recovery time objective (RTO) and the recovery point objective (RPO) for different workload categories, for both a failure within a data center (local high availability) and a total data center failure (disaster recovery). While RPO and
    RTO vary for different workloads because of business, cost, or technological considerations, customers may prefer a single technical solution for ease in operations. However, a single technical solution may require trade-offs that need to be discussed with
    customers so that their expectations are set appropriately.
    Check and understand if there is an organizational preference for a particular HA/DR technology. Customers may have a preference because of previous experiences, established operational procedures, or simply the desire for uniformity across databases from
    different vendors. Understand the motives behind a preference: A customers' preference for HA/DR may not be because of the functions and features of the HA/DR technology. For example, a customer may decide to adopt a third-party solution for DR to maintain
    a single operational procedure. For this reason, using HA/DR technology provided by a SAN vendor (such as EMC SRDF) is a popular approach.
    To design and adopt an HA/DR solution it is also important to understand the implications of applying maintenance to both hardware and software (including Windows security patching). Database mirroring is often adopted to minimize the service disruption
    to achieve this objective.
    HADR Options :
    Failover clustering for HA and database mirroring for DR.
    Synchronous database mirroring for HA/DR and log shipping for additional DR.
    Geo-cluster for HA/DR and log shipping for additional DR.
    Failover clustering for HA and storage area network (SAN)-based replication for DR.
    Peer-to-peer replication for HA and DR (and reporting).
    Backup & Restore ( DR)
    keep your server DB backups in network location ( DR)
    Always keep your sql server 2005 upto date, in case if you are not getting any official support from MS then you have to take care of any critical issues and more..
    Raju Rasagounder Sr MSSQL DBA

  • Need help for Disaster Recovery setup and configuration

    Hi Gurus.
    We are planning to have disaster recovery test plan. Normally we setup our network at another site and then restore data there and then do configuration and setup to run SAP system to new network.
    But this is little more time consuming. We are planning to do something which will might save our time.
    We want to create one Application instance on Central instance on current production server. This instance will be "deactivated" and will not run on production server.
    When we will do the disaster recovery, we will restore CI filesystem to Disaster recovery network. That time this new application instance  will aslo get copied. Once this is done, we just need to go to this instance and start SAP System. This way we will save our time of configuring the new instance and then starting it.
    e.g
    Production host -> prdhost1
    Central Instance -> /usr/sap/P01/DVEBMGS00
    and it's subdirectory: data, work, log, sec
    create new application instance -> /usr/sap/P01/D03
    and it's subdirectory: data, work, log, sec
    create new instance profile -> P01_D03_prdhost1, START_D03_prdhost1
    this configuration will be created but SAP instance will not be started. It will be copied to Disaster Recovery new site and in that new network , there we can start this new application instance.
    Please let me know if we can do that ? if yes, are we going to face any issue in production?
    Other than mentioned above, what FileSystem we need to take care for creating new instance?
    Any help will be highly appreciated.
    Thanks in advance
    Best Regards,
    Basis CK

    Hi!
    Sorry but your scenario is a little bit confusing.
    Let me guess if I understood, you want to configure a "virtual" instance to be able to use it in case of DR.
    I don't advise you to do things that way. Why not use virtual hosts and virtual instances like we do when implementing instances within a cluster or metrocluster.
    You must have the license from DR server installed. I you use virtual hosts all DR issues like printers, logon groups, RFC groups, etc... will be solved.
    If you use virtual hosts and virtual instances all you need to do is replicate the environment into DR site, restore the system and start production.
    Of course... you are using UNIX and within UNIX world all these things are much easier.
    Bear in mind that if you have JAVA instances then I think this is the only recommended procedure.
    Cheers,
    FF

  • SharePoint 2010 backup and restore to test SharePoint environment - testing Disaster recovery

    We have a production SharePoint 2010 environment with one Web/App server and one SQL server.   
    We have a test SharePoint 2010 environment with one server (Sharepoint server and SQL server) and one AD (domain is different from prod environment).  
    Servers are Windows 2008 R2 and SQL 2008 R2.
    Versions are the same on prod and test servers.  
    We need to setup a test environment with the exact setup as production - we want to try Disaster recovery. 
    We have performed backup of farm from PROD and we wanted to restore it on our new server in test environment.Backup completed successfully with no errors.
    We have tried to restore the whole farm from that backup on test environment using Central administration, but we got message - restore failed with errors.
    We choosed NEW CONFIGURATION option during restore, and we set new database names... 
    Some of the errors are:
    FatalError: Object User Profile Service Application failed in event OnPreRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    SPException: The specified user or domain group was not found.
    Warning: Cannot restore object User Profile Service Application because it failed on backup.
    FatalError: Object User Profile Service Application failed in event OnPreRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    Verbose: Starting object: WSS_Content_IT_Portal.
    Warning: [WSS_Content_IT_Portal] A content database with the same ID already exists on the farm. The site collections may not be accessible.
    FatalError: Object WSS_Content_IT_Portal failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    SPException: The specified component exists. You must specify a name that does not exist.
    Warning: [WSS_Content_Portal] The operation did not proceed far enough to allow RESTART. Reissue the statement without the RESTART qualifier.
    RESTORE DATABASE is terminating abnormally.
    FatalError: Object Portal - 80 failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    ArgumentException: The IIS Web Site you have selected is in use by SharePoint.  You must select another port or hostname.
    FatalError: Object Access Services failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    SPException: Object parent could not be found.  The restore operation cannot continue.
    FatalError: Object Secure Store Service failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    SPException: The specified component exists. You must specify a name that does not exist.
    FatalError: Object PerformancePoint Service Application failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    SPException: Object parent could not be found.  The restore operation cannot continue.
    FatalError: Object Search_Service_Application_DB_88e1980b96084de984de48fad8fa12c5 failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
    Aborted due to error in another component.
    Could you please help us to resolve these issues?  

    I'd totally agree with this. Full fledged functionality isn't the aim of DR, getting the functional parts of your platform back-up before too much time and money is lost.
    Anything I can add would be a repeat of what Jesper has wisely said but I would very much encourage you to look at these two resources: -
    DR & back-up book by John Ferringer for SharePoint 2010
    John's back-up PowerShell Script in the TechNet Gallery
    Steven Andrews
    SharePoint Business Analyst: LiveNation Entertainment
    Blog: baron72.wordpress.com
    Twitter: Follow @backpackerd00d
    My Wiki Articles:
    CodePlex Corner Series
    Please remember to mark your question as "answered" if this solves (or helps) your problem.

Maybe you are looking for