Hello,
We are facing an issue with a bare metal recovery of a physical server that is booting from SAN . Here is the context :
We are currently backuping this Windows 2008 R2 physical server with Veeam Agent version 2.2.0.589.
This physical server is a HP BL460c Gen8 Blade server, connected to SAN storage via Emulex Fiber Channel HBA card (SAN built on top of Brocade Switch and Compellent SC8000 storage array). There is one volume to backup (C:), and this is a "Boot From SAN" server.
The backup process is ok and we are trying to validate our capacity to do a bare metal recovery to another physical server. This server is almost the same server, but a Gen9 version, with Qlogic HBA card.
So, we boot the destination server with the veeam recovery media and we connect a USB media that contains the veeam backup (VBK+VBM). This destination server is connected to the same SAN and an empty SAN volume is presented to this server. The objective is to restore on this SAN volume.
The problem is that the Bare Metal Recovery assistant is not able to see our SAN volume. However, we included HBA Qlogic driver in this media, and we are able to load the Qlogic drivers. But the disk is still not selectable in the assistant. And when we do a diskpart/list disk, the disk is present and online.
We've just opened a case to veeam support (#03244119).
Behind this test, we would like to proove that Veeam Agent could replace our old legacy BackupExec...
So if you have any ideas...
Thanks.
-
- Influencer
- Posts: 21
- Liked: 4 times
- Joined: Nov 17, 2015 1:31 pm
- Full Name: H.Schema.
- Contact:
-
- Product Manager
- Posts: 14715
- Liked: 1702 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Bare Metal Recovery with Boot From SAN
Hi Buh95.
I see in the case details that disk issue was resolved and it's now visible. Have you found the root cause of that's BSOD? From the top of my head the incompatible drivers injected during recovery could be the root case. Can you try to re run the restore but before performing it go to Tools > Load Drivers and uncheck 'Inject drivers...' option. Cheers!
I see in the case details that disk issue was resolved and it's now visible. Have you found the root cause of that's BSOD? From the top of my head the incompatible drivers injected during recovery could be the root case. Can you try to re run the restore but before performing it go to Tools > Load Drivers and uncheck 'Inject drivers...' option. Cheers!
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Nov 07, 2018 3:10 pm
- Full Name: Jarek Pogan
- Contact:
Re: Bare Metal Recovery with Boot From SAN
Hi,
i have a similar problem, could you share resolution if any ?
San Disk is visible in diskpart but not with the recovery assisantant.
i have a similar problem, could you share resolution if any ?
San Disk is visible in diskpart but not with the recovery assisantant.
-
- Product Manager
- Posts: 14715
- Liked: 1702 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Bare Metal Recovery with Boot From SAN
Hello Jarek,
Sorry for the delay. Can you please clarify your setup? Have you installed the storage drivers (were these drivers collected during the recovery media creation)? Thank you!
Sorry for the delay. Can you please clarify your setup? Have you installed the storage drivers (were these drivers collected during the recovery media creation)? Thank you!
Who is online
Users browsing this forum: Bing [Bot] and 54 guests