Problem Symptom
The backup package of the NMA component is lost. As a result, the upgrade is suspended.
Problem Diagnosis
1. Use SSH to log in to the node on which the upgrade is suspended as user fsadmin.
2. Run the su - root command to switch to user root.
3. Run the find /opt/dfv/oam/oam-u/backup/nma/upgrade_info/ -name nma_`cat /opt/dfv/oam/oam-u/nma/version |grep nma|awk '{print $2}'`.tar.gz command to check whether the backup package of the NMA component exists.
Causes
During the last upgrade, the NMA backup package has not been stored onto disks. As a result, such NMA backup package fails to be found for the current pre-upgrade check.
Solution
Use SSH to log in to the node on which the upgrade is suspended as user fsadmin.
Run the su - root command to switch to user root.
Run the cd /opt/fusionstorage/repository/deploymanager_pkg/micro command to go to the directory.
Run the tar zcf /opt/dfv/oam/oam-u/backup/nma/upgrade_info/nma_`cat /opt/dfv/oam/oam-u/nma/version |grep nma|awk '{print $2}'`.tar.gz nma_`cat /opt/dfv/oam/oam-u/nma/version |grep nma|awk '{print $2}'` command to restore the lost backup package.
On DeviceManager, click Continue to continue the upgrade.
Check After Recovery
N/A
Suggestion and Summary
N/A
Applicable Versions
All
