---
name: vmwaresolutions-cr_orderinginstance-reqs
title: Requirements for Cyber Recovery
description: As of 17 July 2025, new automated installations of Red Hat® OpenShift® 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: 2026-02-16
---

> ## 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.

# Requirements for Cyber Recovery
{: #cr_orderinginstance_reqs}

As of 17 July 2025, new automated installations of Red Hat® OpenShift® 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}

Cyber Recovery helps you with data protection, cyberthreats, cyberattacks, and ransomware. The instance includes the Veeam® Backup and Replication 12.3.2 add-on service and a Linux® hardened repository (LHR). An edge gateway is required and you can provide your own or order one of the following edges:

* Juniper® vSRX
* FortiGate® Virtual Appliance

You can order add-on services. For more information, see [Services for IBM Cloud Cyber Recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_planning&format=markdown#cr_planning-addon-services).

Price calculations are generated automatically when you access the Cyber Recovery instance order page. Default selections include the Data Center SP Professional license for NSX-T™, the Dual Intel® Xeon® Platinum 8260 processor / 48 cores, 2.4 GHz CPU model, 768 GB RAM, and NFS storage for both the consolidated and workload clusters.

Complete the following tasks:

* If you are ordering an instance for the first time, complete the tasks in the **Before you begin** section on the ordering page. For more information, see [Setting up your environment for your first order](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-completing_checklist&format=markdown).
* Review the information in [Signing up for required accounts](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-signing_required_accounts&format=markdown).
* Review the information in [Cyber Recovery overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_overview&format=markdown).
* Review the domain name format. The domain name is used to generate the username and server names for the instance.

| Name | Value format |
| :------------ | :------------ |
| Domain name | `<root_domain>` (Microsoft® Active Directory™ domain name) |
| vCenter Server login username | `<user_id>@<root_domain>` (Microsoft Active Directory user) or `administrator@vsphere.local` |
| vCenter Server (with embedded PSC) FQDN | `<instance_name>-vc.<root_domain>`. The maximum length is 50 characters. Any hyphens (-) are removed from the instance name. |
| Single Sign-On (SSO) site name | `<root_domain>` |
| Fully qualified ESXi server name | `<host_prefix><n>.<root_domain>`, where `n` is the sequence of the VMware vSphere ESXi™ server. The maximum length is 50 characters. |
| NetBIOS name | First string of `<root_domain>`. The maximum length is 15 characters. |
{: caption="Value format for instance and domain names" caption-side="bottom"}

After the instance is provisioned, do not modify any values that are set during the instance order. Otherwise, the instance might become unusable.
{: attention}