On Wed, 23 Jul 2008, Chapman, Scott wrote:
> OK, so I'm upgrading my final two master servers from 5.0 to 6.0. > > One of these machines has the following /opt/openv filesystem: > Filesystem kbytes used avail capacity > Mounted on > /dev/vx/dsk/datadg/openv 67184350 46684175 13781740 > 78% /opt/openv > > Now I backup the catalog to two locations, one is tape and the other is > disk, and that disk filesystem looks like: > Filesystem kbytes used avail > capacity Mounted on > /dev/vx/dsk/nbu01/catbackupvol 66846432 43192770 16969019 > 72% /catbackup > > So from this you can see that the catalog is big and that the /opt/openv > isn't just full of logs, binaries, patches, etc. So, my question is > will I run out of space during my upgrade from 5 to 6? When netbackup > converts the catalog from the current format to the new format, will it > need temp space? Will the upgrade blow up because I only have 13gig of > space left?? That is a good question, you probably will be OK, you may want to open a case with Symantec to confirm. You could also compress the catalog but would not recommend doing that unless you absolutely needed to.. The size of the old binaries that are kept during the upgrades: $ sudo du -sh pack/*51* 27M pack/NB_51_4_M 224M pack/NB_CLT_51_4_M 616K pack/NB_DMP_51_4_M 34M pack/NB_JAV_51_4_M 3.9M pack/NB_ORA_51_4_M 9.4M pack/NB_VLT_51_4_M Then you have your EMM database: $ sudo du -sh /usr/openv/db/data/ 65M /usr/openv/db/data $ ls /usr/openv/db/data/ EMM_DATA.db EMM_INDEX.db NBDB.db NBDB.log vxdbms.conf I think you'll be ok, just remember to turn off cold backups and switch to hot backups (w/proper policy when going to 6, and are you going to 6.0MP6 or 6.5.2(a)?) Justin. _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu