We are live - Windows 10 support with VEB 1.1

[Mike Resseler]

Hi all,

As you might have seen by the latest responses of Dima P., we are live with VEB 1.1

You can read everything here: http://www.veeam.com/blog/new-veeam-end ... pport.html

Go grab the new bits and upgrade

[Dima P.]

and don’t forget to rate the blogpost

[hoFFy]

Sounds good! Installing right now!

[Dima P.]

Sebastian,
Great! We are awaiting for a feedback

[hoFFy]

Upgrade has been no Problem,
but yesterday, with VEB 1.0 I tried to restore my system into a VM and came across this error:




This persists in 1.1

I have to say that I'm using storage spaces with two disks as a RAID 1. Is this configuration not supported? Yeterday, after ignoring the message, the disk has been unreadable.

Now I'm doing a restore with 1.1 but I believe the result will be the same.
What seems to work ( I have to wait until restore finishes) is the shrinking of partitions... great!

[Dima P.]

What seems to work ( I have to wait until restore finishes) is the shrinking of partitions... great!

Glad to hear!

Yesterday, after ignoring the message, the disk has been unreadable.

It looks like a sector size difference issue: the backed up disk has one logical sector size while the existing disk has another. Open the case and share the recovery logs please, meanwhile I'll ask QA team to take a look.

[hoFFy]

I had to do some more testing... at the end of restore I received an error message that the the size after shrinking is under the minimum size. I'm not sure if this error came from the disk with the different sector size, or if it comes from my system partition.... but I tried the following now: Added another virtual disk (95GB ) and chose to map the disks manually: VEB doesn't complain when I tried to restore my system partition containing 109GB data (not overall disk space) onto a disk with 95GB... it just starts restoring

[Dima P.]

Is that a VMware VM or Hyper-V? With the last you can adjust the disk sector size… Still want a case from you

[wsususer]

I have made a Backup (Inc) with the new VEB 1.1
My System has the German Language.

click on details:
VEB 1.0
29.07.2015 19:15:05 :: System-reserviert (disk 0) (350,0 MB) 37,0 MB read at 37 MB/s [CBT]
29.07.2015 19:15:06 :: Lokaler Datenträger (C:) (100,0 GB) 12,3 GB read at 70 MB/s [CBT]
Lokaler Datenträger (C:)

VEB 1.1 --> last Backup
04.08.2015 21:03:42 :: System-reserviert (disk 0) (350,0 MB) 37,0 MB read at 37 MB/s [CBT]
04.08.2015 21:03:42 :: Lokaler Datenträger (C:) (100,0 GB) 8,6 GB read at 90 MB/s [CBT]
Lokaler Datenträger (C:)
small translation error ?

[lowlander]

Hi,

we upgraded some systems from Windows 8.1 to 10. Before installing VEB 1.1 we removed the old 1.0 binaries. Seems to be that the database is not created during install of 1.1, resulting in a VEB service that won't start. Created a ticket #00985690

[lowlander]

It turned out to be an NTFS security issue, that was caused by the upgrade process. We repaired this by taking over security settings of a clean Windows 10 machine. After that we installed VEB 1.1 and it asked us to reboot. Applying the steps listed below fixed the issue on advise of Veeam support.

1. Open up RegEdit
2. Look for HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint
3. Create new DWORD value called ReCreateDatabase and assign to it 1 (decimal)
4. Start Endpoint service manually or just reboot your pc.
5. If Endpoint started successfully, delete created key.

thanks !

[Gostev]

Thanks all - very much appreciated. Please do keep these minor issues coming, so that we can address them with the micro-update before putting 1.1 on our auto-update servers.