Merge pull request #197415 from realAngryAnalytics/20220504-bcdrcleanup

20220506 0104 perform some cleanup to update docs

Author: PMEds28

articles/synapse-analytics/backuprestore/restore-sql-pool.md

@@ -140,7 +140,7 @@ Steps:
 
 9. Verify that the restored dedicated SQL pool (formerly SQL DW) is online.
 
-10. If the desired destination is a Synapse Workspace, uncomment the code to perform the additional restore step.
+10. **If the desired destination is a Synapse Workspace, uncomment the code to perform the additional restore step.**
     1. Create a restore point for the newly created data warehouse.
     2. Retrieve the last restore point created by using the "Select -Last 1" syntax.
     3. Perform the restore to the desired Synapse workspace.
@@ -164,12 +164,12 @@ Get-AzSubscription
 Select-AzSubscription -SubscriptionName $SourceSubscriptionName
 
 # list all restore points
-Get-AzSynapseSqlPoolRestorePoint -ResourceGroupName $ResourceGroupName -WorkspaceName $WorkspaceName -Name $SQLPoolName
+Get-AzSynapseSqlPoolRestorePoint -ResourceGroupName $SourceResourceGroupName -WorkspaceName $SourceWorkspaceName -Name $SourceSQLPoolName
 # Pick desired restore point using RestorePointCreationDate "xx/xx/xxxx xx:xx:xx xx"
 $PointInTime="<RestorePointCreationDate>"
 
 # Get the specific SQL pool to restore
-$SQLPool = Get-AzSynapseSqlPool -ResourceGroupName $ResourceGroupName -WorkspaceName $WorkspaceName -Name $SQLPoolName
+$SQLPool = Get-AzSynapseSqlPool -ResourceGroupName $SourceResourceGroupName -WorkspaceName $SourceWorkspaceName -Name $SourceSQLPoolName
 # Transform Synapse SQL pool resource ID to SQL database ID because currently the restore command only accepts the SQL database ID format.
 $DatabaseID = $SQLPool.Id -replace "Microsoft.Synapse", "Microsoft.Sql" `
 	-replace "workspaces", "servers" `
@@ -180,7 +180,7 @@ Select-AzSubscription -SubscriptionName $TargetSubscriptionName
 
 # Restore database from a desired restore point of the source database to the target server in the desired subscription
 $RestoredDatabase = Restore-AzSqlDatabase –FromPointInTimeBackup –PointInTime $PointInTime -ResourceGroupName $TargetResourceGroupName `
-    -ServerName $TargetServerName -TargetDatabaseName $TargetDatabaseName –ResourceId $Database.ID
+    -ServerName $TargetServerName -TargetDatabaseName $TargetDatabaseName –ResourceId $DatabaseID
 
 # Verify the status of restored database
 $RestoredDatabase.status
@@ -198,7 +198,11 @@ $RestoredDatabase.status
 
 ```
 
-
+## Troubleshooting
+A restore operation can result in a deployment failure based on a "RequestTimeout" exception. 
+![Screenshot from resource group deployments dialog of a timeout exception.](../media/sql-pools/restore-sql-pool-troubleshooting-01.png)  
+This timeout can be ignored. Review the dedicated SQL pool blade in the portal and it may still have status of "Restoring" and eventually will transition to "Online". 
+![Screenshot of SQL pool dialog with the status that shows restoring.](../media/sql-pools/restore-sql-pool-troubleshooting-02.png)  
 
 ## Next Steps
 

articles/synapse-analytics/media/sql-pools/restore-sql-pool-troubleshooting-01.png

@@ -1,14 +1,14 @@
 ---
 title: Backup and restore - snapshots, geo-redundant 
 description: Learn how backup and restore works in Azure Synapse Analytics dedicated SQL pool. Use backups to restore your data warehouse to a restore point in the primary region. Use geo-redundant backups to restore to a different geographical region.
