---
name: vmwaresolutions-veeam-bms-archi-app-support
title: Overview of application support with Veeam
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-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.

# Overview of application support with Veeam
{: #veeam-bms-archi-app-support}

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}

For applications hosted on the VMs, Veeam® requires network access to the VMs to provide application-aware backups. To enable the application-aware image processing or the guest file system indexing options in the backup job, In the Veeam Backup and Replication console, you need network access between customer overlay and the Veeam bare metal server management network (primary subnet on private VLAN 1). If you want to use these capabilities, routing must be designed and implemented between the customer's VMware NSX-T™ overlay networks.

The guest interaction proxy is a backup infrastructure component that sits between the backup server and the processed VM. This component is needed if the backup or replication jobs perform the following processing of VMs:
* Application-aware processing
* Guest file system indexing
* Transaction log processing

The guest interaction proxy deploys the runtime process only in Microsoft® Windows® VMs. In VMs with another guest OS, the runtime process is deployed by the backup server.

For Windows virtual machine (VM) file level restores, Veeam first tries to connect to the Guest VM through the network, and since the network is isolated, the VMware vSphere® Guest Interaction API is then used to complete a network-less restore.

For Linux® VM file level restores, a File Level Restore (FLR) appliance needs to be deployed before you attempt the file level restore by the IBM Backup Administrator. Otherwise, the first time a tenant tries to restore a file, they receive an error in the Veeam Backup and Replication Console. For two of the three restore options, the FLR appliance requires network connectivity to the Linux VM where the file is to be restored, since the network is isolated. Therefore, only the download option is applicable to this service. This download needs to be moved to the correct place in the file system.

For more information about file level restore, see the Veeam documentation.

## Related links
{: #veeam-bms-archi-app-support-related}

* [Veeam Backup and Replication](https://www.veeam.com/products/veeam-data-platform/backup-recovery.html?ad=menu-products){: external}
* [Veeam Help Center technical documentation](https://helpcenter.veeam.com/?ad=menu-resources){: external}