This is actually one thing that annoys me about Symantec/Veritas. Given
the nature of their catalog/database architecture, it certainly lends
itself to lose synchronization. This can directly lead to data loss,
when you have live images on tapes marked as scratch or available.
NBU *does* give you the option to run a consistency check on your own
(bpdbm -consistency 2), however, if your image database is anything but
tiny, most NBU shops won't have enough idle time to run that command to
completion.
So, in order to adequately protect your data, you need to periodically
open up a ticket with Symantec, in order to do this consistency check.
Not only does NBCC need to run while the backup system is idle, but once
you run backups again, the consistency check needs to be run again,
because new backups make changes to the catalog/databases.
Now, assuming that you get a cracker-jack NBU engineer to turn around
your NBCC data quickly, you also must make the appropriate changes
before backups can run again, or else you run into the same issue that I
described above.
Major PITA! Not sure if anything is different in 6.x, as we haven't
eval'd it yet. Hopefuly, the changes that they've made in 6.x have
obviated the need to run these types of consistency checking.
--Steve
Major, Rusty wrote:
> You need to use the Netbackup Catalog Consistency Utility (NBCC),
> found here. It will run against all the databases and create reports.
> It doesn't fix anything itself, but with this info and a case with
> Veritas, you can get it fixed. Note, this only works on 4.5 - 5.1
> environments.
>
> http://seer.entsupport.symantec.com/docs/267965.htm
>
> I'm actually just about to start the utility on one of my environments
> myself.
>
> -Rusty
>
> ------------------------------------------------------------------------
> *From:* veritas-bu-bounces at mailman.eng.auburn.edu
> [mailto:veritas-bu-bounces at mailman.eng.auburn.edu] *On Behalf Of
> *Lewick, Taylor
> *Sent:* Wednesday, August 23, 2006 9:43 AM
> *To:* Wessam Aly; veritas-bu at mailman.eng.auburn.edu
> *Subject:* Re: [Veritas-bu] netbackup DB inconsistency ?
>
> I have a script that reports on media inconsistencies, I know it works
> under 4.5 and 5.1, not sure about 6.0 because we aren't there yet...
>
>
>
> ------------------------------------------------------------------------
>
> *From:* veritas-bu-bounces at mailman.eng.auburn.edu
> [mailto:veritas-bu-bounces at mailman.eng.auburn.edu] *On Behalf Of
> *Wessam Aly
> *Sent:* Wednesday, August 23, 2006 9:17 AM
> *To:* veritas-bu at mailman.eng.auburn.edu
> *Subject:* [Veritas-bu] netbackup DB inconsistency ?
>
>
>
> Hey all,
>
> I have a mind boggling problem, I have a bunch of media which is the
> following:
>
> - when reports run on the pool, it is reported as protected for 1 year
>
> - when i run bpexpdate on any media to expire it immediately, my
> system reports that the media does not exist
>
> - when i run media contents report of any of those media, i get a
> bunch of backup IDs which do not show up in the "client backups" report
>
> - when i run bpexpdate on the backup IDs themselves, i also get that
> no backup ID exists with the ID i listed
>
> - when i try to erase the media, NB says its assigned and cannot be erased
>
> What i am trying to do is delete these media and redefine them (as if
> completely new) without changing their barcode IDs.
>
> Any help will be greatly appreciated.
>
> NB: Is there a utility or something which will fix inconsistencies
> inside the database ? maybe and export/import thing which will
> automatically do a "cleanup" of old/invalid/inconsistent entries ?
>
> Regards,
>
> Wessam Aly
>
> Senior Systems Adminstrator
>
>
> *******
> IMPORTANT
>
> Confidentiality: This e-mail communication and any attachments thereto
> contain information which is confidential and are intended only for
> the use of the individuals or entities named above. If you are not the
> intended recipient, you are hereby notified that any disclosure,
> copying, distribution or the taking any action in reliance on the
> contents of these documents is strictly prohibited and may be illegal.
> Please notify us of your receipt of this e-mail in error and delete
> the e-mail and any copies of it.
>
> Monitoring/Viruses: Mobinil may monitor all incoming & outgoing
> e-mails in line with current legislation. Although we have taken steps
> to ensure that this e-mail and attachments are free from any Virus, we
> advise that in keeping with good computing practice the recipient
> should ensure they are actually virus free.
>
> The Egyptian Company for Mobile Services (Mobinil)
> www.mobinil.com
> *******
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Veritas-bu maillist - Veritas-bu at mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
--
===================================
Steven L. Sesar
Lead Operating Systems Programmer/Analyst
UNIX Application Services R101
The MITRE Corporation
202 Burlington Road - MS K101
Bedford, MA 01730
tel: (781) 271-7702
fax: (781) 271-2600
mobile: (617) 519-8933
email: ssesar at mitre.org
===================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20060823/ac4ff44b/attachment.html
|
