Search results

Hi, Could you post: pveversion -v The entire task log for the backup What file system is the mounted drive using? Is it a local storage or network storage? Note also that the Proxmox Backup subforum is intended for questions about Proxmox Backup Server [1]. If you have issues with Proxmox VE...

I don't think there are any parameters that can accomplish this as the host can't simply access directories of a VM like it can a container. One workaround that I can think of is to add another virtual drive to VM and mount /var/www/ on this. Then you can exclude the drive from the backup. From...

I can't speak for the status of these drivers, but if it's keeping you back, that's no problem. PBS1 is still supported and will be until ~Q2/2022 [1]. [1] https://pbs.proxmox.com/docs/faq.html#how-long-will-my-proxmox-backup-server-version-be-supported

Just to clarify, the error message seen here isn't necessarily an issue (command 'corosync-cfgtool -k 3' failed: exit code 1). It simply means that corosync could not kill the node, because if you follow the documentation correctly, the node will already be offline. The steps to remove the node...

Note that PBS 2 is now released, so may have been the better option for a fresh install. In any case, PBS1 is still supported and upgrading is straightforward [1], so no worries. From your description, it seems that you may not have mounted a file system, but rather just created a directory on...

@YaseenKamala I'm happy to help :) As @czechsys mentioned, Proxmox VE 5.x is EOL and has been for roughly a year [1]. You should schedule an update as soon as possible to at least version 6 [2]. If you choose to upgrade to version 7 (latest and recommended), you will still need to upgrade to...

Hi, The other backup targets in Proxmox VE are simply storage devices, and as a result, can only support full backups, i.e., upon every backup, a full copy of the VM must be created and stored. PBS is a dedicated backup solution and thus, comes with many extra features that provide a...

Hi, You are correct. There seem to be a few issues with the catalog shell, which I have been meaning to get to. Thanks for pointing this one out. I've created a bug report [1]. For now, you can restore an entrire folder from the shell with: find dirname/** --select This will recursively copy...

Happy I could help :) Although I can't confirm any specific time frame, allowing for these scenarios is a part of our PBS roadmap [1]. [1] https://pbs.proxmox.com/wiki/index.php/Roadmap

Hi, The nodes should all be using the same storage configuration in the background. Is it possible that you have a totally different VM301 backup already on the PBS datastore, owned by user 'biuser@pbs', which could be interfering?

This information is not displayed on an attempted login, only a successful one. And it simply displays the software version, license information, and last login date/time. What specifically is your concern with it?

I'm not sure I follow. Have you installed Proxmox VE and are now having trouble updating the system? Or are you having trouble booting the system?

Is this the log from the node which restarted? It seems like the node lost connection to the cluster, which triggered a reboot (see section 15 of the PVE Admin Guide, in particular, fencing [1]). I'm not entirely sure what caused the node to lose connection though. [1]...

I would still try to set 'cpu: host' as @Republicus suggested, because the default cpu (kvm64) emulates quite an old CPU model, and mostly exists for the sake of guaranteed compatibility between hosts for migragtion.

I have just installed virtualbox 6.1 (from APT, via: focal-updates/multiverse) on ubuntu 20.04, with nested virtualisation enabled on my host, and I had no problems setting VT-x. I am unsure as to why it works for you in version 5.1, but not in 6.1. Where did you install virtualbox from (not...

To get a better idea of how storage is being consumed, could you post the output of zfs list -t all -r <pool_name>?

@xbb, if you are running the latest versions (with 'qemu-server 7.0-13'), would it be possible for you to install the debug version and follow Stefan's previous instructions [1]? This would really help us to further understand the issue. [1]...

Just to confirm, you enabled nested virtualisation on the host, not the VM, right? Did you follow our guide [1] to enable nested virtualisation? Could you post the following? Ubuntu VM config: qm config <vmid> Proxmox VE version: pveversion -v CPU model [1]...

Which concerns did you see in regard to ZFS? I would definitely agree that ZFS is the more reliable option

This is because Ceph requires the full, bare disk. Your disks contain partitions which seem to be in use already. You will have to format the drives, before using them with Ceph. I am unsure where this came from, if not from you, but if you like, you can remove it you remove, destroy and zap it...