This tab sheet contains options related to how your profiles and settings are saved.
Make config file writeable for all users (necessary to use SyncoveryCL command line as normal user).
Encrypt:
Protect With:
Encryption Password:
Repeat:
Store the Settings Password in a File (secured with an encryption key based on the machine ID)
Pathname of password file:
This tab sheet contains start-up related settings.
Scheduler Idle Time After Startup:
Minutes
Use Internet Connectivity Detection:
Detect Internet connection name
Look at this machine's local IP addresses
Syncovery will query www.syncovery.com/whoami.php regularly to detect your Internet connection.
The requests may be logged on the server but the data is not used for anything other than statistics.
Syncovery does not send any further information and no personal data other than your IP address.
Run jobs only if connection / IP contains:
Connection name / IP address must not contain:
Checking Interval:
Minutes (minimum 5 minutes)
Check When Jobs Are Run Manually, Too
Logging:
Abbreviated Logs
Path for logging:
Number of Log Files to Keep (per Profile):
Delete Logs With Nothing To Do
Additional Logging (for troubleshooting)
Internet Protocol Logging
Output Left/Right File Listings
SmartTracking Details
Keep Checkpoint History
File List Building Details
Speed Limit Details
File Security Details
File Share Details
Time Stamp Setting Details
Synthetic Details
With Extremely Detailed Timing Info Only For Debugging
Even More Detailed
Transfer Details (especially for large files and resuming)
No email if drive with specified volume label is missing
Include List Of Copied Files And Other Actions
Send Email In A Digest Every:
Send first digest each day at:
Send high importance emails immediately (not in digest)
Send Daily Summary At
Include Unscheduled Jobs
Use HTML Format
Path For Temporary Files:
Waiting Time countdown before shutdown:
Seconds
Background jobs may prompt to turn on and connect missing drives
Protect incompletely copied files - even if resuming fails, never restart from 0 or delete the incomplete file
Avoid direct folder scans if a remote listing fails
Test and keep alive real-time notifications after
Seconds Silence
Allow Syncovery to raise the Linux inotify watch limit for real-time monitoring when needed
Maximum number of monitored folders:
Max wait for remote listing to start:
Seconds; to complete:
Seconds
Timezone:
(offset from UTC)
Date Format:
(example: mm/dd/yyyy)
Time Format:
(default: hh:nn:ss, where nn=minute)
Registration Name:
Registration Code:
Enable Admin Login
Enable Readonly Login
Enable User Management (Multiple User Accounts with Specific Rights, Require User Logins, etc.)
Require Users to Log In Even from Localhost (Where It Is Normally Not Needed)
Second Factor for Web GUI Logins
Authenticator app for this login:
Require a Second Factor for All Logins
Otherwise only logins from public Internet addresses need one.
Logins from the local network, from this machine and from trusted addresses (see Advanced below) do not.
The Read-Only Login Needs a Second Factor for All Logins Too
When this is off, the read-only login does not ask
for a second factor from the local network, this machine and trusted addresses, even when all logins require one.
From public Internet addresses it always needs one.
Send Login Codes by E-Mail
Each code goes to the e-mail address of the login that logs in:
the addresses of the admin login and of the read-only login are set below, user accounts have their own address in Edit Users.
A login without an address cannot receive codes by e-mail.
SMTP server:
SMTP port:
The Port Uses SSL/TLS Directly (Such as 465; Otherwise STARTTLS)
SMTP user name:
SMTP password:
Sender address:
E-mail address of the admin login:
E-mail address of the read-only login:
Advanced: Addresses That Count Like the Local Network
Syncovery tells by the address of the browser whether a login
comes from the public Internet. Addresses of the local network (such as 192.168.x.x, 10.x.x.x or VPN ranges like 100.64.x.x) and this machine never
count as public. The two settings below are needed only in special cases.
Trusted public addresses:
Public addresses that count like the local network, for example
the fixed address of your office or of a VPN gateway. Logins from them need no second factor, unless one is required for all logins.
Trusted reverse proxies:
When the web GUI is reached through a reverse proxy (such as nginx,
Apache or the reverse proxy of a NAS), every request seems to come from the proxy. Enter its address here, and Syncovery takes the real address
of the browser from the X-Forwarded-For header that the proxy adds. Such headers from any other address are ignored, and a request carrying
them counts as public.
Both fields take comma-separated IP addresses or ranges, such as 203.0.113.7,
198.51.100.0/24 or 2001:db8::/48.
Maximum simultaneously running jobs (profiles):
Max. simultaneous jobs to run in a single execution process:
Lifespan of a profile execution process (number of jobs):
Buffer size for copying files:
Kb
Flush file buffers during copy, after
MB or
Seconds
Use Global Speed Limit Mechanism (needs scheduler restart)
Speed Limit For All Profiles:
MegaBytes/second
Ignore Weekday Restrictions In All Profiles
Force separate folder monitor thread for each real-time profile
Allow different users to run the same job at the same time without warning
Enable status web pages for each SyncoveryCL process (ports 8998 and below).
Global Pascal Script for All Profiles…
Split jobs (to save memory) after
million entries
Do not start a profile if there is less than
MB of system memory available
Split a running job when there is less than
MB of system memory available
Stop a running job if there is less than
MB of system memory available
Enter 0 to switch off any of the three memory limits above.
Use a memory saving algorithm while processing cloud listings
Disable All Free Disk Space Checks
Global Exclusion Masks (separate with semicolon or Enter)
Don't copy
Ignore Totally
File masks which should not be zipped (unless encryption is also chosen)
File masks which should not be updated using Block Level Copying (and no Synthetic Backup)
Minimum file size for Block Level Copying / Synthetic Backup:
Kb
Filename Extension for Incomplete Files During Transfer:
Possible Names of "Users" folder (separate with comma):
Maximum Part Size For Uploads:
MB
Maximum Upload Threads Per File:
Buffer Complete Parts in Memory When Uploading to S3 and Azure (May Use a Lot of Memory)
Accept new SSH and SSL servers
Use SecureBlackBox SSL/TLS rather than OpenSSL
Path For SmartTracking and Caching Databases:
Never allow two profiles to share the same database
Make databases writeable for all users (to use SyncoveryCL via command line as normal user).
Export file list to XML at the end of each job
Embedded Firebird (default - included in the installer)
Standalone Firebird Server (connect directly/locally)
Standalone Firebird Server (connect via TCP/IP)
User Name (default: SYSDBA):
Password (default: masterkey):
Firebird Server Address (IP or computer name):
Choose the event types that Syncovery should log using the system's event log.
Service Start/Stop, Daily Summary Sending
Scheduler Start/Stop
Service Error, Email Sending Failure
Application Error
General Warnings
Profile Run Started
Profile Run Completed Without Errors
Profile Run Completed With Errors
Profile Run General Error (immediately logged before profile completion)
Profile Run Warnings
Profile Modified by User
CPU Usage
CPU 0
CPU 1
CPU 2
CPU 3+
Thread Priority:
Thread Count for File List Building
Folders can be scanned using multithreading. Specify how many folders should be procesed
simultaneously for these types of storages by each job. The maximum is 500.
Local folders
Internet Protocols
Network folders
Remote Listing and Database Cache
Please note: a higher number of threads can cause high CPU and disk or network usage. Threads will
also compete with each other when allocating memory, so more threads can actually be slower than
just a few threads.
Internet protocol and cloud servers (such as FTP or Google Drive) usually allow only a limited
number of simultaneous connections for each user, such as 3 or 8.
Remove default threading limits and other program limits.
On this page, you can configure the private keys that should be used for authentication as a client.
When private keys are set up, you can choose them individually for each profile on the Security tab sheet of the Internet Protocol Settings dialog.
Private Key Name For Reference in This Program:
Private Key File:
Public Key File (for information only - not needed):
Key files must continue to exist in their specified locations.
Enable Profile Priority Mechanism
Prevent Starting Lower Priority Jobs While Higher Ones Are Running
Pause Lower Priority Jobs When a Higher One Starts
Limit Lower Priority Jobs to a Single Copying Thread While Higher Ones are Running
Allow Up To
Jobs to Run Simultaneously Without Enforcing the Above Rules
Profiles can be assigned a priority level on the profile editor dialog box. Profiles with level 0 will be exempted from any of these limitations.