Thanks for posting!
FileMaker Server does not allow back ups directly to a network drive. The recommended approach would be to back up to a local folder and then move the resulting back up to the network drive using a script or whatever method you see fit after the back up has completed successfully.
What if the hard drive on the server becomes corrupt or suffers major corruption. Then all your backups are gone and you can go home for the day/week/year...?
I find this disturbing that you are unable to make an offsite backup. If speed of the backup is an issue define a temp location to save the database to and copy it out to the remote location.
Can you at least schedule that as part of a task that is dependant on a backup task?
On the plus side we are working in a virtualized environment, in this case we can make an I-SCSI target and have the backups saved to a network location. The OS would not know that the drive is not local.
Yes, such a shame this feature is not included in FileMaker Server :(
I was able to setup a solution using Dropbox - Server will see it as a drive and save backups to that location (on windows at least, I know nothing about Mac). There are some limitations like file size and sync time but it gets the job done for me. Probably worth a try.