Skip to content

Commit 1ffb298

Browse files
authored
Update backup-and-restore.md
Modify the main section about the restore to clarify the details about the RTO. In the current document, the ROT details are not visible.
1 parent 2fbd4bb commit 1ffb298

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/synapse-analytics/sql-data-warehouse/backup-and-restore.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,11 @@ Learn how to use backup and restore in Azure Synapse Dedicated SQL pool. Use ded
2020

2121
A *data warehouse snapshot* creates a restore point you can leverage to recover or copy your data warehouse to a previous state. Since dedicated SQL pool is a distributed system, a data warehouse snapshot consists of many files that are located in Azure storage. Snapshots capture incremental changes from the data stored in your data warehouse.
2222

23-
A *data warehouse restore* is a new data warehouse that is created from a restore point of an existing or deleted data warehouse. Restoring your data warehouse is an essential part of any business continuity and disaster recovery strategy because it re-creates your data after accidental corruption or deletion. Data warehouse snapshot is also a powerful mechanism to create copies of your data warehouse for test or development purposes. Dedicated SQL pool restore rates can vary depending on the database size and location of the source and target data warehouse.
23+
A *data warehouse restore* is a new data warehouse that is created from a restore point of an existing or deleted data warehouse. Restoring your data warehouse is an essential part of any business continuity and disaster recovery strategy because it re-creates your data after accidental corruption or deletion. Data warehouse snapshot is also a powerful mechanism to create copies of your data warehouse for test or development purposes.
24+
25+
> [!NOTE]Dedicated SQL pool Recovery Time Objective (RTO) rates can vary. Factors that may affect the recovery (Restore) time:
26+
> - The database size.
27+
> - The location of the source and target data warehouse (i.e., geo-restore).
2428
2529
## Automatic Restore Points
2630

0 commit comments

Comments
 (0)