Recovery: total disaster (1.5.0.306), Case # 01818507

Backup agent for Microsoft Windows servers and workstations (formerly Veeam Endpoint Backup FREE)

Recovery: total disaster (1.5.0.306), Case # 01818507

Veeam Logoby Erhard » Mon Jun 06, 2016 7:03 am

Hello,

on Friday June 3rd we had to perform a recovery for one of our customers because he had caught himself a crypto virus.

We booted the recovery CD we had created on the very same PC using the option to include drivers.

Unfortunately it seems that "include hardware drivers from this computer (recommended" had not worked, because we could not use USB keyboard or USB mouse.

So we reverted to a PS/2 keyboard which did work, but it was not very comfortable to work without a mouse.

Then we had to notify that we could not access USB hard drives which was a bit disturbing, because the backups resided on such drives.

So we got the hard drives out of their USB cases and connected them via S-ATA, still working without mouse, than you very much.

Recovery started - but it resulted in a failure because it could not access some file.

We investigated everything: the new drives had been partitioned and had got the GUID from the backup. The backup file seemed okay.

We started recovery againg because it might have been that Veeam did not know about the newly created partitions and that thing might work with pre-partitioned drives - well, it did not.

So we installed the original drives where Veeam Endpoint Backup was installed running windows so we had working keyboard, working mouse and working USB drives.

We connected the new drives via USB, but hey - Veeam Endpoint backup seems to dislike USB drives as a recovery destination.

Well, I have to tell you that I strongly dislike Veeam as well. You should put that procedure in a commercial to advertise Veeam. Potential customers will be overwhelmed from the ease of product usage, won't they?

However we ended up performing a multi-volume restore running windows from the original drives to new S-ATA drives and performing a row of repair actions afterwards to get the restored drives bootable.

I can hardly tell you how grateful I am: the recovery should have taken minutes, an hour for all systems in total but it ended up in 6 hours, part of those being my spare time.

The recovery boot medium requires a serious review in my opinion.

(Btw, we tried to call Veeam Support but got blocked because Veeam Endpoint Backup support is only provided via the website. But when things are urgent and time is running fast ....)

Considering the fact that we sold Veeam B&R to almost every customer of ours I now have to thing about something: do we trust in Veeam because it is so good - or do we trust in Veeam because others are even worse?

Well, one more thing: typing all this stuff the forum timed-out in the background and when I tried to submit things, everything got lost. Fortunately I had been so clever to backup my text to notepad before ...

CU, Erhard
Erhard
Novice
 
Posts: 6
Liked: never
Joined: Mon Jun 06, 2016 5:57 am
Full Name: Erhard Pütz

Re: Recovery: total disaster (1.5.0.306), Case # 01818507

Veeam Logoby Dima P. » Tue Jun 07, 2016 9:29 pm

Hi Erhard,

Sorry to hear that you have negative experience with recovery media. Can you elaborate how your USB mouse was connected (directly or via usb hub) and what device you were restoring? If it’s a laptop – can you share the model? Also on what operating system recovery media was created? Thanks.
Dima P.
Veeam Software
 
Posts: 6227
Liked: 439 times
Joined: Mon Feb 04, 2013 2:07 pm
Location: SPb
Full Name: Dmitry Popov

Re: Recovery: total disaster (1.5.0.306), Case # 01818507

Veeam Logoby Gostev » Sun Jun 12, 2016 9:12 pm

Perhaps you are restoring to some uncommon hardware that our Recovery Media does not yet support today. We will be more than happy to investigate this for you because we're very much interested in enhancing its compatibility. This way, we can make sure you don't have issues performing similar recoveries in future!

Erhard wrote:Considering the fact that we sold Veeam B&R to almost every customer of ours I now have to thing about something: do we trust in Veeam because it is so good - or do we trust in Veeam because others are even worse?

This part is confusing. Your post above seems to be talking about Veeam Endpoint Backup (new free product with no official support), however in this comment you suddenly switch to Veeam Backup & Replication (9 year old commercial product with full support). Can you confirm what product are you having the issue with?
Gostev
Veeam Software
 
Posts: 21385
Liked: 2348 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: Recovery: total disaster (1.5.0.306), Case # 01818507

Veeam Logoby cdeviney » Sun Jun 12, 2016 10:55 pm

I had similar results using Veeam Endpoint (free).

I had to use 'bare metal recovery', 'local storage', 'entire computer', 'restore'...as best that I can recall.
cdeviney
Lurker
 
Posts: 1
Liked: never
Joined: Wed Mar 09, 2016 6:21 pm
Full Name: Cathy DeViney

Re: Recovery: total disaster (1.5.0.306), Case # 01818507

