From ba8debd2b50f57bbdf0e6341508fac29dd4e4f32 Mon Sep 17 00:00:00 2001
From: Yevhen Miroshnychenko <miroshny@adobe.com>
Date: Mon, 2 Mar 2020 17:31:31 -0600
Subject: [PATCH 1/8] MAGECLOUD-4890: Implement support for backup databases
 from split connections for `ece-tools`

---
 src/cloud/project/project-webint-snap.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/src/cloud/project/project-webint-snap.md b/src/cloud/project/project-webint-snap.md
index 5e8d4896ef4..52c8dc75515 100644
--- a/src/cloud/project/project-webint-snap.md
+++ b/src/cloud/project/project-webint-snap.md
@@ -117,6 +117,10 @@ To restore a snapshot using the Magento CLI:
 ## Dump your database {#db-dump}
 
 You can create a copy of your database using [`magento/ece-tools`]({{ site.baseurl }}/cloud/reference/cloud-composer.html#ece-tools).
+By default, the command creates backups using all the connections to the databases that are available through the environment configuration. That is, if split databases are used, by default backup copies will be created for these databases
+If you need to create backups by selecting one or more databases, for this you need to transfer the database names as an argument to the console command
+
+For help, use the command: ```php vendor/bin/ece-tools db-dump --help ```
 
 {:.procedure}
 To create a database dump:
@@ -140,7 +144,7 @@ To create a database dump:
  {:.bs-callout-info}
 
 -  We recommend putting the application in maintenance mode before doing a database dump in Production environments.
--  The command creates an archive in your local project directory called  `dump-<timestamp>.sql.gz`.
+-  The command creates an archive in your local project directory called  `dump-<label><timestamp>.sql.gz`.
 -  If an error occurs during the dump, the command deletes the dump file to conserve disk space. Review the logs for details (`var/log/cloud.log`).
 -  For Pro Production environments, this command dumps only from one of three high-availability nodes, so production data written to a different node during the dump may not be copied. It generates a `var/dbdump.lock` file to prevent running the command on more than one node.
 

From 917839f837c9c4f898be5f10e7d1e174cd3a170a Mon Sep 17 00:00:00 2001
From: Yevhen Miroshnychenko <y.a.miroshnychenko@gmail.com>
Date: Tue, 3 Mar 2020 07:02:20 -0600
Subject: [PATCH 2/8] Update src/cloud/project/project-webint-snap.md

Co-Authored-By: Margaret Eker <meker@adobe.com>
---
 src/cloud/project/project-webint-snap.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/src/cloud/project/project-webint-snap.md b/src/cloud/project/project-webint-snap.md
index 52c8dc75515..572be7851ea 100644
--- a/src/cloud/project/project-webint-snap.md
+++ b/src/cloud/project/project-webint-snap.md
@@ -116,8 +116,9 @@ To restore a snapshot using the Magento CLI:
 
 ## Dump your database {#db-dump}
 
-You can create a copy of your database using [`magento/ece-tools`]({{ site.baseurl }}/cloud/reference/cloud-composer.html#ece-tools).
-By default, the command creates backups using all the connections to the databases that are available through the environment configuration. That is, if split databases are used, by default backup copies will be created for these databases
+You can create a copy of your database using the [`magento/ece-tools`]({{ site.baseurl }}/cloud/reference/cloud-composer.html#ece-tools) `db-dump` command.
+
+By default, this command creates backups for all database connections that are specified in the environment configuration. For example, if you configured your project to use split databases, the `db-dump` operation creates backups for each of the configured databases.
 If you need to create backups by selecting one or more databases, for this you need to transfer the database names as an argument to the console command
 
 For help, use the command: ```php vendor/bin/ece-tools db-dump --help ```

From 6ee7f74c0dfc0757fa2625cce8822f6704d8d23b Mon Sep 17 00:00:00 2001
From: Yevhen Miroshnychenko <y.a.miroshnychenko@gmail.com>
Date: Tue, 3 Mar 2020 07:03:49 -0600
Subject: [PATCH 3/8] Update src/cloud/project/project-webint-snap.md

Co-Authored-By: Margaret Eker <meker@adobe.com>
---
 src/cloud/project/project-webint-snap.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/cloud/project/project-webint-snap.md b/src/cloud/project/project-webint-snap.md
index 572be7851ea..7ee9994fe96 100644
--- a/src/cloud/project/project-webint-snap.md
+++ b/src/cloud/project/project-webint-snap.md
@@ -145,7 +145,7 @@ To create a database dump:
  {:.bs-callout-info}
 
 -  We recommend putting the application in maintenance mode before doing a database dump in Production environments.
--  The command creates an archive in your local project directory called  `dump-<label><timestamp>.sql.gz`.
+-  This command creates an archive file for each database backup with the file name pattern `dump-<label><timestamp>.sql.gz` where  _label_ is replaced with the database name.  The archive files are available in your local project directory.
 -  If an error occurs during the dump, the command deletes the dump file to conserve disk space. Review the logs for details (`var/log/cloud.log`).
 -  For Pro Production environments, this command dumps only from one of three high-availability nodes, so production data written to a different node during the dump may not be copied. It generates a `var/dbdump.lock` file to prevent running the command on more than one node.
 

From fd34d2669e3a535e9a56972ffa810cf7e2abb8ef Mon Sep 17 00:00:00 2001
From: Yevhen Miroshnychenko <y.a.miroshnychenko@gmail.com>
Date: Tue, 3 Mar 2020 07:03:57 -0600
Subject: [PATCH 4/8] Update src/cloud/project/project-webint-snap.md

Co-Authored-By: Margaret Eker <meker@adobe.com>
---
 src/cloud/project/project-webint-snap.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/cloud/project/project-webint-snap.md b/src/cloud/project/project-webint-snap.md
index 7ee9994fe96..8b453845882 100644
--- a/src/cloud/project/project-webint-snap.md
+++ b/src/cloud/project/project-webint-snap.md
@@ -146,7 +146,7 @@ To create a database dump:
 
 -  We recommend putting the application in maintenance mode before doing a database dump in Production environments.
 -  This command creates an archive file for each database backup with the file name pattern `dump-<label><timestamp>.sql.gz` where  _label_ is replaced with the database name.  The archive files are available in your local project directory.
--  If an error occurs during the dump, the command deletes the dump file to conserve disk space. Review the logs for details (`var/log/cloud.log`).
+-  If an error occurs during the dump, the command deletes any dump files to conserve disk space. Review the logs for details (`var/log/cloud.log`).
 -  For Pro Production environments, this command dumps only from one of three high-availability nodes, so production data written to a different node during the dump may not be copied. It generates a `var/dbdump.lock` file to prevent running the command on more than one node.
 
 {:.bs-callout-tip}

From ef7339423993afd13e65e81d9916435aed7b13d5 Mon Sep 17 00:00:00 2001
From: Yevhen Miroshnychenko <y.a.miroshnychenko@gmail.com>
Date: Tue, 3 Mar 2020 10:55:10 -0600
Subject: [PATCH 5/8] Add examples

---
 src/cloud/project/project-webint-snap.md | 18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)

diff --git a/src/cloud/project/project-webint-snap.md b/src/cloud/project/project-webint-snap.md
index 8b453845882..e78b408f48f 100644
--- a/src/cloud/project/project-webint-snap.md
+++ b/src/cloud/project/project-webint-snap.md
@@ -139,7 +139,23 @@ To create a database dump:
 1. Enter the following command:
 
     ```bash
-    vendor/bin/ece-tools db-dump
+    php vendor/bin/ece-tools db-dump
+    ```
+
+    ```terminal
+    php vendor/bin/ece-tools db-dump
+    The db-dump operation switches the site to maintenance mode, stops all active cron jobs and consumer queue processes, and     disables cron jobs before starting the the dump process.
+    Your site will not receive any traffic until the operation completes.
+    Do you wish to proceed with this process? (y/N)? y
+    2020-01-28 16:38:08] INFO: Starting backup.
+    [2020-01-28 16:38:08] NOTICE: Enabling Maintenance mode
+    [2020-01-28 16:38:10] INFO: Trying to kill running cron jobs and consumers processes
+    [2020-01-28 16:38:10] INFO: Running Magento cron and consumers processes were not found.
+    [2020-01-28 16:38:10] INFO: Waiting for lock on db dump.
+    [2020-01-28 16:38:10] INFO: Start creation DB dump for main database...
+    [2020-01-28 16:38:10] INFO: Finished DB dump for main database, it can be found here: /tmp/qxmtlseakof6y/dump-main-1580229490.sql.gz
+    [2020-01-28 16:38:10] INFO: Backup completed.
+    [2020-01-28 16:38:11] NOTICE: Maintenance mode is disabled.
     ```
 
  {:.bs-callout-info}

From 0a929ae27bf9964f28b58095a9361e0f151455b4 Mon Sep 17 00:00:00 2001
From: Yevhen Miroshnychenko <y.a.miroshnychenko@gmail.com>
Date: Tue, 3 Mar 2020 10:55:25 -0600
Subject: [PATCH 6/8] Update src/cloud/project/project-webint-snap.md

Co-Authored-By: Margaret Eker <meker@adobe.com>
---
 src/cloud/project/project-webint-snap.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/src/cloud/project/project-webint-snap.md b/src/cloud/project/project-webint-snap.md
index e78b408f48f..d484ad4dfb1 100644
--- a/src/cloud/project/project-webint-snap.md
+++ b/src/cloud/project/project-webint-snap.md
@@ -119,7 +119,10 @@ To restore a snapshot using the Magento CLI:
 You can create a copy of your database using the [`magento/ece-tools`]({{ site.baseurl }}/cloud/reference/cloud-composer.html#ece-tools) `db-dump` command.
 
 By default, this command creates backups for all database connections that are specified in the environment configuration. For example, if you configured your project to use split databases, the `db-dump` operation creates backups for each of the configured databases.
-If you need to create backups by selecting one or more databases, for this you need to transfer the database names as an argument to the console command
+You can also backup only selected databases by appending the database names to the command, for example:
+
+```bash
+vendor/bin/ece-tools -- main sales
 
 For help, use the command: ```php vendor/bin/ece-tools db-dump --help ```
 

From 1b14fe6bce3d2dd8038333416354e42daa1ecfc2 Mon Sep 17 00:00:00 2001
From: Yevhen Miroshnychenko <y.a.miroshnychenko@gmail.com>
Date: Tue, 3 Mar 2020 10:56:00 -0600
Subject: [PATCH 7/8] Update src/cloud/project/project-webint-snap.md

---
 src/cloud/project/project-webint-snap.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/cloud/project/project-webint-snap.md b/src/cloud/project/project-webint-snap.md
index d484ad4dfb1..27e23bced62 100644
--- a/src/cloud/project/project-webint-snap.md
+++ b/src/cloud/project/project-webint-snap.md
@@ -122,7 +122,7 @@ By default, this command creates backups for all database connections that are s
 You can also backup only selected databases by appending the database names to the command, for example:
 
 ```bash
-vendor/bin/ece-tools -- main sales
+php vendor/bin/ece-tools -- main sales
 
 For help, use the command: ```php vendor/bin/ece-tools db-dump --help ```
 

From 8fb989f5779f3569631a1034b4da1673665afd60 Mon Sep 17 00:00:00 2001
From: Yevhen Miroshnychenko <y.a.miroshnychenko@gmail.com>
Date: Tue, 3 Mar 2020 10:56:52 -0600
Subject: [PATCH 8/8] Update src/cloud/project/project-webint-snap.md

Co-Authored-By: Margaret Eker <meker@adobe.com>
---
 src/cloud/project/project-webint-snap.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/cloud/project/project-webint-snap.md b/src/cloud/project/project-webint-snap.md
index 27e23bced62..7f99c946255 100644
--- a/src/cloud/project/project-webint-snap.md
+++ b/src/cloud/project/project-webint-snap.md
@@ -164,7 +164,7 @@ To create a database dump:
  {:.bs-callout-info}
 
 -  We recommend putting the application in maintenance mode before doing a database dump in Production environments.
--  This command creates an archive file for each database backup with the file name pattern `dump-<label><timestamp>.sql.gz` where  _label_ is replaced with the database name.  The archive files are available in your local project directory.
+-  This command creates an archive file for each database backup with the file name pattern `dump-<label><timestamp>.sql.gz` where  _label_ is replaced with the database name.  The archive files are saved to your remote project directory, and the path to each file is listed in the command output.
 -  If an error occurs during the dump, the command deletes any dump files to conserve disk space. Review the logs for details (`var/log/cloud.log`).
 -  For Pro Production environments, this command dumps only from one of three high-availability nodes, so production data written to a different node during the dump may not be copied. It generates a `var/dbdump.lock` file to prevent running the command on more than one node.