Jump to content
Sign in to follow this  
Tom45

Can't backup system state (Retrospect 8)

Recommended Posts

Just upgraded to Retrospect 8 and at the end of the log file for c:, I see:

 

Can't back up System State, error -3045 ( there is insufficient storage space to complete the operation)

11/23/2012 7:07:16 PM: Snapshot stored, 105.2 MB

11/23/2012 7:07:36 PM: 67 execution errors

Remaining: 73 files, 16.0 GB

Completed: 443551 files, 154.8 GB, with 9% compression

Performance: 1234.0 MB/minute

Duration: 02:10:09 (00:01:43 idle/loading/preparing)

 

64 bit Windows 7 with 24GB of memory. The drive is a 238 GB SSD with 66GB free.

 

Any ideas what is wrong?

 

Tom

Share this post


Link to post
Share on other sites

This is a new backup to a new 3 TB drive with 99% allocated to Retrospect. So 154 GB is a drop in the bucket for that backup drive.

 

The backup script is set to backup 3 drives, of which the first (c:) is by far the smallest. It is within a few hours of completing the second drive. So I'll see what happens with it.

 

Tom

Share this post


Link to post
Share on other sites

I note that the back-up is completed... Do you have instant scan feature turned on? If the instant scan has not run a full first scan, or many chnages occured since the last scan, this can result in all kind of unexpected errors. I suggest turn the instant scan off and rerun the back up. You can turn teh instant scan off in the services panel for windows (stop it and disble the startup)..

Share this post


Link to post
Share on other sites

After several days, the problem persists along with other problems.

 

Here is the full backup log from the initial backup with sharing errors removed. This is a new script with new catalog and destination drive that has never been used by Retrospect 7.7.

 

+ Normal backup using NT5--BDisk9 at 11/23/2012 4:57 PM
To Backup Set NT5_BDisk9...
 VssWSnapVolume: DoSnapshotSet failed, winerr -2147212513, error -3045
 Can't use Open File Backup option for NT5_C (C:), error -3045 ( there is insufficient storage space to complete the operation)
- 11/23/2012 4:57:26 PM: Copying NT5_C (C:)
 Using Instant Scan

 Can't back up System State, error -3045 ( there is insufficient storage space to complete the operation)
11/23/2012 7:07:16 PM: Snapshot stored, 105.2 MB
11/23/2012 7:07:36 PM: 67 execution errors
 Remaining: 73 files, 16.0 GB
 Completed: 443551 files, 154.8 GB, with 9% compression
 Performance: 1234.0 MB/minute
 Duration: 02:10:09 (00:01:43 idle/loading/preparing)
 Can't use Open File Backup option for NT5_D (D:), error -3045 ( there is insufficient storage space to complete the operation)
- 11/23/2012 7:07:36 PM: Copying NT5_D (D:)
 Using Instant Scan
11/24/2012 9:25:21 AM: Snapshot stored, 78.5 MB
11/24/2012 9:25:40 AM: Execution completed successfully
 Completed: 299038 files, 1,025.4 GB, with 0% compression
 Performance: 1235.4 MB/minute
 Duration: 14:18:03 (00:08:15 idle/loading/preparing)
 Can't use Open File Backup option for NT5_E (E:), error -3045 ( there is insufficient storage space to complete the operation)
- 11/24/2012 9:25:40 AM: Copying NT5_E (E:)
 Using Instant Scan
11/24/2012 10:13:59 AM: Snapshot stored, 905 KB
11/24/2012 10:14:02 AM: 1 execution errors
 Remaining: 1 files, 150.0 GB
 Completed: 4446 files, 67.0 GB, with 43% compression
 Performance: 1426.9 MB/minute
 Duration: 00:48:21 (00:00:18 idle/loading/preparing)
- 11/24/2012 10:14:25 AM: Verifying NT5_BDisk9
11/24/2012 1:19:48 PM: Execution completed successfully
 Completed: 773263 files, 1,252.7 GB
 Performance: 7282.0 MB/minute
 Duration: 03:04:19 (00:08:09 idle/loading/preparing)
