Is there a way to take VMware snapshots instead of production data?
Best answer by coolsport00
View original
Page 2 / 2
Userlevel 7
+6
Not much changes with storage snapshots
it’s just the SAN volume gets a snapshot and the VMware snpashot can be removed.
While Veeam does it’s thing, that SAN volume snapshot is a clone of the VM with the snapshot on it.
I get that. But in the case of a storage snapshot, I believe both the base disk and delta disk(s) would be accessible because the active workload is shifted back to the life files on the array, and not the snapped files.
Userlevel 7
+22
So yeah, those snapshots are there to store the changing data in a delta. If you delete them you lose the data that changed since the start of the backup. I guess when they get orphaned they manage to consolidate or something hence no issues deleting them? I mean otherwise if no one checked that thing could grow to be a monster and then you might not be able to consolidate.
I just consolidated a 140TB Snapshot :)
wow that must have been fun. I have had really bad situations with VMs Snapshots running for weeks.
Userlevel 7
+22
Think about it., If Veeam doesn’t backup the “last” snapshot, why would it be taking a snapshot at all.
I may have to do my own testing to make sure I understand how it works correctly. I had assumed that CBT included blocks on any delta disks in use as well. But like I said, easy enough to test.
With that said, in reference to your above, it takes a snapshot in order to free up the base disk for access. If the VM is attached to the base disk, another VM can’t attach to it to gain read access. The snapshot offloads the access for the production VM to a delta (snapshot) disk. This is almost sort-of difference in the case of storage snapshots.
Not much changes with storage snapshots
it’s just the SAN volume gets a snapshot and the VMware snpashot can be removed.
While Veeam does it’s thing, that SAN volume snapshot is a clone of the VM with the snapshot on it.
a wait a storage snapshot so not as bad
Userlevel 7
+17
This is really becoming a great thread...love it! 😊 Would be nice to have a Veeam PM chime in here….
Userlevel 7
+7
This is really becoming a great thread...love it! 😊 Would be nice to have a Veeam PM chime in here….
Agree, this thread has turned into a great wealth of knowledge when it comes to snapshots.
Userlevel 7
+17
You can read more here.
Userlevel 7
+17
Userlevel 7
+17
The Snapshot Hunter feature Veeam created several years ago was much needed. Mostly takes care of orphaned snaps. You are correct though...if, for whatever reason, Veeam can't /doesn't successfully remove the snap after a backup, it can grow. It's highly advised to never manually delete them or yes...you will lose data. Veeam does continue trying to consolidate using the Hunter. If it still can't remove it, all that's needed is to create a snap manually, let it go for like a minute, then consolidate them all.
Userlevel 7
+20
So yeah, those snapshots are there to store the changing data in a delta. If you delete them you lose the data that changed since the start of the backup. I guess when they get orphaned they manage to consolidate or something hence no issues deleting them? I mean otherwise if no one checked that thing could grow to be a monster and then you might not be able to consolidate.
I just consolidated a 140TB Snapshot :)
😮
Userlevel 7
+6
Although, the existing snapshots prohibit the usage of changed block tracking (CBT). Therefor the speed of the backup will be slower than without additional snapshots.
Also good to know. I didn’t realize that CBT didn’t apply to snapshots - I do see however that to enable CBT there shouldn’t be snapshots on a VM or that can cause errors.
Userlevel 7
+8
Think about it., If Veeam doesn’t backup the “last” snapshot, why would it be taking a snapshot at all.
I may have to do my own testing to make sure I understand how it works correctly. I had assumed that CBT included blocks on any delta disks in use as well. But like I said, easy enough to test.
With that said, in reference to your above, it takes a snapshot in order to free up the base disk for access. If the VM is attached to the base disk, another VM can’t attach to it to gain read access. The snapshot offloads the access for the production VM to a delta (snapshot) disk. This is almost sort-of difference in the case of storage snapshots.
Not much changes with storage snapshots
it’s just the SAN volume gets a snapshot and the VMware snpashot can be removed.
While Veeam does it’s thing, that SAN volume snapshot is a clone of the VM with the snapshot on it.
Page 2 / 2
Comment
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.