Cutover disaster recovery

Hi all,
This question is specific to the scenario of a cutover in a IS-utility (fall back strategy). The scenario is: consider a utility compnay going live on ISU. The SAP ERP was already running in the company. The thing is when the company starts to bring ISU to go live they want to run ERP integrated with ISU in the same server machine.Thus they have to close ERP system for the period when ISU is going live. The time when they go live after migration some un-forseen circumstances make the ISU cutover go bad. Thus they have to close ISU for now and rewoke ERP again until they figure out a way out of the problem.
My question is when we are migarting using emigall/ISMW we are running the objects in create mode. If the cutover went bad and the only change to the ERP is the migrated objects of ISU, in order to reverse the migrated data can we run the objects of the same migration file under delete mode. Will this make the ERP go back to what it was before migration?
waiting for your answers

Hello Hashmi,
Srini said: I suggest you create a parallel production environment as a copy of the current ECC at a certain point in time. After you do all your migration, apply the deltas to the new production box and then switch the production environment to the new box, if everything goes well. The advantage will be that you don't have to bring down your production server for a long time except for the copying and switchover. Another advantage will be that if your migration doesn't go well, you can trash the new environment and start all over depending on how bad your migration went.
In brief, I tend to disagree to having the production system in production with write/change access while doing data migration into a shadow (migration) system since (allmost) all changes done in production must be applied manually in the migration system. The question is if this is possible at all. In contrary, it won't be possible to apply changes of the shadow system (as a result of data migration) to the production system. In addition, don't forget, that copying in Srini's sense is not exactly copying data.
One last point: many basis teams are afraid of restoring the production system hence trying to defeat such an idea. Why? Well, because the have never tried this before. But wouldn't a restore a good fallback strategy?
Cheers,
Fritz

Similar Messages

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.

SharePoint 2013 Search - Disaster Recovery Restore

Hello,
We are setting up a new SharePoint 2013 with a separate Disaster Recovery farm as a hot-standby. In a DR scenario, we want to restore all content and service app databases to the new farm, then fix any configuration issues that might arise due to changes
in server names, etc...
The issue we're running into is the search service components are still pointing to the production servers even though they're in the new farm with completely different server names. This is expected, so we're preparing a PowerShell script to remove
then re-create the search components as needed. The problem is that all the commands used to apply the new search topology won't function because they can't access the administration component (very frustrating). It appears we're in a chicken &
egg scenario - we can't change the search topology because we don't have a working admin component, but we can't fix the admin component because we can't change the search topology.
The scripts below are just some of the things we've tried to fix the issue:
$sa = Get-SPEnterpriseSearchServiceApplication "Search Service Application";
$local = Get-SPEnterpriseSearchServiceInstance -Local;
$topology = New-SPEnterpriseSearchTopology -SearchApplication $sa;
New-SPEnterpriseSearchAdminComponent -SearchTopology $topology -SearchServiceInstance $local;
New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $topology -SearchServiceInstance $local;
New-SPEnterpriseSearchCrawlComponent -SearchTopology $topology -SearchServiceInstance $local;
New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $topology -SearchServiceInstance $local;
New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $topology -SearchServiceInstance $local;
New-SPEnterpriseSearchIndexComponent -SearchTopology $topology -SearchServiceInstance $local -IndexPartition 0 -RootDirectory "D:\SP_Index\Index";
$topology.Activate();
We get this message:
Exception calling "Activate" with "0" argument(s): "The search service is not able to connect to the machine that
hosts the administration component. Verify that the administration component '764c17a1-4c29-4393-aacc-de01119aba0a'
in search application 'Search Service Application' is in a good state and try again."
At line:11 char:1
+ $topology.Activate();
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : InvalidOperationException
Also, same as above with
$topology.BeginActivate()
We get no errors but the new topology is never activated. Attempting to call $topology.Activate() within the next few minutes will result in an error saying that "No modifications to the search topology can be made because previous changes are
being rolled back due to an error during a previous activation".
Next I found a few methods in the object model that looked like they might do some good:
$sa = Get-SPEnterpriseSearchServiceApplication "Search Service Application";
$topology = Get-SPEnterpriseSearchTopology -SearchApplication $sa -Active;
$admin = $topology.GetComponents() | ? { $_.Name -like "admin*" }
$topology.RecoverAdminComponent($admin,"server1");
This one really looked like it worked. It took a few seconds to run and came back with no errors. I can even get the active list of components and it shows that the Admin component is running on the right server:
Name ServerName
AdminComponent1 server1
ContentProcessingComponent1
QueryProcessingComponent1
IndexComponent1
QueryProcessingComponent3
CrawlComponent0
QueryProcessingComponent2
IndexComponent2
AnalyticsProcessingComponent1
IndexComponent3
However, I'm still unable to make further changes to the topology (getting the same error as above when calling $topology.Activate()), and the service application in central administration shows an error saying it can't connect to the admin component:
The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '764c17a1-4c29-4393-aacc-de01119aba0a' in search application 'Search Service Application' is in a good state and try again.
Lastly, I tried to move the admin component directly:
$sa.AdminComponent.Move($instance, "d:\sp_index")
But again I get an error:
Exception calling "Move" with "2" argument(s): "Admin component was moved to another server."
At line:1 char:1
+ $sa.AdminComponent.Move($instance, "d:\sp_index")
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : OperationCanceledException
I've checked all the most common issues - the service instance is online, the search host controller service is running on the machine, etc... but I can't seem to get this database restored to a different farm.
Any help would be appreciated!

