On This Page
...
| Info |
|---|
Duplicate Folder Names: If there are duplicate folder names, DryvIQ will only create the child job for the first folder it encounters and skip the duplicate folder. Therefore, it is important that you verify there are no duplicate folder names before creating your folder mapping job. |
Performance Considerations
The parent for a folder mapping job has minimal impact on performance. However, the child jobs it creates follow the same performance consideration as any job type available in DryvIQ.
If DryvIQ is installed on a single instance, Parallel Writes will be a limiting factor, regardless of how many child jobs are created. In a multi-node scenario, more jobs running concurrently may be configured without impacting performance.
Adding Locations
In addition to choosing the source and destination platforms that will be used for the Folder Mapping job, you need to specify the impersonation options and paths that should be used when creating the child jobs.
...
Target the root of each folder: The child job will be created for the first level folder relative to the source path.
Target a specific directory within each folder: If there is a folder that is exists in every directory, you can define it with this option.
Setting the
...
Job Schedule
After configuring policies, behaviors, and advanced features, you will be prompted to schedule the job. This schedule will be applied to the child jobs. The parent job will run immediately to create the child jobs. After the child jobs are created, the default schedule is set to run every 6 hours so it can review the source for any new content. The parent and child job schedules can be changed at any time.
...