Hi all. I’ve read the Best Practices for Oracle whitepaper by Zerto. It seems there are 2 means by which to ensure a consistent database is available on the recovery side: 1) Use Powershell scripting to place the Oracle database into Hot Backup Mode and run such a script as often as possible and 2) Use the Zerto VSSAgent and schedule checkpoints that way.
I’m wondering if anyone has worked with either approach and if so would you share your experience and own real world ‘best practices’.
James, Thanks for the question and the time on the phone earlier. We discussed that it is possible when using Zerto to use a Zerto created checkpoint, VSS, or user defined checkpoint from the journal when failing over. However, more applicable to you was the “move VPG” function in which Zerto shuts-down the source VMs for the VPG and then fails over to a final checkpoint at the target site. This is ideal for migrations or preemptive failovers where you prefer to have full control over the process. We also discussed the commit-policy feature and the ability to failover and select a different checkpoint or cancel the failover process which can be very handy to ensuring the checkpoint you selected was correct based on your reason for failover occurring. Thanks for your question and for being a Zerto customer.