Thanks for the response Bhavik,
I did ensure the instance was started:
Get-SPEnterpriseSearchServiceInstance -Local
TypeName : SharePoint Server Search
Description : Index content and serve search queries
Id : e9fd15e5-839a-40bf-9607-6e1779e4d22c
Server : SPServer Name=ROYALS
Service : SearchService Name=OSearch15
Role : None
Status : Online
But after attempting to set the admin component I got the results below.
Before setting the admin component:
Get-SPEnterpriseSearchAdministrationComponent -SearchApplication $sa
IndexLocation : E:\sp_index\Office Server\Applications
Initialized : True
ServerName : prodServer1
Standalone :
After setting the admin component:
Get-SPEnterpriseSearchAdministrationComponent -SearchApplication $sa
IndexLocation :
Initialized : False
ServerName :
Standalone :
It's shown this status for a few hours now so I don't believe it's still provisioning. Also, the search service administration is still showing the same error:
The search service is not able to connect to the machine that hosts the administration component. Verify that the administration
component '764c17a1-4c29-4393-aacc-de01119aba0a' in search application 'Search Service Application' is in a good state and try again.

Disaster Recovery set-up for SharePoint 2013

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

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

Recovering lost data from a very old backup (disaster recovery)

Hi all,
I am trying to restore and recover data from an old DAT-72 cassette. All I know is the date when the backup was taken, that is back in November 2006. I do not know the DBID or anything else except for the date.
To recover this, I bought an internal SCSI HP c7438a DAT-72 tape drive on eBay and installed it on a machine running Windows 2003 Server SP2. I made a fresh Oracle 11g Enterprise Edition installation. HP tape drivers have been installed and Windows sees the tape drive without problem. To act as a Media Manager, I have installed Oracle Secure Backup. Oracle Secure Backup sees the HP tape drive without problems as well.
I have to admit my information about Oracle is not very in-depth. I read quite a lot of documents, but the more I read the more confused I become. The closest thing I can find to my situation is the following guide about disaster recovery:
http://download.oracle.com/docs/cd/B10500_01/server.920/a96566/rcmrecov.htm#1007948
I tried the suggestions in this document without success (details below).
My questions are:
1. Is it possible to retrieve data without knowing the DBID?
2. If not, is it possible to figure out the DBID from the tape? I tried to use dd in cygwin, also booted with Knoppix/Debian and Ubuntu CDs to dump the contents of the tape with dd but all of them failed to see the tape device. If there is any way to dump the raw contents of the tape on Windows, I would also welcome input.
3. Is there any way at all to recover this data from the tape given all the unknowns?
Thanks very much in advance,
C:\Program Files>rman target orcl
Recovery Manager: Release 11.2.0.1.0 - Production on Sat Mar 19 15:01:28 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
target database Password:
connected to target database: ORCL (not mounted)
RMAN> SET DBID 676549873;
executing command: SET DBID
RMAN> STARTUP FORCE NOMOUNT; # rman starts instance with dummy parameter file
Oracle instance started
Total System Global Area 778387456 bytes
Fixed Size 1374808 bytes
Variable Size 268436904 bytes
Database Buffers 503316480 bytes
Redo Buffers 5259264 bytes
RMAN> RUN
2> {
3> ALLOCATE CHANNEL t1 DEVICE TYPE sbt;
4> RESTORE SPFILE TO 'C:\SPFILE.TMP' FROM AUTOBACKUP MAXDAYS 7 UNTIL TIME 'SYS
DATE-1575';
5> }
using target database control file instead of recovery catalog
allocated channel: t1
channel t1: SID=63 device type=SBT_TAPE
channel t1: Oracle Secure Backup
Starting restore at 19-MAR-11
channel t1: looking for AUTOBACKUP on day: 20061125
channel t1: looking for AUTOBACKUP on day: 20061124
channel t1: looking for AUTOBACKUP on day: 20061123
channel t1: looking for AUTOBACKUP on day: 20061122
channel t1: looking for AUTOBACKUP on day: 20061121
channel t1: looking for AUTOBACKUP on day: 20061120
channel t1: looking for AUTOBACKUP on day: 20061119
channel t1: no AUTOBACKUP in 7 days found
released channel: t1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 03/19/2011 15:03:26
RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece
RMAN>
RMAN> RUN
2> {
3> ALLOCATE CHANNEL t1 DEVICE TYPE sbt
4> PARMS 'SBT_LIBRARY=C:\WINDOWS\SYSTEM32\ORASBT.DLL';
5> RESTORE SPFILE TO 'C:\SPFILE.TMP' FROM AUTOBACKUP MAXDAYS 7 UNTIL TIME 'SYS
DATE-1575';
6> }
allocated channel: t1
channel t1: SID=63 device type=SBT_TAPE
channel t1: Oracle Secure Backup
Starting restore at 19-MAR-11
channel t1: looking for AUTOBACKUP on day: 20061125
channel t1: looking for AUTOBACKUP on day: 20061124
channel t1: looking for AUTOBACKUP on day: 20061123
channel t1: looking for AUTOBACKUP on day: 20061122
channel t1: looking for AUTOBACKUP on day: 20061121
channel t1: looking for AUTOBACKUP on day: 20061120
channel t1: looking for AUTOBACKUP on day: 20061119
channel t1: no AUTOBACKUP in 7 days found
released channel: t1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 03/19/2011 15:04:56
RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece
RMAN>
-----------------------------------

