Disaster Recovery on XI server

Hi experts,
Sorry this question might be a bit like BASIS question. But i just try my luck here to see hv anyone of you have the experience on Disaster Recover (DR) on XI server?
We know there is lot of product on ECC server DR, but I never heard of anything abt DR for PI/XI server. Normally in business, do they DR the XI? or they just backup it. Any build in tool by SAP can enable us to backup the XI object?
As we know, rebuilding up the SLD, IR, ID can be 1-2 years job. So, any alternative for us to make sure the XI/PI will be operational if the existing hardware failure?
Thanks.
Cheers,
Isaac.

Yeah I know the Import/Export strategy. However, what I am actually looking at is any disaster recovery or some other approach we can use which is close to the DR concept.
For example, if our XI server having serious hardware failure or damaged due to natural disaster. We need to re-install and set all the SLD, RFC, and proxy all over again, right? That's y I m thinking of any Backup tool or DR tool we can use within SAP/ or maybe third party software which is compliance with SAP.. just name some example will do...
It will be good if any of you can share your experience on how your company / client handle this....
Thanks.

Similar Messages

Seeking best practice for disaster recovery for osx server

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

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

"Disaster Recovery with Messaging server"

Suggest a better solution for load balancing on Netscape Messaging Server. Also for disaster recovery - in case one server goes down.

Better solution than what? Nothing? Use a cluster for the mail store. Use more than a single server for the other components and use a load balancer as the front end for those services.

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

How to install and configure Exchange Server 2010 DR (disaster recovery) on Windows server 2012.

We need to install and configure Exchange Server 2010 with DR(disaster recovery on Server 2012.
Pls suggest step by step.
Pankaj Kumar

Hi,
Here is an article which may help you for your reference.
Deploying High Availability and Site Resilience
https://technet.microsoft.com/en-us/library/dd638129(v=exchg.141).aspx
Besides, there is a related thread here.
https://social.technet.microsoft.com/Forums/exchange/en-US/577c9433-a20b-442e-8ce7-be59aea35855/preparation-for-deploying-exchange-2010-servers-at-remote-site-dr-site?forum=exchangesvrdeploylegacy
Hope this is helpful to you.
Best regards,
Belinda Ma
TechNet Community Support

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

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

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.

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 on another Sun Server

I have a question in regards to disaster recovery of Sun servers. We have a client that hosting applications within Sun T platform which utilizes LDOM configuration. These boxes host around five guests.
Currently we use a software called EMC HomeBase(http://www.emc.com/backup-and-recovery/homebase/homebase.htm) to enhance our DR recovery by profiling the Sun box and transmitting that profile to our DR vendor. DR vendor in turn with help from EMC will install the OS, patch level and apply that profile to setup the system with NIC information, file systems and other components so we would only
need to restore our data from NETBACKUP and don't do any system recovery.
Unfortunately, EMC does not support LDOMs nor containers. Now my question is if Sun has a way around this? Please note that the servers will be different models at DR. for example T5220 to a T5440 or V890 to V490.

It'd be rather easy to manually install same LDOM configuration on DR site... all EMC seems to be doing is getting the profile & then someone is creating setup manually...
Anyways... here you go:
Backup & Recovery of guest domain
Archive and backup the guest domain configuration:
ldm list-constraints -x <ldom> > <ldom>.xml
Backup the guest domains over the network with backup software as regular server
Restore the guest domain configuration, assuming that your VSW and VDS resources are available:
ldm add-domain -i <ldom>.xml
Make sure that you have enough VCPU, MAU, and Memory to boot your guest domain.
Jumpstart guest domain and install backup client. Restore data from backup.
Backup LDOM configuration
You can take the backup of the configuration using "ldm add-spconfig saveconfigurtion" command which will store in SP of the server.
For taking the backup of the individual domain use "ldm ls-constrants >> filename.xml" it will give the xml output just redirect it to a file.
While creating the domain again use "ldm create ldomname -f filename.xml"
You can not create control domain by the above procedure we hve to configure manualy or even if your control domain crashed install new OS and install LDOM Manager in the Base OS create /etc/hostname.vsw0 & vsw1 files poweroff the server from SP. set bootmode config=saveconfiguration
How to backup the primary domain
Backup the LDM db files in: /var/opt/SUNWldm
Archive and backup the primary domain configuration:
ldm list-constraints -x primary > primary.xml
Backup the primary domains over the network with backup software as regular server.
How to recover primary domain
Update firmware
Install backup client & LDM software
Restore /var/opt/SUNWldm
Start up LDM services
If all goes well, the LDM config will be read and you will be in initial configuration mode. Save the config to the hypervisor and
reboot. If not, parse the primary.xml file to recreate the primary domain configuration, save config, and reboot.
Restore guest domain configs and data. Then bring up guest domains.

[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 of remaining OVM server

Hi,
I hope some of you can help me with some disaster recovery tests I have to do shortly.
The environment has 2 OVM servers: servre1 and server2 in a server pool.
Server1 has the cluster filesystem shared to it via multiipathing, and in turn, server1 shares the repository and cluster fs with server2 via NFS.
In the meantime, there are other LUNS shared with just server2, which are being replicated with the repository and cluster fs that is currently being used.
If server1 "dies" and this is easy to simulate as just shutting it down, it will stop sharing the repository and fs with server2, the server pool will have errors, and so will server 1 (it cannot be contacted), and so will server2 (it has lost access to repository and cluster fs).
Oracle documentation explains very clearly how to add and remove server pools and servers neatly, but it makes no mention of how to clean up a server in order to reuse in on a new server pool, with a new repository, in this case, the replicated LUNs that were only in server2.
Has any of you done something similar to this? Do I have to go into the OVM Manager database at row level to delete every mention of the old repository? Is there a way of cleaning up the server2 for reuse (other than reinstalling)? In OVM 2.2 there was a cleanup.py script, but I didn´t find such script in 3.0.3...
Any suggestions on how to test this will be welcome. If I have overlooked some useful documentation on this, please point me to it...
Regards,
T.

Dan,
do you mean
sh ./ovm_upgrade.sh dbuser=ovs dbpass=<password> --fixup
Regards,
T.

Disaster Recovery - Managed Server Startup

We are testing some disaster recovery and want to be able to start our managed servers on our B node in MSI mode while the A node with admin server is down. It tests fine and works with nodemanager running. However, we want to assume that there has been a jvm problem on one or more managed servers and they have ceased to run on the B node. When I run the startManagedWebLogic.cmd and plug in my managed server name and admin link (which is obviously unreachable), I get the message below. I copied down the managed servers info (there is no 'config' folder as mentioned in the Oracle instructions so I copied down the 6 server folder into \common\bin\config\acr2 folder). Any tips on getting this to work?
<Apr 9, 2010 11:11:09 AM CDT> <Info> <Management> <BEA-141107> <Version: WebLogi
c Server Temporary Patch for 9216172 Tue Jan 12 02:07:27 PST 2010
WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 >
<Apr 9, 2010 11:11:09 AM CDT> <Critical> <WebLogicServer> <BEA-000362> <Server f
ailed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141247]The configuration di
rectory C:\Oracle\Middleware\wlserver_10.3\common\bin\config does not exist and
the admin server is not available.
at weblogic.management.provider.internal.RuntimeAccessImpl.parseNewStyle
Config(RuntimeAccessImpl.java:200)
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(Runtim
eAccessImpl.java:115)
at weblogic.management.provider.internal.RuntimeAccessService.start(Runt
imeAccessService.java:41)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesMan
ager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServ
icesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:749)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:488)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
at weblogic.Server.main(Server.java:67)
>
<Apr 9, 2010 11:11:09 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to FAILED>
<Apr 9, 2010 11:11:09 AM CDT> <Error> <WebLogicServer> <BEA-000383> <A critical
service failed. The server will shut itself down>
<Apr 9, 2010 11:11:09 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to FORCE_SHUTTING_DOWN>

