Not if you do this way:
1) you go restore
2) you add the vm to inventory
3) you DO NOT power on
4) you do a "revert to snapshot"
5) VOILA' , you get a powered on machine which never crashed, it will
simply have to sync its time and nothing other, just as if it had been
"hibernated" or "suspended".
Database integrity will be ok since it *didn't* crash.
Of course if you try to power on and don't do a "revert to snapshot"
you'll get a VM which *has* crashed.
Or, to better put it, a VM which had its "plug pulled".
But I never take this route since I know I don't want to restore such
a machine; in fact its own O.S. would probably need to perform a
checkdisk and its databases would need an integrity check; and this is
avoidable, just by doing a "revert to snapshot".
Just my 2 cents! :-)
On 12 Ago, 20:27, farewelldave <farewelld...@gmail.com
> The main disadvantage is that Hot backups will get you a crash-
> consistent backup. (At least, in other methods where you're backing up
> the VM while it's in a snapshot.) The main advantage is that the VM is
> not offline for the duration of the backup.
> What do I mean by 'crash-consistent'? Let's say you go to restore a
> Windows 2003 VM and you go restore, add into inventory, and power on.
> Windows will ask you why there was an unexpected shutdown. Database
> servers(i.e., SQL, Exchange, Active Directory) are recommended for
> Cold backup in my book if this is your only backup method. Just
> because the issue with potential data corruption.
> I've got some hosts that really need to be available all the time, and
> so here's what I'm doing to allow for Hot backups, and yet still be
> protected. I am doing weekly backups to an external drive, and then
> swapping out the external drive every week with another drive. This
> way I have two weeks/copies and one being stored off-site all the
> time. Then, I'm doing nightly off-site backups (just Active Directory,
> Exchange, SQL, file-level, etc.) with a backup service and in the
> event that I lose the VM, I can restore the most recent from the drive
> (multi GB but back pretty quickly over eSATA) and then restore the
> most recent data from the offsite backup which is much more reliable
> and still save money in not having to use many more GBs on the backup
> I know my examples are of a Windows VM, so any linux guys may have
> some more detailed info for that OS.
> > James- Nascondi testo citato
> - Mostra testo citato -