Hi All.

I have done some upgrades from 5 to 6 and have not seen a noticable change
in the Image database. My databases were small but I don't think that you
should have  a problem there.

As far as the logging is concerned, there is much more control of the
logging per process. Logging levels for bpsched are no longer present
because it not there any longer.

Regards,

Jim Peppas

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of bob944
Sent: Saturday, April 29, 2006 9:23 PM
To: veritas-bu AT mailman.eng.auburn DOT edu; 'WEAVER, Simon'
Subject: RE: [Veritas-bu] NBU 6.0 catalog size vs 5.1 catalog size

> I asked a question similar to this, in regards to whether NBPUSHDATA 
> needs more disk space, but I am still not entirely sure.
>  
> The response Jim made indicated, that Netbackup leaves the current DB 
> intact and perhaps creates a new DB - but surely this means more disk 
> space.

nbpushdata doesn't need more space unless you have a _lot_ of media and
devices--enough to grow the Sybase DB.  pushdata loads the 5.x flat-file
media manager information into the relational database which has been
present since NBU 6 installation time.  IIRC, the relational DB starts out
at 25MB or so.

NBU 6 installation needed more space to start with (check the Installation
Guide for specific per-platform requirements).  This part is trivial.  Do be
aware that backups of the relational DB, by default, are staged to a staging
directory within the NetBackup structure--so either symlink that somewhere
else or allow for the space at hot-backup time.

As another poster mentioned, the new unified logging is very space-hungry.


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu