Deleting Automated instances in a multisite configuration
Be aware of the following considerations before you delete VMware Cloud Foundation for Classic - Automated instances that are part of a multisite configuration.
When you delete a VMware Cloud Foundation for Classic - Automated instance, the following components are released sequentially:
- All deployed services
- NFS storage
- The Support fee for NSX-T instances or the Support and Services fee for NSX-V instances
- VMware® product licenses
- VMware ESXi™ servers
- Subnets
- VLANs
Review the following information before you proceed.
- Any existing VLANs that you own, outside of IBM Cloud® for VMware Solutions, are not deleted.
- Any VLANs that contain your own resources, such as gateways or Veeam® servers are not deleted.
- Any VLANs or subnets without attached gateways or servers are deleted even though you might have IP addresses assigned to it from the subnets to your VMs.
Because of resource dependencies, the components in your instance are not released immediately when you delete the instance. For example, the VLANs and the VLAN primary subnets cannot be deleted until the ESXi servers are fully reclaimed by the IBM Cloud infrastructure, which happens at the end of the IBM Cloud infrastructure billing cycle. At the end of the billing cycle, which is typically 30 days, the subnets and VLANs are deleted and the instance deletion is completed.
You are billed until the end of the IBM Cloud infrastructure billing cycle for the deleted instance.
Procedure to delete Automated instances in a multisite configuration
- Delete all services from the secondary Automated instance.
- Ensure that no NSX objects are expanded into the secondary instance that you want to delete.
- Delete the secondary vCenter Server from the primary SSO (Single Sign-On) domain. For more information, see Unregister vCenter Server from Single Sign-On.
- Demote the local domain controller VSI (Virtual Service Instance). For more information, see Demoting domain controllers and domains.
- Delete the secondary Automated instance from the IBM Cloud for VMware Solutions console.
- Repeat steps 1 - 5 for all secondary Automated instances in your multisite configuration.
- After deleting all secondary instances, you can also delete the primary instance from the IBM Cloud for VMware Solutions console.