inSync Share file naming convention
The files and folders within the inSync Share folder are not case-sensitive. This means that you cannot have two files that have the same name, but different cases. You also cannot have two folders that have the same name but different cases. The following table lists different file and folder naming scenarios and their outcome.
|You attempt to create a file using a file name that already exists, but you create the new file name using a different case|| |
inSync prompts you to save the new file with a different name. For example, if ReadMe.txt exists inside a folder within inSync Share and you attempt to create readme.txt in the same folder, inSync prompts you to save the new file as readme(2).txt.
|You attempt to create a folder using a folder name that already exists, but you create the folder name using a different case||inSync prompts you to merge the new folder with the existing folder that has the same name. For example, if a folder named Documentation exists in a folder within inSync Share and you attempt to create doCUmentation within the same folder, inSync prompts you to merge doCUmentation with Documentation.|
|You attempt to upload a file using a file name that already exists, but you upload the file name with a different case by using inSync Web||inSync overwrites the content of the existing file with the content in the new file. For example, if notes.txt exists in a folder and you attempt to upload NoTes.txt in the same folder, inSync overwrites the content of notes.txt with the content of NoTes.txt.|
|You create two files, one from inSync Share and the other from inSync Web||Both files are visible via inSync Web. However, only one file will be synced to your devices.|
|You restore a deleted file when a file with the same name exists||You cannot restore a deleted file if a file with the same name exists in the same directory. You must first change the name of the deleted file and then restore it.|
Note: On Linux laptops, if your create multiple files with the same name but different cases, all files other than the original will appear with the suffix conflict. We have not released a new version of the inSync client for Linux in inSync 5.4.2. You can continue using inSync client 5.4 for Linux with inSync Server 5.4.2. For more information, see File naming convention for inSync Share.
Usage of special characters
inSync Share does not sync files that contain specific special characters. The following table lists file and folder naming scenarios and their outcome.
|Usage of symbol||Outcome|
Invalid character list:
'<', '>', ':', ' <double inverted commas>', '|' , '?', '*', '\r' , '\n'
|If a file or folder name contains any of these special characters, those files or folders do not sync to the server. This is because some of the file systems do not allow these characters in the file or folder names.|
|Invalid prefix name list: |
'.~inSync$', '~$', '.~', '~inSync$'
If a file or folder name starts with any of these prefix names, those files or folders do not sync to the server. This is because inSync Share uses these names for temporary file names.
Invalid suffix name list:
If a file or folder name ends with .tmp, those files or folders do not sync to the server. This is because these are usually temporary files created on the computer.
|Invalid file/folder names: |
'desktop.ini', '.DS_Store', 'Icon\r'
If the file or folder is the same as any of these names, those files or folders do not sync to the server. This is because these are system-specific files.
Note: These special characters do not have any impact on backups. They only have an impact on inSync Share.