Hi.

No message was displayed during the upgrades that I have done regarding
space. That could be due to enough space available for any temp procedures,
but after the upgrades, no increase is size was noticed.

If any conversion is done on the existing images, it is not visible (it may
be a background process).

What I did see during the nbpushdata command running was that it was
accesing Media manager info (tapes, devices etc) , so I think it safe to say
that EMM only collect very small amounts of data. 

Jim

-----Original Message-----
From: WEAVER, Simon [mailto:simon.weaver AT astrium.eads DOT net] 
Sent: Tuesday, May 16, 2006 9:11 AM
To: 'Jim Peppas'; bob944 AT attglobal DOT net; veritas-bu AT mailman.eng.auburn 
DOT edu
Subject: RE: [Veritas-bu] NBU 6.0 catalog size vs 5.1 catalog size


Jim
Can you clarify something for me - did you NEED additional disk space for
the nbpushdata command? IE: say my DB is 30GB in size, do you need that same
sort of spare space on disk??

Answers on a postcard to....


Regards

Simon Weaver
3rd Line Technical Support
Windows Domain Administrator 

EADS Astrium Limited, B32AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email: Simon.Weaver AT Astrium-eads DOT net



-----Original Message-----
From: Jim Peppas [mailto:perf AT peppas DOT gr]
Sent: 14 May 2006 21:15
To: bob944 AT attglobal DOT net; veritas-bu AT mailman.eng.auburn DOT edu; 
WEAVER, Simon
Subject: RE: [Veritas-bu] NBU 6.0 catalog size vs 5.1 catalog size


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

This email is for the intended addressee only.
If you have received it in error then you must not use, retain, disseminate
or otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of EADS
Astrium Limited.
Nothing in this email shall bind EADS Astrium Limited in any contract or
obligation.

EADS Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS,
England