Last updated: 2025-12-19

1. Important Points to Understand #

• Backup: “Insurance” for recovery from failures and mistakes (stored in a separate location)

• Snapshot: A “checkpoint” for temporary safekeeping and rollback before updates (primarily for short-term use)
  Snapshots are convenient, but they do not replace backups.

2. Standard Backup (Automatic, Daily) #

2.1 Standard Specifications #

• Daily automatic backup: 1 generation (previous day) is included as standard

• We provide restore functionality from backups

2.2 Storage Location and Method #

• Backups use a method with physically separate computing infrastructure

2.3 Backup Precautions #

• Backup is on a best-effort basis and does not guarantee recovery of all data

• Application consistency (database consistency, etc.) at the time of backup depends on your system configuration

  • For critical systems, consider stopping/flushing/synchronizing on the application side

• Restore will generally restore to the target point in time, so the current data of the restore target will be overwritten

3. Additional Backup Generations (Optional) #

• Example of additional storage: +$110 / month per generation

※Actual pricing follows the contract screen or upgrade screen in the client portal.

• Examples:

  • 7 generations retained: 6 additional generations → +$660/month

  • 14 generations retained: 13 additional generations → +$1,430/month

※The upper limit of retained generations, application timing, and deletion (rotation) behavior follow the contract screen and management screen display.
※If you reduce the number of retained generations, older generations may be deleted.

4. Snapshot (Manual/Operations-oriented) #

4.1 Standard Specifications #

• Snapshot: 1 included as standard

4.2 Additional Snapshots (Optional) #

• Example of additional: +$110 / month per snapshot

※Actual pricing follows the contract screen or upgrade screen in the client portal.

4.3 Snapshot Precautions #

• Snapshots are convenient for rollback before updates, but are “not a backup replacement” for the following reasons

  • May be lost simultaneously in case of storage failure, accidental deletion, or major failure

  • Not suitable for long-term storage

• For systems where consistency is critical, such as databases and queues, we recommend synchronizing on the application side before taking a snapshot

5. Recommended Operations (Common Best Practices) #

• Before OS/middleware updates: Create a snapshot

• Production environment: 7 or more generations of backups recommended (14 generations depending on requirements)

• Critical data: In addition to our backups, external backups on your side are also recommended (3-2-1 rule, etc.)