virtualwatts wrote:When your oracle db backup fails to come up who you gonna call?
Well, that's why you have RMAN in addition to Veeam. There are many reasons to run RMAN, for granular restores, log backups, easy cloning for DEV/TEST environments, the fact that RMAN backups check for silent block level corruption, etc. My point is simply that we've restored backups from Veeam probably 30 times, maybe more if you count all of our testing, and we've never had an Oracle instance fail to start.
virtualwatts wrote:I don't actually know that all I/O is stopped waiting for the snapshot to occur in VMware. There is as much mis-information as information in this space right now. Between me and the techs we have Ora & Windows covered, but the VMware is a recent addition for us and as we've learned over the past 7 months it introduces variables that even befuddle the vendors. If I had a dime for every time a tech support has said "well it shouldn't be doing that..." during our data center virtualization, well, I'd have more than a dollar.
Did I say all I/O is stopped? I don't think so. I said the system is "paused", just long enough for the snapshot to be created. If there are 100 outstanding writes, it's possible the snapshot is made directly in the middle of them, but there is no chance for a partial write of a block because it's not a crash, it's a snapshot. That means there's no chance for a "lost" write (in a physical server "crash" that's why caches have to have battery backup, so as not to loose writes).
virtualwatts wrote:Since we have multiple data stores housing our Oracle files and since we have seen the snapshot creation/merge take several minutes and since Veeam doesn't snapshot memory - I'm just feeling my way through this. Think about it - some unlucky DBA somewhere had to be the first to find out the VMware sync driver corrupts your db. Well, we're at a new ESXi, new bare metal platform and new backup tool release.
I understand your questions. Heck, we've been a virtual shop long before virtualization was "cool" (ESX 2.x days, I even did some early stuff with ESX 1.x). If you think you see strange answers from vendors today, you should have mentioned it to them back in the first part of the decade, most of them didn't even know what virtualization was.