We’ve recently launched SnapBack, a method custom-crafted for FileMaker backups. It takes automated, instant snapshots of your FileMaker solution and the important aspects of your environment configuration.
Within the Soliant.cloud® environment all backups are handled by a method we refer to as “SnapBack.” This custom integration leverages the capabilities of Amazon Web Services (AWS) Snapshots and the Soliant.cloud infrastructure. SnapBacks are designed to eliminate “paused” database time, reduce data loss exposure, optimize for cost reduction, and leverage capabilities of cloud computing. Snapbacks do not rely on FileMaker Server backup schedules. However, should you prefer to additionally have these, each of you can capture these as part of the Snapback process.
Benefits of SnapBack
- Reduces backup times for FileMaker databases to several seconds
- Eliminates the need for additional volume space required to store backups
- Reduces exposure to data loss by providing hourly backups with no interruption
- Contains FileMaker Server Documents data, OS Level Scripts, Web Server files, FileMaker Plug-Ins, and the FileMaker Configuration
- Available for your instance with access via secure FTP using your provided account credentials
- Drastically reduces costs through a tagging system allowing us to assign costs for only the time a SnapBack is mounted
- Provides the Soliant.cloud administration team tools to better manage solutions and reduce costs
How do SnapBacks work?
Soliant.cloud Snapback utilizes AWS EBS snapshots in combination with multiple AWS services and dynamically enforced retention policies. It provides access to specific points in time, on demand.
We use application logic to manage snapshots to back up your data. The resulting system provides not only a primary backup model but also an effective disaster recovery strategy. We store each SnapBack in the highly redundant AWS S3, which boasts 99.99999999999% reliability.
SnapBack Retention Schedules
SnapBacks are set up by default on every Soliant.cloud instance and run every hour on the hour. Retention includes the following:
- Most Recent 24 (The last 24 hours of SnapBacks)
- 7 Daily (The “last” SnapBack for each of the last 7 days)
- 4 Weekly (The “last” SnapBack for each of the last 4 weeks – Saturday Night)
- 3 Monthly (The “last” SnapBack for each of the last 3 Months – Last Day of the Month)
How do I get access to a SnapBack?
Our customers can access their SnapBacks using a self-service method on the Soliant.cloud Client Portal. A list of available SnapBacks gives you the ability to attach a SnapBack to your instance, and you will be notified when it becomes available. The requested SnapBack will appear on your FTP site as a Virtual Directory with the Date and Time of the SnapBack.
To learn more, please see the “Secure FTP Access to your Soliant.cloud FileMaker Server” knowledge base article.
What if I want to use the FileMaker Backup Schedule too?
There are no FileMaker Backup Scripts setup by default. However, you can specify any backup scripts using the FileMaker Server Admin Console. These backups are directed to the default FileMaker Server backup directory.
Note the following:
- If you configure a backup schedule in FileMaker Server, be sure to have enough free space to store your backups in addition to your hosted files.
- You can always access the default backup directory via secure FTP. See “Secure FTP Access to your Soliant.cloud FileMaker Server” knowledge base article.
- The Snapback also captures any FileMaker Server Backup in the default location.
- More than one copy is not recommended, since it adds to Snapback size
- If you require a clone, you can schedule a backup in FileMaker Server and check the option to save a clone. This will require space for at least one backup on disk.