Unsolved
14 Posts
0
742
October 22nd, 2020 11:00
Determining total size of all save sets, and possible filesystem comparison to save sets
Environment:
Single large (36TB) client split into 2 clients (System drives vs Data Drives) being backed up through Networker to a single non-Deduplicated Disk Volume. 1 Full backup each month, 2 months retention (though a 4+ day long job sometimes fails and requires manual intervention). There is definitely data older than 2 months right now due to some failed fulls across different data drives at different times, which will be cycled out after the next successful full on the drive in question.
Question:
I want to compare how much data Networker believes it has saved in save sets vs the actual space used on the Disk Volume, which is exclusively Networker data, but haven't been able to find this after a bit of searching.
nsrcapinfo -d 365 has a 'Capacity estimate' of 46661.9180. If I assume these are GB, that's 46.6TB
Networker Admin - Media - Disk Volume shows 53TB
A quick visual after searching Save Sets adds up to well over 100TB
The server itself has 37TB (x2 fulls = 64TB), plus whatever in Incrementals it may have.
The backup volume itself shows 88.4TB used
Offhand, I do not know block size between the Client and the Backup Targets, though I could find out.
How can one reconcile all the different data into a cohesive answer?
Possibly a second related question - can one scan a Disk Volume for data that is NOT related to any non-expired save sets (orphaned data) to delete?
Thanks!
bingo.1
2.4K Posts
0
October 22nd, 2020 15:00
The first issue is that you need to get the long ssids and the exact save set size. You can achieve this by using mminfo like
mminfo -q "query_parameters" -r "client,level,savetime,ssid(60),sumsize(25)" -ot > file
Now, if you look the directory tree of your aftd volume, you will find the save set in one of the subdirectories being stored in the file "long_ssid". You can get the file size and compare both values. Be careful - the are not 100% the same as the disk file also contains some metadata which sumsize will not show.
scanner, if applied to a volume, will find any save set on the volume - no matter which backup status it has.
Hope this helps.