1 of 1 people found this helpful
I've been trying to track down some issues with other volume "snapshot" tools. AhSayOBM is a program I suspect has caused problems on 2 separate filemaker servers (2012 R2 in both cases) where something went wrong.
Apparently AhSayOBM doesn't allow you to omit folders from the backup process, or at least that was claimed by the IT contact at the company having the issue.
In both instances, we disabled that program entirely, and wrote a scheduled task that copies the filemaker backup folder to a different server so it can be backed up there.
2 of 2 people found this helpful
The main thing to remember is that FMS is not VSS aware so it will NOT put the files in a stable state when VSS runs.
That means that when you restore from a snapshot you WiLL get files that are 'improperly closed' at best and 'damaged' as worst.
So don't count on it as a tool in a FM backup strategy. It can still be used to restore the machine itself and the FMS install but not the files. The files would still have to be restored from a real FMS backup.
The procedure can be made safe but it requires coordination with the team that does the VSS. If you use fmsadmin CLI to pause the FMS files and then the VSS runs and then you resume the files using the fmsadmin CLI then the files on the snapshot will be in a good state.
All of this can be done from the CLI, including running the VSS. You don't want to get in a position where the VSS runs on its own schedule and you carefully try to time the FMS pausing/resuming to match that. It is going to be given that the timing will be off at some point and the expectation will still be that you have restorable files.
(Obviously pausing/resuming the files has an impact on the users; they won't get disconnected but their work will be suspended.)