UDMG Server Space Requirement

UDMG allows the definition of a complex folder structure for the storage of local files. The final and temporary location of a file for a given transfer scenario can be set through the global configuration, at the Server level, or by the transfer rule, which itself depends on the combination of partner/server, account, and the requested target path. This allows you to split into different folders and/or file systems according to the business case, security requirement, access speed, or space management. For more details, please refer to the UDMG Server configuration file, the creation and update of Server entities, and the creation and update of Transfer Rules.
The Temp Directory (also denoted as 'tmpReceiveDir') is only utilized for file transfer where UDMG is on the receiving end (either by actively downloading a file as a client or by being pushed a file as a server). This is where the partial content is stored until the completion of the file data exchange between server and client. At the end of the transfer, the temporary file is moved to its target location that was defined by the Transfer Rule Local Directory (or the default value from the Server entity Receive Directory, or in turn by the default from UDMG Server global configuration).
All the final and temporary folder locations must be large enough to accommodate the expected volume of files and their retention period (to be handled outside of UDMG). For example, let's assume a transfer scenario with a daily download of a 1.6Tb file, a weekly retention is setup with the removal of files older that 7 days, a setup where the temporary and final storage are on different file systems. Considering solely this scenario, the temp storage must be greater than 1.6Tb and the final storage greater than 11Tb. Ideally, both would require to be at least double in size, to allow for transfer failures and retries.
Note that having the temp and final on the same file system would avoid the need for additional space and usually speed up the moving (intra-filesystem move operation versus inter-filesystem copy and delete).

Network Requirements

Universal Data Mover Gateway components run on Windows and Linux operating systems. These systems must be connected to a network that supports TCP/IP. 

TCP/IP provides a set of commands to verify network connectivity between systems. For example, the ping command can determine if an IP connection is possible between two systems. However, the ping command may not work in all network environments. In addition, the ping command may work, but a firewall may deny all other connection attempts between the two systems. Check with your local network administrator to determine the capabilities and topology of your network.

Ports Configuration

Universal Data Mover Gateway is composed of several components that utilize the TCP/IP network for component communications. TCP/IP routes must be available between the distributed components and firewall rules open, if necessary.