Comprehensive data protection for all workloads
Post Reply
spgsit5upport
Expert
Posts: 215
Liked: 16 times
Joined: May 28, 2010 10:25 am
Full Name: Seb
Contact:

Direct SAN connection is not available, failing over to netw

Post by spgsit5upport » Aug 21, 2011 9:59 am

I have VMFS volumes visible OK in Disk Management (M$ iSCSI initiator on a pair of BCM 5708C nics on separate network) on Server 2008 R2

I am getting:

Code: Select all

C:\Program Files (x86)\VMware\VMware Consolidated Backup Framework>vcbSanDbg.exe

[2011-08-21 11:09:58.527 'App' 4396 info] Current working directory: C:\Program
Files (x86)\VMware\VMware Consolidated Backup Framework
[2011-08-21 11:09:58.527 'BaseLibs' 4396 info] HOSTINFO: Seeing Intel CPU, numCo
resPerCPU 2 numThreadsPerCore 1.
[2011-08-21 11:09:58.527 'BaseLibs' 4396 info] HOSTINFO: This machine has 2 phys
ical CPUS, 4 total cores, and 4 logical CPUs.
[2011-08-21 11:09:58.543 'App' 4396 verbose] Building SCSI Device List...
[2011-08-21 11:09:58.558 'App' 4396 error] Dumping SCSI Device/LUN List.
[2011-08-21 11:09:58.558 'App' 4396 info] **** Begin SCSI Device LIst ****
[2011-08-21 11:09:58.558 'App' 4396 info] **** End SCSI Device LIst ****
The LUNs are configured correctly as I use some for Windows access (and they work)

That applies to both arrays Equallogic PS550x & EMC AX4-5i with PowerPath 5.5 SP1

I did see EMC AX4-5i iSCSI and Win2k8

Did you ever have a "pleasure" of dealing with EMC support?
For me it is just a nightmare of dealing with some idiot in India that had NO clue what I was asking & obviously was only armed with web browser pointing to
Google

Will try Dell support in the week

Extra read http://www.petri.co.il/how-to-deal-with ... indows.htm

Help appreciated

Thanks

Seb

spgsit5upport
Expert
Posts: 215
Liked: 16 times
Joined: May 28, 2010 10:25 am
Full Name: Seb
Contact:

Re: Direct SAN connection is not available, failing over to

Post by spgsit5upport » Aug 21, 2011 2:07 pm


spgsit5upport
Expert
Posts: 215
Liked: 16 times
Joined: May 28, 2010 10:25 am
Full Name: Seb
Contact:

Re: Direct SAN connection is not available, failing over to

Post by spgsit5upport » Aug 21, 2011 3:05 pm

It is only partial solution, I can enumerate all LUN using vcbsandbg, but backup still goes over network - VMFS3 is a LUN on AX4-5i:

Code: Select all

[2011-08-21 16:04:22.782 'App' 3644 info] Current working directory: C:\Program
Files (x86)\VMware\VMware Consolidated Backup Framework
[2011-08-21 16:04:22.782 'BaseLibs' 3644 info] HOSTINFO: Seeing Intel CPU, numCo
resPerCPU 2 numThreadsPerCore 1.
[2011-08-21 16:04:22.782 'BaseLibs' 3644 info] HOSTINFO: This machine has 2 phys
ical CPUS, 4 total cores, and 4 logical CPUs.
[2011-08-21 16:04:22.797 'App' 3644 verbose] Building SCSI Device List...
[2011-08-21 16:04:22.891 'App' 3644 trivia] Evaluating 1 paths.
[2011-08-21 16:04:22.891 'App' 3644 trivia] Trying to open path \\?\scsi#disk&ve
n_dell&prod_perc_5#i#6&2a781ece&0&010000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

[2011-08-21 16:04:22.891 'App' 3644 info] Now using Path \\?\scsi#disk&ven_dell&
prod_perc_5#i#6&2a781ece&0&010000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.
[2011-08-21 16:04:22.891 'App' 3644 trivia] Reading 32256 bytes from offset 0.
[2011-08-21 16:04:22.891 'App' 3644 trivia] Found 1 partition(s) on this device.

