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

Summary

Details

Page properties
Content
... ... @@ -15,7 +15,7 @@
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  
... ... @@ -34,7 +34,7 @@
34 34  errors: No known data errors}}}
35 35  
36 36  
37 -== Creating and expanding zfs pool ==
37 +=== Creating and expanding zfs pool ===
38 38  
39 39  ```
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
... ... @@ -51,7 +51,7 @@
51 51  ~> NOTE! `-n` is dry run, remove to commit.
52 52  
53 53  
54 -= Access Control =
54 +== 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 =
74 +== 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 ==
78 +=== 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 ==
82 +=== 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 ==
98 +=== 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 ==
109 +=== 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