Just to be clear, what PTide is describing is technically data masking, but in general is not transforming the data in a useful way. Let's take health data for example. Personal Health Information (PHI) needs to be obscured so that a piece a information cannot be tied back to a particular person. You can't just run a random scramble against a patient's names because then the data becomes unusable for testing. How are we supposed to know that Sasdfr Tswsdfnu is a name or some garbage that the query returned? So, you need to change names into other names. But wait, there is more. You really should be translating Male names into other Male names and Female names into other Female names, so you need to look at the gender of patient and perform replacements based one that information. Furthermore, when you have patient data in multiple systems, you need to transform the data in the same way everyplace it happens. You can't change "Ringo Starr" to "John Smith" in one system and "Anthony Jones" in another. And that is just names. What about addresses? Birthdates? That one has other implications. You can't change babies into octogenarians as it will skew your queries. So, either the answer here is really "no, Veeam can't do data masking" or the question is still open.