Skip to main content

Protection policy

Policy answers three independent questions:

  1. Which source volumes are in scope? Volume groups and ignore rules.
  2. How should they be protected? Replication profiles.
  3. How much work may proceed? Automation profiles.

Replication profile

ParameterMeaning
ONTAP policyExisting asynchronous mirror, mirror-vault, or vault policy
Job scheduleExisting destination cron schedule; DonkeyFleet does not create it
Throttle (Kbps)Optional relationship throttle; when empty, baseline admission uses the lower automation limit
Naming strategysuffix or same_as_source; template provisioning is currently refused
Size policyMatch source, or source size plus configured headroom
Tiering and coolingDestination storage-tier intent; select tiering explicitly

Aggregates, policies, and schedules are discovered values. DonkeyFleet refuses missing or ambiguous placement rather than guessing.

Automation modes

ModeNew protectionRemediationOrphan deletion
manualRecords review work onlyProposal onlyApproval always required
approveHuman approval requiredHuman approval requiredApproval always required
autoEligible work may run when effective dry-run is offOnly implemented bounded rules may runApproval always required

Automation parameters

The form defaults are starting points, not universal sizing recommendations.

ParameterUI defaultOperational effect
Max actions per run10Bounded approval/admission window and preparation batch; does not override baseline limits
Minimum volume age (hours)24Time since first complete observation before protection is eligible
Max orphan transitions5Absolute cap on new orphan transitions in one run
Max orphan transitions (%)10Percentage cap evaluated with the absolute orphan guardrail
Orphan grace (hours)72Minimum orphan duration before cleanup can be proposed
Fill threshold (%)90Opens a destination-fill episode
Autonomous grow (%)10One bounded grow attempt per episode; configure 5 or less for the accepted safety cap
Target utilization (%)70Target used for the human growth recommendation
Episode reset threshold (%)80Fill must recover below this value before a new episode can open
Max cumulative growth (%)25Total autonomous-growth ceiling relative to the episode baseline
Max concurrent initializes1Maximum baselines admitted at once for this automation profile
Intercluster budget (Kbps)200000Total baseline bandwidth budget
Baseline throughput (Kbps)130000Estimate and default throttle input when the replication profile has no throttle
Baseline overrun factor1.5Urgent-alert multiplier over the larger of the size estimate and ten-minute floor
Initial onboarding

Set minimum volume age to 0 only when existing matching volumes should become eligible immediately. With a higher value, they remain in Backlog with min_volume_age until the age is reached and a reconcile observes them again.

Raising max_concurrent_initializes does not guarantee that many simultaneous baselines. Each candidate must also fit the intercluster budget. Estimate the impact on existing scheduled SnapMirror traffic before raising either value.

Volume groups and ignores

Lower numeric group priority wins. Rules inside a group are ordered AND conditions. A matching group assigns both profiles; DonkeyFleet never infers an automation profile from a replication profile.

For Trident-backed Kubernetes storage, volume groups select the backing ONTAP volumes using ONTAP-visible attributes such as the storage prefix and provisioning metadata in the volume comment. DonkeyFleet applies policy to the ONTAP volume UUID, not to the PV or PVC object.

Ignore rules override group matching. Clones and foreign-managed volumes are also structurally excluded. Always preview resulting candidates in dry-run before enabling Apply.