Hi 845725,
If the backups were created with OSB might be you can query the tape with obtool.
http://www.stanford.edu/dept/itss/docs/oracle/10gR2/backup.102/b14236/obref_oba.htmTo list pieces you could use <lspiece> within obtool.
http://www.stanford.edu/dept/itss/docs/oracle/10gR2/backup.102/b14236/obref_oba.htm#BHBBIFFEIf this works you should be able to identify the controlfile autobackup if it has the standard naming < c-dbid-date-xx > and you than know the DBID or you are able to restore a controlfile from a backup piece in the output list.
Might be you have to install 9i or 10g rdbms software as 11g was released a year later in 2007.
Anyway goodluck.
Regards,
Tycho

Welcome to the SQL Server Disaster Recovery and Availability Forum

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

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

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

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

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

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/

Disk Utility in Lion 10.7.4 for Bare Metal Disaster Recovery??

We just got our 15" Macbook Pro back from repair of a catastrophic hard disc failure. Wow. An older Seagate Momentus XT 500 toasted its little self. It seems most of our data are intact. If any software on the *new* hard disc get corrupted, we need a fairly straightforward disaster recovery process.
I need to ask if anyone has successfully used Disk Utility to create a (bare metal) disaster recovery image of everything on their hard drive, including all their software *and* the perfectly functioning OS. We'd like to be able to restore a complete disc image of the new Seagate Momentus 750 XT - taken from a 1 TB Seagate FreeAgent GoFlex USB drive - to the Macbook.
Has anyone done this successfully? Thanks very much for your help!

Time Machine, SuperDuper and Carbon Copy Cloner are some of the utilities that will allow you to backup your disk and do a complete restore.

Planning Disaster Recovery Site for SAP ERP ECC 6.0

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

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

Disaster Recovery For SAP ECC 6.0 On Oracle

