Networker

Re: [Networker] Networker wanting mount of AFTD on wrong storage node?

2008-03-13 10:04:12
Subject: Re: [Networker] Networker wanting mount of AFTD on wrong storage node?
From: Thierry FAIDHERBE <Thierry.Faidherbe AT SKYNET DOT BE>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thu, 13 Mar 2008 15:01:22 +0100
Are you sure the tape containing the staged data to be
in the library (relaunch the inventory to be safe).

Verify also DNS : if the exchange client cannot resolve
SN02, it relies on servers' storage node affinity where SN01 is maybe
the first entry in the list.

HTH

Th
 

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Oscar Olsson
Sent: jeudi 13 mars 2008 14:07
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Networker wanting mount of AFTD on wrong storage node?

We just attemped to restore an exchange database, using NME 5.0.0.315, where
part of the data needed has been staged to tape, and some part of it is on
the AFTD. The AFTD device and volume in question is available on storage
node sn02. However, networker keeps insisting on wanting that volume on
storage node sn01, especially since that node doesn't have any AFTD devices
at all. The question is, why is that?

I have restricted the respective pool to only be allowed to use the AFTD
devices that have a volume mounted for that pool, just to ensure that it
never waits for the volume anywhere else. Also, the clients storage node
affinity list lists storage node sn02 as the top.

This is what it looks like in the logs:

03/13/08 13:34:05 nsrd: Volume Full1mRet3mDB.002.RO mounted on
sn02.qbranch.se needs to be mounted on sn01
03/13/08 13:34:05 nsrd: media event cleared: mount of Full1mRet3mDB.002.RO
cancelled by server
03/13/08 13:34:07 nsrd: media info event: adv_file disk Full1mRet3mDB.002.RO
will be needed
03/13/08 13:34:07 nsrd: Volume Full1mRet3mDB.002.RO mounted on
sn02.qbranch.se needs to be mounted on sn01
03/13/08 13:34:07 nsrd: media event cleared: mount of Full1mRet3mDB.002.RO
cancelled by server

I'm thinking that this might be a bug, possibly in the module for exchange
or in networker 7.3.3, which the server and storage nodes run.

//Oscar

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 with 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

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 with 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