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.0.8 (2025-01-03) | Release Notes

Platform Download Size Checksum
VMware NAbox-4.0.8.ova 964.3 MB 7e1651dd897efd9b9f1a1849c6fb40da
QEMU (Experimental) NAbox-4.0.8.qcow2 944.1 MB 6dbeebd8ccd4ec8f24ac501e9a18003c
Hyper-V (Experimental) NAbox-4.0.8.zip 906.5 MB 8429e1599ef6e684bb7ebe69c0af7671
Update (All platforms) NAbox-4.0.8.nbx 880.6 MB 0ccebb5897331d1edcc643ec0600863c

4.0.7 (2024-09-12) | Release Notes

Platform Download Size Checksum
VMware NAbox-4.0.7.ova 939.9 MB 434de9149ebf132e3c57be9dca3b2e1c
QEMU (Experimental) NAbox-4.0.7.qcow2 919.8 MB 894ecb97b12bc022fe943fbe7b9c446b
Hyper-V (Experimental) NAbox-4.0.7.zip 881.2 MB c5088727c1bb102a0b1a4e910ca486e0
Update (All platforms) NAbox-4.0.7.nbx 835.4 MB b1edbd25bc3f8d8f71430704a27ff9a9

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.8.ova
MD5 (NAbox-4.0.8.ova) = 7e1651dd897efd9b9f1a1849c6fb40da
$ md5sum NAbox-4.0.8.ova
7e1651dd897efd9b9f1a1849c6fb40da NAbox-4.0.8.ova
> CertUtil -hashfile NAbox-4.0.8.ova MD5
MD5 hash of file NAbox-4.0.8.ova MD5:
7e 16 51 dd 89 7e fd 9b 9f 1a 18 49 c6 fb 40 da 
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.