MMRNLA
asked on
NetApp SnapManager for VI snapshot question
We are currently using NetApp SnapManager for VI (VSC.2.1.2) for our backups. Is there any way to determine what each VM contributes in regards to sizing on the backups?
In other words, we have 10 VMs in a datastore. Datastore backup kicks off everynight. For the past week we were seeing 2-3GB backups nightly. Then one night we see a 14GB backup. We would like to determine what VM or VMs caused this inflation in backup size.
In other words, we have 10 VMs in a datastore. Datastore backup kicks off everynight. For the past week we were seeing 2-3GB backups nightly. Then one night we see a 14GB backup. We would like to determine what VM or VMs caused this inflation in backup size.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I don't think this will give you correct results. Keep in mind that on the Netapp you're most likely de-duping data so VMWare snapshots are much different then Netapp snapshots.
Keep in mind that Netapp snapshots are typically data that is mostly deleted but still in place due to snapshot holding data. Since Netapp snapshots don't use a lot of space for new data (pointers only), snapshots typically grow as data is being deleted or moved from the datastore but needs to be held by the snapshot until the scheduled snapshots schedule deletes it.
My $.02
Keep in mind that Netapp snapshots are typically data that is mostly deleted but still in place due to snapshot holding data. Since Netapp snapshots don't use a lot of space for new data (pointers only), snapshots typically grow as data is being deleted or moved from the datastore but needs to be held by the snapshot until the scheduled snapshots schedule deletes it.
My $.02
ASKER