Problem of FLR with Debian and french characters

[jeancharles]

Hello,

My client has VMware vSphere 5.1u1, Debian virtual machines acting as file servers with folders and files in French alphabet on LVMs backed up with Veeam Backup 7 R2. There is no problem with most files and folders, but some (many in fact) have accents and special characters in their name/path.
When we try to use the FLR appliance to restore them we get errors.

The case number is # 00483783

We can use the Instant Recovery to access the files, and we can restore files not using special characters. The limit seems to be with the unicode support of the FLR Appliance.

Is there a way to enable Unicode/UTF-8 support for this appliance, or to have a special "French" version built for now?

Thank you for your help,

Jean-Charles

[Gostev]

Hi, this enhancement should be a part of the future releases. Unfortunately, we had to drop it from R2 last minute due to unforeseen problems the fix has caused. Thanks!

[tsightler]

In the interim perhaps you can simply use rsync/FTP to restore the files from the FLR appliance.

[jeancharles]

Thank you for your answers, I'll give a try at rsync/FTP/SCP, but I can not login on the FLR appliance.
It is hosted on my Veeam Backup Server, appliance name is VeeamFLR_sigsrv1_d0abcf69-170a-4c1d-a55e-694b6810fda0, should my password be VeeamFLR_sigsrv1_d0abcf69-170a-4c1d-a55e-694b6810fda0_r ?

I do not understand clearly the KB : http://www.veeam.com/kb1447

[nefes]

Starting from Veeam B&R 7 you can set any password you want to all appliances. Just go to Options -> Manage Credentials and set password to the account with "FLR helper appliance credentials" description.
It will be used at the next run of FLR job.

[jeancharles]

Thank you, I tried to go that way, but if I change the password I will have to redeploy all my VirtualLabs as they rely on FLR appliance. I'll maybe go that way as it seems the only workaround available for now.
Maybe for next addon it would be interesting to add a second account for "troubleshooting" that would not interfere with existing labs and deployments.

[Gostev]

I don't see why changing the password would require you to redeploy Virtual Labs.

[jeancharles]

It seems the FLR appliance password is also the proxy appliance password

https://dl.dropboxusercontent.com/u/167358/password.jpg


Veeam gives me a warning when I want to edit it.

[Gostev]

I can double check what this means, but pretty sure it does not mean you need to re-create your labs. Instead, this will simply update the appliance.

[foggy]

Not re-create but simply go through the lab wizard to update the password.

[jeancharles]

Ok thank you I will try it, and ftp/scp files to another server to recover them, but when can we expect a working FLR appliance for non english characters? It would really be useful as users cannot live without accents here in France

[foggy]

but when can we expect a working FLR appliance for non english characters?

Please see Anton's first reply in this thread:

Hi, this enhancement should be a part of the future releases. Unfortunately, we had to drop it from R2 last minute due to unforeseen problems the fix has caused. Thanks!

[edv@rubner.com]

Hi,

We use Debian and Veeam 8, Update 3.
Unfortunately, the problem has not been solved.
Even FTP no longer works when I access from a Windows client to the FLR Appliance.

Thanks and Greetings
Michael

[jeancharles]

Hello,
I have not posted an update to this thread, but my client found a way to access the files, you start the virtual machine with Instant VM Recovery, change the IP address and you access it with FaspSCP/WinSCP by specifying the correct character set and can copy files back to production.
My client is also migrating from iso8859-15 to UTF-8 that works well with all new applications and Linux FLR.

[foggy]

We use Debian and Veeam 8, Update 3.
Unfortunately, the problem has not been solved.

As far as I know, ability to restore files with special characters in their names should be included in the upcoming v9.

[jeancharles]

Hello,

Thank you for this input, actually it should be possible to migrate servers to UTF8 and all works well normally.

[fraack]

Hi,

are there any Updates for this functionality? I have a customer running 9.5 U3a. Seems that the problem still exist.

Thanks in advance
Florian

[jeancharles]

Hello,

Sorry my client has two workarounds :

- using FastSCP to read and copy the files

- migrate to UTF8 the samba file servers

Have a good day,