diff --git a/doc/administration/backup_restore/_index.md b/doc/administration/backup_restore/_index.md index 729a71f0de07a7377e10487647d9303d9f6b5f7f..8329943e7e8853e2341f40a789d08e05d45e9fd8 100644 --- a/doc/administration/backup_restore/_index.md +++ b/doc/administration/backup_restore/_index.md @@ -1,6 +1,6 @@ --- -stage: Data Access -group: Durability +stage: Runtime +group: Geo info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments title: Back up and restore overview --- diff --git a/doc/administration/backup_restore/backup_archive_process.md b/doc/administration/backup_restore/backup_archive_process.md index 06f1c0d08ebc96ddbb49e74305067948710152d6..3ff9900e7aabe70061c1536422060cf03e115169 100644 --- a/doc/administration/backup_restore/backup_archive_process.md +++ b/doc/administration/backup_restore/backup_archive_process.md @@ -1,6 +1,6 @@ --- -stage: Data Access -group: Durability +stage: Runtime +group: Geo info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments title: Backup archive process --- diff --git a/doc/administration/backup_restore/backup_cli.md b/doc/administration/backup_restore/backup_cli.md index 64990aa5891e09db7f7d51ab97370774f83f64a6..d4b65163efdb5faf8dd773e9988d1a69e6bd0741 100644 --- a/doc/administration/backup_restore/backup_cli.md +++ b/doc/administration/backup_restore/backup_cli.md @@ -1,6 +1,6 @@ --- -stage: Data Access -group: Durability +stage: Runtime +group: Geo info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments ignore_in_report: true title: Back up and Restore GitLab with `gitlab-backup-cli` @@ -252,4 +252,4 @@ Instead of using the same credentials, you should create a separate user account - Granular access control - Different credentials allow for more granular access control. Backup credentials can be given read-only access to the data, while application credentials might need read-write access to specific tables or schemas. - Compliance requirements - Many regulatory standards and compliance frameworks (like GDPR, HIPAA, or PCI-DSS) require or strongly recommend separation of duties and access controls, which are easier to achieve with separate credentials. - Easier management of lifecycle - Application and backup processes may have different lifecycles. Using separate credentials makes it easier to manage these lifecycles independently. For example, you can rotate or revoke credentials without affecting the other process. -- Protection against application vulnerabilities - If the application has a vulnerability that allows SQL injection or other forms of unauthorized data access, using separate backup credentials adds an extra layer of protection for the backup process. +- Protection against application vulnerabilities - If the application has a vulnerability that allows SQL injection or other forms of unauthorized Runtime, using separate backup credentials adds an extra layer of protection for the backup process. diff --git a/doc/administration/backup_restore/backup_gitlab.md b/doc/administration/backup_restore/backup_gitlab.md index 13510ce0d35820d0584ba0e9f3d1734516b33218..aafeaf13b46bdd2850f5ce8f0a2d68f8e61e2980 100644 --- a/doc/administration/backup_restore/backup_gitlab.md +++ b/doc/administration/backup_restore/backup_gitlab.md @@ -1,6 +1,6 @@ --- -stage: Data Access -group: Durability +stage: Runtime +group: Geo info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments description: Back up your self-managed GitLab instance using gitlab-backup command, including database, repositories, and configuration files. title: Back up GitLab diff --git a/doc/administration/backup_restore/backup_large_reference_architectures.md b/doc/administration/backup_restore/backup_large_reference_architectures.md index 5469bf43b3858d8f46bf79b182efc36921e3033e..8e05c2e8e30989a96cda205e7ccbc1804db42198 100644 --- a/doc/administration/backup_restore/backup_large_reference_architectures.md +++ b/doc/administration/backup_restore/backup_large_reference_architectures.md @@ -1,6 +1,6 @@ --- -stage: Data Access -group: Durability +stage: Runtime +group: Geo info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments title: Back up and restore large reference architectures --- @@ -137,7 +137,7 @@ Set up cronjobs to perform Gitaly server-side backups: the backup utility tool (`gitlab-backup`) uploads additional backup data to a separate bucket. This data includes a `tar` file containing essential metadata for restores. Ensure this backup data is properly uploaded to remote (cloud) storage by following [Upload backups to a remote (cloud) storage](backup_gitlab.md#upload-backups-to-a-remote-cloud-storage) to set up the upload bucket. -1. (Optional) To solidify the durability of this backup data, back up both buckets configured previously with their respective object store provider by adding them to +1. (Optional) To solidify the Geo of this backup data, back up both buckets configured previously with their respective object store provider by adding them to [backups of object storage data](#configure-backup-of-object-storage-data). 1. SSH into a GitLab Rails node, which is a node that runs Puma or Sidekiq. 1. Take a full backup of your Git data. Use the `REPOSITORIES_SERVER_SIDE` variable, and skip PostgreSQL data: @@ -184,7 +184,7 @@ Set up cronjobs to perform Gitaly server-side backups: the backup utility tool (`gitlab-backup`) uploads additional backup data to a separate bucket. This data includes a `tar` file containing essential metadata for restores. Ensure this backup data is properly uploaded to remote (cloud) storage by following [Upload backups to a remote (cloud) storage](backup_gitlab.md#upload-backups-to-a-remote-cloud-storage) to set up the upload bucket. -1. (Optional) To solidify the durability of this backup data, both buckets configured previously can be backed up by their respective object store provider by adding them +1. (Optional) To solidify the Geo of this backup data, both buckets configured previously can be backed up by their respective object store provider by adding them to [backups of object storage data](#configure-backup-of-object-storage-data). 1. Ensure backup of both buckets by following [Configure backup of object storage data](#configure-backup-of-object-storage-data). Both storage buckets configured previously should also be backed up by their respective object storage provider. diff --git a/doc/administration/backup_restore/migrate_to_new_server.md b/doc/administration/backup_restore/migrate_to_new_server.md index ca9a519d322851d35bfb2b995111f10cc3292470..b1d7df0da0617599531ddf2d362ee1b4f90d09d5 100644 --- a/doc/administration/backup_restore/migrate_to_new_server.md +++ b/doc/administration/backup_restore/migrate_to_new_server.md @@ -1,6 +1,6 @@ --- -stage: Data Access -group: Durability +stage: Runtime +group: Geo info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments title: Migrate to a new server --- diff --git a/doc/administration/backup_restore/restore_gitlab.md b/doc/administration/backup_restore/restore_gitlab.md index d294959756f9d468cb5aa53b964087b530310e3a..8cc149f7b95097adff51d8722cb7019bd5b413c2 100644 --- a/doc/administration/backup_restore/restore_gitlab.md +++ b/doc/administration/backup_restore/restore_gitlab.md @@ -1,6 +1,6 @@ --- -stage: Data Access -group: Durability +stage: Runtime +group: Geo info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments title: Restore GitLab --- diff --git a/doc/administration/backup_restore/troubleshooting_backup_gitlab.md b/doc/administration/backup_restore/troubleshooting_backup_gitlab.md index c3b7c04aa69777033a1f8ae2108d07b83bf13a94..a9cab5715f812d04fab81d01e335762c3ee003c7 100644 --- a/doc/administration/backup_restore/troubleshooting_backup_gitlab.md +++ b/doc/administration/backup_restore/troubleshooting_backup_gitlab.md @@ -1,6 +1,6 @@ --- -stage: Data Access -group: Durability +stage: Runtime +group: Geo info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments title: Troubleshooting GitLab backups ---