Disaster Recovery Solution

I have 2 copes of the same database on 2 different server at two different locations. I have to synchronize the data 100% between the two databases... Please help me to select an appropriate solution to accomplish this.
The 2 databases should be always online
What I can think of is
- Merge Replication.
- Transactional Replication with Updatable subscription..
If you can point some other solutions that would be really great... how about Mirroring.. If I use this I may need a 2 way mirroring... is this possible.

Hi Sudhakar,
According to your description, there are lots of built-in ways in SQL Server
to make two servers synchronize. Some points you should take into account, for example, how much bandwidth and latency between two server, and the size of two database, how often and how much do data change and so on. you can choose the method
most suited for your needs. Merge replication allows various sites to work autonomously and later merge updates into a single. As other post, you can choose replication as a disaster recovery solution. In database mirroring, secondary database
is in an offline mode while mirroring is in place. This can ensure integrity in the secondary database in the event of a failover being required.
For more information, see:
Selecting the Appropriate Type of Replication:
http://technet.microsoft.com/en-us/library/ms152565(v=sql.105).aspx
Replication VS Mirroring, and what to use for a Disaster Recovery setup:
http://simplesql.blogspot.in/2011/01/replication-vs-mirroring-and-what-to.html
Thanks,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support

Similar Messages

Disaster Recovery Solutions for KVM Hypervisors

Thanks to all the help and ideas in my Server Specs for Virtual Environment thread, I think a hyper-converged solution is going to be the right fit for my small business environment. I’m looking at hyper-converged systems because it reduces the overall management of the virtual world. This is important for me as well since I am the “all-one-IT-guy” running everything from programming, help desk support, and sys admin roles here at the office.
Question - Scale Computing offers a disaster recovery solution that allows one to have a secondary HC3 stack at a different geographical location. Thus if one location gets wiped out, you can fall back to your secondary.
My company does not have a another geographical location, so I was looking at data center solutions to replicate to. It appears that most data centers only support Hyper-V and...
This topic first appeared in the Spiceworks Community

Thanks to all the help and ideas in my Server Specs for Virtual Environment thread, I think a hyper-converged solution is going to be the right fit for my small business environment. I’m looking at hyper-converged systems because it reduces the overall management of the virtual world. This is important for me as well since I am the “all-one-IT-guy” running everything from programming, help desk support, and sys admin roles here at the office.
Question - Scale Computing offers a disaster recovery solution that allows one to have a secondary HC3 stack at a different geographical location. Thus if one location gets wiped out, you can fall back to your secondary.
My company does not have a another geographical location, so I was looking at data center solutions to replicate to. It appears that most data centers only support Hyper-V and...
This topic first appeared in the Spiceworks Community

Need disaster recovery solution.

Hi Experties,
We r having medium size database (15 GB), which was very important. Currently we a doing Export/Import as our backup utility. We have several branches which r interconnected with main database via vpn. we need to have exact copy of main database in the branches. Also we need exat copy of main database in our location in case of failure.
Please advice on this and help me. If u need further info, pls feed free to contact me.

An export is worth only slightly more than zero ... it is not a backup.
1. Turn on Archive Logging
2. Learn to use RMAN
3. Assuming an Oracle version currently still supported use Streams or Data Guard if appropriate
Again ... Export/Import is not a backup utility. Never has been and was never intended to serve that purpose.

Disaster Recovery Solution (on a budget)

Hello.
I am using Oracle Standard Edition 11g R1 RAC installed on RHEL 5, my datafiles and RMAN backups are on ASM diskgroups. I am not prepared to upgrade to Enterprise Edition at this time for licensing reasons ($$).
My question is this: There is a feature in MS SQL Server called “Log shipping” that I am trying to mimic in my oracle environment, for DR on a remote site. We cannot use Data Guard because we are limited to Standard Edition.
I am aware of archive log destination duplexing, but don’t want to use that because if the connectivity to the DR site drops then Oracle will hang there until it can successfully archive the redo log. We don’t want Oracle to hang if the path to the remote site is down.
I know already about mandatory and optional archive destinations but I don’t want the make the DR archive destination “optional”.
If data guard is out of the question and duplexing my archive destinations is out of the question… can anyone out there suggest some alternatives?
CJ

