Jump to content
ajwh

Errors in Win10 backup

Recommended Posts

Using Version 10.5.0.110

 

I regularly (weekly) back up my wife's machine across the network.

 

On the last two occasions I've been getting errors:

 

-    13/12/2015 14:46:03: Copying OS (C:) on VSH-DHZ04C4J-MT
        13/12/2015 14:53:21: Found: 297,810 files, 54,495 folders, 71.1 GB
        13/12/2015 14:53:30: Finished matching
        Backing up 1 out of 2 files using block level incremental backup, storing full backups for remaining 1.
        13/12/2015 14:53:53: Copying: 498 files (4.4 GB) and 0 hard links
    13/12/2015 14:57:24: Building Snapshot...
        13/12/2015 14:57:27: Copying VSS writer files
        13/12/2015 14:57:40: Finished copying VSS writer files
        Can't back up registry, error -1013 (malformed name)
        13/12/2015 14:57:56: Copying properties for 54,495 folders
        13/12/2015 15:03:49: Finished copying properties for 54,495 folders and 0 files
        Writer "Task Scheduler Writer" backup failed, error -1101 (file/directory not found).
        Component "TasksStore" backup failed, error -1101 (file/directory not found).
        Writer "VSS Metadata Store Writer" backup failed, error -1101 (file/directory not found).
        Component "WriterMetadataStore" backup failed, error -1101 (file/directory not found).
        Writer "Performance Counters Writer" backup failed, error -1101 (file/directory not found).
        Component "PerformanceCounters" backup failed, error -1101 (file/directory not found).
        Writer "ASR Writer" backup failed, error -1101 (file/directory not found).
        Writer "MSSearch Service Writer" backup failed, error -1101 (file/directory not found).
        Writer "IIS Config Writer" backup failed, error -1101 (file/directory not found).
        Component "IISCONFIG" backup failed, error -1101 (file/directory not found).
        13/12/2015 15:04:22: Copying Snapshot: 306 files (362.0 MB)
        13/12/2015 15:06:00: Snapshot stored, 362.0 MB

 

I've run CCleaner against her registry with no benefit.

 

Borh machines are running Win10Pro64, fully updated.

 

This problem first occurred on Dec 6th:

 

    06/12/2015 11:30:52: Building Snapshot...
        06/12/2015 11:30:56: Copying VSS writer files
        06/12/2015 11:31:38: Finished copying VSS writer files
        06/12/2015 11:32:03: Copying properties for 56,258 folders
        06/12/2015 11:38:13: Finished copying properties for 56,258 folders and 0 files
        Writer "ASR Writer" backup failed, error -3050 (VSS reported an error).
        Writer "MSSearch Service Writer" backup failed, error -3050 (VSS reported an error).
        Writer "IIS Config Writer" backup failed, error -3050 (VSS reported an error).
        Component "IISCONFIG" backup failed, error -3050 (VSS reported an error).
        06/12/2015 11:38:45: Copying Snapshot: 217 files (277.9 MB)
        06/12/2015 11:39:59: Snapshot stored, 277.9 MB


All suggestions gratefully received.....
 

Share this post


Link to post
Share on other sites

Was this a clean install of Windows 10 or an upgrade? My experience is that upgrades have given me problems but clean installs have so far been fine.

 

As for the -3050 errors I have found these to usually occur when disk IO is overloaded. Such a situation could be Retrospect trying to do a backup, Windows Update updating and Windows Defender do a scan all at the same time. Something has to give and it is Retrospect that looses.

Share this post


Link to post
Share on other sites

Both machines are upgradees - but three months ago.

 

Retrospect has been working well until recently.

 

It's the Can't back up registry, error -1013 (malformed name) which worries me!

Share this post


Link to post
Share on other sites

Sorry about the delay - yes I've run the Win10 file checker - no issues.

If it is due to corruption within the Registry then this will not show when checking files.

 

Did this problem start after the update/upgrade to Windows 10 Version 1511 (Threshold 2 update)?

 

Several of my machines that were upgrades from earlier versions of Windows had minor issues after this update.

 

(Win10 doesn't do chkdsk).

It still there — they just call it 'Error checking' now.

Share this post


Link to post
Share on other sites

OK - I've run chkdsk ( it's there from the Command Prompt) - no issues.

This is a machine which started with XP, then had an upgrade to Win7, then another to Win10, and I think it's just too much.

Something has got crossed.....

It's seven years old, and I'm replacing it.

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

×