Mercurial > hg > orthanc-book
comparison Sphinx/source/users/backup.rst @ 358:011b01ccf52d
fixing external hyperlinks
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Mon, 30 Mar 2020 18:47:35 +0200 |
parents | e3751a4caa2f |
children | c10fc0838f58 |
comparison
equal
deleted
inserted
replaced
357:6b432ce3a56e | 358:011b01ccf52d |
---|---|
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>`__ |
34 for the official Debian package of Orthanc that automates this backup | 34 for the official Debian package of Orthanc that automates this backup |
35 procedure. Note that in this script, the call to the SQLite | 35 procedure. Note that in this script, the call to the SQLite |
36 command-line tool is used to force the `WAL replay | 36 command-line tool is used to force the `WAL replay |
37 <http://www.sqlite.org/wal.html>`__. This manual replay should not be | 37 <https://www.sqlite.org/wal.html>`__. This manual replay should not be |
38 necessary for Orthanc >= 0.7.3. | 38 necessary for Orthanc >= 0.7.3. |
39 | 39 |
40 | 40 |
41 PostgreSQL and MySQL | 41 PostgreSQL and MySQL |
42 -------------------- | 42 -------------------- |
43 | 43 |
44 The default SQLite engine is well adapted for DICOM routing or for | 44 The default SQLite engine is well adapted for DICOM routing or for |
45 image buffering tasks, but not for enterprise scenarios. In such | 45 image buffering tasks, but not for enterprise scenarios. In such |
46 cases, you are highly recommended to use the `PostgreSQL back-end | 46 cases, you are highly recommended to use the `PostgreSQL back-end |
47 <http://www.orthanc-server.com/static.php?page=postgresql>`__ or the | 47 <https://www.orthanc-server.com/static.php?page=postgresql>`__ or the |
48 `MySQL/MariaDB back-end | 48 `MySQL/MariaDB back-end |
49 <http://www.orthanc-server.com/static.php?page=mysql>`__. | 49 <https://www.orthanc-server.com/static.php?page=mysql>`__. |
50 | 50 |
51 If using PostgreSQL, you can do hot backups (i.e. while Orthanc is | 51 If using PostgreSQL, you can do hot backups (i.e. while Orthanc is |
52 running), and you benefit from all the flexibility of PostgreSQL | 52 running), and you benefit from all the flexibility of PostgreSQL |
53 backup. These procedures are out of the scope of this manual. Please | 53 backup. These procedures are out of the scope of this manual. Please |
54 check the `official backup and restore manual | 54 check the `official backup and restore manual |
55 <https://www.postgresql.org/docs/devel/static/backup.html>`__. | 55 <https://www.postgresql.org/docs/devel/backup.html>`__. |
56 | 56 |
57 Similar backup procedures are available for MySQL and MariaDB as | 57 Similar backup procedures are available for MySQL and MariaDB as |
58 well. Please check the official manual about `database backup methods | 58 well. Please check the official manual about `database backup methods |
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 |