Discussions specific to the VMware vSphere hypervisor
Post Reply
haris2887
Novice
Posts: 7
Liked: 1 time
Joined: Oct 11, 2012 11:50 am
Contact:

Veeam not Using defined Server ISCSI targets. MPIO

Post by haris2887 » Sep 25, 2014 6:46 am

Hello.
i have a problem with veeam that no-one seems to be able to solve, Including Veeam Support. case 00640986

I have setup ISCSI targets in my windows server 2012R2 machine and i can connect to the SAN ( offline disk shows in disk manager). I have also setup server 2012R2 MPIO.
Image

When i run a backup JOB .
Veeam automatically makes another Iscsi session and does not use my existing session. Because of this behavious the backup fails because the SAN in our enviroment needs CHAP authentication , when veeams Makes the new iscsi session it does not use CHAP hence it can access the SAN.

There is the session created by Veeam to access the SAN.
I then i went ahead and disabled CHap auth on the SAN. and Bang! everything works, Screen shot below shows the Iscsi sucessfully connected to SAN.
Image

Here is my MPIO configuration SHOWING 2 Paths

Code: Select all

MPIO Storage Snapshot on Thursday, 25 September 2014, at 16:44:27.030

Registered DSMs: 1
================
+--------------------------------|-------------------|----|----|----|---|-----+
|DSM Name                        |      Version      |PRP | RC | RI |PVP| PVE |
|--------------------------------|-------------------|----|----|----|---|-----|
|Microsoft DSM                   |006.0003.09600.16384|0020|0003|0001|030|False|
+--------------------------------|-------------------|----|----|----|---|-----+


Microsoft DSM
=============
MPIO Disk3: 02 Paths, Round Robin, ALUA Not Supported
        SN: 600EB3BA97EFB97000000066                                        
        Supported Load Balance Policies: FOO RR RRWS LQD WP LB

    Path ID          State              SCSI Address      Weight
    ---------------------------------------------------------------------------
    0000000077030003 Active/Optimized   003|000|003|000   0
        Adapter: Microsoft iSCSI Initiator...              (B|D|F: 000|000|000)
        Controller: 46616B65436F6E74726F6C6C6572 (State: Active)

    0000000077030002 Active/Optimized   003|000|002|000   0
        Adapter: Microsoft iSCSI Initiator...              (B|D|F: 000|000|000)
        Controller: 46616B65436F6E74726F6C6C6572 (State: Active)

MPIO Disk2: 02 Paths, Round Robin, ALUA Not Supported
        SN: 600EB3BA97EFB97000000054                                        
        Supported Load Balance Policies: FOO RR RRWS LQD WP LB

    Path ID          State              SCSI Address      Weight
    ---------------------------------------------------------------------------
    0000000077030001 Active/Optimized   003|000|001|000   0
        Adapter: Microsoft iSCSI Initiator...              (B|D|F: 000|000|000)
        Controller: 46616B65436F6E74726F6C6C6572 (State: Active)

    0000000077030000 Active/Optimized   003|000|000|000   0
        Adapter: Microsoft iSCSI Initiator...              (B|D|F: 000|000|000)
        Controller: 46616B65436F6E74726F6C6C6572 (State: Active)

MSDSM-wide default load balance policy: N\A

No target-level default load balance policies have been set.

================================================================================

MPIO Storage Snapshot on Tuesday, 23 September 2014, at 23:09:12.306

Registered DSMs: 1
================
+--------------------------------|-------------------|----|----|----|---|-----+
|DSM Name                        |      Version      |PRP | RC | RI |PVP| PVE |
|--------------------------------|-------------------|----|----|----|---|-----|
|Microsoft DSM                   |006.0003.09600.16384|0020|0003|0001|030|False|
+--------------------------------|-------------------|----|----|----|---|-----+


Microsoft DSM
=============
MPIO Disk6: 02 Paths, Round Robin, ALUA Not Supported
        SN: 600EB3BA97EFB97000000066                                        
        Supported Load Balance Policies: FOO RR RRWS LQD WP LB

    Path ID          State              SCSI Address      Weight
    ---------------------------------------------------------------------------
    0000000077030003 Active/Optimized   003|000|003|000   0
        Adapter: Microsoft iSCSI Initiator...              (B|D|F: 000|000|000)
        Controller: 46616B65436F6E74726F6C6C6572 (State: Active)

    0000000077030002 Active/Optimized   003|000|002|000   0
        Adapter: Microsoft iSCSI Initiator...              (B|D|F: 000|000|000)
        Controller: 46616B65436F6E74726F6C6C6572 (State: Active)

MPIO Disk5: 02 Paths, Round Robin, ALUA Not Supported
        SN: 600EB3BA97EFB97000000054                                        
        Supported Load Balance Policies: FOO RR RRWS LQD WP LB

    Path ID          State              SCSI Address      Weight
    ---------------------------------------------------------------------------
    0000000077030001 Active/Optimized   003|000|001|000   0
        Adapter: Microsoft iSCSI Initiator...              (B|D|F: 000|000|000)
        Controller: 46616B65436F6E74726F6C6C6572 (State: Active)

    0000000077030000 Active/Optimized   003|000|000|000   0
        Adapter: Microsoft iSCSI Initiator...              (B|D|F: 000|000|000)
        Controller: 46616B65436F6E74726F6C6C6572 (State: Active)