11/24/2012 1:19:49 PM: 71 execution errors
Total duration: 20:21:17 (00:18:27 idle/loading/preparing)

 

Error -3045 happens a lot.

 

The next day I disabled Instant Scan and got no improvement:

 

+ Normal backup using NT5--BDisk9 at 11/25/2012 10:00 PM
To Backup Set NT5_BDisk9...
 VssWSnapVolume: DoSnapshotSet failed, winerr -2147212513, error -3045
 Can't use Open File Backup option for NT5_C (C:), error -3045 ( there is insufficient storage space to complete the operation)
- 11/25/2012 10:00:00 PM: Copying NT5_C (C:)
 Can't back up System State, error -3045 ( there is insufficient storage space to complete the operation)
11/25/2012 10:08:28 PM: Snapshot stored, 108.1 MB
11/25/2012 10:08:34 PM: 80 execution errors
 Remaining: 81 files, 17.5 GB
 Completed: 1548 files, 6.7 GB, with 38% compression
 Performance: 1140.0 MB/minute
 Duration: 00:08:33 (00:02:34 idle/loading/preparing)
 Can't use Open File Backup option for NT5_D (D:), error -3045 ( there is insufficient storage space to complete the operation)
- 11/25/2012 10:08:34 PM: Copying NT5_D (D:)
11/25/2012 10:11:46 PM: Snapshot stored, 80.9 MB
11/25/2012 10:11:50 PM: Execution completed successfully
 Completed: 280 files, 345.4 MB, with 11% compression
 Performance: 1090.6 MB/minute
 Duration: 00:03:15 (00:02:56 idle/loading/preparing)
 Can't use Open File Backup option for NT5_E (E:), error -3045 ( there is insufficient storage space to complete the operation)
- 11/25/2012 10:11:51 PM: Copying NT5_E (E:)
11/25/2012 10:11:56 PM: Snapshot stored, 905 KB
 Can't save Backup Set NT5_BDisk9, error -1103 ( write protected)
11/25/2012 10:11:58 PM: Execution incomplete
 Remaining: 1 files, 150.0 GB
 Completed: 0 files, zero KB, with 0% compression
 Performance: 0.0 MB/minute
 Duration: 00:00:07 (00:00:06 idle/loading/preparing)
11/25/2012 10:12:10 PM: Execution incomplete
Total performance: 1131.5 MB/minute with 36% compression
Total duration: 00:11:57 (00:05:38 idle/loading/preparing)

 

Still can't backup system state. And now the third source (e:) fails because it thinks the destination is write protected. The first two sources in the script didn't report that error.

 

Any idea what is going on here? Should I dump version 8 and go back to 7.7?

 

Tom

Share this post


Link to post
Share on other sites

Should I dump version 8 and go back to 7.7?

 

Well, I have come very close to doing just this myself. I am rather dissappointed so far in v8. None of the new features seem to work (InstantScan!!) or are useful to me and the fundamental reliability of the product seems to have got worse.

 

Maybe it's time to move on :angry: .

Share this post


Link to post
Share on other sites

 VssWSnapVolume: DoSnapshotSet failed, winerr -2147212513, error -3045
 Can't use Open File Backup option for NT5_C (C:), error -3045 ( there is insufficient storage space to complete the operation)

 

This looks to me that Windows is trying to tell Retrospect that it cannot creat a volume snapshot using VSS because there is insufficient disk space available to store the snapshot. (This is a different snapshot from the one that Retrospect is storing as part of the backup.) This snapshot is required for Open File Backup.

 

There is a percentage of total available volume space allocated for snapshot storage. If the size of the snapshot to be stored is larger than the space allocated then the service will fail. I have encountered this problem in the past. From a command prompt you can use vssadmin.exe to check what space is being used by VSS.

 

 

John

Share this post


Link to post
Share on other sites

