SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
staging problem
Author Message
Post staging problem 
Hi all

I have a problem that I have seen at two separate networker installations:

7.6.2.681 (server and client)
Windows nsrserverhost

Staging policy:
Stage from AFTD to tape at certain watermarks.
Tape library has one drive

The staging starts and requests to read from AFTD and a tape(!!)

What could make it need to read from a tape ?
How can I locate which savesets on this tape that it is trying to stage ?

Regards,
Eivind



via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

View user's profile Send private message
Post  
It looks strange as it should only move save sets from the AFTD volume.

However, assuming a bug, could it be that you have also assigned tape devices to the source pool and that for whatever reason NW creates a worklist that also contains tape save sets?

Just a guess.

View user's profile Send private message
Post staging problem 
There was some changes in 7.6 that changed the way AFTD volumes work.
Previously, if your AFTD filled up during a save, the save would wait for space to become available in that volume.
Now, AFTDs are handled like a tape volume, and will continue the saveset on another volume.

Maybe your AFTD ran out of space, and the tail of the saveset was written to a tape?
So when you stage that ssid, it would need to read the start of the saveset from AFDT, and the end of it from tape - because staging acts on savesets, not chunks of savesets in a volume.

You could identify any continued savesets with 'mminfo -av', the 'c' flag in the output is complete, h is head (start of saveset), m is middle and t is tail.
Those last three flags all indicate that more than one volume is needed for that saveset.

Or, something like this will grab a list of all ssids on your AFTD volume, and then check what volume types and names contain each saveset

$ mminfo -av -q 'volume=your_aftd_volume_name' -r ssid | perl -ne 'chomp;system("mminfo -q ssid=$_ -xc, -r ssid,type,volume|grep -v ssid");'
(but won't work in a windows environment unless you've got perl/grep available, there's probably ways to do the same thing from windows with different tools though)

Regards,
Josh




7.6.2.681 (server and client)

The staging starts and requests to read from AFTD and a tape(!!)

What could make it need to read from a tape ?
How can I locate which savesets on this tape that it is trying to stage ?


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Post staging problem 
Hi

Thank you for your reply.

I don't see how it can write the tail of a backup to a tape when there is only one drive and it is used to receive the stage job.
None of the savesets have other flag than 'c'

But, there is an issue with the raid controller on the backupserver and I will wait for it to be resolved to see if it may somehow be the casue.

Thanks
Eivind


-----Original Message-----
From: Small, Joshua [mailto:joshua.small < at > citi.com]
Sent: 24. november 2011 01:06
To: 'NETWORKER < at > LISTSERV.TEMPLE.EDU'; Eivind Antonsen
Subject: RE: staging problem

There was some changes in 7.6 that changed the way AFTD volumes work.
Previously, if your AFTD filled up during a save, the save would wait for space to become available in that volume.
Now, AFTDs are handled like a tape volume, and will continue the saveset on another volume.

Maybe your AFTD ran out of space, and the tail of the saveset was written to a tape?
So when you stage that ssid, it would need to read the start of the saveset from AFDT, and the end of it from tape - because staging acts on savesets, not chunks of savesets in a volume.

You could identify any continued savesets with 'mminfo -av', the 'c' flag in the output is complete, h is head (start of saveset), m is middle and t is tail.
Those last three flags all indicate that more than one volume is needed for that saveset.

Or, something like this will grab a list of all ssids on your AFTD volume, and then check what volume types and names contain each saveset

$ mminfo -av -q 'volume=your_aftd_volume_name' -r ssid | perl -ne 'chomp;system("mminfo -q ssid=$_ -xc, -r ssid,type,volume|grep -v ssid");'
(but won't work in a windows environment unless you've got perl/grep available, there's probably ways to do the same thing from windows with different tools though)

Regards,
Josh




7.6.2.681 (server and client)

The staging starts and requests to read from AFTD and a tape(!!)

What could make it need to read from a tape ?
How can I locate which savesets on this tape that it is trying to stage ?


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

View user's profile Send private message
Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB