Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

4639

April 24th, 2008 01:00

What to check if auto media management not working?

The question is rather simple. I have had auto media management running, Although nothing is changed, it now stopped. If i manually change the mode of the media to recyclable, the media is re-used. As far as i can see i have no issues concerning faulty values for retention time.

Can anyone help me in a step-by-step check if all the required service etc are running in order for Auto media management to work?

14.3K Posts

May 20th, 2008 13:00

There is NSR_SAVESET_RETENTION to keep an eye on when it comes to retention for module.

455 Posts

April 24th, 2008 01:00

Look at the properties/configuration. of you jukebox or drive see if the box is ticked / or not.

On the devices tab, highlight you jukebox, right click / select properties.....

19 Posts

April 24th, 2008 04:00

Box is checked. Was already on also.

455 Posts

April 24th, 2008 04:00

Highlight you media, right click, select recycle ( Not Change Mode) make sure its on Auto, and try.

19 Posts

April 24th, 2008 05:00

Thanks again. This also already on Auto.

Is it possible to check wether a process has ran and found a number of tapes to begin re-using?

Message was edited by: AFC
AFC

455 Posts

April 24th, 2008 06:00

If, like you said, the Recycle is on Auto and you have media management on Auto in your device config then the media should state should change to Recyclable, provided the Browsing/Retension period assigned to all your Savasets on that media are expired.

Check your Retension and Browsing policy for your clients.

19 Posts

April 24th, 2008 06:00

If, like you said, the Recycle is on Auto and you
have media management on Auto in your device config
then the media should state should change to
Recyclable, provided the Browsing/Retension period
assigned to all your Savasets on that media are
expired.

Will look into that, i have one piece of media that normally would be up to recycle today. I must check myself if it will be automatically set to recyclable? There is no logging that states if the changeover is attempted but (for any reason) not succeeded? Would be nice to take a look into that!

Check your Retension and Browsing policy for your
clients.

Will check this straight away and let you know if i have found anything there. If something is not set-up correctly in terms of retention time, should the listed retentiondate not still be a future date (in other words: a date still to come)?

In the mean time i have checked my clients, all have a (browse and) retention time set to 4 weeks.
I will check if one particular tape will be overwritten correctly.

It remains strange that the recycle process cannot be monitored...

Message was edited by:
AFC

19 Posts

April 24th, 2008 23:00

The one tape i was looking at is now set to recyclable (On this particular one it works. Let's see if it remains working in the coming days. So i'll keep this one open for now

14.3K Posts

April 28th, 2008 03:00

Auto media management has nothing to do with recycling tapes.

253 Posts

April 28th, 2008 08:00

I agree with Hrvoje, I do not have auto media management set and my tapes still automatically recycle.

19 Posts

May 13th, 2008 00:00

Here's the result of the MMINFO command (It is one of the tapes that could be re-used as far as i could see):
C:\Documents and Settings\Administrator>mminfo -avot -q volume=000005L3 -r "ssid
,ssretent(20),ssflags,sumflags,clflags,clretent(20),state,type"
ssid retention time ssflags fl clflg clretent state type
4278126440 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
4294903656 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
4261349224 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
4211017578 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
4244572008 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
3774810197 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
4194240362 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
4227794794 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
4177463147 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
4160685944 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
4143908728 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
3976136627 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
3959359431 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
3942582217 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
3925805001 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
3909027801 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
4127131513 5/9/2008 11:59:59 PM vrF cr 5/9/2008 11:59:59 PM LTO Ult
rium-3
4110354302 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
4093577086 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
4076799870 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
4060022669 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
4043245458 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
4026468253 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
4009691040 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
3992913830 5/9/2008 11:59:59 PM vrF cr 5/9/2008 11:59:59 PM LTO Ult
rium-3
3573483924 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
3892250592 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
3539929503 5/9/2008 11:59:59 PM vrF cr 5/9/2008 11:59:59 PM LTO Ult
rium-3
3506375077 5/9/2008 11:59:59 PM vrF cr 5/9/2008 11:59:59 PM LTO Ult
rium-3
3875473398 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
3858696198 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
3841918987 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
3456043467 5/9/2008 11:59:59 PM vrF cr 5/9/2008 11:59:59 PM LTO Ult
rium-3
3825141786 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
3808364586 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3
3724478765 5/9/2008 11:59:59 PM vF cb 5/9/2008 11:59:59 PM LTO Ult
rium-3

What do i need to look for in the output of this command?


As for the versions we are running NetWorker Management Console version 3.2.3.Build.11 based on NetWorker version nw_7_3_2_jumbo.Build.11. This is installed on a Windows 2003 Server Enterprise Edition, Service Pack 1.

19 Posts

May 13th, 2008 00:00

After a few days of carefully observating, i find that nothing is happening in terms of re-using the tapes. I am relabeling the tapes now in the hope that a newly applied label will recycle the thing when the tape is needed.

@ Hrvoje and Larry Alexis: Is there some sort of checklist that i can use to see if everything i am doing is correct?

All answers are greatly appreciated!

14.3K Posts

May 13th, 2008 00:00

For one such tape can you post following:
mminfo -avot -q volume= -r "ssid,ssretent(20),ssflags,sumflags,clflags,clretent(20),state,type"

Also, what NW and OS is that? Recently there has been an issue recognized respect to nsrim which could cause issue like that in case you have specific OS and NW version.

14.3K Posts

May 13th, 2008 01:00

If on UNIX box do man mminfo. If on Windows, you can download from PL docs section for NW document which is titled Command Line Reference Guide.

Yes, both values need to be expired for saveset to expire. Let's play with your file system then.

Do following:
mminfo -avot -q client= -r "savetime(20),sscreate(20),sscomp(20),ssbrowse(20),ssretent(20),clretent(20),level"

This will give you time of backup (both client and server side) and their policies applied along with level.

14.3K Posts

May 13th, 2008 01:00

From output you can see that majority of savesets are still browsable and expired. Actually none of them is expired yet and majority of them is still browsable. I'm not sure about which locale NW is using on your system, but 5/9/2008 might mean 5th September and not 9th of May. And even if it is May it is possible that due to backup cycle dependency this data is till valid (and it will remain valid as long as last backup cycle component is).
No Events found!

Top