At the top-left of the main windows is a burger menu , which when clicked, shows more options, one of which is Global Settings:
Update Check: If this button is clicked a check is made to see if a new version of SyncBackPro is available for download. You can also check via the Help tab in the main window. Internet access is required to check for new versions. If a new version is found, you have the option to ignore it. If so, SyncBackPro will not prompt you again about a new version being available (when doing automated periodic update checks). Skipping versions is not recommended as they may contain critical bug fixes.
•Stop background backups from starting: If ticked, any profiles set to run in the background (periodically, via a file/folder change or when a program is started or stopped) will not be started. This does not affect scheduled tasks, profiles set to run on media insert, or profiles set to run on login or logout.
•Stop all running profiles when Windows is shutdown or restarted: If enabled then when you shutdown or restart Windows then all running profiles will be stopped.
•Prompt me to remove the blank password restriction on the Windows Scheduler: By default you cannot use a blank/empty password when scheduling tasks. If this item is ticked then whenever you schedule a profile, and you are using Windows with this restriction, you will be prompted to ask you if you'd like SyncBackPro to remove that restriction. Note that you will not be prompted if the restriction has already been removed. If you do not have the access rights in Windows to remove the blank password restriction then the checkbox is disabled.
•Check periodically for new versions: If ticked then SyncBackPro will check, every 30 days, if a new version of SyncBackPro is available. See also the Update Check button (to check for a new version immediately) and also the Help -> Update Check main menu item. Internet access is required to check for new versions. Variables are also available that can retrieve the latest version number and also check to see if a new version is available.
•Start with Windows: If ticked, SyncBackPro will start after Windows is rebooted. It will start minimized. If you have profiles set to run periodically (not via a schedule), or to run whenever there are changes, it is recommended you use this option.
•Change the tray icon if any profiles have failed: If ticked, and any profiles fail when run, then the icon shown in the system tray will change to indicate this. To reset the icon, e.g. you have reviewed the failed profile(s) and are aware of the problem, then right-click on the SyncBack tray icon and select Reset tray icon. The tray icon will show an orange cross if background backups are being stopped from starting (see option above) and a red cross if background backups can start.
oReset tray icon when the newest log of a failed profile is displayed: If ticked then the tray icon is automatically reset when the newest log of a profile (that has failed) is displayed. Viewing older logs, or logs of profiles that haven't failed on their last run, will not reset the tray icon.
•Disable profile prompt notifications for ALL profiles: If enabled then profile prompts are never shown. This is a quick way to switch off the notifications if you find them distracting
•Amount of time to pause after resuming from hibernation or sleep: If the computer is put into sleep or hibernate mode, then resumed, this is the number of seconds that SyncBackPro will pause (sleep) before it does anything. This gives Windows time to re-establish network connections etc.
•Amount of time to delay before background profiles are started…: When SyncBackPro is started it will wait this amount of time before the first background profile is started. This gives you time to disable background tasks or to exit SyncBackPro before they start.
•Highlight profiles that have not run successfully for…: If the value is above zero then any profiles that have not run successfully for that number of days will have a special icon placed next to their name in the main window. This lets you clearly see which profiles are not running as expected. Note that disabled profiles are ignored and it does not apply to group profiles.
•Use the Windows Event Log: If ticked then errors are recorded in the Windows Event Log. These are not profile errors but errors related to using the program when the user cannot be prompted. They are typically used by technical support staff to help debug problems with the software.
•Default communication encryption to use with cloud services: By default SyncBackPro will use TLS v1.0 encryption when communicating with all cloud, and online services, if Windows 8.0 or earlier is used, otherwise TLS v1.2 is used. This provides the best compatibility with all cloud services and versions of Windows. More secure versions are available but they may not work with the cloud service or your operating system. This setting is the global default and so applies to all profiles, but you can override this setting in any cloud profile.
SyncBackPro has the ability to check if a file has been changed. If your system is infected with ransomware then it will encrypt many of your files, e.g. documents, text files, pictures, music, videos, etc. It usually won't encrypt files required by the system, e.g. EXE and DLL files. In most cases you will know immediately if you are infected with ransomware because it will likely prompt you for payment to decrypt your files. However, your backups are usually automated so your backups will continue to run, which means your backup files are likely to be replaced with the encrypted files. To avoid this happening you can configure SyncBackPro to check if a specific file has changed, and if so, no profiles will run. To use this:
1.Click the Create button. SyncBackPro will then create a file, with random content, in your My Documents folder. The file will have a random filename, but have the extension of .RTF
2.SyncBackPro will then calculate the hash file of that file and record it.
3.Now, whenever a profile is run, SyncBackPro will check to see if that file has changed, and if so, will not run the profile.
You can choose an existing file, if you wish, but you need to be sure that the file will not change. If you do change the files contents, click the Re-hash button to recalculate the hash value of the file. If you use an existing file it is recommended you copy a document or spreadsheet file that you already have and use the copy. By having an actual valid document it is more likely that it will be encrypted by ransomware.
If you no longer want to detect if the file has changed, click the Clear button.
Note that 2BrightSparks cannot guarantee that SyncBackPro will be able to detect all types of ransomware infection using this technique.
•Put new, imported, and copied profile settings files into...: This setting defines where to put the settings files for new profiles (existing profiles settings files are not moved). It is recommended that Automatic is used as this will store new profiles in the same folder as SyncBackPro when it is run from removable media or an external drive (connected via USB or Firewire), or the C:\Users\[username]\AppData\Local\2BrightSparks\SyncBack\ folder when not.
If SyncBackPro is being run from removable media or an external drive (connected via USB or Firewire) then you will not be able to choose where to store profiles (they will always be stored in the same folder as the program). If you do not have write access to the folder SyncBackPro is being run from then you cannot choose that option.
The roaming application directory is for people using corporate networks where files are typically stored on a server.
You can also choose a specific folder to store your profiles and settings in. Optionally, you can specify that only that folder is used. An important point to remember is that if you change the folder then all the profiles in that folder become unavailable. You can also specify a settings folder to use via the command line.
•Backup all profiles when the program exits (Unattended): This is the same setting as above except it applies only when exiting from an unattended run, e.g. run via a schedule. See the Profiles Backup section below for more details on making backups of your profiles.
•Backup all profiles when the program exits (Attended): By default a backup is made of all the profiles when SyncBack exits, either attended (e.g. run manually from the Start menu) or unattended (e.g. run automatically from a schedule). If this option is enabled, then a backup of all the profiles is made automatically when SyncBack exits from an attended run. Below the checkbox you can specify where to put the backup of the profiles. See the Profiles Backup section below for more details on making backups of your profiles.
•Number of days backup to keep: By default SyncBack will delete backup profile files that are over 30 days old. You can change this or set it to keep the backups forever (by using 0 days). See the Profiles Backup section below for more details on making backups of your profiles.
You can choose to have your profiles automatically backed up to another folder when the program exits. This backup can be done when run attended, e.g. it was run manually from the desktop or start menu, and/or unattended, e.g. it was run automatically from a schedule. If you have a large number of profiles then you may wish to only backup your profiles when exiting from an unattended run.
When you close SyncBack, via the Exit button at the bottom-right of the main windows, there is a drop-down menu to tell SyncBack if it should backup the profiles or not, regardless of the settings.
Another profile backup option is to use the –export command line parameter. You could create a scheduled task in Windows to run SyncBack (with just the -export command line parameter) every morning, for example, to backup the profiles.
You can manually create a backup of your profiles by simply exporting them.
To restore your profiles you can simply import them.
So as not to interfere with the Windows shutdown/restart/logoff process, profiles will never be automatically backed up if SyncBack is closing due to a Windows shutdown/restart/logoff.
This page contains settings related to how SyncBackPro communicates with FTP, FTPS, and SFTP servers. It is strongly recommended that you do not change any of these values and that the defaults are used.
•File buffer size: This is the size, in bytes, of the buffer used to send and receive files. The default size is 262144 bytes, and the minimum size is 8192 bytes.
•Send buffer size: This value directly affects the TCP window size. If the value is set to 0 the default Windows value is used and setsockopt() is not called. The default SyncBackPro value is 131072 bytes. This setting is only used by SmartFTP (FTP and SFTP) and Eldos FTP (not Eldos SFTP).
•Set the send buffer size automatically: When enabled the send buffer is automatically increased after the socket is connected until it reaches the optimal size. This option is enabled by default. This setting is only used by SmartFTP (FTP and SFTP) and Eldos FTP (not Eldos SFTP).
•Receive buffer size: This value directly affects the TCP window size. If the value is set to 0 the default Windows value is used and setsockopt() is not called. The default SyncBackPro value is 131072 bytes This setting is only used by SmartFTP (FTP and SFTP) and Eldos FTP (not Eldos SFTP).
•Set the receive buffer size automatically: When enabled the receive buffer is automatically increased after the socket is connected until it reaches the optimal size. This option is enabled by default. This setting is only used by SmartFTP (FTP and SFTP) and Eldos FTP (not Eldos SFTP).
This page contains settings related to how SyncBackPro communicates with a SysLog server (as specified in RFC 3164). When certain tasks are performed, e.g. profiles run, a message will be sent to the SysLog server.
•Send status messages to a SysLog server: If enabled, messages will be sent to a SysLog server.
•SysLog hostname or IP address: The hostname or I.P. address of the SysLog server. To broadcast use the I.P. address 255.255.255.255
•SysLog port number: The port number of the SysLog server. The default is 514.
•SysLog facility number (0 to 23): The facility number that SyncBackPro should use in messages sent to the SysLog server. The default is 16. Note that usually the numbers 0 to 15 are used for system messages.
•Send date and time in GMT timezone: The dates & times of the messages can either be in the local timezone (of the computer running SyncBackPro) or in the GMT/UTC timezone.
•Send messages in UTF8: Messages can either be in ASCII or UTF8.
•Prefix messages with username: To help with tracking, the messages sent to the SysLog server can optionally be prefixed with the Windows username.
•Send Test Message: Press to send a test message to the SysLog server.
The format of the profile end message is:
Profile [Profile_Name] Message [[Result=Result_Value Result_Description][Error=Error_Message][Integrity Check | Simulated][Restore][Unattended][Group=Group_Name][ProfileName]]
Many of these are optional, e.g. if there is no error message then it will not be there. For the profile result, the numeric values are:
0 = No result
1 = Unknown profile
2 = Profile is already running
3 = Profile has been imported and not run yet
4 = Profile is running
5 = Internal error
6 = Simulated run was aborted
7 = Simulated run failed
8 = Simulated run was a success
9 = Restore was aborted
10 = Restore failed
11 = Restore was a success
12 = Run was aborted
13 = Run failed
14 = Run was a success
15 = Failed due to network connection
16 = Failed because left or right could not be scanned
17 = Failed because the left and right could not be compared
18 = Run failed because Run Before program stopped profile
19 = Run failed because profile is disabled
20 = Run failed because drive errors were found
21 = Run failed because the log could not be emailed
22 = Run failed because the Volume Shadow Copy service failed
23 = Profile was aborted because it reached its run-time limit
24 = Profile was aborted because too many files would be deleted
25 = Profile was aborted because too many files would be updated
26 = Profile was aborted because of Touch Licensing
27 = Integrity check run was aborted
28 = Integrity check run failed
29 = Integrity check run was a success
30 = Ransomware Protection
31 = Profile aborted remotely
32 = Profile was aborted because too many files would be copied
•Enable sending of anonymous usage data to help improve the software: If enabled, SyncBack will send anonymous usage data to help improve the software. Please read the Runtime Intelligence help page for more details.
SyncBack stores passwords and other sensitive settings in an encrypted form. By default, a very simple encryption is used and it is relatively easy for someone to decrypt it (if they have access to your settings files). However, there are settings to make it considerably more difficult to decrypt:
SyncBack uses the Windows encryption routines, which means that the following encryption options are only available if your installation of Windows allows for 256-bit AES encryption. It may not be available due to the import and/or export laws in your country.
An important point to remember is that if you use any of these encryption settings then it limits what you can export and import.
For example, if you use a key file then another computer will never be able to import any profiles you export unless they also have your key file. If you use the Windows Data Protection option then another computer (or even Windows user on your computer) will never be able to import any profiles you export.
Also, if any of these settings are changed then SyncBack must re-encrypt all your encrypted settings (program settings and for all profiles).
•Use 256-bit AES encryption for storing sensitive settings: If set, SyncBack will use 256-bit AES encryption. Although this is a much stronger method of encryption than the default one, it is not impossible for someone determined enough to decrypt these settings (if they have access to your settings files). This is because the key to the encryption is within SyncBack itself and is the same key for all installations of SyncBack. By using the same key it simplifies exporting and importing profiles. You also have no encryption or decryption key to lose (and so lose access to the encrypted settings). With the next setting you have the option of supplying your own encryption key.
•Encryption key for sensitive stored settings: If set, SyncBack will use the encryption key stored in the specified file. You can create an encryption key file by clicking the Create Key File button (see below). Without this file it is impossible for someone to decrypt your settings. It also means that if you lose the file, its contents change, or you don't have access to the file (e.g. it's on a USB key and you forgot to plug it in), then SyncBack will not be able to decrypt your settings. It is recommended that you create the file on removable storage (e.g. a USB key) so that you can keep the file physically secure and also make a secure backup of the file. If you export a profile then you must remember that the computer that imports the profile will not be able to decrypt the settings without access to the key file.
oCreate Key File: When pressed you are prompted for a password. Enter a password (we recommend it contains at least 16 characters) then choose the file name to store the encryption key in. The filename can be whatever you want, and have any filename extension, but it must have a filename extension, e.g. enc.key. The file should be stored somewhere secure that SyncBack can access whenever it is run. Note that the key file you create is not used unless you select it as the key file.
•Store sensitive settings using the Windows Data Protection API: If set, SyncBack will use cryptographic routines in Windows to further encrypt the settings. This makes it impossible for someone to decrypt your settings, even if they have your settings files and the encryption key file, unless they are also logged into your Windows account on your computer. If you use this option you are strongly advised to create a Password Reset Disk whenever you change your Windows password. The reset disk must obviously be kept physically secure. If you export a profile then you must remember that the computer that imports the profile will not be able to decrypt the settings unless it is the same computer and same user account. If you reinstall Windows you will probably also lose access to the encrypted settings. If an administrator forcibly changes your Windows password you will also lose access to the encrypted settings (it's not a problem if you yourself change your Windows password).
If you lose the key file, or you are using the Windows Data Protection API and import your exported profiles on another computer (for example), then your encrypted settings will essentially become corrupt and invalid. Your serial number is one such setting, which means you will be prompted for your serial number again. All passwords are also stored encrypted, so you will need to re-enter those.
You can select what action SyncBackPro should take when you double-click on a profile:
This opens a window where you can change how profile log files are created. See this page of the help file for more details.
Please note that SyncBack Monitor will work only with SyncBackPro/SyncBackSE V9 (and newer) and does not support SyncBackFree.
See the SyncBack Monitor page in this help file for more details.
All Content: 2BrightSparks Pte Ltd © 2003-2021