DR (Disaster Recovery) server installation.

Dear Experts,
We have one server for BI PRD. We are not using it at the moment. We wish
to carry out DR (Disaster Recovery) trial on this server. Regarding thiswe have following queries :
1. Do we require separate SAP License key for this server when setup forDR (already SAP license key exists for it as BI server)
2. We will re-install BI on the same server after our DR test so whetherwe need to regenerate License key for BI or not?
3. We have two R/3 PRD servers in HACMP mode in SAN. Can we take the
backup of R/3 PRD and restore it on DR Trial Server? If yes, whether we
will face any problem for existing PRD server?
4. Whether Existing PRD and Trial DR Server will clash or hang since
these will be in the same local network and SAN
Please advise.
Regards,
Kailas Padwale.
BASIS Team.

Hi,
As per your query you have not mentiones here what is your opreting system and whcih SAP verson you are using. If any one need related to implimentaion then we keep in mind to os,sap version,database etc.
Your Question: If you want to DR of PRD then you have to get my answer.
1. Do we require separate SAP License key for this server when setup forDR (already SAP license key exists for it as BI server)
ANS= Yes you can generated from SAP Site becasue now this is BI and you want to DR but for this you have not paid any thing to SAP its free.
2. We will re-install BI on the same server after our DR test so whetherwe need to regenerate License key for BI or not?
ANS=NO becasue you have to use only PRD copy you can not run BI here otherwise how can you say this is DR server. DR Server means you can copy in existing running server, in case you running server get down then within short period you can provide the solution. After rectificaton actual server you will shift in old one.
3. We have two R/3 PRD servers in HACMP mode in SAN. Can we take the
backup of R/3 PRD and restore it on DR Trial Server? If yes, whether we
will face any problem for existing PRD server?
ANS=You can restore backup but you have to take backup only one PRD server and restore it in DR. Just chang your IP Address and rest can be same. You will not face any issue on this if you run in the same network. I will recmond if you use database in DR server itself then good for your running system will not impect.
4. Whether Existing PRD and Trial DR Server will clash or hang since
these will be in the same local network and SAN
ANS= No because you will use seprate IP address and data will be in DR server not in SAN.
In case you need more help, pls get in touch.
Anil

Similar Messages

Disaster Recovery server for SAP and HACMP Cluster script for SAP ECC 6.0

Hi,
I need document for Disaster Recovery server for SAP? I have to configure the DR Server If you have, please share this document if possible.
Have you any cluster script ( HACMP Cluster script for SAP ECC 6.0 ) ?
Thanks & Regards,

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>?

Disaster recovery server

hi experts
i am using
SAP Version: ECC 6.0 SR3
Database Version: 10.2.0.4
OS Version: HP-UX B.11.31
i have a server where O/S installed. i want to make this as a disaster Recovery server.
now i want to know.
1- what is the man power needed.?
2 -which technical guys i needed.?
3-how much time it will take?
4- can a basis consultant only do this job?
5-Is any separate team for DR server installation.
kindly guide me in detail regarding this.
thanks

> SAP Version: ECC 6.0 SR3
> Database Version: 10.2.0.4
> OS Version: HP-UX B.11.31
>
> i have a server where O/S installed. i want to make this as a disaster Recovery server.
> now i want to know.
> 1- what is the man power needed.?
It's possible to do all this with one guy, but if you're inventive you can surely employ more people with this.
> 2 -which technical guys i needed.?
You will need people that are actually capable to do this.
The most likely people for that seem to be HP-UX and Oracle admins.
> 3-how much time it will take?
Depends totally on the business recoverability requirements.
How much downtime can it take until your business breaks?
How much is business willing to pay for that?
Usually you build the whole backup setup around those two questions.
> 4- can a basis consultant only do this job?
Depends on the basis consultant.
Usually those guys can at least recover the database.
> 5-Is any separate team for DR server installation.
Well, if there is one in your company - yes.
Most often and usually there won't be an extrea team for that as ensuring recoverability is one of the prime tasks of every DBA.
regards,
Lars

Datafiles Mismatch in production & disaster recovery server

