Search results

Thanks, I commented on that bug, showing my support for this feature. Is making a gigantic zfs snapshot and pushing that to an S3 service the most viable workaround in the interim? Thanks!

Good day everyone! I have a lovely 3 node PVE cluster being backed up with a PBS 4.0 server. The backups on that PBS server are replicated to an off site PBS instance as well. For additional redundancy and resilience, I've been tasked with implementing immutable backups using S3 compatible...

Thank you for the list of things to check! Starting with the configuration, here it is: root@xxx:~# cat /etc/proxmox-backup/s3.cfg s3-endpoint: wasabi access-key xxx endpoint s3.ca-central-1.wasabisys.com region ca-central-1 secret-key xxx I've now set...

Thanks for the suggestion. I did try this with no change in behaviour.

I need some help with an access issue that I can't figure out myself. I just upgraded my primary PBS server to the latest PBS version as of this post. All went well with the upgrade (Thanks Proxmox! :) ). I then created a trial account on wasabi, created a bucket and a user to access it. I...

Looks like updates were automatically applied. Some of the updates included systemd components which is what triggered the systemd restart. I imagine we'll have to reboot the node, but are there any tricks to fixing this type of issue without a reboot? Thanks!

This morning, one node of a 3 node cluster decided to restart systemd. I haven't figured out why yet - don't see any updates having been installed or the like. The result is that we are unable to log in to the web interface and cron jobs are failing with a "failure setting user credentials"...

Thanks! So setting it to 2 will not use any additional space?

Hello! We have a 3-node PVE 7.2-4 cluster using Ceph 16.2.7. The cluster has been around for several years and we've completed most of the upgrades we want on it. We had been short on disk space for a long time, but recently added additional disk space. Unfortunately, when ceph was...

That's a good idea. Thanks for the reply!

We completed a PVE and Ceph upgrade from 6.4 to 7.2 Friday night. A 9.5TB NVR VM backup started shortly thereafter. We noticed the operation of the VM ground to a halt and the backup performance was fairly slow (71Mbps read, 52Mbps write). I applied the update to pve-qemu-kvm as described...

I can't now as I destroyed the pool. What I saw was just 'unclean' status. I followed this article which took me down the path of troubleshooting: Ran: ceph pg dump_stuck unclean (inactive, stale, undersized etc produced no output) I did not have peering errors. I then wound up at item 5.2.4...

Thanks so much for your reply, Mira! I was doing more reading about the rack/host/osd, etc domains. If I created a new rule (copy of ssd_ruleset) like this, it would work? (I know I still have many issues with using ceph with just two hosts): { "rule_id": 2, "rule_name"...

proxmox 6.1-8 ceph 14.2.22 I apologize in advance for the length of this post. I'll try to be brief but succinct with the explanation of the scenario. I inherited a proxmox 6.1 cluster with some unusual configuration. host a and b have a mix of HDDs and SSDs while host c is a cluster member...

When scanning my email on mobile or desktop clients, I think it would be more helpful to have the status result at the start of the emali subject line rather than the end. That would help me more swiftly determine if I need to look at the content of the message or not. This would be in line...

Sorry to not be clear - I'm talking about snapshots created in the PVE web gui. For example, if I make a PVE snapshot before a major change and that VM is included in a PBS backup job, does the snapshot get included in the backup? Can it be restored? Thanks

I've done lots of searching and haven't seen this question answered, but I apologize in advance if I missed something. Does Proxmox Backup Server backup manually created snapshots of a VM? Can the snapshots be restored without restoring the entire VM? Thanks in advance!