Thread Info
  • Locked Locked
  • Replies 4 replies
  • Subscribers 5 subscribers
  • Views 2412 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

restore trick after update why? Rebuild from ISO why?

maygyver

Hello all,

I have seen serveral advices to do a restore direct after an update/upgrade, why? I had no need to do it in 16 years Astaro/Sophos UTM.

Even I was never told to do a rebuild from ISO from support and I had no need to do it. Everytime there was a Astaro/Sophos patch sooner or later.

 

We should discuss this. May be I missed something.

 

May



This thread was automatically locked due to age.
Parents

  • Hi May

     

    - To do a restore of a backup after an update is also new for me, maybe some  files could get corrupted and will be rewritten with the restore?

    - Rebuild from ISO is often the only way to get a cluster back to life: One node updated to (bad) version X the other remains  on (good) version X-1; the only to go back to X-1 is re-imaging. (If the quality of the Sophos-Patches would be good this wouldn't be neccessary)

     

    Regards, Peter

  • in reply to pebo

    The rebuild from iso in case of a broken HA or a bad update and switching to old version X-1 is normal.

    But when my "one" or within HA both are running fine, is a rebuild really useful?

    may

  • in reply to maygyver

    maygyver said:

    But when my "one" or within HA both are running fine, is a rebuild really useful?

    No, if it runs fine the files on the box should be same like the ones in the  iso-image  - except you deployed a faulty update or changed files/configuration by using console root-login and you need a clean system again ;-) 

  • in reply to maygyver

    Guessing based on what I've seen here, May, it seems that sometimes a configuration file upgrade "breaks" the configuration.  This seems to be because there was a hiccup when the Up2Date was modifying settings and/or objects.  Guessing again, I would say that this "breakage" happens to less than one in a thousand UTMs, so it's not surprising that you haven't experienced it.

    All I can say is that it has helped a few people here fix a problem that appeared immediately after an Up2Date.  I only recommend it when a new issue appears unexpectedly in a configuration in a configuration that had worked perfectly before an Up2Date.

    In any case, it's a "free" test that's non-destructive because you can immediately go back to the new configuration if restoring the pre-Up2Date doesn't resolve the new problem.

    Re-imaging from ISO is necessary if it's the programs that are broken instead of the configuration.  Again, it's not something that I've seen here often.

    Cheers - Bob

Reply
  • in reply to maygyver

    Guessing based on what I've seen here, May, it seems that sometimes a configuration file upgrade "breaks" the configuration.  This seems to be because there was a hiccup when the Up2Date was modifying settings and/or objects.  Guessing again, I would say that this "breakage" happens to less than one in a thousand UTMs, so it's not surprising that you haven't experienced it.

    All I can say is that it has helped a few people here fix a problem that appeared immediately after an Up2Date.  I only recommend it when a new issue appears unexpectedly in a configuration in a configuration that had worked perfectly before an Up2Date.

    In any case, it's a "free" test that's non-destructive because you can immediately go back to the new configuration if restoring the pre-Up2Date doesn't resolve the new problem.

    Re-imaging from ISO is necessary if it's the programs that are broken instead of the configuration.  Again, it's not something that I've seen here often.

    Cheers - Bob

Children
No Data