![]() It improves speed of merging folder tree and getting the job into balance (especially when only few files differ on different agents). "Agent's level" means that the value is taken either from Agent Profile or the Agent's core (it's true by default in the core).Įnabled Lazy indexing means that the Agent will not hash any files until some other Agent requests to download it. This parameter must comply with lazy indexing, see here for usage examples.ĭisabling hashing at all, while "Disable differential sync" is Yes in Agent Profile does not make sense and will cause job to stuck.ĭisabling it is not advisable for Synchronization jobs, especially if agents tend to go offline periodically as other agents won't be able to download the files until file owner is back online. It is similar to Lazy indexing, and applies to the file owner - the Agent which updated the file last. Works only for Consolidation and Distribution jobs.įorce file owner to hash files transfer_job_force_owner_to_hash_file Otherwise, job will wait for the agents to be online. If there are offline agents, count the job as complete for them. Read more about it here.įorce complete job for offline Agents ignore_offline_agentsĭeprecated in 3.4.0, replaced with functionality to abort a job run on error. See here for more details.ĭefines whether an Agent will follow the link and synchronise its content as files and folders. Option to prioritise active downloads based on file names. See here here for detailsįile download priority file_download_priority Has some side effect, see here for more details. The path that was chosen for a pre-indexing trigger in a Distribution or Consolidation job will be created if its missing.Įnables data compression in the job to save network traffic. If certain level is selected, all events above it in the list are also included. If value is "Agent's level" will be same as in Agent profile. Sets the level for agent's event log, or even disables logging. Works only for Consolidation and Distribution jobs.Ĭonsoles events level events_logging_level Use this setting to force job completion in N seconds if, for some reason, the job gets stuck. See here for more details.Īutomatically stop job after (sec) timeout ![]() Edit the filter to receive only events of interest. Some of the events are disabled in the filter and won't show up on Management Console. The combination of Job Profile settings and Agent Profile settings make configuration complete. You can change these settings at any time by editing an existing job profile.Īll agents doing the job share its group of Job Profile Settings. ![]() When you create a new job, you can define the following collection of settings for that job (in “Job Profile Settings”). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |