Originally posted by: jtswoody
I agree the customer is looking for something which is mutually exclusive - PowerHA is meant to automatically failover to a secondary system in the event of the loss of a primary system's ability to run an application. However, the customer does not want to let PowerHA determine when a disaster has occurred, and they don't want software such as PowerHA to automatically handle failover.
Considering our customer's concern, I believe they only want to replicate their data to a secondary storage system. When they eventually have a DR site, they can make it a warm site, with a secondary server running, connected to the secondary storage system, ready to access the replicated data in the event of a disaster as determined by the customer.
The customer's RTO is 8-12 hours. This is plenty of time to declare a disaster, to switch over to using the server at the DR site, to start up their Oracle database and applications on this secondary server, and to switch their users over to access their data at the DR site. This allows the customer to manually failover to the server at the secondary site, without using any automatic failover, such as that provided by PowerHA.