Datafiles Mismatch in production & disaster recovery server though everything in sync
We performed all the necessary prerequisites & processes related to DRS switchover successfully also our DRS server is constantly updated through logs application in mount state whan we opened DRS database in mount state it opened successfully however when we issued command
Recover database
It dumped with foll errors:
ora-01122 database file 162 failed verification check
ora-01110 data file 162 </oracle/R3P/sapdata7/r3p*****.data>
ora-01251 unknown file header version read for file 162
as I do not remember the exact name now
However upon comparing the same file at production(which was now in shutdown state) the file sizes were mismatching so we went ahead to copy the datafile from production to DRS in database shutdown state at DRS through RCP utitlity of AIX 5.3 since our Operating system is AIX 5.3
Though this remote copy was success
we again started database in mount state & issued command
Recover database
But still it dump the same error but now for another datafile in DRS
I mean I would appreciate if somebody could point out that despite our DRS was constantly being updated through our Production in terms of continuous log application before this activity logs were sync in both the systems also origlos,mirrorlogs & controlfiles were pulled from production system as it is infact the whole structure was as replica of production system , then why did datafile sizes mismatch??
Details
SAP version :- 4.7
WAS :- 620
Database :- Oracle 9.2
Operating system :- AIX 5.3

I am in a process of DR Planning.
My present setup :
O/S : HP-UX 11.31
SAP ECC 6
Oracle 10g Database.
I know about dataguard and i have implemnted same on our other application but not for SAP.
I have ame doubts and I request you to please guide me for the same.
1. SAP License key -- it required hardware key. So will i have to generate license key another hardware key i.e. for machine where standby database.
2. Database on standby site will be in manage recovery mode. Will I have to make any changes or any other file realted to SAP on standby host ? (some i know such as I upgrade SAP kernal, same i have to upgrade at standby host)
Will you give me some link related to document for DR

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

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

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

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

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>?

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

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

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

Could u tell me last applyed archive log in disaster recovery server

