Media Mover provides accelerated file movement between Agents using standard templates.
Media Mover works on all Agents and provides support for growing source files.
Before you can transfer files using Media Mover, you must add and configure your jobs using one of four Media Mover job types. You must also configure any Agent groups for local storage.
Media Mover offers four job types:
MediaDropBox transfers data between a single source location and one or more destinations. This job type polls the specified location at a user-determined interval and sends any changes detected to the specified destination(s).
MediaAggregator retrieves files from multiple Agents, transfers them to a single target Agent, and stores the files on its local disk or locally attached storage. The files transferred from the source Agents may be stored on a per Agent basis, or in a single flat folder on the target Agent. This is referred to as a pull file transfer template.
MediaDistributor allows you to schedule a push distribution in which multiple directories from a single source Agent are transferred to one or more target Agents.
MediaReplicator is a bulk file transfer option that allows you to schedule a distribution from a source Agent to one or more target Agents. As it is designed for dealing with large numbers of files, it does not have the file readiness checks that are present with MediaDropbox, MediaAggregator and MediaDistributor. This job type should be used when files are not growing in size in the source directory.
To add a Media Mover job:
To complete Basic configuration:
To complete Advanced configuration:
Enter file patterns (e.g. file extensions) to include or exclude. Separate multiple filters with commas. Include File Patterns includes all file names/types by default.
Select whether to Exclude Subdirectories. Enter any specific subdirectories to exclude. Subdirectories that match those specified are excluded regardless of where they appear in the folder path. To exclude a folder at a specific level, use the @ symbol to anchor the folder path.
For all job types except MediaReplicator, select the File Readiness Check Type:
Note: If the local or network file system supports file locking, the readiness check is not required.
If File Readiness Check Type is set to Consecutive Seek, MD5 Hash, or Date/Time and Size, set the File Readiness Check Delay. This is the pause, in seconds, between two phases of file readiness check. The default delay is 10 seconds. When set to Stream Growing Files, this is the time that must pass without file changes for the file to be declared complete.
If File Readiness Check Delay is set to Stream Growing Files, specify the following:
Specify any Source Deletions After Successful Transfer and enter any Source Directories to Exclude from Deletion Scan. These options allows the removal of specific files or directories after a successful transfer. Empty directories will only be deleted if they have not been modified within the previous five minutes.
Specify whether to Skip Source File Not Found On Send and/or Skip Files With 0 Byte Size.
Select any options by which to filter Source File Data. This option allows you to filter files by date or time, based on when the file was last modified, or accessed, or when the file was created.
Note: Destination Specification options are not available for MediaReplicator.
Select the number of Simultaneous Transfer Streams. The default is 10.
Specify to Use UDP Control Channel instead of TCP. This option should be used for firewall traversal when the TCP port cannot be opened.
Note: When Use UDP Control Channel is set to Yes, file transfers automatically use UDP WAN acceleration, which may override the Use WAN Accelerator setting.
Select whether to Use WAN Accelerator. The default is Yes. This setting uses all available bandwidth up to the user-specified bandwidth maximum. Use this option on high-latency, high-bandwidth networks where throughput is a top priority. If the throughput is less than 57200 Bps, the transfer will switch to TCP.
Set the WAN Accelerator Aggressiveness, which indicates the job's sensitivity to other network traffic. The higher the level of aggressiveness, the less the job accommodates other network traffic.
Enter any of the following bandwith settings:
Note: A bandwidth throttle specifies the rate at which the source will make the data available to the network, regardless of how fast the machine is sending. Bandwidth Throttle is the rate at which the source reads the data from disk and puts it in the send queue. A throttle is split amongst the concurrent target Agents. If, for example, your throttle is 50Mb/sec and you specify two target Agents, the bandwidth be divided equally at 25Mb/sec per target.
Note: Once a job has started, all bandwidth throttles are applied at the times based on the Daylight Savings Time (DST) in effect when the job started. If DST changes while the job is running, bandwidth time of day changes may be off by an hour.
Set the Encryption Level. The default is No Encryption – unsigned:
Note: Mutual authentication is always used, regardless of the encryption level specified. Encryption is done in-stream and not on disk prior to sending.
Select the Delivery Mode for transferring files:
Choose whether to Compress Files. The default value is No. Choose this option if you are running over a low speed WAN link.
Specify whether to Follow Symbolic Links. If a symbolic link references a directory and this option is enabled, the directory is transferred. If disabled, only the symbolic link itself is transferred.
If you are running over a low speed WAN link, enable Incremental Transfer to transfer only the changed bytes of a file, rather than the entire file.
In MediaReplicator only, enable Synchronize Target with Source to delete files from the target folder if they are not found in the source folder.
Note: Use caution when enabling the Synchronize Target with Source option. Any content deleted on the target Agent is not recoverable via Signiant.
Select whether to Verify for sufficient disk space before Job transfers start and/or Verify if target directory exists. These verifications ensure that the transfer is not aborted due to insufficient disk space or a nonexistent directory.
Select additional time parameters, choose whether a transfer is interrupted upon failure, and set the job's queuing priority.