Hi All,

I'm using the FMServer Config 5.5 on an Xserve running Mac Server 10.2.8. I have two schedules set up to back up all databases to an attached RAID. One runs weekly and the other nightly. The Schedules window says that they are running when they should, but if I look at the file dates, they're from more than 3 weeks ago. I've tried altering the script to save to the Xserve's harddrive, but I get the same results.

Has anyone seen this behavior?

Thanks in advance,

Andy Mowrey

FMS 5.5 does not backup large databases from multiple volumes such as RAIDs or to a volume other than the one the hosted file resides on.

Andy:

It should work fine - I've got FMS 5.5 on OSX backing up to several volumes. It is possible that the menu item "Allow Schedules to Run" in FMServer Config has been unchecked. Looking in the Schedules pane, it appears that they'll run (the checkboxes are checked) but if the menu item is unchecked, the schedules don't run. I've seen this happen at one of my clients, and when I suggest that someone has unchecked it, they look at me like I'm a madman. So, either it is an odd bug, or someone is fiddling with the server.

-Stanley

FMS 5.5 does not backup large databases from multiple volumes such as RAIDs

Is this an OS X limitation? I've been using my Windows FM Server with a RAID array for years.

Something that has tricked me in the past: the files have to be opened in FM Server before they can be backed up in schedules.

I also back up all the time to a raid system adn multiple volumes. BUT I have noticed that mounting the volume can be the problem in X. Try reselecting the destination and see if the volume changes slightly (eg. "volume" to "volume-1" changes. THis happens all the time for me.

Why would you not keep the volume mounted? If you're backing up to it on a scheduled basis, you should keep the volume mounted at all times, or create an AppleScript which fires ahead of the scheduled backup and mounts the volume.

-Stanley

This was a problem in OSX FMS 5.5, and only with larger files, both in Gb size and number of records. Supposedly fixed in latest version but I never had any luck.