ayufan/pve-patches

Repository with public Proxmox patches

No longer maintained. Use Proxmox Backup Server instead. This provides significantly more elegant and scalable solution.

Proxmox Patches

Proxmox VE is a complete virtualization management solution for servers. You can virtualize even the most demanding application workloads running on Linux and Windows Servers. Checkout their page: proxmox.com.

Due to lack of better backup functionality I prepared patches to support differential backups in Proxmox VE. These patches are in use for over over a 6 years already :)

You find it valuable?

Buy me a Beer

What are differential backups?

According to Wikipedia:

A differential backup is a type of data backup that preserves data saving only the difference in the data since the last full backup. (…) Another advantage, at least as compared to the incremental backup method of data backup, is that at data restoration time, at most two backup media are ever needed to restore all the data. This simplifies data restores as well as increases the likelihood of shortening data restoration time.

What my patches do?

My patches extends vzdump, xdelta3 and Web-GUI support. And yes, these patches fully support OpenVZ and KVM.

System administrator can use one additional parameter in Backup Jobs (Datacenter -> Backup -> Add/Edit) the Full Backup Every:

• By default this value is set to 0. Which simply means: use old behavior (always create full backups).
• But if you specify value larger than 0, for example 7. It will instruct the vzdump to create full backup once a week and use differentials for the rest.

Please consider the following example:

    vzdump 101 --remove 0 --mode snapshot --compress lzo --storage local --node hvm --fullbackup 4

It will create full backup of VM101 every 4 days, compressed using lzo, stored on local storage.

How to install?

The installation procedure is fairly simple:

```bash
git clone https://github.com/ayufan/pve-patches
cd pve-patches
bash pve-6.0-11-diff-backup-addon apply
```

When everything went right, you’ll see:

```text
Proxmox VE 6.0-11 - differential backup support
Kamil Trzcinski, http://ayufan.eu/, [email protected]

PATCHED: /usr/share/pve-manager/
PATCHED: /usr/share/perl5/PVE/

Restarting PVE API Proxy Server: pveproxy.
Restarting PVE Daemon: pvedaemon.
```

Then install latest version of pve-xdelta3, which enables the support for LZOP and ZSTD compressors. You can find the sources here.

```bash
wget https://github.com/ayufan/pve-xdelta3/releases/download/3.0.11.zstd/pve-xdelta3_3.0.11-dfsg-1ubuntu1.zstd.ayufan2_amd64.deb
dpkg -i pve-xdelta3_3.0.11-dfsg-1ubuntu1.zstd.ayufan2_amd64.deb
```

Feel free to compile the sources yourself by downloading the repo and executing dpkg-buildpackage -b -us -uc.

And what about uninstall?

The procedure is simpler than installation. Type in the bash:

```bash
bash pve-6.0-11-diff-backup-addon revert
```

After a while, you’ll see:

```text
Proxmox VE 6.0-11 - differential backup support
Kamil Trzcinski, http://ayufan.eu/, [email protected]

RESTORED: /usr/share/pve-manager/
RESTORED: /usr/share/perl5/PVE/

Restarting PVE API Proxy Server: pveproxy.
Restarting PVE Daemon: pvedaemon.
```

What about UPGRADE? (READ THIS)

This is important part. If you will ever want to upgrade your Proxmox installation (by apt-get dist-upgrade or apt-get upgrade) ALWAYS revert/uninstall patches. You will still be able to apply them afterwards.

Hunks FAILED, but the patch version matches release! HELP?!

In case of any problems applying or reverting patches you can always simple revert back to stock. Simply reinstall modified packages (supported since 6.0-11):

```bash
./pve-6.0-11-diff-backup-addon reinstall
```

Then you can try to reapply patches once again. However, keep in mind that reinstall can install a newer version of the packages. In such cases it is advised always to do it connected with upgrade of Proxmox.

```bash
apt-get update
apt-get dist-upgrade
./pve-6.0-11-diff-backup-addon reinstall
./pve-6.0-11-diff-backup-addon apply
```

This effectively ensures that patch is applied on the latest version and completely in a clean approach.

In order to remove all leftovers you have to edit /etc/pve/vzdump.cron and remove fullbackup switch from vzdump command line.

How to apply new patch version?

• Use previous patch to revert changes.
• Download new patch version and apply as described before.

The results

The results are really astonishing! These are real word values:

```text
VM   full      diff 1day   diff 2days   diff 3days    diff 4days
1.   39.10GB   41MB        47MB         51MB          55MB
2.   96.84GB   1.07GB      1.38GB       1.43GB        1.68GB
3.   83.95GB   1.68GB      2.66GB       3.69GB        4.25GB
4.   9.19GB    76KB        76KB         166MB         198MB
```

You see the differences. The diff sizes strictly depends on the use of the VMs. Using differential backups I have backups from last month (full backup once a week, differential daily)

Is it stable?

Yes, it is. This extensions uses xdelta3 as differential backup tool, which proven to be well tested and stable. A number of people use it for over 6 years already :)

However, if you happen to be paranoidal about backups… You should consider running following script. The script simply tries to verify all differential backups. I recently updated the script to support new VMA archive. So now you can verify backups all supported backups.

```bash
./pve-verify-backups <backup-dir>
```

Changelog

