- 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.
- Depending on the version of SAMBA used, the maximum file size may be 2GB or 4GB. Refer to the documentation for the version of SAMBA you use.
- 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 see this article for a possible reason.
Common problems using SAMBA with SyncBack Print
Modified on: Mon, 6 Nov, 2023 at 2:33 PM
Did you find it helpful? Yes No
Send feedbackSorry we couldn't be helpful. Help us improve this article with your feedback.