- It is always advisable to make sure you're using the latest version of SAMBA. The latest version can be downloaded here.
- Depending on the SAMBA version/configuration, a files last modification date & time is the same as the creation date & time. To resolve this either configure SAMBA to correctly store the last modification date & time, use a Fast Backup profile, or backup to a single compressed Zip file.
- SAMBA has 2GB file size limit.
- File/directory permissions must be set correctly. On the Linux system, the underlying permissions must allow the user the backups are run under to have permission to create, read, and delete the backup files. Make sure the umask value is set correctly otherwise you may not be able to read, create, or overwrite your backup files.
- If your SAMBA share is mapped to a drive letter, and SyncBack cannot see it, try upgrading your version of SAMBA or using a UNC path instead. For SyncBackPro/SE running under Windows Vista or later, see this article for a possible reason. This last issue should not affect SyncBackFree.
- We have received occasional reports that SyncBack can see the share fine, but has issues when browsing inside it whereby the contents of certain sub-folders are not listed and/or scanned (while other comparable sub-folders are). After some investigation, we believe this may be an incompatibility between certain versions of SAMBA and the version of Delphi in which SyncBack is written. If so, and an upgrade of SAMBA does not fix it, we regret there is no known feasible fix.
Common problems using SAMBA with SyncBack Print
Modified on: Mon, 1 Nov, 2021 at 4:30 PM
Did you find it helpful? Yes No
Send feedbackSorry we couldn't be helpful. Help us improve this article with your feedback.