Atlas project production

Backup Maintainer - Google Drive Backup Upload

Collects configured backup sources and uploads them to a designated Google Drive location for retention and recovery readiness.

Internal-only entry. Do not publish externally without review.

Type: System
Lifecycle: Active
Last touched: 2026-03-24
Visibility: Internal

Purpose

Collects configured backup sources and uploads them to a designated Google Drive location for retention and recovery readiness.

Current state

Production cron runs `/home/bousdtech/Backup-Maintainer.sh` daily. The script is not stored in this repo, but it is referenced in the production cron list, indicating active use for district backup handling. Current registry state: Supported Helper Workflow / Active / High. Backup and recovery operations. Trigger / frequency: daily at 06:00 per `docs/cron-example.txt`..

Next step

backup scope, retention, and validation checks are not documented here. Yes - document backup scope, retention policy, and restore testing cadence.

Interfaces

Inputs

configured backup sources [validate].

Outputs

Google Drive backup storage.

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Not in scope.

Automation Engines

Not in scope.

Human Interfaces

Not in scope.

Operational Adoption

Not in scope.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Data integrity and contracts

Source of truth rules

configured backup sources [validate]. remain the authoritative upstream inputs for this workflow.
Google Drive backup storage. should be treated as downstream copies, recipients, or operational consumers rather than the authoring system.

Safe handling

Protect credentials, generated files, logs, and any transient export artifacts.
Treat student identifiers, rosters, and related records as FERPA-restricted data.
Limit staff identity, employment, or account data to approved administrators and business owners.

Operational notes

Reliability posture

not documented; confirm backup job logging and alerting. Failure impact: reduced recovery capability and potential data-loss exposure. Manual fallback: manual backup copy procedures..

Observability

not documented; confirm backup job logging and alerting.
Failure impact: reduced recovery capability and potential data-loss exposure..
Manual fallback: manual backup copy procedures..

Security and privacy

Drive credentials and backup-source access should be restricted. Classification: likely confidential operational data. backup data should follow retention and access policies.

Dependencies

Upstream

backup-source availability, Google Drive access, storage quotas.

Downstream

Google Drive backup storage.

Ownership

Owners

Technology Services

Users

Technology Services

Backup Maintainer - Google Drive Backup Upload

Operational Notes

Method: scripted backup collection and Google Drive upload.
Implementation: /home/bousdtech/Backup-Maintainer.sh.
Trigger / frequency: daily at 06:00 per docs/cron-example.txt.
Failure impact / fallback: reduced recovery capability and potential data-loss exposure. Manual fallback: manual backup copy procedures..
Related references: docs/cron-example.txt.

Registry Alignment

Mapped registry entry: INT-077
Registry clarified: Production cron runs /home/bousdtech/Backup-Maintainer.sh daily.
Validation gaps: backup scope, retention, and validation checks are not documented here.