Just out of curiosity but what version of server / client are you running ....

Does the networker client automatically pick up the EXT4 file system (are the 
other file systems on the client EXT4)

I don't have a linux box to test this on, but if you did a catch-all backup 
that specified the files system types  ... does it pick it up automatically ie 
instead of using ALL for the saveset try 
        All-ext3
        All-ext4 
        ... and any other filesystem type you might have, I have come across 
all-zfs, all-ufs, all-lofs, all-ntfs  - has anyone seen a definitive list of 
valid files system types?


Mat


-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Tim Mooney
Sent: Thursday, 7 February 2013 9:30 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] savepnpc that alters the list of filesystems?

In regard to: Re: [Networker] savepnpc that alters the list of...:

> NetWorker gets the list of file systems from /etc/fstab on Linux 
> systems when the backup begins (precmd). In order to accomplish what 
> you want, you need to explicitly list out the file systems in the 
> client resource rather than using "All."

I actually misspoke in my earlier description.  The snapshot mount is actually 
*always* present in /etc/fstab:

/dev/sanvg2/bbcontent_snap      /bbsnap  ext4 defaults,noatime,noauto 1 2

The savepnpc precmd is *not* adding that.  It's just generating the snapshot 
and mounting it on /bbsnap.  The savepncp postcmd unmounts it and removes the 
snapshot, but leaves the entry in /etc/fstab.

We did it that way because we thought that would make it easier with NetWorker, 
but as we discovered, the "All" saveset still is not including /bbsnap among 
the list.

We're guessing that's either happening because of the ",noauto" on the mount 
options, which is pretty much required for this scenario, or because the client 
may actually be looking at /proc/mounts too and discovering that even though 
there's an ext4 filesystem mentioned in /etc/fstab, it's not (yet) mounted on 
/bbsnap.

Tim

> On Feb 6, 2013, at 3:58 PM, Tim Mooney <Tim.Mooney AT NDSU DOT EDU>
> wrote:
>
>> All-
>>
>> NetWorker server: NetWorker 7.6.2.5 on RHEL 6.3 x86_64 NetWorker 
>> client: NetWorker 7.6.2.5 on RHEL 5.9 x86_64
>>
>> Does anyone know when, during the save process, the list of 
>> filesystems to back up is set?  In particular, does it happen 
>> *before* the precmd in a savepnpc script?
>>
>> I ask because we're trying to use a savepnpc precmd script to 
>> snapshot a Linux LVM volume and then mount the snapshot in a new 
>> place and have NetWorker back up the snapshot.  We are using the 
>> "All" saveset for the client.  So far, NetWorker hasn't even noticed 
>> that the new snapshot filesystem is available for backup, so I'm 
>> concerned that it may be setting the list of volumes to back up *before* the 
>> precmd runs.
>>
>> Note that the precmd is doing the snapshot, mounting the volume, and 
>> updating /etc/fstab with the entry for the new mounted volume.
>>
>> Any thoughts on whether this should work?
>>
>> Tim
>> --
>> Tim Mooney                                             Tim.Mooney AT ndsu 
>> DOT edu
>> Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
>> Room 242-J6, IACC Building                             701-231-8541 (Fax)
>> North Dakota State University, Fargo, ND 58105-5164
>

-- 
Tim Mooney                                             Tim.Mooney AT ndsu DOT 
edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, IACC Building                             701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
********************************* DISCLAIMER *********************************
The information contained in the above e-mail message or messages (which 
includes any attachments) is confidential and may be legally privileged. It is 
intended only for the use of the person or entity to which it is addressed. If 
you are not the addressee any form of disclosure, copying, modification, 
distribution or any action taken or omitted in reliance on the information is 
unauthorised. Opinions contained in the message(s) do not necessarily reflect 
the opinions of the Queensland Government and its authorities. If you received 
this communication in error, please notify the sender immediately and delete it 
from your computer system network.