All, We're running a single solaris 9 server, with NBU 6.5 (yes, still).
My catalog backups recently started reporting really large numbers of kilobytes. In the example below, the last of the comma delimited output is the kbytes field. That same number appears in the GUI: # bpdbjobs -most_columns | cut -d, -f1,2,4,15 | egrep "\,6\," | more 2572429,6,0,18014398509281312 <==========(whoa) <snip> While these values are more consistent to what we're used to seeing: 2553923,6,0,566784 2553897,6,0,568096 2553703,6,0,572768 2553364,6,0,672736 2553043,6,0,568768 2552540,6,0,560480 2552272,6,0,559040 2552217,6,0,559744 2552009,6,0,563936 For clarity, the fields in the examples here are backupid, type (6=catalog), status, kbytes. Even with the seemingly wacky kb numbers now being reported, the status remains a constant "0", successfully completed. This a pretty static environment. Anyone know what the deal is? Thanks, Ron
_______________________________________________ Veritas-bu maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