Veeam Logoby Delo123 » Mon Jun 13, 2016 7:09 am

Maybe all the USB Ports were USB3.0 like the new Intel NUCS? Anyone know if they are supported yet?
Delo123
Expert
 
Posts: 348
Liked: 94 times
Joined: Fri Dec 28, 2012 5:20 pm
Full Name: Guido Meijers

Re: Recovery: total disaster (1.5.0.306), Case # 01818507

Veeam Logoby rreed » Mon Jun 13, 2016 1:22 pm

I backup my home laptop to USB HDD - and had to recover it - both w/o issue. Works fine. Approx. 4-5 year old Dell, I think Toshiba USB HDD less than a year old.

If you need PS/2 keyboard, sounds like quite legacy hardware. Good point on USB hub, typically when you get down to very base drivers/BIOS, things won't be seen on the other side of a USB hub. Go direct, and if one doesn't work, try another.
VMware 6
Veeam B&R v9
Dell DR4100's
EMC DD2200's
EMC DD620's
Dell TL2000 via PE430 (SAS)
rreed
Expert
 
Posts: 354
Liked: 72 times
Joined: Tue Jun 30, 2015 6:06 pm

Re: Recovery: total disaster (1.5.0.306), Case # 01818507

Veeam Logoby kapple » Mon Jun 13, 2016 1:58 pm 1 person likes this post

Veeam Endpoint Backup worked flawlessly for me when the hard drive in my laptop died. Yes, I use a wireless USB mouse/keyboard as well.
kapple
Influencer
 
Posts: 22
Liked: 2 times
Joined: Thu Jun 14, 2012 7:13 pm
Location: Rochester, NY
Full Name: Ken Applebaum

Re: Recovery: total disaster (1.5.0.306), Case # 01818507

Veeam Logoby mkaec » Mon Jun 13, 2016 2:17 pm 1 person likes this post

Erhard wrote:So we reverted to a PS/2 keyboard which did work, but it was not very comfortable to work without a mouse.

At my college job, a PC came in for installation to the residential network and we did not have a mouse that worked with it. This incident quickly identified which technicians would go on to be senior technicians. :)

Erhard wrote:Considering the fact that we sold Veeam B&R to almost every customer of ours I now have to thing about something: do we trust in Veeam because it is so good - or do we trust in Veeam because others are even worse?

I imagine it is a little of both. I think Veeam products are good, but that baseline has been very low for a long time.
mkaec
Expert
 
Posts: 178
Liked: 48 times
Joined: Thu Jul 16, 2015 1:31 pm
Full Name: Marc K

Re: Recovery: total disaster (1.5.0.306), Case # 01818507

Veeam Logoby ddayton » Mon Jun 13, 2016 2:29 pm 1 person likes this post

Each variation of vendor/model desktop and laptop i have deployed with Veeam Endpoint Backup (EPB) I have always created the boot media and tested booting it and in most cases went through a trial backup and restore. I avoid USB 3.0 ports when doing a bare metal restore because the 3.0 hardware typically takes special drivers. I have had only one model of an HP desktop that the USB mouse and keyboard did not work, but fortunately the desktop also had PS/2 for both. I would be afraid to attempt using a USB drive on such a desktop for the backup media, but in my case all of my EPB's target B&R repositories at work and that is over the network. I have successfully retored three of these desktops from a full backup. At home I also use EPB and there I use an external USB hard drive (WD 2TB) and I have successfuly restored my wife's HP Envy laptop that was running Windows 8.1. I have used other products that cost plenty of money that claim bare metal restore and it really depends on how well WinPE supports the hardware because they didn't work in all cases either. EPB is a great free tool, but it is up to us to test and verify our installations and take some of the responsibility.
:)
ddayton
Enthusiast
 
Posts: 31
Liked: 10 times
Joined: Mon Nov 12, 2012 6:40 pm
Full Name: Don Dayton

Re: Recovery: total disaster (1.5.0.306), Case # 01818507

Veeam Logoby rockandroller » Mon Jun 13, 2016 4:31 pm 1 person likes this post

I recently restored via 'EPB' to an older machine we keep up in the ceiling, booting from USB restore key in a USB hub at the end of a long active USB extension (wireless mouse and keyboard dongle was also in the same hub).
I was very pleased at the performance, restoring from a network share.
rockandroller
Novice
 
Posts: 5
Liked: 1 time
Joined: Wed Feb 11, 2015 1:03 am
Full Name: Michael Walker

Re: Recovery: total disaster (1.5.0.306), Case # 01818507

Veeam Logoby Dima P. » Mon Jun 13, 2016 4:55 pm 1 person likes this post

