Received email notification of above error but there is plenty of space on volume, lun and OS. Backup is remotely verified.
SME logs
[06:15:21.012] Starting asynchronous DoSnapshotSet. Please wait...
[06:15:22.012] Operation pending, please wait...(1)
[06:15:27.012] Operation pending, please wait...(2)
[06:15:30.011] Error in calling VSS API: Error code = 0x8007000e Error description:
[06:15:30.136] CLEANUP FAILED BACKUP
[06:15:30.136] Warning: Invalid SnapInfo folder renamed to:
[06:15:30.136] P:\SME_SnapInfo\EXCH__VMMAIL2\SG__First Storage Group\03-30-2010_06.03.485675_invalid
[06:15:30.136] Rename SnapInfo folder from and to: [06:15:30.136] P:\SME_SnapInfo\EXCH__VMMAIL2\SG__First Storage Group\03-30-2010_06.03.48
[06:15:30.136] P:\SME_SnapInfo\EXCH__VMMAIL2\SG__First Storage Group\03-30-2010_06.03.485675_invalid
[06:15:30.574] Error code: 0x8007000e [06:15:30.574] An autosupport message is sent on failure to the storage system of LUN [Q].
Applog shows
Event Type: Error
Event Source: Navssprv
Event Category: None
Event ID: 4110
Date: 3/30/2010
Time: 6:04:47 AM
User: N/A
Computer: VMMAIL2
Description:
Data ONTAP VSS hardware provider's AbortSnapshot method is called [SnapshotSetId={ab52eabf-1b56-4598-8cb3-ee26b52254f4}]. VSS has failed the current shadow copy session because the previous errors are not continuable.
I noticed the SnapInfo folder named 03-30-2010_06.03.485675_invalid
What causes an invalid Snapinfo folder?
On successful backups I see a Logs folder that looks like it holds exchange logs, a couple of XML files and an SME file.
Thanks for any help.