John is correct. Check the Windows Event logs for more errors. The errors you are getting are coming from VSS and not from Retrospect. Something on your system is preventing the backup of open files.

Share this post


Link to post
Share on other sites

Thanks John. I had a vague idea of what VSS is, but had never looked into it, nor had I ever heard of vssadmin.

 

For whatever reason, the space for c: was full:

 

C:\Windows\System32>vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Shadow Copy Storage association
  For volume: (E:)\\?\Volume{37d258fc-bebe-11df-989f-005056c00008}\
  Shadow Copy Storage volume: (E:)\\?\Volume{37d258fc-bebe-11df-989f-005056c00008}\
  Used Shadow Copy Storage space: 0 B (0%)
  Allocated Shadow Copy Storage space: 0 B (0%)
  Maximum Shadow Copy Storage space: 18.63 GB (1%)
Shadow Copy Storage association
  For volume: (D:)\\?\Volume{33cda9fa-d475-11e1-9794-806e6f6e6963}\
  Shadow Copy Storage volume: (D:)\\?\Volume{33cda9fa-d475-11e1-9794-806e6f6e6963}\
  Used Shadow Copy Storage space: 0 B (0%)
  Allocated Shadow Copy Storage space: 0 B (0%)
  Maximum Shadow Copy Storage space: 18.63 GB (1%)
Shadow Copy Storage association
  For volume: (C:)\\?\Volume{1e19789a-eb64-11de-af7a-806e6f6e6963}\
  Shadow Copy Storage volume: (C:)\\?\Volume{1e19789a-eb64-11de-af7a-806e6f6e6963}\
  Used Shadow Copy Storage space: 17.71 GB (7%)
  Allocated Shadow Copy Storage space: 18.196 GB (7%)
  Maximum Shadow Copy Storage space: 18.628 GB (7%)

 

So I did a vssadmin delete shadows /all

 

Will see how tonights backup goes after this.

 

Tom

Share this post


Link to post
Share on other sites

Shadow Copy Storage association
  For volume: (E:)\\?\Volume{37d258fc-bebe-11df-989f-005056c00008}\
  Shadow Copy Storage volume: (E:)\\?\Volume{37d258fc-bebe-11df-989f-005056c00008}\
  Used Shadow Copy Storage space: 0 B (0%)
  Allocated Shadow Copy Storage space: 0 B (0%)
  Maximum Shadow Copy Storage space: 18.63 GB (1%)

Shadow Copy Storage association
  For volume: (D:)\\?\Volume{33cda9fa-d475-11e1-9794-806e6f6e6963}\
  Shadow Copy Storage volume: (D:)\\?\Volume{33cda9fa-d475-11e1-9794-806e6f6e6963}\
  Used Shadow Copy Storage space: 0 B (0%)
  Allocated Shadow Copy Storage space: 0 B (0%)
  Maximum Shadow Copy Storage space: 18.63 GB (1%)

Shadow Copy Storage association
  For volume: (C:)\\?\Volume{1e19789a-eb64-11de-af7a-806e6f6e6963}\
  Shadow Copy Storage volume: (C:)\\?\Volume{1e19789a-eb64-11de-af7a-806e6f6e6963}\
  Used Shadow Copy Storage space: 17.71 GB (7%)
  Allocated Shadow Copy Storage space: 18.196 GB (7%)
  Maximum Shadow Copy Storage space: 18.628 GB (7%)

 

Have you at some point manually changed the space allocation for System Restore. By default Windows 7 — and by a look at a recent install Windows 8 too — allocates 5% of total volume space for System Restore. Assuming the output from vssadmin was before you deleted the snapshots the fact that no space has been allocated or used on your D: and E: volumes may indicate that insufficient space is allocated.

 

Under normal operation VSS will always run near maximum available space with the oldest snapshots being deleted to make space for new snapshots. On the laptop I am using to write this I have the allocation set to 10% of 240GB volume which currently is enough for four snapshots/restore points.

 

 

John

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×