Skip to content

Jobs

A job defines the source, target, and execution behavior for one repeatable data movement task.

Typical job contents

  • source Storage Repository and path
  • target Storage Repository and path
  • execution target such as a shared pool or dedicated runner
  • synchronization settings
  • filters and exclusions
  • scheduling
  • optional audit-based delta settings when supported
  • optional local change-feed delta settings for supported local-source jobs
  • optional integrity evidence for reviewable transfer-hash reporting

Safe operator workflow

  1. configure source and target paths carefully
  2. review filters and exclusions
  3. validate the execution target
  4. start with Dry Run or Scan
  5. move to Run only after the result looks correct

Save behavior

The job detail page is the main place to review and update configuration. Save changes before starting a run if you changed source, target, scheduling, or advanced settings.

When a job is part of a Migration Planning job set, saving a changed configuration opens a review step. You can save only the current part or apply only the changed items to the other parts in the same set. Scope-defining inclusion filters remain generated by Migration Planning and Delete excluded is blocked for migration job-set parts.

Transfer behavior

New jobs copy by default. Copy mode transfers source content to the destination without deleting files that exist only on the destination.

Enable Mirror data only when the destination should match the source exactly. Mirror mode can delete destination-only files, so the first live mirror run requires an explicit confirmation in the run overlay.

Enable Prevent overwrites when copy mode must never update files that already exist at the destination. The setting is copy-mode only and is not available with Mirror data.

The live-run confirmation overlay repeats Mirror data, Prevent overwrites, and Delete excluded so you can make a final adjustment before starting a live run. Changes made there are saved to the job when the live run starts.

Migration Planning also lets you choose Mirror data before creating proposed job parts. Use mirror mode only when the destination for each part should match its source scope exactly.

Sync strategy

The Sync Strategy tab shows only the options that fit the source type:

  • cloud or business sources can show audit-based delta settings when the provider supports them
  • local sources can show local change-feed delta settings when the assigned dedicated runner supports them
  • ordinary tree sync remains the safe default

Audit-based delta and local change-feed delta both need a trusted full-tree baseline before targeted delta runs can be trusted.

See also