Skip to Content

Changes for page Proxmox Backup server

Last modified by Kevin Wiki on 2024/05/21 21:23
From version 13.1
edited by Kevin Wiki
on 2024/04/06 11:12
Change comment: There is no comment for this version
To version 22.1
edited by Kevin Wiki
on 2024/04/06 14:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,8 +2,11 @@
2 2  (((
3 3  (% class="col-xs-12 col-sm-8" %)
4 4  (((
5 -= Configuration =
5 +(% class="wikigeneratedid" %)
6 +Backsup are primarly done through proxmox backup server taking snapshot of running lxc and vm's. These are stored on mirrored ZFS array and synchronized to both off-site location and cloud storage provider.
6 6  
8 += Backup Server configuration =
9 +
7 7  Backup server is setup with:
8 8  
9 9  * zfs storage
... ... @@ -15,43 +15,52 @@
15 15  ** permissions
16 16  * timings and simulator
17 17  
18 -= ZFS storage array =
21 +== ZFS storage array ==
19 19  
20 20  There are currently 2 x 8TB WD drives. Current pool status:
21 21  
22 -{{{kevin@clio:~$ sudo zpool status pergamum
23 - pool: pergamum
24 - state: ONLINE
25 - scan: scrub repaired 0B in 09:52:23 with 0 errors on Sun Mar 10 10:16:24 2024
25 +(((
26 +{{code language="none"}}
27 +kevin@clio:~$ sudo zpool status pergamum
28 +pool: pergamum
29 +state: ONLINE
30 +  scan: scrub repaired 0B in 09:52:23 with 0 errors on Sun Mar 10 10:16:24 2024
26 26  config:
32 +        NAME                                            STATE     READ WRITE CKSUM
33 +        pergamum                                        ONLINE       0     0     0
34 +          raidz1-0                                      ONLINE       0     0     0
35 +            scsi-0QEMU_QEMU_HARDDISK_drive-scsi2-part1  ONLINE       0     0     0
36 +            sdc1                                        ONLINE       0     0     0
37 +errors: No known data errors
38 +{{/code}}
39 +)))
27 27  
28 - NAME STATE READ WRITE CKSUM
29 - pergamum ONLINE 0 0 0
30 - raidz1-0 ONLINE 0 0 0
31 - scsi-0QEMU_QEMU_HARDDISK_drive-scsi2-part1 ONLINE 0 0 0
32 - sdc1 ONLINE 0 0 0
33 33  
34 -errors: No known data errors}}}
42 +=== Creating and expanding zfs pool ===
35 35  
36 -
37 -== Creating and expanding zfs pool ==
38 -
39 -```
44 +(((
45 +{{code language="none"}}
40 40  zpool create pergamum raidz /dev/disk/by-partuuid/9fab17e5-df2d-2448-b5d4-10193c673a6b /dev/disk/by-partuuid/f801ed37-1d6c-ee40-8b85-6bfc49aba0fb -f
41 41  zfs set mountpoint=/mnt/pergamum pergamum
42 42  (zpool import -c /etc/zfs/zpool.cache -aN)
43 43  zpool export pergamum
44 -```
50 +{{/code}}
51 +)))
45 45  
46 46  
54 +(((
47 47  have not tried yet, but adding another set of disks for an additional top-level virtual device to our existing RAID-Z pool:
48 -```
56 +
57 +{{code language="none"}}
49 49  zpool add -n pergamum raidz DISK1 DISK2
50 -```
59 +{{/code}}
60 +
61 +
51 51  ~> NOTE! `-n` is dry run, remove to commit.
63 +)))
52 52  
53 53  
54 -= Access Control =
66 +== Access Control ==
55 55  
56 56  Each client host that wants to backup their contents to the backup server should have their unique API token for authentication.
57 57  
... ... @@ -71,15 +71,15 @@
71 71  
72 72  >Note! The path will not be define until after the Datastore namespace is define in the steps below
73 73  
74 -= Proxmox datastore =
86 +== Proxmox datastore ==
75 75  
76 76  If none exists create the datastore. Ours point is named `proxmox-backup` and points to ZFS storage mounted at `/mnt/pergamum`. All references to `proxmox-backup` referes to what you named it as in the create step here.
77 77  
78 -== Namespace ==
90 +=== Namespace ===
79 79  
80 80  Namespaces is what we will use in a datastore to separate permissions to each host. It's important to create these for the API tokens create in Access Control section above.
81 81  
82 -== Prune & Garbage collect ==
94 +=== Prune & Garbage collect ===
83 83  
84 84  We don't require backups for every day of the year. Pruning lets you systematically delete older backups, retaining backups for the last given number of time intervals. There exists a fantastic simulator that can be used to experiment with different backup schedules and prune options: [[https:~~/~~/pbs.proxmox.com/docs/prune-simulator/>>https://pbs.proxmox.com/docs/prune-simulator/]]. The current configuration is:
85 85  
... ... @@ -95,7 +95,7 @@
95 95  * prune schedule: 0/6:00
96 96  * enabled: true
97 97  
98 -== Verify jobs ==
110 +=== Verify jobs ===
99 99  
100 100  Current configuration is:
101 101  
... ... @@ -106,7 +106,7 @@
106 106  * skip verified: true
107 107  * re-verify after: 30 days
108 108  
109 -== Permissions ==
121 +=== Permissions ===
110 110  
111 111  Permissions are explained in the Access Control section above, but it can be easier to configure permissions from the datastore. Navigate to the datastore Permission tab and add API Token Permission:
112 112  
... ... @@ -119,43 +119,93 @@
119 119  
120 120  Tailscale is used to create a network that uses wireguard to transparently between local and remote machines. To not require a third party a local instance of headscale is used as the tailscale login server.
121 121  
122 -Setting up a connection should only require `sudo tailscale up ~-~-login-server https:~/~/TAILSCALE_SUBDOMAIN.schleppe.cloud`.
123 -To view the status: `sudo tailscale status`.
134 +{{code language="bash"}}
135 +curl -fsSL https://pkgs.tailscale.com/stable/ubuntu/focal.noarmor.gpg | sudo tee /usr/share/keyrings/tailscale-archive-keyring.gpg >/dev/null
136 +curl -fsSL https://pkgs.tailscale.com/stable/ubuntu/focal.tailscale-keyring.list | sudo tee /etc/apt/sources.list.d/tailscale.list
124 124  
125 -= Client Configuration =
138 +sudo apt-get update
139 +sudo apt-get install tailscale
126 126  
127 -Configure Backup on the Datacenter or PVE host level in the proxmox web GUI. If a backup storage is already added input the following preferences:
128 -\\{{code language="none" width="100%"}}Selection mode: include selected VMs
129 -Send email to: kevin.midboe+{PVE_HOSTNAME}@gmail.com
130 -Email: On failure only
131 -Mode: Snapshot
132 -Enabled: True
133 -Job Comment: {{guestname}}, {{node}}, {{vmid}}{{/code}}
141 +systemctl status tailscaled.service
142 +sudo tailscale up --login-server SUBDOMAIN.schleppe.cloud
143 +tailscale status
144 +{{/code}}
134 134  
135 -= Methodology =
146 +Connect to headscale login server:
136 136  
137 -Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
148 +{{code language="none"}}
149 +$ sudo tailscale up --login-server https://SUBDOMAIN.schleppe.cloud
138 138  
139 -== Sub-paragraph ==
151 +To authenticate, visit:
140 140  
141 -Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
153 + https://SUBDOMAIN.schleppe.cloud/register/nodekey:fe30125f6dc09b2ac387a3b06c3ebc2678f031d07bd87bb76d91cd1890226c9f
142 142  
143 -= Proxmox backup server =
155 +Success.
156 +{{/code}}
144 144  
145 -= =
158 +View more info in the docs: [[https:~~/~~/earvingad.github.io/posts/headscale/>>https://earvingad.github.io/posts/headscale/]]
146 146  
147 -Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
160 += Jottacloud client =
148 148  
149 -== Sub-paragraph ==
162 +Cloud backup provider used is jottacloud. They provide a cli to easily add directories to sync to their cloud backup storage.
163 +NOTE! This setup still uses user `kevin` and not the correct jottad user.
150 150  
151 -Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
165 +(((
166 +{{code language="none"}}
167 +# install jotta-cli
168 +sudo curl -fsSL https://repo.jotta.cloud/public.asc -o /usr/share/keyrings/jotta.gpg
169 +echo "deb [signed-by=/usr/share/keyrings/jotta.gpg] https://repo.jotta.cloud/debian debian main" | sudo tee /etc/apt/sources.list.d/jotta-cli.list
170 +sudo apt-get update
171 +sudo apt-get install jotta-cli
152 152  
153 -== Sub-paragraph ==
173 +# configure runtime environment
174 +sudo useradd -m jottad
175 +sudo usermod -a -G jottad backup
176 +{{/code}}
177 +)))
154 154  
155 -Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
179 +Create systemd file: `/usr/lib/systemd/user/jottad.service ` and enable with :
180 +
181 +(((
182 +
183 +
184 +{{code language="ini" layout="LINENUMBERS" title="/usr/lib/systemd/user/jottad.service"}}
185 +[Unit]
186 +Description=Jotta client daemon
187 +
188 +[Service]
189 +Type=notify
190 +# Group=backup
191 +# UMask=0002
192 +
193 +# EnvironmentFile=-%h/.config/jotta-cli/jotta-cli.env
194 +ExecStart=/usr/bin/jottad stdoutlog datadir %h/.jottad/
195 +Restart=on-failure
196 +
197 +[Install]
198 +WantedBy=default.target
199 +{{/code}}
156 156  )))
157 157  
202 +== Flaws ==
158 158  
204 +Since proxmox backup server uses chunks for deduplicating data a complete file list is required. This makes it impossible to download a single file representing a VM or LXC, all files must be downloaded and imported into proxmox backup server for reconstruction.
205 +
206 +It also seems like there are a LOT of files shifting - being added and deleted. Making the diff uploaded to jottacloud huge.
207 +
208 += Client Configuration =
209 +
210 +Configure Backup on the Datacenter or PVE host level in the proxmox web GUI. If a backup storage is already added input the following preferences:
211 +
212 +* selection mode: include selected VMs
213 +* send email to: [[[email protected]>>mailto:[email protected]]]
214 +* email: on failure only
215 +* mode: snapshot
216 +* enabled: true
217 +* job comment: ~{~{guestname}}, ~{~{node}}, ~{~{vmid}}
218 +)))
219 +
220 +
159 159  (% class="col-xs-12 col-sm-4" %)
160 160  (((
161 161  {{box title="**Contents**"}}