MSDSM-wide default load balance policy: N\A

No target-level default load balance policies have been set.

================================================================================

MPIO Storage Snapshot on Tuesday, 23 September 2014, at 22:53:05.043

Registered DSMs: 1
================
+--------------------------------|-------------------|----|----|----|---|-----+
|DSM Name                        |      Version      |PRP | RC | RI |PVP| PVE |
|--------------------------------|-------------------|----|----|----|---|-----|
|Microsoft DSM                   |006.0003.09600.16384|0020|0003|0001|030|False|
+--------------------------------|-------------------|----|----|----|---|-----+


Microsoft DSM
=============
MPIO Disk3: 02 Paths, Round Robin, ALUA Not Supported
        SN: 600EB3BA97EFB97000000066                                        
        Supported Load Balance Policies: FOO RR RRWS LQD WP LB

    Path ID          State              SCSI Address      Weight
    ---------------------------------------------------------------------------
    0000000077030003 Active/Optimized   003|000|003|000   0
        Adapter: Microsoft iSCSI Initiator...              (B|D|F: 000|000|000)
        Controller: 46616B65436F6E74726F6C6C6572 (State: Active)

    0000000077030001 Active/Optimized   003|000|001|000   0
        Adapter: Microsoft iSCSI Initiator...              (B|D|F: 000|000|000)
        Controller: 46616B65436F6E74726F6C6C6572 (State: Active)

MPIO Disk2: 02 Paths, Round Robin, ALUA Not Supported
        SN: 600EB3BA97EFB97000000054                                        
        Supported Load Balance Policies: FOO RR RRWS LQD WP LB

    Path ID          State              SCSI Address      Weight
    ---------------------------------------------------------------------------
    0000000077030002 Active/Optimized   003|000|002|000   0
        Adapter: Microsoft iSCSI Initiator...              (B|D|F: 000|000|000)
        Controller: 46616B65436F6E74726F6C6C6572 (State: Active)

    0000000077030000 Active/Optimized   003|000|000|000   0
        Adapter: Microsoft iSCSI Initiator...              (B|D|F: 000|000|000)
        Controller: 46616B65436F6E74726F6C6C6572 (State: Active)

MSDSM-wide default load balance policy: N\A

No target-level default load balance policies have been set.

================================================================================

MPIO Storage Snapshot on Tuesday, 23 September 2014, at 22:49:35.446

Registered DSMs: 1
================
+--------------------------------|-------------------|----|----|----|---|-----+
|DSM Name                        |      Version      |PRP | RC | RI |PVP| PVE |
|--------------------------------|-------------------|----|----|----|---|-----|
|Microsoft DSM                   |006.0003.09600.16384|0020|0003|0001|030|False|
+--------------------------------|-------------------|----|----|----|---|-----+


Microsoft DSM
=============
MPIO Disk3: 01 Paths, Round Robin, ALUA Not Supported
        SN: 600EB3BA97EFB97000000066                                        
        Supported Load Balance Policies: FOO RR RRWS LQD WP LB

    Path ID          State              SCSI Address      Weight
    ---------------------------------------------------------------------------
    0000000077030001 Active/Optimized   003|000|001|000   0
        Adapter: Microsoft iSCSI Initiator...              (B|D|F: 000|000|000)
        Controller: 46616B65436F6E74726F6C6C6572 (State: Active)

MPIO Disk2: 01 Paths, Round Robin, ALUA Not Supported
        SN: 600EB3BA97EFB97000000054                                        
        Supported Load Balance Policies: FOO RR RRWS LQD WP LB

    Path ID          State              SCSI Address      Weight
    ---------------------------------------------------------------------------
    0000000077030000 Active/Optimized   003|000|000|000   0
        Adapter: Microsoft iSCSI Initiator...              (B|D|F: 000|000|000)
        Controller: 46616B65436F6E74726F6C6C6572 (State: Active)

MSDSM-wide default load balance policy: N\A

No target-level default load balance policies have been set.

================================================================================

Vitaliy S.
Product Manager
Posts: 23001
Liked: 1557 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Veeam not Using defined Server ISCSI targets. MPIO

Post by Vitaliy S. » Sep 25, 2014 11:24 am

Hi Haris,

Veeam should not create any new iSCSI targets during Direct SAN mode, unless you're using integration with storage snapshots. I see that you're using HP LeftHand storage, so can you please clarify if you would like to use direct SAN mode or storage snapshot integration to backup your production VMs?

If it is the second, then CHAP authentication is not supported in integration with HP storage yet. You can either backup production VMs using direct SAN mode with CHAP authentication (Veeam will be using existing iSCSI targets) and disable storage snapshot integration checkbox in the backup console or use storage snapshots for backing up the VMs, but with no CHAP authentication.

Let me know if that helps!

haris2887
Novice
Posts: 7
Liked: 1 time
Joined: Oct 11, 2012 11:50 am
Contact:

