I am running our monthly tape job and I keep getting mesages about " Potential data sovereignty violation: target tape library location (X) does not match source backup location (Y).
Since the location in veeam is just "location name" and the logic is apparently just "not in the same location" , this means any time I send a backup copy to tape I get this message.
In the specific case I just pasted, location X is 3 blocks from location Y.
Some way to better define which locations have real data sovereignty issues would be great. If only to avoid the warning messages when setting up a job to backup to a repository in a different datacenter.
Hi, would it help if we added the ability to join multiple locations into groups, where between locations within the particular group there's no violation? Thanks.
Necromancing a thread here...
This has not yet been resolved ? This has been bugging me for years -> yes, I can just place the same tag on everything but - what's the point of having the tag then.
I like noting what resides where, but my offsite copies are getting this "Potential data sovereignty violation". Perhaps you could implement those groups after 6 years
To be honest it's not a warning, it's a notice. Job finishes with "Success" - just checked. So not an issue really, maybe just a little annoying.
