Jump to content
Sign in to follow this  
IndependentEdit

Retrospect 10.5 & FileMaker 13

Recommended Posts

Trying to use Retrospect 10.5 to backup FileMaker Pro 13 databases.  Whenever the backup script runs (backing up the database folder from the FMP server) it shows 3 execution errors, with the same three databases reported as "appearing incomplete."

 

Yet when I then run an immediate backup using the same script, the execution completes successfully.

 

Any ideas why?  Is this an issue I need to be concerned about?

 

Share this post


Link to post
Share on other sites

When you back up any kind of database files, you need to be sure that the files are closed at the time of backup and that no user (or the application itself) is able to modify any record. It sounds like something may be changing the database files during your scheduled backups.

 

If you can't lock out the database files during the backup window, you will need to generate a copy of each database and back up the copy.

Share this post


Link to post
Share on other sites

Script filemaker to stop the database, make a duplicate cold copy (in another directory), and then re-open the original database

 

and then

 

set retrospect to backup that duplicate copy

Share this post


Link to post
Share on other sites

Dantz/EMC/Roxio/Retrospect/whatevertheyarecalledtoday produce various addins for Retrospect to backup other makes of database. Considering their loooooooooong Mac history it is amazing and very disappointing they they do not write an equivalent addin to automate backing up FileMaker Server databases.

 

Other than the script approach suggested by Pete another approach is to use the standard ability in FileMaker Server to do scheduled backups to another folder, and then tell Retrospect to only backup that folder and not the 'live' databases.

 

On a related topic, the same issue will apply these days to PostgresSQL databases as used by Apple's Wiki and Profile Manager software, and - if you use it MySQL databases. Again these are extremely common types of database even in the Mac world let alone Linux world and it is again a major failing and oversight for Retrospect not to provide their own solutions for backing up such databases.

 

Just noticed, while it might be a less common scenario, even those addins for backing up databases that Retrospect do have are kept only for the Windows version making the Mac version a second class product. This is inexcusable, if they designed it properly addins should be platform agnostic.

Share this post


Link to post
Share on other sites

Just crate a backup script from the Filemaker Admin interface and then tell Retrospect to back those files up. I have Filemaker set to backup the databases hourly and once each night and have Retrospect backup the nightly backup folder. Works great and no additional scripting is needed. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×