UCM setup DR (Disaster Recovery) environment

Hi all,
We did implementation part in production. Now we are planning setup DR (Disaster Recovery) environment.When ever Production will goes down automatically RD will take place to provide continue services to user, But in installation part of RD little bit challenging,let me know below problems how we can override.
1) While installing UCM in DR environment I need to give Production DB schema details, Is it workout (if I give production DB Schema details , is there any effect in production )
2) All ways production and DR both file systems will sync up every time. How we can achieve these thing?
Thanks.

Vijay,
read this document: http://download.oracle.com/docs/cd/E17904_01/doc.1111/e15250/recommendations.htm#CHDGAEEA
In a nutshell:
- as for installation, configuration, etc. I'd suggest you to use images (OracleVM will do you the service and it's almost free)
- you will need to synchronize database AND file system
- if Oracle DB Enterprise Edition is your database, you may use DataGuard to synchronize primary and secondary locations (DG is free in EE, in SE or other databases you may use Oracle Golden Gate or a third party product)
- for file system you will need a 3rd party system (I was recommended TrueCopy - this very much depends who is your HW provider)
Note that you can use file system synchronization even for database - I'd suggest to use Partitioning option, because the size of files that need to be synchronize will be smaller - but you might transfer also errors in the database, whilst DataGuard will transfer only correct transactions, so your secondary db will always be in a consistent state.

Similar Messages

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.

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.

I want to setup a Disaster Recovery Server for Sharepoint Server 2010

There are four production server running sharepoint server 2010 and one SQL server for
ContentDB management.

DR depends upon your backup stratgies, i.e
1) if you taking full backup of sharepoint using SharePoint tool
2) If you taking just SQL backup( Content DB and Services DB).
3) using the 3rd party tool for backup and recovery.
apart from above, you also have make a decision what point of time you want recovery.
from your questions, what i think for you.
Setup new farm with same SharePoint level.same customization, same services configuration, and same number of web apps.
then backup from Prod server( SQL content DBs) and then restore into new farm and mount them.
this is one time thing, Now you have to make decision, how data move from Prod to QA( i mean frequency i.e daily, monthly etc).
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

OIM 11gR2- Disaster Recovery Setup

Hi,
Does anyone has suggestions/already in place architecture for Deploying OIM11gR2 setup in Disaster Recovery Mode.
Any help is appreciated.
Regards

What are the requirements/expectations out of DR? Do you need to replicate the same infra in terms of NFR's e.g. DR site has same performance and user capacity like production then you need to replicate the production infrastructure/architecture in DR data center. However DR strategy completely depends on Client strategy. In Ideal scenerio DR site is cold (i.e. only active in case of production failure) and has same capacity like production. But depending on the client you may want to propose the scale down version of production on DR site and you can also check if you can keep the DR site active also to increase the solution performance. All this need to think through in terms of criticality of the IAM functionality, cost of infrastructure, cost of licence and DR policy for the Client. Now a days every client prefer RAC database but few clients go with Non RAC databases also with storage/disk backup in DR site on every interval.

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

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

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

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

Disaster Recovery-MS SQL Server 2008 License

We are planning to build a Disaster Recovery environment for Production Environment. Technology used: SharePoint Foundation2010, MSBI and MS Sql Server 2008 Standard.
Current Production Server has SQL Server2008 standard (Core license) installed in it.
Do we need separate MS SQL Server 2008 licence for Disaster Recovery (DR) Server in order to keep the DR and Production database running in both the environments simultaneously.
We don't want to keep database down in DR environment as this impacts our code deployment process.
Each time code gets deployed to Production, we will have to follow few extra steps to keep DR and Production in sync.
Example:
1. Bring up the MS SQL Server database in DR environment
2. Deploy the solution and bring down the DR database.
Please suggest...

We are planning to build a Disaster Recovery environment for Production Environment. Technology used: SharePoint Foundation2010, MSBI and MS Sql Server 2008 Standard.
Current Production Server has SQL Server2008 standard (Core license) installed in it.
Do we need separate MS SQL Server 2008 licence for Disaster Recovery (DR) Server in order to keep the DR and Production database running in both the environments simultaneously.
We don't want to keep database down in DR environment as this impacts our code deployment process.
Each time code gets deployed to Production, we will have to follow few extra steps to keep DR and Production in sync.
Example:
1. Bring up the MS SQL Server database in DR environment
2. Deploy the solution and bring down the DR database.
Please suggest...
Yes you will need license for SQL server in DR environment.
Licensing is wast and non technical question so it will be best answered by Licensing expert.
For more detailed information regarding to the license issue, please call 1-800-426-9400Call: 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00
P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. For international customers, please use the Guide to Worldwide Microsoft Licensing Sites to
Find contact information in your locations.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

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.

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

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

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

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

Cisco Expressway Core & Edge Cluster, or Disaster Recovery Setup

Hi All,
Dear experts,
I have two sites HQ & Branch.below are my questions for Expressway Core & Edge Cluster
1. Can i create one cluster for 6 sever for Expressway Core and distribute 3 server in HQ & 3 server in Branch for HA
2. Can i create one cluster for 6 sever for Expressway Edge and distribute 3 server in HQ & 3 server in Branch for HA
3. How would be the DNS SRV records and call flow work if the main site Expressway Edge goes down in HQ. How the Branch Side Expressway Edge becomes active for B2B calls.
4. What is the best design to have disaster recovery for Expressway core and Expressway Edge between Sites(HQ & Branch)
Regards,
Irf

Regarding 1 and 2, as long as the round trip delay is no more than 30ms maximum, you should be fine. I presume the HQ Branch offices for the Expressway-Core have a shared internal network, since the Core goes inside the corporate network, while the Edge goes in the DMZ or outside the network for public access.
For 3, as long as you have your SRV records setup correct, you can set the priority of which office gets used first, and then second, in case of a failure.
I don't have an answer for 4 unfortunately.

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

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

OIM Disaster Recovery Setup

We are in the processing of completing setup of our production environment with OIM 9.1.0.2. Our setup is running on WAS 6.1 in a two node cluster. We run to an Oracle database. For DR we were planning to take a backup of the production database and restore it on the DR database. We would install OIM in WAS on a DR server as well, pointing to the newly restored database.
Does anyone have any pointers on things to watch out for or configuration changes that may need to be done to allow this to work?
Thanks for any assistance,
Rich Shok

What are the requirements/expectations out of DR? Do you need to replicate the same infra in terms of NFR's e.g. DR site has same performance and user capacity like production then you need to replicate the production infrastructure/architecture in DR data center. However DR strategy completely depends on Client strategy. In Ideal scenerio DR site is cold (i.e. only active in case of production failure) and has same capacity like production. But depending on the client you may want to propose the scale down version of production on DR site and you can also check if you can keep the DR site active also to increase the solution performance. All this need to think through in terms of criticality of the IAM functionality, cost of infrastructure, cost of licence and DR policy for the Client. Now a days every client prefer RAC database but few clients go with Non RAC databases also with storage/disk backup in DR site on every interval.

UCM setup DR (Disaster Recovery) environment

Similar Messages

Maybe you are looking for