Veritas InfoScale™ Operations Manager 7.3.1 Add-ons User's Guide
- Section I. VCS Utilities Add-on 7.3.1
- Section II. Distribution Manager Add-on 7.3.1
- Section III. Fabric Insight Add-on 7.3.1
- Section IV. Patch Installer Add-on 7.3.1
- Introduction to Patch Installer Add-on
- Using Patch Installer Add-on
- Section V. Storage Insight Add-on 7.3.1
- Performing the deep discovery of enclosures
- About Storage Insight Add-on
- Adding HITACHI storage enclosures for deep discovery
- Editing the deep discovery configuration for an enclosure
- Monitoring the usage of thin pools
- Monitoring storage array metering data
- Managing LUN classifications
- Appendix A. Enclosure configuration prerequisites
- HITACHI enclosure configuration prerequisites
- EMC Symmetrix storage array configuration prerequisites
- Device setup requirements for EMC Symmetrix arrays
- IBM XIV enclosure configuration prerequisites
- NetApp storage enclosure configuration prerequisites
- EMC CLARiiON storage enclosures configuration prerequisites
- Hewlett-Packard Enterprise Virtual Array (HP EVA) configuration prerequisites
- IBM System Storage DS enclosure configuration prerequisites
- IBM SVC enclosure configuration prerequisites
- EMC Celerra enclosure configuration prerequisites
- EMC VNX storage enclosure configuration prerequisites
- EMC VPLEX storage enclosure configuration prerequisites
- Appendix B. Commands used by Management Server for deep discovery of enclosures
- Performing the deep discovery of enclosures
- Section VI. Storage Insight SDK Add-on 7.3.1
- Overview of Storage Insight SDK Add-on 7.3.1
- Managing Veritas InfoScale Operations Manager Storage Insight plug-ins
- About creating Storage Insight plug-in
- About discovery script
- About the enclosure discovery command output
- Creating a Storage Insight plug-in
- Editing a Storage Insight plug-in
- Testing a Storage Insight plug-in
- About creating Storage Insight plug-in
- Section VII. Storage Provisioning and Enclosure Migration Add-on 7.3.1
- Provisioning storage
- Creating a storage template using VxFS file systems
- Migrating volumes
- Provisioning storage
- Section VIII. Veritas HA Plug-in for VMware vSphere Web Client
- Introduction to Veritas HA Plug-in for vSphere Web Client
- Installation and uninstallation of Veritas HA Plug-in for vSphere Web Client
- Configurations for Veritas HA Plug-in for vSphere Web Client
- Section IX. Application Migration Add-on
- Introduction to Application Migration Add-on
- Creating and managing an application migration plan
- Understanding application migration operations
Understanding the cleanup operation
Cleanup operation is an internal operation which takes place whenever a critical task fails in an operation. This operation takes care of cleaning up the managed hosts to ensure the system is in a clean and known state so that the operation can be performed again after taking corrective measures.
The status or the progress of this operation is not displayed in the user interface. To view the status of this operation, check the logs available in the managed hosts.
Setup Storage - If you had selected the
option in the wizard, mirror is removed for all volumes between source and target disk groups. Mirror disk groups are deleted.Rehearse and Migrate - All volumes of the mirror disk groups are reattached with the corresponding volumes in the source disk group. If the plan created the target cluster configuration, the configuration is backed up and then removed.
Setup Storage - Cleanup is performed only for disk groups marked as Create New. For these disk groups, replication is stopped (if established), secondary site is deleted and primary RVG is removed if the RVG was created by the plan. Disk groups created on the target cluster by the plan is also removed.
Rehearse - Snapshots created for volumes are removed from the secondary. Cache object and cache volume are deleted. VCS resources for disk groups, IPs, etc. are restored. If the plan created the target cluster configuration, the configuration is backed up and then removed.
Migrate - Replication, if stopped, is started again. If the plan created the target cluster configuration, the configuration is backed up and then removed.