[2011-08-21 16:04:22.891 'App' 3644 trivia] Evaluating 1 paths.
[2011-08-21 16:04:22.891 'App' 3644 trivia] Trying to open path \\?\scsi#disk&ve
n_dell&prod_perc_5#i#6&2a781ece&0&010100#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

[2011-08-21 16:04:22.907 'App' 3644 info] Now using Path \\?\scsi#disk&ven_dell&
prod_perc_5#i#6&2a781ece&0&010100#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.
[2011-08-21 16:04:22.907 'App' 3644 trivia] Reading 32256 bytes from offset 0.
[2011-08-21 16:04:22.907 'App' 3644 trivia] Found 1 partition(s) on this device.

[2011-08-21 16:04:22.907 'App' 3644 trivia] Evaluating 1 paths.
[2011-08-21 16:04:22.907 'App' 3644 trivia] Trying to open path \\?\scsi#disk&ve
n_emc&prod_power&#{4a54205a-c920-4e28-88c5-9a6296a74b0b}&emcp&power1#{53f56307-b
6bf-11d0-94f2-00a0c91efb8b}.
[2011-08-21 16:04:22.938 'App' 3644 info] Now using Path \\?\scsi#disk&ven_emc&p
rod_power&#{4a54205a-c920-4e28-88c5-9a6296a74b0b}&emcp&power1#{53f56307-b6bf-11d
0-94f2-00a0c91efb8b}.
[2011-08-21 16:04:22.938 'App' 3644 trivia] Reading 32256 bytes from offset 0.
[2011-08-21 16:04:22.938 'App' 3644 trivia] Found 1 partition(s) on this device.

[2011-08-21 16:04:22.938 'App' 3644 trivia] Evaluating 1 paths.
[2011-08-21 16:04:22.938 'App' 3644 trivia] Trying to open path \\?\scsi#disk&ve
n_emc&prod_power&#{4a54205a-c920-4e28-88c5-9a6296a74b0b}&emcp&power3#{53f56307-b
6bf-11d0-94f2-00a0c91efb8b}.
[2011-08-21 16:04:22.938 'App' 3644 info] Now using Path \\?\scsi#disk&ven_emc&p
rod_power&#{4a54205a-c920-4e28-88c5-9a6296a74b0b}&emcp&power3#{53f56307-b6bf-11d
0-94f2-00a0c91efb8b}.
[2011-08-21 16:04:22.938 'App' 3644 trivia] Reading 32256 bytes from offset 0.
[2011-08-21 16:04:22.938 'App' 3644 trivia] Found 1 partition(s) on this device.

[2011-08-21 16:04:22.938 'App' 3644 trivia] Evaluating 1 paths.
[2011-08-21 16:04:22.938 'App' 3644 trivia] Trying to open path \\?\scsi#disk&ve
n_emc&prod_power&#{4a54205a-c920-4e28-88c5-9a6296a74b0b}&emcp&power5#{53f56307-b
6bf-11d0-94f2-00a0c91efb8b}.
[2011-08-21 16:04:22.953 'App' 3644 info] Now using Path \\?\scsi#disk&ven_emc&p
rod_power&#{4a54205a-c920-4e28-88c5-9a6296a74b0b}&emcp&power5#{53f56307-b6bf-11d
0-94f2-00a0c91efb8b}.
[2011-08-21 16:04:22.953 'App' 3644 trivia] Reading 32256 bytes from offset 0.
[2011-08-21 16:04:22.953 'App' 3644 trivia] Found 1 partition(s) on this device.

[2011-08-21 16:04:22.953 'App' 3644 info] Partition #1 is a VMFS partition.
[2011-08-21 16:04:22.953 'App' 3644 trivia] Reading 1574400 bytes from offset 11
14112.
[2011-08-21 16:04:23.187 'App' 3644 trivia] Found an ESX LVM v3 signature on par
tition 1.
[2011-08-21 16:04:23.187 'App' 3644 info] Found logical volume 4e367274-62feee4c
-94e6-001ec9d406c2.
[2011-08-21 16:04:23.187 'App' 3644 trivia] Evaluating 1 paths.
[2011-08-21 16:04:23.187 'App' 3644 trivia] Trying to open path \\?\scsi#disk&ve
n_eqlogic&prod_100e-00#1&1c121344&0&000500#{53f56307-b6bf-11d0-94f2-00a0c91efb8b
}.
[2011-08-21 16:04:23.187 'App' 3644 info] Now using Path \\?\scsi#disk&ven_eqlog
ic&prod_100e-00#1&1c121344&0&000500#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.
[2011-08-21 16:04:23.187 'App' 3644 trivia] Reading 32256 bytes from offset 0.
[2011-08-21 16:04:23.219 'App' 3644 trivia] Found 1 partition(s) on this device.

