7.6.1 is a GA release and requires you to go through the portal for Symantec FileConnect
This requires a serial number.
This is to inform you that we had tried to upgrade our Ops Center from v220.127.116.11 to v7.6.1 but it didn't go well.
We were able to take the backup of the DB using the script and it was sucessfull.
We did the defrag of the DB using the inbuilt script and it was sucessfull too.
We started the install script and we got the message that DB upgrade is in progress and it will take some time.
Our DB size is approx 17GB..we waited for almost 12-14 hours but upgrade process was still the same, we contacted the Support and they told us that we need to cancel the upgrade as this should not have taken that much of time and we cancelled the upgrade and did the restore from the backup that we had taken earlier and opscenter was operational again on old version v18.104.22.168.
That is odd, I have certainly seen it take longer. It all ends up depending on your hardware.
What are the specs of your Opscenter server's hardware?
In 7.6 release guides (see below), it's better to stop using SPARC T2 series from master server (or anything using Sybase SQL, that would mean including OpsCenter)
Sybase SQL Anywhere performance is poor using SPARC T-series processor versions older than T4-4. Symantec recommends that you do not run your master server on this type of hardware.
Note: NetBackup uses the Sybase SQL Anywhere database server internally to store the NetBackup configuration data and backup image headers that run on the master server.
In addition, continued support for OpsCenter on Solaris is going away.
OpsCenter 7.7 does not support Solaris Sparc and Solaris x86 platforms.
■ OpsCenter 7.7 Agent is not supported on Solaris platform.
■ OpsCenter 7.7 does not support clustering on Solaris platform.
■ OpsCenter 7.7 does not support Language Packs (LP) on Solaris platform
If you have any questions, please let us know.