1374923E45198DE1E040000A2A666149 Posted June 14, 2011 Report Share Posted June 14, 2011 I have Retrospect 7.7.562 running on a Windows 7 Ultimate desktop with a network of Windows 7 Home Premium desktop and laptop. The program will stall in the middle of a backup and doesn't seem to recover. At the moment I am looking at the backup screen with the program stalled for the last eight hours on a program called Annual Set A.rbc which is a Retrospect catalog for my annual backup (not the weekly one that is stalled). The program is running - I can look at all the other items such as Backup Report; History; and so on. The backup medium is an Iomega REV drive of 35 GByte capacity, with 8 GByte still free. The Events page shows 'Can't use Open File Backup option for WINDOWSXPMA (C:), error -1017 (insufficient permissions)' but this is a frequent message which usually comes up at least once per partition and doesn't normally cause a freeze. Any ideas? I know from the past that it will not be possible to close down Retrospect by exiting - I will have to use Task Manager to kill the program when it is in this limbo state. The problem does not exist in Retrospect 7.6.123 Roy Tipping Quote Link to comment Share on other sites More sharing options...
poorman Posted June 14, 2011 Report Share Posted June 14, 2011 The reference to open file backup in the error message makes me suspect that something is amiss with the Windows shadow copy capability on the client machine. I'm no expert on diagnosing and fixing shadow copy, but google finds quite a few threads such as this one that discuss it. There's a command line utility named "vssadmin" that displays the current state of the shadow copy subsystem. The common theme seems to be that if some of the "vssadmin list" commands hang or fail then there's something you need to fix. Also, there were a few threads on this topic in the old Retrospect report forum. For example, searching for "vssadmin retrospect" found this thread that might help. -- Pete Quote Link to comment Share on other sites More sharing options...
1374923E45198DE1E040000A2A666149 Posted June 15, 2011 Author Report Share Posted June 15, 2011 The reference to open file backup in the error message makes me suspect that something is amiss with the Windows shadow copy capability on the client machine. I'm no expert on diagnosing and fixing shadow copy, but google finds quite a few threads such as this one that discuss it. There's a command line utility named "vssadmin" that displays the current state of the shadow copy subsystem. The common theme seems to be that if some of the "vssadmin list" commands hang or fail then there's something you need to fix. Also, there were a few threads on this topic in the old Retrospect report forum. For example, searching for "vssadmin retrospect" found this thread that might help. -- Pete Quote Link to comment Share on other sites More sharing options...
1374923E45198DE1E040000A2A666149 Posted June 15, 2011 Author Report Share Posted June 15, 2011 Pete, Thanks for the suggestions. Unfortunately running vssadmin list writers shows that Windows Volume Shadow Service is working correctly with all the running writers. Running chkdsk /f, which was also suggested on the thread, produced no errors on any of my partitions. And today it hung again, with errors -1017 and -1020, as previously, this time on a file that had previously saved correctly. Roy Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.