Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Automatic Recycal 6

Status
Not open for further replies.

ingar

Technical User
Jun 24, 2003
15
SA
Hi

recently my Volumes which have passed the expiration date, don't automaticly change to Recyc mode (as they used to before) I have to manully change the mode to Recycalable, and once I change them to Recycalable, I get an R next to the Tape label. Any idea whats going wrong?

 
Amazing how often this question comes up.

Volumes do not become recyclable after a certain period.

Volumes become recyclable when all save sets contained on the volume become recyclable.

A save set becomes recyclable when it is no longer required in order to satisfy the retention policy, i.e. a younger save set can be used instead.

Your volumes are probably not changing to recyclable because they contain one or more save sets that have other save sets that depend on them. Thus by making them recyclable manually you are creating a situation where you may not be able to recover up to your configured retention period.
 
Hi

The Status of all the saveset with in the volume show to be recyc, and the volume still dose not change to Expired.
 
All of the savesets on that particular volume may be marked as recyclable because the individual savesets have passed their retention policies. The expiration of the volume occurs when all of the dependent savesets of the savesets on that volume have passed their retention policies. E.g., if you have a volume with full save sets of a particular client whose retention policy is one month, and you have weekly full backups with incrementals in between, the volume will not become recyclable until after the incrementals have all expired, approximately one week after the expiration date of the volume with the full backups.

There also seem to be some issues with aborted/incomplete savesets on volumes messing up recycling.
 
Hi,

I thought maybe someone is interessted in and that it may help. I had this problem several times and the Solution works.

Solution Title: Volumes are not automatically recycled anymore after update to NetWorker 7.1.2


Here is the solution:
Automatically scheduling nsrim -X to run on a daily basis will address this issue until all tape volumes written before the upgrade to NW 7.1.2 are overwritten. Once all the tapes prior to the update have been overwritten the scheduled runs of nsrim -X can be stopped and tapes will automatically recycle correctly.

Here is the problem or goal:
Volumes are not automatically recycled anymore after all residing savesets expired
Error: 'savegrp: nsrim run recently, skipping'

Problem Environment:
Windows 2000 SP4
NetWorker for Windows 7.1.2
Manually executed 'nsrim' leads to the expected results (expired tapes are marked as 'Eligible for recycling')

Causes of this problem:
The usage of the volume expiry date has changed in NetWorker 7.1.2. This used to be set to two years from when the tape was labelled, but it is now used to track the expiry date of the saveset written to the tape that will expire last. This is now used to inform NetWorker when a tape is eligible for recycling.

Changes affecting this problem:
Update to NetWorker 7.1.2


Kind regards
 

you can check the estimated recycle date for a volume:

mminfo -q volume=xxxxx,!ssrecycle -r ssbrowse,ssretent

and find the latest date.
 
Maybe the pool that the volumes belong to have the "manual recycle" selected?
 
Hi,

Mine is not upgraded from previous version of Networker, i installed it as version 7.1.2 but i faced same problem...

I have two groups (Daily and Weekly) and all clients are running sucessful FULL backup all the times.
For daily, my retention/browse policies is 6 days and for Weekly, it 30 days. but it just won't expire automatically until i run the nsrim -X , i belive that no dependency save sets as that no incr backup.

The status of saveset on the volumes show recyc,
can anybody tell me what went wrong?? or If there is dependency save set, how i check?

One more question.
How Networker pick the volumes in the pools?? i got new tapes and expired tape. whcih want will Networker choose first???

Thanks :)

day88
 
Hi day88,

NW prefers to use recyclable media before he will use a new one. However, by default, the media will always remain a member of the same pool. As a consequence, if there is a recyclable tape, NW will only use it if it belongs to the same pool - otherwise it will use a new one.

Of course you may open the pools by setting the two attributes
- recycle to other pools
- recycle from other pools
 
day88: two things:

1. yes, I faced the same f* problem, i must to issue nsrim -X every day, I don't know when I should stop, since I have save sets with a retention of 6 years... :(

2. I faced the same problem with the 6 days retention. I have some save sets (Oracle DBs) with a retention of 7 days (a week), but the index expirated in 1 month!! (take a look to thread480-912982 : )

So I fixed with the following:

The default retention policy is a year and the default browse policy is a month. Usssualy, all guys modify the "default server" (the only one marked in the windows GUI administrator, NW obviuosly) to retent/browse policy to 1 month. Now, when you have save sets with retentions less than 1 month (1 week or 6 days in our case) the save sets will have the week retention, but the index is saved by the server, who ussualy is the server by default, so the index will have a retention policy of 1 month regardless if the data has 1 week of retention. So to fix the problem I put the default server (the NW server ussualy) to a retention policy of the shorteest retention, in my case, 1 week, and the problem was solved.

This is not documented.

Hope this helps you.
 
There is a bug in 7.1.2 on Windows :

README for LGTpa67290
=====================

This binary provides a fix for the problem where nsrim skips
execution after savegrp runs. The problem only happens on
Windows.

The customers running 7.1.2 on Windows should use this fix.

The binary in the zip file is liblocal.dll.

All the Networker services should be stopped before
replacing liblocal.dll
 
This thread have been quite useful for several guys (including me)

LGTObug and milano, thanks a lot!!

I was issuing nsrim -X as LGTObug stated and worked as patch, but your final solutions will help to all of us. I didn't installed yet, but I guess your post has a strong source.

Cheers.
 
Where can I download the patch?

pls, don't ask me for legato support...

Cheers.
 
I also need the patch, but it is no longer located at the path specified. Anybody else know where it has been moved?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top