Veritas-bu

Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks

2008-08-06 17:35:57
Subject: Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks
From: "Mark Glazerman" <Mark.Glazerman AT spartech DOT com>
To: <bob944 AT attglobal DOT net>, <veritas-bu AT mailman.eng.auburn DOT edu>
Date: Wed, 6 Aug 2008 16:20:10 -0500
Fixed !!...

Symantec have outdone themselves (strange to say I know !!).  Engineering 
created two binaries to replace the bpbkar and bpmount files in 
/usr/openv/netbackup/bin.  Once this was done I was able to successfully backup 
ZFS filesystems on my test box with ALL_LOCAL_DRIVES as the only backup 
selection.  No need to specify all the possible zfs filesystems on all clients 
in the policy as I had been doing.  The real test will come tonight when the 
policy will try and kick off proper but I'm confident that they've fixed our 
issue without the need for upgrading everything to 6.5.2 !!

Anyone who's had similar issues is advised (by engineering) to contact support 
and to reference technote 303000 
(http://seer.entsupport.symantec.com/docs/303000.htm) and ask to be sent the 
engineering binaries that ARE available.  The binaries appear to work on both 
6.5 and 6.5.1 clients (at least they are on our systems).

Just thought I'd update everyone on a successful resolution to a very annoying 
issue.

Mark Glazerman
Desk: 314-889-8282
Cell: 618-520-3401
 please don't print this e-mail unless you really need to

-----Original Message-----
From: bob944 [mailto:bob944 AT attglobal DOT net] 
Sent: Monday, August 04, 2008 3:02 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Cc: Mark Glazerman
Subject: RE: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks

> I didn't say that Exclude lists don't work for directories.  
> I said that Include lists don't work for directories.  [...]

No.  Include lists work exactly the same way as exclude lists;
directories and/or files are valid.  Reference the Veritas NetBackup
System Administrator's Guide, Vol I for syntax rules.

This misunderstanding might be attributed to way the *_list rules are
applied.  Note that an exclude list can only exclude items that are in
the policy's selection list (obviously).  And that an include list can
only include items that were excluded by an exclude list.  (Perhaps
that's the logic in Symantec renaming the include list to "exceptions to
the exclude list.")  Stated another way, the selection list defines the
universe of data to be backed up.  Excludes subtract from the universe.
Includes reinstate only items from the set of excluded items.

You can see the processing steps in the client's bpbkar log.  Logging
level 0 will show each directive as it is encountered; level 1 and
higher will show the process more clearly via the PrintFile lines.  From
that I can infer the reason the rules are as they are (above):  bpbkar
processes the selection list and only mentions exclude_list items when
they match its current path; include_list entries are only mentioned
when they match the current exclude_list item.

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu