Resetting Jobs
- Andrea Harvey
On This Page
Overview
Reset options control how DryvIQ will re-evaluate tracking state or permission propagation on the next job execution. Executing a reset sets the corresponding flags in the database. The job must be executed in order for the change to take effect. If you select to run the job when selecting the rest type, the job will automatically start the next execution if the job is not currently running. Note that reset options aren’t available for system jobs.
Â
Reset Type | Description | Resets Tracking Data |
|---|---|---|
Statistics | This reset will recalculate all item transfer statistics to ensure report accuracy. After all content has been transferred, a Statistics reset is recommended to ensure all tracking statistics represent the final calculations and to ensures job report accuracy. If several errors or pending items have been encountered, a Statistics reset after remediation ensures the latest tracking state is reflected. | No |
Soft | This reset will preserve all previous tracking data and allow DryvIQ to re-evaluate all content, rather than only detecting content that has changed. After the initial job run, subsequent runs leverage the change detection feature, which allows DryvIQ to focus only on transferring content that has changed rather than evaluating all content. This ensures efficient transfer performance. However, not all platforms track changes the same way. A Soft reset will preserve all previous tracking data but allow DryvIQ to re-evaluate the entire content hierarchy to ensure all content is transferred based on the given job configuration. | No |
Hard | This reset will clear all previous tracking data and allow DryvIQ to re-evaluate all content, rather than only detecting content that has changed. After the initial job run, subsequent runs leverage the change detection feature, which allows DryvIQ to focus only on transferring content that has changed rather than evaluating all content. This ensures efficient transfer performance. However, not all platforms track changes the same way. A Hard reset clears all previous tracking data and allows DryvIQ to re-evaluate the entire content hierarchy to ensure all content is transferred based on the given job configuration. | Yes |
Permissions | This reset allows DryvIQ to re-evaluate all content and re-apply all permissions to ensure any new permissions on the source are applied to the destination. A permissions reset will never remove permissions previously transferred. This reset will not detect any changes to content; these changes will transfer on the job run following the reset. After the initial run, subsequent runs leverage the change detection feature, which allows DryvIQ to focus only on transferring content that has changed rather than evaluating all content. This ensures efficient transfer performance. However, if only a new permission is added during a transfer but the item didn’t change, the new permission will not be detected. A permission reset will allow DryvIQ to re-evaluate all content and re-apply the permissions. | No |
Complete | This reset is a combination of both a Hard rest and a Permissions reset. Rather than running a hard and permission job reset as separate runs, this option offers both in one. | Yes |
Â
You should save a copy of all log files before performing a reset.
Resetting Jobs from the Jobs List
Click Migrate in the navigation menu on the left.
Click Migrations.
Select the job(s) you want to reset. A blue check mark identifies jobs you selected.
Click More Options.
Click Reset job(s).
Â
Select the reset type you want to use.
Â
If you want to reset and run the job, select Run the selected job(s) now.
Click Done.
Resetting a Job from the Job Reports
While viewing the reports for an individual job,
Click More Options.
Click Reset job.
Select the reset type you want to use.
If you want to reset and run the job, select Run the selected job(s) now.
Click Done.