From f46b793aaf0d32e73836a6a99d962624340e820e Mon Sep 17 00:00:00 2001 From: Jesper Madsen <32263802+jesp209i@users.noreply.github.com> Date: Fri, 27 Jun 2025 08:25:20 +0200 Subject: [PATCH 1/2] Add one more limitation to database backups --- umbraco-cloud/databases/backups.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/umbraco-cloud/databases/backups.md b/umbraco-cloud/databases/backups.md index baa9f85298a..6393d53a5a6 100644 --- a/umbraco-cloud/databases/backups.md +++ b/umbraco-cloud/databases/backups.md @@ -17,6 +17,8 @@ When restoring a database backup on Umbraco Cloud, certain elements may cause is - **SQL Server logins** - Custom SQL Server logins (for example, admin, sysuser, etc.) may conflict with existing logins when restoring the database in the hosting platform. - **Complex Database Objects** - Custom complex database objects in SQL is an element with external dependencies or special server configurations, which may result in conflicts when restoring the database in our hosting platform. +Also note: Restoring a database will switch the existing database with a fresh one with the restored content. Because the initial database is removed you will not be able to create database backups with a timestamp that lies before the restore. Any existing backups are still available though. + ## Backup on Umbraco Cloud On Umbraco Cloud, you can utilize our 35-day point-in-time recovery to create and download a `bacpac` file from your project. From b74a33a06061e7362c2473504445a5ca3d6d9bca Mon Sep 17 00:00:00 2001 From: Jesper Madsen <32263802+jesp209i@users.noreply.github.com> Date: Fri, 27 Jun 2025 09:34:01 +0200 Subject: [PATCH 2/2] Update backups.md --- umbraco-cloud/databases/backups.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/umbraco-cloud/databases/backups.md b/umbraco-cloud/databases/backups.md index 6393d53a5a6..4c04fd779cd 100644 --- a/umbraco-cloud/databases/backups.md +++ b/umbraco-cloud/databases/backups.md @@ -17,7 +17,9 @@ When restoring a database backup on Umbraco Cloud, certain elements may cause is - **SQL Server logins** - Custom SQL Server logins (for example, admin, sysuser, etc.) may conflict with existing logins when restoring the database in the hosting platform. - **Complex Database Objects** - Custom complex database objects in SQL is an element with external dependencies or special server configurations, which may result in conflicts when restoring the database in our hosting platform. -Also note: Restoring a database will switch the existing database with a fresh one with the restored content. Because the initial database is removed you will not be able to create database backups with a timestamp that lies before the restore. Any existing backups are still available though. +{% hint style="info" %} +Restoring a database replaces the existing database with a fresh one containing the restored content. Once a Restore has run, you cannot create database backups with a **Date and Time for snapshot (UTC)** earlier than the time of the Restore-operation. However, any existing backups are still available. +{% endhint %} ## Backup on Umbraco Cloud