Group: Forum Members
Posts: 12K,
Visits: 72K
|
When you start a Reflect image as a VM with viBoot, writes are redirected to a separate file. It's a similar concept to having a VM snapshot/checkpoint. Within viBoot, you have the option to create a new Reflect backup of the VM's current state. The reason is that one of the use cases for viBoot is for business continuity in case of a disaster. For example, if you have a physical server that completely dies, you can start that server's backup as a VM somewhere else to keep that server up, and when you repair the server, you can make a new Reflect backup based on the current state of that server VM (which might have been running for a few days at that point) and use THAT to restore the real physical server. But if you don't care about saving changes, you can just delete the VM within the viBoot application whenever you're done with it and choose not to preserve changes. But no matter what you do, the Reflect image backups themselves are never modified.
|