Upgrading from NAbox 3.x
You cannot do an in-place upgrade from NAbox 3 to NAbox 4, you have to deploy a new virtual appliance.
You can migrate your data though, once both versions are running. Please follow the instructions in the documentation.
The migration copies your systems configuration and all metrics.
Upgrading from NAbox 4.0b2 and below
If you are currently running NAbox 4.0b2 or below, the upgrade will block on "Installation".
When it happens, log into NAbox with ssh and
run sudo upgrade
4.0.4 (2024-07-09)
OVA : NAbox-4.0.4.ova | 888.2 MB (md5 cb14ca5673d720af2ee9cef88ad656f5)
Update : NAbox-4.0.4.nbx | 776.0 MB (md5 182909645ce9b40a2232787422ab1e86)
Release Notes
4.0.3 (2024-07-03)
OVA : NAbox-4.0.3.ova | 1.4 GB (md5 1118efc05f393386e3546c988092cfc9)
Update : NAbox-4.0.3.nbx | 775.9 MB (md5 52557637ba6cfe0ce5a6581bf9fd1a0b)
Release Notes
Verifying checksum
It is recommended that you verify the checksum for the ova file to avoid issues while deploying the image into vSphere.
$ md5 NAbox-4.0.4.ova
MD5 (NAbox-4.0.4.ova) = cb14ca5673d720af2ee9cef88ad656f5
$ md5sum NAbox-4.0.4.ova
cb14ca5673d720af2ee9cef88ad656f5 NAbox-4.0.4.ova
> CertUtil -hashfile NAbox-4.0.4.ova MD5
MD5 hash of file NAbox-4.0.4.ova MD5:
cb 14 ca 56 73 d7 20 af 2e e9 ce f8 8a d6 56 f5
CertUtil: -hashfile command completed successfully.
3.5.3 (2024-05-29)
OVA : NAbox-3.5.3.ova | 3.6 GB (md5 c5f1984f0758a667fb7c9e986e349acd)
Update : NAbox-3.5.3.update | 1.1 GB (md5 de3c25045bd5520446296053302e8d65)
Release Notes
3.5.2 (2024-04-02)
OVA : NAbox-3.5.2.ova | 4.0 GB (md5 a7b0202e2911f8dc280ad08a853b9625)
Update : NAbox-3.5.2.update | 1.1 GB (md5 69534c447e0d8eba484d51463cca0da1)
Release Notes
Upgrading from NAbox 2.x
There is no upgrade path from NAbox 2.x to NAbox 3.x, the foundations of the OS are totally different (moving from Debian Linux to Alpine Linux).
Currently there is no way to batch import configuration or existing metrics, but it can be done manually.
Note that you are strongly encouraged to move your installation to NetApp Harvest 2 which has a different backend storage than NetApp Harvest 1.x (moving from Graphite to Prometheus).
A common practice when moving to NAbox v3 is to deploy the new virtual appliance, and let both running for a while until you consider having enough history with the new virtual appliance, then decomission NAbox 2.x.
Verifying checksum
It is recommended that you verify the checksum for the ova file to avoid issues while deploying the image into vSphere.
$ md5 NAbox-3.5.3.ova
MD5 (NAbox-3.5.3.ova) = c5f1984f0758a667fb7c9e986e349acd
$ md5sum NAbox-3.5.3.ova
c5f1984f0758a667fb7c9e986e349acd NAbox-3.5.3.ova
> CertUtil -hashfile NAbox-3.5.3.ova MD5
MD5 hash of file NAbox-3.5.3.ova MD5:
c5 f1 98 4f 07 58 a6 67 fb 7c 9e 98 6e 34 9a cd
CertUtil: -hashfile command completed successfully.
About Harvest 2.x
You need NAbox 3 to run NetApp Harvest 2.x. Please note that NetApp Harvest 1.x is no longer available from NetApp web site. If you just downloaded NetApp Harvest, you probably want to download NAbox 3.x above.
2.6.4 (2023-08-26)
OVA : NAbox-2.6.4.ova | 1.0 GB (md5 ac5e6a9826445bfc15f6b74ba94896ef)
Update : nabox-2.6.4.tgz | 496.3 MB
Release Notes
Verifying checksum
It is recommended that you verify the checksum for the ova file to avoid issues while deploying the image into vSphere.
$ md5 NAbox-2.6.4.ova
MD5 (NAbox-2.6.4.ova) = ac5e6a9826445bfc15f6b74ba94896ef
$ md5sum NAbox-2.6.4.ova
ac5e6a9826445bfc15f6b74ba94896ef NAbox-2.6.4.ova
> CertUtil -hashfile NAbox-2.6.4.ova MD5
MD5 hash of file NAbox-2.6.4.ova MD5:
ac 5e 6a 98 26 44 5b fc 15 f6 b7 4b a9 48 96 ef
CertUtil: -hashfile command completed successfully.