Jump to content

Question about "rolling back" to previous IoX


johnnyt

Recommended Posts

Let's say I upgraded to latest IoX (using AC "Upgrade Packages" button) and it resulted in a major bug so I want to go back while waiting for a fix to be released. I have a backup from just before the upgrade and can restore it but does it actually go back to the IoX (n-1) version on the backup? 

If YES, what are the risks related to having upgraded the underlying OS components and PG3/PG3x but being a version behind with IoX? (Would newer OS/PG3 stuff be mostly backwards compatible?)

If NO, it doesn't go back to IoX n-1 that's part of the backup, given there isn't a way (like there was with 994i) to download an older version of IoX, does that mean there simply is no way to go back?

 

Link to comment
2 hours ago, johnnyt said:

If NO, it doesn't go back to IoX n-1 that's part of the backup, given there isn't a way (like there was with 994i) to download an older version of IoX, does that mean there simply is no way to go back?

No, restoring a backup does not roll back the firmware upgrade. At this time I've not seen any ability from UDI to roll back on the Polisy/eisy. You would probably need to open a support ticket and see if there is an internal method that they could supply, but I think even UDI had commented that it was not an option currently to "roll back". 

If an update created a "major bug" that impacted lots of users there would probably be a quick fix update. 

At present the "Upgrade Packages" button updates anything that is released by UDI. So if you want a PG3/PG3x update you use the same method. It would also then potentially update the IoX version as well. The two are not mutually exclusive for methods for updating. It's apparently an effort to keep users on the latest versions of both IoX and PG3x as each release fixes something or adds features. (So you wouldn't necessarily be a "version behind" if you're updating.)

Link to comment
40 minutes ago, Geddy said:

If an update created a "major bug" that impacted lots of users there would probably be a quick fix update. 

The key part of that statement is "that impacted lots of users".

For the bug I'm thinking of currently in 5.7.0 (still being reported as occurring) that also occurred in 5.6.4 and enables all programs, it appears it's not impacting enough users to generate a fix given it's been 18 days since release of 5.7.0 plus a month before that for 5.6.4. But this bug is absolutely catastrophic  for someone with 1200 programs of which 350-400 are supposed to remain disabled (and long before that number of programs is reached).

While UDI did help when it happened to me in August (running 5.6.4), it was a major disruption to have to drop everything I was doing and had planned in order to, first of all troubleshoot/find/report what had messed up my automation big time, then try to recover with UDI (during their business hours in a different timezone) one email at a time, then make myself available to allow them to log into my system and sit there while they investigate and do the repairs. Perhaps they don't mind the cost of not being able to roll back but I did.

While one can adopt a plan to always delay upgrades and read the forum carefully before doing one (and that's what I am/will be doing) that too has a cost, and it still doesn't provide any assurances I won't run into a catastrophic issue UDI didn't fix because there aren't enough people impacted.

There seems to be so many moving parts that make things so brittle you'd think there would be value in having the ability to roll back. Maybe I'll put in a feature request for an OS snapshot capability or a system imaging utility that one can run before an upgrade. 

 

Link to comment
Guest
This topic is now closed to further replies.

×
×
  • Create New...