Skip to content

Commit ec64a14

Browse files
authored
Update concepts-business-continuity.md
1 parent 5dc784a commit ec64a14

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/mariadb/concepts-business-continuity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ You can use the service's backups to recover a server from various disruptive ev
4040
You can perform a point-in-time-restore to create a copy of your server to a known good point in time. This point in time must be within the backup retention period you have configured for your server. After the data is restored to the new server, you can either replace the original server with the newly restored server or copy the needed data from the restored server into the original server.
4141

4242
> [!IMPORTANT]
43-
> Deleted servers can be restored only within **five days** of deletion after which the backups are deleted. The database backup can be accessed and restored only from the Azure subscription hosting the server. To restore a dropped server, refer [documented steps](howto-restore-dropped-server.md). To protect server resources, post deployment, from accidental deletion or unexpected changes, administrators can leverage [management locks](../azure-resource-manager/management/lock-resources.md).
43+
> Deleted servers cannot be restored. To protect server resources, post deployment, from accidental deletion or unexpected changes, administrators can leverage [management locks](../azure-resource-manager/management/lock-resources.md).
4444
4545
## Recover from an Azure regional data center outage
4646

0 commit comments

Comments
 (0)