Update restore how-tos with conditions

Author: rachel-msft

articles/mariadb/howto-restore-server-cli.md

@@ -1,17 +1,15 @@
 ---
 title: How to backup and restore a server in Azure Database for MariaDB
 description: Learn how to backup and restore a server in Azure Database for MariaDB by using the Azure CLI.
-author: rachel-msft
-ms.author: raagyema
+author: ajlam
+ms.author: andrela
 ms.service: mariadb
 ms.devlang: azurecli
 ms.topic: conceptual
-ms.date: 11/10/2018
+ms.date: 10/25/2019
 ---
 # How to back up and restore a server in Azure Database for MariaDB using the Azure CLI
 
-## Backup happens automatically
-
 Azure Database for MariaDB servers are backed up periodically to enable Restore features. Using this feature you may restore the server and all its databases to an earlier point-in-time, on a new server.
 
 ## Prerequisites
@@ -72,11 +70,13 @@ The `az mariadb server restore` command requires the following parameters:
 | restore-point-in-time | 2018-03-13T13:59:00Z | Select a point in time to restore to. This date and time must be within the source server's backup retention period. Use the ISO8601 date and time format. For example, you can use your own local time zone, such as `2018-03-13T05:59:00-08:00`. You can also use the UTC Zulu format, for example, `2018-03-13T13:59:00Z`. |
 | source-server | mydemoserver | The name or ID of the source server to restore from. |
 
-When you restore a server to an earlier point in time, a new server is created. The original server and its databases from the specified point in time are copied to the new server.
+WWhen you restore a server to an earlier point in time, a new server is created. The original server and its databases from the specified point in time are copied to the new server.
+
+The location and pricing tier values for the restored server remain the same as the original server. 
 
-The location and pricing tier values for the restored server remain the same as the original server.
+After the restore process finishes, locate the new server and verify that the data is restored as expected. The new server has the same server admin login name and password that was valid for the existing server at the time the restore was initiated. The password can be changed from the new server's **Overview** page.
 
-After the restore process finishes, locate the new server and verify that the data is restored as expected.
+The new server created during a restore does not have the firewall rules or VNet service endpoints that existed on the original server. These rules need to be set up separately for this new server.
 
 ## Geo restore
 
@@ -113,12 +113,14 @@ The `az mariadb server georestore` command requires the following parameters:
 |location | eastus | The location of the new server. |
 |sku-name| GP_Gen5_8 | This parameter sets the pricing tier, compute generation, and number of vCores of the new server. GP_Gen5_8 maps to a General Purpose, Gen 5 server with 8 vCores.|
 
->[!Important]
->When creating a new server by a geo restore, it inherits the same storage size and pricing tier as the source server. These values cannot be changed during creation. After the new server is created, its storage size can be scaled up.
+When creating a new server by a geo restore, it inherits the same storage size and pricing tier as the source server. These values cannot be changed during creation. After the new server is created, its storage size can be scaled up.
+
+After the restore process finishes, locate the new server and verify that the data is restored as expected. The new server has the same server admin login name and password that was valid for the existing server at the time the restore was initiated. The password can be changed from the new server's **Overview** page.
 
-After the restore process finishes, locate the new server and verify that the data is restored as expected.
+The new server created during a restore does not have the firewall rules or VNet service endpoints that existed on the original server. These rules need to be set up separately for this new server.
 
 ## Next steps
 
-- Learn more about the service's [backups](concepts-backup.md).
-- Learn more about [business continuity](concepts-business-continuity.md) options.
+- Learn more about the service's [backups](concepts-backup.md)
+- Learn about [replicas](concepts-read-replicas.md)
+- Learn more about [business continuity](concepts-business-continuity.md) options

articles/mariadb/howto-restore-server-portal.md

@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mariadb
 ms.topic: conceptual
-ms.date: 04/15/2019
+ms.date: 10/25/2019
 ---
 
 # How to backup and restore a server in Azure Database for MariaDB using the Azure portal
@@ -68,10 +68,13 @@ The following steps restore the sample server to a point-in-time:
 
 5. Once the restore finishes, locate the new server that is created to verify the data was restored as expected.
 
->[!Note]
->Note the new server created by point-in-time restore has the same server admin login name and password that was valid for the existing server at the point-in-time chose. You can change the password from the new server's **Overview** page.
+
+The new server created by point-in-time restore has the same server admin login name and password that was valid for the existing server at the point-in-time chose. You can change the password from the new server's **Overview** page.
+
+The new server created during a restore does not have the firewall rules or VNet service endpoints that existed on the original server. These rules need to be set up separately for this new server.
 
 ## Geo restore
+
 If you configured your server for geographically redundant backups, a new server can be created from the backup of that existing server. This new server can be created in any region that Azure Database for MariaDB is available.  
 
 1. Select **Databases** > **Azure Database for MariaDB**. You can also type **MariaDB** in the search box to find the service.
