Difference between revisions of "Debian Upgrades"

From Roaring Penguin
Jump to: navigation, search
Line 40: Line 40:
  
 
<div style="float:right; clear:both; margin-right:0.5em">[[Support Wiki | [Home]]]</div>
 
<div style="float:right; clear:both; margin-right:0.5em">[[Support Wiki | [Home]]]</div>
[[category:All]][[category:Upgrade]][[category:Management]]
+
[[category:All]][[category:Upgrade]]

Revision as of 14:00, 24 July 2017

Important!

Upgrades to Debian MUST be done one version at a time!

You can find your current version with the command:

 cat /etc/debian_version

We currently provide packages for versions:

 5.x Lenny   (CanIt packages discontinued as of 10.1.5, unsupported by Debian since February 2012)
 6.x Squeeze (unsupported by Debian since February 2016)
 7.x Wheezy  (Debian support ending May 2018)
 8.x Jessie  (Current CanIT appliance version, Debian support ending TBD)
 9.x Stretch (CanIt appliance images coming soon, Debian support ending TBD)

Distribution Upgrade Instructions

Our ISO installations provide a unified upgrade command which can be provided the target version codename in order to initiate a distribution upgrade. That said, each version change has specific extra steps to consider, such as upgrading the database and fixing problems with caused by the upgrade.

The instructions for each are provided below:

Lenny to Squeeze

Squeeze to Wheezy

Wheezy to Jessie

Jessie to Stretch

Work in progress. Stretch support is expected with the next CanIt release. Upgrade instruction will follow.

Migrating to a new appliance

If you need to upgrade multiple versions it can actually be faster and safer to simply build a new appliance with our current ISO then follow the migration instructions as documented in Chapter E.5 of the Administration Guide.

Upgrade and Migration Support

You may wish to contact Roaring Penguin support staff to have us perform the upgrade or migration on your behalf. Normally these arrangements are made within our regular working hours (9AM-5PM Eastern), so it is best to try to schedule at time that cause minimal disruption. Upgrades are typically fairly quick, only requiring somewhere between 5 and 20 minutes of downtime for each version. This will be longer if a database upgrade is required.