360Works MirrorSync 6 Makes FileMaker Synchronization Easy

360Works announces MirrorSync 6, the easy-to-use FileMaker data replication tool can quickly and seamlessly sync an offline database running on FileMaker Go or FileMaker Pro with a database hosted by FileMaker Server. It can sync various configurations of SQL databases, such as MySQL, Salesforce, Amazon DynamoDB or Redshift, and WordPress with FileMaker. This new version also makes it very easy to synchronize two FileMaker Servers to handle mission critical tasks like server clustering for load balancing and data disaster recovery.

 

 

Jesse Barnum, President of 360Works, says “MirrorSync 6 is the most major change since version 3. One of the biggest features is that MirrorSync can now automatically detect all new fields and tables.” In version 6, there is no need to re-configure or re-paste script steps when you have solution changes (for client-to-server sync, as well as server-to-server).

 

Overall, the MirrorSync configuration client and sync management has been greatly improved. Creating and editing configurations is much faster, especially for many tables. Sync status updates are more responsive, and configuration changes can be made without canceling active syncs. New fields and layouts are automatically detected and added to the sync. Auto-detection of primary keys, creation / modification timestamps, and writebacks has been greatly improved. In addition, the configuration client no longers requires Java to be pre-installed, and is signed and notarized for compatibility with the latest versions of Mac OS X without annoying security pop-ups.

 

Automatic File Transfers Between Servers:
When setting up a server-to-server sync for the first time, you no longer need to manually download, copy, and upload the databases between the servers. Just install MirrorSync 6 on both servers and click the ‘sync now’ button. MirrorSync will transfer the files (even for multi-file solutions) and run the initial sync.

 

Automatic Version Update Between Servers:
If you’ve used MirrorSync 4 or 5, you’re familiar with the automatic update feature, which automatically sends database updates to users in the field. MirrorSync 6 now uses the same approach for server-to-server syncs. Just modify a single calculation field, and MirrorSync will replace the database on the spoke server with a new version after the next successful sync. You can even schedule this feature, so that it runs overnight without disrupting connected users.

 

MirrorSync 6 Makes Syncs Safer:
Deletion scanning now runs two separate checks to ensure a record has been deleted before deleting on the other side of the sync. Checks have been added to make sure that no client record exists in the MirrorSync table before downloading a copy for the spoke to sync. Recover mode is now more discerning about which records to re-write after a previous failed sync which helps to prevent situations where recovery could cause a large number of records to be modified. Lastly, there have been multithreading improvements for storing and accessing the internal sync database for better reliability.

 

Robust Enough for the Largest of Files:
For users with large databases, MirrorSync now utilizes streaming when reading from FileMaker Server and Pro/Go. This allows fetching data of unlimited size, while reducing RAM requirements.

 

MirrorSync now supports custom location for temp files. This is particularly important when using the database download feature with very large databases; you can now store these temporary copies on an external volume with more free space than the boot drive.

 

Easy Migration:
After upgrading your existing MirrorSync 4 or 5 installation, existing offline databases in the field will continue to be able to sync with the new MirrorSync 6 server. You can utilize MirrorSync’s automatic version update feature to update these users to the latest version after completing a sync with their older version.

 

Notable Features in MirrorSync 6:

  • Automated deployment and version management for server-to-server syncs * Now uses the Data API (instead of XML or xDBC)
  • All new MirrorSync script, re-written to support new features in FileMaker 17 and later
  • Unlimited tables
  • Leverages new FileMaker features for much faster container field syncs
  • Configuration client is now a standalone application that does not require Java to be installed
  • Added support for Get( UUIDNumber ) primary keys
  • Added support for the iPod touch (which is a great and inexpensive option for offline data collection)

MirrorSync 6 is available now. You can download the software instantly from mirrorsync.com and start syncing with the new improvements. MirrorSync is free for 1 FileMaker Pro/Go device, with additional devices priced at $8-$95 per device depending on quantity. This price is for a single FileMaker solution, with addition solutions priced at $200/each, and server-to-server syncs priced at $1,600 – $2,000 depending on the types of databases. All prices are one-time costs, not annual.

Comments are closed.