Documentation RSS feed for this section

Amazon drive no longer supported

Posted on August 23, 2019 by in News

Unfortunately, Amazon drive has been reduced to Amazon Photos in August 2019, and all third party solutions have been locked out. Some developers got a notification from Amazon, but unfortunately the Syncovery team was taken completely by surprise when it stopped working on August 22nd, 2019.

Syncovery can no longer access Amazon drive in any way. The new Syncovery 8.43 will warn users about this new situation.

We recommend choosing a more professional storage solution such as from Microsoft, Backblaze, Box, Google Drive, DropBox, or others.

If you need to download files from your Amazon drive before canceling your subscription, we recommend using the Amazon Photos app. It seems to work better than Cloud Sync on a Synology NAS. Most importantly, the Photos App will be able to show the total file count and size relatively soon after starting the sync, and you will be able to guess how long the whole download will take. As opposed to Synology Cloud Sync, which will just run for days and you never know when it might complete.

Syncovery 8 Released

Posted on July 11, 2018 by in Documentation

The Windows version of Syncovery 8 has been released today. Syncovery 8 is a major new version with numerous larger and smaller new features and improvements.

Syncovery 8 is a free upgrade for licenses ordered on or after August 1st, 2015. All registration codes generated since then still work with Syncovery 8.

These are the most notable bullet points:

  • New .sz file format – allows uploading compressed and encrypted files without local temp files
  • Adds native support for Google Cloud Storage (v8.05).
  • Adds support for PCloud (v8.06).
  • Fast block level copying with the new File System Monitoring service (Windows only)
  • PascalScript allows to customize job functionality and e-mail notifications.
  • Subfolder selection can now be set to automatically include future new files and folders.
  • SharePoint and OneDrive folder listing is now “changes” based.

Read more about the new version 8 here.

Chaining Profiles (Running Profiles in Sequence)

Posted on June 12, 2018 by in Best Practices, Documentation

There are several ways to run jobs one at a time.

Running profiles with the scheduler running one job at a time

One way to run jobs one after another is to use the Scheduler. Give them a scheduled time and leave a minute between each profile. On the Scheduler tab sheet, click on the Tools and Settings button and uncheck “Start Profiles In Parallel”. Alternatively, go to the Program Settings dialog, tab sheet Advanced, and specify 1 for Max. simultaneous jobs.

Running profiles via manual invocation

For manual runs, select the profiles in the Overview, right-click the selection and choose “Run in Unattended Mode”. This will run them one after another, as opposed to “Run in Background”.

If you need Syncovery to do other things while the jobs are running, you can open Syncovery a second time.

Chaining profiles directly

Another way is to chain profiles. As an “after” command line in “Execute before/after” you can put:
RUN PROFILE Profile Name

This will start the next profile when the first one has finished, and so forth. The problem is that the chaining is always done, so it may be a problem if there is an occasion where you want to run only one of the chained jobs.

Using the command line

Yet another way is to use the Syncovery command line and invoke your jobs from a batch file or script:
Syncovery Command Line

Windows 10: Syncovery Update Required

Posted on May 14, 2018 by in Best Practices

Syncovery Update Required

For continued compatibility with recent Windows 10 updates, please make sure you update Syncovery to version 7.98d at least.

It is recommended to update Syncovery before installing any further Windows updates.

Syncovery 7.98d includes an updated Syncovery VSS Service to fix a potential compatibility issue that could cause the upgrade installation to fail and/or get stuck in a reboot loop. Or Windows might just boot up with a blank screen, or show a spinning mouse cursor instead of a login screen.

This happened only on some systems, but to be safe, please update Syncovery.

If you already updated Windows, that’s fine. In that case please update Syncovery too to avoid any potential problems in the future.

Questions? Please email support@syncovery.com.

Backblaze B2 – Backup and Mirror Your Data With Syncovery

Posted on November 17, 2017 by in News

Low Cost, High Performance Cloud Storage with Backblaze B2

Using Syncovery, you can now store and synchronize your data on BackBlaze B2. Syncovery is a generic file synchronization, mirroring and backup tool that provides an extremely wide range of features. It is a lightweight tool that runs on a variety of platforms and is highly optimized to run efficiently with little CPU and memory usage.

Advantages of using Backblaze B2 with Syncovery

  • B2 is a high-reliability and high performance storage
  • Syncovery runs on Windows, Macintosh, Linux, FreeBSD, and Solaris/Illumos (Intel only)
  • Supported processors are i386, x64, ARM, as well as PPC and PPC64EL (on request)
  • Syncovery can run directly on Synology, QNAP and other NAS devices (dedicated installers are available for Synology and QNAP)
  • You can set up multiple jobs with extreme customizeability, including:
    • File Masks & Filters
    • Compression, Encryption, and Filename Encryption
    • Multithreaded Transfers
    • File List Cache can avoid re-scanning the B2 folders every time the profile runs
    • Manual, scheduled, or real-time operation
    • One-Way or Two-Way Syncs
    • SmartTracking for Two-Way Syncs can detect deleted files and you can use B2 as central repository for sharing files between several computers
    • File timestamps are preserved on B2
    • Detailed log files and email notifications
    • Synthetic Backup can upload only the changed blocks in larger files to save bandwidth
    • You can also use the same tool to sync local folders and other types of storage.
    • Many additional options are available
  • For more details on Syncovery, please visit the main page on our web site as well as our Feature Matrix

