Thursday, November 29, 2012 3:29 PM
Quick question regarding replication; when a VM is replicated, is it supposed to be off or in a saved state? In my POC it was always off, however I did read some documentation that said it was in a saved state (I of course cannot locate it now).
If it is indeed supposed to be off, is there any chance of being able to use saved states in the future?
Thursday, November 29, 2012 5:06 PM
The replica is off - you really don't want two of the exact machine running at the same time. It takes a 'manual' step to have the replica start.
What do you mean by a saved state? The contents of the running VM are regularly being copied to the replica so it is being kept up to date (within a few minutes). The VM saved state does not make sense in this environment, so I am not sure what you mean by saved state.
- Marked As Answer by Lawrence LvMicrosoft Contingent Staff, Moderator Friday, December 14, 2012 8:34 AM
Saturday, February 02, 2013 7:05 AM
If you save state a VM the replication data is sent to the replica server - but you're not able to initiate a failover if the original VM is in a saved state and still visible to the replica server.
I was a little disappointed that when doing an unplanned failover - the replica VM would boot up from an inconsistent state - it would have been very cool if something like a "saved state" was replicated. (Although I probably wouldn't have liked to pay the price in the bandwidth this would require).