Scheduled Backup to external volume

[Mike Owen]

Is there any reason why FM Server 8 should not see an external drive as a valid path for a scheduled backup?

I am trying to set up a scheduled backup in FMServer 8 to a mounted external drive (windows) from a server (OSX) using the path:

filemac:/Mounted Volume Name/Backup Folder/

but I can't stop it showing "Not a valid path".

[IdealData]

There is no support for aliases either - a clue?

I think the folder must be a "real" folder on the local machine only.

[Mike Owen]

Thanks IdealData.

Is this the last word? ... or does anyone else have any clues?

[Steven H. Blackwell]

This has been discussed in FM Foprums before, IIRC. External volumes are not supported in this fashion.

Make a local backup copy to the server hard drive, or better still to a logical or physical partition on the local server. Push that local copy of the backups out to external drives.

This is the recommended process, and it avoids the problems if the external drive is not mounted. If you are running FileMAker Server on OS X correctly, e.g. at the LogOut prompt, the drives don't mount anyway, IIRC.

Steven

[Mike Owen]

Thanks, Steven.

[Amazin1]

Why is this not supported? I have internal drives on our server to which i want to make back ups and you cannot even set a path to these internal drives. I did this with no problem in FM 6. This seems like a step backward. I have used FM for years because I didn't want to deal with the complications of SQL, etc. It now seems FM is heading down that path! Also, Steven what do you mean "Push that local copy of the backups out to external drives." Sounds like another complexity I and others do not need.

Jim

[Steven H. Blackwell]

What's past is past. You should have no problem sending the backup to an internal drive on the server. If you do, there is a configuration error, a permissions error, or both.

You have FMS make a local backup. You then push that copy out to elsewhere on the network for subsequent backup by whatever enterprise backup software you're using, such as Retrospect or BackUp Exec., etc.

Steven

[Jim Gill]

I really feel like Filemaker is missing the boat on this issue. Not being able to backup directly to an external drive is like driving your car without insurance. Yeah you can pay when you get in a crash but it is a lot nicer driving around with peace of mind. Also by "pushing out" the backup folder/files with an additional piece of software is adding another layer potential issues and is just plain redundant. Filemaker is all about getting rid of redundancy correct? Accessing/validating an external drive is a very basic networking scenario that all software/OS can do except Filemaker Server? Wow it sounds like the "no right click" on a Mac syndrome.

[Steven H. Blackwell]

I suggest that you read the White Paper on Backups provided by Wim Decorte and found here. It discusses this process in great detail.

FWIW, I believe on Windows that you can use the UNC name to access a share on a network file server. The entire issue of making remote backups as the primary backup destination is complex and requires careful planning and error trapping.

Steven