@@ -87,9 +90,12 @@ If you configured your server for geographically redundant backups, a new server
 
 3. Fill out the rest of the form with your preferences. You can select any **Location**. After selecting the location, you can select **Pricing Tier**. By default the parameters for the existing server you are restoring from are displayed. You can click **OK** without making any changes to inherit those settings. Or you can change **Compute Generation** (if available in the region you have chosen), number of **vCores**, **Backup Retention Period**, and **Backup Redundancy Option**. Changing **Pricing Tier** (Basic, General Purpose, or Memory Optimized) or **Storage** size during restore is not supported.
 
->[!Note]
->The new server created by geo restore has the same server admin login name and password that was valid for the existing server at the time the restore was initiated. The password can be changed from the new server's **Overview** page.
+The new server created by geo restore has the same server admin login name and password that was valid for the existing server at the time the restore was initiated. The password can be changed from the new server's **Overview** page.
+
+The new server created during a restore does not have the firewall rules or VNet service endpoints that existed on the original server. These rules need to be set up separately for this new server.
+
 
 ## Next steps
-- Learn more about the service's [backups](concepts-backup.md).
-- Learn more about [business continuity](concepts-business-continuity.md) options.
+- Learn more about the service's [backups](concepts-backup.md)
+- Learn about [replicas](concepts-read-replicas.md)
+- Learn more about [business continuity](concepts-business-continuity.md) options

articles/mysql/howto-restore-server-cli.md

@@ -1,16 +1,15 @@
 ---
 title: How to backup and restore a server in Azure Database for MySQL
 description: Learn how to backup and restore a server in Azure Database for MySQL by using the Azure CLI.
-author: rachel-msft
-ms.author: raagyema
+author: ajlam
+ms.author: andrela
 ms.service: mysql
 ms.devlang: azurecli
 ms.topic: conceptual
-ms.date: 04/01/2018
+ms.date: 10/25/2019
 ---
 # How to back up and restore a server in Azure Database for MySQL using the Azure CLI
 
-## Backup happens automatically
 Azure Database for MySQL servers are backed up periodically to enable Restore features. Using this feature you may restore the server and all its databases to an earlier point-in-time, on a new server.
 
 ## Prerequisites
@@ -74,7 +73,9 @@ When you restore a server to an earlier point in time, a new server is created.
 
 The location and pricing tier values for the restored server remain the same as the original server. 
 
-After the restore process finishes, locate the new server and verify that the data is restored as expected.
+After the restore process finishes, locate the new server and verify that the data is restored as expected. The new server has the same server admin login name and password that was valid for the existing server at the time the restore was initiated. The password can be changed from the new server's **Overview** page.
+
+The new server created during a restore does not have the firewall rules or VNet service endpoints that existed on the original server. These rules need to be set up separately for this new server.
 
 ## Geo restore
 If you configured your server for geographically redundant backups, a new server can be created from the backup of that existing server. This new server can be created in any region that Azure Database for MySQL is available.  
@@ -109,12 +110,13 @@ The `az mysql server georestore` command requires the following parameters:
 |location | eastus | The location of the new server. |
 |sku-name| GP_Gen5_8 | This parameter sets the pricing tier, compute generation, and number of vCores of the new server. GP_Gen5_8 maps to a General Purpose, Gen 5 server with 8 vCores.|
 
+When creating a new server by a geo restore, it inherits the same storage size and pricing tier as the source server. These values cannot be changed during creation. After the new server is created, its storage size can be scaled up.
 
->[!Important]
->When creating a new server by a geo restore, it inherits the same storage size and pricing tier as the source server. These values cannot be changed during creation. After the new server is created, its storage size can be scaled up.
+After the restore process finishes, locate the new server and verify that the data is restored as expected. The new server has the same server admin login name and password that was valid for the existing server at the time the restore was initiated. The password can be changed from the new server's **Overview** page.
 
-After the restore process finishes, locate the new server and verify that the data is restored as expected.
+The new server created during a restore does not have the firewall rules or VNet service endpoints that existed on the original server. These rules need to be set up separately for this new server.
 
 ## Next steps
-- Learn more about the service's [backups](concepts-backup.md).
-- Learn more about [business continuity](concepts-business-continuity.md) options.
+- Learn more about the service's [backups](concepts-backup.md)
+- Learn about [replicas](concepts-read-replicas.md)
+- Learn more about [business continuity](concepts-business-continuity.md) options

articles/mysql/howto-restore-server-portal.md

@@ -5,7 +5,7 @@ author: ajlam
 ms.author: andrela
 ms.service: mysql
 ms.topic: conceptual
-ms.date: 04/01/2018
+ms.date: 10/25/2019
 ---
 
 # How to backup and restore a server in Azure Database for MySQL using the Azure portal
@@ -66,8 +66,9 @@ The following steps restore the sample server to a point-in-time:
 
 5. Once the restore finishes, locate the new server that is created to verify the data was restored as expected.
 