You could specify a second (non-ASM) archive log destination locally and write your own scripts to copy the archived logs to the DR machine and your own scripts to apply those archived logs. You may be able to do this just by copying the data files out of the ASM diskgroup to the file system on the remote server, but I'm not certain this is possible.
You may want to take a look at this thread Re: DB standby with 10g Standard Edition which includes a link to Niall Litchfield's "You Probably Don't Need DataGuard" presentation.
Justin

Seeking best practice for disaster recovery for osx server

I am seeking a solid disaster recovery solution. I would be happy if it complements Time Machine, but I don't require that.
I use DAR2 for the linux systems, but with the aid of nice UI provided by the distro vendor. It provides all the files necessary to follow up a clean base OS install with a file restore to provide a full recovery from a disaster.
I just placed a new Mac Mini Server with the Promise Tech DS4600 in service, so I am eager to put a plan in place.
What do other Mac OS Server users do?
I would be most grateful for links to articles, products and suggestions.

For anyone who comes across this post, here is what I settled on:
The server is a mac mini server and is configured with RAID 1 over the two hard disks. I use DAR to backup the linux boxes to the OSX Server. Carbon Copy Cloner is used to backup the OSX Server to a 2 terabyte storage array.
Hopefully this will suffice for the time being. I continue to look for better approaches.

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

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

ACTIVE/ACTIVE Disaster Recovery configuration

If I have two separate 10.2.0 RAC databases in two separate geographical locations and each database is receiving updates and sending the changes to the other database via Streams, how would you configure a disaster recovery solution for this?
In this scenario, each database is intended to be a copy of the other. It is an ACTIVE/ACTIVE type of setup.
Do you need also have a data guard database for each of these databases to support disaster recovery?
Thanks for your feedback.

Hello Sergio,
To get to Ironport Dcoumentation, please do the following:
1) go to www.cisco.com
2) Login with CCO id and password
3) Select support
4) On resulting page, under Prduct Name, select Security
5) You should see "Email Security" and "Web Security" option there, which will bring you to the Documents.
For WSA the doc guides are here http://www.cisco.com/en/US/customer/products/ps10164/products_user_guide_list.html
For The ESA the doc guides are here http://www.cisco.com/en/US/customer/products/ps10154/products_user_guide_list.html
Regards,
Eric

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

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

Disaster Recovery set-up for SharePoint 2013

Hi,
We are migrating our SP2010 application to SP2013. It would be on-premise setup using virtual environment.
To handle disaster recovery situation, it has been planned to have two identical farms (active, passive) hosted in two different datacenters.
I have prior knowledge of disaster recovery only at the content DB level.
My Question is how do we make two farm identical and how do we keep Database of both the farm always in sync.
Also if a custom solution is pushed into one of the farm, how does it replicate to the other farm.
Can someone please help me in understanding this D/R situation.
Thanks,
Rahul