Re: Veeam not Using defined Server ISCSI targets. MPIO

Post by haris2887 » Sep 25, 2014 10:32 pm

Hi Thanks for your Reply.
Yes we are using storage snapshots with HP store virtual.

Thats a bummer that veeam does not support CHAP when using storage snapshots.
Is this a freture that will be introduced in V8.

Vitaliy S.
Product Manager
Posts: 23001
Liked: 1557 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Veeam not Using defined Server ISCSI targets. MPIO

Post by Vitaliy S. » Sep 26, 2014 8:49 am

As far as I know, this capability is not a part of v8 release, but it is tracked and has chances to be introduced in our next updates/releases.

dries.vergote
Service Provider
Posts: 26
Liked: 4 times
Joined: Apr 24, 2015 2:51 pm
Full Name: Dries Vergote
Contact:

Re: Veeam not Using defined Server ISCSI targets. MPIO

Post by dries.vergote » Jan 22, 2019 8:19 pm

hi

Did this ever got updated that chap authentication is allowed via storage snapshot integration?

How is the best way to configure this with netapp solidfire?
We are making a backup from the iscsi disk to local storage.

Regards.

dries.vergote
Service Provider
Posts: 26
Liked: 4 times
Joined: Apr 24, 2015 2:51 pm
Full Name: Dries Vergote
Contact:

Re: Veeam not Using defined Server ISCSI targets. MPIO

Post by dries.vergote » Jan 22, 2019 9:31 pm

Additionally:
We get the following error:
1/22/2019 10:06:18 PM Unmask of volume [24] to hostname [veeam_MicrosoftInitiator] and IQN [iqn.1991-05.com.microsoft:veeam] failed: xPermissionDenied

how do we configure the solidfire and iscsi to work with storage integration?
We tried with CHAP and without CHAP authentication. Both failed on the storage integration way.

What is the transport mode on the proxy for this? I used direct san without chap authentication and the iscsi mounted > works but isn't really fast.
In automatic mode and with storage integration enabled I get the above error. (no chap on the Solidfire ISCSI volume).

thx in advance.

dries.vergote
Service Provider
Posts: 26
Liked: 4 times
Joined: Apr 24, 2015 2:51 pm
Full Name: Dries Vergote
Contact:

Re: Veeam not Using defined Server ISCSI targets. MPIO

Post by dries.vergote » Jan 24, 2019 3:18 pm

Update with Case # 03379095
Anyone has experience with veeam and solidfire configuration? Also with the snapshot storage integration?
We found out the the snapshot volume that is created by veeam not have the correct access group and therefore no ISCSI access to backup from.
When during backup job added manually to the access group the backup is completed successfully.

How can this process be automated?

Thx in advance.

Ryan S
Service Provider
Posts: 7
Liked: never
Joined: Jan 12, 2017 12:34 pm
Full Name: Ryan S
Location: Malaysia
Contact:

Re: Veeam not Using defined Server ISCSI targets. MPIO

Post by Ryan S » Jan 24, 2019 4:14 pm

do you see any unallocated disk at windows disk management of all the assigned backup proxy?
if your configuration are correct you should see those disk appear as unallocated black bars, those disk only for view purpose we must not configure anything on it...
After that your Veeam shall be able to proceed direct SAN backup method

second thing is how about iSCSI as IP not IQN ?

dries.vergote
Service Provider
Posts: 26
Liked: 4 times
Joined: Apr 24, 2015 2:51 pm
Full Name: Dries Vergote
Contact:

Re: Veeam not Using defined Server ISCSI targets. MPIO

Post by dries.vergote » Jan 24, 2019 4:33 pm

Hi

Yes I can see the volume I want to back-up in diskmanagement. I only have set the disk online but nothing else.
I'm not using direct SAN but storage integrated snapshot.

I tried direct at one point but if I enable storage integrated snapshot the backup fails.
1/22/2019 10:06:18 PM :: Error: Unmask of volume [24] to hostname [veeam_MicrosoftInitiator] and IQN [iqn.1991-05.com.microsoft:veeam] failed: xPermissionDenied

What do you mean ISCSI as IP. It's the newly created snapshot by veeam that is not able to connect as it has no access group permission on the netapp.
The disk I want to backup is available, the snapshot isn't .

dries.vergote
Service Provider
Posts: 26
Liked: 4 times
Joined: Apr 24, 2015 2:51 pm
Full Name: Dries Vergote
Contact:

Re: Veeam not Using defined Server ISCSI targets. MPIO

Post by dries.vergote » Jan 28, 2019 6:40 am 1 person likes this post

The problem is solved. The rights of the user connecting to veeam on the netapp must be leveled up to clusteradmin and volumes.

Andreas Neufert
Veeam Software
Posts: 3820
Liked: 687 times
Joined: May 04, 2011 8:36 am
Full Name: Andreas Neufert
Location: Germany
Contact:

Re: Veeam not Using defined Server ISCSI targets. MPIO

Post by Andreas Neufert » Jan 28, 2019 8:12 am

Thanks for sharing.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 9 guests