- Posts: 21
- Liked: never
- Joined: Dec 08, 2011 5:52 pm
- Full Name: Lyle Ryan
As a repository gets full, I'd like to see which VM's are the biggest consumers. Maybe I can adjust the backups of those VM's or contact the owners to investigate, rather than increasing the repository size or decreasing retention. In our case repository expansion is not easy.
The size of the VM probably isn't the only indicator, since backup sizes also depend on how often the data is changing. A view of repository consumption per VM would really tell me which VM's to look at.
- Posts: 7328
- Liked: 773 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
When you backup several VMs in the same job, the VMs data is deduplicated, so it is not possible to recognize the size of each VM backup.
However, in the upcoming version, will be an option to keep VM backups separately.
For now you can use VM Change Rate History to detect which VMs contribute most to the backup file size.
Users browsing this forum: Bing [Bot], Google [Bot] and 21 guests