ISY Backups What is actually backed up?

[ES1400]

I would like to know what is actually is backed up when backing up my 994i pro. I understand my applications are backed up, but what about the system part?

 

My concern is if I update to a new release, run it to unexpected problems can I restore to a previous release and actually get back to the previous application and system configurations exactly. Or will there other let overs from the new update? My fear is getting stuck after a update and not having a quick way back to being operational and forced to debug issues before getting operational.

 

Right now I'm using v4.2.18 and want to keep up UD development but have that fear of SYSTEM updates. 

 

ES1400

[larryllix]

You can backup, decompress the file and load it into your browser or editor. You can read everything there easily.

[LeeG]

The information in the ISY is in the Backup file.  ISY configuration, Variables, Programs, device nodes, perhaps other things in the ISY related to optional modules, etc.

 

Information physically in Insteon devices, PLM is not part of the Backup file.  Information to Restore devices, PLM is in the Backup file.

 

Upgrading from Official release 4.2.18 to Official release 4.2.30 should not introduce issues that would not allow going back to 4.2.18.

 

However, life is not an absolute.   There have been cases where a pre v2.0 PLM failed when an upgrade was done even though the upgrade did not modify the PLM.  There could be issues with device communication that exist at 4.2.18 but were not noticed.  Electronics fail at unexpected times.  I upgrade my ISY with every new image and have never found it necessary to return to a previous image.  Others that require a turn key environment from Insteon in general may find something to have an issue with.  

 

I would recommend taking a current ISY Backup and upgrading to 4.2.30.      

[Xathros]

It is my understanding that everything in the ISY is backed up with the exception of:

1. The firmware itself.
2. The contents of the web server (if you have the network module).

 

As long as you backup before upgrading, you can always reinstall an older firmware then restore a backup matching that older version of the firmware to get back to where you were.  The backup names include the firmware version number in them for your convenience.

 

-Xathros

[ES1400]

I guess you hit on the real issue in the reloading the firmware, I have to ask where to get and download older version of firmware that matches my older backups version if it's not included with the backups,

.

My experience has been the firmware (operating system) is separate from the application code. By by backing up my ISY system covers my custom application coding, the download from ud covers the new version of operating system. However, where can I download an older versions of the operating system to match one of my older back ups? I realize the need to regress to an older system and application is slim, but knowing how to restore a configuration to a known good point allows me to sleep at night.

 

Having said the above I assume the ISY is in three parts, A bootstrap loader or similar, operating system and then the application we the user develop or am I back in the dark ages again?

 

By the way, thanks for your responses it helps to have someone to work with and learn from their lessons learned.

ES1400

[stusviews]

ES1400,

 

Advanced search, search for Release in titles only.

[Xathros]

I guess you hit on the real issue in the reloading the firmware, I have to ask where to get and download older version of firmware that matches my older backups version if it's not included with the backups,

.

My experience has been the firmware (operating system) is separate from the application code. By by backing up my ISY system covers my custom application coding, the download from ud covers the new version of operating system. However, where can I download an older versions of the operating system to match one of my older back ups? I realize the need to regress to an older system and application is slim, but knowing how to restore a configuration to a known good point allows me to sleep at night.

 

Having said the above I assume the ISY is in three parts, A bootstrap loader or similar, operating system and then the application we the user develop or am I back in the dark ages again?

 

By the way, thanks for your responses it helps to have someone to work with and learn from their lessons learned.

ES1400

Most of the firmwares can be found here: http://forum.universal-devices.com/forum/15-current-release-betas-and-bug-reports/

 

If you can't find it there, Many of us archive them as we go along.  I'm sure I or another here can come up with what you need.  If not, I bet support would happily provide any previous version you desire.

 

-Xathros

[paulbates]

...

However, life is not an absolute.   There have been cases where a pre v2.0 PLM failed when an upgrade was done even though the upgrade did not modify the PLM.  There could be issues with device communication that exist at 4.2.18 but were not noticed.  Electronics fail at unexpected times.  I upgrade my ISY with every new image and have never found it necessary to return to a previous image.  Others that require a turn key environment from Insteon in general may find something to have an issue with.  

 

I would recommend taking a current ISY Backup and upgrading to 4.2.30.      

 

ES1400

Lee captured it perfectly. There always some risk involved. However, if you look at "the norm" here, people upgrade their devices regularly to get the latest and greatest, or to address particular problems. Part of "getting there" is to review the Software Releases & Updates section of the board as recommended by Stu and Xathros.  Releases and the process are documented well in the posts. Here a couple of approaches for you to consider

 

1) Wait for a version of firmware on the Software Releases & Updates section of the board to become an Official Release,and plan an upgrade around that. Official Releases are indicated in the forum on the thread for each version. A message will appear along the top of your Admin console when there is a newer, official release than what you are running. Wait for that. This approach keeps you reasonably current, and makes sure that others have tried the mid releases along the way and identified known problems. If you are having no problems, and are not looking for new functionality that you've read about, this is a reasonable approach to keep you current.

 

2) Adopt an non official release. If you are having a specific problem and a non-official release fixes it, or, you need new functionality in a non-official release, manually upgrade to one of these. Only use this method of you really need it, and then, wait a week or so for others to try it and report in.

 

I would recommend 1) as a normal practice. And as Lee indicates, no one can deliver a perfect upgrade scenario, It doesn't exist. However, having had my ISY for 8 months and upgraded maybe 4 times, I've not had any unrecoverable problems. UDI provides the proper level of change controls and versioning to my satisfaction, and they are always active on the board or available via support to help me out.

 

You'll need to find your comfort level between these two scenarios.  Also, backups have not failed me. when you make configuration, hw or ISY program changes, take a back up.

 

Paul