MaxDB disaster Recovery site setup

Hello Experts
We are hosting SAP apllication in our datacentre. For one of our customer we need Disaster Recovery site. As planned by our maneegment we are going to have a DR centre at some other location. Our DC and DR are connected by suffcient link.
My SAP Instance is running ion MaxDB database and RHEL5. Can you please suggest me how I should look forward to set up the DR site?
Can I setup a SAP server in my DR site with same SID server will restore the initial backup from DC and then go for log mirroring?  In this case I will have to install SAP system with same SID? IP address?

There are several possibilities to approach your goal, for a start check
Note 952783 - FAQ: MaxDB high availability
It has a nice comparison of the different possibilities.
Markus

Similar Messages

  • Best Way to setup a disaster Recovery site for a logical standby database

    I have a logical standby DB (L1DB) as a reporting db on the same machine as the primary (P1DB). We are planning on building a disaster recovery site with similar hardware and potentially have disk mirroring of atleast the redo log files.
    The DR site can hold an additional physical standby (S1DB) for the primary (P1DB). I am trying to understand what would be the best way to setup the Disaster Recovery site for the L1DB logical stdby. Ideally, when the disaster happens, and I no longer have P1DB and L1DB, I should be able to switch to S1DB as the new primary. But how do I setup to have a L2DB that takes the place of L1DB and has its contents and can be setup as a logical standby of S1DB?

    If you already setup one logical standby, then you know how it works, so not sure what question you are asking ?
    Personally I would setup L2DB as a standby of the original primary P1DB. Having downstream standby databases complicates things, and adds additional lag between primary transaction time and L2DB apply.

  • 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

  • Synchronizing Disaster Recovery site with the production server

    Hi All,
    One of the customer is asking the following query:
    "How Disaster recovery site can be synchronized with the production server and how do they switch? Will the web logic server do this for them?"
    This customer is having two sites one live and one a DR (Disaster Recovery) site on different location.
    Can somebody answer my query?
    Thanks in advance.,
    Regards.,
    Naveen

    Firstly
    Is your Datagaurd Physical( Redo Apply) or Logical( SQL apply)?
    Does it have Datagaurd Broker?
    When Datagaurd is setup in your environment - on the primary database( live database) the Datagaurd users LGWR or/and ARCH process to collect redo data and ship this data to standby ( DR site) and the FAL process to provide client-server mechanism for shipping archived logs to standby.
    On standby database, The Datagaurd users RFS process to receive redo records from primary database, the MRP process applies redo information to standby database.
    If the Data Gaurd Broker is enabled, Datagaurd also used DMON process to manage and monitor both primary and standby databases as a unified configuration.
    When there is any connectivity issue to the standby and when connection is re-established, the accumulated archive logs are automatically shipped and apploed to stanby, until stanby is resynchronized with the primary. This process does not require any administrative intervention.
    If there is a very large Archive Gap between the primary and secondary due to some major issue. Then the unshipped archive logs need to be shipped manually from primary to standby and needs to be applied in standby to sync up with primary. For some reason there will also arise rare issues like problem with not applying of archive logs though log shipping is success. So some work arround will solve it.
    Comming to planned /unplanned outages of production site.
    Datagaurd has Failover and Switchover( planned ) methods, These are not automatic, but have to be explicitly initiated by the administrator( So there will be downtime but minimal). Once initiated, Datagaurd automates the processes involved.
    - S K A
    Edited by: user12297346 on Jan 27, 2010 7:13 AM

  • Fusion Middleware, Disaster Recovery Sites with Oracle Applications

    I have oracle applications EBS R12.x.x deployed with one disaster recovery site. I have some composite applications built on SOA 11g suite deployed at OFM which is taking care of my EBS R12.x.x (not disaster recovery site) instance. When my EBS R12.x.x down, is it possible that services deployed at OFM starts taking care of my disaster recovery site.
    Regards

    There really aren't any stupid questions, just dumb answers :-)
    Have taken a look at B/R section in Admin Guide?
    For 10.1.3.x refer this:
    http://download.oracle.com/docs/cd/B32110_01/core.1013/b32196/part5.htm#i436649
    For 10.1.2.x refer this:
    http://download.oracle.com/docs/cd/B14099_19/core.1012/b13995/part5.htm#i436649
    Hope this will help.
    Thanks
    Shail

  • Disaster Recovery site for Exchange 2013

    Hi, I have to build DR site with Exchange 2013 environment and unable to see document for Exchange 2013 perspective.
    In new environment will contain 10 CAS/MBS co-located servers in primary datacenter with two mailbox copies and disaster recovery site with 5 Exchange 2013 CAS/MBS co-located servers with one database copy in blocked activation mode. Any document related
    to this screnario would be helpful. The required solution is when all the servers in PDC goes down then DR site would be activated at DMZ level and Server level. Can I use same IP subnet/Site for the DR site?

    Hi,
    Yes, you can use the same subnet for DR site. If you use the same subnet, you need to use stretched VLAN.
    Here is a related thread for your reference. (This case is for Exchange 2010, but it also applies to Exchange 2013 DAG deployment)
    http://social.technet.microsoft.com/Forums/exchange/en-US/80ca452f-f950-4496-83e8-3067d571bb57/exchange-2010-dag-across-sites-different-subnets-vs-stretched-vlan?forum=exchangesvravailabilityandisasterrecovery
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Need recommentation to setup Disaster recovery site

    Hi All,
    1.What are the basic things we need to analyze before we recommend the business to go for oracle Dataguard for DR setup?
    2. Do you know any technology that will replicate the schema from one datacenter[one primary database ] to another datacenter [secondary or replication database]?
    3. What are the various option to configure the disaster recovery plan at schema level?
    Thanks

    Hello;
    1.What are the basic things we need to analyze before we recommend the business to go for oracle Dataguard for DR setup?Network - bandwidth requirements. How much Redo do you generate? How far away is the standby site? ( proposed network bandwidth and latency )
    Power - UPS requirements ( how will you monitor the standby site )
    RMAN requirements - Where would you backup? At the primary site or the standby site? If Standby what is the cost of extra equipment? How far away should the standby site be?
    Business needs for data ( 24/7, 6 to 6 Monday - Friday etc ) This would help determine a possible protection mode and what switchover failover options you might need.
    Allowed downtime if any ( patches, upgrades etc)
    How much data loss can be tolerated if you have network, hardware issues? For Primary site? If standby site is lost?
    The idea is to develop a plan that meets your business needs.
    2. Do you know any technology that will replicate the schema from one datacenter[one primary database ] to another datacenter [secondary or replication database]?Data Guard Logical Standby since you pick what you want to apply
    Data Pump will also work
    3. What are the various option to configure the disaster recovery plan at schema level?Going to depend upon how much protect the business requires. If all you want is a copy then Data Pump might work.
    If you require zero data loss then Data Guard is the way to go.
    Frankly I would not use a Logical Standby, I would use a physical standby so I could switchover.
    A Logical Standby is a nice idea, but a physical gives you an exact copy and I believe is much easier to maintain.
    Best Regards
    mseberg

  • EP6 disaster recovery environment setup

    I would like to check if anyone on (EP6 SP2 patch 5, Windows 2003 server platform, Oracle database) who may have setup a disaster recovery (DR) environment (obviously in a different location to their production environment). We are also using KM and collaboration.
    We need to create an off-site DR environment for our EP6 solution and need to replicate data to this site every 4-6 hours so that we could recover in the event of a disaster (and not lose more than 6 hours worth of data).
    If you know have experience or know of someone who has done this before,(Windows platform), pls let me know.

    Hi Rajev,
    Duplicating your EP6 installation on a differend server is rather straightforward, so I will not go into that part.  With respect to your Oracle DB, one way of doing this would be to cross-link your log files to the DR server.  Then in case of recovery, you would only need to bring-up the Oracle DB, apply the log files, and then startup your EP6 instance.  Depending on the hardware you're using, your DR environment shoud be able to take over within a matter of 10-15 minutes.

  • RAC at Disaster Recovery site?

    HI
    I am having two node RAC production database right now. Now i want to implement disaster recovery using oracle data guard and for that also i am planning to go for 2 node RAC. Is it possible to implement two node RAC at disaster recover site. If yes then please send me link for the document that is related to this implementation.
    DB Version:10.2.0.1
    OS:LINUX
    Thank You....

    hi,
    yes its similar to normal stanby crearttion
    http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimaryRACPhysicalStandby.pdf
    http://www.dba-oracle.com/real_application_clusters_rac_grid/single_instance.htm
    regards,
    Deepak

  • Recovering Archivedlogs on a disaster recovery site

    DBA's need you help.
    I have oracle 9i standard edition, management has asked to develop disater recovery solution without adding any extra cost(ie no tools to be bought). I am doing some research with RMAN to do this. I have programs to move the archived logs from production to disaster site.
    I have my disaster database in sink with my production till yesterday's full backup. Now today evening i just want to apply the todays archivedlogs backed up from production site. Is it possible to do this and how? Remember i will not restore the entire backup and then do the recovery. One more point i also have control file backup for today.
    Your responses are appreciated.
    Thanks in advance
    Amit

    hi,
    i believe it is not possible to recover your db by applying the archivelog to disaster site.when you restore your db from the previous backups then it becomes a seperate db,now consider the situtaion on your production db ...
    users are making changes to prod server and this causes lots of arhivelogs to be generated on prod server,now the ctlfile of prod db knows the name and location of archivelogs,And if you perform rcovery on prod site then it is ok,but if you want to recover your disaster db by using these logs then the disaster site ctlfile dosen't know about the location and name of the archivelogs which was generated on prod site.because both db's ctl file is out syncronisation.
    now if you only concerned bout the changes to be made on disaster site then you have an option of creating matrilized views on disaster site and keep syncronise it with prod db.
    in your scenario you need to create a standy db to accomplish your tasks,but as you have standerd edition then it is also not possible to create a standby db.but i believe there must be some alternate ways to achieve this in your existing standerd edition just use google to make it true.
    hare krishna
    alok

  • Disaster Recovery site failover

    Hi all
    Can someone please assist me, im trying to setup a failover between my primary site and my DR site. I have attached a network connectivity diagram any help you can give me is greatly appreciated.
    With Thanks

    You are best discussing the licensing implications with your Oracle account manager rather than posting here as it is only via that route that you will get a defnitive answer applicable to your specific companies contractual agreements with Oracle.

  • Disaster Recovery (DR) Setup

    Hi All,
    I need to have a fail-over system for BODS so that if Prod goes down, the DR version can take-over as soon as possible.
    Whereas I can install BDOS on the DR box, and setup SQLServer replication for the database itself fro repositories etc, what I don't understand is how the DR system would be able to take over from Prod properly given that Jobserver ports, access server ports, Management Console settings, Tomcat settings, the server name itself (for RFC Server links and other DS console links etc) and the URL for Webservice provision and WSDL -- All these things would be different wouldn't they?
    So, what can be done to set up a fully replicating DR box that, with minimal effort, could replace the Prod as closely as possible? How to keep everythign in sync that isn't in the repository database?
    Thanks,
    Flip.

    Hi Flip,
    I'm also interested in a DR solution. I hope that someone can help us out.
    Cheers,
    Mike

  • Composition  Disaster Recovery - Mirroring

    Hi Experts,
    I am planning to setup Disaster Recovery site for the current Production.
    The Environment is:
    SAP NetWeaver 7.2 SR 1
    DB2 9.1 on AIX 6.1
    I am quite doubt on the strategy of mirroring the java. We have few CAFs and BPM running in current production.
    Kindly provide your valuable inputs.
    Regards,
    Nikhil Bose

    As per the documentation, we are following a full off-line back up weekly and a delta daily.  Of course, this serves us the DR site. We doubt whether this is enough to bring back the CAF process states.
    There is a custom table in R/3 storing CAF process-state specific information. For this reason, we are thinking of doing the full off-line backup daily.
    Kindly let me know any thought/concerns on this approach.
    Regards,
    Nikhil.

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

Maybe you are looking for