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.

86

87

=== Namespace ===

88

89

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.

90

91

=== Prune & Garbage collect ===

92

93

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:

94

95

* 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:

110

111

* local datastore: proxmox-backup

* namespace: root

* max-depth: full

* schedule: daily

* skip verified: true

116

* 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:

121

122

* path: /datastore/proxmox-backup/CLIENT_NAME

123

* API Token: root@pam!CLIENT_NAME

124

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

130

131

Setting up a connection should only require `sudo tailscale up ~-~-login-server https:~/~/TAILSCALE_SUBDOMAIN.schleppe.cloud`.

132

To view the status: `sudo tailscale status`.

133

134

= Jottacloud client =

135

136

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

137

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

(((

# install jotta-cli

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

143

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

144

sudo apt-get update

145

sudo apt-get install jotta-cli

146

147

# configure runtime environment

148

sudo useradd -m jottad

149

sudo usermod -a -G jottad backup

)))

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

(((

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

159

[Unit]

160

Description=Jotta client daemon

[Service]

Type=notify

# Group=backup

# UMask=0002

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

168

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.

179

180

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

181

182

= Client Configuration =

183

184

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:

185

186

* selection mode: include selected VMs