Fine-Tuning Data Transfer Performance; Section 2.4, "Fine-Tuning Data Transfer Performance - Novell PLATESPIN PORTABILITY SUITE 8.1 Configuration Manual

Network Communication Prerequisites for Workload Portability and Protection Operations
Table 2-3
System
Portability Suite Server host
Portability Suite Server host
All source workloads
Windows workloads and
targets
All targets
All targets
Portability Suite Server host;
all sources
All Linux sources
VMware ESX Server 2.5
VMware ESX Server 3.0.x
Citrix Xen Server
Portability Suite Server host;
All Windows sources

2.4 Fine-Tuning Data Transfer Performance

You can fine-tune data transfer during migration jobs for optimum performance over your network.
The specifics of functionality and configuration procedures depend on the data transfer method
selected for a particular job. See
Section 2.4.1, "Fine-Tuning File-Level and VSS-Aware Block-Level Transfer Performance,"
on page 21
Section 2.4.2, "Fine-Tuning Block-Level Data Transfer Performance," on page 22
20 PlateSpin Portability Suite 8.1 Configuration Guide
Open Port Remarks
80 (TCP) Required for HTTP communication among the
Portability Suite Server, sources, and targets.
443 (TCP) Required for HTTPS communication (if SSL is
used) between the Portability Suite Server and the
source or target machines. This is also the default
port for the VMware Infrastructure 3 Web service.
3725 (TCP) Required for targets to initiate communication
during file-level data transfer, except for I2X jobs,
during which this port needs to be open on the
migration target only. For Server Sync jobs
required for both sources and targets.
137 - 139 (NetBIOS) Required for NetBIOS communications.
9999 (TCP) Required during block-level data transfer for
communication between source and target.
10000-10026 (TCP) Required for block-level data transfer, with a
distinct port for each target volume.
SMB Required for Take Control communication and file-
level data transfer.
(TCP 139, 445 and
UDP 137, 138)
22 (TCP) Required for Take Control communication.
135/445 (TCP) For DCOM/RPC communication between
Portability Suite Server and a source for taking
control of and rebooting the workload through
WMI.
NOTE: WMI (RPC/DCOM) can use TCP ports 135
and 445 as well as random/dynamically assigned
ports above 1024.
"Supported Transfer Methods" in your User Guide.