-author: joannapea
-manager: craigg
+author: realAngryAnalytics
+manager: joannapea
 ms.service: synapse-analytics
 ms.topic: conceptual
 ms.subservice: sql-dw 
-ms.date: 11/13/2020
-ms.author: joanpo
-ms.reviewer: igorstan
+ms.date: 05/04/2022
+ms.author: stevehow
+ms.reviewer: joanpo
 ms.custom: seo-lt-2019"
 ---
 
@@ -58,9 +58,6 @@ The following lists details for restore point retention periods:
 
 When you drop a dedicated SQL pool, a final snapshot is created and saved for seven days. You can restore the dedicated SQL pool to the final restore point created at deletion. If the dedicated SQL pool is dropped in a paused state, no snapshot is taken. In that scenario, make sure to create a user-defined restore point before dropping the dedicated SQL pool.
 
-> [!IMPORTANT]
-> If you delete the server/workspace hosting a dedicated SQL pool, all databases that belong to the server/workspace are also deleted and cannot be recovered. You cannot restore a deleted server.
-
 ## Geo-backups and disaster recovery
 
 A geo-backup is created once per day to a [paired data center](../../availability-zones/cross-region-replication-azure.md?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json). The RPO for a geo-restore is 24 hours. You can restore the geo-backup to a server in any other region where dedicated SQL pool is supported. A geo-backup ensures you can restore data warehouse in case you cannot access the restore points in your primary region.
@@ -94,11 +91,11 @@ You can either keep the restored data warehouse and the current one, or delete o
 
 To restore a data warehouse, see [Restore a dedicated SQL pool](sql-data-warehouse-restore-points.md#create-user-defined-restore-points-through-the-azure-portal).
 
-To restore a deleted or paused data warehouse, you can [create a support ticket](sql-data-warehouse-get-started-create-support-ticket.md).
+To restore a deleted data warehouse, see [Restore a deleted database](sql-data-warehouse-restore-deleted-dw.md), or if the entire server was deleted, see [Restore a data warehouse from a deleted server](sql-data-warehouse-restore-from-deleted-server.md).
 
 ## Cross subscription restore
 
-If you need to directly restore across subscription, vote for this capability [here](https://feedback.azure.com/d365community/idea/dea9ea22-0a25-ec11-b6e6-000d3a4f07b8). Restore to a different server and ['Move'](../../azure-resource-manager/management/move-resource-group-and-subscription.md?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json) the server across subscriptions to perform a cross subscription restore.
+You can perform a cross-subscription restore by follow the guidance [here](sql-data-warehouse-restore-active-paused-dw.md#restore-an-existing-dedicated-sql-pool-formerly-sql-dw-to-a-different-subscription-through-powershell).
 
 ## Geo-redundant restore
 
@@ -107,6 +104,10 @@ You can [restore your dedicated SQL pool](sql-data-warehouse-restore-from-geo-ba
 > [!NOTE]
 > To perform a geo-redundant restore you must not have opted out of this feature.
 
+## Support Process
+
+You can [submit a support ticket](sql-data-warehouse-get-started-create-support-ticket.md) through the Azure portal for Azure Synapse Analytics.
+
 ## Next steps
 
 For more information about restore points, see [User-defined restore points](sql-data-warehouse-restore-points.md)

articles/synapse-analytics/media/sql-pools/restore-sql-pool-troubleshooting-02.png

@@ -41,7 +41,7 @@ In this article, you learn how to restore a dedicated SQL pool (formerly SQL DW)
 ```powershell
 $SubscriptionID="<YourSubscriptionID>"
 $ResourceGroupName="<YourResourceGroupName>"
-$ServereName="<YourServerNameWithoutURLSuffixSeeNote>"  # Without database.windows.net
+$ServerName="<YourServerNameWithoutURLSuffixSeeNote>"  # Without database.windows.net
 $DatabaseName="<YourDatabaseName>"
 $TargetServerName="<YourtargetServerNameWithoutURLSuffixSeeNote>"  
 $TargetDatabaseName="<YourDatabaseName>"