From ebe659e618b9dd4bc7150e1c87ea94840b55dcfc Mon Sep 17 00:00:00 2001 From: Anupam Kumar Date: Fri, 6 Dec 2024 18:51:12 +0530 Subject: [PATCH] enh(Maintenance): update sync with clients after data recovery Signed-off-by: Anupam Kumar --- admin_manual/maintenance/restore.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/admin_manual/maintenance/restore.rst b/admin_manual/maintenance/restore.rst index f924e27d390..9290f146bfc 100644 --- a/admin_manual/maintenance/restore.rst +++ b/admin_manual/maintenance/restore.rst @@ -96,9 +96,15 @@ to try an recover as much data as possible. Files missing on the server are therefore recovered from the clients and in case of different content the users will be asked. +This can also help in rare scenarios when the database is newer than the data directory. +The server will restore the data from the clients and preserve the shares. +Until then the files would be visible but not accessible. +A :ref:`files:scan ` is required afterwards to update the database. + .. note:: The usage of `maintenance:data-fingerprint` can cause conflict dialogues and difficulties deleting files on the client. Therefore it's only recommended to prevent dataloss if the backup was outdated. + This command does not require the server to be in maintenance mode. If you are running multiple application servers you will need to make sure the config files are synced between them so that the updated `data-fingerprint`