We periodically get the 227 error and that is often accompanied by an entry in the problem report (search for the master server having the issue) which implies that the catalog policy has exceeded it's maximum number of configured attempts. This will just randomly occur and after that point it won't run a scheduled backup but will let me submit manual catalog backups. It notmally only complains about 1 schedule inside the catalog policy (We have a night and day schedule within the catalog policy).
Our fix for this requires the catalog policy to be deleted and then cycling of all the NBU services. Once NBU is back up create a new catalog policy and normally things are fine again. We found that this would normally coincide with our master server getting beat up with regard to CPU and memory so we now have a script which restarts the NBU services on a weekly basis to clear out any old or lingering NBU processes which might be hanging onto resources. Hope this is somewhat helpful. 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marianne Van Den Berg Sent: Monday, December 01, 2008 3:16 AM To: Justin Piszcz Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NBU6.5.2a Solaris 10 Hot Catalog backup failing Looks like we have a resource problem - cpu utilization on master sitting at 100% all the time. Might be a combination of VBR data collection on master and 6.5.2 being more resource intensive... Anybody with similar experience? Regards M. -----Original Message----- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: 29 November 2008 23:50 To: Marianne Van Den Berg Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] NBU6.5.2a Solaris 10 Hot Catalog backup failing On Sat, 29 Nov 2008, Marianne Van Den Berg wrote: > Nope - no entries in critical section. > Catalog backups have been working fine after 6.5.2 upgrade (about 3 > weeks ago); been failing last 4 days. > > -----Original Message----- > From: Justin Piszcz [mailto:[EMAIL PROTECTED] > Sent: 29 November 2008 19:26 > To: Marianne Van Den Berg > Cc: VERITAS-BU@mailman.eng.auburn.edu > Subject: Re: [Veritas-bu] NBU6.5.2a Solaris 10 Hot Catalog backup > failing > > > > On Sat, 29 Nov 2008, Marianne Van Den Berg wrote: > >> Hi All >> >> >> >> Clustered NBU 6.5.2a master server (with EEB's) on Solaris 10. >> Tcp_fusion disabled. >> >> >> >> Hot Catalog backups (the last stream backing up the images and the >> parent) have been failing for a couple of days now with all sorts of >> errors - 50, 41, 25, 227. >> >> >> >> This particular stream failed with 41 after backing up 41Gb: >> >> Error bpbrm (pid=26181) db_FLISTsend failed: network connection timed >> out (41). >> >> Master server is doing network backup to media server (also on > 6.5.2). >> >> >> >> Has anybody seen this? Ideas? Advise? > > Do you have policies in the critical section of the catalog backup > policy? > > Justin. > > Next step I would perform is to verify your catalog (bpdbm) check consistency 2 and look for any bad images. Justin. _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu