Hi Justin. Regarding the "229" error that you are getting, are you
performing file level backups (snapshot method 0), vmdk backups
(snapshot method 1 or 2), or are your performing vmdk full and file
level incrementals (snapshot method 3)?
-George Winter
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Justin
King
Sent: Thursday, February 05, 2009 4:04 PM
To: nbu
Subject: [Veritas-bu] NOM & VCB
2 questions:
1. Is anyone using NOM that can give feedback on its value as a
reporting tool?
I have a 'simple' environment (without the Authorization & Authenication
extensions), and when I tried to install them, I ended up screwing
things up so badly that I had to recover the NBDB/EMM database from a
previous day. I think I know what not to do next time, but I have about
10-12 media servers (Win/Linux mix) and would prefer to not install
VxSAT/Az on each.
2. I'm using 6.5.3 throughout the environment and just started doing VCB
backups. For the most part, they seemed to be working okay; however,
all of the sudden without anything knowingly changing, I'm getting
'event out of sequence - image inconsistency (229)' error. No idea
what's going on, and the docs say to change from FlashBackup to WinNT
policy type to 'correct'. That's a poor workaround, IMHO. Anyone seen
this and been able to overcome?
Thanks much in advance-
Justin King
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
