Skip to content

Commit 9204402

Browse files
authored
Merge pull request #114562 from HamzaAqel/BCDR1
BCDR1
2 parents 6e8277e + 5d71d61 commit 9204402

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

articles/postgresql/flexible-server/concepts-backup-restore.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -110,9 +110,7 @@ For latest and custom restore point options, the estimated time to recover depen
110110
If you've configured your server within a virtual network, you can restore to the same virtual network or to a different virtual network. However, you can't restore to public access. Similarly, if you configured your server with public access, you can't restore to private virtual network access.
111111

112112
> [!IMPORTANT]
113-
> A user can't restore deleted servers. If you delete a server, all databases that belong to the server are also deleted and can't be recovered. To help protect server resources from accidental deletion or unexpected changes after deployment, administrators can use [management locks](../../azure-resource-manager/management/lock-resources.md).
114-
>
115-
>If you accidentally deleted your server, please reach out to support. In some cases, your server might be restored with or without data loss.
113+
> Deleted servers can be restored. If you delete the server, you can follow our guidance [Restore a dropped Azure Database for PostgreSQL Flexible server](how-to-restore-dropped-server.md) to recover. Use Azure resource lock to help prevent accidental deletion of your server.
116114
117115

118116
## Geo-redundant backup and restore

0 commit comments

Comments
 (0)