UNSOLVED

earth2009

updated

17 years ago

E

earth2009

53 Posts

0

384

July 24th, 2009 04:00

Networker EDL Recycling Problem

Networker 7.4.4 running on Windows x64 2003 box, with EDL and Scalar i2k libraries fibre attached via switch.

We have recently upgraded Networker Server from 7.3.3 to 7.4.4 due to bugs found in the NMC in version 7.3.3. No clients upgraded all were at least 7.3.

I have found that certain volumes in the EDL are not being automatically recycled. AMM is enabled, recycling from/ to other pools under Media Pools is ticked, no hardware issues with the EDL.

E.g. Volume S00024 in the "Daily EDL" pool expired on 22/07/2009 but is just sitting there as full.

I have to go to Media> Volumes> right click volume> recycle- auto> ok then it recycles fine.

Why is Networker doing this? I have tried turning off AMM and it still does the same. EDL is working ok, backups run fine, but there are a lot of full volumes some have not expired yet (5 week browse policy and 5 week retention policy as they get cloned off to tape), some have which just sit there.

The knockon effect is some backup groups just hang overnight with "waiting for writeable volumes for daily EDL pool".

Has anyone ever seen this issue before and know of a workaround or fix?

It's worth pointing out that AMM is turned off for the Scalar i2k library but it managed to recycle expired volumes just fine- 3 week browsable and 6 months retention policy.

I always thought AMM was for labelling new unlabelled volumes and not recycling, but not sure on this.

Many thanks.
  • DavidHampson

    2 Intern

    •

    1080 Posts

    88

    0

    Posted July 24th, 2009 05:00

    First of all AMM will only affect unlabelled tapes so if these are previously used tapes forget about it, it is out of the equation.

    Secondly we need to determine if the volumes you expect to be reused are recyclable - can you run this command against one of the volumes:

    mminfo -q volume=volumename -r state

    - confirm the volume comes back with an E for expired. If not check for savesets not yet recycled:

    mminfo -q volume=volumename,ssrecycle=false

    One thing that may cause the problem if all savesets have passed out of their expected retention time is that there may be dependent savesets - incremental savesets yet to expire on other volumes which require earlier incrementals and full backups to be able to do a recovery of the saveset they were taken for.