Foreign characters in file names
It is very common to have non-English characters in file names. In most cases Syncrify will work correctly out of the box. However, in certain cases you may have to change a few configuration parameters. Therefore, consider using the following suggestions only if you are running into problems backing up files containing non-English characters.
Handing foreign characters on client side
Syncrify uses XML to store profile information on the client machine. The very first line (prolog) contains encoding for an XML file. If this encoding does not cover the characters used in top-level folders, that folder won't get backed up. Use the following steps to specify a custom encoding.
IMPORTANT These steps only matter if a top-level folder uses foreign characters. No modification is required if deeper files/folders contain foreign characters in their name.
Windows
Linux
Handing foreign characters on server side
By default Syncrify server uses UTF-8 to handle characters, which covers most languages in the world and therefore, you should not have to do anything. However, if things are not working as expected, try putting the following lines in $INSTALL_DIR\config\server.properties file:
sun.jnu.encoding=ISO8859_8
file.encoding=ISO8859_8
Server running on Linux
It is very important that environment variable $LANG is setup correctly on your Linux machine. If the value of $LANG is not correctly setup, the OS won't read file names correctly and you will end-up getting error messages in Syncrify.
The value for $LANG gets set when machine boots. However, if Syncrify gets launched before the script that sets $LANG is invoked, Syncrify won't know about this value. Therefore, we recommend you set the value for $LANG in the script that starts up Syncrify. This is done by adding the following line to the launch script.
export LANG="en_US.UTF-8" - bash shell
set LANG="en_US.UTF-8" - C shell
|
