• Skip to main content
  • Skip to secondary menu
  • Skip to primary sidebar
The Blog of Jorge de la Cruz

The Blog of Jorge de la Cruz

Everything about VMware, Veeam, InfluxData, Grafana, Zimbra, etc.

  • Home
  • VMWARE
  • VEEAM
    • Veeam Content Recap 2021
    • Veeam v11a
      • Veeam Backup and Replication v11a
    • Veeam Backup for AWS
      • Veeam Backup for AWS v4
    • Veeam Backup for Azure
      • Veeam Backup for Azure v3
    • VeeamON 2021
      • Veeam Announces Support for Red Hat Enterprise Virtualization (RHEV/KVM)
      • Veeam announces enhancements for new versions of Veeam Backup for AWS v4/Azure v3/GVP v2
      • VBO v6 – Self-Service Portal and Native Integration with Azure Archive and AWS S3 Glacier
  • Grafana
    • Part I (Installing InfluxDB, Telegraf and Grafana on Ubuntu 20.04 LTS)
    • Part VIII (Monitoring Veeam using Veeam Enterprise Manager)
    • Part XII (Native Telegraf Plugin for vSphere)
    • Part XIII – Veeam Backup for Microsoft Office 365 v4
    • Part XIV – Veeam Availability Console
    • Part XV – IPMI Monitoring of our ESXi Hosts
    • Part XVI – Performance and Advanced Security of Veeam Backup for Microsoft Office 365
    • Part XVII – Showing Dashboards on Two Monitors Using Raspberry Pi 4
    • Part XIX (Monitoring Veeam with Enterprise Manager) Shell Script
    • Part XXII (Monitoring Cloudflare, include beautiful Maps)
    • Part XXIII (Monitoring WordPress with Jetpack RESTful API)
    • Part XXIV (Monitoring Veeam Backup for Microsoft Azure)
    • Part XXV (Monitoring Power Consumption)
    • Part XXVI (Monitoring Veeam Backup for Nutanix)
    • Part XXVII (Monitoring ReFS and XFS (block-cloning and reflink)
    • Part XXVIII (Monitoring HPE StoreOnce)
    • Part XXIX (Monitoring Pi-hole)
    • Part XXXI (Monitoring Unifi Protect)
    • Part XXXII (Monitoring Veeam ONE – experimental)
    • Part XXXIII (Monitoring NetApp ONTAP)
    • Part XXXIV (Monitoring Runecast)
  • Nutanix
  • ZIMBRA
  • PRTG
  • LINUX
  • MICROSOFT

Veeam – Configure Veeam Locations to improve data sovereignty control and reporting

26th April 2018 - Written in: veeam

Greetings friends, with the upcoming launch of GDPR, many of the companies that use Veeam or service providers using Veeam are facing many new challenges, in this Blog I will not discuss all the challenges that a regulation like GDPR has, but how Veeam can help.

Since the release of Veeam Backup & Replication v9.5 U3, Veeam has included a new feature called Locations, which will help us with the task of marking infrastructure elements and backup elements, so that we can visualize all this later. When we are performing Veeam tasks once we have the Locations configured, we will be able to see a warning in the jobs that will allow us to check if we are not sending backups to sites where the new regulation does not allow.

The elements that we can assign Locations are the following:

  • Elements in Virtual infrastructure: vCenter Servers, datacenters, clusters and hosts.
  • Backup infrastructure elements: backup repositories, scale-out backup repositories, tape libraries and tape vaults.
  • Elements in Agent management: protection groups.
  • Veeam Cloud Connect for service providers: cloud repositories and hardware plans.

Configuring Veeam Locations in Veeam Backup & Replication v9.5 U3

As mentioned before, we will need Veeam Backup & Replication v9.5 U3 or higher to configure the Locations. We will go to Home – Inventory and click on Locations:

Once in the Locations menu, we can add as many as we need for our environment:
Assigning Veeam Locations in virtualization elements

We can assign the Veeam Locations to different elements, the first and most important is to assign the Locations to the virtualization elements and to all the VMs within these environments, for this, from Home – Inventory – Cluster or Host we will right-click and select Location:

It will ask us if we want to assign all the sub-elements to this Location too, so that all the VMs inside are marked as being in my UK Datacenter:


Assigning Veeam Locations in Veeam Agents controlled with Veeam Backup & Replication 9.5U3 Console

From Veeam Backup & Replication v9.5 U3, you can also manage all the Veeam Agents of the Veeam console, in a very comfortable and efficient way, you can assign a Location to Veeam Agents elements in a very simple way, as always we will go to Home – Inventory, and from the Physical & Cloud Infrastructure menu, we will click on the element that we want to assign a Location:

This Location will be assigned to all the Veeam Agents that the Protection Group contains, in my case it is a Hyper-V that I have virtual in Microsoft Azure.

Different Locations can of course be assigned to different Protection Groups.

Assigning Veeam Locations in Backup elements

Last but not least, we can assign Locations to all the Backup Repositories we have in the environment, for this we will go to Home – Backup Infrastructure and select the Repository we want, and assign the different Locations.

Assigning Veeam Locations in Cloud elements

Finally, I would like to show you how to apply Veeam Locations to our Veeam Cloud provider, to do this from Home – Backup Infrastructure – Service Providers, we will select the service provider(s) and assign a Location to them:

Export or import the Veeam Locations list

Imagine that you have an environment with several Data Centers, where there are multiple Veeam Backup & Replication Servers, for this we can export the list of Locations from one VBR, and import it into another, as simple as going to the Locations menu and clicking on Export or Import:

Warning when selecting a resource that is located in another Location

When you are creating a job within Veeam, selecting the Veeam Repository will automatically check between the source of the VM or hardware and the Repository, allowing you to show a warning to the Backup administrator that a violation is occurring between the source and destination of the data:

Notification messages in Veeam jobs to warn the administrator

If the backup manager still ignores this warning, it will be displayed in the Veeam job summary:

Once we have all the elements of Veeam in their respective Locations, we can go to Veeam ONE and create the necessary reports.

To do this you can visit the following blog post.

Filed Under: veeam Tagged With: veeam, VEEAM GDPR, VEEAM LOCATION, veeam security, VEEAM TAGS

Reader Interactions

Comments

  1. Ludovico says

    28th July 2020 at 8:36 am

    great explanation. we are trying to apply locations to our Veeam infrastructure (Veeam 10) but we experience some apparently strange behavior: not able to apply location to single backup repository objects. When we select a backup repository, the “Set location” menu doesn’t appear (only exception the “Default Backup repository”). Any idea?

  2. Diego says

    27th November 2024 at 5:06 pm

    Hi all,

    When I’m job editing in the “Storage” step, This takes a long time to check locations. Why…..

  3. jorgeuk says

    4th December 2024 at 8:22 pm

    Hello Diego, I am not sure, if it is taking too long, please open a support case with Veeam so they can review.

Trackbacks

  1. Veeam – Simple, yet powerful, data sovereignty reports in PDF format on Veeam ONE – The Blog of Jorge de la Cruz says:
    27th April 2018 at 12:57 pm

    […] friends, we saw the other day how to configure Veeam Locations in our virtualization environment, Cloud providers and in our Backup […]

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

  • E-mail
  • GitHub
  • LinkedIn
  • RSS
  • Twitter
  • YouTube

Posts Calendar

April 2018
M T W T F S S
 1
2345678
9101112131415
16171819202122
23242526272829
30  
« Mar   May »

Disclaimer

All opinions expressed on this site are my own and do not represent the opinions of any company I have worked with, am working with, or will be working with.

Copyright © 2025 · The Blog of Jorge de la Cruz