To step a little bit outside of the TSM box, have you considered using
iptables (you¹re a Linux shop, right?) with a time rule on the TSM server to
block these troublesome hosts/subnets from connecting to TSM during
undesirable times. You can either be heavy-handed and stop any matching
packet afte
Maybe both are correct!
Perhaps the discrepancy folks are seeing relates to .vmdk files that are
thick vs. thin provisioned. If it's thick-provisioned, the .vmdk file is
full-size and thus when the .vmdk is backed up, you get everything (used and
unused space). If it is thin-provisioned, the .vm
