{"id":11184,"date":"2024-03-20T08:30:46","date_gmt":"2024-03-19T22:30:46","guid":{"rendered":"https:\/\/www.penguinpunk.net\/blog\/?p=11184"},"modified":"2025-01-30T16:02:22","modified_gmt":"2025-01-30T06:02:22","slug":"vmware-cloud-on-aws-tmcham-part-13-delete-the-sddc","status":"publish","type":"post","link":"https:\/\/www.penguinpunk.net\/blog\/vmware-cloud-on-aws-tmcham-part-13-delete-the-sddc\/","title":{"rendered":"VMware Cloud on AWS – TMCHAM – Part 13 – Delete the SDDC"},"content":{"rendered":"

\"\"<\/a><\/p>\n

\"\"<\/a><\/p>\n

*Update* 2025\/01\/30 – The VMware docs site has been moved to Broadcom’s Techdocs site. I won’t be updating all of the VMware links on this weblog, but this post will get the treatment.<\/p>\n

Following on from my article on host removal<\/a>, in this edition of Things My Customers Have Asked Me (TMCHAM), I’m going to cover SDDC removal on the VMware-managed VMware Cloud on AWS<\/a> platform. Don’t worry, I haven’t lost my mind in a post-acquisition world. Rather, this is some of the info you’ll find useful if you’ve been running a trial or a proof of concept (as opposed to a pilot) deployment of VMware Cloud Disaster Recovery (VCDR)<\/a> and \/ or VMware Cloud on AWS and want to clean some stuff up when you’re all done.<\/p>\n

 <\/p>\n

Process<\/strong><\/p>\n

Firstly, if you’re using VCDR and want to deactivate the deployment, the steps to perform are outlined here<\/a>, and I’ve copied the main bits from that page below.<\/p>\n

    \n
  1. Remove all\u00a0DRaaS Connector<\/span>s from all protected sites. See\u00a0Remove a DRaaS Connector from a Protected Site<\/a> (new link here<\/a><\/em>).<\/li>\n
  2. Delete all\u00a0recovery SDDC<\/span>s. See\u00a0Delete a Recovery SDDC<\/a> (new link here<\/a><\/em>).<\/li>\n
  3. Deactivate the recovery region from the Global DR Console. (Do this step last.) See\u00a0Deactivate a Recovery Region<\/a> (new link here<\/a><\/em>). Usage charges for VMware Cloud DR<\/span>\u00a0are not stopped until this step is completed.<\/li>\n<\/ol>\n

    Funnily enough, as I was writing this, someone zapped our lab for reasons. So this is what a Region deactivation looks like in the VCDR UI.<\/p>\n

    \"\"<\/a><\/p>\n

    Note that it’s important you perform these steps in that order, or you’ll have more cleanup work to do to get everything looking nice and tidy. I have witnessed firsthand someone doing it the other way and it’s not pretty. Note also that if your Recovery SDDC had services such as HCX connected, you should hold off deleting the Recovery SDDC until you’ve cleaned that bit up.<\/p>\n

    Secondly, if you have other workloads deployed in a VMware Cloud on AWS SDDC and want to remove a PoC SDDC, there are a few steps that you will need to follow.<\/p>\n

    If you’ve been using HCX to test migrations or network extension, you’ll need to follow these steps<\/a> (new link here<\/a><\/em>) to remove it. Note that this should be initiated from the source side, and your HCX deployment should be in good order before you start (site pairings functioning, etc). You might also wish to remove a vCenter Cloud Gateway, and you can find information on that process here<\/a> (new link here<\/a><\/em>).<\/p>\n

    Finally, there are some AWS activities that you might want to undertake to clean everything up. These include:<\/p>\n