Sounds as if shared memory could not be initiated, but I have no idea how would you fix it in this case. I assume you are backing up this via virtual name, right?
BackupMedium::ReportIoError: read failure on backup device 'Legato#33c886c8-5c31-4a97-be27-2bedcaa69ae6'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
I'm running NW 7.6.1 on Windows, and 5.2.2.23 on the SQL Client.
2 days with EMC support hasn't resulted in a solution. In fact, they referred me to Microsoft. MS at this point has no idea. Local SQL backup and restores work, as well as a local backup and restore using Redgate's tool. I know the sqlvdi.dll is only called when using a third party tool (NW, or Redgate).
If anyone has suggestions I would love to hear them.
ble1
4 Operator
•
14.4K Posts
0
January 27th, 2008 13:00
GJFox
1 Message
0
February 2nd, 2011 06:00
I have encountered a very closely related issue. When I attempt a restore on SQL 2005 SP3 I get a sqlvdi.dll error:
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=4632. Thread=5608. Server. Instance=MSSQLSERVER. VD=Global\Legato#33c886c8-5c31-4a97-be27-2bedcaa69ae6_SQLVDIMemoryName_0.
AND......
BackupMedium::ReportIoError: read failure on backup device 'Legato#33c886c8-5c31-4a97-be27-2bedcaa69ae6'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
I'm running NW 7.6.1 on Windows, and 5.2.2.23 on the SQL Client.
2 days with EMC support hasn't resulted in a solution. In fact, they referred me to Microsoft. MS at this point has no idea. Local SQL backup and restores work, as well as a local backup and restore using Redgate's tool. I know the sqlvdi.dll is only called when using a third party tool (NW, or Redgate).
If anyone has suggestions I would love to hear them.