Dear PM
I would like to back up a Netapp. To do this, I have integrated it as a storage object. When backing up a volume, I get a warning ‘Item with possible non-UTF8 characters detected’. I then opened a ticket and the support team explained how to deal with this behaviour. So far so good.
In addition, the support colleague pointed out to me that this topic is not yet on the development roadmap and asked me to contribute it this way.
So dear PM: I request the implementation of a correct handling of non-UTF8 characters. Thank you.
Rainer
-
- Novice
- Posts: 3
- Liked: never
- Joined: Nov 08, 2024 12:16 pm
- Full Name: Rainer
- Contact:
-
- Product Manager
- Posts: 14684
- Liked: 1693 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Item with possible non-UTF8 characters detected
Hello rainerb,
Thank you for your request, noted!
For all the newcomers, please refer to this registry key which can define the non-UTF8 encoding for your NAS jobs. It addresses the issue of FLR or NAS to tape jobs when non-UTF8 is present in the backup. Thank you!
Example: \\someserver;windows-1258;\\someotherserver\someshare;iso-8859-9;172.16.24.38:/nfsshare;hz-gb-2312;\\prg10556;windows-1251
The logic checks if the processed share (by FLR or NAS-to-Tape job) have a name starting with the given value. Adding \\myserver will match every share on the server like \\myserver\myshare and \\myserver\myothershare.
The list of valid encoding names can be found here: https://learn.microsoft.com/en-us/dotne ... t-encoding
Thank you for your request, noted!
For all the newcomers, please refer to this registry key which can define the non-UTF8 encoding for your NAS jobs. It addresses the issue of FLR or NAS to tape jobs when non-UTF8 is present in the backup. Thank you!
Code: Select all
Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\
Name: SourceFileSystemEncoding
Type: REG_SZ
Format: <sharename1>;<encodingname1>;<sharename2>;<encodingname2>;…;<sharenameN>;<encodingnameN>
The logic checks if the processed share (by FLR or NAS-to-Tape job) have a name starting with the given value. Adding \\myserver will match every share on the server like \\myserver\myshare and \\myserver\myothershare.
The list of valid encoding names can be found here: https://learn.microsoft.com/en-us/dotne ... t-encoding
-
- Novice
- Posts: 3
- Liked: never
- Joined: Nov 08, 2024 12:16 pm
- Full Name: Rainer
- Contact:
Re: Item with possible non-UTF8 characters detected
Hello Dima,
Thank you for your message. I am not sure whether the information will help me and how I can use it. I do not back up shares but use the Netapp integration and then have connected volumes. How should I address that then? I have the Netapp as an object. With the share I then have a vServer. In the job I address NetappObject:/volume. Not as in the example \\vserver\share or vserver:/share
The Veeam server gets access to all volumes by adjusting the Netapp export policy, regardless of whether I have access with my backup user.
I have to set it up like that because, for historical reasons, many volumes run in mixed mode and I do not have consistent access via the share level.
Best
Rainer
Thank you for your message. I am not sure whether the information will help me and how I can use it. I do not back up shares but use the Netapp integration and then have connected volumes. How should I address that then? I have the Netapp as an object. With the share I then have a vServer. In the job I address NetappObject:/volume. Not as in the example \\vserver\share or vserver:/share
The Veeam server gets access to all volumes by adjusting the Netapp export policy, regardless of whether I have access with my backup user.
I have to set it up like that because, for historical reasons, many volumes run in mixed mode and I do not have consistent access via the share level.
Best
Rainer
-
- Product Manager
- Posts: 14684
- Liked: 1693 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Item with possible non-UTF8 characters detected
Hello Rainer,
The key will work anyway. Under the NetappObject:/volume we track the information about the file shares, so you can define a custom encoding per-share via regkey which will be used further for restores / NAS to tape or other activities (which operate at a file share level). Thank you!
The key will work anyway. Under the NetappObject:/volume we track the information about the file shares, so you can define a custom encoding per-share via regkey which will be used further for restores / NAS to tape or other activities (which operate at a file share level). Thank you!
Who is online
Users browsing this forum: No registered users and 2 guests