In this section it's possible to find and set datamovers' settings, which have been centralized on a single page, eliminating the need to configure them from each workstation.
From the droplist PC name, select the pc where the datamover intended to be configured runs, then you can start setting up the parameters described below.
SCHEDULING TAB
These are parameters related to the datamover's behaviour when fetching and managing the jobs.
• Database Fetch Interval: Sets the rate, in seconds, at which the jobs are searched in the database. (default = 60)
• Deferral factor to use when long fetching duration is detected: In case the query to fetch the jobs in the database takes a long time, the next fetch will be made after the query duration multiplied by the value set here. For example: if the query takes 2 minutes to fetch the jobs and this value is set to 10 (default), the next fetch will occur after 2min x 10 = 20 minutes. To disable this behaviour, set this value to 0.
• Job check Interval: Sets the rate, in seconds, at which jobs are scanned. (default = 20)
• Pending SQLServer updates retry interval: Specify the rate, in seconds, at which SQL Server updates are pending. (default = 30)
• Max number of internal retries on copy error: Specify the number of internal attempts Data Mover can make to complete the requested action. The possible values are:
0 - only one attempt - no retry (default)
1 - one attempt plus one retry
2 - one attempt plus two attempts
...etc
The internal retries set here are multiplied by the T-workflow retries added by the "Retry" workflow actions. For example, if it is set to "2" and the T-workflow has a "3 times" retry action, the requested action will be repeated 9 times ([2 + 1] * 3).
Note: The copy channel remains blocked during all attempts.
• Wait interval between internal retries (msec): Sets the interval (in milliseconds) between repetitions of 2 intervals. (default = 120,000)
• Ignore non-ingested assets: If enabled, jobs requested for uningested assets (i.e. no recorded media) will not run.
• Background requests fetch: This option requests a list of jobs through the thread to run as a background process and improve system performance.
• Lazy fetching: if activated, it allows you to check the list of tasks every certain seconds (set to the interval for checking tasks).
• Save t-workflow logs for each job: If this setting is disabled (default), log files will be created only for jobs and stored in the "%LocalAppData%\Etere\Log\dm.job\" directory. If you enable this setting, an additional log file will be created for each job (containing all associated T-workflow lines) and stored in the "%LocalAppData%\Etere\Log\dm.wflog\" directory.
Note: Enable this option only when necessary, it creates multiple log files (~100 KB per job) and can fill disk storage. As a preventive measure, it is suggested to set the "Keep copy of logs for following days" parameter described below, to a shorter period (e.g. 7 days).
• Automatically try to abort dead jobs: If enabled, Datamover activities (such as Rhozet transcoding) associated with an aborted/reset T workflow will be automatically aborted. If disabled, the process launched by datamover will keep running until the end, even if the workflow has been already aborted.
Note: Datamover automatically checks for dead jobs with a frequency of 1 minute, so, if the action ends in the meantime, it will not be aborted.
• Configuration self update: If enabled, datamover automatically refresh itself when an action is modified. If disabled, to let Datamover take the modifications it's necessary to use the function "Refresh system configuration".
TROUBLESHOOTING TAB
• Show text message console: allows you to add a fourth tab to the application to list all operations performed in Etere Data Transfer.
• Avoid logging: If enabled, Datamover won't write log files.
• Disable SSL extensions (always use legacy FTP libraries): In Datamover actions, it's possible to use SSL (Secure Socket Layer) encryption for Multistep Copy, Rename File, and Delete File actions. Use this option to disable SSL encryption in all Datamover actions and return to the legacy file transfer method. This can be used as troubleshooting to investigate the process. You can also click on a specific task and check this option to disable the SSL extension, the "SSL on" indicator will disappear from the bottom of the Data Mover display.
• Select messages automatically sent by the event: Configure which events (i.e. errors, transfers, application events, heartbeats) should be logged or not (depending also on the "avoid logging" setting).
• Keep log copies for subsequent days: Set the maximum log retention time (default = 30) on the system.