Veeam Home | Support | Downloads
Best Practices for Veeam Backup & Replication 7.0 for VMware

Veeam Management Pack Help Center  > Best Practices for Deployment & Configuration >  Components Overview > Repository > Windows Server

Windows Server

Previous page Next page Print this Topic

Table of contents

If you are using a Windows server as a repository, consider that the storage can be a local disk, directly attached disk-based storage (such as a USB hard drive), or iSCSI/FC SAN LUN, or any device that appears as a drive letter at the system level.

noteNote

Network drives mapped in user profiles will not work as they are only available during the interactive login session. If necessary to use them as repository locations, please select the CIFS/SMB repository and provide the full UNC path and authentication information.

On a Windows repository, Veeam Backup & Replication deploys a local Veeam transport service (when you add a Windows-based server to the product console, Veeam Backup & Replication installs a set of components, including the Veeam backup proxy service with Veeam transport service, on that server).

When any job addresses the repository, the transport service on the repository establishes a connection with the source-side transport service on the backup proxy, enabling efficient data transfer over LAN or WAN.

Windows repositories can be configured to function as vPower NFS servers. In this case, Veeam Backup & Replication will run the vPower NFS service directly on the backup repository (namely, on the managing Windows server to which storage is attached) and provide ESX(i) hosts with transparent access to backed up VM images stored on the repository. For more details, refer to the Planning for Data Recovery & Verification section.

Table of contents