Hi All,
This is our infrastructure
Windows 2003 Server
SAP ECC 6.0
Oracle 10
Legato Networker Client / Library
Actually our Backup Strategy is to do an Online Backup Every Night from monday to saturday. We want to test our backup by doing a Restore. We are assuming a complete loss of the system including hardware.
What we do:
1. Install the SAP System on a new host with the same hardware characteristic of the source system.
2. Install & Configure the legato utility.
3. Copy the E:\oracle\MIS\sapbackup\ directory from the source system to the test system.
4. Them we put the database in mount mode.
5. Execute the command: brrestore -b bdyxwoqv.fnf -m full (bdyxwoqv.fnf-> Full Online Backup that was executed without problems).
It gives the following errors:
BR0386E File 'F:\ORACLE\MIS\SAPDATA2\SR3_10\SR3.DATA10' reported as not found by
backup utility
BR0386E File 'F:\ORACLE\MIS\SAPDATA3\SR3700_9\SR3700.DATA9' reported as not foun
d by backup utility
BR0280I BRRESTORE time stamp: 2008-10-01 17.45.19
BR0279E Return code from 'backint -u MIS -f restore -i E:\oracle\MIS\sapbackup\.
rdyybrzp.lst -t file -p E:\oracle\MIS\102\database\initMIS.utl': 2
BR0374E 0 of 63 files restored by backup utility
BR0280I BRRESTORE time stamp: 2008-10-01 17.45.19
BR0231E Backup utility call failed
BR0406I End of file restore: rdyybrzp.rsb 2008-10-01 17.45.19
BR0280I BRRESTORE time stamp: 2008-10-01 17.45.19
BR0404I BRRESTORE terminated with errors
Since this is a new SAP system it never will find the SAPDATA files because they where on the source system and this is a new test system.
We found the following note:
96848 Disaster recovery for SAP R/3 on Oracle
But this note is for SAP R/3 no for SAP ECC!
It explain that you have to install your SAP system with the System Copy Method (is this the only way??).
2.) Installation of the R/3 System
The installation of SAP software contains the software installation of the database. The initial SAP database should be created again but the SAP data should not be loaded.
Install the SAP system with the Oracle-specific system copy method, which is based on backup/restore. This method is described in the system copy guide for your Product/Release. Refer to Note 659509 for products that are based on Web AS.
3.) Modification of the installation
Above all, you must take into account the mounted file systems at the time of the loss. If necessary create new SAPDATA directories (mount points). These generally identify a disk or a logical storage area (logical volume).
Are we working in the right way? maybe there is a formal procedure to do a Restore from an Online backup when you complete loss your system.
Please some tips.
Best Regards,
Erick Ilarraza

Hi Eric,
Thanks a lot for your reply, I will follow the Note 96848 Disaster recovery for SAP R/3 on ORACLE point 5.
5.) Restore profile and log files, as you sayed in case of disaster we will lost our "source" system.
On the other hand to configure the legato client we take care of the name of the server, we configured the .sap, .cfg and .utl files so in theory the restore will be done on the new test system since we run the brrestore command from that system.
Officially there is not a documentation from SAP to do a Restore from a Online Backup with SAP ECC, SAP Netweaver (ABAP / ABAP + Java). You only have the 96848 note??? I found the following information:
http://help.sap.com/saphelp_nw70/helpdata/en/65/cade3bd0c8545ee10000000a114084/frameset.htm
But there is not a official procedure like a System Copy Guide or Installation Guide.
Best Regards,
Erick Ilarraza

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

RMAN backup and restore for Disaster Recovery

