CM6 to CM6.0.1 Upgrade

[glimma]

Hi All,

I'm trying to upgrade CM6 to CM6.0.1 on a S8300D using System Platform.

I currently have CM 6.0 running patch 18856, installed on System Platform 6.0.3.

From the System Platform Home Page, I click on Virtual Machine Management, followed by Solution Template.
I hightlight the SP CD/DVD and click on Upgrade. I then select the CM_onlyEmbed.ovf, the page then shows the upgrade details and I then press upgrade.

It then seems to go through all the upgrade tasks, but fails everytime on the Restore VM Data.

If I look in the backup log it shows
2013-03-14 11:26:46,211|RESTORE Starting restore --------------------------------------------------------------
2013-03-14 11:26:46,338|RESTORE Arguments: -d vm-data -f upgrade-backup.tgz -n -u -v cm,utility_server
2013-03-14 11:26:46,338|RESTORE Archive set to /vspdata/backup/archive/upgrade-backup.tgz
2013-03-14 11:29:30,045|RESTORE executing pre_restore.sh for cm with dataset version 1
2013-03-14 11:29:30,046|sleep pid is 17852
2013-03-14 11:29:30,046|./vm-data/pre_restore.sh pid is 17853
2013-03-14 11:29:30,129|+ exit 0
2013-03-14 11:29:30,130|17853 finished
2013-03-14 11:29:30,131|kill -- -17852
2013-03-14 11:29:30,150|RESTORE vm-data/pre_restore.sh - Successful
2013-03-14 11:29:30,205|RESTORE executing pre_restore.sh for utility_server with dataset version 1
2013-03-14 11:29:30,254|sleep pid is 17863
2013-03-14 11:29:30,276|+ exit 0
2013-03-14 11:29:30,278|./vm-data/pre_restore.sh pid is 17865
2013-03-14 11:29:30,287|17865 finished
2013-03-14 11:29:30,287|kill -- -17863
2013-03-14 11:29:30,288|RESTORE vm-data/pre_restore.sh - Successful
2013-03-14 11:29:30,315|RESTORE executing restore.sh for cm with dataset version 1
2013-03-14 11:29:30,328|sleep pid is 17869
2013-03-14 11:29:30,369|./vm-data/restore.sh pid is 17870
2013-03-14 11:29:30,454|+ export VSP_RESTORE_DIRECTORY=/tmp/tmp.Aerog14042/upgrade-backup/vm-data/cm
2013-03-14 11:29:30,542|+ VSP_RESTORE_DIRECTORY=/tmp/tmp.Aerog14042/upgrade-backup/vm-data/cm
2013-03-14 11:29:30,543|+ [[ cm = _* ]]
2013-03-14 11:29:30,543|+ plugin_dir='/vspdata/template/*/systems/cm/plugins/restore'
2013-03-14 11:29:30,543|+ cd /vspdata/template/CM_onlyEmbed/systems/cm/plugins/restore
2013-03-14 11:29:30,543|+ chmod 755 .
2013-03-14 11:29:30,544|+ chmod +x .restore
2013-03-14 11:29:30,544|+ runuser -G vsplog vspvm -- ./.restore -d /tmp/tmp.Aerog14042/upgrade-backup/vm-data/cm
2013-03-14 11:29:30,544|+ /opt/avaya/vsp/util/logger.py -f /opt/avaya/vsp/backup/scripts/log-vm.conf
2013-03-14 11:35:45,883|17870 finished
2013-03-14 11:35:45,883|kill -- -17869
2013-03-14 11:35:45,884|RESTORE vm-data/restore.sh - Failed with exit code 5
2013-03-14 11:35:46,013|RESTORE ****** FAILED ******

The upgrade process then rolls back to the current CM template.

Does the upgrade facility work, or I'm I better backing up CM and then removing the exiting CM template and then installing CM6.0.1?

Thanks

 

[manofdos]

I've ran into this before. Make sure to read the release notes on the system platform versions and Patches. Everything has to be on a supported level for the upgrade to work. I'd patch system platform to 6.0393 and try the upgrade again.

CM 6.2 is out now as well and may be the better option all the way around.

Just upgrade System platform to 6.22 and then upgrade CM to 6.2 and install service pack 5. That is the most current release available.