I'm currently working on the backups of my solutions and I'm having problems with specifying the location of the backup. It peforms a backup perfectly fine when the backup location is specified to be the default location. I want to backup it up on a different volume.

When I specify the location of where the backup should go besides that of the default, it never runs. I get a "Disabled" during it's scheduled run. The schedule window does in fact say that my backup locations are valid paths. Is there something that I am missing in regards to setting and scheduling my backups.

The location where I would like the backups to go are in a different volume that is a stripped volume. I am not sure if this would make any difference at all.

Thanks.

It should back up to the volume as long as it is assigned a drive letter. You can't use //servername/sharename.

HTH

John

i'm having this exact same issue...

i can't assign my drives letters because i'm not on a windows operating system.

filemaker 7 server.. running on mac os x server 10.3.5 on a G5 dual 2.0 with a gig of RAM. same exact problem as described in the first post. has anybody else seen or experienced this?

i really need this fixed!

- j

If the files are in any location other than the default location, you must manually do a "Get Info" on the database file. Under "Ownership & Permissions" specify fmsadmin as the "Group" and "Read & Write" for "Access." The schedule is being disabled because FM Server can't write to the specified location.

HTH,

Colin

I am having the same problem. I want to back up my databases every hour to folders that are named 01, 02, 03, etc. Even when I create these folders as subfolders of the default backup location, backup does not work. BTW, the path is displayed as being valid. And the permissions are set right.

What is the worst though is that when a backup is not possible, FMP Server clandestinely disables that backup script (by unchecking the box) without notifying me. I am unable to check the server every day and I have encountered loss of data because of this.

I am fed up with having to spend time after time on workarounds for features that FileMaker has not programmed well or has simply forgotten. But here is mine: use a shell script to copy the original files to a backup location and activate it with a cron job (works only on Mac and Linux though). The such backed-up databases are a little corrupt but they self-recover upon opening.

I would never use a file that was copied while still open. You may be able to recover the file but later on find some corruption getting into your system.

FMS 5.5 had this backup problem: it was unable to backup a file that was hosted on a volume other than the volume with the FMS application or to another volume or when the files were hosted on a RAID volume. Only solution was to have the application and data on the same volume, back up to that volume then move the back up files to another volume via AppleScript.

I have no experience in FMS 7.