Exchange 2010 Application Managed Snapshot

[Dave Finch]

When my scheduled Application Managed Snapshot runs, it fails with the following error:
"Event : E00070100 EID_SCHED_STATUS_FAILED_MSG
Severity : Warning
Component : SAN/iQ
Object Type : Snapshot Schedule
Object Name : ACGEX03_E_Sch_SS_1
Management Group : MGT_ABQ
Cluster : CL_ABQ-3TB
IP/Hostname : ABQSAN01
Date and Time : 01/16/2011 12:00:37 GMT
User : System
Resolution : http://h20000.www2.hp.com/bizsupport/site/search/r4_0/jsp/search.jsp?lang=en&cc=US&pc=0&sc=2&cf=1&cm=1&cs=1&c130=1&c115=1&c110=1&c120=1&nh=10&rf=0&lkc=1&lk=1&tx=E00070100
Message : The snapshot schedule 'ACGEX03_E_Sch_SS_1' status in cluster 'CL_ABQ-3TB' is 'Failed': 'App-Managed SS Failed:Shadow copying the specified volume is not supported.'."

A manual application managed snapshot fails, too, but it simply indicates: "Shadow copying the specified volume is not supported."

The database and transaction logs are on separate, dedicated, volumes. The exchange server connects using MS iSCSI. The firewall is off on all networks. I've enabled diagnostic logging on the Exchange server's Exchange Writer set to High but no errors are logged.

It's Exchange 2010 SP1 running on Windows Server 2008 R2 with current Windows updates. All patches have been applied to SAN i/Q 9.0 (i.e. no updates indicated in the CMC).

The LHNVssProvider is registerd:
H:\>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Provider name: 'HP P4000 VSS Provider'
Provider type: Hardware
Provider Id: {acef7bd9-c49b-435a-bb6c-bc3bab91fda5}
Version: 9.0.0.1006

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7

There are existing shadow copies created by Windows backup. I've set the schedule so that the backup and the snapshots occur at different times, but this failed before we started using Windows backup, too.

Any help is appreciated,
Dave

[Emilo]

Hello,

Were you ever able to get this fixed??

[M.Braak]

Yes i want to know also because we have the same problem now with our new exchange 2010 implementation. It seems the problem is caused by having seperate volumes for the databases and logs. When i place them on the same volume the snapshot works. But offcourse that's not adviceble. Really want to know if anyone knows a fix.