Hi DBA'S,
we are using oracle 9.2.0.8 my production database has dr(our dr is not a stand by it is created in diff way) server every time one cron job sync the database and transfer the new logs from production server to dr server. i want to know last applied archive in dr server.
i am using this query select max(sequence#) from v$log_history; it is showing same results in boath production and dr when ever we backup 2 days before archive to some backup directory sync is going to fail
please tell me correct query to find out the last applied archived log in dr server
Thanks&Regards
Tirupathi

we are using oracle 9.2.0.8 my production database has dr(our dr is not a stand by it is created in diff way) server every time one cron job sync the database and transfer the new logs from production server to dr server. i want to know last applied archive in dr server.i am using this query select max(sequence#) from v$log_history; it is showing same results in boath production and dr when ever we backup 2 days before archive to some backup directory sync is going to fail
please tell me correct query to find out the last applied archived log in dr server>
As you are running cron job to bring the dr in sync, i suppose v$log_history might give you the wrong results.In your case check :-
select sequence#,applied from v$archived_log where applied='YES';
select max(sequence#) from v$archived_log where applied='YES';Would like to know, why manual recovery (archive logs being manually applied) is being performed, and not automatic.
In case you switch to automatic below query would be useful :-
select al.thrd "Thread", almax "Last Seq Received", lhmax "Last Seq Applied"
    from (select thread# thrd, max(sequence#) almax
            from v$archived_log
           where resetlogs_change#=(select resetlogs_change# from v$database)
           group by thread#) al,
         (select thread# thrd, max(sequence#) lhmax
           from v$log_history
            where first_time=(select max(first_time) from v$log_history)
           group by thread#) lh
          where al.thrd = lh.thrd;Refer [http://aprakash.wordpress.com/2010/07/21/use-of-varchived_log-and-vlog_history-on-physical-standby/]
HTH
Anand

Disaster Recovery Server for EP 6.0

Hello All,
We are running EP 6.0 with Windows 2003 / MSSQL 2005 platform. We would like to have a DR server for the same. Can we prefer the log shipping method to set up DR server?
For ECC we use the log shipping method in our DR server, but I am not sure if this works for Portal. Please clarify
Regards,
Anand

Hello All,
Any help on this?
Regards,
Anand

Archive Log Gap between Disaster recovery server & Production Server

Hi
Can anybody provide me the script to find out the archive log missing on Production Server means that archive log backed up & deleted from the production server & rest of the Archive logs has been shipped on to the DR server. Means it will shot the gap between production server & DR server until that log which has been deleted from the production server , but next logs has been shipped to the DR server. But rest of the logs only be applied when delete log be restored on the production server & shipped on the DR server.
thanks.
Regards
Ravi Kant Arya

Ravi,
The question is how are you getting the archive logs shipped over to your standby database? If you are doing it via FTP or scripts, then you may want to look at configuring DataGuard to do it for you. Look at "Setting Up Oracle Dataguard for SAP" at:
http://www.oracle.com/us/solutions/sap/wp-ora4sap-dataguard11g-303811.pdf
Good Luck.
Mike Kennedy

Disaster Recovery steps for BO

BO XI R2 SP 1
Oracle10g
Windows 2003
We would like to do a drill for BO recovery and need to know what proper steps would be required.
This is so far I understand; if I'm missing something then please advise.
Take backups of Prod CMS, PMDB and Data warehouse schemas
Restore all these schema's in the DR (disaster recovery) database
Now the issue is when we restore CMS; it shows Prod server information and Infoview doesn't let you log in.
Appreciate any assistance. Thanks

Hi Tim - Thanks for sharing the guide; it was very helpful.
I still have one question;
suppose we take the backup of schemas from production database server connecting to production BO server, say BOPRODmachine.domain.com
and then we restore all schemas in disaster recovery server database and file store on disaster recovery BO server, say BODRmachine.domain.com
How will the restored CMS data recognized this new disaster recovery BO server?
We tried to do that and BODRmachine shows that all servers are running on BOPRODmachine in CMC -> Servers
When we tried to connect via Infoview, it didn't let us as server name was different.
Do we have to rebuild the database for CMS on disaster revocery environment before starting the CMS server?
Please advise. Thanks

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] 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

Mailbox Recovery From Disaster Exchange Server 2013

I have to exchange server EX01 and EX02. Now EX01 have to down didn't run anyway. Default database on EX01 that have to Administrator mailbox and the default database was not member of dag. now i can't move administrator database another database location.
Md. Ramin Hossain

Hi Ramin,
Thank you for your question.
By our understanding, Ex01 didn’t run any way, we could take a disaster recovery by the following steps:
Reset the computer account for the down server;
Install the operating system and name on the new server with the same name as the lost server. Recovery won't succeed if the server on which recovery is being performed doesn't have the same name as the lost server;
Join the server to the same domain as the lost server;
Install the necessary prerequisites and operating system components;
Log on to the server being recovered and open a command prompt;
Navigate to the Exchange 2013 installation files, and run the following command:
Setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms
7. After Setup has completed, but before the recovered server is put into production, reconfigure any custom settings that were previously present on the server, and then restart the server.
The following link is about Exchange 2013 prerequisites:
http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx
We could learn more about Exchange 2013 disaster recovery by the following link:
http://technet.microsoft.com/en-us/library/dd876880(v=exchg.150).aspx
Then, we could recovery database from a backup or copy of a database by the following steps:
Create the recovery database;
This example creates the recovery database RDB2 on the Mailbox server MBX1 using a custom path for the database file and log folder:
New-MailboxDatabase -Recovery -Name RDB2 -Server MBX1 -EdbFilePath "C:\Recovery\RDB2\RDB2.EDB" -LogFolderPath "C:\Recovery\RDB2"
   2. Copy a recovered database and its log files, or restore a database and it log files, to the location we will use for our recovery database.
   3. Use Eseutil to bring that database into a clean shutdown state.
In the following example, EXX is the log generation prefix for the database (for example, E00, E01, E02, and so on).
Eseutil /R E01 /l E:\Databases\RDB1 /d E:\Databases\RDB1
4. Create a recovery database. Give the recovery database a unique name, but use the name and path of the database file for the EdbFilePath parameter, and the location of the recovered log files for the LogFolderPath parameter.
The following example illustrates creating a recovery database that will be used to recover DB1.edb and its log files, which are located at E:\Databases\RDB1.
     New-MailboxDatabase -Recovery -Name <RDBName> -Server <ServerName> -EdbFilePath " E:\Databases\RDB1\DB1.EDB" -LogFolderPath "E:\Databases\RDB1"
5. Restart the Microsoft Exchange Information Store service:
Restart-Service MSExchangeIS
6. Mount the recovery database:
    Mount-database <RDBName>
We could refer to the following link:
http://technet.microsoft.com/en-us/library/dd876954(v=exchg.150).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

DR (Disaster Recovery) server installation.

Similar Messages

Maybe you are looking for