NAS mounted filesystems with linux and win proxy servers

[C_J_Hund]

Hi all,

Is there anything special you need to do to backup NAS mounted shares on a linux server?  I have the policy set up to follow nfs shares.  However, when I run a full backup it doesn't look like I'm picking up these mounted shares.  I don't see those mounted filespace names show up in the output to either the check_coverage or bplist commands. 

I've tried backing up one of the NAS mounted shares as follows:
bpbackup -s Full -p <my policy> -L <my share name> > log

And what I see coming from the log of that command is:
13:19:01 Initiating backup
13:19:02 INF - Server status = 241

Sincere thanks,
C.J.

[scorpy_582]

Hi CJ,

Mount the filesystem with -o nolock option.

mount -t nfs -o nolock <servername>:<share> <mountpoint>

i have seen it solving the problem in the past.
 

[C_J_Hund]

Very helpful, thank you.  What would be the problem is this were a Windows client? 

[Darren_Dunham]

You don't mention the contents of the backup selections on the policy.  Have you placed the mountpoints in there?  You can't use / or ALL_LOCAL_FILES and grab the external servers, even with "Follow NFS" checked.

Exit Status Code 241: the specified schedule is the wrong type for this request

What is the "policy type" for the policy, and what are the schedule types for the schedule(s) that you have associated with the policy?

--
Darren

[C_J_Hund]

Thanks, Darren.  I hadn't added any of these mounted shares to the backup selections page on the policy.  Is that my problem?  I was told all I needed to do was just check that "Follow NFS" button.  

The policy is of type "standard".  I have two schedules, a "Full Backup" and a "Differential Incremental Backup".

Thanks,
C.J.

[Darren_Dunham]

Follow NFS

Note  The Follow NFS attribute applies only to UNIX clients in certain policy types.  NetBackup allows selecting it only in those instances.

The Follow NFS attribute specifies that you want NetBackup to back up or archive any NFS mounted files that are named in the backup selection list, or by the user in the case of a user backup or archive.  Clear the box to prevent the back up or archive of NFS mounted files.
-------
By not placing them in the include list, that would explain them not being backed up.  But I don't think that explains the code 241.  Do you get that after naming the mount point?  Your schedules seem normal, so I'm not sure what's up with that status exit.

--
Darren

[C_J_Hund]

I believe after pulling those NAS attached shares into my backup selections that I'm finally backing them up.  I see these shares being backed up in a test full.

I have the same issue on a win box.  I have a cifs attached NAS share which I mounted on the Z: drive.  I have the "backup network drives" button checked for this Win policy and I have the share name specified in the backup selections like, "Z:\<share name".  Still, it looks like my test backups skip right over it.  What's also interesting here is that when I try to back up that share manually on the client, I don't see the Z: drive show up in my list of available drives to back up.  It is mounted, though. 

Do you know what I might have missed here?

Sincere thanks,
C.J.