diff --git a/docs/concepts-advanced/backups.md b/docs/concepts-advanced/backups.md index 5323bb9703..27f9210415 100644 --- a/docs/concepts-advanced/backups.md +++ b/docs/concepts-advanced/backups.md @@ -1,37 +1,222 @@ # Backups -Lagoon makes use of the [k8up operator](https://github.com/vshn/k8up) to provide backup functionality for both database data as well as containers' persistent storage volumes. This operator utilizes [Restic](https://github.com/restic/restic) to catalog these backups, which is typically connected to an AWS S3 bucket to provide secure, off-site storage for the generated backups. +Lagoon provides multiple methods for backing up environment data. Automated +backups are done without user interaction and manual backups are done on-demand, +as requested by users. -## Production Environments +## Automated Backups -### Backup Schedules +By default, Lagoon will run nightly backups for each database and persistent +volume. Daily backups are kept for seven days, and weekly backups are kept for +six weeks. -Backups of databases and containers' persistent storage volumes happens nightly within production environments by default. +Lagoon keeps an up to date list of available backups. To view them, check the +`Backups` tab of an environment in the Lagoon UI or use the Lagoon CLI (`lagoon +list backups --help`). -If a different backup schedule for production backups is required, this can be specified at a project level via setting the "Backup Schedule" variables in the project's [.lagoon.yml](../concepts-basics/lagoon-yml.md#backup-schedule) file. +!!! note "Lagoon administrators" + Automated backups are reliant on the [installation of + K8up](/installing-lagoon/requirements/#k8up-for-backups). Default settings + can be [configured](https://github.com/uselagoon/build-deploy-tool/blob/main/docs/buildrequirements.md#backup-related-variables) + per Lagoon remote. -### Backup Retention +### Downloading -Production environment backups will be held according to the following schedule by default: +In order to download the contents of a backup, it must first be retrieved. Click +the `Retrieve` button in the UI or run `lagoon retrieve --help`. After some time +(how long depends on how large the backup is), it will be available to download. +Click the `Download` button in the UI or run `lagoon get backup --help`. + +### Configuring + +Automated backups can be disabled by setting the `LAGOON_BACKUPS_DISABLED=true` +[environment +variable](/concepts-advanced/environment-variables/#build-time-environment-variables-lagoon-api). + +The storage bucket name can be changed by setting the `LAGOON_BAAS_BUCKET_NAME` +environment variable. **Do not change this unless asked by your Lagoon +administrator.** + +#### Backup Schedules + +Schedules use a cron-compatible syntax with the default being to run nightly +backups (`M H(22-2) * * *`). The `M` is special to Lagoon to allow for load +balancing, and must be set, any other value will cause build failures. + +!!! Info "Timezones:" + + Backup schedules use the cluster's local timezone. + +Each environment type can be configured to have it's own schedule: + +**Production** + +* The schedule can be set in code by changing the `backup-schedule` in the + [.lagoon.yml](../concepts-basics/lagoon-yml.md#backup-schedule) file. +* The schedule can be set using environment variables: + + | Name | Value | + |:-------------------------------------------|:--------------| + | `LAGOON_FEATURE_FLAG_CUSTOM_BACKUP_CONFIG` | `enabled` | + | `LAGOON_BACKUP_PROD_SCHEDULE` | Cron schedule | + +**Development** + +The schedule can be set using environment variables: + +| Name | Value | +|:-------------------------------------------|:--------------| +| `LAGOON_FEATURE_FLAG_CUSTOM_BACKUP_CONFIG` | `enabled` | +| `LAGOON_BACKUP_DEV_SCHEDULE` | Cron schedule | + +**Pull Request** + +The schedule can be set using environment variables: + +| Name | Value | +|:-------------------------------------------|:--------------| +| `LAGOON_FEATURE_FLAG_CUSTOM_BACKUP_CONFIG` | `enabled` | +| `LAGOON_BACKUP_PR_SCHEDULE` | Cron schedule | + +#### Backup Retention + +Backups will be held according to the following retention policy by default: * Daily: 7 * Weekly: 6 -* Monthly: 1 -* Hourly: 0 -If a different retention period for production backups is required, this can be specified at a project level via setting the "Backup Retention" variables in the project's [.lagoon.yml](../concepts-basics/lagoon-yml.md#backup-retention) file. +Production environments can set a different retention policy by changing +`backup-retention` in the +[.lagoon.yml](http://localhost:8000/concepts-basics/lagoon-yml/#backup-retention) +file. + +!!! warning + Retention policies are evaluated by Restic, a 3rd party open source + software. Make sure you are familiar with the [policy + options](https://restic.readthedocs.io/en/v0.17.1/060_forget.html#removing-snapshots-according-to-a-policy) + as they can be unintuitive. + +Other environment types cannot set a different retention policy. -## Development Environments +#### Storage Location + +Lagoon supports custom backup locations and credentials for any project when all +four of the following variables are set as `BUILD` type variables. The +environment variables need to be set at the project level (not per environment), +and requires a Lagoon deployment after setting them (for every environment). + +!!! danger + Using custom settings will override cluster default. Any misconfiguration or + invalid/expired credentials may cause automated backups to fail or be + inaccessible. -Backups of development environments are attempted nightly and are strictly a best effort service. +| Environment variable name | Purpose | +|:---------------------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| `LAGOON_BAAS_CUSTOM_BACKUP_ENDPOINT` | Specify the S3 compatible endpoint where any Lagoon initiated backups should be stored. An example for S3 Sydney would be: `https://s3.ap-southeast-2.amazonaws.com`. | +| `LAGOON_BAAS_CUSTOM_BACKUP_BUCKET` | Specify the bucket name where any Lagoon initiated backups should be stored.An example custom setting would be: `example-restore-bucket`. | +| `LAGOON_BAAS_CUSTOM_BACKUP_ACCESS_KEY` | Specify the access key Lagoon should use to access the custom backup bucket. An example custom setting would be: `AKIAIOSFODNN7EXAMPLE`. | +| `LAGOON_BAAS_CUSTOM_BACKUP_SECRET_KEY` | Specify the secret key Lagoon should use to access the custom backup bucket. An example custom setting would be: `wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY`. | -## Retrieving Backups +No public access is needed on the S3 bucket and can be made entirely private. -Backups stored in Restic will be tracked within Lagoon, and can be recovered via the "Backup" tab for each environment in the Lagoon UI. +Lagoon will automatically prune the files in these S3 buckets, so no object +retention policy is needed at the bucket level. -## Custom Backup and/or Restore Locations +#### Retrieval Location -Lagoon supports custom backup and restore locations via the use of the "[Custom Backup Settings](../concepts-advanced/environment-variables.md#custom-backup-settings)" and/or "[Custom Restore Settings](../concepts-advanced/environment-variables.md#custom-restore-location)" variables stored in the Lagoon API for each project. +Lagoon supports custom retrieval locations and credentials for any project when +all four of the following variables are set as `BUILD` type environment +variables. The environment variables need to be set at the project level (not +per environment), and requires a Lagoon deployment after setting them (for every +environment). !!! danger - Proceed with caution: Setting these variables will override backup/restore storage locations that may be configured at a cluster level. Any misconfiguration will cause backup/restore failures. + Using custom settings will override cluster default. Any misconfiguration or + invalid/expired credentials may cause retrieval of backups to fail or be + inaccessible. + +| Environment variable name | Purpose | +|:----------------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| `LAGOON_BAAS_CUSTOM_RESTORE_ENDPOINT` | Specify the S3 compatible endpoint where any Lagoon initiated restores should be stored. An example for S3 Sydney would be: `https://s3.ap-southeast-2.amazonaws.com`. | +| `LAGOON_BAAS_CUSTOM_RESTORE_BUCKET` | Specify the bucket name where any Lagoon initiated restores should be stored.An example custom setting would be: `example-restore-bucket`. | +| `LAGOON_BAAS_CUSTOM_RESTORE_ACCESS_KEY` | Specify the access key Lagoon should use to access the custom restore bucket. An example custom setting would be: `AKIAIOSFODNN7EXAMPLE`. | +| `LAGOON_BAAS_CUSTOM_RESTORE_SECRET_KEY` | Specify the secret key Lagoon should use to access the custom restore bucket. An example custom setting would be: `wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY`. | + +The S3 bucket must have public access enabled, as Lagoon will create [presigned +URLs](https://docs.aws.amazon.com/AmazonS3/latest/userguide/ShareObjectPreSignedURL.html) +for the objects inside the bucket as needed. + +An example AWS IAM policy that you can create to allow access to just the S3 +bucket `example-restore-bucket` is: + +```json title="aws_iam_restore_policy.json" +{ + "Version": "2012-10-17", + "Statement": [ + { + "Effect": "Allow", + "Action": [ + "s3:GetBucketLocation", + "s3:ListBucket" + ], + "Resource": [ + "arn:aws:s3:::example-restore-bucket" + ] + }, + { + "Effect": "Allow", + "Action": [ + "s3:PutObject", + "s3:GetObject", + "s3:GetObjectVersion", + "s3:GetBucketLocation", + "s3:PutObjectAcl" + ], + "Resource": [ + "arn:aws:s3:::example-restore-bucket/*" + ] + } + ] +} +``` + +For increased security and reduced storage costs you can opt into [removing +restored backups after a set +lifetime](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html) +(e.g. 7 days). Lagoon caters for this scenario gracefully and will re-create any +restored snapshots as needed. + +## Manual Backups + +Users can create manual backups by running a backup task, syncing data from one +environment to another, or by running custom commands in containers. + +### Tasks + +For Drupal projects, there are tasks available that will run drush backups. For +non-Drupal projects, a [custom task](/using-lagoon-advanced/custom-tasks/) can +be created to take a backup. + + + +### Sync + +For Drupal projects, the use of `drush` to sync the database and files is +recommneded. For non-Drupal projects, +[lagoon-sync](https://github.com/uselagoon/lagoon-sync) can be added to the +project and used to sync the database and files. + +### Manual + +The Lagoon cli base images contain all the tools needed to backup databases and +transfer files. A user familiar with `mysqldump` and `rsync` can make manual +backups. + +## Restoring Backups + +Lagoon cannot automatically restore backups. After downloading the backups, +users can restore them manually by [copying](/interacting/ssh/#copying-files) +them to the desired environment. diff --git a/docs/concepts-advanced/environment-variables.md b/docs/concepts-advanced/environment-variables.md index b359ff855f..1093702eca 100644 --- a/docs/concepts-advanced/environment-variables.md +++ b/docs/concepts-advanced/environment-variables.md @@ -168,70 +168,3 @@ This variable, if set, will define the [logging](../logging/logging.md) level yo On production environments, this value defaults to `E_ALL & ~E_DEPRECATED & ~E_STRICT & ~E_NOTICE`. On development environments, this value defaults to `E_ALL & ~E_DEPRECATED & ~E_STRICT`. - -### Custom Backup Settings - -Lagoon supports custom backup locations and credentials for any project when all four of the following variables are set as `BUILD` type variables. The environment variables need to be set at the project level (not per environment), and requires a Lagoon deployment after setting them (for every environment). - -Please note that any use of these variables means that all environment and database backups created and managed by Lagoon will be stored using these credentials, meaning that any interruption of these credentials' may lead to failed or inaccessible backups. - -| Environment variable name | Purpose | -|:---------------------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| `LAGOON_BAAS_CUSTOM_BACKUP_ENDPOINT` | Specify the S3 compatible endpoint where any Lagoon initiated backups should be stored. An example for S3 Sydney would be: `https://s3.ap-southeast-2.amazonaws.com`. | -| `LAGOON_BAAS_CUSTOM_BACKUP_BUCKET` | Specify the bucket name where any Lagoon initiated backups should be stored.An example custom setting would be: `example-restore-bucket`. | -| `LAGOON_BAAS_CUSTOM_BACKUP_ACCESS_KEY` | Specify the access key Lagoon should use to access the custom backup bucket. An example custom setting would be: `AKIAIOSFODNN7EXAMPLE`. | -| `LAGOON_BAAS_CUSTOM_BACKUP_SECRET_KEY` | Specify the secret key Lagoon should use to access the custom backup bucket. An example custom setting would be: `wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY`. | - -No public access is needed on the S3 bucket and can be made entirely private. - -Lagoon will automatically prune the files in these S3 buckets, so no object retention policy is needed at the bucket level. - -### Custom Restore Location - -Lagoon supports custom restore locations and credentials for any project when all four of the following variables are set as `BUILD` type environment variables. The environment variables need to be set at the project level (not per environment), and requires a Lagoon deployment after setting them (for every environment). - -Please note that any use of these variables means that all environment and database snapshots restored by Lagoon will be stored using these credentials. This means that any interruption of these credentials' access may lead to failed or inaccessible restored files. - -| Environment variable name | Purpose | -|:----------------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| `LAGOON_BAAS_CUSTOM_RESTORE_ENDPOINT` | Specify the S3 compatible endpoint where any Lagoon initiated restores should be stored. An example for S3 Sydney would be: `https://s3.ap-southeast-2.amazonaws.com`. | -| `LAGOON_BAAS_CUSTOM_RESTORE_BUCKET` | Specify the bucket name where any Lagoon initiated restores should be stored.An example custom setting would be: `example-restore-bucket`. | -| `LAGOON_BAAS_CUSTOM_RESTORE_ACCESS_KEY` | Specify the access key Lagoon should use to access the custom restore bucket. An example custom setting would be: `AKIAIOSFODNN7EXAMPLE`. | -| `LAGOON_BAAS_CUSTOM_RESTORE_SECRET_KEY` | Specify the secret key Lagoon should use to access the custom restore bucket. An example custom setting would be: `wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY`. | - -The S3 bucket must have public access enabled, as Lagoon will create [presigned URLs](https://docs.aws.amazon.com/AmazonS3/latest/userguide/ShareObjectPreSignedURL.html) for the objects inside the bucket as needed. - -An example AWS IAM policy that you can create to allow access to just the S3 bucket `example-restore-bucket` is: - -```json title="aws_iam_restore_policy.json" -{ - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action": [ - "s3:GetBucketLocation", - "s3:ListBucket" - ], - "Resource": [ - "arn:aws:s3:::example-restore-bucket" - ] - }, - { - "Effect": "Allow", - "Action": [ - "s3:PutObject", - "s3:GetObject", - "s3:GetObjectVersion", - "s3:GetBucketLocation", - "s3:PutObjectAcl" - ], - "Resource": [ - "arn:aws:s3:::example-restore-bucket/*" - ] - } - ] -} -``` - -For increased security and reduced storage costs you can opt into [removing restored backups after a set lifetime](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html) (e.g. 7 days). Lagoon caters for this scenario gracefully and will re-create any restored snapshots as needed. diff --git a/docs/concepts-basics/lagoon-yml.md b/docs/concepts-basics/lagoon-yml.md index 8eb4c67799..46402c45d5 100644 --- a/docs/concepts-basics/lagoon-yml.md +++ b/docs/concepts-basics/lagoon-yml.md @@ -181,7 +181,7 @@ Drupal & Drush 9: Sync database & files from master environment: Specify the number of monthly backups Lagoon should retain for your project's production environment\(s\). -The global default is `1` if this value is not specified. +The global default is `0` if this value is not specified. ### `backup-retention.production.weekly` @@ -207,7 +207,11 @@ The global default is `0` if this value is not specified. Specify the backup schedule for this project. Accepts cron-compatible syntax with the notable exception that the `Minute` block must be the letter `M`. Any other value in the `Minute` block will cause the Lagoon build to fail. This allows Lagoon to randomly choose a specific minute for these backups to happen, while users can specify the remainder of the schedule down to the hour. -The global default is `M H(22-2) * * *` if this value is not specified. Take note that these backups will use the cluster's local timezone. +The global default is `M H(22-2) * * *` if this value is not specified. + +!!! Info "Timezones:" + + Backup schedules use the cluster's local timezone. ## Environments diff --git a/docs/ja/concepts-advanced/environment-variables.md b/docs/ja/concepts-advanced/environment-variables.md index dfc8d61037..52c48ee241 100644 --- a/docs/ja/concepts-advanced/environment-variables.md +++ b/docs/ja/concepts-advanced/environment-variables.md @@ -168,70 +168,3 @@ DB_USER=$DB_USERNAME # DB_USERNAMEの値でDB_USERを再定義します。例え `production`環境では、この値はデフォルトで`E_ALL & ~E_DEPRECATED & ~E_STRICT & ~E_NOTICE`になります。 開発環境では、この値はデフォルトで`E_ALL & ~E_DEPRECATED & ~E_STRICT`になります。 - -### カスタムバックアップ設定 { #custom-backup-settings } - -Lagoonは、次の4つの変数すべてが`BUILD`タイプの変数として設定されている場合、任意のプロジェクトのカスタムバックアップ場所と認証情報をサポートします。環境変数はプロジェクトレベルで(環境ごとではなく)設定する必要があり、それらを設定した後にLagoonのデプロイメントが必要です(すべての環境について)。 - -これらの変数のいずれかを使用すると、Lagoonが作成および管理するすべての環境とデータベースのバックアップがこれらの認証情報を使用して格納されることを意味します。つまり、これらの認証情報の中断がバックアップの失敗またはアクセス不能を引き起こす可能性があります。 - -| 環境変数名 | 目的 | -|:---------------------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| `LAGOON_BAAS_CUSTOM_BACKUP_ENDPOINT` | Lagoonによって開始されたバックアップを保存するS3互換エンドポイントを指定しますS3 Sydneyの例は次のようになります。 `https://s3.ap-southeast-2.amazonaws.com` | -| `LAGOON_BAAS_CUSTOM_BACKUP_BUCKET` | Lagoonによって開始されたバックアップを保存するバケット名を指定します。カスタム設定の例は次のようになります。 `example-restore-bucket` | -| `LAGOON_BAAS_CUSTOM_BACKUP_ACCESS_KEY` | カスタム バックアップバケットにアクセスするためにLagoonが使用するアクセスキーを指定します。カスタム設定の例は次のようになります。 `AKIAIOSFODNN7EXAMPLE` | -| `LAGOON_BAAS_CUSTOM_BACKUP_SECRET_KEY` | カスタムバックアップバケットにアクセスするためにLagoonが使用する秘密キーを指定します。カスタム設定の例は次のようになります。 `wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY` | - -S3バケットではパブリックアクセスは不要で、完全にプライベートにすることができます。 - -LagoonはこれらのS3バケット内のファイルを自動的に削除するため、バケットレベルでのオブジェクト保持ポリシーは必要ありません。 - -### カスタム復元場所 { #custom-restore-location } - -`BUILD`タイプの環境変数として以下の全4つの変数が設定されている場合、任意のプロジェクトに対してカスタムリストアロケーションとクレデンシャルを設定できます。環境変数はプロジェクトレベルで設定する必要があり(環境ごとではなく)、それらを設定した後、Lagoonのデプロイが必要です(各環境について)。 - -これらの変数を使用すると、Lagoonによって復元されたすべての環境とデータベースのスナップショットがこれらのクレデンシャルを使用して保存されることに注意してください。これらのクレデンシャルへのアクセスが中断されると、復元されたファイルの失敗またはアクセス不能につながる可能性があることを意味します。 - -| 環境変数名 | 目的 | -|:----------------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| `LAGOON_BAAS_CUSTOM_RESTORE_ENDPOINT` | Lagoonによって開始された復元を保存する S3 互換エンドポイントを指定します。S3 Sydneyの例は次のようになります。 `https://s3.ap-southeast-2.amazonaws.com` | -| `LAGOON_BAAS_CUSTOM_RESTORE_BUCKET` | Lagoonによって開始された復元を保存するバケット名を指定します。カスタム設定の例は次のようになります。 `example-restore-bucket` | -| `LAGOON_BAAS_CUSTOM_RESTORE_ACCESS_KEY` | カスタム復元バケットにアクセスするためにLagoonが使用するアクセスキーを指定します。カスタム設定の例は次のようになります。 `AKIAIOSFODNN7EXAMPLE` | -| `LAGOON_BAAS_CUSTOM_RESTORE_SECRET_KEY` | カスタム復元バケットにアクセスするためにLagoonが使用するシークレットキーを指定します。カスタム設定の例は次のようになります。 `wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY` | - -Lagoonは必要に応じてバケット内のオブジェクトの[署名済みURL](https://docs.aws.amazon.com/AmazonS3/latest/userguide/ShareObjectPreSignedURL.html) を作成するため、S3バケットではパブリックアクセスが有効になっている必要があります。 - -S3バケット `example-restore-bucket` のみへのアクセスを許可するように作成できる AWS IAM ポリシーの例は次のとおりです。 - -```json title="aws_iam_restore_policy.json" -{ - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action": [ - "s3:GetBucketLocation", - "s3:ListBucket" - ], - "Resource": [ - "arn:aws:s3:::example-restore-bucket" - ] - }, - { - "Effect": "Allow", - "Action": [ - "s3:PutObject", - "s3:GetObject", - "s3:GetObjectVersion", - "s3:GetBucketLocation", - "s3:PutObjectAcl" - ], - "Resource": [ - "arn:aws:s3:::example-restore-bucket/*" - ] - } - ] -} -``` - -セキュリティの強化とストレージコスト削減のために、[設定されたライフタイム後に復元されたバックアップを削除する](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html)(例えば、7日間)を選択することができます。Lagoonはこのシナリオをうまく処理し、必要に応じて復元されたスナップショットを再作成します。 diff --git a/docs/ja/concepts-basics/lagoon-yml.md b/docs/ja/concepts-basics/lagoon-yml.md index 68cc75195e..f06add3520 100644 --- a/docs/ja/concepts-basics/lagoon-yml.md +++ b/docs/ja/concepts-basics/lagoon-yml.md @@ -171,7 +171,7 @@ Drupal & Drush 9: マスター環境からデータベースとファイルを プロジェクトのproduction環境の月次バックアップの保持数を指定します。 -この値が指定されていない場合、デフォルトは `1` です。 +この値が指定されていない場合、デフォルトは `0` です。 ### `backup-retention.production.weekly` @@ -197,7 +197,11 @@ Drupal & Drush 9: マスター環境からデータベースとファイルを プロジェクトのバックアップスケジュールを指定します。ただし、`Minute` ブロックは `M` でなければならず、他の値は Lagoon ビルドに失敗します。これにより、Lagoonはこれらのバックアップを何分に行うかランダムに選択することができ、ユーザーはスケジュールの残りの部分を時間単位で指定できます。 -この値が指定されていない場合、グローバルデフォルトは `M H(22-2) * * *` です。注意して頂きたいのは、 これらのバックアップは、クラスタのローカルタイムゾーンを使用します。 +この値が指定されていない場合、グローバルデフォルトは `M H(22-2) * * *` です。 + +!!! Info "タイムゾーン:" + + バックアップ スケジュールでは、クラスターのローカル タイムゾーンが使用されます。 ## 環境 { #environments } diff --git a/docs/ja/resources/faq.md b/docs/ja/resources/faq.md index cbacc39c26..ac7f3db20b 100644 --- a/docs/ja/resources/faq.md +++ b/docs/ja/resources/faq.md @@ -12,18 +12,6 @@ それは素晴らしいニュースです！[sales@amazee.io](mailto:sales@amazee.io)までメールでお問い合わせいただけます。 -## バックアップをどのように復元することができますか？ - -ファイルやデータベースのバックアップを提供しており、通常は最大で24時間ごとに取得しています。これらのバックアップはオフサイトで保存されています。 - -日次バックアップは最大7つ、週次バックアップは最大4つ保持しています。 - -バックアップの復元や回復が必要な場合は、お気軽にチケットを提出するか、チャットでメッセージを送ってください。喜んでお手伝いします！ - -## データベースダンプをどのようにダウンロードすることができますか？ - - - ## 私は無効なSSL証明書エラーが出ています まず最初に試すべきことは、[私たちのドキュメンテーションに記載されているSSLに関する情報](../concepts-basics/lagoon-yml.md#ssl-configuration-tls-acme)を参照してみてください。 diff --git a/docs/resources/faq.md b/docs/resources/faq.md index fe3f385509..7fb0a61fdf 100644 --- a/docs/resources/faq.md +++ b/docs/resources/faq.md @@ -12,18 +12,6 @@ If you've found a security issue, please send your findings to [security@amazee. That's great news! You can contact them via email at [sales@amazee.io](mailto:sales@amazee.io). -## How can I restore a backup? - -We have backups available for files and databases, typically taken every 24 hours at most. These backups are stored offsite. - -We keep up to 7 daily backups and 4 weekly backups. - -If you ever need to recover or restore a backup, feel free to submit a ticket or send us a message via chat and we will be more than happy to help! - -## How can I download a database dump? - - - ## I'm getting an invalid SSL certificate error The first thing to try is what is listed in [our documentation about SSL](../concepts-basics/lagoon-yml.md#ssl-configuration-tls-acme).