Proxmox Backup server

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

* namespace: root

* keep last: 4

* keep: hourly: -

* keep daily: 6

* keep weekly: 3

* keep monthly: 6

* keep yearly: 4

* max_depth: full

* prune schedule: 0/6:00

* enabled: true

=== Verify jobs ===

Current configuration is:

101

102

* local datastore: proxmox-backup

* namespace: root

* max-depth: full

* schedule: daily

* skip verified: true

107

* re-verify after: 30 days

=== Permissions ===

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

* Propagate: true

= Tailscale =

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

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`.

124

125

= Jottacloud client =

126

127

Cloud backup provider used is jottacloud. They provide a cli to easily add directories to sync to their cloud backup storage.

128

NOTE! This setup still uses user `kevin` and not the correct jottad user.

129

130

131

{{{# install jotta-cli

132

sudo curl -fsSL https://repo.jotta.cloud/public.asc -o /usr/share/keyrings/jotta.gpg

133

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

134

sudo apt-get update

135

sudo apt-get install jotta-cli

136

137

# configure runtime environment

138

sudo useradd -m jottad

139

sudo usermod -a -G jottad backup}}}

140

141

142

Create systemd file: `/usr/lib/systemd/user/jottad.service ` and enable with :

(((

{{code language="ini" layout="LINENUMBERS" title="/usr/lib/systemd/user/jottad.service"}}

148

[Unit]

149

Description=Jotta client daemon

[Service]

Type=notify

# Group=backup

# UMask=0002

# EnvironmentFile=-%h/.config/jotta-cli/jotta-cli.env

157

ExecStart=/usr/bin/jottad stdoutlog datadir %h/.jottad/

Restart=on-failure

[Install]

WantedBy=default.target

)))

== Flaws ==

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.

168

169

It also seems like there are a LOT of files shifting - being added and deleted. Making the diff uploaded to jottacloud huge.

170

171

= Client Configuration =

172

173

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:

174

175

* selection mode: include selected VMs