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.2.2 (2026-06-10) | Release Notes

Platform Download Size Checksum
VMware NAbox-v4.2.2.ova 1.3 GB db26e327406f7a169f39561c91339a21
QEMU (Experimental) NAbox-v4.2.2.qcow2 2.5 GB bf391fb1aa7043c384cc9f80040e0057
Hyper-V (Experimental) NAbox-v4.2.2.zip 1.2 GB bc9685e3ff37a1186e737d97543b6665
Update (All platforms) NAbox-v4.2.2.nbx 1.1 GB 4eab92e34036f89b726676e4433350c1

4.2.1 (2026-05-18) | Release Notes

Platform Download Size Checksum
VMware NAbox-v4.2.1.ova 1.3 GB 7b2400ec8a4553cc43d57c03c06bc842
QEMU (Experimental) NAbox-v4.2.1.qcow2 2.5 GB ebdbef7907104533571b6602ff8e8594
Hyper-V (Experimental) NAbox-v4.2.1.zip 1.2 GB d1cef8233376a5f8060a1dce3636e8c1
Update (All platforms) NAbox-v4.2.1.nbx 1.1 GB 87659d9be3b9081c086cc434504d0cb1

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-v4.2.2.ova
MD5 (NAbox-v4.2.2.ova) = db26e327406f7a169f39561c91339a21
$ md5sum NAbox-v4.2.2.ova
db26e327406f7a169f39561c91339a21 NAbox-v4.2.2.ova
> CertUtil -hashfile NAbox-v4.2.2.ova MD5
MD5 hash of file NAbox-v4.2.2.ova MD5:
db 26 e3 27 40 6f 7a 16 9f 39 56 1c 91 33 9a 21 
CertUtil: -hashfile command completed successfully.

3.5.4 (2026-03-09) | 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 (2026-03-09) | 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 (2026-03-08) | 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.