How To Move From a Primary Server To a Fallback Server
(Doc ID 1907467.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Communications ASAP - Version 7.0.1 and later
Information in this document applies to any platform.
We Need to identify the steps to move from primary server to fallback server.
We have a primary server and fallback server architecture. Databases are connected via Oracle Dataguard and files are copied using rsync.
We want to perform fallback activity, please clarify below queries:
Q1. Due to Dataguard, all the data from primary would be copied on to fallback. Do we need to replace IP address / hostname of the primary server with the fallback server anywhere in ASAP schema?
Q2. If yes, can we make this entity configurable in some ASAP config, so that instead of using IP/ DNS name, we can use generic entity as ‘Hostname’ etc?
Q3. Due to rsync implementation, the sar files and the activation jar files would get copied on the fallback server. Is there any need to undeploy and redeploy the sar files again on the fallback server once it is online?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document