I am doing some server consolidation by exporting nodes from one server to another and am finding that once the node data gets to the target and offsite copies are completed, there are some big differences in the total occupancy numbers.
For instance, of 3-nodes I exported, there is a difference of between <1GB (rounding error - nothing to worry about), 300GB (concerned about such a big difference) and 1TB LESS (really concerned about such a huge difference) on the target server. The management classes are identical so I can't explain the differences based on number of copies and other retention values. None of these nodes I just exported are being used/actively backing up so no new backups to confuse things. Expire inventory had finished before the exports were run. Export Node says "completion state of SUCCESS". All ISP servers are at 8.1.14.110. Not running dedup (regular FILEDEV class) on any server. We had too many issues with damaged backups. IIRC, a long time ago there used to be an Audit Occupancy command but that seems to have gone away? So how does one fix these erroneous occupancy numbers? Audit volumes? Audit stgpools? -- *Zoltan Forray* Enterprise Backup Administrator VMware Systems Administrator Enterprise Compute & Storage Platforms Team VCU Infrastructure Services www.ucc.vcu.edu zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://phishing.vcu.edu/ <https://adminmicro2.questionpro.com>