[2011-08-21 16:04:23.219 'App' 3644 info] Partition #1 is a VMFS partition.
[2011-08-21 16:04:23.219 'App' 3644 trivia] Reading 1574400 bytes from offset 11
14112.
[2011-08-21 16:04:23.265 'App' 3644 trivia] Found an ESX LVM v3 signature on par
tition 1.
[2011-08-21 16:04:23.265 'App' 3644 info] Found logical volume 4cb6bfba-10fe4b2d
-66b0-001ec9d406c4.
[2011-08-21 16:04:23.265 'App' 3644 trivia] Evaluating 1 paths.
[2011-08-21 16:04:23.265 'App' 3644 trivia] Trying to open path \\?\scsi#disk&ve
n_eqlogic&prod_100e-00#1&1c121344&0&000400#{53f56307-b6bf-11d0-94f2-00a0c91efb8b
}.
[2011-08-21 16:04:23.265 'App' 3644 info] Now using Path \\?\scsi#disk&ven_eqlog
ic&prod_100e-00#1&1c121344&0&000400#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.
[2011-08-21 16:04:23.265 'App' 3644 trivia] Reading 32256 bytes from offset 0.
[2011-08-21 16:04:23.281 'App' 3644 trivia] Found 1 partition(s) on this device.

[2011-08-21 16:04:23.281 'App' 3644 info] Partition #1 is a VMFS partition.
[2011-08-21 16:04:23.281 'App' 3644 trivia] Reading 1574400 bytes from offset 11
14112.
[2011-08-21 16:04:23.297 'App' 3644 trivia] Found an ESX LVM v3 signature on par
tition 1.
[2011-08-21 16:04:23.312 'App' 3644 info] Found logical volume 4cb6bff5-abe0ead0
-524a-001ec9d406c4.
[2011-08-21 16:04:23.312 'App' 3644 error] Dumping SCSI Device/LUN List.
[2011-08-21 16:04:23.312 'App' 3644 info] **** Begin SCSI Device LIst ****
[2011-08-21 16:04:23.312 'App' 3644 info] Found SCSI Device: NAA:60019b90b0aadc0
00e420ab388b1ab7c504552432035
[2011-08-21 16:04:23.312 'App' 3644 info] Visible on 1 paths:
[2011-08-21 16:04:23.312 'App' 3644 info] Device Name: \\?\scsi#disk&ven_dell&pr
od_perc_5#i#6&2a781ece&0&010000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 T
arget: 0 Lun: 0
[2011-08-21 16:04:23.312 'App' 3644 info] Lun does not contain any VMFS/LVM sign
atures.
[2011-08-21 16:04:23.312 'App' 3644 info] Found SCSI Device: NAA:60019b90bae50c0
015c01377713db1b2504552432035
[2011-08-21 16:04:23.312 'App' 3644 info] Visible on 1 paths:
[2011-08-21 16:04:23.328 'App' 3644 info] Device Name: \\?\scsi#disk&ven_dell&pr
od_perc_5#i#6&2a781ece&0&010100#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 T
arget: 1 Lun: 0
[2011-08-21 16:04:23.328 'App' 3644 info] Lun does not contain any VMFS/LVM sign
atures.
[2011-08-21 16:04:23.328 'App' 3644 info] Found SCSI Device: NAA:60060160a6a0220
0e2d4802561b9e011524149442035
[2011-08-21 16:04:23.328 'App' 3644 info] Visible on 1 paths:
[2011-08-21 16:04:23.328 'App' 3644 info] Device Name: \\?\scsi#disk&ven_emc&pro
d_power&#{4a54205a-c920-4e28-88c5-9a6296a74b0b}&emcp&power1#{53f56307-b6bf-11d0-
94f2-00a0c91efb8b}, Bus: 0 Target: 0 Lun: 0
[2011-08-21 16:04:23.328 'App' 3644 info] Lun does not contain any VMFS/LVM sign
atures.
[2011-08-21 16:04:23.328 'App' 3644 info] Found SCSI Device: NAA:60060160a6a0220
06c79c6e6f8c3e011565241494420
[2011-08-21 16:04:23.328 'App' 3644 info] Visible on 1 paths:
[2011-08-21 16:04:23.328 'App' 3644 info] Device Name: \\?\scsi#disk&ven_emc&pro
d_power&#{4a54205a-c920-4e28-88c5-9a6296a74b0b}&emcp&power3#{53f56307-b6bf-11d0-
94f2-00a0c91efb8b}, Bus: 0 Target: 0 Lun: 1
[2011-08-21 16:04:23.343 'App' 3644 info] Lun does not contain any VMFS/LVM sign
atures.
[2011-08-21 16:04:23.343 'App' 3644 info] Found SCSI Device: NAA:60060160a6a0220
0cc306e6a61b9e011565241494420
[2011-08-21 16:04:23.343 'App' 3644 info] Visible on 1 paths:
[2011-08-21 16:04:23.343 'App' 3644 info] Device Name: \\?\scsi#disk&ven_emc&pro
d_power&#{4a54205a-c920-4e28-88c5-9a6296a74b0b}&emcp&power5#{53f56307-b6bf-11d0-
94f2-00a0c91efb8b}, Bus: 0 Target: 0 Lun: 2
[2011-08-21 16:04:23.343 'App' 3644 info] Lun contains VMFS/LVM signatures:
[2011-08-21 16:04:23.343 'App' 3644 info] VMFS LVM signature.
[2011-08-21 16:04:23.343 'App' 3644 info] ID: LVID:4e367277-f38387a4-9e38-001ec9
d406c2/4e367274-62feee4c-94e6-001ec9d406c2/1 Name: 4e367274-62feee4c-94e6-001ec9
d406c2
[2011-08-21 16:04:23.343 'App' 3644 info] Found SCSI Device: NAA:6090a0286094315
e57cbd401d000d079313030452d30
[2011-08-21 16:04:23.343 'App' 3644 info] Visible on 1 paths:
[2011-08-21 16:04:23.343 'App' 3644 info] Device Name: \\?\scsi#disk&ven_eqlogic
&prod_100e-00#1&1c121344&0&000500#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 0
 Target: 5 Lun: 0
