https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMzQwIiwiaGFzaCI6IjAwMmYwNjRkLTA2NDMtNDlhZC04ODRjLTQ2MWExNjZiNjMxYyJ9
1-800-691-1991 | 9am - 8pm ET
EN

File Name Is Changed During FLR to a Non-original Location

Challenge

When restoring individual files to a location that is different from the original one, the "period" symbols contained in the file name will be removed. For example, file.name.txt will be restored as filename.txt

If such files are restored to their original location, they will not be affected by this behavior.

Cause

This is a known issue with Veeam Backup Browser engine which is used in Veeam Agent for Microsoft Windows and Veeam Backup and Replication products. During recovery, the backup browser performs a forbidden character check using the general vocabulary. As a result some file names may be modified due to the removal of the forbidden character.

Solution

To preserve the existing file names when restoring the files to a non-original location, use Windows Explorer.
KB ID:
2340
Product:
Veeam Agent for Microsoft Windows, Veeam Backup & Replication
Version:
VBR 7.x, 8.x, 9.x; VAW 1.x, 2.x
Published:
2017-10-19
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later