Skip to content

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.

4.1.2 (2026-02-03) | Release Notes

Platform Download Size Checksum
VMware NAbox-4.1.2.ova 1.1 GB 4da9ef693ace65b031055c7cfb1278b7
QEMU (Experimental) NAbox-4.1.2.qcow2 1.1 GB 1a71ffa832304dc6db3e884160e142db
Hyper-V (Experimental) NAbox-4.1.2.zip 1.1 GB 063403b155a9cc402f06fe93f113744c
Update (All platforms) NAbox-4.1.2.nbx 922.5 MB 52af1a16811477a2f3ca6ec3a20b8eb2

4.1.1 (2026-01-28) | Release Notes

Platform Download Size Checksum
VMware NAbox-4.1.1.ova 1.1 GB f07c50c8cf3860edb0959d02e138e3cb
QEMU (Experimental) NAbox-4.1.1.qcow2 1.1 GB c746c87d16ece40c81d4f2a4a0f3e6fa
Hyper-V (Experimental) NAbox-4.1.1.zip 1.1 GB 226896c426a54371df65993f80aff83b
Update (All platforms) NAbox-4.1.1.nbx 922.0 MB e5b348c1ef316ed6afdeb76b37653ccd

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.1.2.ova
MD5 (NAbox-4.1.2.ova) = 4da9ef693ace65b031055c7cfb1278b7
$ md5sum NAbox-4.1.2.ova
4da9ef693ace65b031055c7cfb1278b7 NAbox-4.1.2.ova
> CertUtil -hashfile NAbox-4.1.2.ova MD5
MD5 hash of file NAbox-4.1.2.ova MD5:
4d a9 ef 69 3a ce 65 b0 31 05 5c 7c fb 12 78 b7 
CertUtil: -hashfile command completed successfully.

3.5.4 (2024-08-12) | Release Notes

Platform Download Size Checksum
VMware NAbox-3.5.4.ova 3.6 GB 6271f5f19bbe312e87afcfb4560830b1
Update (All platforms) NAbox-3.5.4.update 1.1 GB 1317497c1ee034b88ce3602aa2ef8e3f

3.5.3 (2024-05-29) | Release Notes

Platform Download Size Checksum
VMware NAbox-3.5.3.ova 3.6 GB c5f1984f0758a667fb7c9e986e349acd
Update (All platforms) NAbox-3.5.3.update 1.1 GB de3c25045bd5520446296053302e8d65
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.4.ova
MD5 (NAbox-3.5.4.ova) = 6271f5f19bbe312e87afcfb4560830b1
$ md5sum NAbox-3.5.4.ova
6271f5f19bbe312e87afcfb4560830b1 NAbox-3.5.4.ova
> CertUtil -hashfile NAbox-3.5.4.ova MD5
MD5 hash of file NAbox-3.5.4.ova MD5:
62 71 f5 f1 9b be 31 2e 87 af cf b4 56 08 30 b1 
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-18) | Release Notes

Platform Download Size Checksum
VMware NAbox-2.6.4.ova 1.0 GB ac5e6a9826445bfc15f6b74ba94896ef
Update (All platforms) nabox-2.6.4.tgz 496.3 MB 3330f70daeb989e0f3aef43821ba7fe7

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.