[2011-08-21 16:04:23.359 'App' 3644 info] Lun contains VMFS/LVM signatures:
[2011-08-21 16:04:23.359 'App' 3644 info] VMFS LVM signature.
[2011-08-21 16:04:23.359 'App' 3644 info] ID: LVID:4cb6bfbb-56244462-ea31-001ec9
d406c4/4cb6bfba-10fe4b2d-66b0-001ec9d406c4/1 Name: 4cb6bfba-10fe4b2d-66b0-001ec9
d406c4
[2011-08-21 16:04:23.359 'App' 3644 info] Found SCSI Device: NAA:6090a0286094515
a57cba401d000d0f0313030452d30
[2011-08-21 16:04:23.359 'App' 3644 info] Visible on 1 paths:
[2011-08-21 16:04:23.359 'App' 3644 info] Device Name: \\?\scsi#disk&ven_eqlogic
&prod_100e-00#1&1c121344&0&000400#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 0
 Target: 4 Lun: 0
[2011-08-21 16:04:23.359 'App' 3644 info] Lun contains VMFS/LVM signatures:
[2011-08-21 16:04:23.359 'App' 3644 info] VMFS LVM signature.
[2011-08-21 16:04:23.359 'App' 3644 info] ID: LVID:4cb6bff6-f1dabe1a-7c90-001ec9
d406c4/4cb6bff5-abe0ead0-524a-001ec9d406c4/1 Name: 4cb6bff5-abe0ead0-524a-001ec9
d406c4
[2011-08-21 16:04:23.359 'App' 3644 info] **** End SCSI Device LIst ****

Code: Select all

Backing up object "[VMFS3] vcenter/vcenter.vmdk"
Unable to establish direct connection to the shared storage (SAN).
Please ensure that:
- HBA is properly installed in the Veeam Backup server computer, or software iSCSI initiator is configured correctly.
- SAN volume can be seen by operating system in the Windows Disk Management snap-in on the Veeam Backup server.
- Read access is allowed for the Veeam Backup server computer on the corresponding LUN (refer to your SAN documentation).

