Configure scheduled local and off-site photo backups

Why use this

1. A household may have a photo archive and two intended backup destinations but no clear way to tell whether recent files reached either one. A completed copy operation can create false confidence if restoration has never been considered.

2. This job could make the backup arrangement, monitoring and recovery expectations inspectable before configuration. Distinguishing an additional copy from a synchronized deletion path helps the owner evaluate whether the plan protects the collection as intended.

Why an agent / simpler alternative

Useful judgment

Reconcile source folders, schedules and retention expectations, and identify failure conditions that logs should expose.

Simpler alternative

Use a supported backup application's standard configuration when it already covers the desired destinations.

Unsuitable when

The plan lacks a recoverable original, requires secret handling or would delete existing copies without explicit approval.

Proposed inputs

1. Name

   Photo inventory

   Owner

   Archive owner

   Minimum scope

   Source folder scope, approximate volume and exclusions

   Quality check

   Identify duplicates, originals and private content

2. Name

   Backup brief

   Owner

   Owner

   Minimum scope

   Approved destinations, retention and recovery priorities

   Quality check

   Distinguish backup retention from mirroring

Access and setup — proposed or unknown

Proposed minimum

1. Start with a destination/schedule diagram and synthetic file manifest; no credentials, cloud account setup or transfers.

Compatibility unknowns

1. Current drive state, cloud permissions, scheduling tools and exact runtime compatibility are unknown.

External actions requiring approval

1. Creating credentials, persistent access, cloud uploads, paid storage and destructive retention changes require appropriate approval or handoff.

Expected deliverable and review checks

Proposed artifact

Proposed backup configuration, failure-monitoring checklist and bounded restore-check plan.

Critical checks

1. Keep originals intact; identify destination capacity and encryption needs; require evidence of recoverability beyond a successful job status.

Missing output evidence

This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

1. Signal

   A missing drive path becomes an empty local folder

   Why it matters

   The job can appear successful at the wrong destination

   Proposed response

   Verify destination identity before any future copy.

2. Signal

   Deletion propagation removes both copies

   Why it matters

   Synchronization defeats the retention goal

   Proposed response

   Separate retention rules and stop destructive operations.

Effort and cost — unknown

Setup work

1. Inventory folders and define retention/recovery requirements.

Ongoing review

1. Review failed runs, destination health and authorized restore checks.

Unknowns

1. Storage growth, transfer charges, hardware reliability and restore effort are unknown.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invent a manifest of five photos, an unavailable local destination and one deleted source file; review the proposed copy/retention behavior.

Acceptance checks

1. Flag unavailable storage; preserve retained copies; specify a recovery check; transfer no files.

Stop conditions

1. Stop before credential creation, paid storage, cloud upload or deletion.

Limits

1. A configured schedule or clean log cannot establish that photos are complete, intact and recoverable.