---
name: vmwaresolutions-cr_addingremovingservers
title: Expanding and contracting capacity for Cyber Recovery instances
description: As of 17 July 2025, new automated installations of Red Hat&reg; OpenShift&reg; for VMware® are no longer available for new or existing deployments of VMware Cloud Foundation for Classic - Automated instances. You can still use or delete your existing Red Hat OpenShift for VMware automated installations until 16 July 2026. The service will no longer be available from 17 July 2026.
last-updated: 2025-10-24
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/vmwaresolutions?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Expanding and contracting capacity for Cyber Recovery instances
{: #cr-addingremovingservers}

As of 17 July 2025, new automated installations of Red Hat&reg; OpenShift&reg; for VMware® are no longer available for new or existing deployments of VMware Cloud Foundation for Classic - Automated instances. You can still use or delete your existing Red Hat OpenShift for VMware automated installations until 16 July 2026. The service will no longer be available from 17 July 2026.
{: deprecated}

Expand or contract the capacity of your Cyber Recovery instances according to your business needs, by adding or deleting VMware vSphere ESXi™ servers or Network File System (NFS) storage.

## Before you add or delete ESXi servers
{: #cr-addingremovingservers-before}

You must migrate the VMware vCenter Server® virtual machines (VMs) before you delete a server. This requirement applies to the vCenter Server VM and to the additional vCenter high availability VMs on the management cluster.

## Adding or deleting ESXi servers
{: #cr-addingremovingservers-add-delete-esxi}

The processes to add and delete servers for Cyber Recovery instances are similar to the ones for Automated instances. For more information, see:
* [Adding ESXi servers to Automated instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservers&format=markdown)
* [Deleting ESXi servers from Automated instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_removingservers&format=markdown)

## Adding or removing NFS storage
{: #cr-addingremovingservers-add-delete-nfs}

The processes to add and remove NFS storage for Cyber Recovery instances are similar to the ones for Automated instances. For more information, see:
* [Adding NFS storage to Automated instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingnfs&format=markdown)
* [Removing NFS storage from Automated instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_removingnfs&format=markdown)

## Related links
{: #cr-addingremovingservers-related}

* [Planning for Cyber Recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_planning&format=markdown)
* [Requirements for Cyber Recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_orderinginstance_reqs&format=markdown)
* [Adding, viewing, and deleting clusters for Cyber Recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_addingviewingclusters&format=markdown)