--- name: vmwaresolutions-veeam-cr-sag-planning title: Planning the deployment 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: 2025-12-31 --- > ## 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. # Planning the deployment {: #veeam-cr-sag-planning} 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} Plan the deployment by capturing information for use in the subsequent steps. Select the planning tasks for the deployment environment that you intend to build: * [Immutable backup plan](#veeam-cr-sag-planning-ib) * [Isolated recovery environment plan](#veeam-cr-sag-planning-ire) ## Immutable backup planning {: #veeam-cr-sag-planning-ib} Capture the following details of the VMware Cloud Foundation for Classic - Automated instance and Veeam® service instance: | Parameter | Description | | ----------- | ------------- | | `` | The VCF for Classic - Automated instance domain name. For example, `test.ibmcloud.local` | | `` | The VCF for Classic - Automated instance subdomain name. For example, if the root domain is `test.ibmcloud.local`, then the subdomain is `test`. | | `` | The code for the data center in which the VCF for Classic - Automated instance is deployed into, such as DAL10. | | `` | The `Public VLAN` number can be obtained from the UI by browsing to the VCF for Classic - Automated instance's Infrastructure page. | | `` | The ID can be found from the VLAN number and the IBM Cloud® CLI. For example, for VLAN number `1344`, `ibmcloud sl vlan list` `awk '/1344/ { print "Public_VLAN_ID: " $1 }'`. | | `` | The Private VLAN number can be obtained from the UI by browsing to the VCF for Classic - Automated Infrastructure page. The `Secondary Private VLAN` number is not required. | | `` | The ID can be found from the VLAN number and the IBM Cloud CLI. For example, for VLAN number `1607`, `ibmcloud sl vlan list` `awk '/1607/ { print "Private_VLAN_ID: " $1 }'` | | `` | The `Primary subnet for hosts and virtual server instances` on the `Private VLAN` can be obtained from the UI by browsing to the VCF for Classic - Automated instance's Infrastructure page. | | `` | The ID can be found from the subnet identifier and the IBM Cloud CLI. For example, for subnet `10.38.207.128`, `ibmcloud sl subnet list` `awk '/10.38.207.128/ { print "Private_Subnet_ID: " $1 }'`. | | `` | The `Primary subnet for hosts and virtual server instances` on the `Public VLAN`. | | `` | The ID can be found from the subnet identifier and the IBM Cloud CLI. For example, for subnet `169.60.242.0`, `ibmcloud sl subnet list` `awk '/169.60.242.0/ { print "Public_Subnet_ID: " $1 }'` | | `` | The FQDN can be obtained from the UI by browsing to the VCF for Classic - Automated instance's Summary page. | | `` | The IP address of the first AD/DNS server can be obtained from the UI by browsing to the VCF for Classic - Automated instance's Summary page. | | `` | The IP address of the second AD/DNS server can be obtained from the UI by browsing to the VCF for Classic - Automated instance's Summary page. | | `` | The IP address of the Veeam Backup and Replication server. | {: caption="Capture parameters for Immutable backup planning" caption-side="bottom"} Define the following parameters: | Parameter | Description | | ----------- | ------------- | | `jmp_security_group_name` | The required name for the security group to protect the jump server. | | `as_security_group_name` | The required name for the security group to protect the automation server. | | `js_hostname` | The required jump server hostname. | | `as_hostname` | The required automation server hostname. | | `ansible_ip` | The IP address of the automation server. | | `lhbr_hostname` | The required Linux® hardened repository server hostname. | | `sa_veeam_cyber_admin_password` | A complex password is used for the Veeam service account `sa-veeam-cyber-admin` account. | | `your_username` | A username for the account on the automation server so that you can SSH to the server. | | `timezone` | The time zone to be configured in the Linux hardened repository. For more information, see the [time zone catalog](https://manpages.ubuntu.com/manpages/questing/man3/DateTime%3A%3ATimeZone.3pm.html){: external}. | | `lhbr_root_password` | This password is the IBM Cloud supplied initial root password that is provided after provisioning of the Linux bare metal server. It is used to initially connect to the server for configuration and stored in the Ansible® vault file. | | `sa_ansible_password` | A complex password that is stored in the Ansible vault file that is used for the `sa-ansible` service account on the Veeam backup server. | | `immutability_period` | The required immutability period for the Linux Hardened repository. For example, `30` for 30 days. | | `max_concurrent_jobs` | Specifies the maximum allowed number of concurrent tasks for the backup repository. For example, Veeam recommends one task = one CPU core and 2 GB RAM per core. For more information, see [Task limitation for backup repositories](https://helpcenter.veeam.com/archive/backup/120/vsphere/limiting_tasks.html){: external}. | {: caption="Define parameters for Immutable backup planning" caption-side="bottom"} ## Isolated recovery environment planning {: #veeam-cr-sag-planning-ire} The following information is needed for the isolated recovery environment planning: | Parameter | Description | | ----------- | ------------- | | `` | A public key for vSRX user. | | `` | The private IP of the vSRX that is reachable from the automation server. | | `` | The IP address of the Veeam cyberproxies in the production environment. Multiple proxies are possible. | | `` | The IP address of the Linux hardened repository server. | | `` | The FQDN or IP address of the vCenter appliance in the production environment. | | `` | The username of the account in vCenter appliance in the production environment. | | `` | The password for the `vcsa_user`. | | `` | The subdomain of the root domain of the vCenter appliance in the production environment. | {: caption="Parameters for Isolated recovery environment planning" caption-side="bottom"} ## Related links {: #veeam-cr-sag-planning-related} * [Cyber recovery with Veeam architecture overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam-cr-sa-overview&format=markdown)