News RSS feed for this section

Google Docs protocol completely replaced with Google Drive

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”.

Syncovery 7 Released

The new version 7 is available for Mac and Windows!

For more info, please see www.syncovery.com/syncovery7/.

DropBox, Google Drive, Box.net, OneDrive, Rackspace All Supported

The latest Windows version 6.55 supports these new cloud services:

DropBox, Google Drive, Box.net, OneDrive, Rackspace

Services we have been supporting for a longer while include:
Amazon S3, Amazon Glacier, Microsoft Azure, Google Docs

In addition, any cloud service that can be accessed via WebDAV, FTP, or SSH/SFTP can be used.

Google Drive is essentially a replacement for Google Docs. It will basically see the same files, so you could simply switch an existing profile over from Google Docs to Google Drive. However, there are differences regarding native Google Docs documents and document conversions. Google Drive has no conversion options. An advantage of Google Drive is that it can retain the Last Modified timestamps of files that you upload with Syncovery. Google Drive also implements the choice of using the Recycle Bin for deleted files or not.

Because Google Drive works differently with converted documents, it may not be able to replace the Google Docs API in some cases. Both options are still available in the protocol selection. When you switch protocols, please check if everything works correctly with manual runs of your jobs before automating them.

v6.40 (Windows) adds support for SkyDrive

Starting with version 6.40, the Windows version of Syncovery supports SkyDrive from Microsoft.

SkyDrive offers some free online storage, which has made it popular. You need to sign up for it with Microsoft under skydrive.live.com. If you already have a SkyDrive account, you can also see your files on that web site.

To sync with SkyDrive using Syncovery, please choose your local folders on the left-hand side, and click on the Internet button for the right-hand side. Then, choose SkyDrive as Internet Protocol and specify the folder where the data should be stored. You should also specify your SkyDrive username and password here.

Even though your data is uploaded via secure https with SSL, you may want to use zipping and encryption for your files. To keep a constantly updated mirror of your data, we recommend using the option “Zip Each File Individually”.

With SkyDrive, the “Last Modified” and “Created” timestamps of files can be preserved, so Filename Encoding is not necessary.

Additional cloud services will be added in the near future. Feel free to send your suggestions to info@syncovery.com!

Works on OS X 10.9 (Mavericks)

Syncovery works fine on Apple’s new operating system, OS X 10.9 (Mavericks).

To install it, you need to go to the Mac OS System Preferences, Security & Privacy, and specify that you want to allow apps downloaded from: Anywhere.

v6.35 (Windows) adds support for Rackspace Cloud Files

Syncovery for Windows now supports synchronizing your files with Rackspace Cloud Files. This is the first of a series of new cloud services that will be supported in the near future.

Cloud storage allows you to upload as much data as you need, paying only for the storage that you are actually using. It is a highly recommended storage location for your online backups. You need to sign up with the cloud storage provider, and then set up a profile to upload your data. Choose your local folders on the left-hand side, and click on the Internet button for the right-hand side. Then, choose the protocol you want to use (for example: Rackspace), and specify a container and folder where the data should be stored. You should also specify your Rackspace username and password (access key) here.

Even though your data is uploaded via secure https with SSL, you may want to use zipping and encryption for your files. To keep a constantly updated mirror of your data, we recommend using the option “Zip Each File Individually”.

Due to the nature of Rackspace Cloud Files, the “Last Modified” timestamp of your documents cannot be preserved. Therefore, we recomend to use the “Filename Encoding” feature of Syncovery. This adds the timestamps to the file names when uploading, and restores the original names and timestamps when restoring. You will find this checkmark on the Versioning tab sheet, as well as on the Internet dialog.

Additional cloud services will be added in the near future. Feel free to send your suggestions to info@syncovery.com!

Amazon Glacier Backup

Since version 6.20, Syncovery can upload files to Amazon Glacier. To set up Glacier as the destination, click on the Internet button for the right-hand side and choose Glacier as the Internet Protocol.

Amazon Glacier is intended for long term archiving and backup with the expectation that most operations are uploads and not downloads. Downloads should be a rare exception, since they can be extremely slow. To download a file, Syncovery needs to initiate a job with Amazon Glacier, and even with small files, it takes at least three hours for Amazon Glacier to retrieve the item. The same is true for file listings. Therefore, Glacier cannot be used for two-way synchronizations. It is intended only for backing up and archiving.

Please be aware that there is a download fee from Amazon if you download more than 5% of your data per month (or something like that). It seems that in some special cases, the download fee can be extreme. If you intend to make a full backup and restore for testing, please read the fee schedule closely, and also read articles such as this one:
Is There a Landmine Hidden in Amazon’s Glacier?


Two methods to use Glacier

  • Choose S3 inside our software, and use a lifecycle rule in S3 to move files to Glacier to reduce costs. See the Amazon Web Services Blog
  • Choose Glacier directly in our software. The rest of this article describes this method.

Because there is no quick way to get a file listing from Glacier, Syncovery maintains a local database with the information of all the files on Glacier. This database is automatically maintained and it is independent from the checkmark “Cache Destination File List”. Therefore, with Glacier, there is no need to use the caching option. The local databases used for Glacier are separate for each vault, but shared among all profiles. When you create a new profile that accesses an existing vault, it will alraedy know the vault contents, if the vault has been used on the same machine.

Glacier also cannot rename items which have been uploaded. When you rename or move files on the local side, they have to be uploaded again.

In version 6.20, the download process is still inefficient if you need to download many files. It will initiate the download job for each file and wait for it to complete, then download the file, and then proceed to the next file. You can specify a number of files to copy in parallel in this fashion (on the Files tab sheet), but the limit is 30. So, you can download up to 30 files in 3 to 5 hours, but downloading 300 files will take 30 to 50 hours. This limitation will be removed in a future update.

In light of this, if there is a chance you will need a complete restore, it may make sense to use “Zip Packages” with many files per zip archive, instead of uploading individual files.

This information will be updated as support for Glacier is optimized and more experiences are made with Amazon’s new service.

Mountain Lion Compatibility

A Mountain Lion compatible update of Syncovery is now available. The version number must be 6.03 or higher.

To be able to continue using your old configuration and profiles, please use at least version 6.04 or higher.

The migration wizard should appear automatically, or you can invoke it via the File menu. You can also manually import config files via the File menu.

Since version 6.04, no special action is required any more to migrate your settings.

Syncovery 6 has been released

Version 6 has been released in mid-2012, under the new name Syncovery! After one year of development, we are confident that the improvements will be great to have for all our users and customers. Version 6 uses new registration codes and you can order your license or upgrade from Super Flexible File Synchronizer. Many customers will receive a free upgrade, if their license purchase was within the past two years.

The list of new features can be seen here.

If you wish to upgrade, please install Syncovery on top of your current version and it will show the migration wizard.

For those customers who are using the ExtremeSync Remote Service, please note that you need to replace it with the new Syncovery Remote Service and update all clients and servers at once, unless you want to keep both Remote Services running during the transition period.

Everybody can now upload “any file” to Google Docs!

Apparently Google has removed a limitation and it is now possible for all Google customers to upload “any file” to Google Docs. If you would like to try it, make sure you have the latest software version from our web site.

Up until at least mid-2011, our Synchronizer could only upload converted files unless the customer had a Google Apps Premier account. Now this problem is completely gone.

That is really great news I think!