client-backup-restore

Automate on-demand backup and restore of client deployment data.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Number531/Legal-API --skill client-backup-restore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: client-backup-restore
Source: https://github.com/Number531/Legal-API/tree/main/.claude/skills/client-backup-restore
Command: npx skills add https://github.com/Number531/Legal-API --skill client-backup-restore

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gcloud, docker, psql, and includes scripts (resource) components.

What problem does it solve?

On-demand backup and restore for client deployments ensures data safety, quick disaster recovery, and verifiable data integrity across multiple client databases and reports.

Core Features & Use Cases

  • On-demand database export: creates full database dumps to a WORM bucket for compliance and audit trails.
  • Reports archive: bundles session data and raw sources for offsite storage and restoration.
  • Restore verification: validates backends by comparing row counts and generating a manifest for integrity checks.
  • Cross-client protection: prevents cross-client restore by tying backups to client identifiers and enforcing pre-restore checks.

Quick Start

Run a complete client backup by issuing the backup command with the client_id and monitor the resulting manifest and logs.

Frequently Asked Questions about client-backup-restore

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate on-demand Cloud SQL database backups for multiple clients?

Automating on-demand Cloud SQL database backups is achieved by running targeted scripts that export full database dumps to GCS storage. The process ties each backup to a specific client identifier and generates a manifest for compliance and audit trails.

What is the best way to prevent cross-client data restores in a multi-tenant disaster recovery scenario?

Preventing cross-client data restores requires enforcing pre-restore checks that tie backups to unique client identifiers. This safeguard ensures that exported Cloud SQL databases and reports are only restored to their original client deployment.

How do I verify data integrity after restoring a client database from a GCS archive?

Verifying data integrity after a restore involves comparing row counts between the source and destination. The process validates backends and generates a manifest to confirm that the restored Cloud SQL data matches the original backup.

Do I need Docker and gcloud to perform point-in-time recovery for client deployments?

Yes, performing point-in-time recovery for client deployments requires Docker, gcloud, and psql. These dependencies enable the scripts to interact with Cloud SQL databases, manage containers, and execute structured database exports to GCS.

Can I bundle session data and raw sources for offsite storage during a database backup?

Yes, bundling session data and raw sources for offsite storage is supported during the backup process. The scripts create a reports archive alongside the Cloud SQL database dump, ensuring comprehensive client deployment data preservation.