Networker

[Networker] A problem with the staging.

2006-02-10 03:29:48
Subject: [Networker] A problem with the staging.
From: Jean-Marc VAN MILLON/CRELAN <jm.vanmillon AT CRELAN DOT BE>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 10 Feb 2006 09:12:20 +0100
hello,

Our infrastructure:
A legato server, which is backuping his index and bootstrap to a device
disk (a local filesystem of 40 GB).
Two storage node connected to HP library, with each 4 tape drives.
Each server or node is running linux SuSE SLES 8.
As the device disk is limited by space, we do some staging from the device
disk to one HP library, each day.

The problem :
Usually a save set on the device disk is copied on one tape and then
deleted.
Some times, there is something strange :
I try to stage one saveset, legato respond and mount a tape of the correct
staging pool in each tape drive. So i've got 4 tape mounted instead of just
one.
But legato still didn't actually stage anything....
Any idea how i can stage this saveset?
Is there a way to delete without staging a saveset present on a device
disk?


Some logs:

How I get the information to stage :
 /usr/sbin/mminfo -a -ocnt -rssid,cloneid,name,totalsize
-q'!incomplete',pool=LBKdrpool,location=localdiskRO
give me:
...
2213264967  1139523142 bootstrap                        41146336
2783452925  1139285756 index:hn083                    6178455108
770453970   1139552721 index:hn083                    6290131956



When i try to stage the second saveset, i've got my problem.

hn100:/nsr/LBKscripts # /usr/sbin/nsrstage -v -s hn100 -b LBKbootstrap -m
-S 2783452925/1139285756
Obtaining media database information on server hn100
Parsing save set id(s)
Migrating the following save sets (ids):
        2783452925
Automatically copying save sets(s) to other volume(s)

Starting migration operation...
NSR server hn100: busy
waiting 30 seconds then retrying
NSR server hn100: busy
waiting 30 seconds then retrying
NSR server hn100: busy
waiting 30 seconds then retrying
NSR server hn100: busy
waiting 30 seconds then retrying
NSR server hn100: busy
waiting 30 seconds then retrying
NSR server hn100: busy
waiting 30 seconds then retrying
NSR server hn100: busy
waiting 30 seconds then retrying
NSR server hn100: busy
waiting 30 seconds then retrying


And with legato networker administrator, i can see 4 tape mounted of the
pool LBKbootstrap. But still, legato doesn't write.



Thank you for your answers,
Kind regards,



Van Millon Jean-marc
Crédit Agricole
Bvd Sylvain Dupuis, 251
1070 Bruxelles/Belgium
Dpt: ICTS/Production/Osa
Tel:02/558.73.63
Fax:02/558.76.32
Email: jm.vanmillon AT crelan DOT be





This email and any attached files are confidential and may be legally 
privileged.If you are not the intended recipient, any disclosure, reproduction, 
copying, distribution, or other dissemination or use of this communication is 
strictly prohibited.  If you have received this transmission in error please 
notify the sender immediately and then delete this email.Email transmission 
cannot be guaranteed to be secure or error free as information could be 
intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain 
viruses.  The sender therefore is in no way liable for any errors or omissions 
in the content of this message, which may arise as a result of email 
transmission. If verification is required, please request a hard copy.
Please bear in mind that the content of any email leaving and entering the 
recipient network 
will be verified against viruses, spam and unsuitable content in accordance 
with the recipient 
policies and regulations.  Halted messages will therefore be destroyed without 
any further 
notice.

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

<Prev in Thread] Current Thread [Next in Thread>