Hi Guys,
I am very new to Oracle and have a question about RMAN backup and restore feature. I am simulating a disaster recovery scenario by having two VMs running oracle 11g, say hosta and hostb, hosta is sort of production db and the other a disaster recovery db (one that will be made primary when disaster occurs). My goal is to backup production db using RMAN and restore it on the other machine. For some reason when I restore the db on hostb, the command restores the previous backup but not the most recent one e.g. I took a backup yesterday (09/20) and applied it to the hostb that worked fine, but when I try to apply a fresh backup from today (09/21) it always picks up the old backup. Here's a dump of the screen:
Starting restore at 21-SEP-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /oracle/app/dev/oradata/forums/s
ystem01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /oracle/app/dev/oradata/forums/s
ysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /oracle/app/dev/oradata/forums/u
ndotbs01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /oracle/app/dev/oradata/forums/u
sers01.dbf
channel ORA_DISK_1: reading from backup piece /oracle/app/dev/flash_recovery_are
a/FORUMS/backupset/o1_mf_nnnd0_TAG20110920T040950_77jx3zk7_.bkp
channel ORA_DISK_1: piece handle=/oracle/app/dev/flash_recovery_area/FORUMS/back
upset/o1_mf_nnnd0_TAG20110920T040950_77jx3zk7_.bkp tag=TAG20110920T040950
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:05
Finished restore at 21-SEP-11
Notice that it reads the backup piece from this location /oracle/app/dev/flash_recovery_are
a/FORUMS/backupset/
whereas my latest backups are stored at a different location.
I am executing following steps at the RMAN prompt on hosta and hostb:
hosta (production site)
backup as compressed backupset database plus archivelog
backup current controlfile format'/oracle/oracle_bkup/ctl_%U'
backup spfile
hostb (Disaster site)
set dbid=13732232063
startup force nomount
restore spfile to '/oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora' from '/export/home/dev/restore_db/backupset/2011_09_21/o1_mf_nnsnf_TAG20110921T114945_77ndg9ys_.bkp'
shutdown immediate
/* create a init<db_name>.ora file with SPFILE= /oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora */
startup force pfile='/export/home/dev/restore_db/initforums.ora' nomount
restore controlfile from '/export/home/dev/restore_db/backupset/2011_09_21/ctl_1hmn3mic_1_1'
/* restart rman here */
quit
alter database mount;
catalog start with '/export/home/dev/restore_db/backupset/2011_09_21' noprompt;
/* call the next two commands on run */
restore database;
recover database;
alter database open resetlogs
quit
Any help will be greatly appreciated.
Thanks,
Rajesh

Thanks guys, I really appreciate all your help here. I redid everything all over again to get all the information you guys wanted. Since I noticed that more eyes are looking into this I am going to reiterate my steps one more time followed by specific answers to questions. My first backup on Host B is located under ..../restore_db/backupset whereas the subsequent one is under .../restore_db/backupset/backupset2.
I take backup on Host A using:
rman target /
backup as compressed backupset database plus archivelog;
backup spfile;
quit;
I restore the backup on Host B using:
set dbid=13732232063;
startup force nomount;
restore spfile to '/oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora' from '/export/home/dev/restore_db/backupset/o1_mf_nnsnf_TAG20110928T171830_787gbpxh_.bkp'
shutdown immediate;
startup force nomount;
restore controlfile from '/export/home/dev/restore_db/backupset/o1_mf_ncsnf_TAG20110928T171638_787gbkxn_.bkp'
quit;
/* restart rman here */
alter database mount;
catalog start with '/export/home/dev/restore_db/backupset' noprompt;
restore database;
recover database;
alter database open resetlogs;
quit;
I take another backup on Host A using (notice no spfile backup this time):
backup as compressed backupset database plus archivelog;
quit;
I restore the database on Host B using:
alter database mount;
catalog start with '/export/home/dev/restore_db/backupset/backupset2' noprompt;
recover database;
alter database open;
quit;
Output of List Backup of database (I have done this after I recovered the second time, also note that it is referring to backupset2 which is were my second backup is stored)
RMAN> list backup of database;
using target database control file instead of recovery catalog
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
89 Full 261.87M DISK 00:01:37 28-SEP-11
BP Key: 91 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171638
Piece Name: /export/home/dev/restore_db/backupset/o1_mf_nnndf_TAG2011092
8T171638_787g77rx_.bkp
List of Datafiles in backup set 89
File LV Type Ckp SCN Ckp Time Name
1 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
2 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
3 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
4 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
97 Full 259.16M DISK 00:00:00 28-SEP-11
BP Key: 100 Status: AVAILABLE Compressed: YES Tag: TAG20110928T18352
7
Piece Name: /export/home/dev/restore_db/backupset/backupset2/o1_mf_nnndf
TAG20110928T183527787lv0nb_.bkp
List of Datafiles in backup set 97
File LV Type Ckp SCN Ckp Time Name
1 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
2 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
3 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
4 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf
Output of list backup (done after restoring the control file)
RMAN> list backup;
BS Key Size Device Type Elapsed Time Completion Time
87 89.20M DISK 00:00:26 28-SEP-11
BP Key: 87 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171526
Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
_28/o1_mf_annnn_TAG20110928T171526_787g50bm_.bkp
List of Archived Logs in backup set 87
Thrd Seq Low SCN Low Time Next SCN Next Time
1 34 1302253 20-SEP-11 1306439 20-SEP-11
1 35 1306439 20-SEP-11 1307647 20-SEP-11
1 36 1307647 20-SEP-11 1307701 20-SEP-11
1 37 1307701 20-SEP-11 1311393 20-SEP-11
1 38 1311393 20-SEP-11 1311511 20-SEP-11
1 39 1311511 20-SEP-11 1332479 20-SEP-11
1 40 1332479 20-SEP-11 1344418 20-SEP-11
1 41 1344418 20-SEP-11 1350409 20-SEP-11
1 42 1350409 20-SEP-11 1350449 20-SEP-11
1 43 1350449 20-SEP-11 1350854 21-SEP-11
1 44 1350854 21-SEP-11 1350895 21-SEP-11
1 45 1350895 21-SEP-11 1353114 21-SEP-11
1 46 1353114 21-SEP-11 1353254 21-SEP-11
1 47 1353254 21-SEP-11 1353865 21-SEP-11
1 48 1353865 21-SEP-11 1353988 21-SEP-11
1 49 1353988 21-SEP-11 1375403 21-SEP-11
1 50 1375403 21-SEP-11 1376149 21-SEP-11
1 51 1376149 21-SEP-11 1376206 21-SEP-11
1 52 1376206 21-SEP-11 1376246 21-SEP-11
1 53 1376246 21-SEP-11 1379990 21-SEP-11
1 54 1379990 21-SEP-11 1380229 21-SEP-11
1 55 1380229 21-SEP-11 1380266 21-SEP-11
1 56 1380266 21-SEP-11 1380528 21-SEP-11
1 57 1380528 21-SEP-11 1380724 21-SEP-11
1 58 1380724 21-SEP-11 1380861 21-SEP-11
1 59 1380861 21-SEP-11 1381033 21-SEP-11
1 60 1381033 21-SEP-11 1381077 21-SEP-11
1 61 1381077 21-SEP-11 1402243 22-SEP-11
1 62 1402243 22-SEP-11 1423341 22-SEP-11
1 63 1423341 22-SEP-11 1435456 22-SEP-11
1 64 1435456 22-SEP-11 1454415 23-SEP-11
1 65 1454415 23-SEP-11 1490903 23-SEP-11
1 66 1490903 23-SEP-11 1491266 23-SEP-11
1 67 1491266 23-SEP-11 1491347 23-SEP-11
1 68 1491347 23-SEP-11 1492761 23-SEP-11
1 69 1492761 23-SEP-11 1492891 23-SEP-11
1 70 1492891 23-SEP-11 1493678 23-SEP-11
1 71 1493678 23-SEP-11 1493704 23-SEP-11
1 72 1493704 23-SEP-11 1494741 23-SEP-11
1 73 1494741 23-SEP-11 1494790 23-SEP-11
1 74 1494790 23-SEP-11 1510154 23-SEP-11
1 75 1510154 23-SEP-11 1514286 23-SEP-11
1 76 1514286 23-SEP-11 1531967 24-SEP-11
1 77 1531967 24-SEP-11 1543266 24-SEP-11
1 78 1543266 24-SEP-11 1558427 24-SEP-11
1 79 1558427 24-SEP-11 1566924 24-SEP-11
1 80 1566924 24-SEP-11 1578292 24-SEP-11
1 81 1578292 24-SEP-11 1596894 25-SEP-11
BS Key Size Device Type Elapsed Time Completion Time
88 84.03M DISK 00:00:30 28-SEP-11
BP Key: 88 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171526
Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
_28/o1_mf_annnn_TAG20110928T171526_787g63s9_.bkp
List of Archived Logs in backup set 88
Thrd Seq Low SCN Low Time Next SCN Next Time
1 82 1596894 25-SEP-11 1609028 25-SEP-11
1 83 1609028 25-SEP-11 1622303 25-SEP-11
1 84 1622303 25-SEP-11 1626430 25-SEP-11
1 85 1626430 25-SEP-11 1634486 25-SEP-11
1 86 1634486 25-SEP-11 1648398 25-SEP-11
1 87 1648398 25-SEP-11 1669259 26-SEP-11
1 88 1669259 26-SEP-11 1686820 26-SEP-11
1 89 1686820 26-SEP-11 1686959 26-SEP-11
1 90 1686959 26-SEP-11 1689168 26-SEP-11
1 91 1689168 26-SEP-11 1704759 26-SEP-11
1 92 1704759 26-SEP-11 1719597 27-SEP-11
1 93 1719597 27-SEP-11 1740407 27-SEP-11
1 94 1740407 27-SEP-11 1750125 27-SEP-11
1 95 1750125 27-SEP-11 1765592 27-SEP-11
1 96 1765592 27-SEP-11 1781498 28-SEP-11
1 97 1781498 28-SEP-11 1802311 28-SEP-11
1 98 1802311 28-SEP-11 1811009 28-SEP-11
1 99 1811009 28-SEP-11 1813811 28-SEP-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
89 Full 261.87M DISK 00:01:37 28-SEP-11
BP Key: 89 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171638
Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
_28/o1_mf_nnndf_TAG20110928T171638_787g77rx_.bkp
List of Datafiles in backup set 89
File LV Type Ckp SCN Ckp Time Name
1 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
2 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
3 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
4 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf

