Program Settings

  • Prefs
  • Startup
  • Logs
  • Notify
  • Misc, License
  • Advanced
  • Types, Limits
  • Cloud
  • DB
  • Events
  • Performance
  • Keys
  • More

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:
Syncovery will query https://www.syncovery.com/whoami.php regulary 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 name contains one of
these settings
        
Connection name must not contain


Checking Interval:
Minutes (minimum 5)
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 Listrings
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
Even More Detailed
Transfer Details (especially for large files and resuming)
Create Profile Change Logs

Log Real-Time Monitoring Status Every
  Minutes    

Create timerlog files (for debugging only), level:
Checkpoint logging (for debugging only)

Send email when tasks complete

For scheduled tasks
Attach log file
For manually started tasks
List filtered items
Send Email even when nothing was done
Use simple success/failure subjects
Send Email only when an error has occured
Send email when a file has been replaced
Send email upon conflict
No email if re-run is successful
Failing Jobs Being Retried: Send Email After:
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
Use HTML Format

Path For Temporary Files:  
Waiting Time countdown before shutdown:
Seconds
Scheduler 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




Registration Name:  
Registration Code:  



 
   
Timezone:  
  (offset from UTC)
Date Format:  
  (example: mm/dd/yyyy)
Time Format:  
  (default: hh:nn:ss, where nn=minute)

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
Split jobs (to save memory) after
  million entries
Use Global Speed Limit Mechanism (needs scheduler restart)
Speed Limit For All Profiles
  MegaBytes/second
Disable All Free Disk Space Checks
Ignore Weekdays 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 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 on Block Level (and no Synthetic Backup)
Minimum file size for Block Level Copying / Synthetic Backup:
Kb
File Name Extension For Incomplete Files During Transfer:

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 rather than OpenSSL

   

Path For SmartTracking and Caching Database:
Never allow two profiles to share the same database
Make databases writeable for all users (to use SyncoveryCL via command line as normal user).

Embedded Firebird (default - included in installation)
Standalone Firebird Server(connect directly/lockally)
Standalone Firebird Server(connect via TCP/IP)

User Name (default: SYSDBA):
Password (default: masterkey):
Firebird Server Address (IP or computer name):

Service Start/Stop

Scheduler Start/Stop

Service Error

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 With 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 disc 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 GoogleDrive) usually allow only a limited
number of simultaneous connections for each users (such as 3 or 8)



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 (optional):







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.