According to dpkg.log, starting with 1.4.14 upgraded to 2.0.21 :
2016-05-20 17:22:17 status half-installed urbackup-server:amd64 1.4.14.1402-1
2016-05-20 17:22:18 status unpacked urbackup-server:amd64 2.0.21.0
All images backups i’ve done are FULL backups.
The last good restore i am able to do is with this full image backup :
root@urbackup1:~# ll /media/backup/urbackup/SV54/
total 27557764
drwxr-xr-x 1 urbackup urbackup 216 mai 20 21:18 160520-1805_Image_C
drwxr-xr-x 1 urbackup urbackup 256 mai 20 18:05 160520-1805_Image_SYSVOL
The backup was made with server version 2.0.21 and associate client without CBT (don’t remember the version at this moment …)
I didn’t test all of them but If you want have others backups that i can try :
root@urbackup1:~# ll /media/backup/urbackup/SV54/
total 27557764
drwxr-xr-x 1 urbackup urbackup 216 mai 20 21:18 160520-1805_Image_C
drwxr-xr-x 1 urbackup urbackup 256 mai 20 18:05 160520-1805_Image_SYSVOL
drwxr-xr-x 1 urbackup urbackup 256 mai 21 14:26 160521-1425_Image_SYSVOL
drwxr-xr-x 1 urbackup urbackup 216 mai 21 16:54 160521-1426_Image_C
drwxr-xr-x 1 urbackup urbackup 278 mai 22 15:12 160522-1159_Image_C
drwxr-xr-x 1 urbackup urbackup 328 mai 22 11:59 160522-1159_Image_SYSVOL
drwxr-xr-x 1 urbackup urbackup 278 mai 23 16:20 160523-1343_Image_C
drwxr-xr-x 1 urbackup urbackup 328 mai 23 13:43 160523-1343_Image_SYSVOL
drwxr-xr-x 1 urbackup urbackup 278 mai 27 21:11 160527-1816_Image_C
drwxr-xr-x 1 urbackup urbackup 328 mai 27 18:16 160527-1816_Image_SYSVOL
drwxr-xr-x 1 urbackup urbackup 278 juin 3 13:39 160603-1023_Image_C
drwxr-xr-x 1 urbackup urbackup 328 juin 3 10:23 160603-1023_Image_SYSVOL
drwxr-xr-x 1 urbackup urbackup 328 juin 17 14:52 160617-1451_Image_SYSVOL
drwxr-xr-x 1 urbackup urbackup 278 juin 17 18:30 160617-1452_Image_C
drwxr-xr-x 1 urbackup urbackup 278 juin 20 12:08 160620-1123_Image_C
drwxr-xr-x 1 urbackup urbackup 328 juin 20 11:23 160620-1123_Image_SYSVOL
drwxr-xr-x 1 urbackup urbackup 278 juin 21 18:56 160621-1822_Image_C
drwxr-xr-x 1 urbackup urbackup 328 juin 21 18:22 160621-1822_Image_SYSVOL
drwxr-xr-x 1 urbackup urbackup 328 juin 22 16:03 160622-1602_Image_SYSVOL
drwxr-xr-x 1 urbackup urbackup 278 juin 22 16:34 160622-1603_Image_C
The latest 20/21/22 June doesn’t work, i.e VM doesnt boot after restore.
I move to CBT client with version 2.0.25-cbt (with server 2.0.26 or 27)
BTW, i’ve made an other image restore test of a Windows 2012 R2 VM backed up with the same server also in CBT mode and it works great, maybe an issue with this particular VM / OS version (Windows 2008 R2 vs Windows 2012 R2) ?
EDIT : Forget this, it was with a VM backed up without CBT client …
In fact you are right, only the last “real” full backup is restoring correctly, others were “full” but in fact “incremental” due to the “synthetic full image backup” setting …
Restoring full client image from an image backup made with 2.0.29 doesn’t work.
But restoring the first real full backup made with 2.0.21 and then restoring the last full (but in fact incremental due to the “synthetic full image backup” setting) image backup made with 2.0.29 works.
All others restoration i’ve test failed on VM reboot …
Maybe i should try to remove all images backups for this client with a cleanup, restart a full + an incremental and then try to restore ?
By the way, It would be nice to integrate this functionnality directly from the web GUI, i.e the ability to browse the content of image volumes and to extract files from GUI.
Are there plans to integrate this functionnality soon ?
Yes, it would be difficult to do this consistently with VHDZ on Windows, though. And I have to fix existing bugs. Currently I am testing image backups, haven’t found (i.e. reproduced) any issue yet, though.
Restoration works fine now.
I’ve deleting all client backups, made a new full image backup, then an incremental, and restore the incremental.
VM is booting properly after the restore.