Detaching and removing plexes that have been incorrectly configured by interrupting a storage migration task that was initiated from VOM (Veritas Operations manager)
Article ID: 100026872
Updated On:
Cause
The migration process was interrupted when the VOM managed host (MH) lost connectivity with the VOM central management server (MS).
Resolution
1. Determine which MHs have outstanding migration tasks that have not completed. This can be done using the VOM GUI.
2. From the MH, run these commands:
# cd /opt/VRTSsfmh/bin
# ./vxtemplate list jobs (to show outstanding jobs)
# ./vxtemplate purge -a (to purge jobs from queue)
Note: If jobs are left that will not purge (for example, the WAITING jobs), remove /var/opt/VRTSsfmh/tasks.json.
3. Remove the plexes.
# vxprint -htg
# vxplex -g
Note: The plex should now show DISABLED.
# vxedit -g
4. Use vxprint to check that plex was removed:
# vxprint -htg
Issue/Introduction
The VOM User Interface view of the migration process for volumes, for managed hosts, show some volumes in WAITING or PENDING.
Was this article helpful?
Yes
No
Powered by
