Oracle Business/Disaster Recovery Test Plan ?

I've been asked to create a business/disaster recovery plan (Cover our Oracle environment) outlining what to test in the event of a DR/BR situation once the DB has been restored. Does anybody have a word template or any information would assist me in this task
Thanks

I cannot give you a templace since that would be a site specific confidential documents; however, you really do not need one.
You might just consider adding a note that the exact steps required would depend on the exact nature of the diaster but in all cases would basically follow the pattern of
restore missing files
forward recovery the restored database using the backed up archive logs
open the restored, recovered database
Upon startup Oracle will check itself for consistency. If the database is found to be consisten, which it should be, then the database will be opened. The application can now be started. No additional checks by the DBA are required.
In the event the database is not consistent then the steps above would be repeated for the file(s) not restored as part of the first attempt and the process repeated. Error information will be logged to the database alert log file.
HTH -- Mark D Powell --

Similar Messages

  • 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

  • Oracle VM disaster recovery network meta file discovery fails.

    I am using the Oracle White Paper "Oracle VM 3: Integrating Oracle VM into a Disaster Recovery Solution using SAN" 
    http://www.oracle.com/technetwork/server-storage/vm/ovm3-disaster-recovery-1872591.pdf
    The problem I am facing is that during the server discovery process in part 2 step  8 the meta network config files from the Primary site are not being recognized by the servers at the DR Site.
    I received no errors during the DR Site server discoverer process which should have picked up the meta network config files brought over from the Primary Site OVM servers. I have rediscovered the servers and I have restarted the servers with no success. I am stuck any help or guidance would be appreciated.
    Thank you, Russell

    After working with Greg King the Author of "Oracle VM 3: Integrating Oracle VM into a Disaster Recovery Solution using SAN" and Sairam Thota from Oracle support, we have come to the conclusion that this is a bug. We did upgrade to OVM 3.2.6 from OVM 3.2.1 with no success on resolving this issue. However, Greg did get the network config files working on the DR site but he had to do it manually. The SR with Oracle that I created is still open and I am awaiting a bug number to be assigned for this issue.
    Thank you, Russell

  • Testmanagement: transport of business blueprints and test plans?

    For the moment we have  the following situation:
    We have a 3 system landscape. (development system, test system and productive system)
    On the the test system, the testmanagment module (testworkbench) was integrated. This is used by 5 test projects from extern SAP systems.
    My question: Is there a possibility to transport the Businesses Blueprints and the test plans of the actual test projects into the productive system?

    Hello Marc,
    We have experienced similar problems. A transport of the test plan and copies of the test plans have resulted in us loosing status values and test notes. 
    I was informed it had to do with the fact the information is stored in the GUI. How I don't know, I am not a technical person.
    I was wondering if you may have encountered the similar problems I have had above and found ways around it.
    You can reach me at [email protected] as well.

  • Outlook Freeze during Disaster Recovery Test

    Hi Guys
    Our Exchange Infrastructure is configured as followed (All Servers belong to 1 AD-Site):
    Main Datacenter:
    2x Exchange 2010 *MBX Role with DAG*
    2x Exchnage 2010 *CAS/HT*
    DR-Site Datacenter
    1x Exchange 2010 *CAS/HT/MBX Role with DAG*
    1x Exchange 2010 *MBX with DAG*
    We had our DR-Site test and a strage problem turned up.
    The Mailbox (DAG Datacenter Switchover) and Hub-Transport Part worked well and everything was failovered successfully to the DR-Site Enviroment. 
    For the CAS Part we configured the CAS Array  DNS-Record (mail.internal.domain.tld),
    pointing to the DR-Site Server. That worked fine, but the Outlook performance was awful.
    Within Outlook (without Cache Modus) we weren't able to open or send Mails without
    experiencing  Outlook freezes.
    The Outlook functions were working but the User Expirience was very bad (Freezing, Not responding etc.).
    Have someone exprirenced such problems? If yes, do you have any solutions?
    Thanks
    Azim

    Hello Hany, thanks for the Answer.
    For the Test we shut down all Main-Site Server's.
    There were no Exchange System's running in the main site during the test.
    We haven't checked the link utilization.
    J

  • 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

  • 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

  • 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 of remaining OVM server

    Hi,
    I hope some of you can help me with some disaster recovery tests I have to do shortly.
    The environment has 2 OVM servers: servre1 and server2 in a server pool.
    Server1 has the cluster filesystem shared to it via multiipathing, and in turn, server1 shares the repository and cluster fs with server2 via NFS.
    In the meantime, there are other LUNS shared with just server2, which are being replicated with the repository and cluster fs that is currently being used.
    If server1 "dies" and this is easy to simulate as just shutting it down, it will stop sharing the repository and fs with server2, the server pool will have errors, and so will server 1 (it cannot be contacted), and so will server2 (it has lost access to repository and cluster fs).
    Oracle documentation explains very clearly how to add and remove server pools and servers neatly, but it makes no mention of how to clean up a server in order to reuse in on a new server pool, with a new repository, in this case, the replicated LUNs that were only in server2.
    Has any of you done something similar to this? Do I have to go into the OVM Manager database at row level to delete every mention of the old repository? Is there a way of cleaning up the server2 for reuse (other than reinstalling)? In OVM 2.2 there was a cleanup.py script, but I didn´t find such script in 3.0.3...
    Any suggestions on how to test this will be welcome. If I have overlooked some useful documentation on this, please point me to it...
    Regards,
    T.

    Dan,
    do you mean
    sh ./ovm_upgrade.sh dbuser=ovs dbpass=<password> --fixup
    Regards,
    T.

  • Looking for comment on disaster recovery plan

    Looking for some comment on where we are and where we’re planning on going with our Continuity of Operations / Disaster Recovery plan.
    Current setup is Oracle 10.2.0.2.0 on HP-UX Itanium 64-bit. OAS / Forms 9i on a separate HP-UX Itanium box. We do not have control over the version of Oracle or the hardware. I am pushing the powers that be on upgrading to 10.2.0.4, but am not holding my breath.
    Basic backup is threefold. DB is in archivelog mode. RMAN full backup is taken weekly. Incremental backup taken daily. These backups are to disk. In addition, a daily full-system backup (to tape) is done with the db shut down, providing a daily cold backup as well as backup of the online backups. Also daily exports – full and schema specific.
    All db files are on an HP SAN unit. SAN replication software is used to mirror all i/o to a similar unit located at a sister site. Likewise, they replicate their SAN to ours. Each site has a pair of backup servers to be used by the other site if needed. Sister site has already tested loading our backup servers, mounting the mirror of their SAN, and starting the db.
    Since sister site is a couple of hours away and crosses major network boundaries, management would like to also put up a DataGuard standby at a facility only 30 minutes away and within our own network. Plan is to host that on duplicate HP servers, but disk would be on a NAS instead of a SAN.
    I have managed a DataGuard setup, but did not create/configure it, so am now digging into the docs, starting with the DataGuard Concepts. I’ve never worked with NAS and am not clear on how it differs from SAN, and what the implications are.
    I'm looking for any comment, especially any red flags, on what I’ve described.

    Satish Kandi wrote:
    Not an expert comment on your setup but just the thoughts that came to my mind while reading this...
    1. What is the setup for backup preservation? Is it in one of the servers only? Is the backup also replicated?Belt and suspenders. The backup location on disk is part of what gets mirrored to the sister SAN. Plus, the nightly system backup to tape picks it up as well.
    2. What about OAS/Forms 9i backup? You have not mentioned anything about that.That is also mirrored to the sister SAN.
    3. What is the archive log generation frequency? Or how much data loss can you afford?A typical day will see one or two dozen archivelog files.
    >
    In addition, a daily full-system backup (to tape) is done with the db shut down, providing a daily cold backup as well as backup of the online backupsLucky you :-) but I don't see a need for this with the levels of backup that you have (especially with RMAN weekly backup and daily archive log backup). No, no need, but it does give us another layer at no real cost. This cold backup is really just a byproduct of a daily full system shutdown and backup. We have a high tolerance for system down time, but low tolerance for data loss.

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

  • 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 on a new host. Oracle 11.1.0.6

    Oracle 11.1.0.6, windows server 2003 R2 Service Pack 2 x64)
    I need to test disaster recovery on a new host(with diferent name).
    It looks like I am able to complete recovery stage but dbcontrol doesn't work for me.
    I was told: if you change host name or ip address you should delete repository and recreate it.
    Do I need to import emkey.ora file on a new host as well?
    I used this post
    11g Disaster recovery on a new host.

    restored database on a new host
    copied emkey.ora to a new host c:\oracle\product\11.1.0\db_1\sysman\config
    set ORACLE_SID=ORA2
    run cmd
    C:\oracle\product\11.1.0\db_1\BIN>emctl config emkey -emkeyfile C:\oracle\produc
    t\11.1.0\db_1\sysman\config\emkey.ora -force
    Oracle Enterprise Manager 11g Database Control Release 11.1.0.6.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Please enter repository password:
    The Em Key has been configured successfully.
    C:\oracle\product\11.1.0\db_1\BIN>emctl config emkey -copy_to_repos
    Oracle Enterprise Manager 11g Database Control Release 11.1.0.6.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Please enter repository password:
    The Em Key has been copied to the Management Repository. This operation will cau
    se the Em Key to become unsecure.
    After the required operation has been completed, secure the Em Key by running "e
    mctl config emkey -remove_from_repos".
    emctl.bat stop dbconsole
    emctl config emkey -repos -sysman_pwd password
    emctl secure dbconsole -sysman_pwd password
    emctl.bat start dbconsole
    now able to open
    https://oratest05.domainname.com:1158/em/
    but unable to logon
    Your username and/or password are invalid.

  • How to migrate Planning from Production to Disaster-Recovery server?

    We are using Planning 11.1.1.3 Oracle repository. Presently our DR Planning Application name is different than production's name, and the DR's Windows server names are different from Production's. Otherwise, all other configuration the same.
    How do we migrate Planning from Production to Disaster-Recovery server? We stopped Planning on DR server. Then we exported production planning Oracle repository and imported it to DR Planning. We restarted DR's Planning. DR planning seems to be running fine, but I am afraid to click "Refresh Planning" on DR Planning - it might update Production server. So how can I be sure DR and Production planning are disconnected ?
    Is there anything we need to do? This method seems to be faster than migrating with LCM.
    Edited by: Essbase Fan on Oct 18, 2010 10:11 AM

    You are definitely go about it the correct way, if you are migrating the whole planning application I have to agree it is a safer and quicker route.
    The connection information to essbase is stored in the planning system database/schema so as long as you have not migrated that then you should be good to refresh.
    To put your mind at rest, log into the planning application and edit the datasource associated with the application then you will see where the essbase server is it is going to refresh.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • 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

Maybe you are looking for