Footnotes

In Veeam technical documentation, we use footnotes to provide additional information on table content.

If there is only one footnote in a table, use the asterisk character (*) to mark the necessary word or sentence. If there is more than one footnote in a table, use Arabic numerals to mark the necessary words and sentences; number all footnotes consecutively in the order in which they appear in the table.

Tip

In some cases, it is acceptable to use notes instead of footnotes. However, if one note refers to multiple table rows or columns, consider adding a footnote instead.

Example 1 (Asterisk)

The following table describes network ports that must be opened to ensure proper communication with the Veeam Backup & Replication console installed remotely.

Example 1 (Asterisk)
From	To	Protocol	Port	Notes
Veeam Backup & Replication Console	Backup server	TCP	9392	Port used by the Veeam Backup & Replication console to connect to the backup server.
		TCP	10003	Port used by the Veeam Backup & Replication console to connect to the backup server only when managing Veeam Cloud Connect.
		TCP	9396	Port used by the Veeam.Backup.UIService process for managing database connections.
Veeam Backup & Replication Console	Mount server (if the mount server is not located on the console)	TCP	2500 to 3300*	Default range of ports used as data transmission channels. For every TCP connection that a job uses, one port from this range is assigned.

* This range of ports applies to newly added backup infrastructure components. If you upgrade to Veeam Backup & Replication 10.0 from earlier versions of the product, the range of ports from 2500 to 5000 will apply to the already added components.

Example 2 (Numbers)

Depending on the storage system type, you can perform the following operations:

Example 2 (Numbers)
Operation/ Storage Type	Dell EMC Unity/VNX(e)	HPE 3PAR StoreServ, HPE Primera	HPE StoreVirtual	HPE Nimble	NetApp FAS/AFF, FlexArray (V-Series), Fujitsu ETERNUS HX/AX, IBM N series, Lenovo DM-Series	Cisco HyperFlex	IBM Spectrum Virtualize Lenovo V-Series	Universal Storage API Integrated Systems
Backup from Storage Snapshots
Backup from primary storage arrays	✓	✓	✓	✓	✓	✓	✓	✓
Backup from secondary storage arrays	✕	✓1	✕	✓1	✓1	✕	✓1	✕
Veeam Explorer from Storage Snapshots
Restore from primary storage arrays	✓	✓	✓	✓	✓	✕	✓	✓
Restore from secondary storage arrays	✓	✓	✓	✓	✓	✕	✓	✓3
Snapshot Orchestration
Snapshot-only job for primary storage arrays	✕	✓	✕	✓	✓	✕	✓	✓
Snapshot-only job for secondary storage arrays	✕	✓1	✕	✓1	✓1	✕	✓1	✕
Backup from Storage Snapshots with Snapshot Retention
Backup job with snapshot retention on primary storage arrays	✕	✓	✕	✓	✓	✕	✓	✓
Backup job with snapshot retention on secondary storage arrays	✕	✓1	✕	✓1	✓1	✕	✓1	✕
Other Operations
Storage rescan	✓	✓	✓	✓	✓	✓2	✓	✓
Snapshot creation and deletion (manual)	✓	✓	✓	✓	✓	✕	✓	✓

1 Storage snapshot technology:

HPE 3PAR StoreServ — snapshot creation on Peer Persistent target
HPE Nimble — snapshot replication
NetApp FAS and AFF Series, FlexArray (V-Series), Fujitsu ETERNUS HX/AX, IBM N series, and Lenovo DM-Series — snapshot replication with SnapMirror/SnapVault
IBM Spectrum Virtualize and Lenovo V-Series — snapshot creation on HyperSwap target

2 Infrastructure only

3 Contact vendor to check compatibility and storage system configuration

Example 3 (Notes)

The machine where Orchestrator will be deployed must meet the necessary hardware and software requirements. Note that the Orchestrator server can function as a Veeam Backup & Replication server and must have sufficient resources provided.

Example 3 (Notes)
Specification	Requirement
OS	Only 64-bit versions of the following operating systems are supported: Microsoft Windows Server 2019 Microsoft Windows Server 2016 Microsoft Windows Server 2012 R2 Microsoft Windows Server 2012 Microsoft Windows Server 2008 R2 SP1 Note: You cannot install Orchestrator on a machine running Microsoft Windows Server Core.
User Management	Windows domain-joined machine
SQL Server	Local or remote installations of the following versions of Microsoft SQL Server are supported: Microsoft SQL Server 2019 Microsoft SQL Server 2017 Microsoft SQL Server 2016 (2016 SP2 Express Edition is included in the setup) Microsoft SQL Server 2014 Microsoft SQL Server 2012 (2012 SP4 Express Edition is included in the setup) Note: It is not recommended to use the Express Edition in any production Orchestrator deployments — it should only be used for product evaluation.
Additional Software	All components will be installed during setup. For inline Report Template editing, Microsoft Word component of SP2 for Microsoft Office 2010 or later is required.
Veeam Software	If a standalone Veeam Backup & Replication server is used for backup and replication task management, it must be version 9.5 Update 4 or later. However, it is recommended that you install version 10 cumulative patch 2 as it includes a number of important fixes related to the Orchestrator functionality. Note: If you connect a standalone Veeam Backup & Replication server to the Orchestrator server, it must be joined to either the same domain or a trusted domain.
Virtualization Platform	VMware vSphere 5.5, 6.0, 6.5, 6.7, 7.0 Note: The Orchestrator server must be connected to VMware vCenter Servers. Direct connections to vSphere hosts are not supported.
Storage System	NetApp ONTAP 9.3, 9.4, 9.5, 9.6, 9.7