Setting it up

Create a new profile, using either Wizard Mode or Advanced Mode. On the right-hand side, click the Internet button and change the protocol to B2 as shown in the following screenshot. Enter your Account ID and Application Key, which you can get from the Buckets page in the B2 web interface. Choose your container and folder with the Browse buttons. To create a new container, just type the name.

B2 Settings

B2 Settings

Using Syncovery 8 with Amazon S3 Inventories

Posted on July 18, 2017 by in Best Practices

Syncovery 8 can use Amazon S3 Inventories. On the second tab sheet of the Internet Protocol Settings dialog, please choose “Use S3 Inventories”.

To make Amazon generate these Inventories, go to the AWS S3 Management Console and refer to the screenshot below.

Inventory Name: your free choice
Filters: empty, or specify the folder you need
Destination Bucket: must be the same bucket that is listed
Destination Prefix: must be empty

Support for Google Team Drives

Posted on June 28, 2017 by in News

Support for Google Team Drives

Syncovery 7.85 uses the new Google Drive API V3 with support for Team Drives. Any one profile can sync with your main Google Drive, or one Team Drive. There is a new Container field with Browse button on the Internet dialog, allowing you to choose your Team Drive.

Additional New Features in 7.85:
– uses much less memory when processing cloud folder listings (such as Google Drive)
– produces much smaller databases (factor 4-10 reduction)
– in many cases, existing databases can be deleted in order to get the new smaller databases. Except if you depend on Synthetic Backup / Block Level Copying or Cache Destination File List.

Using Google Nearline with Syncovery

Posted on June 16, 2016 by in Best Practices, Documentation

Since v8.05, Syncovery natively supports Google Cloud Storage. You can choose it in the protocol selection on the Internet dialog.

The native Google Cloud Storage API is highly recommended and more efficient than using the older XML (S3) API described below.

You can still use the Amazon S3 compatible API for Google Cloud Storage. In that case, choose S3 as protocol, and specify your bucket like this:

bucketname@storage.googleapis.com

You can get your Access ID and Secret Key via the Interoperability tab sheet of the Cloud Storage Settings page
https://console.cloud.google.com/storage/settings

Please don’t choose unsupported features like Reduced Redundancy, as they will cause errors.

See also
https://cloud.google.com/storage/docs/migrating

Using Multiple Accounts With Same Cloud Storage

Posted on November 15, 2015 by in Best Practices, Documentation

When you create several profiles using the same cloud storage, you will notice that they automatically connect to the same account. This affects OAuth cloud storage such as Google Drive, OneDrive, DropBox etc.

However, it is also possible to use different accounts for different profiles.

Each cloud account needs to be identified on the Internet Protocol Settings dialog, using the Account (opt.) field. You could enter the email addresses there or anything else. What you enter does not directly mean anything, it is just a name under which the cloud authentication tokens are saved.

Then when you click the Browse button, an Internet Browser window will appear, asking you to authenticate the user. On this screen, the previous user may appear, so you need to click “Not me” or something like that in order to log the previous user out and log the new one in.

If a profile should be associated with a different account, just change the Account ID to something else, and you will have the chance to re-authenticate it.

If you want to completely re-assign your jobs, you can use the button “Forget Cloud Access Tokens” on the Program Settings dialog, tab sheet “Cloud”.

Google Docs protocol completely replaced with Google Drive

Posted on May 29, 2015 by in Best Practices, News

In May 2015, the older Google Docs API was shut down by Google, and it can no longer be used. It has been completely replaced with the newer Google Drive protocol.

To handle the situation, the new versions 7.17 and 7.20 beta 15 of Syncovery have been releaed. The Google Drive protocol can now fulfill all tasks that the obsolete Google Docs protocol could.

The main feature that had been missing before these updates was the conversion of native Google documents. This is now available, so that all existing tasks can be performed with the new Google Drive API.

Previous Google Docs jobs will automatically use document conversion where chosen. New jobs, and existing Google Drive jobs, need to have document conversion enabled if desired. The checkmark is on the second tab sheet of the Internet dialog. Note that the available file types for conversion have been updated on the Google Docs tab sheet.

Once a profile is switched over to the new Google Drive protocol, you will have to authenticate Syncovery in a browser window. The prompt will appear if you run the job manually in attended mode.

If you need to use several different user accounts in different profiles, this is entirely possible! Just make sure that each profile has a different Account ID shown on the Internet dialog. When the authentication page appears, make sure you log out of the current Google account and log back in with the next account and authorize Syncovery.

If you need to re-do the authentication, you can click the button “Forget cloud access tokens” on the Program Settings dialog, tab sheet “Cloud”.

Note that your Google accounts must “Allow users to install Google Drive apps”.

Older posts