---
name: vmwaresolutions-veeam_server_host
title: Virtualization servers and hosts
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-11-25
---

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

# Virtualization servers and hosts
{: #veeam_server_host}

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}

The virtualization servers and hosts are an infrastructure that must be integrated with Veeam® managed infrastructure. During service deployment, the VMware Cloud Foundation for Classic - Automated instance is automatically registered. You can add the following types of servers and hosts to the backup infrastructure:

* [VMware vSphere Server](https://helpcenter.veeam.com/archive/backup/120/vsphere/add_vmware_server.html){: external}
* [VMware Cloud Director](https://helpcenter.veeam.com/archive/backup/120/vsphere/adding_vcloud_director.html){: external}
* [Microsoft Windows Server](https://helpcenter.veeam.com/archive/backup/120/vsphere/add_windows_server.html){: external}
* [Linux Server](https://helpcenter.veeam.com/archive/backup/120/vsphere/add_linux_server.html){: external}
* [Hyper-V servers](https://helpcenter.veeam.com/archive/backup/120/hyperv/add_hyperv_server.html){: external}
* [Veeam Backup for AWS servers](https://helpcenter.veeam.com/archive/vbaws/6a/vbr_integration/deployment.html){: external}
* [Veeam Backup for Microsoft Azure servers](https://helpcenter.veeam.com/archive/vbazure/5a/vbr_integration/deployment.html){: external}
* [Veeam Backup for Google Cloud servers](https://helpcenter.veeam.com/archive/vbgc/40/vbr_integration/deployment.html){: external}
* [Nutanix AHV clusters](https://helpcenter.veeam.com/archive/vbahv/40/userguide/deployment.html){: external}
* [Kasten K10 instances](https://helpcenter.veeam.com/archive/backup/120/kasten_integration/deployment.html){: external}


## General-purpose backup proxies
{: ##veeam_server_host_gen}

A general-purpose backup proxy is a component that operates as a data mover. The backup proxy processes jobs and delivers backup and restore traffic. General-purpose backup proxies can be used for the following operations:
* **NAS backup** - General-purpose backup proxies transfer data between a shared source file and a backup repository. In IBM Cloud&reg;, a general-purpose backup proxy needs to be deployed if you are backing up IBM Cloud File services in Classic or VPC environments.
* **Veeam agent and integration of storage system snapshot** - General-purpose backup proxies transfer data between a storage system and a backup repository. You cannot integrate any storage system in IBM Cloud. During service deployment, a general-purpose backup proxy is deployed on the Veeam backup server.


## Related links
{: #veeam_server_hosts-links}

* [General-purpose backup proxies](https://helpcenter.veeam.com/archive/backup/120/vsphere/backup_proxy_general.html){: external}