Metalogix Replicator will replicate content, but nothing below the Web Application level (you'd still have to configure the SAs, Central Admin settings, deploy solutions, etc.).
While AlwaysOn is a good choice, do remember that ASync AO is not supported across all of SharePoint's databases (see
http://technet.microsoft.com/en-us/library/jj841106.aspx). LogShipping is a good choice, especially with content databases as they can be placed in a read only mode on the DR farm for an
active crawl to be completed against them.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Welcome to the SQL Server Disaster Recovery and Availability Forum

(Edited 8/14/2009 to correct links - Paul)
Hello everyone and welcome to the SQL Server Disaster Recovery and Availability forum. The goal of this Forum is to offer a gathering place for SQL Server users to discuss:
Using backup and restore
Using DBCC, including interpreting output from CHECKDB and related commands
Diagnosing and recovering from hardware issues
Planning/executing a disaster recovery and/or high-availability strategy, including choosing technologies to use
The forum will have Microsoft experts in all these areas and so we should be able to answer any question. Hopefully everyone on the forum will contribute not only questions, but opinions and answers as well. I’m looking forward to seeing this becoming a vibrant forum.
This post has information to help you understand what questions to post here, and where to post questions about other technologies as well as some tips to help you find answers to your questions more quickly and how to ask a good question. See you in the group!
Paul Randal
Lead Program Manager, SQL Storage Engine and SQL Express
Be a good citizen of the Forum
When an answer resolves your problem, please mark the thread as Answered. This makes it easier for others to find the solution to this problem when they search for it later. If you find a post particularly helpful, click the link indicating that it was helpful
What to post in this forum
It seems obvious, but this forum is for discussion and questions around disaster recovery and availability using SQL Server. When you want to discuss something that is specific to those areas, this is the place to be. There are several other forums related to specific technologies you may be interested in, so if your question falls into one of these areas where there is a better batch of experts to answer your question, we’ll just move your post to that Forum so those experts can answer. Any alerts you set up will move with the post, so you’ll still get notification. Here are a few of the other forums that you might find interesting:
SQL Server Setup & Upgrade – This is where to ask all your setup and upgrade related questions. (http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/threads)
Database Mirroring – This is the best place to ask Database Mirroring how-to questions. (http://social.msdn.microsoft.com/Forums/en-US/sqldatabasemirroring/threads)
SQL Server Replication – If you’ve already decided to use Replication, check out this forum. (http://social.msdn.microsoft.com/Forums/en-US/sqlreplication/threads)
SQL Server Database Engine – Great forum for general information about engine issues such as performance, FTS, etc. (http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/threads)
How to find your answer faster
There is a wealth of information already available to help you answer your questions. Finding an answer via a few quick searches is much quicker than posting a question and waiting for an answer. Here are some great places to start your research:
SQL Server 2005 Books Onlinne
Search it online at http://msdn2.microsoft.com
Download the full version of the BOL from here
Microsoft Support Knowledge Base:
Search it online at http://support.microsoft.com
Search the SQL Storage Engine PM Team Blog:
The blog is located at https://blogs.msdn.com/sqlserverstorageengine/default.aspx
Search other SQL Forums and Web Sites:
MSN Search: http://www.bing.com/
Or use your favorite search engine
How to ask a good question
Make sure to give all the pertinent information that people will need to answer your question. Questions like “I got an IO error, any ideas?” or “What’s the best technology for me to use?” will likely go unanswered, or at best just result in a request for more information. Here are some ideas of what to include:
For the “I got an IO error, any ideas?” scenario:
The exact error message. (The SQL Errorlog and Windows Event Logs can be a rich source of information. See the section on error logs below.)
What were you doing when you got the error message?
When did this start happening?
Any troubleshooting you’ve already done. (e.g. “I’ve already checked all the firmware and it’s up-to-date” or "I've run SQLIOStress and everything looks OK" or "I ran DBCC CHECKDB and the output is <blah>")
Any unusual occurrences before the error occurred (e.g. someone tripped the power switch, a disk in a RAID5 array died)
If relevant, the output from ‘DBCC CHECKDB (yourdbname) WITH ALL_ERRORMSGS, NO_INFOMSGS’
The SQL Server version and service pack level
For the “What’s the best technology for me to use?” scenario:
What exactly are you trying to do? Enable local hardware redundancy? Geo-clustering? Instance-level failover? Minimize downtime during recovery from IO errors with a single-system?
What are the SLAs (Service Level Agreements) you must meet? (e.g. an uptime percentage requirement, a minimum data-loss in the event of a disaster requirement, a maximum downtime in the event of a disaster requirement)
What hardware restrictions do you have? (e.g. “I’m limited to a single system” or “I have several worldwide mirror sites but the size of the pipe between them is limited to X Mbps”)
What kind of workload does you application have? (or is it a mixture of applications consolidated on a single server, each with different SLAs) How much transaction log volume is generated?
What kind of regular maintenance does your workload demand that you perform (e.g. “the update pattern of my main table is such that fragmentation increases in the clustered index, slowing down the most common queries so there’s a need to perform some fragmentation removal regularly”)
Finding the Logs
You will often find more information about an error by looking in the Error and Event logs. There are two sets of logs that are interesting:
SQL Error Log: default location: C:\Program Files\Microsoft SQL Server\MSSQL.#\MSSQL\LOG (Note: The # changes depending on the ID number for the installed Instance. This is 1 for the first installation of SQL Server, but if you have mulitple instances, you will need to determine the ID number you’re working with. See the BOL for more information about Instance ID numbers.)
Windows Event Log: Go to the Event Viewer in the Administrative Tools section of the Start Menu. The System event log will show details of IO subsystem problems. The Application event log will show details of SQL Server problems.

hi,I have a question on sql database high availability. I have tried using database mirroring, where I am using sql standard edition, in this database mirroring of synchronous mode is the only option available, and it is giving problem, like sql time out errors on my applicatons since i had put in the database mirroring, as asynchronous is only available on enterprise version, is there any suggestions on this. thanks ---vijay

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

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

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

Planning Disaster Recovery Site for SAP ERP ECC 6.0

Dear All,
I am planning for DR ( Disaster Recovery ) Site. Our current environment is
Production Site
OS        : AIX 5.3
DB        : IBM DB2      version 8.2
SAP      : SAP ERP 6.0 ECC 6
Disaster Recovery Site
OS        : AIX 6.1
DB        : IBM DB2      version 9.5
SAP      : SAP ERP 6.0 ECC 6
I have following confusion in planning the solution.
1 - If I export the data at db level from production site and import that data in DR Site ... than DR Site will be equivalent to Production Site or not.
2 - if answer of point 1 is yes then for SAP DR ... HADR is the best solution or there is any other better solution exist.
regards
Syed Saifuddin

Hello Syed,
If you export from the prod db and import into the disastor recover db then they will be the same provided that SAP environment is all the same. I would recommend that you update the prod side to the same db2 release and fixpack level as soon as possible though as 9.5 (or even better 9.7) has some advanced features that make administration alot easier and save much space.
HADR would be the best setup for disaster recovery in db6 environment.
Check the following documentation which should answer most of your queries.
SAP Note 960843 # DB6:Installation SA MP
"High Availability and Disaster Recovery Options for DB2 on Linux, UNIX,
and Windows"
http://www.redbooks.ibm.com/redbooks/pdfs/sg247363.pdf
"Data Recovery and High Availability Guide and Reference"
http://publibfp.boulder.ibm.com/epubs/pdf/c1042280.pdf
Please update if questions remain unanswered.
Regards,
Paul

How to implement Disaster Recovery in TimesTen?

hello, chris:
we have a requirement to implement disaster recovery from remote when the master and standby nodes are failover in local. how to implement it in timesten? Can master standby pairs with subscribers mode caryy out it? when the master and standby nodes are fail, can subscriber node take over the application?? thank you.

The best, and recommended, solution for this is to have an active/standby pair located locally as the primary mechanism for high-availability and to configure a remote readonly subscriber datastore. In the event that the primary site completely fails, the remote subscriber can be easily (few seconds) promoted to an active to form the basis of a new active/standby pair at the remote site.
It is not supported to split an active/standby pair across a network connection that is anything less than LAN grade but a remote subscriber can be located across any reasonable network connection (WAN, VPN etc.) as long as there is sufficient bandwidth and the latency is not too high.
Chris

Disaster Recovery Solution

Similar Messages

Maybe you are looking for