Mercurial > hg > orthanc-book
comparison Sphinx/source/users/backup.rst @ 918:c10fc0838f58
backup
author | Alain Mazy <am@osimis.io> |
---|---|
date | Tue, 07 Mar 2023 12:13:53 +0100 |
parents | 011b01ccf52d |
children |
comparison
equal
deleted
inserted
replaced
917:a96b0a9b96c3 | 918:c10fc0838f58 |
---|---|
23 * The SQLite index (by default, the ``OrthancStorage/index*`` files | 23 * The SQLite index (by default, the ``OrthancStorage/index*`` files |
24 next to the configuration file). | 24 next to the configuration file). |
25 | 25 |
26 3. Restart Orthanc. | 26 3. Restart Orthanc. |
27 | 27 |
28 It is mandatory to stop Orthanc, as the Orthanc core makes the | 28 It is recommended to stop Orthanc, as the Orthanc core makes the |
29 assumption that it is the only process to access the SQLite database | 29 assumption that it is the only process to access the SQLite database |
30 at any time. | 30 at any time. |
31 | 31 |
32 Karsten Hilbert provided us with a `sample backup script | 32 Karsten Hilbert provided us with a `sample backup script |
33 <https://github.com/jodogne/OrthancContributed/blob/master/Scripts/Backup/2014-01-31-KarstenHilbert.sh>`__ | 33 <https://github.com/jodogne/OrthancContributed/blob/master/Scripts/Backup/2014-01-31-KarstenHilbert.sh>`__ |
59 <https://dev.mysql.com/doc/refman/8.0/en/backup-methods.html>`__. | 59 <https://dev.mysql.com/doc/refman/8.0/en/backup-methods.html>`__. |
60 | 60 |
61 Here are some contributed documents: | 61 Here are some contributed documents: |
62 | 62 |
63 * `Backup for Windows 10, Orthanc and PostgreSQL plugin <https://blog.goo.ne.jp/wakida_ortho/e/3eb557fd134cf6136d5ba66cf72fd85a>`__ (in Japanese, 2020-02-02). | 63 * `Backup for Windows 10, Orthanc and PostgreSQL plugin <https://blog.goo.ne.jp/wakida_ortho/e/3eb557fd134cf6136d5ba66cf72fd85a>`__ (in Japanese, 2020-02-02). |
64 | |
65 | |
66 Restoring backups | |
67 ----------------- | |
68 | |
69 You should always stop Orthanc while you restore the DB backup. | |
70 You may run Orthanc while the storage (DICOM file) backup is being restored | |
71 but you should expect to have some data unavailable. | |
72 | |
73 Data consistency | |
74 ^^^^^^^^^^^^^^^^ | |
75 | |
76 If you are running backups on a running system, it is very likely that | |
77 your DB backup won't happen exactly at the same time as your storage backup | |
78 (the DICOM files). | |
79 | |
80 After you've restored your backup, you'll likely need | |
81 to resend e.g. the last 24 hours data from the modalities to make sure | |
82 the data that was not included in the backup is pushed to Orthanc again. | |
83 When new data is pushed to Orthanc, it is recommended to have the | |
84 ``OverwriteInstances`` set to ``true`` to force Orthanc rewrite files for | |
85 instances that were in the DB backup and not on the storage backup. | |
86 | |
87 This kind of recovery might create orphan files in the DICOM storage | |
88 (files that are not referenced by Orthanc anymore). As of 2023, there | |
89 is no script/procedure available to delete these orphan files. | |
90 | |
91 | |
92 | |
93 |