take care that Your backup script does not copy any files in use - just copy the backups from FMS. If Your backup doesn't run at the same time (should run after the FMS backups..) as the FMS backups, it seems save
I personally don't use automator, I have a sync-app - but it does quite the same
I'd avoid using automator altogether.
In practice I tend to:
- Backup to local store on FMS machine
- Schedule a system level script within FMS Admin to run periodically to copy the backup files off to another location via rsync, ftp, or whatever. This gives the benefit of being able to manage everything within Filemaker Server Admin Console, with notifications etc.
If your Automator script is not running at the same time as the FileMaker backup and is not taking any files being used by the FileMaker Server at the moment, then it is OK.
One issue though: You need to know a few things:
- Did the FileMaker backup schedule run ... so that you are actually taking offsite copies of recent files?
- Are the files OK: Let FileMaker Server verify the backup files (setup in schedule).
- Did your Automator script run and succeed.
The first two controls can be done by letting FileMaker send you emails confirming that the backup schedule did run and that the files are OK.
The last one you need to set up with automator or some other tool.
And ... are you aware that the FileMaker Server script schedule setup allows you to let it run a system script after the schedule?
Consider letting this script move your files to an offsite destination.
Thanks James. I should should have looked at server for the backup task solution and will.