Working with Growing Files
Growing files are "in-progress" files that continue to grow in size, such as videos generated at live events. Watch Folders can detect and transfer these growing to a target directory.
Requirements
- Both the source host and remote host must be running IBM Aspera High-Speed Transfer Server 3.6.0 and later to support the faspstream technology used to transfer growing files.
- The transfer user on the node running the Watch Folder service transfer must not have a docroot.
- Pull Watch Folders do not support growing files.
Configuration
When creating or editing a Watch Folder in Console, you can configure how Console handles growing files in the Growing Files section under More Options:
Option | Description | Default | Example |
---|---|---|---|
Maximum parallel transfers | The maximum number of concurrent transfers of growing files watchfolder can initiate. | 8 | 4 |
Target rate | The target transfer rate. | 10000 | 10000 |
Bandwidth policy | The bandwidth policy used for prioritizing growing file transfers. | fair | high |
Transport encryption | Transfer with an encryption method. | none | aes128 |
TCP port | TCP port to use for this Watch Folder. If different, Console connects to the target node using this port instead. | 22 | 22 |
fasp™ port (UDP) | UDP port to use for this Watch Folder. If different, Console connects to the target node using this port instead. | 33001 | 33001 |
Completion timeout | Duration in seconds of inactivity after which Console considers the growing file transfer to be complete. | 10 | 15 |
Memory |
The maximum amount of memory that the faspstream binary is allowed to use. |
128 | 128 |
Chunk size | The size of data to pack before sending over the network. | 128 | 128 |
Growing file filters | Defines which files are considered growing files. Click the ![]() |
*.m2p |
Note: Sessions with growing files are not affected by settings in the Transfer section.