Oracle Application Server 10g Disaster Recovery

Hi all,
This is regarding Disaster Recovery approach for Oracle Application Server 10g. There are two environments Active (DC-PROD) and Stand-By (DR-PROD). Each environment have 2 nodes where OAS Instances are installed in both nodes and each environment has a Virtual Hostname (Virtual IP) used. The 2 nodes hostnames of DC-PROD environment differs from 2 nodes of the other environment DR-PROD.
However the Virtual Hostname is same between two environments.
The env DC-PROD is setup already and is working fine. Now we have to setup DR-PROD env for disaster Recovery purpose. DR-PROD is also setup independently from DC-PROD. Each env has seperate DB servers in RAC mode. We are using EMC SRDF replication technology to do DB replication between DC-PROD and DR-PROD environments.
There is no disk replication between Oracle Application Servers of two environments DC-PROD and DR-PROD. DC-PROD is NOT setup using Oracle AS Guard for some reasons and we are in a situation that DC-PROD should not be touched at all.
So if the Database is replicated from DC-PROD to DR-PROD servers using EMC SRDF replication technology, while bring up OAS Infra services in DR-PROD node, OC4J is failing to come up. After some workarounds, OC4J cameup but we are unable to login to OIDDAS console.
ssoServer.log shows the following: -
Mon May 30 11:01:23 IST 2011 [DEBUG] AJPRequestHandler-ApplicationServerThread-8 DatabaseConfigReadergetting partner apps configs: select site_id, site_token, site_name, home_url, success_url, logout_url, encryption_key, encryption_mask_pre, encryption_mask_post, start_date, end_date, administrator_id, administrator_info from wwsso_papp_configuration_inf_t where site_id = '06B9F06C'
Mon May 30 11:01:23 IST 2011 [DEBUG] AJPRequestHandler-ApplicationServerThread-8 Partner Site ID: 06B9F06C
Mon May 30 11:01:23 IST 2011 [DEBUG] AJPRequestHandler-ApplicationServerThread-8 exception before getAuthLevel
oracle.security.sso.server.conf.ConfigurationException: Partner application configuration not found:06B9F06C
at oracle.security.sso.server.conf.DatabaseConfigReader.getPartnerConfiguration(DatabaseConfigReader.java:143)
Please provide us the inputs to achieve Disaster Recovery for OAS 10g without using Oracle AS Guard.
This is very urgent and your inputs are greatly appreciated.
Regards,
Mahendra.

Another point to add for the environment details. Both DC-PROD and DR-PROD environments does not have connectivity at all. Only the DB connectivity is there for doing DB replication.
EMC SRDF replication technology is a block by block replication i.e., a disk replication. Hope these details are sufficient for environment specifications.

Cutover disaster recovery

Similar Messages

Maybe you are looking for