I have just started to test Urbackup and am so far loving it. I am having an issue with the full image backups on windows 7 machines, and I suspect server 2008 as well. When I do a full image backup the main partitions are backing up correctly but the system recovery partition which is the system and active partition is not backing up. The size of the sysvol_ files is 0.
I started out using the 32 bit version 1.2.1 server and just switched today to 1.2.1 64bit. The sysvol files are 0 size with both.
Client version is 1.2
Here is the log info for the backup:
Starting full image backup…
Request of SYSVOL failed. Reason: Opening filesystem on device failed. Stopping.
Transferred 4.08691 KB - Average speed: 33.48 MBit/s
Transferred 73.6681 GB - Average speed: 406.911 MBit/s
Time taken for creating image of client Mstarcevic-Laptop: 25m 55s
This usually just means, that the client does not have the “System reserved” restore volume (called SYSVOL in UrBackup). That’s why it is probably an Info-level log message.
With regards to the zero sized files… They should be cleaned up during the cleanup.
I will add more info to the log message and think about removing the file directly.
Problem is that the client system really does have the “recovery” partition and test restores do not restore it, (restoring to a blank hard drive). Consequentially, the disk will not boot. I get the “missing operating system” message during boot.
Here is the results of running sysvol_test.exe:
INFO: Found no SYSVOL on the same physical device as ‘C’.
No sysvolume found.
Trying to open SYSVOL()…
Could not open SYSVOL(). Last error=3
In order to rule out the OEM partition I removed it and shifted the partitions to line up with the beginning of the drive. Full image still didn’t backup the Restore volume.
DEBUG: Filesystem. Vol="\?\Volume{14e3d04e-bf1c-11e2-baa1-806e6f6e6963}" Name=
“recovery” Type=“ntfs” VPaths=0 Size=13703282688
DEBUG: Filesystem. Vol="\?\Volume{96d65aac-bf1c-11e2-91e7-806e6f6e6963}" Name=
“os” Type=“ntfs” VPaths=1 Size=114327805952
DEBUG: Filesystem. Vol="\?\Volume{da830951-eb2a-11e1-9843-806e6f6e6963}" Name=
“” Type="" VPaths=1 Size=0
INFO: Found no SYSVOL on the same physical device as ‘C’.
No sysvolume found.
Trying to open SYSVOL()…
Could not open SYSVOL(). Last error=3
UrBackup uses some heuristics to find the system restore volume. It looks for NTFS-volumes which…
…have the name “system reserved”, or
…are smaller than 200MB and not mounted (e.g. have a drive letter assigned)
I’ll have to think about how to improve this. In your case, you could rename the volume to “system reserved”. UrBackup does not brother to do incrementals of this volumes, since it assumes it is a small volume.
Removed the restore image out of the restore partition, re-sized it down to the minimum size which was about 120 meg, and renamed it to “system reserved”. Then I performed a full image backup and it correctly backed up the sysvol partition. Although this did work in my case, I would hate to have to do this for all of our pcs that have the restore partition. I hope you can find a more flexible way to deal with the sysvol partition as I would image many of our Dell’s will have this type of setup.
Can you run the sysvol_test with the debug info on one such “vanilla” install, or did you run it on one? That may help me develop a strategy for finding the “system reserved” volumes.
This was the sysvol_test from before I adjusted the partitions:
DEBUG: Filesystem. Vol="\?\Volume{14e3d04e-bf1c-11e2-baa1-806e6f6e6963}" Name=
“recovery” Type=“ntfs” VPaths=0 Size=13703282688
DEBUG: Filesystem. Vol="\?\Volume{96d65aac-bf1c-11e2-91e7-806e6f6e6963}" Name=
“os” Type=“ntfs” VPaths=1 Size=114327805952
DEBUG: Filesystem. Vol="\?\Volume{da830951-eb2a-11e1-9843-806e6f6e6963}" Name=
“” Type="" VPaths=1 Size=0
INFO: Found no SYSVOL on the same physical device as ‘C’.
No sysvolume found.
Trying to open SYSVOL()…
Could not open SYSVOL(). Last error=3
This is the sysvol_test after I adjusted the partitions:
DEBUG: Filesystem. Vol="\?\Volume{7b88274e-c257-11e2-bb8d-806e6f6e6963}" Name=
“system reserved” Type=“ntfs” VPaths=0 Size=131567616
DEBUG: Found potential candidate: \?\Volume{7b88274e-c257-11e2-bb8d-806e6f6e696
3}
DEBUG: Filesystem. Vol="\?\Volume{2d27584b-c258-11e2-9a0e-806e6f6e6963}" Name=
“os” Type=“ntfs” VPaths=1 Size=127899521024
DEBUG: Filesystem. Vol="\?\Volume{da830951-eb2a-11e1-9843-806e6f6e6963}" Name=
“” Type="" VPaths=1 Size=0
DEBUG: Selected: \?\Volume{7b88274e-c257-11e2-bb8d-806e6f6e6963}
Found sysvol “\?\Volume{7b88274e-c257-11e2-bb8d-806e6f6e6963}” Path: “”
Trying to open SYSVOL(\?\Volume{7b88274e-c257-11e2-bb8d-806e6f6e6963})…
Successfully opened SYSVOL.
In my bare metal restore to a spare hard drive I still got the missing OS error. I haven’t had a chance yet to take a look at the partitions in a partition editor.
Looked at the partitions on my restore test drive.
Drive contains 2 partitions just as my original drive in the correct sizes.
First partition is 125Mbytes just as my original but the format is Raw and contains no data.
Second partition is labeled System Reserved and is the same size as my original C drive but contains the boot files that should be on the sysvol partition.
So, it restored the sysvol partition where C should be and didn’t restore C at all.
I was restoring with Ver .3 CD as the version 1.0 will not boot up properly on my laptop, (Not unusual for my laptop to have issues with Linux Live CDs).
Can you send me the “.mbr” file of the backup (martin@urbackup.org). That way I can see the partition layout.
With regards to the recovery parition. I’m a bit confused. The 13GB partition is the recovery partition from the manufacurer, right? So what is the boot partition… I’ll see that in the .mbr file as well, btw. (bootable flag).
In reguards to the partition sizes: Originally my Dell laptop contained a small 34meg OEM partition that was in a special format and contained Dell diagnostics. The next partition contained not only the Win 7 boot partition but also a Dell Factory image, the partition size was 13Gig, and it’s name was “Recovery”. The last partition was the C drive and the remaining drive space.
What I did to get a successful Sysvol backup was remove the OEM partition, remove the factory image files out of the Boot partition, rename the partition to “System Reserved” and reduce the Boot partition down to the minimum size (about 137Meg). I also resized C to it’s maximum size, (it’s a 128gig SSD and I could use the extra space).
So, in regards to your question, the Factory Restore partition was also the Win 7 boot partition, it was named “Recovery” and not the usual size.