Users Guide

behavior when a service is deleted is to retain the storage volume available to make sure no critical data is
deleted.
As a best practice, you need to perform the following tasks while decommissioning a service. Make sure
to perform these tasks to avoid issues in provisioning of future services due to conflicts.
Decommissioning Hyper-V based storage, host, and clusters
To decommission Hyper-V based storage, host, and clusters:
1. SCVMM clusters should be uninstalled through SCVMM.
2. SCVMM host groups should be deleted if no longer used.
3. Hyper-V hosts should be removed from SCVMM.
4. Hyper-V hosts should be removed from the domain.
5. Storage volumes should be set offline and deleted when the data is no longer used.
6. If required, remove ASM provisioned VLANs from the host facing ports of the switch.
7. Remove host entries from DNS server.
Decommissioning VMware based storage, host, and clusters
To decommission VMware based storage, host, and clusters:
1. Delete unused clusters from VMware vCenter.
2. Delete unused data centers from VMware vCenter.
3. Remove hosts from VMware vCenter.
4. Storage volumes should be set offline and deleted when the data is no longer used.
5. If required, remove ASM provisioned VLANs from the host facing ports of the switch.
Component types
The components (physical or virtual or applications) are the main building blocks of a template.
The following component types are defined in ASM:
• Storage
• Switch
• Server
• Cluster
• Virtual Machine
• Application
NOTE: Currently, ASM does not support Switch configuration.
NOTE: It is recommended to add physical devices to the template first, then configure virtual
resources, and lastly configure application settings to be deployed on the resources.
Related Tasks
Storage
Server
Server (OS Installation only) Component Setting
48