...
The DryvIQ Platform’s bi-directional bidirectional hybrid/sync capabilities enable organizations to leverage and preserve content across on-premises systems and any cloud servicetheir storage platforms. Seamless to users, new files /and file changes from either system are automatically reflected in the other. DryvIQ Migrate uses jobs to perform specific actions between the source and destination platforms. While there are several job types available, the most common type of jobs are copy and sync. See Create New Job | Transfer Direction for more information.
To create a job, select click Create Job on the Jobs option from the left menu, and select Create Jobpage.
...
This will launch the Create Job wizard . There DryvIQ will lead you through a wizard to where you select all the applicable options for your migration scenario. There are seven steps. Refer to the table below for an overview of each step and links to documentation for each step.
...
Job Creation Step | Description |
---|---|
The job type defines the kind of job and the actions the job will perform with the content. There are four job types available: |
|
|
|
| |
During this step, you will select your source and destination connections and the path for the job. You can enable impersonation for the job during this step. | |
Categories allow for the logical grouping of jobs for reporting and filtering purposes. The category is optional and does not alter the job function in any way. DryvIQ comes with a “Default” category that is assigned to all new jobs. You can create and manage custom categories based on your needs. | |
Policies is where you define what should happen once items have been successfully transferred and set up rules around how to deal with content as it is updated on your resources while the job is running. Policies define how DryvIQ handles file version conflicts and whether or not it persists a detected file deletion. Each job has its own policies defined, and the settings are NOT global across all jobs | |
Behaviors determine how the job should execute and what course of action to take in different scenarios. |
Some behaviors are enabled by default as recommended settings to ensure content is transferred successfully to the destination. | |
The Advanced section provides optional job configurations that determine what features you want to preserve, filter, or add during your content transfer. | |
During this step, you will review the configuration settings selected before creating the job. This is also where you will create the job schedule and stop policies. |