Direct SAN connection is not available, failing over to network mode...
Seb

Gostev
SVP, Product Management
Posts: 24643
Liked: 3470 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Direct SAN connection is not available, failing over to

Post by Gostev » Aug 21, 2011 8:10 pm

Hi Seb,

Try changing Veeam Backup service account to Local System and see if it helps (I've seen this help with certain SAN devices having this kind of issue). If this does not help, best would be to contact our support for further troubleshooting.

On an unrelated note, kindly please review the rules of posting technical issues provided in big red font when you click New Topic. Normally, this topic should have been deleted, because you have managed to brake most of them :D what helped here is that there clearly were no moderators around on Saturday ;)

Thanks!

spgsit5upport
Expert
Posts: 215
Liked: 16 times
Joined: May 28, 2010 10:25 am
Full Name: Seb
Contact:

Re: Direct SAN connection is not available, failing over to

Post by spgsit5upport » Aug 22, 2011 8:20 am

I can NOT do that, as I am backing up to a remote UNC share that needs to login with a user name/password (local system does not have rights to do it)

I am sorry, but do not see what rules could be broken!

Seb

Gostev
SVP, Product Management
Posts: 24643
Liked: 3470 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Direct SAN connection is not available, failing over to

Post by Gostev » Aug 22, 2011 8:27 am

Local System uses computer account's privileges when going on the network. Grant your computer account permissions on this share, if possible.
For a start though, try this at least as a test, by backing up locally, to see if this even helps.

READ THIS BEFORE POSTING A SUPPORT ISSUE
2. Posting log snippets is prohibited. Full logs must be provided to support instead.
3. Posting about a technical issue without referencing support case ID is prohibited.

spgsit5upport
Expert
Posts: 215
Liked: 16 times
Joined: May 28, 2010 10:25 am
Full Name: Seb
Contact:

Re: Direct SAN connection is not available, failing over to

Post by spgsit5upport » Aug 22, 2011 10:37 am

But local system account does not have any rights to my remote SQL database! so the service can NOT start

Seb

Gostev
SVP, Product Management
Posts: 24643
Liked: 3470 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Direct SAN connection is not available, failing over to

Post by Gostev » Aug 22, 2011 1:09 pm

Gostev wrote:try this at least as a test, by backing up locally, to see if this even helps

spgsit5upport
Expert
Posts: 215
Liked: 16 times
Joined: May 28, 2010 10:25 am
Full Name: Seb
Contact:

Re: Direct SAN connection is not available, failing over to

Post by spgsit5upport » Aug 22, 2011 2:42 pm

As I said, I can NOT try, as the service will NOT start due to the stated fact!

So if the service does not start, I can NOT start the application & I can NOT try to backup localy

Seb

Gostev
SVP, Product Management
Posts: 24643
Liked: 3470 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Direct SAN connection is not available, failing over to

Post by Gostev » Aug 22, 2011 3:24 pm

Sorry, my extra comments got lost in the previous post. There is this issue that causes 404 when posting every now and then that we are keep fighting with.

Can you make a default install (with local SQL Express) for the purpose of this testing? With such install, you should be able to run the service as Local System. Again, this is needed just to pinpoint the issue and see if I was right - and not for long-term usage. Thanks.

spgsit5upport
Expert
Posts: 215
Liked: 16 times
Joined: May 28, 2010 10:25 am
Full Name: Seb
Contact:

Re: Direct SAN connection is not available, failing over to

Post by spgsit5upport » Aug 22, 2011 4:03 pm

Ok, will do it when find a spare moment

Seb

spgsit5upport
Expert
Posts: 215
Liked: 16 times
Joined: May 28, 2010 10:25 am
Full Name: Seb
Contact:

Re: Direct SAN connection is not available, failing over to

Post by spgsit5upport » Aug 22, 2011 8:42 pm

Tried adding the domain user that is associated with Veeam service to local administrators group.
By hand, (could be by GPO - http://www.frickelsoft.net/blog/?p=13 )

Makes no difference, still Unable to establish direct connection to the shared storage (SAN).

Seb

Post Reply

Who is online

Users browsing this forum: AdsBot [Google], Bing [Bot], cdekermadec and 30 guests