maiocon.blogg.se - Snapshot consolidation

To manually remove the snapshot chain and revert your VM to its pre-snapshot configuration, you must remove it from your inventory. NOTE: This will effectively revert your VM to its state when the first snapshot in the chain was created – this may be many months in some cases! In many cases this is just seven hours worth of replication.

When this happens, the most effective resolution is to remove the snapshot chain manually, and point the VM back to its original (underlying) *.vmdk and *flat.vmdk file. With Replicas, the priority is on successful replication and each snapshot represents only one restore point. Often when you see an invalid snapshot configuration, VMware is no longer able ro consolidate the disks and you will see the following error:

24 VMware snapshots created/removed on the source VM.

Each snapshot is represented by a disk descriptor file “*-0000**.vmdk” and a thin disk representing the delta accumulated “*delta.vmdk”.

7-9 VMware “snapshots” at the replica site at any given time (these are the restore points).

This is NOT to sat that there is a problem with Veeam Veeam is awesome, however it is subject to events on the underlying infrastructure and possible on VPN/MPLS links between sitesįor example: A VM with one disk, which is replicated offsite hourly with seven restore points will have the following snapshot overhead: Specifically if you use a product like Veeam, which leverages a VMware Snapshot to quiesce data, you may see an Invalid Snapshot Configuration from time to time.The more often you protect your data, the more often you create and remove snapshots.

The more heavily you rely on snapshots, the more likely it is you will come across a problem with snapshots. Mostly, they occur because of problems with storage arrays during snapshot creation/consolidation, but they can also occur if certain process become interrupted (like replication) mid-snapshot. John Borhek How to guides, VMware January 22, 2018