Networker 8.2 :: although deleting the expired saveset manually, Disk Space not decreased

Have to wait for nsrim, or run it manually "nsrim -X"

Regards

Lukas

Sent with BlackBerry Work (www.blackberry.com)

Please tell us what the exact NetWorker version you are using on your NetWorker server.  There are many variations of 8.2.x.x.

> Check if the disk volume has the "scan needed" flag. If yes, you'll need to change it (right click on volume -> Mark Scan Needed -> Scan is Not needed -> OK). Then, you can run nsrim -X to recover space.

The "scan needed" flag is set by NetWorker because it believes there are valid savesets that are on the volume that is not in the media database.  For this reason, it is not a good idea to disable this flag without further investigation, otherwise you can cause data loss.

Better to perform the scan using "scanner -m (device name)".  Once scan is completed, you can then remove the flag, and then review what is on the volume.

I have done the attached steps, I could delete the data before 25th April. but after the next backup, I couldn't find any backup before the action I executed? I have no explanation for that !!

[root@nebrser ~]#  mminfo -avot -q 'client= bdsobr104-bar' -r 'totalsize,pool,group,client,sscreate(20),sscomp(20),level,name' | grep -v 'ss-created' |sort -u

1783838404 DiskPool      Dsa_bdsobr104-bar_DB_grp bdsobr104-bar 05/08/2017 08:31 05/08/2017 08:36 full DSA_DB

1784014644 DiskPool      Dsa_bdsobr104-bar_DB_grp bdsobr104-bar 05/09/2017 06:36 05/09/2017 06:41 full DSA_DB

       4904 DiskPool      Dsa_bdsobr104-bar_FS_grp bdsobr104-bar 05/09/2017 00:48 05/09/2017 00:48 full /dev/null

       5052 DiskPool      Dsa_bdsobr104-bar_FS_grp bdsobr104-bar 05/10/2017 00:47 05/10/2017 00:47 full /dev/null

      total pool          group       client          ss created         ss completed      lvl name

[root@nebrser ~]#

[root@nebrser ~]# mminfo -mv

state volume                  written  (%)  expires     read mounts capacity volid      next type

       nebrser.001              184 GB   2% 06/07/2017  32 GB    25   7407 GB 9053920 4293594183 file

       nebrser.002              186 GB   3% 06/06/2017  65 GB    21   7407 GB 4287244003 4175894423 file

       nebrser.003              201 GB   3% 05/26/2017  23 GB    22   7407 GB 4270466789 4257600639 file

[root@nebrser ~]#

@ eng.galileo@gmail.com : This discussion is already marked as "This question has been Answered."

Please remove this flag if it is not yet resolved.

There is a discrepancy between how much space NetWorker is using vs. how much the file system reports is being used. For each device, the file system through “df -h” shows 400 GB+ usage that is unaccounted for from the mminfo output.

volume               written  (%) 

nebrser.001          184 GB

nebrser.002          186 GB

nebrser.003          201 GB

Filesystem                              Size  Used Avail Use% Mounted on

/dev/mapper/mpath0p1              7.3T  6.3T 660G  91% /nsrstore_0

/dev/mapper/mpath1p1              7.3T  6.3T 661G  91% /nsrstore_1

/dev/mapper/mpath2p1              7.3T  6.3T 653G  91% /nsrstore_2

Please verify the usage by:

1. Display the volume name, and the device they are mounted on:   nsrmm -C
2. Use mminfo to display all the saveset id numbers and their corresponding saveset sizes:
   • mminfo -avot -r volume,ssid,sumsize  nebrser.001 | sort > nebrser001.txt 2>&1
   • mminfo -avot -r volume,ssid,sumsize  nebrser.002 | sort > nebrser002.txt 2>&1
   • mminfo -avot -r volume,ssid,sumsize  nebrser.003 | sort > nebrser003.txt 2>&1
3. Since your NetWorker devices are configure as simple file devices, then for each saveset, there will be a file where the device is created, and the file name will be the saveset id number.  For example, on my NetWorker server, you see mminfo reporting a saveset with ssid=4279458770, and on the file system, there is a corresponding file 4279458770.0.  (The space that this ssid occupies is slightly larger due to overhead).

mminfo -avot -r volume,ssid,sumsize

volume               ssid                    size

               Default.001         4279458770          82 KB

dir  C:\temp\file-device

05/10/2017  02:29 PM           131,072          4279458770.0

05/10/2017  02:19 PM                47                nsr.dir

05/10/2017  02:19 PM            65,536            volume

The ssid list in step #2 and #3 should be identical. The corresponding sizes should also be similar, with a small difference.

Using the output from #2 and #3, you should be able to identify what should and should not be on the file device directory structure.  And if the discrepancy are because of ssids, then you should scan the ssid (scanner -m -S ssid#  nw-device-name) or the entire volume, to repopulate the media database with this info, and then determine if you want to keep the ssid.  If not, then delete using  : nsrmm -d -S ssid#