I recently migrated to a new vCenter which, as expected, needed various work etc. to get the backup/replication jobs in sync.
However, I've come in this morning to a failed Backup Copy job due to the WAN-X cache drive filling up. It was configured with 250Gb but only covers no more than around 6 OS/s (would be useful if there's a way we can actually review this info somewhere?
I've added another 50Gb & re-sync'd the job but it makes me wonder whether or not we're leaving "old" digests folders, related to previous instances of VMs on legacy vCenters behind when we do these kinds of migrations? If so, what's the safest way to clean them up given that everything is named with GUIDs etc. so not easily recogniseable?
**Feature Request**: As an aside, I can't remember which of our jobs are pointing to this WAN-X (I know someone is likely to ask how many jobs are using it) without editing every job to check, but it would be really cool if there was some way we could do the equivalent of, say, right click on a WAN-X in the console, select properties or simlar, then list all the jobs that are CURRENTLY dependent on that WAN-X? Would be even better in a standard pane (select WAN-X on the left, show useful info about it on the right etc.)
Actually, if my theory above is correct & there are defunct digests lurking around, it'd also be useful to be able to somehow automatically clear down legacy digests folders/caches...
[New Sig: PLEASE get GFS tape support for incrementals!!!]