Note: Aspera recommends installing Console on 64-bit Windows, which is essential for maximizing MySQL performance.
|Minimum Hardware Requirement||
|Data Storage Requirement||
In terms of planning for the size growth of the database, the per file records generate 1-2KB per file transfer, and the session records generate 8-12KB per session. For some size estimates, here are a few examples:
Note: If there is an existing installation, shut down the MySQL database and the Apache HTTP server during installation.
|Firewall (on the Console Machine)||
Open the following ports on the Console machine:
|Firewall (on the Node Machines)||
Note: No servers are listening on UDP ports.When an Aspera client initiates a transfer, the client opens an SSH session to the SSH server on the designated TCP port and negotiates the UDP port over which the data transfer will occur.
For Aspera servers that have multiple concurrent clients, the Windows operating system does not allow Aspera's FASP protocol to reuse the same UDP port for multiple connections. Thus, if you have multiple concurrent clients and your Aspera server runs on Windows, then you must allow inbound connections on a range of UDP ports, where the range of ports is equal to the maximum number of concurrent FASP transfers expected. These UDP ports should be opened incrementally from the base port, which is UDP/33001, by default. For example, to allow 10 concurrent FASP transfers, allow inbound traffic from UDP/33001 to UDP/33010.