Search results

Just to close this one off from my POV. I am running Restic backups via the resticprofile wrapper tool deployed locally on the PBS instance. I use the schedule feature built in to resticprofile that handles the systemd service/timer for daily backups/forgets/prunes. I run a...

Or there are more important things to do before this and there are other perfectly working methods of cloud backup of the PBS datastore.

Tonight I restored the 50GB PBS datastore via Restic from Borgbase (cloud), I was able successfully run a PBS verification on a VM and then restore in PVE after adding the restored datastore. VM started up straight away with zero issues. sudo resticprofile restore latest --target...

Again, the datastore is just files. Restic chunks, checksums, dedupes, encrypts, copies. I don’t know what you’re so afraid of. What can possibly happen to a bunch of files that are checksummed and verified as exact duplicates? I’ve ready the forum posts. I’m not using rclone (with crypt...

Ok champ. The chunk store is just folders of fixed size files. Files on disk that are being 1:1 backed up after shutting down the PBS service. How is backing up the PBS datastore files a 'hack'? What's the alternative? Building a VPS with terabytes or storage and running another PBS server? How...

I'll continue to use Restic (with the awesome resticprofile wrapper) to back up the local PBS repo to Borgbase. I am now running a script before a backup (using the resticprofile "run-before" run hook https://creativeprojects.github.io/resticprofile/configuration/run_hooks/index.html) to...

So changing backup strategy to only using PVE backups (no PBS) and using Restic to upload full dump files and use its dedup results in far greater backup sizes which will double cost for cloud stored backups (I'm using Borgbase as a hosted backup repository). b0c5356c 2025-05-23 02:00:08...

No I didn't - I was at work trying to contribute while I had 5mins.

Restic does not seem to to make much difference to the already de-duped PBS data, maybe 1GB smaller in Restic for the same data: root@pve01:~# du -s /mnt/backup0/ 56074654 /mnt/backup0/ ➜ restic stats a3899631 repository caecd736 opened (version 2, compression level auto) [0:00] 100.00%...

What issues have people had with an rclone restore? My test restores have worked fine. Been using Restic and PVE/PBS for years now.

What form factor? Are they internal drives?

What are you using for storage on the N100?

Oh - I forgot this: root@pve01:~# pveversion -v proxmox-ve: 8.2.0 (running kernel: 6.8.4-2-pve) pve-manager: 8.2.2 (running version: 8.2.2/9355359cd7afbae4) proxmox-kernel-helper: 8.1.0 proxmox-kernel-6.8: 6.8.4-2 proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2 ceph-fuse: 17.2.7-pve3 corosync...

It works if I revert to "Default (Auto)" remove the email address and then change back to "Notification system" Should probably be considered a UI bug. Changing to "Notification system" should remove previous config in /etc/pve/jobs.cfg

So it turns out that if you previously had email options set in the UI and change "Notification mode" from "Default (Auto)" to "Notification system" the old email address and "mailnotification always" is left in the /etc/pve/jobs.cfg config file.

/etc/pve/notifications.cfg smtp: xx-support author xx-pve01 from-address no-reply@xx.com.au mailto-user root@pam mode tls port 465 server smtp-relay.gmail.com matcher: default-matcher comment Route all notifications to xx-support mode all target xx-support...

I am using "Notification System" in the backup config

I have set up an SMTP notification target (Google Workspace) that uses the smtp-relay.gmail.com host and no authentication (src IP verification). When I test using the PVE > Notifications > Test button the test email comes through as "Author <email@address.com". When I use the same notification...

The backup simulator shows the correct schedule: What is causing it to run backups every few minutes whenever I enable that job?

I changed an existing backup schedule and set Schedule to 03:00. I selected the "Every day 21:00" from the drop down and changed to 03:00 so I had the correct format. The backup is now running every 3mins instead of daily at 03:00. What have I done wrong here? /etc/pve/jobs.cfg...