Message "VM restart is recommended. Note that using the created snapshot might cause data inconsistency"
This is a multi-part message in MIME format. --------------030605070709060509080800 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi, After a Live Storage Migration Engine reported: Failed to create live snapshot 'Auto-generated for Live Storage Migration' for VM 'test'. VM restart is recommended. Note that using the created snapshot might cause data inconsistency. Let's say we restarted the VM and everything is working fine. In the snapshots tab, I see two snapshots: "Current" and a "Auto-generated for Live Storage Migration". We have the option to delete the "Auto-generated for Live Storage Migration" snapshot. Is there a chance that deleting this snapshot will commit it and corrupt it's backing chain image? Why is a restart recommended? --------------030605070709060509080800 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hi,<br> <br> After a Live Storage Migration Engine reported:<br> <blockquote>Failed to create live snapshot 'Auto-generated for Live Storage Migration' for VM 'test'.<br> VM restart is recommended. Note that using the created snapshot might cause data inconsistency.<br> </blockquote> Let's say we restarted the VM and everything is working fine.<br> In the snapshots tab, I see two snapshots: "Current" and a "Auto-generated for Live Storage Migration".<br> We have the option to delete the "Auto-generated for Live Storage Migration" snapshot.<br> <br> Is there a chance that deleting this snapshot will commit it and corrupt it's backing chain image?<br> <br> Why is a restart recommended?<br> </body> </html> --------------030605070709060509080800--
participants (1)
-
Christopher Pereira