]> git.proxmox.com Git - proxmox-backup.git/blob - docs/faq.rst
docs: faq: move support table to CSV
[proxmox-backup.git] / docs / faq.rst
1 FAQ
2 ===
3
4 What distribution is Proxmox Backup Server (PBS) based on?
5 ----------------------------------------------------------
6
7 Proxmox Backup Server is based on `Debian GNU/Linux <https://www.debian.org/>`_.
8
9
10 Which platforms are supported as a backup source (client)?
11 ----------------------------------------------------------
12
13 The client tool works on most modern Linux systems, meaning you are not limited
14 to Debian-based backups.
15
16
17 Will Proxmox Backup Server run on a 32-bit processor?
18 -----------------------------------------------------
19
20 Proxmox Backup Server only supports 64-bit CPUs (AMD or Intel). There are no
21 future plans to support 32-bit processors.
22
23
24 .. _faq-support-table:
25
26 How long will my Proxmox Backup Server version be supported?
27 ------------------------------------------------------------
28
29 .. csv-table:: Table Title
30 :file: faq-release-support-table.csv
31 :widths: 30 26 13 13 18
32 :header-rows: 1
33
34 How can I upgrade Proxmox Backup Server to the next point release?
35 ------------------------------------------------------------------
36
37 Minor version upgrades, for example upgrading from Proxmox Backup Server in
38 version 3.1 to 3.2 or 3.3, can be done just like any normal update.
39 But, you should still check the `release notes
40 <https://pbs.proxmox.com/wiki/index.php/Roadmap>`_ for any relevant noteable,
41 or breaking change.
42
43 For the update itself use either the Web UI *Node -> Updates* panel or
44 through the CLI with:
45
46 .. code-block:: console
47
48 apt update
49 apt full-upgrade
50
51 .. note:: Always ensure you correctly setup the
52 :ref:`package repositories <sysadmin_package_repositories>` and only
53 continue with the actual upgrade if `apt update` did not hit any error.
54
55 .. _faq-upgrade-major:
56
57 How can I upgrade Proxmox Backup Server to the next major release?
58 ------------------------------------------------------------------
59
60 Major version upgrades, for example going from Proxmox Backup Server 2.4 to
61 3.1, are also supported.
62 They must be carefully planned and tested and should **never** be started
63 without having an off-site copy of the important backups, e.g., via remote sync
64 or tape, ready.
65
66 Although the specific upgrade steps depend on your respective setup, we provide
67 general instructions and advice of how a upgrade should be performed:
68
69 * `Upgrade from Proxmox Backup Server 2 to 3 <https://pbs.proxmox.com/wiki/index.php/Upgrade_from_2_to_3>`_
70
71 * `Upgrade from Proxmox Backup Server 1 to 2 <https://pbs.proxmox.com/wiki/index.php/Upgrade_from_1.1_to_2.x>`_
72
73 Can I copy or synchronize my datastore to another location?
74 -----------------------------------------------------------
75
76 Proxmox Backup Server allows you to copy or synchronize datastores to other
77 locations, through the use of *Remotes* and *Sync Jobs*. *Remote* is the term
78 given to a separate server, which has a datastore that can be synced to a local store.
79 A *Sync Job* is the process which is used to pull the contents of a datastore from
80 a *Remote* to a local datastore.
81
82
83 Can Proxmox Backup Server verify data integrity of a backup archive?
84 --------------------------------------------------------------------
85
86 Proxmox Backup Server uses a built-in SHA-256 checksum algorithm, to ensure
87 data integrity. Within each backup, a manifest file (index.json) is created,
88 which contains a list of all the backup files, along with their sizes and
89 checksums. This manifest file is used to verify the integrity of each backup.
90
91
92 When backing up to remote servers, do I have to trust the remote server?
93 ------------------------------------------------------------------------
94
95 Proxmox Backup Server transfers data via `Transport Layer Security (TLS)
96 <https://en.wikipedia.org/wiki/Transport_Layer_Security>`_ and additionally
97 supports client-side encryption. This means that data is transferred securely
98 and can be encrypted before it reaches the server. Thus, in the event that an
99 attacker gains access to the server or any point of the network, they will not
100 be able to read the data.
101
102 .. note:: Encryption is not enabled by default. To set up encryption, see the
103 :ref:`backup client encryption section <client_encryption>`.
104
105
106 Is the backup incremental/deduplicated/full?
107 --------------------------------------------
108
109 With Proxmox Backup Server, backups are sent incrementally to the server, and
110 data is then deduplicated on the server. This minimizes both the storage
111 consumed and the impact on the network. Each backup still references all
112 data and such is a full backup. For details see the
113 :ref:`Technical Overview <tech_design_overview>`