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.10 (2025-03-05) | Release Notes

Platform Download Size Checksum
VMware NAbox-4.0.10.ova 994.0 MB 8deb78434bc2d951f78830119538e1ba
QEMU (Experimental) NAbox-4.0.10.qcow2 973.2 MB a897a492928ef11d4a0528990384c1e1
Hyper-V (Experimental) NAbox-4.0.10.zip 931.2 MB 869bd82ee629b4dba517b714a756c08d
Update (All platforms) NAbox-4.0.10.nbx 904.1 MB a5aad69a3fea4c87c6acf52bc2ffb6c0

4.0.9 (2025-02-10) | Release Notes

Platform Download Size Checksum
VMware NAbox-4.0.9.ova 997.8 MB 914659d962523f665abf48f721da4d92
QEMU (Experimental) NAbox-4.0.9.qcow2 976.2 MB e0c068200f1f530dda9f72e0f10c7b81
Hyper-V (Experimental) NAbox-4.0.9.zip 935.0 MB 2e8d899f059861c93ee48842f371ba46
Update (All platforms) NAbox-4.0.9.nbx 899.7 MB c8e88dde4c53287a3e698a07cfbb4705

Beta versions

4.1.0b1 (2025-03-22) | Release Notes

Platform Download Size Checksum
VMware NAbox-4.1.0b1.ova 996.7 MB 466a8257df94ede6c2eb79433d5b28dd
QEMU (Experimental) NAbox-4.1.0b1.qcow2 976.0 MB dc2a6cb1949067a61ee39811f877c8e8
Hyper-V (Experimental) NAbox-4.1.0b1.zip 933.7 MB 0981948882b85e12117eadf8b074d12a
Update (All platforms) NAbox-4.1.0b1.nbx 908.4 MB 9fd9e3daf1021289364eba4ffaa281a7

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.0b1.ova
MD5 (NAbox-4.1.0b1.ova) = 466a8257df94ede6c2eb79433d5b28dd
$ md5sum NAbox-4.1.0b1.ova
466a8257df94ede6c2eb79433d5b28dd NAbox-4.1.0b1.ova
> CertUtil -hashfile NAbox-4.1.0b1.ova MD5
MD5 hash of file NAbox-4.1.0b1.ova MD5:
46 6a 82 57 df 94 ed e6 c2 eb 79 43 3d 5b 28 dd 
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.