So no one has ever had to restart a managed server on a clustered environment when the admin was down? Seems like this would be a common disaster recovery item that would be needed. If anyone has this working please provide details. These details found in Oracle documentation are a bit incomplete...
Starting a Managed Server in MSI Mode
To start up a Managed Server in MSI mode:
1.Ensure that the Managed Server’s root directory contains the config subdirectory.
If the config directory does not exist, copy it from the Administration Server’s root directory or from a backup to the Managed Server’s root directory.
Note: Alternatively, you can use the -Dweblogic.RootDirectory=path startup option to specify a root directory that already contains these files.
2.Start the Managed Server at the command line or using a script.
The Managed Server will run in MSI mode until it is contacted by its Administration Server. For information about restarting the Administration Server in this scenario, see Restarting a Failed Administration Server.
I have used the root.directory switch to point to these locations as well but still get message.....<Apr 13, 2010 11:28:05 AM CDT> <Critical> <WebLogicServer> <BEA-000386> <Server
subsystem failed. Reason: weblogic.descriptor.ResourceUnavailableException: Miss
ing SerializedSystemIni.dat
weblogic.descriptor.ResourceUnavailableException: Missing SerializedSystemIni.da
t
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityPro
xy.<init>(DescriptorManager.java:153)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityPro
xy.instance(DescriptorManager.java:137)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(Des
criptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(Abstract
DescriptorBean.java:991)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getC
redential(SecurityConfigurationMBeanImpl.java:709)
Truncated. see log file for complete stacktrace
>
<Apr 13, 2010 11:28:05 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server st
ate changed to FAILED>

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 on XI server

Similar Messages

Maybe you are looking for