Re: [Veritas-bu] /opt/openv space required during upgrade
I guess I'm a bit confusedwill netbackup convert the old flat catalog into the new "real" database catalog? Will it not need to have roughly the same amount of space for that new catalog as it would for the old catalog? If so, that would mean twice the amount of space I am using now, at least temporarily during the conversion? Or maybe nothing actually gets converted?? I have had to compress this database already (years ago) to fit it into the existing filesystemso I'm compressing catalog entries after 7 days. Scott Chapman Senior Technical Specialist Storage and Database Administration ICBC - Victoria Ph: 250.414.7650 Cell: 250.213.9295 -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2008 9:47 AM To: Chapman, Scott Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] /opt/openv space required during upgrade 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: > Filesystemkbytes usedavail capacity > Mounted on > /dev/vx/dsk/datadg/openv 671843504668417513781740 > 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: > Filesystemkbytes used avail > capacity Mounted on > /dev/vx/dsk/nbu01/catbackupvol6684643243192770 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 224Mpack/NB_CLT_51_4_M 616Kpack/NB_DMP_51_4_M 34M pack/NB_JAV_51_4_M 3.9Mpack/NB_ORA_51_4_M 9.4Mpack/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. This email and any attachments are intended only for the named recipient and may contain confidential and/or privileged material. Any unauthorized copying, dissemination or other use by a person other than the named recipient of this communication is prohibited. If you received this in error or are not named as a recipient, please notify the sender and destroy all copies of this email immediately. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] /opt/openv space required during upgrade
Well that's just a huge relief!! Thanks Justin! Scott Chapman Senior Technical Specialist Storage and Database Administration ICBC - Victoria Ph: 250.414.7650 Cell: 250.213.9295 -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2008 2:35 PM To: Chapman, Scott Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] /opt/openv space required during upgrade On Wed, 23 Jul 2008, Chapman, Scott wrote: > I guess I'm a bit confusedwill netbackup convert the old flat > catalog into the new "real" database catalog? Will it not need to have No, the only thing that is converted into a "real" database catalog is your EMM database (robot and drive definitions/tapes). > roughly the same amount of space for that new catalog as it would for > the old catalog? See above > If so, that would mean twice the amount of space I am > using now, at least temporarily during the conversion? Or maybe nothing > actually gets converted?? Only to the EMM database (small < 100mb) > > I have had to compress this database already (years ago) to fit it into > the existing filesystemso I'm compressing catalog entries after 7 > days. Ok. > > Scott Chapman > Senior Technical Specialist > Storage and Database Administration > ICBC - Victoria > Ph: 250.414.7650 Cell: 250.213.9295 This email and any attachments are intended only for the named recipient and may contain confidential and/or privileged material. Any unauthorized copying, dissemination or other use by a person other than the named recipient of this communication is prohibited. If you received this in error or are not named as a recipient, please notify the sender and destroy all copies of this email immediately. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] /opt/openv space required during upgrade
On Wed, 23 Jul 2008, Chapman, Scott wrote: > I guess I'm a bit confusedwill netbackup convert the old flat > catalog into the new "real" database catalog? Will it not need to have No, the only thing that is converted into a "real" database catalog is your EMM database (robot and drive definitions/tapes). > roughly the same amount of space for that new catalog as it would for > the old catalog? See above > If so, that would mean twice the amount of space I am > using now, at least temporarily during the conversion? Or maybe nothing > actually gets converted?? Only to the EMM database (small < 100mb) > > I have had to compress this database already (years ago) to fit it into > the existing filesystemso I'm compressing catalog entries after 7 > days. Ok. > > Scott Chapman > Senior Technical Specialist > Storage and Database Administration > ICBC - Victoria > Ph: 250.414.7650 Cell: 250.213.9295 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] /opt/openv space required during upgrade
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: > Filesystemkbytes usedavail capacity > Mounted on > /dev/vx/dsk/datadg/openv 671843504668417513781740 > 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: > Filesystemkbytes usedavail > capacity Mounted on > /dev/vx/dsk/nbu01/catbackupvol668464324319277016969019 > 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 224Mpack/NB_CLT_51_4_M 616Kpack/NB_DMP_51_4_M 34M pack/NB_JAV_51_4_M 3.9Mpack/NB_ORA_51_4_M 9.4Mpack/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
