Feature Request - Backing up the FMS schedules

Feature request time. Yesterday I had an unfortunate incident where a client updated FMS and it became corrupted. Admin console would not login, we couldn’t really get it going unless a complete reinstall. What made it worse though is all the schedules were not saved prior to update and so we could not access them to restore. I had the painstaking process of restoring as best I could by looking at an older loadschedules.log and event.log for when they ran…

Is there any way the admin console action of saving schedules can be programmed? I couldn’t see a way via fmsadmin command line tool. It seems to be just in teh admin console but I do wonder if the admin console API has this ? Do you know?

If a feature like this were available in Otto, to perform nightly backups of the schedule config this would be awesome and another feather in your cap :slight_smile:

This is on our road map. Soon.

We are thinking we will back up everything that it would take to restore a server.

What do you think of that idea?

Todd

2 Likes

Hmm, well… I suppose you could back up everything but do we really need everything… I’m just not sure about that idea…

Kidding… of course it’s a bloody brilliant idea!

1 Like

All you need ist the preferences xml. Stop the server services completely, restore the preferences to a corrupted server and start it and everything works again.
Always backup the preferences before an update!

There is more that you need to backup besides the preferences xml. You need all the OttoFMS data as well, and a few other things.

Todd

In total? True. But to be safe in case of a corruption of the server due to an update I’ve found the preferences file does fix THIS issue. (Edit: If not please educate me because I’d rather be on the safe side)