• v1: initial public release with support for PVE2.2 and PVE2.3 (2013-03-05)
• v2: improved kvm backup size and speed for PVE2.3 (2013-03-08)
• v3: added support for PVE3.0 (2013-06-02)
• v3': updated pve-verify-backups to support VMA archives (2013-06-06)
• v3'': updated patches to support PVE3.1 (2013-08-24)
• v3'': updated xdelta3 to 3.0.6. More info about changes: http://xdelta.org/ (2013-08-24)
• v3'': updated patches to support PVE3.2 (2014-03-15)
• v3'': added FAQ (2014-04-30)
• v3'': updated patches to support PVE3.3 (2014-09-23)
• v3'': updated patches to support PVE3.4 (2015-02-26)
• v3'': updated patches to support PVE4.0 (2015-11-07)
• v3'': updated patches to support PVE4.1 (2016-01-22)
• v3'': updated patches to support PVE4.1-22 (2016-04-13)
• v3'': updated patches to support PVE4.2 (2016-05-02)
• v3'': updated patches to support PVE3.4-14 (2016-08-02)
• v3'': updated patches to support PVE4.2-17 (2016-08-02)
• v3'': updated patches to support PVE4.3 (2016-10-24)
• v3'': updated patches to support PVE4.4 (2017-01-23)
• v3'': updated patches to support PVE4.4-13 (2017-04-10)
• v3'': updated patches to support PVE5.0 (2017-07-20)
• v3''': updated patches to support PVE5.1 (2018-03-13)
• Please take a look at commit stream :)

Detailed list of changes

1. pve-xdelta3:
   • repackaged from http://packages.debian.org/wheezy/xdelta3
   • added support for lzop
   • removed all python references
2. vzdump:
   • added “fullbackup” option
3. qmrestore and vzrestore:
   • added support for differential backups
4. PVE.dc.BackupEdit:
   • added controls for maxfiles and fullbackup

Author

Kamil Trzciński, 2013-2020

License

MIT

pve-patches's Issues

VZDump doen't delete backup files after remove this patch

Hi there

I have 2 customers which I install the patch but, due performace problems, we decide to remove the patch...
But after that, we notice that vzdump doesn't remove old backup files....
Someone here has the same problem?

Thanks a lot

Not anable add fullbackup parameter

Hi!
Proxmox V6.1-3 in cluster mode.
apply patch, install xdelta3 on any host.
when add parametr maxfiles - 3 and any parametr full backup every:
I take mistake:
Parameter verification failed. (400)
fullbackup: property is not defined in schema and the schema does not allow additional properties.
Any idea?
PS. I update to 6.1-5. Wil it work on this version?

patch for version 6.0.6

Hello

I migrated proxmox to new server. After update, I noticed new version 6.0.6. However, I couldn't find patch for 6.0.6. Not sure if I can use 6.0.5 on 6.0.6. Please suggest

Thanks

Abhishek

Full backup every X don't work

Hello
Thanks for your tool, i install on proxmox 6.1.8, no problem to patch.
The first backup is process as full, this is fine. But the parameter --fullbackup is not applied.

My command :
vzdump 103 --mode snapshot --compress lzo --storage local --fullbackup 4

After multiple exec of the command, only the first full backup is present all others is diff.

Files:

/var/lib/vz/dump/vzdump-qemu-103-2020_04_29-09_26_56.vma.gz
/var/lib/vz/dump/vzdump-qemu-103-2020_04_29-09_26_56.vma.gz--differential-2020_04_29-09_33_12.vcdiff
/var/lib/vz/dump/vzdump-qemu-103-2020_04_29-09_26_56.vma.gz--differential-2020_04_29-09_36_29.vcdiff
/var/lib/vz/dump/vzdump-qemu-103-2020_04_29-09_26_56.vma.gz--differential-2020_04_29-09_43_25.dat
/var/lib/vz/dump/vzdump-qemu-103-2020_04_29-09_26_56.vma.gz--differential-2020_04_29-09_48_08.vcdiff
/var/lib/vz/dump/vzdump-qemu-103-2020_04_29-09_26_56.vma.gz--differential-2020_04_29-09_50_22.vcdiff
/var/lib/vz/dump/vzdump-qemu-103-2020_04_29-09_26_56.vma.gz--differential-2020_04_29-09_51_59.vcdiff
/var/lib/vz/dump/vzdump-qemu-103-2020_04_29-09_26_56.vma.gz--differential-2020_04_29-09_54_16.vcdiff
/var/lib/vz/dump/vzdump-qemu-103-2020_04_29-09_26_56.vma.gz--differential-2020_04_29-09_56_57.vcdiff

Do you have an idea of what is wrong ?

Thanks

Keep on taking backup even when Max backup is defined

Hello

I am having issue with max number of backup. Here's my current setting:

I want to have 3 backup copies and full backup on 4th day but it keep on taking backups. My understanding is that every 4th day (as max # of backups is 3) , it will delete first old backup copy. However that does not seem to be the case:

Can anyone please help?

Zstd differential backup on 6.2-4

Good afternoon.
I am glad that such a project exists.

I would like to know if it will work differential backup on Zstd?

Would it be possible for Proxmox to make a full daily backup and every hour to make a differential backup?

Hello, Congratulations on this work!
Would it be possible for Proxmox to make a full daily backup and every hour to make a differential backup of the VM?

Thanks in advance.
Best resgards

No changes in GUI pve 6.1-3

I applied this today on one of my pve 6.1-3 node from 4 node cluster. I cannot see any changes on web gui. neither in backup pane in individual VM. I tried clear browser cache and incognito mode also

`root@pve:/tmp/pve-patches-master# bash pve-6.0-11-diff-backup-addon apply
Proxmox VE 6.0-7 - differential backup support, v3
Kamil Trzcinski, http://ayufan.eu/, [email protected]

checking file usr/share/pve-manager/js/pvemanagerlib.js
Hunk #1 succeeded at 38698 (offset 326 lines).
checking file usr/share/perl5/PVE/LXC/Create.pm
Hunk #1 succeeded at 72 (offset 1 line).
Hunk #2 succeeded at 110 (offset 1 line).
checking file usr/share/perl5/PVE/QemuServer.pm
Hunk #1 succeeded at 5862 (offset -82 lines).
Hunk #2 succeeded at 6225 (offset -82 lines).
Hunk #3 succeeded at 6553 (offset -80 lines).
checking file usr/share/perl5/PVE/Storage.pm
Hunk #1 succeeded at 514 (offset 2 lines).
Hunk #2 succeeded at 1265 (offset 2 lines).
Hunk #3 succeeded at 1311 (offset 2 lines).
checking file usr/share/perl5/PVE/Storage/Plugin.pm
checking file usr/share/perl5/PVE/VZDump/Common.pm
checking file usr/share/perl5/PVE/VZDump.pm
Hunk #2 succeeded at 613 (offset 28 lines).
Hunk #3 succeeded at 680 (offset 28 lines).
Hunk #4 succeeded at 886 (offset 28 lines).
Hunk #5 succeeded at 898 (offset 28 lines).
Hunk #6 succeeded at 909 (offset 28 lines).
checking file usr/share/perl5/PVE/VZDump/LXC.pm
checking file usr/share/perl5/PVE/VZDump/QemuServer.pm
Hunk #1 succeeded at 246 (offset 3 lines).
Hunk #2 succeeded at 356 (offset 3 lines).
$ patch_apply /
patching file usr/share/pve-manager/js/pvemanagerlib.js
Hunk #1 succeeded at 38698 (offset 326 lines).
patching file usr/share/perl5/PVE/LXC/Create.pm
Hunk #1 succeeded at 72 (offset 1 line).
Hunk #2 succeeded at 110 (offset 1 line).
patching file usr/share/perl5/PVE/QemuServer.pm
Hunk #1 succeeded at 5862 (offset -82 lines).
Hunk #2 succeeded at 6225 (offset -82 lines).
Hunk #3 succeeded at 6553 (offset -80 lines).
patching file usr/share/perl5/PVE/Storage.pm
Hunk #1 succeeded at 514 (offset 2 lines).
Hunk #2 succeeded at 1265 (offset 2 lines).
Hunk #3 succeeded at 1311 (offset 2 lines).
patching file usr/share/perl5/PVE/Storage/Plugin.pm
patching file usr/share/perl5/PVE/VZDump/Common.pm
patching file usr/share/perl5/PVE/VZDump.pm
Hunk #2 succeeded at 613 (offset 28 lines).
Hunk #3 succeeded at 680 (offset 28 lines).
Hunk #4 succeeded at 886 (offset 28 lines).
Hunk #5 succeeded at 898 (offset 28 lines).
Hunk #6 succeeded at 909 (offset 28 lines).
patching file usr/share/perl5/PVE/VZDump/LXC.pm
patching file usr/share/perl5/PVE/VZDump/QemuServer.pm
Hunk #1 succeeded at 246 (offset 3 lines).
Hunk #2 succeeded at 356 (offset 3 lines).
APPLIED

$ service pveproxy restart
$ service pvedaemon restart`

Wrong FS type

Hi,
Not sure why but my 1st backup after applying the patch failed.

INFO: starting new backup job: vzdump 136 --quiet 1 --maxfiles 1 --fullbackup 7 --mode stop --mailto [hidden] --mailnotification always --storage BACKUP-SERVER --compress lzo
INFO: doing full backup, because no backup found in last 7 day(s)
INFO: Starting Backup of VM 136 (lxc)
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: CT Name: ELK
INFO: creating archive '/mnt/pve/BACKUP-SERVER/dump/vzdump-lxc-136-2019_02_24-23_00_02.tar.lzo'
mount: wrong fs type, bad option, bad superblock on /dev/mapper/LUN_BACKUPS-vm--136--disk--1,
missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.

umount: /mnt/vzsnap0/: not mounted
command 'umount -l -d /mnt/vzsnap0/' failed: exit code 32
ERROR: Backup of VM 136 failed - command 'mount /dev/dm-14 /mnt/vzsnap0//' failed: exit code 32
INFO: Backup job finished with errors
TASK ERROR: job errors

6.1-8 patch fails to apply

I was setting up a new Proxmox server today and was trying to apply your patch to it
It failed with this

root@pve0:~/pve-patches# bash pve-6.0-11-diff-backup-addon apply
Proxmox VE 6.0-7 - differential backup support, v3
Kamil Trzcinski, http://ayufan.eu/, [email protected]

checking file usr/share/pve-manager/js/pvemanagerlib.js
Hunk #1 succeeded at 38532 (offset 160 lines).
checking file usr/share/perl5/PVE/LXC/Create.pm
Hunk #1 succeeded at 116 (offset 45 lines).
Hunk #2 succeeded at 154 (offset 45 lines).
checking file usr/share/perl5/PVE/QemuServer.pm
Hunk #1 succeeded at 5409 (offset -535 lines).
Hunk #2 succeeded at 5731 (offset -576 lines).
Hunk #3 succeeded at 6059 (offset -574 lines).
checking file usr/share/perl5/PVE/Storage.pm
Hunk #1 succeeded at 519 (offset 7 lines).
Hunk #2 succeeded at 1279 (offset 16 lines).
Hunk #3 succeeded at 1325 (offset 16 lines).
checking file usr/share/perl5/PVE/Storage/Plugin.pm
Hunk #1 succeeded at 432 (offset 9 lines).
Hunk #2 succeeded at 919 (offset 6 lines).
checking file usr/share/perl5/PVE/VZDump/Common.pm
checking file usr/share/perl5/PVE/VZDump.pm
Hunk #1 FAILED at 8.
Hunk #2 succeeded at 627 (offset 43 lines).
Hunk #3 FAILED at 651.
Hunk #4 FAILED at 830.
Hunk #5 FAILED at 842.
Hunk #6 succeeded at 944 with fuzz 1 (offset 91 lines).
4 out of 6 hunks FAILED
checking file usr/share/perl5/PVE/VZDump/LXC.pm
Hunk #1 succeeded at 314 (offset 11 lines).
Hunk #2 succeeded at 409 (offset 46 lines).
checking file usr/share/perl5/PVE/VZDump/QemuServer.pm
Hunk #1 succeeded at 249 (offset 6 lines).
Hunk #2 succeeded at 359 (offset 6 lines).
FAILED to apply!

no changes to the webgui

Hi,
Currently trying to install on 5.4.3 PVE used the patch

bash pve-5.4-5-diff-backup-addon apply

root@prometheus:~/pve-patches# bash pve-5.4-5-diff-backup-addon test
Proxmox VE 5.4-5 - differential backup support, v3
Kamil Trzcinski, http://ayufan.eu/, [email protected]

$ patch_apply / --dry-run --batch
checking file usr/share/pve-manager/js/pvemanagerlib.js
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored
checking file usr/share/perl5/PVE/LXC/Create.pm
Reversed (or previously applied) patch detected!  Skipping patch.
2 out of 2 hunks ignored
checking file usr/share/perl5/PVE/QemuServer.pm
Reversed (or previously applied) patch detected!  Skipping patch.
3 out of 3 hunks ignored
checking file usr/share/perl5/PVE/Storage.pm
Reversed (or previously applied) patch detected!  Skipping patch.
4 out of 4 hunks ignored
checking file usr/share/perl5/PVE/Storage/Plugin.pm
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored
checking file usr/share/perl5/PVE/VZDump.pm
Reversed (or previously applied) patch detected!  Skipping patch.
7 out of 7 hunks ignored
checking file usr/share/perl5/PVE/VZDump/LXC.pm
Reversed (or previously applied) patch detected!  Skipping patch.
2 out of 2 hunks ignored
checking file usr/share/perl5/PVE/VZDump/QemuServer.pm
Reversed (or previously applied) patch detected!  Skipping patch.
2 out of 2 hunks ignored

then i thought it was the version so i updated but first uninstalled the patch then updated to 5.4.13 and reinstall the patch and still no change on the webGUI

Thank you

pve-xdelta3 package version

Hello.

The install doc states we should "latest version of pve-xdelta3" using this command:
dpkg -i pve-xdelta3_3.0.6-1_amd64.deb

The same documentation links to this repo: https://github.com/ayufan/pve-xdelta3
This repo is xdelta3 3.0.11, with lzma support included.

There's quite a difference between the repo (3.0.11) and the deb package (3.0.6, august 2013).

Shouldn't the patch install download the last package?
It's here: https://github.com/ayufan/pve-xdelta3/releases/download/v3.0.11/pve-xdelta3_3.0.11-dfsg-1ubuntu1ayufan1_amd64.deb

And shouldn't the documentation ask to install this package (3.0.11)?

fullbackup property not defined

Hello

I applied for 6.1.3
I got the new menu but impossible to validate because an issue on "Full backup every ..."

any idea

Regards

Proxmox 5.2-4 Issue

Actually it works well, the only problem is that I had to install the patch package manually.

Proxmox 5.1-52 Varient

Is there a way to apply this to 5.1-52?

Cannot see backups in 5.2-10

Hi,
I'm having a problem with the script.
The job run very well, but in the backup section of the backupped vm, there are no differential items displayed, only the last full.
In the backup storage, on the contrary, there are all the right files.

Have you notice this on v 5.2-10?

pve patch for new Proxmox VE 6.1.3

Good morning,
do you have an idea about the release of the patch for last Proxmox VE 6.1.3?
Many tanks in advance
Paolo

pve-patches 6.0-7 aren't compatible with proxmox 6.0-10

# pveversion
pve-manager/6.0-10/337e50bb (running kernel: 5.2.0-73630-g66925f93919a)

# ./pve-6.0-7-diff-backup-addon apply
Proxmox VE 6.0-7 - differential backup support, v3
Kamil Trzcinski, http://ayufan.eu/, [email protected]

checking file usr/share/pve-manager/js/pvemanagerlib.js
Hunk #1 succeeded at 38316 (offset 137 lines).
checking file usr/share/perl5/PVE/LXC/Create.pm
checking file usr/share/perl5/PVE/QemuServer.pm
Hunk #1 succeeded at 5972 (offset -57 lines).
Hunk #2 succeeded at 6335 (offset -57 lines).
Hunk #3 succeeded at 6661 (offset -57 lines).
checking file usr/share/perl5/PVE/Storage.pm
checking file usr/share/perl5/PVE/Storage/Plugin.pm
checking file usr/share/perl5/PVE/VZDump.pm
Hunk #2 FAILED at 170.
Hunk #3 succeeded at 585 (offset -153 lines).
Hunk #4 succeeded at 652 (offset -153 lines).
Hunk #5 succeeded at 858 (offset -153 lines).
Hunk #6 succeeded at 870 (offset -153 lines).
Hunk #7 succeeded at 881 (offset -153 lines).
1 out of 7 hunks FAILED
checking file usr/share/perl5/PVE/VZDump/LXC.pm
Hunk #1 succeeded at 303 (offset 1 line).
Hunk #2 succeeded at 363 (offset 1 line).
checking file usr/share/perl5/PVE/VZDump/QemuServer.pm
Hunk #1 succeeded at 235 (offset -2 lines).
Hunk #2 succeeded at 345 (offset -2 lines).
FAILED to apply!

issue day out of range?

Hi.
Currently getting this issue not sure why?
running proxmox 5.4.5

INFO: starting new backup job: vzdump 101 --storage usb --fullbackup 10 --maxfiles 2 --mailnotification failure --compress lzo --quiet 1 --mailto [email protected] --mode snapshot
ERROR: Backup of VM 101 failed - Day '' out of range 1..31 at /usr/share/perl5/PVE/VZDump.pm line 824.
INFO: Backup job finished with errors

Proxmox 5.3-12 Issue

Hi.
When running "bash pve-5.1-diff-backup-addon apply" i get the following error messages.
What am I doing wrong? Can you helpme with this?

Oct 02 09:50:00 prox-02 systemd[1]: pvesr.service: Main process exited, code=exited, status=255/n/a
Oct 02 09:50:00 prox-02 systemd[1]: Failed to start Proxmox VE replication runner.

Oct 02 09:50:00 prox-02 pvesr[22342]: Compilation failed in require at /usr/bin/pvesr line 6, line 755.
Oct 02 09:50:00 prox-02 pvesr[22342]: BEGIN failed--compilation aborted at /usr/bin/pvesr line 6, line 755.

line 6 says:
use PVE::CLI::pvesr

Not working with latest Proxmox 6.07

oot@prox:/mnt/b/prox-install/pve-patches/pve-patches# bash pve-6.0-5-diff-backup-addon apply
Proxmox VE 6.0-5 - differential backup support, v3
Kamil Trzcinski, http://ayufan.eu/, [email protected]

checking file usr/share/pve-manager/js/pvemanagerlib.js
Hunk #1 succeeded at 37953 (offset 8068 lines).
checking file usr/share/perl5/PVE/LXC/Create.pm
Hunk #1 succeeded at 71 (offset -1 lines).
Hunk #2 succeeded at 109 (offset -1 lines).
checking file usr/share/perl5/PVE/QemuServer.pm
Hunk #1 succeeded at 5960 (offset 618 lines).
Hunk #2 succeeded at 6323 (offset 635 lines).
Hunk #3 succeeded at 6649 (offset 659 lines).
checking file usr/share/perl5/PVE/Storage.pm
Hunk #1 succeeded at 512 (offset 18 lines).
Hunk #2 succeeded at 1263 (offset -71 lines).
Hunk #3 succeeded at 1309 (offset -71 lines).
checking file usr/share/perl5/PVE/Storage/Plugin.pm
Hunk #1 succeeded at 423 (offset 25 lines).
Hunk #2 FAILED at 925.
1 out of 2 hunks FAILED
checking file usr/share/perl5/PVE/VZDump.pm
Hunk #2 succeeded at 170 (offset -2 lines).
Hunk #4 succeeded at 812 (offset 9 lines).
Hunk #5 succeeded at 1018 (offset 2 lines).
Hunk #6 succeeded at 1030 (offset 2 lines).
Hunk #7 succeeded at 1041 (offset 2 lines).
checking file usr/share/perl5/PVE/VZDump/LXC.pm
Hunk #1 succeeded at 302 (offset 6 lines).
Hunk #2 succeeded at 362 (offset 6 lines).
checking file usr/share/perl5/PVE/VZDump/QemuServer.pm
FAILED to apply!
root@prox:/mnt/b/prox-install/pve-patches/pve-patches# uname
Linux
root@prox:/mnt/b/prox-install/pve-patches/pve-patches# uname -r
5.0.21-2-pve

apt install --reinstall "cannot be downloaded

Hello, I have a freshly installed proxmox 6.0-7 running and wanted to install the plugin, and well it failed, so below is that the "fairly straight-forward solution" of reinstalling doesnt seem to work because Reinstallation of qemu-server is not possible, it cannot be downloaded. internet is working though, as the git clone works nicely.

Can't backup CTs

I'm quite new to Proxmox, so perhaps this is not an issue with your delta backup patches - but this is not something I expected, either, so I'm looking for help where I can :-)

This is the output of an attempt at CT backup:

INFO: doing full backup, because no backup found in last 7 day(s)
INFO: Starting Backup of VM 153 (lxc)
INFO: Backup started at 2019-11-05 21:48:53
INFO: status = running
INFO: CT Name: sql-insert
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
INFO: creating archive '/mnt/pve/synology-nfs/dump/vzdump-lxc-153-2019_11_05-21_48_53.tar.gz'
INFO: tar: /mnt/pve/synology-nfs/dump/vzdump-lxc-153-2019_11_05-21_48_53.tmp: Cannot open: Permission denied
INFO: tar: Error is not recoverable: exiting now
INFO: remove vzdump snapshot
ERROR: Backup of VM 153 failed - command 'set -o pipefail && lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar cpf - --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' --one-file-system '--warning=no-file-ignored' '--directory=/mnt/pve/synology-nfs/dump/vzdump-lxc-153-2019_11_05-21_48_53.tmp' ./etc/vzdump/pct.conf ./etc/vzdump/pct.fw '--directory=/mnt/vzsnap0' --no-anchored '--exclude=lost+found' --anchored '--exclude=./tmp/?' '--exclude=./var/tmp/?' '--exclude=./var/run/?.pid' ./ | gzip --rsyncable >/mnt/pve/synology-nfs/dump/vzdump-lxc-153-2019_11_05-21_48_53.tar.dat' failed: exit code 2
INFO: Failed at 2019-11-05 21:48:53

I'm not sure why tar doesn't have permission to create archive for container... VM backups were successful. Is there something I could do to fix this?

Error pve-6.2-4-diff-backup-addon

The patch did not work on the hypervisor installed yesterday:

root@prox1:~/pve-patches# bash pve-6.2-4-diff-backup-addon apply
Proxmox VE 6.2-4 - differential backup support, v3
Kamil Trzcinski, http://ayufan.eu/, [email protected]

checking file usr/share/perl5/PVE/LXC/Create.pm
checking file usr/share/perl5/PVE/QemuServer.pm
checking file usr/share/perl5/PVE/Storage.pm
Hunk #2 succeeded at 1397 with fuzz 2.
Hunk #4 FAILED at 1453.
1 out of 4 hunks FAILED
checking file usr/share/perl5/PVE/Storage/Plugin.pm
checking file usr/share/perl5/PVE/VZDump.pm
checking file usr/share/perl5/PVE/VZDump/Common.pm
checking file usr/share/perl5/PVE/VZDump/LXC.pm
Hunk #1 succeeded at 319 (offset 2 lines).
Hunk #2 succeeded at 414 (offset 2 lines).
checking file usr/share/perl5/PVE/VZDump/QemuServer.pm
checking file usr/share/pve-manager/js/pvemanagerlib.js
FAILED to apply!

Backup work, restore don't work.

Hi,

Nice to see you in github.

Backup is OK, but restore not :

TASK ERROR: file does not look like a template archive: /backups/dump/vzdump-lxc-104-2018_07_25-07_03_02.tar.gz--differential-2018_07_25-07_07_01.vcdiff

Proxmox-5.2 with ZFS file system.

Patch script for 6.1-8 does not work on 6.1-8

checking file usr/share/perl5/PVE/VZDump/QemuServer.pm
Hunk #1 succeeded at 242 with fuzz 2 (offset -7 lines).
Hunk #2 FAILED at 359.
1 out of 2 hunks FAILED

• there's no sub "archive" anymore, instead there are 2 now, looks like some major changes are coming ("Proxmox Backup Server"?)
• patching sub "archive_vma" seems to do the job... still needs some testing

Integrate into Proxmox repo

Why does this not get integrated into the Proxmox repo, so everyone can use this without applying patches :-)

Proxmox 5.4-1 Issue

Hi,

pveproxy will fail to start after applying latest patch.
pveproxy starts normally without applying patch.

Sample output with aptch applied :
systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-04-25 09:12:12 CEST; 13min ago
Main PID: 19852 (code=exited, status=0/SUCCESS)
CPU: 1.298s

Apr 25 09:12:12 pveproxy[8763]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Apr 25 09:12:12 pveproxy[8763]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
Apr 25 09:12:12 pveproxy[8763]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line
Apr 25 09:12:12 pveproxy[8763]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm
Apr 25 09:12:12 pveproxy[8763]: Compilation failed in require at /usr/bin/pveproxy line 11.
Apr 25 09:12:12 pveproxy[8763]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Apr 25 09:12:12 systemd[1]: pveproxy.service: Control process exited, code=exited status=255
Apr 25 09:12:12 systemd[1]: Failed to start PVE API Proxy Server.
Apr 25 09:12:12 systemd[1]: pveproxy.service: Unit entered failed state.
Apr 25 09:12:12 systemd[1]: pveproxy.service: Failed with result 'exit-code'.

Any idea?

Thanks,

Christophe.

Extreme long time issue?

Hi,
Currently did the test before and after and really long without the patches 3 hours and with the patch 26 hours

Proxmox upgrade without revert/uninstall patch

Hi there,

What is a good approach if I did dist-upgrade to another minor upgrade and completely forgotten to revert patches?

THX.

Virtual Environment 4.4-22/2728f613 - No file to patch. Skipping patch.

root@pve03:~/pve-patches# bash pve-4.4-diff-backup-addon apply
Proxmox VE 4.4 - differential backup support, v3
Kamil Trzcinski, http://ayufan.eu/, [email protected]

can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:

|diff --git a/ext6/pvemanagerlib.js b/ext6/pvemanagerlib.js
|index 7a92574..d2bca5b 100644
|--- a/ext6/pvemanagerlib.js
|+++ b/ext6/pvemanagerlib.js

No file to patch. Skipping patch.
1 out of 1 hunk ignored

Installed On PVE But Not Showing "Full Backup Every"

Hey Guys,

Can you please assist?
I installed the software following the guide on one of our cluster servers, but there is no "Full Backup Every" option available.

Do I need to install it on all servers for it to show? Or am I missing something?

Kind Regards

Proxmox 6.0-9 does it work?

HiI would like to use this patch but I have production environment.
Is current version of patch tested on proxmox version 6.0-9?
Thanks for answer

Pve-patches-5.4-5 doesn't work in PVE-5.4-7

Hey all,
I just installed the pve-patch-5.4-5 as it's the last for proxmox ve 5.4-X
The procces just go fine and it's look like is already patched.
But backup in the GUI still sayin that there are just full backups (same size) for each lxc and vm.
the line for vzdump in file /etc/pve/vzdump.cron doesn't have the option --fullbackup
and even the man of vzdump neider talk about it.
So, I was wondering My self what am I doing wrong and how to make the patch work.
thanks in advantage
hector

Full Backup Every entry not shown in WB Gui

Install like description without any errors but the new entry is not shown in the WEB Gui if I add a new backup task.

Proxmox 6.1-3 with the last patch pve-6.1-3-diff-backup-addon and pve-xdelta3_3.0.6-1_amd64.deb.

Any ideas

Helge

Proxmox VE 6.0 Compatibility - Has anyone tried the patches yet on PVE 6?

Since I don't see any issues yet, my guess is it works fine, or no one brave enough to try it yet. Just wondering. :)

Error on 3 nodes Ceph Proxmox 5.3-8 Cluster

Hi,

iam getting this error:

Hunk #5 succeeded at 1016 (offset 1 line).
Hunk #6 succeeded at 1028 (offset 1 line).
Hunk #7 succeeded at 1039 (offset 1 line).
patching file VZDump/LXC.pm
patching file VZDump/QemuServer.pm
PATCHED: /usr/share/perl5/PVE/
Job for pveproxy.service failed because the control process exited with error code.
See systemctl status pveproxy.service and journalctl -xe for details.
Job for pvedaemon.service failed because the control process exited with error code.
See systemctl status pvedaemon.service and journalctl -xe for details.

Output off journalctl -xe:

-- Unit pveproxy.service has begun starting up.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: Global symbol "$uncomp" requires explicit package name (did you forget to declare "my $uncomp"?) at /usr/share/perl5/PVE/QemuServer.pm line 5989, line 755.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: Compilation failed in require at /usr/share/perl5/PVE/QemuConfig.pm line 8, line 755.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/QemuConfig.pm line 8, line 755.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: Compilation failed in require at /usr/share/perl5/PVE/HA/Resources/PVEVM.pm line 10, line 755.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Resources/PVEVM.pm line 17, line 755.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: Compilation failed in require at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 20, line 755.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 20, line 755.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: Compilation failed in require at /usr/share/perl5/PVE/VZDump.pm line 18, line 755.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/VZDump.pm line 18, line 755.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: Compilation failed in require at /usr/share/perl5/PVE/API2/Backup.pm line 15, line 755.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Backup.pm line 15, line 755.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 15, line 755.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 15, line 755.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13, line 755.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13, line 755.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 15, line 755.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 15, line 755.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: Compilation failed in require at /usr/bin/pveproxy line 11, line 755.
Feb 12 19:05:11 pvenode01 pveproxy[9870]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11, line 755.
Feb 12 19:05:11 pvenode01 systemd[1]: pveproxy.service: Control process exited, code=exited status=255
Feb 12 19:05:11 pvenode01 systemd[1]: Failed to start PVE API Proxy Server.
-- Subject: Unit pveproxy.service has failed

Thanks for your help.

Proxmox 5.3 script compatible?

Hi,

Can you update the script to be compatible with the version 5.3 ?

@ayufan

Thank you

Backup is fine, can't restore

Hi,
I've tested it on version 6.05 and now on 6.1.5.
Backups are completely fine.
Restores only work on full backups.
Restores from differentials are throwing this error within 3 seconds:
TASK ERROR: command 'set -o pipefail && pve-xdelta3 -q -d -c -R -s /mnt/pve/BackupNFS/dump/vzdump-qemu-100-2020_01_27-17_27_39.vma.lzo /mnt/pve/BackupNFS/dump/vzdump-qemu-100-2020_01_27-17_27_39.vma.lzo--differential-2020_01_27-17_38_02.vcdiff | vma extract -v -r /var/tmp/vzdumptmp17813.fifo - /var/tmp/vzdumptmp17813' failed: got timeout

The restore was tested from NFS and from local disk. The destinations that were tested: NFS, local disks.
Previous version was 6.0.5 with 6.0.5 patch.
Right now there's 6.1.5 with 6.1.3 patch which was applied without problems.

The error is always the same.
Please assist.

Thank you!

Expected timeframe for 5.2-1 compatible scripts?

Hi there,

Not an issue per se but I just wanted to ask when you might provide packages for 5.2-1.

Thanks

No access web GUI since apply patch 6.1-8 (to) 6.1-11

Now I have version 6.1-11 of Proxmox, but script doesn't work with this newest version.

Hello,

I have a Proxmox version 6.1-8 and git clone the pve-patches, I put "bash pve-5.4-5-diff-backup-addon apply" and I have this return :

root@ns3080769:~/pve-patches# bash pve-5.4-5-diff-backup-addon apply
Proxmox VE 5.4-5 - differential backup support, v3
Kamil Trzcinski, http://ayufan.eu/, [email protected]

checking file usr/share/pve-manager/js/pvemanagerlib.js
Hunk #1 succeeded at 40632 (offset 10747 lines).
checking file usr/share/perl5/PVE/LXC/Create.pm
Hunk #1 succeeded at 116 (offset 44 lines).
Hunk #2 succeeded at 155 (offset 45 lines).
checking file usr/share/perl5/PVE/QemuServer.pm
Hunk #1 succeeded at 5613 (offset 271 lines).
Hunk #2 FAILED at 5688.
Hunk #3 succeeded at 6458 (offset 474 lines).
1 out of 3 hunks FAILED
checking file usr/share/perl5/PVE/Storage.pm
Hunk #1 FAILED at 494.
Hunk #2 FAILED at 780.
Hunk #3 succeeded at 1404 with fuzz 1 (offset 70 lines).
Hunk #4 succeeded at 1450 (offset 70 lines).
2 out of 4 hunks FAILED
checking file usr/share/perl5/PVE/Storage/Plugin.pm
Hunk #1 FAILED at 398.
1 out of 1 hunk FAILED
checking file usr/share/perl5/PVE/VZDump.pm
Hunk #1 FAILED at 8.
Hunk #2 FAILED at 171.
Hunk #3 succeeded at 636 (offset -101 lines).
Hunk #4 FAILED at 795.
Hunk #5 FAILED at 981.
Hunk #6 FAILED at 993.
Hunk #7 succeeded at 953 with fuzz 2 (offset -51 lines).
5 out of 7 hunks FAILED
checking file usr/share/perl5/PVE/VZDump/LXC.pm
Hunk #1 succeeded at 319 (offset 23 lines).
Hunk #2 succeeded at 414 (offset 58 lines).
checking file usr/share/perl5/PVE/VZDump/QemuServer.pm
Hunk #1 succeeded at 243 with fuzz 2 (offset 6 lines).
Hunk #2 FAILED at 347.
1 out of 2 hunks FAILED
FAILED to apply!

My VMs work but, now I can't access to my web manager, and pve-proxy fail...

root@ns3080769:~/pve-patches# pveproxy start
unknown file 'priv/acme/plugins.cfg' at /usr/share/perl5/PVE/Cluster.pm line 474.
Compilation failed in require at /usr/share/perl5/PVE/API2/ACMEAccount.pm line 13.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/ACMEAccount.pm line 13.
Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 23.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 23.
Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 14.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 14.
Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 16.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 16.
Compilation failed in require at /usr/bin/pveproxy line 11.
BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.

Please help.

Best regards,
DECIGrade

Not working anymore?

Hey guys,

Ok so the updates were working well. Untill now I tried updating the addon, but when I run apply I get the below message, and I am not seeing the "Full Backup Every" option anymore...

root@c3:~/pve-patches# ./pve-6.1-8-diff-backup-addon apply
Proxmox VE 6.1-8 - differential backup support, v3
Kamil Trzcinski, http://ayufan.eu/, [email protected]

checking file usr/share/pve-manager/js/pvemanagerlib.js
Hunk #1 succeeded at 40632 (offset 2100 lines).
checking file usr/share/perl5/PVE/LXC/Create.pm
Hunk #2 succeeded at 155 (offset 1 line).
checking file usr/share/perl5/PVE/QemuServer.pm
Hunk #1 succeeded at 5613 (offset 204 lines).
Hunk #2 FAILED at 5731.
Hunk #3 succeeded at 6458 (offset 405 lines).
1 out of 3 hunks FAILED
checking file usr/share/perl5/PVE/Storage.pm
Hunk #1 FAILED at 519.
Hunk #2 succeeded at 1404 with fuzz 1 (offset 125 lines).
Hunk #3 succeeded at 1450 (offset 125 lines).
1 out of 3 hunks FAILED
checking file usr/share/perl5/PVE/Storage/Plugin.pm
Hunk #1 FAILED at 432.
Hunk #2 FAILED at 919.
2 out of 2 hunks FAILED
checking file usr/share/perl5/PVE/VZDump.pm
Hunk #2 succeeded at 638 (offset 9 lines).
Hunk #3 succeeded at 727 (offset 9 lines).
Hunk #4 succeeded at 949 (offset 9 lines).
Hunk #5 succeeded at 965 (offset 9 lines).
Hunk #6 succeeded at 983 with fuzz 2 (offset 9 lines).
checking file usr/share/perl5/PVE/VZDump/Common.pm
Hunk #1 succeeded at 210 (offset 7 lines).
checking file usr/share/perl5/PVE/VZDump/LXC.pm
Hunk #1 succeeded at 319 (offset 5 lines).
Hunk #2 succeeded at 414 (offset 5 lines).
checking file usr/share/perl5/PVE/VZDump/QemuServer.pm
Hunk #1 succeeded at 243 with fuzz 2 (offset -6 lines).
Hunk #2 FAILED at 359.
1 out of 2 hunks FAILED
FAILED to apply!

Question for you Kamil..

Big fan, your patches are a huge improvement to proxmox backup system and hugely appreciated.

My question is, for your own use, how many differential backups do you use before taking a new full backup, personally?

I understand the risk that each previous differential file is need to restore a machine up till the point one wishes to restore to, but if each diff backup (as well as the initial full) is backed up and securely stored (zfs) as well, is it feasible to do 1 full per year? What do you personally do?

Performance

Can we do something about the performance?
Currently we use a CIFS/SMB volume via a 1Gbit/s interface.
A full backup for a medium sized VM needs about 2mins whereas it needs about 30mins to finish using xdelta3.

INFO: status: 70% (15040643072/21474836480), sparse 25% (5543481344), duration 1478, read/write 6/5 MB/s

As xdelta3 is only able to use one thread combined with a medium compression this is probably the bottleneck.

Installation error for Proxmox 6.2 on Debian Core

I do not use the proxmox iso and install proxmox from repo on top of debian 10.
Follow your advices for installation. After install

pve-xdelta3_3.0.11-dfsg-1ubuntu1.zstd.ayufan2_amd64.deb

I repeat

bash pve-6.1-8-diff-backup-addon apply

then came output:

root@intel-server:~/pve-patches# bash pve-6.1-8-diff-backup-addon apply

Proxmox VE 6.1-8 - differential backup support, v3
Kamil Trzcinski, http://ayufan.eu/, [email protected]

checking file usr/share/pve-manager/js/pvemanagerlib.js
Hunk #1 succeeded at 41663 (offset 3131 lines).
checking file usr/share/perl5/PVE/LXC/Create.pm
Hunk #2 succeeded at 155 (offset 1 line).
checking file usr/share/perl5/PVE/QemuServer.pm
Hunk #1 succeeded at 5621 (offset 212 lines).
Hunk #2 FAILED at 5731.
Hunk #3 succeeded at 6469 (offset 416 lines).
1 out of 3 hunks FAILED
checking file usr/share/perl5/PVE/Storage.pm
Hunk #1 FAILED at 519.
Hunk #2 succeeded at 1404 with fuzz 1 (offset 125 lines).
Hunk #3 FAILED at 1325.
2 out of 3 hunks FAILED
checking file usr/share/perl5/PVE/Storage/Plugin.pm
Hunk #1 FAILED at 432.
Hunk #2 FAILED at 919.
2 out of 2 hunks FAILED
checking file usr/share/perl5/PVE/VZDump.pm
Hunk #2 succeeded at 640 (offset 11 lines).
Hunk #3 FAILED at 718.
Hunk #4 succeeded at 922 with fuzz 2 (offset 11 lines).
Hunk #5 succeeded at 938 with fuzz 2 (offset 11 lines).
Hunk #6 succeeded at 956 with fuzz 2 (offset 11 lines).
1 out of 6 hunks FAILED
checking file usr/share/perl5/PVE/VZDump/Common.pm
Hunk #1 succeeded at 210 (offset 7 lines).
checking file usr/share/perl5/PVE/VZDump/LXC.pm
Hunk #1 succeeded at 317 (offset 3 lines).
Hunk #2 succeeded at 412 (offset 3 lines).
checking file usr/share/perl5/PVE/VZDump/QemuServer.pm
Hunk #1 succeeded at 243 with fuzz 2 (offset -6 lines).
Hunk #2 FAILED at 359.
1 out of 2 hunks FAILED
FAILED to apply!

Can you explain what happend?

Patch not workink on Proxmox 6.0-11

root@pve:~/pve-patches# bash pve-6.0-7-diff-backup-addon apply
Proxmox VE 6.0-7 - differential backup support, v3
Kamil Trzcinski, http://ayufan.eu/, [email protected]

checking file usr/share/pve-manager/js/pvemanagerlib.js
Hunk #1 succeeded at 38372 (offset 193 lines).
checking file usr/share/perl5/PVE/LXC/Create.pm
checking file usr/share/perl5/PVE/QemuServer.pm
Hunk #1 succeeded at 5944 (offset -85 lines).
Hunk #2 succeeded at 6307 (offset -85 lines).
Hunk #3 succeeded at 6633 (offset -85 lines).
checking file usr/share/perl5/PVE/Storage.pm
checking file usr/share/perl5/PVE/Storage/Plugin.pm
checking file usr/share/perl5/PVE/VZDump.pm
Hunk #2 FAILED at 170.
Hunk #3 succeeded at 585 (offset -153 lines).
Hunk #4 succeeded at 652 (offset -153 lines).
Hunk #5 succeeded at 858 (offset -153 lines).
Hunk #6 succeeded at 870 (offset -153 lines).
Hunk #7 succeeded at 881 (offset -153 lines).
1 out of 7 hunks FAILED
checking file usr/share/perl5/PVE/VZDump/LXC.pm
Hunk #1 succeeded at 303 (offset 1 line).
Hunk #2 succeeded at 363 (offset 1 line).
checking file usr/share/perl5/PVE/VZDump/QemuServer.pm
Hunk #1 succeeded at 243 (offset 6 lines).
Hunk #2 succeeded at 353 (offset 6 lines).
FAILED to apply!

Excessively large diffs

Hi ayufan,

first of all, thanks for your great contribution!
Currently, I am testing your patches for my home server / lab.

What makes me wonder is, that the diffs vary depending on the vm type depending their size.

E.g. an LXC container holding a db and some data results in megabytes up to some gigabytes while a Windows VM running as file server with ~200gb of data results in a diff of ~100gb size after a day without many changes. Qemu agent seems to run, as I can ping the VM without errors.
Is there another aspect I could have a closer look on to remedy this circumstance?

Thanks in advance!

PVE 5.2-2

Error on 5.4-3

ERROR: Backup of VM 102 failed - Day '' out of range 1..31 at /usr/share/perl5/PVE/VZDump.pm line 824.
INFO: stat: missing operand
INFO: Try 'stat --help' for more information.

Full backup set to every 7, with Max Backups set to 14

Installation problems

There is a problem with the installation. PVE is 5.4-3`bash pve-5.4-5-diff-backup-addon apply
Proxmox VE 5.4-5 - differential backup support, v3
Kamil Trzcinski, http://ayufan.eu/, [email protected]

checking file usr/share/pve-manager/js/pvemanagerlib.js
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored
checking file usr/share/perl5/PVE/LXC/Create.pm
Reversed (or previously applied) patch detected! Skipping patch.
2 out of 2 hunks ignored
checking file usr/share/perl5/PVE/QemuServer.pm
Reversed (or previously applied) patch detected! Skipping patch.
3 out of 3 hunks ignored
checking file usr/share/perl5/PVE/Storage.pm
Reversed (or previously applied) patch detected! Skipping patch.
4 out of 4 hunks ignored
checking file usr/share/perl5/PVE/Storage/Plugin.pm
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored
checking file usr/share/perl5/PVE/VZDump.pm
Reversed (or previously applied) patch detected! Skipping patch.
7 out of 7 hunks ignored
checking file usr/share/perl5/PVE/VZDump/LXC.pm
Reversed (or previously applied) patch detected! Skipping patch.
2 out of 2 hunks ignored
checking file usr/share/perl5/PVE/VZDump/QemuServer.pm
Reversed (or previously applied) patch detected! Skipping patch.
2 out of 2 hunks ignored
FAILED to apply!
`

Exclude disk from VM backup

I have scheduled proxmox backup job which runs fine. I have a vm which has additional disk from another hard drive. I want to exclude that from the backup. Is there is any way I can define exclude disk option?

INFO: trying to get global lock - waiting...
INFO: got global lock
INFO: starting new backup job: vzdump 132 --node proxmox --storage ONETB --mode snapshot --remove 0 --compress lzo --mailto [email protected]
INFO: Starting Backup of VM 132 (qemu)
INFO: Backup started at 2020-05-13 23:35:17
INFO: status = running
INFO: update VM 132: -lock backup
INFO: VM Name: zoneminder
INFO: include disk 'scsi1' 'ONETB:132/vm-132-disk-0.raw' 200G
INFO: include disk 'virtio0' 'ONETB:132/vm-132-disk-1.qcow2' 32G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/pve/ONETB/dump/vzdump-qemu-132-2020_05_13-23_35_17.vma.lzo'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task '9d652773-b4c2-4dd6-9979-bc0b02fe104c'

In this case, I want to exclude 200G disk vm-132-disk-0.raw from backing up. I dont have enough space to take regular backup nor it is super critical data to backup however, I want to ensure OS disk is backed up and I can restore the vm in case of disaster.

Thanks.

Abhishek