From 64c05cd5a9dbcfe36930497b34e6b66b6adbedb7 Mon Sep 17 00:00:00 2001
From: Ashraf Khamis <akhamis@gitlab.com>
Date: Thu, 27 Feb 2025 11:29:04 +0000
Subject: [PATCH] Add note to direct transfer docs
---
doc/administration/get_started.md | 8 ++++++++
doc/user/project/settings/import_export.md | 7 +++++++
2 files changed, 15 insertions(+)
diff --git a/doc/administration/get_started.md b/doc/administration/get_started.md
index e8e754f57023..a08314efddd6 100644
--- a/doc/administration/get_started.md
+++ b/doc/administration/get_started.md
@@ -173,6 +173,14 @@ All backups are encrypted. After 90 days, backups are deleted.
For more information about GitLab SaaS backups, see our [Backup FAQ page](https://handbook.gitlab.com/handbook/engineering/infrastructure/faq/#gitlabcom-backups).
+{{< alert type="note" >}}
+
+You should not use [direct transfer](../user/group/import/_index.md) or
+[project export files](../user/project/settings/import_export.md) to back up your data.
+Using project export files for backups does not always work, and not all items are exported.
+
+{{< /alert >}}
+
### Alternative backup strategies
In some situations the Rake task for backups may not be the most optimal solution. Here are some
diff --git a/doc/user/project/settings/import_export.md b/doc/user/project/settings/import_export.md
index 9bdfcf91cd26..3dfb7ea4878c 100644
--- a/doc/user/project/settings/import_export.md
+++ b/doc/user/project/settings/import_export.md
@@ -15,6 +15,13 @@ title: Migrate projects and groups by using file exports
Migrating groups and projects by using [direct transfer](../../group/import/_index.md) is recommended. However, in some
situations, you might need to migrate groups and project by using file exports.
+{{< alert type="note" >}}
+
+You should not use project export files to back up your data.
+Using project export files for backups does not always work, and not all items are exported.
+
+{{< /alert >}}
+
## Known issues
- Due to a known issue, you might encounter a
--
GitLab