comparison Sphinx/source/faq/features.rst @ 998:bd7fbe3042f7

recycling/protection
author Alain Mazy <am@osimis.io>
date Mon, 18 Dec 2023 09:47:49 +0100
parents 1316bc62b5d5
children 2e103fb1fa11
comparison
equal deleted inserted replaced
997:e12cf25cc93b 998:bd7fbe3042f7
31 .. _recycling: 31 .. _recycling:
32 32
33 Recycling/Protection 33 Recycling/Protection
34 -------------------- 34 --------------------
35 35
36 Because of its focus on low-end computers, Orthanc implements **disk 36 Because of its focus on low-end computers, Orthanc may implement **disk
37 space recycling**: The patient that has been stored for the longest 37 space recycling**: The patient that has been stored for the longest
38 time inside Orthanc can be automatically deleted when the disk space 38 time inside Orthanc can be automatically deleted when the disk space
39 used by Orthanc grows above a threshold, or when the number of stored 39 used by Orthanc grows above a threshold, or when the number of stored
40 patients grows above a threshold. This feature enables the automated 40 patients grows above a threshold. This feature enables the automated
41 control of the disk space dedicated to Orthanc. Note that each time 41 control of the disk space dedicated to Orthanc. Note that each time
45 Recycling is controlled by the ``MaximumStorageSize`` and the 45 Recycling is controlled by the ``MaximumStorageSize`` and the
46 ``MaximumPatientCount`` options in the :ref:`Orthanc configuration 46 ``MaximumPatientCount`` options in the :ref:`Orthanc configuration
47 file <configuration>`. Setting both these values to 0 will disable 47 file <configuration>`. Setting both these values to 0 will disable
48 recycling. 48 recycling.
49 49
50 Starting with version 1.11.2, Orthanc also implements another **rejection**
51 behaviour when the ``MaximumStorageSize`` or ``MaximumPatientCount`` is
52 reached. In this case, patients are not recycled but Orthanc rejects new incoming
53 data. Check the ``MaximumStorageMode`` option in the :ref:`Orthanc configuration
54 file <configuration>`.
55
50 It is possible to prevent important data from being automatically 56 It is possible to prevent important data from being automatically
51 recycled. This mechanism is called **protection**. Each patient can be 57 recycled. This mechanism is called **protection**. Each patient can be
52 individually protected against recycling by using the 58 individually protected against recycling by using the
53 ``Unprotected/Protected`` switch that is available from Orthanc 59 ``Unprotected/Protected`` switch that is available from Orthanc
54 Explorer. 60 Explorer.
58 recycling. The rationale is that we think it is important to keep 64 recycling. The rationale is that we think it is important to keep
59 available all the data related to one patient. Unwillingly losing a 65 available all the data related to one patient. Unwillingly losing a
60 study/series that is part of the same patient might lead to a loss in 66 study/series that is part of the same patient might lead to a loss in
61 consistency with respect to the medical history of this patient. 67 consistency with respect to the medical history of this patient.
62 68
63 Starting with version 1.11.2, Orthanc also implements another **rejection** 69 To protect/unprotect a patient, one must call the ``/patients/../protected`` route::
64 behaviour when the ``MaximumStorageSize`` or ``MaximumPatientCount`` is 70
65 reached. In this case, patients are not recycled but Orthanc rejects new incoming 71 $ curl -X PUT http://localhost:8042/patients/0946fcb6-cf12ab43-bad958c1-bf057ad5-0fc6f54c/protected -d "1"
66 data. Check the ``MaximumStorageMode`` option in the :ref:`Orthanc configuration 72 $ curl -X PUT http://localhost:8042/patients/0946fcb6-cf12ab43-bad958c1-bf057ad5-0fc6f54c/protected -d "0"
67 file <configuration>`. 73
68 74
69 .. _compression: 75 .. _compression:
70 76
71 Compression 77 Compression
72 ----------- 78 -----------