USB 3.0 indeed requires additional driver - otherwise it operates as USB 2.0 (might require enabling 3.0 support in BIOS sometimes). Regarding the recovery media, drivers are either collected during its creation (it case you used the collect drivers option which is checked by default) or it can be installed manually during recovery via Load Drivers utility.

Hidden gem #1: you can use only keyboard during BMR as regular Microsoft ‘tab and arrows’ keys are fully supported
Hidden gem #2: you can use touch screen (but that again requires drivers to be collected)
Dima P.
Veeam Software
 
Posts: 6227
Liked: 439 times
Joined: Mon Feb 04, 2013 2:07 pm
Location: SPb
Full Name: Dmitry Popov

Re: Recovery: total disaster (1.5.0.306), Case # 01818507

Veeam Logoby ds2 » Mon Jun 13, 2016 6:28 pm 1 person likes this post

Hello,

with VEB I've done a restore of a physical W2012 R2 Standard to completly different hardware. Only do not inject drives during restore and everything went fine. No BSOD or anything else at boot. Just install the new drivers, create a new recoverymedia an start a new backupchain. In my point of few VEB has realy done a great job for me!

For sure I have some addational wishes for VEB, but don't forget we ware talking about a free product (also free for commercial use).

Greetings

Rene
ds2
Enthusiast
 
Posts: 76
Liked: 16 times
Joined: Thu Jul 16, 2015 6:31 am
Full Name: Rene Keller

Re: Recovery: total disaster (1.5.0.306), Case # 01818507

Veeam Logoby Erhard » Tue Jun 14, 2016 7:49 am

Hello,

sorry for the late reply but I am kind of busy ...

I will try to answer most questions. In case I overlooked something, please tell me.

> Can you elaborate how your USB mouse was connected (directly or via usb hub)

No USB hub was used.

> what device you were restoring?

A Fujitsu PC (Business Line).

> Also on what operating system recovery media was created?

Windows 7. But I am not sure whether it was 32 or 64 bit.

> Maybe all the USB Ports were USB3.0

The system had both USB 2.0 and 3.0 ports and of course keyboard and mouse were connected to USB 2.0 directly.

> Veeam Endpoint Backup and Veeam B&R

Since I have a lot of problems with both I am wondering if the brand is a good choice at all.

> Hidden gem #...

If a recovery is required (especially the entire system) there is no time to test this and test that and try around. Time is critical and things have to work. Everyone can do backups. I need something that can recover properly.

> Only do not inject drives during restore

What do you mean? This sounds like some important hint! When I created the recovery medium (ISO) on those PCs I used "Include network settings from this computer" and "Include hardware drivers from this computer" options from the "Create Recovery Media" wizzard. Should I uncheck "Include hardware drivers from this computer"? I thought it would be useful to have the hard drive controller driver on the recovery medium because otherwise it might not be able to access any drives?!

Best regards,

Erhard
Erhard
Novice
 
Posts: 6
Liked: never
Joined: Mon Jun 06, 2016 5:57 am
Full Name: Erhard Pütz

Re: Recovery: total disaster (1.5.0.306), Case # 01818507

Veeam Logoby Erhard » Tue Jun 14, 2016 7:53 am

Hello again,

> Only do not inject drives during restore

Do you really mean "drives"?

I am asking because I read "drivers" ....

Of course I did not plug-in or unplug drives while the restore was in progress.

Best regards, Erhard
Erhard
Novice
 
Posts: 6
Liked: never
Joined: Mon Jun 06, 2016 5:57 am
Full Name: Erhard Pütz

Re: Recovery: total disaster (1.5.0.306), Case # 01818507

Veeam Logoby ds2 » Tue Jun 14, 2016 8:08 am

Erhard wrote:What do you mean? This sounds like some important hint! When I created the recovery medium (ISO) on those PCs I used "Include network settings from this computer" and "Include hardware drivers from this computer" options from the "Create Recovery Media" wizzard. Should I uncheck "Include hardware drivers from this computer"? I thought it would be useful to have the hard drive controller driver on the recovery medium because otherwise it might not be able to access any drives?!


Sorry,I meant drivers!

To have the drivers in the recoverymedia is realy good if you restore to the same machine or exactly the same hardware. That is the reason why I create for each machine a new recoverymedia.

But if you restore to a new machine with other hardware then I use the option to not inject the drivers during the recovery, because wrong drivers causes BSOD or anything else.
ds2
Enthusiast
 
Posts: 76
Liked: 16 times
Joined: Thu Jul 16, 2015 6:31 am
Full Name: Rene Keller

Next

Return to Veeam Agent for Windows



Who is online

Users browsing this forum: No registered users and 16 guests