Composition Disaster Recovery - Mirroring

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

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

Similar Messages

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

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/

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.

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.

Disaster Recovery Soltuion

Hi Everyone,
In the case of Production system unavailable, by the destruction like due to fire or water floods, to avoid the system down-time for couple of days/weeks. We are planning to go for Disaster Recovery solution.
We are planning to go with this solution for our production systems like EHP4 for SAP ERP 6.0/NW 7.01, Solution Manager 7.0 EHP1 systems.
Our landscape was configured in Distributed systems (CI+DB), OS:Win2003 and DB: MS SQL Server 2005.
My doubts are as follows.
1.) I am not able to find any document for DR solution, can anyone guide me where can I find the Documents releated to DR Solution
2.) In the DR Solution Systems as well we need to connect to SAP or not? I mean for remote support or RFC Connections and etc?
3.) Where can I find the Best Practices for DR? I have gone through the Best Practices but not able to find the proper things related to DR.
4.) Can anyone guide me the correct procedure or steps for the DR solution to follow?
I'm planning to do like these OS intallation, DB installation then SAP Installation then copy the Back-up of Production system to Back-up system (DR solution system).
Thanks and Regards
Pavan

Hello Pavan,
I have found the following documentation about Disaster recovery:
http://help.sap.com/saphelp_erp2004/helpdata/en/6b/bd91381182d910e10000009b38f8cf/
frameset.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/f2/31ad5c810c11d288ec0000e8200722/
frameset.htm
Also the following notes:
437160 : MS Disaster Recovery Articles for MS SQL Server
965908 : SQL Server Database Mirroring and SAP Applications
741289 : Profile parameters of the J2EE Engine are lost
(This Note indicate parameters which must be maintained in
the instance profile)
193816 : Restore with SQL Server
799058 : Setting Up Microsoft SQL Server 2005
I hope this information helps you.
Regards,
Blanca

Disaster Recovery - HPSU8

We currently are running HPSU 8.3 and have been tasked with developing a good disaster recovery plan should the server fail. We have purchased a new server that's identical to the production server. Does Hyperion have documentation/recomnedations for restoring HPSU 8 to another server. We are backing up the entire production server nightly. If anyone can point me in the right direction for this I'd appreciate it. I called support, but they just directed me to e-support and told me I should be able to find documentation online but I have been unable to locate this information so i was hoping someone may be able to assist me. Thanks, Bob Cook REZ1

Exactly, the attached doc regarding HANA standby means for high availibility not disaster recovery. if the entire data center goes belly up, there will be no shared disk available. I talked with a few folks from SAP BI area. It seems to me that at this point the best way to handle HANA disaster recovery is manual:
1. Back up HANA to local backup system (storage or tapes) at regular interval (e.g. nightly) and ship (ftp/ship etc.) the back up to DR site.
2. Back up HANA log more frequently (e.g. hourly) and ship the log backups to DR site.
In the event of a DR, the backups shipped to the DR site will be used to restore a HANA DR system. Of course, nomal DR practice still applies, such as, use of virtual names everywhere, change DNS entries, etc. to make the resumption of DR processing at DR site seamless ...
This is very similar to the very early days of RDBMS DR practice. I expect SAP will make the HANA DR less painful by implementing something similar to modern days RDBMS DR solution (e.g. database mirroring, standby db, replication, etc.) in the future.

Crystal Disaster Recovery server

Is there a known best practice to have 2 mirrored Crystal Servers running simulaneously? We have 1 we use in production and we are trying to configure one for disaster recovery. I haven't been able to find anything on this. I welcome any help.

Hello, I'm doing a "Plant ECC6 to do a test disatre / Recovery.
During the installation, I would use the same <sidadm> existing as it is in the PRD.
If I tell you to install it during the same <sidadm> it will overwrite what already exists, or do I just enter the password of existing <sidadm>?

Fusion Middleware, Disaster Recovery Sites with Oracle Applications

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

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

Disaster Recovery 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

Concurrent Transactions,Disaster Recovery

Hello friends,
I have an application on sql server which is used for online reservation.Could you tell me roadmap in order to handle concurrent transaction and disaster recovery plan? I am using sql server 2008 R2.
Thanks in advance.

Hi,
I suggest you read this article:
High Availability and Disaster Recovery (OLTP)---a Technical Reference Guide for Designing Mission-Critical OLTP Solutions
http://msdn.microsoft.com/en-us/library/ms190202.aspx
If one high-availability option cannot meet the requirement, you
may consider combining some of the high-availability options.
The white paper Proven SQL Server Architectures for High Availability and Disaster Recovery2 shows the details of five commonly used architectures:
◦ 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).
The whitepaper also describes the architectures and also presents case studies that illustrate how real-life customers have deployed these architectures to meet their business requirements. You can download it here:
Proven SQL Server Architectures for High Availability and Disaster Recovery
Thanks.
Tracy Cai
TechNet Community Support

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

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

Lync Server 2013 - Disaster Recovery Plan

Hi All,
I am looking for a document which has the information about the different scenarios regarding High Availability and Disaster Recovery and things to perform during that situation
Eg.
If a front end Server is failed. then the load will be moved to another front end server in the pool
similarly back end Server fails, then the load gets moves back to SQL mirroring server by SQL Witness server
Anil Kumar (MCITP)
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Hi Anil
A similar thread for your reference which might help you
https://social.technet.microsoft.com/Forums/lync/en-US/67e5dfa3-92ee-4732-ab1a-48b52f028650/lync-2013-site-resiliency?forum=lyncdeploy
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

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

Composition Disaster Recovery - Mirroring

Similar Messages

Maybe you are looking for