Automate SQL Disaster Recovery

Hi All,
Need some suggestions on automating the SQL DR tasks. Here is the scenario:
- We have a standby SQL Server which regularly gets updated with the content (through SSIS jobs etc) from the Primary SQL Server
- If the Primary SQL Server goes down, we point Lync pool to the backup SQL Store to restore the functionality while we rebuild the primary SQL Server. However this SQL Store change needs the use of Topology Builder (as SQL Server names are not the same),
a task which cannot be automated using Powershell or SQL scripts.
Can the Topology Builder step be automated in anyway?
PS: In OCS we had all tasks automated by using Update-PoolBackend and other cmdlets to point to the backup SQL Server. We want to do the same in Lync too, thereby reducing manual steps.
--Hakeem

Is your backup SQL server in a remote site or the same site? If it's remote, the only way to provide full HA failover is with a metropolitan data center design with a stretched SQL cluster and VLAN, SAN replication etc. See
this article.
Attempting to replicate or mirror the SQL content (using log shipping or database mirroring) is not supported and doesn't work properly. More info here on my blog http://www.justin-morris.net/sql-database-mirroring-with-lync-server-2010-series-%E2%80%93-backend-databases/.
The introduction of the CMS (xds database) complicates DR somewhat, so you will need to first assess what Lync services you require to be available in a DR situation.
Today, Lync provides voice resiliency quite well in a DR situation, but other services (IM and Presence, Conferencing) require more design work to provide availability in the event of disaster.
Justin Morris | Consultant | Modality Systems
Lync Blog - www.justin-morris.net
Twitter: @jm_deluxe
If this post has been useful please click the green arrow to the left or click "Propose as answer"

Similar Messages

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

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

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

Disaster Recovery in Windows 2003/Cluster, SQL 2000 and R3

Hi,
Can someone share experience/knowledge of disaster recovery scenarios in MSCS/SQL Server/SAP. One of our customer has R3/SQL Server2000/Win 2003 (Cluster).
We would like to evaluate best possible options for the Disaster Recovery which are supported by SAP.
We have thought about
1. Log shipping
2. Standby Database
3. Restore backup on new cluster
4. Homogeneous System copy.
We do not want to go for first two and would like to explore on 3rd and 4th option.
Any links to documents/blogs will be helpful.
Thanks,
Manoj

> I am confused. Option 3 will be restoring backup
Yes - but what will you restore? Everything? If you're running on a cluster it's unlikely that both nodes will fail at the same time so there is still one node that can and will run the software, no?
> and 4 will be sapinst. Isn't it? Are both options supported by SAP?
Yes.
> Is there a SAP standard documentation for building cluster from scratch and build SAP system from backup or sapinst for DR?
The standard installation documentation cover a cluster installation.
> I am sure there will be installation document if it is a fresh installation. But not sure if there is one for DR.
If you have a cluster then you have a high availability already. If a node fails, you will "just" reinstall that node and put it back into the cluster.
What kind of DR scenario are you thinking about?
Markus

SQL SERVER 2014 DISASTER RECOVERY

Hi All,
Please let me know on below topic.
SQL SERVER 2014 DISASTER RECOVERY

Hello,
Please read the following resources:
http://blogs.technet.com/b/dataplatforminsider/archive/2014/04/08/sql-server-2014-brings-on-premises-and-cloud-database-together-to-improve-data-availability-and-disaster-recovery.aspx
http://blogs.technet.com/b/francesco_diaz/archive/2014/02/06/sql-server-2014-alwayson-availability-groups-add-azure-replica-wizard-in-action.aspx
http://blogs.technet.com/b/francesco_diaz/archive/2013/11/15/sql-server-2014-ctp2-alwayson-availability-groups-hybrid-it-scenario-using-windows-azure.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Synchronizing Disaster Recovery site with the production server

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

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

Is anyone doing disaster recovery for a J2EE application?

We generally use database log shipping to maintain a standby database for our ABAP instances. We can successfully fail over our production application to our disaster recovery site with no real issues. With the J2EE instances (EP, ESS/MSS, BI, etc), we have a few concerns:
hostname cannot change, without going through a system copy procedure, so we would have to keep the hostnames in DR the same. (for example, ref: oss note 757692 - changing hostname is not supported)
fully qualified domain name - from what I understand, there are potentially issues with changing the fqdn, for example SSO certificates, BSPs, XI has issues, etc.
we can't keep both hostname and fqdn the same between DR and production, or we could never do a DR test.
Has anyone implemented disaster recovery for any SAP J2EE application that has run into these concerns and addressed them? Input would be greatly appreciated regarding how you addressed these issues, or how you architected your disaster recovery implementation.
Regards,
David Hull
The Walt Disney Company

