]>
Commit | Line | Data |
---|---|---|
ec1ae7e6 | 1 | .. _terms: |
1531185d | 2 | |
04e24b14 DW |
3 | Terminology |
4 | =========== | |
5 | ||
6 | Backup Content | |
7 | -------------- | |
8 | ||
9 | When doing deduplication, there are different strategies to get | |
10 | optimal results in terms of performance and/or deduplication rates. | |
11 | Depending on the type of data, it can be split into *fixed* or *variable* | |
12 | sized chunks. | |
13 | ||
14 | Fixed sized chunking requires minimal CPU power, and is used to | |
15 | backup virtual machine images. | |
16 | ||
17 | Variable sized chunking needs more CPU power, but is essential to get | |
18 | good deduplication rates for file archives. | |
19 | ||
20 | The Proxmox Backup Server supports both strategies. | |
21 | ||
22 | ||
23 | Image Archives: ``<name>.img`` | |
24 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
25 | ||
26 | This is used for virtual machine images and other large binary | |
27 | data. Content is split into fixed-sized chunks. | |
28 | ||
29 | ||
30 | File Archives: ``<name>.pxar`` | |
31 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
32 | ||
33 | .. see https://moinakg.wordpress.com/2013/06/22/high-performance-content-defined-chunking/ | |
34 | ||
35 | A file archive stores a full directory tree. Content is stored using | |
36 | the :ref:`pxar-format`, split into variable-sized chunks. The format | |
37 | is optimized to achieve good deduplication rates. | |
38 | ||
39 | ||
40 | Binary Data (BLOBs) | |
41 | ~~~~~~~~~~~~~~~~~~~ | |
42 | ||
43 | This type is used to store smaller (< 16MB) binary data such as | |
717ce406 | 44 | configuration files. Larger files should be stored as image archives. |
04e24b14 DW |
45 | |
46 | .. caution:: Please do not store all files as BLOBs. Instead, use the | |
717ce406 | 47 | file archive to store entire directory trees. |
04e24b14 DW |
48 | |
49 | ||
50 | Catalog File: ``catalog.pcat1`` | |
51 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
52 | ||
53 | The catalog file is an index for file archives. It contains | |
717ce406 | 54 | the list of included files and is used to speed up search operations. |
04e24b14 DW |
55 | |
56 | ||
57 | The Manifest: ``index.json`` | |
58 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
59 | ||
717ce406 | 60 | The manifest contains a list of all backed up files, and their |
04e24b14 DW |
61 | sizes and checksums. It is used to verify the consistency of a |
62 | backup. | |
63 | ||
44df558d TL |
64 | Backup Namespace |
65 | ---------------- | |
66 | ||
67 | Namespaces allow for the reuse of a single chunk store deduplication domain for | |
6481fd24 | 68 | multiple sources, while avoiding naming conflicts and enabling more fine-grained |
44df558d TL |
69 | access control. |
70 | ||
6481fd24 DW |
71 | Essentially, they're implemented as a simple directory structure and don't |
72 | require separate configuration. | |
04e24b14 DW |
73 | |
74 | Backup Type | |
75 | ----------- | |
76 | ||
77 | The backup server groups backups by *type*, where *type* is one of: | |
78 | ||
79 | ``vm`` | |
e1dc2d22 SI |
80 | This type is used for :term:`virtual machine<Virtual machine>`\ s. It |
81 | typically consists of the virtual machine's configuration file and an image | |
82 | archive for each disk. | |
04e24b14 DW |
83 | |
84 | ``ct`` | |
e1dc2d22 SI |
85 | This type is used for :term:`container<Container>`\ s. It consists of the |
86 | container's configuration and a single file archive for the filesystem's | |
87 | contents. | |
04e24b14 DW |
88 | |
89 | ``host`` | |
717ce406 DW |
90 | This type is used for file/directory backups created from within a machine. |
91 | Typically this would be a physical host, but could also be a virtual machine | |
92 | or container. Such backups may contain file and image archives; there are no | |
93 | restrictions in this regard. | |
04e24b14 | 94 | |
04e24b14 DW |
95 | Backup ID |
96 | --------- | |
97 | ||
e87e4499 | 98 | A unique ID for a specific Backup Type and Backup Namespace. Usually the |
44df558d TL |
99 | virtual machine or container ID. ``host`` type backups normally use the |
100 | hostname. | |
04e24b14 DW |
101 | |
102 | Backup Time | |
103 | ----------- | |
104 | ||
44df558d | 105 | The time when the backup was made with second resolution. |
04e24b14 DW |
106 | |
107 | ||
108 | Backup Group | |
109 | ------------ | |
110 | ||
44df558d TL |
111 | The tuple ``<type>/<id>`` is called a backup group. Such a group may contain |
112 | one or more backup snapshots. | |
113 | ||
04e24b14 | 114 | |
ec1ae7e6 | 115 | .. _term_backup_snapshot: |
04e24b14 DW |
116 | |
117 | Backup Snapshot | |
118 | --------------- | |
119 | ||
120 | The triplet ``<type>/<ID>/<time>`` is called a backup snapshot. It | |
ff438963 | 121 | uniquely identifies a specific backup within a namespace. |
04e24b14 DW |
122 | |
123 | .. code-block:: console | |
124 | :caption: Backup Snapshot Examples | |
125 | ||
126 | vm/104/2019-10-09T08:01:06Z | |
127 | host/elsa/2019-11-08T09:48:14Z | |
128 | ||
171a00ca | 129 | As you can see, the time format is RFC3339_ with Coordinated |
04e24b14 DW |
130 | Universal Time (UTC_, identified by the trailing *Z*). |
131 | ||
132 |