From 5a4e88b2dbbdc0d20018b1c408073bde87cc79b8 Mon Sep 17 00:00:00 2001 From: Margaret Eker Date: Wed, 14 Oct 2020 11:22:18 -0500 Subject: [PATCH 1/8] Add note about snapshot best practice --- src/cloud/architecture/pro-architecture.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/cloud/architecture/pro-architecture.md b/src/cloud/architecture/pro-architecture.md index b67bbb6410d..563a1c9bfb2 100644 --- a/src/cloud/architecture/pro-architecture.md +++ b/src/cloud/architecture/pro-architecture.md @@ -178,6 +178,9 @@ Weeks 12 to 22 | One backup per month - **Recovery Point Objective (RPO)**—is 1 hour for the first 24 hours; after which, the RPO is 6 hours (maximum time to last backup). - **Recovery Time Objective (RTO)**—depends on the size of the storage. Large EBS volumes take more time to restore. +{:.tip} +The automatic backups are intended for disaster recovery. During development, we highly recommend that you use the Snapshot option to create a snapshot of your environment as a first step after accessing your {{site.data.var.ece}} project. We also recommend creating snapshots before you apply any major changes to your environment. See [Snapshots and backup management](https://devdocs.magento.com/cloud/project/project-webint-snap.html). If you fail to create a snapshot, see [Reset an environment on Cloud] article in the _Magento Help Center_ for information on restoring your environment. + ### Production technology stack The Production environment has three virtual machines (VMs) behind an Elastic Load Balancer managed by an HAProxy per VM. Each VM includes the following technologies: From e8ea14b6f525574812522b2b2cf9ea35383948d4 Mon Sep 17 00:00:00 2001 From: Margaret Eker Date: Wed, 14 Oct 2020 11:45:56 -0500 Subject: [PATCH 2/8] Corrections to note about backups --- src/cloud/architecture/pro-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/cloud/architecture/pro-architecture.md b/src/cloud/architecture/pro-architecture.md index 563a1c9bfb2..28d07cc7c23 100644 --- a/src/cloud/architecture/pro-architecture.md +++ b/src/cloud/architecture/pro-architecture.md @@ -179,7 +179,7 @@ Weeks 12 to 22 | One backup per month - **Recovery Time Objective (RTO)**—depends on the size of the storage. Large EBS volumes take more time to restore. {:.tip} -The automatic backups are intended for disaster recovery. During development, we highly recommend that you use the Snapshot option to create a snapshot of your environment as a first step after accessing your {{site.data.var.ece}} project. We also recommend creating snapshots before you apply any major changes to your environment. See [Snapshots and backup management](https://devdocs.magento.com/cloud/project/project-webint-snap.html). If you fail to create a snapshot, see [Reset an environment on Cloud] article in the _Magento Help Center_ for information on restoring your environment. +On Pro Staging and Production environments, you must submit a support ticket to restore an environment from an automatic backup. You can backup the database and code for your Production and Staging environments using CLI commands. See [Dump your database]({{ site.baseurl }}/cloud/project/project-webint-snap.html#db-dumpump] and [bin/magento setup:backup]({{site.baseurl }}/guides/v2.4/reference/cli/magento-commerce.htm#setupbackup). For Integration environments, we highly recommend that you create a snapshot of your environment as a first step after accessing your {{site.data.var.ece}} project and before applying any major changes. See [Snapshots and backup management](https://devdocs.magento.com/cloud/project/project-webint-snap.html). ### Production technology stack From 9ee185e09a2f6c014f96c2efe497cada92d0547c Mon Sep 17 00:00:00 2001 From: Margaret Eker Date: Wed, 14 Oct 2020 11:50:07 -0500 Subject: [PATCH 3/8] Update src/cloud/architecture/pro-architecture.md --- src/cloud/architecture/pro-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/cloud/architecture/pro-architecture.md b/src/cloud/architecture/pro-architecture.md index 28d07cc7c23..c40e3cd9c21 100644 --- a/src/cloud/architecture/pro-architecture.md +++ b/src/cloud/architecture/pro-architecture.md @@ -179,7 +179,7 @@ Weeks 12 to 22 | One backup per month - **Recovery Time Objective (RTO)**—depends on the size of the storage. Large EBS volumes take more time to restore. {:.tip} -On Pro Staging and Production environments, you must submit a support ticket to restore an environment from an automatic backup. You can backup the database and code for your Production and Staging environments using CLI commands. See [Dump your database]({{ site.baseurl }}/cloud/project/project-webint-snap.html#db-dumpump] and [bin/magento setup:backup]({{site.baseurl }}/guides/v2.4/reference/cli/magento-commerce.htm#setupbackup). For Integration environments, we highly recommend that you create a snapshot of your environment as a first step after accessing your {{site.data.var.ece}} project and before applying any major changes. See [Snapshots and backup management](https://devdocs.magento.com/cloud/project/project-webint-snap.html). +On Pro Staging and Production environments, you must submit a support ticket to restore an environment from an automatic backup. You can backup the database and code for your Production and Staging environments using CLI commands. See [Dump your database]({{ site.baseurl }}/cloud/project/project-webint-snap.html#db-dumpump] and [bin/magento setup:backup]({{site.baseurl }}/guides/v2.4/reference/cli/magento-commerce.htm#setupbackup). For Integration environments, we highly recommend that you create a snapshot as a first step after accessing your {{site.data.var.ece}} project and before applying any major changes. See [Snapshots and backup management](https://devdocs.magento.com/cloud/project/project-webint-snap.html). ### Production technology stack From 510cfa02d1ebc1266c33d7e5064f471590ec25d5 Mon Sep 17 00:00:00 2001 From: Margaret Eker Date: Wed, 14 Oct 2020 17:16:50 -0500 Subject: [PATCH 4/8] Update src/cloud/architecture/pro-architecture.md Co-authored-by: hguthrie --- src/cloud/architecture/pro-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/cloud/architecture/pro-architecture.md b/src/cloud/architecture/pro-architecture.md index c40e3cd9c21..61e237e7e7c 100644 --- a/src/cloud/architecture/pro-architecture.md +++ b/src/cloud/architecture/pro-architecture.md @@ -178,7 +178,7 @@ Weeks 12 to 22 | One backup per month - **Recovery Point Objective (RPO)**—is 1 hour for the first 24 hours; after which, the RPO is 6 hours (maximum time to last backup). - **Recovery Time Objective (RTO)**—depends on the size of the storage. Large EBS volumes take more time to restore. -{:.tip} +{:.bs-callout-tip} On Pro Staging and Production environments, you must submit a support ticket to restore an environment from an automatic backup. You can backup the database and code for your Production and Staging environments using CLI commands. See [Dump your database]({{ site.baseurl }}/cloud/project/project-webint-snap.html#db-dumpump] and [bin/magento setup:backup]({{site.baseurl }}/guides/v2.4/reference/cli/magento-commerce.htm#setupbackup). For Integration environments, we highly recommend that you create a snapshot as a first step after accessing your {{site.data.var.ece}} project and before applying any major changes. See [Snapshots and backup management](https://devdocs.magento.com/cloud/project/project-webint-snap.html). ### Production technology stack From a1ff769501658ba1b1fb4efc421352c7d8f0b45e Mon Sep 17 00:00:00 2001 From: Margaret Eker Date: Wed, 14 Oct 2020 17:17:07 -0500 Subject: [PATCH 5/8] Update src/cloud/architecture/pro-architecture.md Co-authored-by: hguthrie --- src/cloud/architecture/pro-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/cloud/architecture/pro-architecture.md b/src/cloud/architecture/pro-architecture.md index 61e237e7e7c..23f6e7d6f76 100644 --- a/src/cloud/architecture/pro-architecture.md +++ b/src/cloud/architecture/pro-architecture.md @@ -179,7 +179,7 @@ Weeks 12 to 22 | One backup per month - **Recovery Time Objective (RTO)**—depends on the size of the storage. Large EBS volumes take more time to restore. {:.bs-callout-tip} -On Pro Staging and Production environments, you must submit a support ticket to restore an environment from an automatic backup. You can backup the database and code for your Production and Staging environments using CLI commands. See [Dump your database]({{ site.baseurl }}/cloud/project/project-webint-snap.html#db-dumpump] and [bin/magento setup:backup]({{site.baseurl }}/guides/v2.4/reference/cli/magento-commerce.htm#setupbackup). For Integration environments, we highly recommend that you create a snapshot as a first step after accessing your {{site.data.var.ece}} project and before applying any major changes. See [Snapshots and backup management](https://devdocs.magento.com/cloud/project/project-webint-snap.html). +On Pro Staging and Production environments, you must submit a support ticket to restore an environment from an automatic backup. You can backup the database and code for your Production and Staging environments using CLI commands. See [Dump your database]({{ site.baseurl }}/cloud/project/project-webint-snap.html#db-dump) and [bin/magento setup:backup]({{site.baseurl }}/guides/v2.4/reference/cli/magento-commerce.htm#setupbackup). For Integration environments, we highly recommend that you create a snapshot as a first step after accessing your {{site.data.var.ece}} project and before applying any major changes. See [Snapshots and backup management](https://devdocs.magento.com/cloud/project/project-webint-snap.html). ### Production technology stack From 46cc1e64cddbb01ec43352a138c4ffa824e8cff3 Mon Sep 17 00:00:00 2001 From: Margaret Eker Date: Wed, 14 Oct 2020 17:18:28 -0500 Subject: [PATCH 6/8] Update src/cloud/architecture/pro-architecture.md --- src/cloud/architecture/pro-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/cloud/architecture/pro-architecture.md b/src/cloud/architecture/pro-architecture.md index 23f6e7d6f76..75fbd2949f8 100644 --- a/src/cloud/architecture/pro-architecture.md +++ b/src/cloud/architecture/pro-architecture.md @@ -179,7 +179,7 @@ Weeks 12 to 22 | One backup per month - **Recovery Time Objective (RTO)**—depends on the size of the storage. Large EBS volumes take more time to restore. {:.bs-callout-tip} -On Pro Staging and Production environments, you must submit a support ticket to restore an environment from an automatic backup. You can backup the database and code for your Production and Staging environments using CLI commands. See [Dump your database]({{ site.baseurl }}/cloud/project/project-webint-snap.html#db-dump) and [bin/magento setup:backup]({{site.baseurl }}/guides/v2.4/reference/cli/magento-commerce.htm#setupbackup). For Integration environments, we highly recommend that you create a snapshot as a first step after accessing your {{site.data.var.ece}} project and before applying any major changes. See [Snapshots and backup management](https://devdocs.magento.com/cloud/project/project-webint-snap.html). +On Pro Staging and Production environments, you must submit a support ticket to restore an environment from an automatic backup. You can backup the database and code for your Production and Staging environments using CLI commands. See [Dump your database]({{site.baseurl}}/cloud/project/project-webint-snap.html#db-dump) and [bin/magento setup:backup]({{site.baseurl }}/guides/v2.4/reference/cli/magento-commerce.htm#setupbackup). For Integration environments, we highly recommend that you create a snapshot as a first step after accessing your {{site.data.var.ece}} project and before applying any major changes. See [Snapshots and backup management]({{ site.baseurl}}/cloud/project/project-webint-snap.html). ### Production technology stack From 7871283610b04736798c39cbfb06521e481c5e27 Mon Sep 17 00:00:00 2001 From: Margaret Eker Date: Wed, 14 Oct 2020 17:18:55 -0500 Subject: [PATCH 7/8] Update src/cloud/architecture/pro-architecture.md --- src/cloud/architecture/pro-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/cloud/architecture/pro-architecture.md b/src/cloud/architecture/pro-architecture.md index 75fbd2949f8..fb19c173e06 100644 --- a/src/cloud/architecture/pro-architecture.md +++ b/src/cloud/architecture/pro-architecture.md @@ -179,7 +179,7 @@ Weeks 12 to 22 | One backup per month - **Recovery Time Objective (RTO)**—depends on the size of the storage. Large EBS volumes take more time to restore. {:.bs-callout-tip} -On Pro Staging and Production environments, you must submit a support ticket to restore an environment from an automatic backup. You can backup the database and code for your Production and Staging environments using CLI commands. See [Dump your database]({{site.baseurl}}/cloud/project/project-webint-snap.html#db-dump) and [bin/magento setup:backup]({{site.baseurl }}/guides/v2.4/reference/cli/magento-commerce.htm#setupbackup). For Integration environments, we highly recommend that you create a snapshot as a first step after accessing your {{site.data.var.ece}} project and before applying any major changes. See [Snapshots and backup management]({{ site.baseurl}}/cloud/project/project-webint-snap.html). +On Pro Staging and Production environments, you must submit a support ticket to restore an environment from an automatic backup. You can backup the database and code for your Production and Staging environments using CLI commands. See [Dump your database]({{site.baseurl}}/cloud/project/project-webint-snap.html#db-dump) and [bin/magento setup:backup]({{site.baseurl }}/guides/v2.4/reference/cli/magento-commerce.htm#setupbackup). For Integration environments, we highly recommend that you create a snapshot as a first step after accessing your {{site.data.var.ece}} project and before applying any major changes. See [Snapshots and backup management]({{site.baseurl}}/cloud/project/project-webint-snap.html). ### Production technology stack From 3711ca5af8eac88c902289acb9a02096ffb86ab2 Mon Sep 17 00:00:00 2001 From: Margaret Eker Date: Thu, 15 Oct 2020 10:16:13 -0500 Subject: [PATCH 8/8] Update src/cloud/architecture/pro-architecture.md --- src/cloud/architecture/pro-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/cloud/architecture/pro-architecture.md b/src/cloud/architecture/pro-architecture.md index fb19c173e06..48840e2b590 100644 --- a/src/cloud/architecture/pro-architecture.md +++ b/src/cloud/architecture/pro-architecture.md @@ -179,7 +179,7 @@ Weeks 12 to 22 | One backup per month - **Recovery Time Objective (RTO)**—depends on the size of the storage. Large EBS volumes take more time to restore. {:.bs-callout-tip} -On Pro Staging and Production environments, you must submit a support ticket to restore an environment from an automatic backup. You can backup the database and code for your Production and Staging environments using CLI commands. See [Dump your database]({{site.baseurl}}/cloud/project/project-webint-snap.html#db-dump) and [bin/magento setup:backup]({{site.baseurl }}/guides/v2.4/reference/cli/magento-commerce.htm#setupbackup). For Integration environments, we highly recommend that you create a snapshot as a first step after accessing your {{site.data.var.ece}} project and before applying any major changes. See [Snapshots and backup management]({{site.baseurl}}/cloud/project/project-webint-snap.html). +On Pro Staging and Production environments, you must submit a support ticket to restore an environment from an automatic backup. You can backup the database and code for your Production and Staging environments using CLI commands. See [Dump your database]({{site.baseurl}}/cloud/project/project-webint-snap.html#db-dump) and [bin/magento setup:backup]({{site.baseurl }}/guides/v2.4/reference/cli/magento-commerce.html#setupbackup). For Integration environments, we highly recommend that you create a snapshot as a first step after accessing your {{site.data.var.ece}} project and before applying any major changes. See [Snapshots and backup management]({{site.baseurl}}/cloud/project/project-webint-snap.html). ### Production technology stack