Skip to content

Latest commit

 

History

History
46 lines (41 loc) · 1.54 KB

backup-snapshot-file-structure.md

File metadata and controls

46 lines (41 loc) · 1.54 KB
Raw

Backup snapshot file structure

Backup snapshots are stored in rotating increment directories named after the date and time the snapshot was taken. Each snapshot directory contains a full backup snapshot of all relevant data stores. Repository, Search, and Pages data is stored efficiently via hard links.

Please note Symlinks must be maintained when archiving backup snapshots. Dereferencing or excluding symlinks, or storing the snapshot contents on a filesystem which does not support symlinks will result in operational problems when the data is restored.

The following example shows a snapshot file hierarchy for hourly frequency. There are five snapshot directories, with the current symlink pointing to the most recent successful snapshot:

./data
   |- 20180124T010000
   |- 20180125T010000
   |- 20180126T010000
   |- 20180127T010000
   |- 20180128T010000
      |- audit-log
      |- benchmarks
      |- elasticsearch
      |- git-hooks
      |- hookshot
      |- pages
      |- repositories
      |- storage
      |- authorized-keys.json
      |- enterprise.ghl
      |- es-scan-complete
      |- manage-password
      |- mysql.sql.gz
      |- redis.rdb
      |- settings.json
      |- ssh-host-keys.tar
      |- ssl-ca-certificates.tar
      |- strategy
      |- uuid
      |- version
   |- current -> 20180128T010000

Note: the GHE_DATA_DIR variable set in backup.config can be used to change the disk location where snapshots are written.