Date: Fri, 29 Mar 2024 11:18:27 +0000 (UTC)
Message-ID: <346036433.4117.1711711107005@skald.opmantek.com>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_4116_1824920252.1711711107005"
------=_Part_4116_1824920252.1711711107005
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
AB1-ABI4 Upgrade Pre-Flight Checklist
AB1-ABI4 Upgrade Pre-Flight Checklist
Approach
You can upgrade current server software or you can build new servers and=
migrate data; in-situ vs in-paralell respectively.
- in-paralell - this is the least risk option but requires additional res=
ources
- in-situ - suits single server installations with a single outage window=
.
=
Must Check before you start in-situ
Check each of the following items before upgrading in-situ.
- Are you on an older OS? e.g. Centos6, Debian 7 etc.
- upgrade all servers to newer distribution or create new server instance=
s and use the in parallel upgrade
- Does your server _lack_ plenty of extra disk and possible CPU to accomm=
odate both installs
- add extra disk capacity to allow copying of current data
- or use the in parallel upgrade and create new server instances with sim=
ilar disk capacity
- You have a test system and have tested the upgrade process or you have =
a complete snapshot of your current server with a tested restore
- Complete a test upgrade on a test server before attempting on live syst=
em
- Check down time for your service during the upgrade is acceptable, it w=
ill take time and if you have a multi server system all servers need to be =
completed before the complete service is restored.
- An in-paralell build would enable zero downtime and provide an opportun=
ity to test and confirm before migrating.
- Are you new to linux system administration and debugging
------=_Part_4116_1824920252.1711711107005--