Search results

Sorry, but for me it's unclear what the problem is, how to reproduce / when does it happen, and what's different in your setup from a standard PVE installation were there's no issue like those you seem to describe. IIUC, you use/need some custom SSH settings that do not seem compatible with PVE...

If you don't mind powering off the source system, this [1] may help. I've haven't tried it yet, so I can't really say how good it could be to backup and specially on restore. [1] https://www.apalrd.net/posts/2024/pbs_image/

As much of the performance of your SAN/network you want to devote to a saferemove operation without impacting other operations ;) I don't see that happening any time soon unless some sort of cluster aware filesystem with thin provisioning gets properly implemented on Linux. I.e. a VMWare VMFS...

Hello, PVE 9 added "Support for snapshots as volume chains on Directory/NFS/CIFS storages (technology preview)". On any file level storage, like a directory or an NFS, you can use QCOW2 format for the disk(s) of your VMs, which already provides snapshot functionality and in some aspects in a...

The problem is that saferemove is throttled by default to a whooping 10MBytes/s. If you check with ps -ef while a snapshot is being removed you'll see a cstream process zeroing the snapshot volume. Meanwhile the very welcome improvement of using discard gets published, use this to increase the...

Use PBS to backup your VMs and set a replica job to S3 storage [1] [1] https://pbs.proxmox.com/docs/storage.html#datastores-with-s3-backend

You can't expect an exact answer if you don't provide an exact question: you are giving zero information on how your server/cluster is/was configured, zero information on what did you / happened to bork it and zero information on the current status. You don't even mentioned you have a cluster...

Hello, Is Veeam restore working for you with PVE plugin v12.1.5.17 either with PVE9 or PVE8.x? Recently Veeam has published PVE plugin v12.1.5.17 which should support PVE9 [1]. Tried using it to restore some backups made from ESXi but after selecting the destination storage and disk format I...

I would have tried to: - create another LUN in the iSCSI storage - connect it manually on one node - create an ext4 on it - mount it on that single node at /nnt/IMPORT - add it to PVE as directory storage in just that host. Essentially the same as the local disk you did, but using the iSCSI storage

Manual [1] says default is 262144, although it should not apply unless you have firewall enabled both for the host and at Datacenter level. I would also think that "default" could mean "use whatever is in the system", but it does in fact apply PVE's default for the value. Which, OTOH, is high...

Maybe you have it set at host's level firewall on PVE? Check on webUI or in /etc/pve/nodes/<NODE>/host.fw

I would go with LVM unless you want to use i.e. zfs-sync replication from "your" proxmox at the VPS to some other external Proxmox. It makes little sense to use ZFS in "your" Proxmox: CoW stacking and read/write amplification stacking will affect performance (which OTOH will be already be...

This has been discussed dozens of times already. That setup with those backup sizes won't ever perform well. You are using the two things that kill PBS GC performance: network shares and HDD only datastore. Your datastore size requires proper deployment. Every GC has to touch every single chunk...

Each K and M must be in a different host because you want your fault domain to be host (the default), not disk: i.e. if fault domain was disk you may end up with too many K or M (or both!) for some PGs in the same host and if that host goes down (i.e. a simple reboot) your VMs will hang because...

Thanks for the tip, it put me on the right track :). This is definitely what happened: someone did eject the nic from Windows: Any user can eject devices, even non-admin ones (come on, Microsoft, it's a server OS!!). It's an RDP host and I bet their GPO don't restrict user access to that...

Umm, might be but AFAIK no user should have permissions for it. Checked a log of event logs too and didn't find anything relevant (there's a lot of noise in the event log related to networked disk errors). By chance, do you know in which log exactly would something like that show up?

Looking for some clues about this or if someone else has seen this happening too (it's been a first for me and I do have thousand of VMs). Using PVE8.4.5. Have a VM with Windows 2019 with virtio drivers 0.1.271, running fine for a couple of weeks since the last reboot. This morning all of a...

Which is still very useful! Dreaming is free (and fun!).

Does this means that PDM will be able to automagically setup SDN on both host/clusters so they automagically see each other so we can migrate between them without relying on other means for connectivity (VPNs and so on)?

Been out of the loop for a while. Would you mind posting a link to that thread? Think I've missed that issue completely. Thanks!