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 20.1
edited by Kevin Wiki
on 2024/04/06 14:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,7 +2,7 @@
2 2  (((
3 3  (% class="col-xs-12 col-sm-8" %)
4 4  (((
5 -= Configuration =
5 += Backup Server configuration =
6 6  
7 7  Backup server is setup with:
8 8  
... ... @@ -15,43 +15,52 @@
15 15  ** permissions
16 16  * timings and simulator
17 17  
18 -= ZFS storage array =
18 +== 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
22 +(((
23 +{{code language="none"}}
24 +kevin@clio:~$ sudo zpool status pergamum
25 +pool: pergamum
26 +state: ONLINE
27 +  scan: scrub repaired 0B in 09:52:23 with 0 errors on Sun Mar 10 10:16:24 2024
26 26  config:
29 +        NAME                                            STATE     READ WRITE CKSUM
30 +        pergamum                                        ONLINE       0     0     0
31 +          raidz1-0                                      ONLINE       0     0     0
32 +            scsi-0QEMU_QEMU_HARDDISK_drive-scsi2-part1  ONLINE       0     0     0
33 +            sdc1                                        ONLINE       0     0     0
34 +errors: No known data errors
35 +{{/code}}
36 +)))
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}}}
39 +=== Creating and expanding zfs pool ===
35 35  
36 -
37 -== Creating and expanding zfs pool ==
38 -
39 -```
41 +(((
42 +{{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 -```
47 +{{/code}}
48 +)))
45 45  
46 46  
51 +(((
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 -```
53 +
54 +{{code language="none"}}
49 49  zpool add -n pergamum raidz DISK1 DISK2
50 -```
56 +{{/code}}
57 +
58 +
51 51  ~> NOTE! `-n` is dry run, remove to commit.
60 +)))
52 52  
53 53  
54 -= Access Control =
63 +== 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 =
83 +== 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 ==
87 +=== 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 ==
91 +=== 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 ==
107 +=== 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 ==
118 +=== 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  
... ... @@ -122,40 +122,79 @@
122 122  Setting up a connection should only require `sudo tailscale up ~-~-login-server https:~/~/TAILSCALE_SUBDOMAIN.schleppe.cloud`.
123 123  To view the status: `sudo tailscale status`.
124 124  
125 -= Client Configuration =
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
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}}
138 +sudo apt-get update
139 +sudo apt-get install tailscale
134 134  
135 -= Methodology =
141 +systemctl status tailscaled.service
142 +sudo tailscale up --login-server SUBDOMAIN.schleppe.cloud --authkey AUTHKEY
143 +tailscale status
144 +{{/code}}
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.
146 += Jottacloud client =
138 138  
139 -== Sub-paragraph ==
148 +Cloud backup provider used is jottacloud. They provide a cli to easily add directories to sync to their cloud backup storage.
149 +NOTE! This setup still uses user `kevin` and not the correct jottad user.
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.
151 +(((
152 +{{code language="none"}}
153 +# install jotta-cli
154 +sudo curl -fsSL https://repo.jotta.cloud/public.asc -o /usr/share/keyrings/jotta.gpg
155 +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
156 +sudo apt-get update
157 +sudo apt-get install jotta-cli
142 142  
143 -= Proxmox backup server =
159 +# configure runtime environment
160 +sudo useradd -m jottad
161 +sudo usermod -a -G jottad backup
162 +{{/code}}
163 +)))
144 144  
145 -= =
165 +Create systemd file: `/usr/lib/systemd/user/jottad.service ` and enable with :
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.
167 +(((
168 +
148 148  
149 -== Sub-paragraph ==
170 +{{code language="ini" layout="LINENUMBERS" title="/usr/lib/systemd/user/jottad.service"}}
171 +[Unit]
172 +Description=Jotta client daemon
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.
174 +[Service]
175 +Type=notify
176 +# Group=backup
177 +# UMask=0002
152 152  
153 -== Sub-paragraph ==
179 +# EnvironmentFile=-%h/.config/jotta-cli/jotta-cli.env
180 +ExecStart=/usr/bin/jottad stdoutlog datadir %h/.jottad/
181 +Restart=on-failure
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.
183 +[Install]
184 +WantedBy=default.target
185 +{{/code}}
156 156  )))
157 157  
188 +== Flaws ==
158 158  
190 +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.
191 +
192 +It also seems like there are a LOT of files shifting - being added and deleted. Making the diff uploaded to jottacloud huge.
193 +
194 += Client Configuration =
195 +
196 +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:
197 +
198 +* selection mode: include selected VMs
199 +* send email to: [[[email protected]>>mailto:[email protected]]]
200 +* email: on failure only
201 +* mode: snapshot
202 +* enabled: true
203 +* job comment: ~{~{guestname}}, ~{~{node}}, ~{~{vmid}}
204 +)))
205 +
206 +
159 159  (% class="col-xs-12 col-sm-4" %)
160 160  (((
161 161  {{box title="**Contents**"}}