->[!Note]
->Note the new server created by point-in-time restore has the same server admin login name and password that was valid for the existing server at the point-in-time chose. You can change the password from the new server's **Overview** page.
+The new server created by point-in-time restore has the same server admin login name and password that was valid for the existing server at the point-in-time chose. You can change the password from the new server's **Overview** page.
+
+The new server created during a restore does not have the firewall rules or VNet service endpoints that existed on the original server. These rules need to be set up separately for this new server.
 
 ## Geo restore
 If you configured your server for geographically redundant backups, a new server can be created from the backup of that existing server. This new server can be created in any region that Azure Database for MySQL is available.  
@@ -85,10 +86,13 @@ If you configured your server for geographically redundant backups, a new server
 
 3. Fill out the rest of the form with your preferences. You can select any **Location**. After selecting the location, you can select **Pricing Tier**. By default the parameters for the existing server you are restoring from are displayed. You can click **OK** without making any changes to inherit those settings. Or you can change **Compute Generation** (if available in the region you have chosen), number of **vCores**, **Backup Retention Period**, and **Backup Redundancy Option**. Changing **Pricing Tier** (Basic, General Purpose, or Memory Optimized) or **Storage** size during restore is not supported.
 
->[!Note]
->The new server created by geo restore has the same server admin login name and password that was valid for the existing server at the time the restore was initiated. The password can be changed from the new server's **Overview** page.
+The new server created by geo restore has the same server admin login name and password that was valid for the existing server at the time the restore was initiated. The password can be changed from the new server's **Overview** page.
+
+The new server created during a restore does not have the firewall rules or VNet service endpoints that existed on the original server. These rules need to be set up separately for this new server.
+
 
 
 ## Next steps
-- Learn more about the service's [backups](concepts-backup.md).
-- Learn more about [business continuity](concepts-business-continuity.md) options.
+- Learn more about the service's [backups](concepts-backup.md)
+- Learn about [replicas](concepts-read-replicas.md)
+- Learn more about [business continuity](concepts-business-continuity.md) options

articles/postgresql/howto-restore-server-cli.md

@@ -6,12 +6,11 @@ ms.author: raagyema
 ms.service: postgresql
 ms.devlang: azurecli
 ms.topic: conceptual
-ms.date: 05/06/2019
+ms.date: 10/25/2019
 ---
 
 # How to back up and restore a server in Azure Database for PostgreSQL - Single Server using the Azure CLI
 
-## Backup happens automatically
 Azure Database for PostgreSQL servers are backed up periodically to enable Restore features. Using this feature you may restore the server and all its databases to an earlier point-in-time, on a new server.
 
 ## Prerequisites
@@ -75,9 +74,9 @@ When you restore a server to an earlier point in time, a new server is created.
 
 The location and pricing tier values for the restored server remain the same as the original server. 
 
-After the restore process finishes, locate the new server and verify that the data is restored as expected.
+After the restore process finishes, locate the new server and verify that the data is restored as expected. The new server has the same server admin login name and password that was valid for the existing server at the time the restore was initiated. The password can be changed from the new server's **Overview** page.
 
-The new server created during a restore does not have the firewall rules that existed on the original server. Firewall rules need to be set up separately for this new server.
+The new server created during a restore does not have the firewall rules or VNet service endpoints that existed on the original server. These rules need to be set up separately for this new server.
 
 ## Geo restore
 If you configured your server for geographically redundant backups, a new server can be created from the backup of that existing server. This new server can be created in any region that Azure Database for PostgreSQL is available.  
@@ -112,14 +111,13 @@ The `az postgres server georestore` command requires the following parameters:
 |location | eastus | The location of the new server. |
 |sku-name| GP_Gen4_8 | This parameter sets the pricing tier, compute generation, and number of vCores of the new server. GP_Gen4_8 maps to a General Purpose, Gen 4 server with 8 vCores.|
 
+When creating a new server by a geo restore, it inherits the same storage size and pricing tier as the source server. These values cannot be changed during creation. After the new server is created, its storage size can be scaled up.
 
->[!Important]
->When creating a new server by a geo restore, it inherits the same storage size and pricing tier as the source server. These values cannot be changed during creation. After the new server is created, its storage size can be scaled up.
+After the restore process finishes, locate the new server and verify that the data is restored as expected. The new server has the same server admin login name and password that was valid for the existing server at the time the restore was initiated. The password can be changed from the new server's **Overview** page.
 
-After the restore process finishes, locate the new server and verify that the data is restored as expected.
-
-The new server created during a restore does not have the firewall rules that existed on the original server. Firewall rules need to be set up separately for this new server.
+The new server created during a restore does not have the firewall rules or VNet service endpoints that existed on the original server. These rules need to be set up separately for this new server.
 
 ## Next steps
-- Learn more about the service's [backups](concepts-backup.md).
-- Learn more about [business continuity](concepts-business-continuity.md) options.
+- Learn more about the service's [backups](concepts-backup.md)
+- Learn about [replicas](concepts-read-replicas.md)
+- Learn more about [business continuity](concepts-business-continuity.md) options