bmclachlan Posted September 14, 2010 Report Share Posted September 14, 2010 I am again using 7.7 after an unusual issue with 7.6. W+hen I first upgraded to 7.7 when it became available I also received this error with 7,7 - Insufficient storage space available. Here is the log: + Normal backup using Tablet M700 APR 20 at 9/13/2010 10:00 PM To Backup Set Tablet M700 Apr 20... T-8: VssWSnapVolume: DoSnapshotSet failed, winerr -2147212513, error -3045 Can't use Open File Backup option for Bill on M700, error -3045 ( there is insufficient storage space to complete the operation) - 9/13/2010 10:00:15 PM: Copying Bill on M700 9/13/2010 10:04:20 PM: Snapshot stored, 11.7 MB 9/13/2010 10:04:29 PM: Comparing Bill on M700 9/13/2010 10:05:17 PM: Execution completed successfully Completed: 188 files, 522.7 MB Performance: 287.6 MB/minute (183.3 copy, 667.1 compare) Duration: 00:05:01 (00:01:22 idle/loading/preparing) There is more than 150 GB available on the storage device. Why does this error occur? R was attempting to backup up a Win 7 Ultimate 64 bit client. R runs on a Win 7 Pro PC. Quote Link to comment Share on other sites More sharing options...
AndrewA Posted September 14, 2010 Report Share Posted September 14, 2010 Since the error is happening for open file backup the insufficient storage space error is mostly likely referring to the C: drive of the machine that it is trying to backup. Retrospect uses the volume shadow copy service within Windows and it by default uses space on the C: drive when creating snapshots. Quote Link to comment Share on other sites More sharing options...
bmclachlan Posted September 14, 2010 Author Report Share Posted September 14, 2010 thanks Andrew. The client has 90 GB of free space on the C drive so something else must be happening. Quote Link to comment Share on other sites More sharing options...
bmclachlan Posted October 5, 2010 Author Report Share Posted October 5, 2010 Further to this issue, the client application error log reports a VSS error at the time of the backup. The VSS error log states that the error is typically due to the requestor app not allowing the callback service access to the app. 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.