Domink,
The problem with exclude lists is that if you start having a
different exclude list for each server, it quickly becomes a nightmare keeping
those lists current and up to date. Also, because ALL_LOCAL_DRIVES
doesn’t recognize the ZFS filesystems, the only way to have them included
was to start listing the mountpoints in the backup selections tab of the
policy. We tried looking at include lists also but those only work for
individual files, not whole directories.
This brought us to our workaround where we had to specify every
possible zfs mountpoint in the backup policy and then make sure that each of
those directories existed on every server (to avoid the 71’s). That
has worked like a charm over the weekend so will have to do until there is a
release of NBU which includes ZFS under the ALL_LOCAL_DRIVES backup selection
Thanks
Mark Glazerman
Desk: 314-889-8282
Cell: 618-520-3401
P please don't print this e-mail unless you really need to
From: Dominik.X.Pietrzykowski AT nab.com DOT au
[mailto:Dominik.X.Pietrzykowski AT nab.com DOT au]
Sent: Monday, August 04, 2008 1:17 AM
To: Mark Glazerman
Subject: Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks
You couldn't
use exclude lists ???
Incase anyone
is considering implementing any ZFS in their environment which they want to
back up using NetBackup we found out yesterday that ALL_LOCAL_DRIVES as the
backup selection does NOT cover ZFS filesystems.
We have a
number of Sun boxes which have various test and development oracle instances
which are housed inside ZFS file systems. We blew away one of these test
instances the other day (after doing a full OS backup and the required RMAN
backups) but when we went to restore the data from the ZFS filesystems, NBU
didn’t have anything under the uppermost directory. A quick check
of other systems with ZFS showed the same issue.We spent the better part of 2
days playing around with the include_list’s and exclude_list’s but
nothing worked.
In order to
backup ZFS file systems you must explicitly add the ZFS directories into the
backup selections of the backup policy. This “fix” was also
confirmed by Symantec support who were also happy to tell me that ZFS
isn’t officially supported by NBU yet.
This on its
own should work great if you have a single policy backing up a single server
with all it’s ZFS under the same parent directory. However, if like
us, you have a backup policy which backs up multiple servers, each with their
own uniquely named ZFS file systems, you need to get a bit creative.
The policy in
question backs up 15 Sun boxes with a total of 6 differently named ZFS
file systems spread amongst them. If you just list the file systems in
the backup selections, NBU looks for each of those different filesystems on
each server and spits out an error code 71 (None of the files in the file list
exist) for every directory it can’t find. The only way we could
work out to avoid these errors (and there were a lot of them) was to create every
missing directory on every server and then touch a tiny file inside each of
these directories. Now when the policy runs, it sees each directory (as
listed in the backup selection) on each server and doesn’t moan about
anything. Perhaps not the neatest of fixes but it works.
Apologies for
the wordy post, just thought I’d put this info out there in case anyone
else is moving towards ZFS.
Mark
Glazerman
Enterprise
Storage Administrator
Spartech
Corporation
Desk:
314-889-8282
Fax:
314-854-8282
Cell:
618-520-3401
mark.glazerman AT spartech DOT com
http://www.spartech.com
P please
don't print this e-mail unless you really need to
This e-mail and any files transmitted with it
are confidential, are intended solely for the use of the addressee, and may be
legally privileged. If you have received this email in error please notify the
sender immediately, and do not copy or forward it.
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
National Australia Bank Ltd - ABN 12 004 044 937
This email may contain confidential information. If you are not the intended
recipient, please immediately notify us at postmaster AT nab.com DOT au or by replying to
the sender, and then destroy all copies of this email. Except where this email
indicates otherwise, views expressed in this email are those of the sender and
not of National Australia Bank Ltd. Advice in this email does not take account
of your objectives, financial situation, or needs. It is important for you to consider
these matters and, if the e-mail refers to a product(s), you should read the
relevant Product Disclosure Statement(s)/other disclosure document(s) before
making any decisions. If you do not want email marketing from us in future,
forward this email with "unsubscribe" in the subject line to Unsubscriptions AT nab.com DOT au in
order to stop marketing emails from this sender. National Australia Bank Ltd
does not represent that this email is free of errors, viruses or interference.
=