Premise Question about Configuration Backup

Motorola Premise

kmitchell

Member
I found some topics in the help file that talk about backing up the server configuration and I just want to verify that I understand this correctly.

First of all, what I want to do is make a "Backup" of my Premise server configuration so I can do a "Reset" and experiment a bit. I then want to do another "Reset", and then I want to "Restore" to the original configuration.

Based on this I would:

1. Select "Backup to Client"

2. Do a "Reset"

3. Do whatever a want to do as an experiment.

4. Do another "Reset"

5. Do a "Restore from Client" and select the file I saved when I did a "Backup to Client".


Is this correct?

Thanks,
Ken
 
When you perform a "Restore from Client", Builder will automatically perform a reset (i.e. the existing data is purged and the new data is imported) ... so you can skip step #4.

BTW, Be sure to individually export all of your custom Modules. If you tweak anything in the Plugins, Automation Browser, Themes, etc then you'll need to export them as well. Life is easier if you can restore things in bits and pieces rather than one big chunk.
 
The Backup directory under SYS also has 'limited' backup capabilities. It acts as a 'checkpoint' as to when changes are made to the last configuration. When you have totally messed Premise up (Personally, I wouldn't know), you can use one of the backupxxx.xdo to get back to he previous 'good' configuration. You can do this by going into the time period you think was still good. Rename that backupxxx.xdo to slserver.xdo, then replace the slserver.xdo under the schema directory.

Its a kludge, but like all good kludges, it works.

Definitely heed 123's advice. Make sure you export your module(s). Or else you'll have to find out if this kludge really does work....
 
When you perform a "Restore from Client", Builder will automatically perform a reset (i.e. the existing data is purged and the new data is imported) ... so you can skip step #4.

BTW, Be sure to individually export all of your custom Modules. If you tweak anything in the Plugins, Automation Browser, Themes, etc then you'll need to export them as well. Life is easier if you can restore things in bits and pieces rather than one big chunk.

So are you saying that a "Backup to Client" doesn't back up everything? All I want is a snapshot of the server configuration so I can go back to that same configuration later. Are custom modules not saved as a part of a backup? Is the tweaked code for the standard modules not saved as a part of the backup?

I understand the reason behind exporting individual custom modules so you can import them individually but I think I'm confused about Backup and Restore.

Thanks for being patient,
Ken
 
"Backup to Client" makes a complete copy of everything. You don't have to take my word for it; try it.

Exporting your Modules is a good practice; it is handy to have a copy of your custom modules for your own use and for sharing with others. Plus, if you modify and render a module completely FUBAR, just delete it and import the exported copy. This is much faster than restoring from a complete backup and doesn't cause the Premise Server service to restart.

Eventually, you'll start modifying standard-issue modules, like the AutomationBrowser and Plugins, and then you'll definitely want to export your customized version.
 
Backup to Client is the right way to maintain good Config management....and exporting individual modules is a better way to keep you from going insane...

Case in Point.

Yesterday I was making some changes (adding sone Insteon logic)..ran into a snag (has anybody ran into a unrecoverable break?), and had to restart. My last backup (backup to client) was a few days old (shame on me). It restored perfectly. EXCEPT it was missing a couple of updates I had made to modules. I imported the copies I had previoulsy made. And bingo! A completely restored Premise...

As I'm writing this...do any of the other HA solutions provide such a robust backup and restoration method?
 
Back
Top