Upgradd 5.1 to 6.0mp4 with large DB - Advice Pls 1

[AnotherAlan]

Hi All,
NBU 5.1
Solaris 9
I am about to embark on an upgrade of a production backup environment from 5.1 to 6.0mp4, consisting of one master and one media server.
I have done this in the past on a test system without too many problems, however I am seeking advice on this as my database for this system is 115gb in size.
I am considering the impact or implications of compressing the catalog prior to doing the upgrade.
Does anyone have any experience of upgrading with this compression or any other gotchas I should look out for.
All help / advice appreciated.

Many Thanks
Al

 

[dukbtr]

We upgraded last year from 5.1 to 6.0 MP4 and compression on our catalog didn't make a difference in the upgrade, granted ours is only 50gig.

The biggest peace of advice I have is if you have Tech Support w/ Symantec use them. I called before the upgrade and told them that we were upgrading and want there help in running consistency checks on the catalog, globdb, vm.conf, bp.conf, etc. This helped weed out a lot of gotchas before we even started.

 

[AnotherAlan]

Thanks for the reply.
I actually performed the upgrade today without any problems or issues.

Now lets wait for 6.5.

Cheers

 

[AnotherAlan]

Well that statement turned out to be false.

It appears that I have hit an issue with Veritas Cluster alias names not being recognised and resolved correctly.
Although everything looks ok with bp.conf, dns, bpclntcmd, telnetting to bpcd and vnetd, hosts files, nsswitch.conf and such like, my backup is failing with error 48.

I've been through the troubleshooting doc and Veritas support. Neither of which were any good (surprise!)

Strange thing is that I have other Veritas clusters who have not experienced this problem after the upgrade.

Pointing to the active node works, pointing to the passive node works, pointing to the alias doesn't.
Changing the client name in bp.conf (on the off chance) doesn't work.

And so it goes on...

 

[AnotherAlan]

Forgot to mention...I can complete a restore from the alias name...just not start a backup....