Search results

Any news on the subject. Several people have the same problem and the fix shoud not too complicated.

I have the same problem. On a Windows Server 2003R2 with just 65 GB hard disk, 14,5 GB are "changed" every day even though the machine is NOT used at all! Even the deduplication doesn't seem to reduce the amount. Where do this tremendous changes come from? INFO: creating Proxmox Backup Server...

Actually it is not the problem, that differences are not known, but it seems to be a design deficiency in the container backup format, which is quite different from the VM backup format.

The problem is not LUKS vs ZFS encryption, but the problem to be able to remotely unlock the server. The servers usually have no keyboard/monitor. So a base system is needed to boot up, connect via SSH to unlock the volumes.

At boot decryption is not possible (otherwise I could use full rpool encryption). So is it possible to prevent pve-cluster.service to automatically start up and wait for manual disk decryption and manuall start command (all via ssh)?

I have to store the master private key AND the master key password which is much longer than the actuall encryption key. So I still dont' understand what the use case scenaria is, where the use of the RSA master encryption is useful instead of storing the actual encryption key.

The data disk are encrypted (my manually typing in a password), so stealing the servers (and switching it off of cause) keeps the data safe. The problem however is data or passwords which resides on the unencrytped system volume. To keep data save the passwords and keys should be on encrypted...

1) Where does PBS store the encryption key in a cluster? I have a proxmox cluster with 3 nodes and created a backup key on node1 as well as a master key. The documentation says, the keys are in /root/.config/proxmox-backup. The corresponding directory in node2 has only the file "fingerprint" and...

1) I subscribed to the mailing list, but it is very difficult to follow anything there, because there there are no ordered discussion threads, all topics are mixed up. I don't see how to do a disussion there. Is there any tool for this or how do you use it? 2) Why don't you explain the problem...

Here the log: 2020-11-16T09:38:28+01:00: percentage done: 3.92% (44 of 1123 snapshots) 2020-11-16T09:38:28+01:00: verify pvebackup:ct/103/2020-10-03T22:14:06Z - manifest load error: unable to load blob '"/data1/pvebackup/ct/103/2020-10-03T22:14:06Z/index.json.blob"' - No such file or directory...

The defective backup snapshothas a ever running hour glass in the contents view

I opened a feature request https://bugzilla.proxmox.com/show_bug.cgi?id=3138 to speed up container backup, but it gets closed multiple times without discussion and even with wrong claims. The feature request is perfectly valid, because PBS would be the ONLY backup solution in the world, which...

I opened a feature request https://bugzilla.proxmox.com/show_bug.cgi?id=3138 to speed up container backup, but it gets closed multiple times without discussion and even with wrong claims. The feature request is perfectly valid, because PBS would be the ONLY backup solution in the world, which...

1) How to fix the verification error? 2) How to remove vm/208, which is not listed in contents?

PBS should come with preconfigured fail2ban support. No service should be exposed to the internet without it. This is one reason I choose ssh tunnel, because everything with security works out of the box.

The new manual verification ends with the following error: 2020-11-18T15:31:32+01:00: verify pvebackup:vm/145/2020-09-06T14:37:17Z 2020-11-18T15:31:32+01:00: check qemu-server.conf.blob 2020-11-18T15:31:32+01:00: check drive-ide0.img.fidx 2020-11-18T15:31:32+01:00: verified 0.00/0.00 MiB...

Where to find the task id? I tried the following: # proxmox-backup-manager task log pvebackup:v-bdc1352d-dd0b Error: unable to parse UPID 'pvebackup:v-bdc1352d-dd0b' # proxmox-backup-manager task log v-bdc1352d-dd0b Error: unable to parse UPID 'v-bdc1352d-dd0b' proxmox-backup-manager task log...

Here the log: 2020-11-16T06:49:17+01:00: verify pvebackup:vm/145/2020-09-08T01:21:03Z 2020-11-16T06:49:17+01:00: check qemu-server.conf.blob 2020-11-16T06:49:17+01:00: check drive-ide0.img.fidx 2020-11-16T06:49:17+01:00: verified 0.00/0.00 MiB in 0.00 seconds, speed 0.00/0.00 MiB/s (0...

no. Could it happen automatically? Anyway: the log should tell more about the error.

After running for 1,5 days my verification job failed with error "TASK ERROR: verification failed - please check the log for details", but the whole log only says "0 errors" for each step. Where to find information, what failed exactly? BTW: It would be a good thing, if it were possible to...