The statement is incorrect for two primary reasons. First, the Open Systems SnapVault (OSSV) agent on the primary system acts as a client and initiates communication; it does not listen for incoming connections. It is the secondary NetApp storage system that listens for SnapVault communications. Second, the primary port used for SnapVault data transfer is TCP 10566, not 10000. While TCP port 10000 is used for the Network Data Management Protocol (NDMP) control connection, the secondary system listens on this port, not the primary OSSV agent.

The statement "True" is incorrect because it misrepresents the fundamental communication architecture of SnapVault with an OSSV agent. The primary system (with the OSSV agent) is the initiator, and the secondary NetApp system is the listener. Furthermore, it specifies the wrong primary port for SnapVault data transfer.

1. NetApp

Inc. (2013). Data ONTAP® 8.2 Data Protection Online Backup and Recovery Guide For 7-Mode.

Reference: Page 188

Section: "Firewall configurations for Open Systems SnapVault".

Quote: "The secondary system must allow incoming connections on TCP port 10566 (the SnapVault port) and TCP port 10000 (the NDMP port). The primary system must allow incoming connections on a range of TCP ports for data connections from the secondary system."

Commentary: This official guide explicitly states that the secondary system listens on ports 10566 and 10000

directly contradicting the question's claim that the primary OSSV agent listens on port 10000.

2. NetApp

Inc. (2012). Open Systems SnapVault 3.0.1 Installation and Administration Guide for Windows.

Reference: Page 20

Section: "Firewall considerations".

Quote: "The SnapVault secondary system must be configured to allow incoming connections on TCP port 10566 (the SnapVault port) and TCP port 10000 (the NDMP port)."

Commentary: This OSSV-specific documentation confirms that the listening role belongs to the secondary system

not the primary system where the OSSV agent resides.

3. NetApp

Inc. (2011). TR-3487: SnapVault Best Practices Guide.

Reference: Page 11

Section 2.3 "Network".

Quote: "The SnapVault secondary listens for requests on TCP port 10566. The SnapVault primary initiates a connection to the secondary on this port."

Commentary: This technical report clearly defines the roles: the secondary listens

and the primary initiates. It also specifies the correct port

10566

for the initial connection

further invalidating the question's premise.