Valid Backup Path frustration

[Justin P.]

Trying to create a second backup schedule, and am getting stung here:

This path is valid:

filemac:/IS_Server_HD1/Users/administrator/Documents/

But this path is not:

filemac:/IS_Server_HD1/Users/administrator/Documents/FMS7_Backup2

I assumed permissions (Documents is admin admin, rwx------), but setting same as Documents folder, or changing group to fmsadmin rw- makes no difference.

Any advice?

(my advice for filemaker, please include a bloody file browser next time, so we don't have to mess with your filemac: path formats!)

Thanks for your help.

Justin

[Martin Brändle]

Add a / (slash) to your path.

In order that the backup is done, the directory should have admin:fmsadmin owner/groupship and drwxrwx--- permissions set.

Martin

[Justin P.]

Thanks for the fast response. I apologize for leading you astray

[Martin Brändle]

What's your version of FM 7 server? You should update to 7v03 and see if the problem persists. See also this FM techinfo article.

[Justin P.]

Thanks for the link.

I am indeed running 7.0v3, updated within a week of it's relkease.

I have always found Filemaker updates to be twitchy though, and this one is no exception: About Menu shows 7.0v3, while Info screenin Server Admin shows 7.0v1.

Driving me bonkers! Something so simple, should definitely not be so hard...

[dkemme]

I too downloaded and installed v3 update within a week and my FMSAdmin About... states v3. Could this be your problem, an upgrading problem? Did you have any difficulty with the updating process? Was the fmserver daemon stopped prior to the upgrade process? If so I would suggested reinstalling and reupdating (?sniglet) after insuring that the fmserver daemon is stopped.

[CTabor7873]

Having problems running a schedule to a network shared drive and a USB flash drive. Can someone please help. I can set to any internal HD but can't figure out anything else.

Thanks,

Collyn Tabor

[stevie.at]

I currently ran into the same problem...the path appears to be valid (including the slash), permissions are set right, all updates installed but FMS doesn't run it - I always get the error message saying that the folder is not writeable in the event.log

Did anyone figure that out in the meantime?

[QuinTech]

This may be a firmware or similar problem. I've noticed that with many Microsoft drivers, for example, a CD burner, a command-line interface is not supported. Thus, if your CD writer is the F: drive, then typing something like copy C:thisfile.txt F:*.* will not work despite the fact that this is a perfectly valid syntax.

If FMS is running something similar, it wouldn't surprise me that the necessary driver files are not present for writing to a USB drive. You may need to back up to a hard disk location and copy from there to the USB drive.

IMHO, a USB drive is not a good idea for backing up anyways. They're nice when you need to quickly transfer data to another computer, but far too volatile for backups.

HTH,

Jerry