Highlighted
gmelo24
1 Copper

why Networker can't not automatically delete save set

Hi

why Networker can't not automatically delete saveset?

when i run the command nsrim -X said:

No space was recovered from device....

asd.png

Tags (1)
0 Kudos
4 Replies
masonb1
3 Argentium

Re: why Networker can't not automatically delete save set

Hello gmelo24,

You dont mention the NetWorker version you are running but a common cause of this type of situation is where the ddboost volumes are marked as "scan required".  You can check this by running mminfo -q scan=true -r <volume_name>

When "scan required! flag is set volume contents are not changed.

There are several ways to remove this flag if this is the reason - consult Knowledge Article 466500 for reference (look this up on Support portal or follow link below: -

https://emcservice--c.na55.visual.force.com/apex/KB_BreakFix_clone?id=kA2j0000000R5nJ

There can be other causes if this does not resolve your issue but probably best to open a Support Case with DELL EMC and then when root cause identified you can report back here for reference.

Regards,

Bill

0 Kudos
gmelo24
1 Copper

Re: why Networker can't not automatically delete save set

The Networker Version is 8.2.2.6

0 Kudos
masonb1
3 Argentium

Re: why Networker can't not automatically delete save set

Hello gmel024,

This version of NW is not in Support now and 8.2.4 will go out of support soon.

Did you find any devices reported as scan required by the mminfo command I put in last post?

Were you able to follow Knowledge Article to remove the flag if you did?

If none were scan required - do you have recyclable savesets on these DDBoost volumes - you can check with

mminfo -q volume=<vol name>, recycle=true -r client,name,ssid,ssflags

This should list anything which is recyclable which could possible be deleted after further checks.

Regards,

Bill

0 Kudos
ble1
6 Indium

Re: why Networker can't not automatically delete save set

It can be couple of things... first, check what you have on those devices... for example:

mminfo -avot -q volume=<volume name> -r 'name,savetime(20),ssbworse(20),ssretent(20),level,group,client,name'

Do this for each device and inspect output.  ssid won't be removed if:

- there is dependent savesent down the line (see level dependency)

- scan flag is set (mminfo -avot -q scan -r volume will show you if this is the case)

- in some cases, read operations on volume will block removal

0 Kudos