Add note about snapshot best practice (#8044)

* Add note about snapshot best practice

* Corrections to note about backups

* Update src/cloud/architecture/pro-architecture.md

* Update src/cloud/architecture/pro-architecture.md

Co-authored-by: hguthrie <hguthrie@users.noreply.github.com>

* Update src/cloud/architecture/pro-architecture.md

Co-authored-by: hguthrie <hguthrie@users.noreply.github.com>

* Update src/cloud/architecture/pro-architecture.md

* Update src/cloud/architecture/pro-architecture.md

* Update src/cloud/architecture/pro-architecture.md

Co-authored-by: hguthrie <hguthrie@users.noreply.github.com>

Author: meker12

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.
 
+{:.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.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
 
 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: