Search results

When the documentation says that Proxmox VE "X" supports Debian "Y", what it exactly refers to? I suppose it means that Proxmox is based on that Debian version, and also that containers can run that Debian version. But what about VMs? Can an old release of Proxmox run a VM on which a recent...

Whoa! I misread the warning in the UI. I am off by one year :) If I upgrade PVE, after that will I be able to boot the old containers to launch the debian upgrade?

I have some proxmox containers running Debian 10, on a machine with PVE 6.4. Now I need to upgrade those to Debian 11 and then 12 (because I need certain recent packages). Can I do it with PVE 6.4? I ask because I know containers use the host's kernel, so I am not sure how this works. Or...

Thus to manually delete an old media-set and reuse its tapes, the correct way is just to select the tapes that belong to it and click FORMAT? (The reason is: since I backup manually without a fixed schedule, I am forced to set the retention policy to forever, but I don't really want to keep...

@dcsapak: I understand that the retention policy specifies when a media-set is retired. Currently, it appears it is only possible to specify a time interval (e.g. retire after two weeks). This is appropriate for scheduled backups, but it seems to me that it does not work well for manual backups...

Thanks a lot Dominik. Thus the proposed --force argument means "from now on use this password – but be warned that the old tapes still use the old one". Ok. By the way I noticed two little problems in the command: 1. The command currently asks for both the old and new password before...

@dcsapak maybe? :-)

I am using PBS to backup to tape. I have enabled encryption. Two questions: 1. I am not 100% sure that I have written down my password exactly. My backup server is still in good health, so I suppose I have the keys in /etc/proxmox-backup. Is there a way to retrieve the password, or at least to...

@dcsapak I don't need to follow that scheme exactly; what I would like to achieve, somehow, is simply to have frequent backups for recent times, and then more spaced backups for less recent times. For example, daily backups for the last 7 days, then weekly backups for the last 4 weeks, then...

Before PBS, I managed my tape backups manually using a ladder schedule, for example: Do a daily backup Keep the last 7 days. Every 7 days, move the backup to the "weekly" category Keep the last 4 weeklies. Every 4 weeks, move the backup to the "monthly" category Keep the monthlies indefinitely...

feature request here

WIth the instructions above and a little tweaking, I installed proxmox-backup-client on Ubuntu 20.04 LTS arm64 on a Raspberry PI 4: # get and install rust curl https://sh.rustup.rs -sSf | sh # get and install required dependencies apt install libclang-dev llvm gcc g++ clang-7 libacl1-dev...

I run tape backups without a fixed schedule; my datasets are rather small, so a single tape can contain several. (I have a simple drive, no library or tape changer). Since I have no fixed schedule, I set continue as my media set allocation policy. The idea is to trigger manually a new set...

Not just that. Grub also fails to boot if any encrypted dataset is present in the pool. See here

For anyone that could encounter the same problem: turns out the problem was that I had created a zfs dataset (in addition to the ones created by the PBS installer) without specifying the dnodesize=legacy option. When grub encounters a dataset with dnodesize=auto (the default), it fails to boot...

Is it possible to build from source the backup client for Ubuntu ARM64 (i.e. raspberry pi 4)?

Today, I started my Proxmox Backup server, and grub fails to boot. The server is a repurposed old machine with two 4TB HDD with ZFS RAID 1. This kind of failure happened to me in the past with PVE, when I was trying to have ZFS disks connected to a Dell PERC controller (an unhealthy idea that...

It also seems that this procedure corrupts the zfs cache files (the system works, but there is a FAILED message at boot). To rebuild it: zpool set cachefile=/etc/zfs/zpool.cache rpool update-initramfs -k all -u reboot

I found out the missing step: at the (initramfs) prompt, force the pool to be imported even if it was last accessed on a different machine: zfs import -f rpool zfs export rpool (the final export step is probably unneccessary, but just in case...) Shut down the machine, remove the temporary...

update: I have realized that I did not backup the boot partition. So for backup I did dd if=/dev/sda2 of=partition-sda2 dd if=/dev/sdb2 of=partition-sdb2 dd if=/dev/sdc2 of=partition-sdc2 and to restore (from removable media) dd if=partition-sda2 of=/dev/sdb2 dd if=partition-sdb2 of=/dev/sdc2...