Changes for page Proxmox Backup server

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -50,6 +50,71 @@
50	50	```
51	51	~> NOTE! `-n` is dry run, remove to commit.
52	52
	53	+
	54	+= Access Control =
	55	+
	56	+Each client host that wants to backup their contents to the backup server should have their unique API token for authentication.
	57	+
	58	+API Token:
	59	+
	60	+* user: [[root@pam>>mailto:root@pam]]
	61	+* token name: CLIENT_NAME
	62	+* expire: never
	63	+* enabled: true
	64	+
	65	+Permissions - Add a API Token Permission:
	66	+
	67	+* path: /datastore/proxmox-backup/CLIENT_NAME
	68	+* api token: root@pam!CLIENT_NAME
	69	+* role: DatastoreBackup
	70	+* propagate: true
	71	+
	72	+>Note! The path will not be define until after the Datastore namespace is define in the steps below
	73	+
	74	+= Proxmox datastore =
	75	+
	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	+
	78	+=== Namespace ===
	79	+
	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	+
	82	+=== Prune & Garbage collect ===
	83	+
	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	+
	86	+* datastore: proxmox-backup
	87	+* namespace: root
	88	+* keep last: 4
	89	+* keep: hourly: -
	90	+* keep daily: 6
	91	+* keep weekly: 3
	92	+* keep monthly: 6
	93	+* keep yearly: 4
	94	+* max_depth: full
	95	+* prune schedule: 0/6:00
	96	+* enabled: true
	97	+
	98	+=== Verify jobs ===
	99	+
	100	+Current configuration is:
	101	+
	102	+* local datastore: proxmox-backup
	103	+* namespace: root
	104	+* max-depth: full
	105	+* schedule: daily
	106	+* skip verified: true
	107	+* re-verify after: 30 days
	108	+
	109	+=== Permissions ===
	110	+
	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	+
	113	+* path: /datastore/proxmox-backup/CLIENT_NAME
	114	+* API Token: root@pam!CLIENT_NAME
	115	+* Role: DatastoreBackup
	116	+* Propagate: true
	117	+
53	53	= Tailscale =
54	54
55	55	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.