For general data protection regulation (GDPR) compliance, Veeam can add a location tag to which component?

Veeam Backup & Replication V12 provides a location tagging feature specifically for extents within a Scale-out Backup Repository (SOBR). This functionality is crucial for data sovereignty and compliance with regulations like GDPR. By assigning a location tag to a repository extent, administrators can use the "Data Locality" placement policy. This policy ensures that backups of virtual machines or other workloads are stored on extents that share the same location tag as the source workload's infrastructure, thereby keeping data within a specific geographical region.

A. File copy job: A job is a configured task, not a storage component where data resides; therefore, it cannot be assigned a location tag for data residency purposes.

B. Proxy server: A proxy server is a data mover component that processes data in transit but is not the final storage destination for long-term retention.

D. WAN accelerator: A WAN accelerator optimizes data transfer and uses a cache, but it is not a primary backup repository and cannot be tagged for data location compliance.

1. Veeam Backup & Replication V12 User Guide for VMware vSphere: In the section "Scale-Out Backup Repositories

" under the sub-section "Adding Extents

" the guide states: "You can assign a location to the extent. The location can be later used for the Data Locality placement policy to store backups to extents in the same location as the source VM." (See section: Scale-Out Backup Repositories > Adding Extents > Step 4. Specify Backup Repository Settings).

2. Veeam Backup & Replication V12 User Guide for VMware vSphere: The "Placement Policy" section for Scale-out Backup Repositories details the "Data Locality" option: "With the Data Locality option

Veeam Backup & Replication analyzes the location of the source VM... and stores its backup to an extent in the same location." This confirms the link between location tags on extents and job placement for compliance. (See section: Scale-Out Backup Repositories > Placement Policy).