Again, answering my own question. I think my issue here was due to accidental overlapping incremental backups.
In a synth policy, having 2 incremental backups that overlap: EG: IMG1 INCR start: 1/20/10 17:01:00 elapsed: 0:56.000 IMG2 INCR start: 1/20/10 17:01:03 elapsed: 0:57.100 The Synth catches a DB error 238 and throws a 671 bpdbm log shows something like this: 14:21:59.969 [4748.3972] <16> synthesize_client_images: Expected to find previous backup system_dc_linux_synth_01_1264208459_INCR.f for image system_dc_linux_synth_01_1264276830_INCR.f, found system_dc_linux_synth_01_1264276827_INCR.f On 1/21/2010 8:46 PM, David Stanaway wrote: > We are seeing quite a few of these on out 6.5.4 w2k8 master/media setup > and can't account for them as the chain of Full/Diff-Incr are good. > > Has anyone else come across these when by all accounts they should have > succeeded? > > NBU support is unfortunately not being very illuminating. > _______________________________________________ > 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