KURO

Backup Center

Copies stay in Google Cloud. This page does not hold them. Staff remain on central.kurocardshop.com.

KURO Central

Backup history

Dates are Asia/Tokyo. Each row is a name, a time, and a size. Secret values are not listed.

Backup schedule

Loading the current schedule.

Locked. Unlock this card before the schedule changes. Google still chooses the hour.

Test only

Staff stay on the live database. The SHOPLINE quantity is not rewritten. The drill database name starts with backup-drill-.

Switch staff to this backup

Locked. Unlock this card before a restore. Typing RESTORE MAIN is still required after that.

This rewinds staff, SHOPLINE mirrors, Gameology, payments, and Kuro Oripa together. A bad deploy should roll back the Cloud Run revision instead.

Pick a night to see the gap.

First this builds kuro-restore-… beside the live database. Traffic does not move.

  1. Pause Cloud Scheduler jobs.
  2. Smoke one business route and one unrelated workspace on a zero-traffic candidate.
  3. After traffic moves, keep the SHOPLINE inventory writer off.
  4. Pull SHOPLINE orders strictly after the backup timestamp, then check ReCORE, Wise, and logs.

Owner emails

Locked. Unlock this card before an email is added.

At least two owners. The list is in git and the backup bucket, not in Firestore. If every login is locked, add an email with gcloud from the runbook. That does not block a restore.