# HG changeset patch # User Alain Mazy # Date 1678187633 -3600 # Node ID c10fc0838f58362ab00d3fd8aa3e5b5e2f867686 # Parent a96b0a9b96c31c883109ec29e123fd9ebdd4de6a backup diff -r a96b0a9b96c3 -r c10fc0838f58 Sphinx/source/users/backup.rst --- a/Sphinx/source/users/backup.rst Mon Feb 27 16:24:17 2023 +0100 +++ b/Sphinx/source/users/backup.rst Tue Mar 07 12:13:53 2023 +0100 @@ -25,7 +25,7 @@ 3. Restart Orthanc. -It is mandatory to stop Orthanc, as the Orthanc core makes the +It is recommended to stop Orthanc, as the Orthanc core makes the assumption that it is the only process to access the SQLite database at any time. @@ -61,3 +61,33 @@ Here are some contributed documents: * `Backup for Windows 10, Orthanc and PostgreSQL plugin `__ (in Japanese, 2020-02-02). + + +Restoring backups +----------------- + +You should always stop Orthanc while you restore the DB backup. +You may run Orthanc while the storage (DICOM file) backup is being restored +but you should expect to have some data unavailable. + +Data consistency +^^^^^^^^^^^^^^^^ + +If you are running backups on a running system, it is very likely that +your DB backup won't happen exactly at the same time as your storage backup +(the DICOM files). + +After you've restored your backup, you'll likely need +to resend e.g. the last 24 hours data from the modalities to make sure +the data that was not included in the backup is pushed to Orthanc again. +When new data is pushed to Orthanc, it is recommended to have the +``OverwriteInstances`` set to ``true`` to force Orthanc rewrite files for +instances that were in the DB backup and not on the storage backup. + +This kind of recovery might create orphan files in the DICOM storage +(files that are not referenced by Orthanc anymore). As of 2023, there +is no script/procedure available to delete these orphan files. + + + +