Networker

Re: [Networker] Waiting for an already mounted volume

2010-03-12 15:41:56
Subject: Re: [Networker] Waiting for an already mounted volume
From: Louis Munro <lm AT LOUISMUNRO DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 12 Mar 2010 15:39:57 -0500
Hi Allan and thanks for your help,
The problem is not so much that the devices unmount themselves (they are
still mounted). It's just that  networker seems to think they aren't there
anymore...

We mount the NFS shares almost exactly like you do except that we use the
automounter:
[ from /etc/auto_master ]
/netDD          -hosts
-nosuid,nobrowse,intr,vers=3,proto=tcp,rsize=32768,wsize=32768,xattr,hard

I'm wondering if the use of the automounter could be the cause of the
problem.
I'll try it without the automounter and see if that fixes it.
We are also due for an upgrade to 7.5. Perhaps this will be our excuse to
upgrade. It looks like there are a number of bug fix related to mounting
volumes in the more recent versions.

Regards,
Louis


On Thu, Mar 11, 2010 at 4:42 PM, Nelson, Allan <an AT ceh.ac DOT uk> wrote:

> Hi Louis
> I'm running a very similar setup to you...
> Networker 7.4.2 on Solaris 10
> DataDomain  690 restorer connected directly to the backup server via 3 x
> 1Gb connections with another 1Gb connection to the WAN for replication
> off-site.
> DD adv_file device is NFS mounted.
> We've been running this for almost a year now and I haven't seen any
> problems with the adv_file device unmounting itself.
>
> The mount command we use takes the form...
> mount –F nfs –o intr,hard,rsize=32768,wsize=32768,proto=tcp,vers=3
> <ddrhostname>:/backup <mount-point>
> and we've done all the recommended tcp/nfs tweaks (let me know if you need
> a list of those).
>
> The one difference I can see from your post is that we don't have Auto
> Media Management enabled on the adv_file device.  I can't find anything to
> back this statement up, but I'm sure I saw something in the dim and distant
> past about not enabling that. You could try turning that off and see if it
> helped?  Is there a particular reason you have that turned on?
>
> Hope this helps...
> Allan.
>
> ________________________________________
> From: EMC NetWorker discussion [NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
> Behalf
> Of Louis Munro [lm AT LOUISMUNRO DOT COM]
> Sent: 11 March 2010 18:32
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: [Networker] Waiting for an already mounted volume
>
> Hello list users,
>
> I'm having some problems with Networker backing-up to adv_file devices on
> my
> brand new DataDomain Storage device.
>
> Every so often (on average once a week) Networker will stop while doing the
> backups and complain about the following (from the daemon log):
>
> nsrd media request critical: Waiting for 1 writable volumes to backup pool
> 'DataDomain UNIX FS' tape or disk
>
> The thing is, the volume is there. It is already mounted and available. We
> have to manually unmount it and then Networker will remount it (since auto
> media management is enabled) and resume the backups.
>
> Is anyone else having that problem?
>
> We are running NetWorker 7.4.5.Build.746 Network Edition on Solaris 10. The
> adv_file is an NFS share exported from a DataDomain NAS. The share is
> automounted on demand (using autofs) and a network problem is not suspected
> at this time (we are able to cd to the adv_file directory when the problem
> occurs).
>
> The storage node is connected directly to the NAS through ethernet (i.e. a
> crossover link).
>
>
>
> Any ideas?
>
> (Apologies for a possible douple posting. It looks like exchange ate my
> first email to the list.)
>
> Louis Munro
>

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

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