ADSM-L

[ADSM-L] Huge differences in file count after exporting node to a different server

2017-10-25 15:37:12
Subject: [ADSM-L] Huge differences in file count after exporting node to a different server
From: Zoltan Forray <zforray AT VCU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 25 Oct 2017 15:35:00 -0400
I am curious if anyone has seen anything like this.

A node was exported (filedata=all) from one server to another (all servers
are 7.1.7.300 RHEL)

After successful completion (took a week due to 6TB+ to process) and
copypool backups on the new server, the Total Occupancy counts are the same
(13.52TB).  However, the file counts are waaay off (original=17,561,816 vs
copy=12,471,862)

There haven't been any backups performed to either the original (since the
export) or new node. Policies are the same on both servers and even if they
weren't, that wouldn't explain the same occupancy size/total.

Neither server runs dedup (DISK based storage volumes).

Any thoughts?

--
*Zoltan Forray*
Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
Xymon Monitor Administrator
VMware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
www.ucc.vcu.edu
zforray AT vcu DOT 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/


ADSM.ORG Privacy and Data Security by KimLaw, PLLC