I haven't done this personally, but I do have some experience with these issues in different HA environments.
To your first point: You can change the hostname, note 757692 tells you exactly how to do it. However like the note says, "Changing the name of a host server in a production system is not automatically supported by SAP." When it says "supported by SAP" I think it means SAP the company, not SAP's software. So I would contact SAP to see if this configuration would be covered under your service agreement. Then you have to think about whether you want to do something that isn't "officially supported" by SAP. Also I'm sure you'll need some kind of additional licensing for the DR systems as their hardware keys will de different.
To your second point: As for SSO certs (SAP Login Tickets), I think they should still work as long as the SID and client number of the issuing system remain the same. I don't think they are hostname or fqdn dependant. For BSPs I would think they would still work as long as they use relative paths rather than absolute paths. And for XI... I have no idea what kind of issues may arise, I'm not an XI guy.
Again, I haven't done what you're describing myself. This is just based on my HA experiences.
Hope this helps a little,
Glenn

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.

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 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] Moving the Essbase server to another physical server

Hi All,
I have 3 Solaris servers part of the EPM 11.1.2.1 environment:
Server1.company.com:
Foundation services, APS, EAS
Server2.company.com:
Essbase Server, Essbase Studio Server.
Installation done on a SAN disk using user ID hypadmin
Server3.company.com:
*Nothing installed here*.
Its the standby server in case Server2 goes down.
Note: I couldn't find any documentation for my below approach... So please understand the risk involved before attempting the same.
Pre-disaster recovery:
I copy the home directory of hypadmin from Server2 to Server3.
During disaster recovery:
I update the Essbase server host name from Server2.company.com to Server3.company.com and similarly update the opmn.xml file.
Finally mount the SAN onto Server2 and start up the services.
Has anyone done the same..? Have you faced any issues? Is there a better way of doing this?
Thanks
Regards,
Kent

Hi,
I believe the usual way of doing this is to have a DR environment, rather than just one server (so for you you would have 2 DR servers). The DR environment has hosts file entries to map Production host names to DR IP addresses.
In DR you are connected to a separate SQL instance and you install and configure the products exactly as you would for Production (exactly the same hostnames).
Then when you are finished you shut down the DR environment and turn on SQL log shipping between the Production and DR databases.
If your Production environment goes down you stop the SQL log shipping, then you can bring up DR and change the DNS names (as required) to give your users access.
For Essbase storage you can either backup Production cubes to DR or mount the Production SAN in DR. The only problem with the latter is that if Production goes down and the SAN is lost you can't bring up DR fully either.
Let me know if you still have questions.
-Dan

Disaster Recovery scenario for MSCS Production system.

Hi
Our production system is on win2008/sql2008 MSCS. We decided to install a disaster recovery system. We will use a database replication software. If we have a standalone production system, not a MSCS system, i know that i can install Disaster Recory system with same SID and hostname and i don't need any homogeneous system copy procedure to switch to DR system. But in our scenario, we have many hostname (sap cluster group, sql cluster group, hostnames of nodes... etc.).
How can i install my DR system (which hostname.. etc.) to make our DR scenario easy?
Best Regards...

You May have trouble with RFC connections:
So, one possible solution is, your new server name(Host name) should be your message server name to minimise the trouble and you have to maintain this for all RFC connections (to Prod ECC system) to virtual host which could be message server.
If I could think if any other possible issues, I will update.
Krishna

Dispatcher status showing stopped for disaster recovery server.

HI,
today to test the data in our disaster recovery server for which we have log shipping every 30minutes we started the server in sap level during the process we can see that work +disp status is showing stopped.when i checked the log files in work directory it is showing below errors.
C sloledb.cpp [OpenOledbConnection,line 22822]: Error/Message: (err 4060, sev 0), Cannot open database "INP" requested by the login. The login failed.
M * LOCATION    SAP-Server atriooonsapdr01_INP_00 on host terhsapdr01 (wp 0)
M * ERROR       tskh_init: db_connect
M *
M * TIME        Mon Oct 06 16:31:42 2008
M * RELEASE     640
M * COMPONENT   Taskhandler
M * VERSION     1
M * RC          13
M * MODULE      thxxhead.c
M * LINE        9780
M * COUNTER     1
kindly suggest what to check and how to resolve.

Hi Anil.
you should be sure if user SAPINPDB exists in the database system and it is mapped to the SAPINPDB user of the DB.... this if you use SQL Server, but the rule should be something like this in other DB systems!!!
Regards
Pedro

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

Automate SQL Disaster Recovery

Similar Messages

Maybe you are looking for