Necessity of Backup DB (log replication) when running 11g under VMware?
Posted on 2011-09-29
Hello - i need to use Oracle standard 11g for a financial software suite. We are on a tight budget since we are starting up, and I was told we need a backup (standby) database to compliment our primary one. So I was quoted approx 30hrs of DBA time to install and build/configure the production database (which is fine), and then an additional 20hrs of DBA time to install 11g and establish standby database for the main production database.. by using log replication... including setting up all necessary scripts, etc. and on top of that I need another $6000 or so for the database log replication stool that provides redundancy in Oracle Std Edition.
Since I'm going to be running the Oracle VM on VMware, I was thinking I would be better off by getting VMware snapshots of the VM (and backup these snapshots using Veeam as well). Wouldnt this be better than going with the secondary (backup) server approach?
I assume restoring from a snapshot would be faster than running off the "standby" DB server - is this correct?
I realize I have to run a script before the snapshot to quiesce the DB prior to export, (pre-freeze/post-thaw script) after the snapshot, but if these are taken care of, would this approach be risky? and then I assume i have to put the control files in the same vmdk file so i can have everything in my snapshot in case something goes wrong.
Also just wanted to note that i am getting an ongoing monthly support package from the same firm that will be doing the initial oracle configuration, and they support vmware even though oracle officially doesn't.
Would 5 support hrs of DBA per month (proactive and reactive) be considered sufficient for a small database with 5 users?