Azure Data Box system requirements

This article describes the important system requirements for your Microsoft Azure Data Box and for the clients connecting to the Data Box. We recommend you review the information carefully before you deploy your Data Box, and then refer back to it as necessary during the deployment and subsequent operation.

The system requirements include:

  • Software requirements for hosts connecting to Data Box - describes the supported platforms, browsers for the local web UI, SMB clients, and any additional requirements for hosts that can connect to the Data Box.
  • Networking requirements for the Data Box - provides information about the networking requirements for the optimum operation of the Data Box.

Software requirements

The software requirements include the information on the supported operating systems, supported browsers for the local web UI, and SMB clients.

Supported operating systems for clients

Here is a list of the supported operating systems for the data copy operation via the clients connected to your device.

Operating system Versions
Windows Server 2008 R2 SP1
2012
2012 R2
2016
2019
Windows 7, 8, 10
Linux

Supported file systems for Linux clients

Protocols Versions
SMB 2.X and later
NFS All versions up to and including 4.1

Supported storage accounts

Here is a list of the supported storage accounts and the storage types for the Data Box device. For a complete list of all different types of storage accounts and their full capabilities, see Types of storage accounts.

Storage account / Supported storage types Block blob Page blob* Azure files Notes
Classic Standard Y Y Y
General-purpose v1 Standard Y Y Y Both hot and cool are supported.
General-purpose v1 Premium Y
General-purpose v2 Standard Y Y Y Both hot and cool are supported.
General-purpose v2 Premium Y
Blob storage Standard Y Both hot and cool are supported.

* - Data uploaded to page blobs must be 512 bytes aligned such as VHDs.

Note

Azure Data Lake Storage Gen 2 accounts are not supported.

Supported storage types

Here is a list of the supported storage types for the Data Box device.

File format Notes
Azure block blob
Azure page blob The data should be 512 bytes aligned.
Azure Files

Supported web browsers

Here is a list of web browsers supported for the local web UI.

Browser Versions Additional requirements/notes
Google Chrome Latest version Tested with Chrome
Microsoft Edge Latest version
FireFox Latest version Tested with FireFox
Internet Explorer Latest version If you cannot sign in, check if cookies and Javascript are enabled. To enable the UI access, add the device IP to Privacy Actions so that the device can access cookies.

Networking requirements

Your datacenter needs to have high-speed network. We strongly recommend that you have at least one 10-GbE connection. If a 10-GbE connection is not available, a 1-GbE data link can be used to copy data but the copy speeds are impacted.

Port requirements

The following table lists the ports that need to be opened in your firewall to allow for SMB or NFS traffic. In this table, in or inbound refers to the direction from which incoming client requests access to your device. Out or outbound refers to the direction in which your Data Box device sends data externally, beyond the deployment: for example, outbound to the Internet.

Port no. In or out Port scope Required Notes
TCP 80 (HTTP) In LAN Yes This port is used to connect to Data Box Blog storage REST APIs over HTTP. If not connecting to REST APIs, this automatically redirects to local web UI over 8443.
TCP 443 (HTTPS) In LAN Yes This port is used to connect to Data Box Blog storage REST APIs over HTTPS. If not connecting to REST APIs, this automatically redirects to local web UI over 8443.
TCP 8443 (HTTPS-Alt) In LAN Yes This is an alternative port for HTTPS and is used when connecting to local web UI for device management.
TCP 445 (SMB) Out/In LAN In some cases
See notes
This port is required only if you're connecting via SMB.
TCP 2049 (NFS) Out/In LAN In some cases
See notes
This port is required only if you're connecting via NFS.
TCP 111 (NFS) Out/In LAN In some cases
See notes
This port is used for rpcbind/port mapping and required only if you're connecting via NFS.

Next steps