Changes for page Proxmox Backup server
Last modified by Kevin Wiki on 2024/05/21 21:23
From version
28.1
edited by Kevin Wiki
on 2024/05/21 19:17
on 2024/05/21 19:17
Change comment:
There is no comment for this version
To version
22.1
edited by Kevin Wiki
on 2024/04/06 14:16
on 2024/04/06 14:16
Change comment:
There is no comment for this version
Summary
Details
- Page properties
-
- Content
-
... ... @@ -3,11 +3,8 @@ 3 3 (% class="col-xs-12 col-sm-8" %) 4 4 ((( 5 5 (% class="wikigeneratedid" %) 6 - Followingprovidessetupsteps,configurationexplanationandapplicationinstructionsforbackupserver. Thisboxboth generatesbackupsand syncs themtoremote locations.View generalbackupexplanation page[[Serverbackup>>doc:infra.Backup.WebHome]] for high-levelinformation.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. 7 7 8 -(% class="wikigeneratedid" %) 9 -Web GUI: [[https:~~/~~/clio.schleppe:8007/#pbsDashboard>>url:https://clio.schleppe:8007/#pbsDashboard]] 10 - 11 11 = Backup Server configuration = 12 12 13 13 Backup server is setup with: ... ... @@ -208,54 +208,16 @@ 208 208 209 209 It also seems like there are a LOT of files shifting - being added and deleted. Making the diff uploaded to jottacloud huge. 210 210 211 -= Syncthing = 212 - 213 -TODO 214 - 215 215 = Client Configuration = 216 216 217 217 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: 218 218 219 219 * selection mode: include selected VMs 220 -* send email to: E MAIL_ADDRESS213 +* send email to: [[kevin.midboe+PVE_HOSTNAME@gmail.com>>mailto:kevin.midboe+PVE_HOS[email protected]]] 221 221 * email: on failure only 222 222 * mode: snapshot 223 223 * enabled: true 224 224 * job comment: ~{~{guestname}}, ~{~{node}}, ~{~{vmid}} 225 - 226 - 227 -= Debugging/issues live here = 228 - 229 -== Permission denied anything for certain backups == 230 - 231 -When trying to restore a VM I noticed that it was very outdated. Before doing anything I got a `Permission denied (os error 13)` error message. I checked the permissions of the storage mount in proxmox cluster, generated new API key, removed and re-added the storage to node getting permission denied, and what gave it away I also got it when running the CLI command from proxmox-backup-server host. 232 - 233 -{{code language="bash"}} 234 -kevin@clio:~$ sudo proxmox-backup-client snapshot forget -ns apollo -repository proxmox-backup 'vm/201/2023-07-31T01:31:18Z' 235 -[sudo] password for kevin: 236 -Password for "root@pam": ***************** 237 -fingerprint: **:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:**:** 238 -Are you sure you want to continue connecting? (y/n): y 239 -storing login ticket failed: $XDG_RUNTIME_DIR must be set 240 -Error: removing backup snapshot "/mnt/pergamum/proxmox-backup/ns/apollo/vm/201/2023-07-31T01:31:18Z" failed - Permission denied (os error 13) 241 - 242 -kevin@clio:~$ ls -l "/mnt/pergamum/proxmox-backup/ns/apollo/vm/201/2023-07-31T01:31:18Z" 243 -total 263 244 --rw-r--r-- 1 root root 667 Feb 17 01:16 client.log.blob 245 --rw-r--r-- 1 root root 167936 Feb 17 01:16 drive-scsi0.img.fidx 246 --rw-r--r-- 1 root root 539 Feb 17 01:16 index.json.blob 247 --rw-r--r-- 1 root root 342 Feb 17 01:16 qemu-server.conf.blob 248 -{{/code}} 249 - 250 -Aha! The owner of everything in these folders should be `backup:backup`. 251 - 252 -**Resolve using:** 253 - 254 -{{code language="bash"}} 255 -kevin@clio:~$ sudo chown -R backup:backup /mnt/pergamum/proxmox-backup/ns/apollo/* 256 -{{/code}} 257 - 258 - 259 259 ))) 260 260 261 261