Scheduled snapshots fail after upgrade to SANiQ 10

[balblas]

Hi,

Since we've upgraded our P4000 SAN to version 10.0.00.1888.0 none of our scheduled application managed snapshot work anymore.

Manually creating an application managed snapshot works fine.

We did upgrade both the HP Lefthand DSM for MPIO and the HP Lefthand Application Aware Snashot Manager to version 10 on the Windows 2008R2 hosts.

The error logged on the P4000 end is "The snapshot schedule 'xxxxxxxx_Sch_SS_1' status in cluster 'xxxxxxxx' is 'Failed': 'App-Managed SS Failed: VSS Provider: ISCSI error 0xefff000a. Authorization Failure.'."

On the affected Windows servers the error is "Failed to connect snapshot LUN , 0x80001001 - ISCSI error 0xefff000a. Authorization Failure."

I tried re-creating the snapshot schedule as well, but that did not resolve the issue.

I'm sure the HP Lefthand Application Aware Snashot Manager on the Windows host is configured correctly, and I'm using the correct IP address in the server configuration on the P4000. Otherwise a manual application aware snapshot for the same Windows server and the same volume wouldn't work either.

[P4000Rich]

Check the VSS agent installed on your host systems and ensure that it is the latest version.   If it is not at the latest it will not work.

[GreenfieldsTech]

Hi,

After upgrading to SAN IQ 10, we are experiencing the same issue. Did you find a resolution?

We are using the latest VSS agent.

Thanks,

[gwolters]

Hello,

We had some problems after the upgrade to SAN/IQ 10 too. Especially when snapshots were made by DPM backup (using HP application aware snapshots). Solved it by:

1) creating an server cluster in CMC (that will assign all servers in that cluster to the snapshot)

2) installed next microsoft hotfixes (to fix iSCSI, MPIO connection errors during backup wich caused crashing of the hyper-v cluster). Got the list from an HP engineer who handeld my case:

Specific to clustering;

2750820 Event log after you configure the quorum model to Node Majority and to File Share Witness on a Windows Server 2008 R2-based Cluster service

http://support.microsoft.com/kb/2750820/EN-US

2531907 Validate SCSI Device Vital Product Data (VPD) test fails after you install Windows Server 2008 R2 SP1

http://support.microsoft.com/kb/2531907/EN-US

2685891 CAP does not come online in a Windows Server 2008 R2-based failover cluster

http://support.microsoft.com/kb/2685891/EN-US

Specific to Hyper-V;

2705759 Live migration fails when you perform a live migration of a Hyper-V virtual machine in Windows Server 2008 R2

http://support.microsoft.com/kb/2705759/EN-US

2666703 You cannot restore a virtual machine that has a semicolon in its name or in its directory path on a Windows Server 2008 R2 SP1-based server

http://support.microsoft.com/kb/2666703/EN-US

General;

mpio

2718576 MPIO disk is removed unexpectedly when a PR_IN command fails in a Windows Server 2008 R2 environment

http://support.microsoft.com/kb/2718576/EN-US

msiscsi;

2684681          Iscsicpl.exe process stops responding when you try to reconnect a storage device to a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2

http://support.microsoft.com/kb/2684681/EN-US

rdbss;

2670567 "0x000000027" Stop error when you copy a file from a redirected folder in Windows 7 or in Windows Server 2008 R2

http://support.microsoft.com/kb/2670567/EN-US

Kernel;

2705742 "0x0000003B" Stop error when you use a Citrix XenApp application in Windows 7 or in Windows Server 2008 R2

http://support.microsoft.com/kb/2705742/EN-US

rpcss;

2756999 Handle leak occurs on a COM client that is running on a Windows 7 or Windows Server 2008 R2 computer

http://support.microsoft.com/kb/2756999/EN-US

Mrxsmb10;

2727324 Computer stops responding after you connect to an SMB 1 server in Windows 7 or in Windows Server 2008 R2

http://support.microsoft.com/kb/2727324/EN-US

Mrxsmb20;

2739674 You cannot connect to remote computers by using the SMB protocol on a computer that is running Windows 7 or Windows Server 2008 R2

http://support.microsoft.com/kb/2739674/EN-US

tcpip;

2752370 "0x000000D1" Stop error when you perform a network-related operation on a computer that is running Windows 7 or Windows Server 2008 R2

http://support.microsoft.com/kb/2752370/EN-US

2524478          The network location profile changes from "Domain" to "Public" in Windows 7 or in Windows Server 2008 R2

http://support.microsoft.com/kb/2524478/EN-US

After thes solutions everthing runs like it should.

Regards Gerard