Jump to content
bpmhutch

Version 7.7 - Writer "ASR Writer" backup failed

Recommended Posts

Just upgraded from Retro Pro 7.6 to 7.7 on Windows 7 Home Premium. Pro 7.6 ran without any problems, Pro 7.7 gives the error:

 

Writer "ASR Writer" backup failed, error -1017 (insufficient permission)

 

I'm running Pro 7.7 as administrator.

 

Anyone any thoughts?

 

Peter

Share this post


Link to post
Share on other sites

I'm seeing similar errors, but not on every run. Here's two otherwise-identical backup runs from within the same instance of Retrospect (i.e without closing the app between backups, so whatever permissions it had for the first run it also had for the second, and vice versa:

+ Retrospect version 7.7.203

Launched at 12/17/2009 12:14 PM

 

+ Driver Update and Hot Fix, version 7.7.1.102 (64-bit)

 

+ Normal backup using Daily backup at 12/18/2009 8:19 PM

To Backup Set Backup Set B...

 

- 12/18/2009 8:19:22 PM: Copying System (C:)

Writer "ASR Writer" backup failed, error -1017 ( insufficient permissions).

Writer "MSSearch Service Writer" backup failed, error -1017 ( insufficient permissions).

Writer "WMI Writer" backup failed, error -1017 ( insufficient permissions).

Component "WMI" backup failed, error -1017 ( insufficient permissions).

Writer "COM+ REGDB Writer" backup failed, error -1017 ( insufficient permissions).

Component "COM+ REGDB" backup failed, error -1017 ( insufficient permissions).

Writer "Registry Writer" backup failed, error -1017 ( insufficient permissions).

Component "Registry" backup failed, error -1017 ( insufficient permissions).

12/18/2009 8:34:29 PM: Snapshot stored, 166.9 MB

12/18/2009 8:34:43 PM: 7 execution errors

Completed: 1929 files, 656.4 MB, with 48% compression

Performance: 325.4 MB/minute

Duration: 00:15:20 (00:13:19 idle/loading/preparing)

 

- 12/18/2009 8:34:48 PM: Verifying Backup Set B

12/18/2009 8:35:12 PM: Execution completed successfully

Completed: 1929 files, 656.4 MB

Performance: 2187.7 MB/minute

Duration: 00:00:24 (00:00:05 idle/loading/preparing)

 

 

+ Normal backup using Daily backup at 12/19/2009 1:00 PM

To Backup Set Backup Set B...

 

- 12/19/2009 1:00:00 PM: Copying System (C:)

12/19/2009 1:09:51 PM: Snapshot stored, 225.0 MB

12/19/2009 1:10:10 PM: Execution completed successfully

Completed: 425 files, 312.2 MB, with 40% compression

Performance: 328.5 MB/minute

Duration: 00:10:10 (00:09:12 idle/loading/preparing)

 

- 12/19/2009 1:10:16 PM: Verifying Backup Set B

12/19/2009 1:10:34 PM: Execution completed successfully

Completed: 425 files, 312.2 MB

Performance: 1702.3 MB/minute

Duration: 00:00:18 (00:00:06 idle/loading/preparing)

 

 

Retrospect 7.7 Pro (with latest RDU), running as Administrator under 64-bit Win7 Ultimate

Share this post


Link to post
Share on other sites

Was the backupset that you are backing up to created with 7.6? If so, try creating a new backup set, backup the 7.7, and see you get the same errors. I have done a lot of windows 7 backups, but most were with fresh backup sets.

 

I'll try and reproduce this to bypass the escalation process.

 

-Jeff

Share this post


Link to post
Share on other sites

The backup sets were created under 7.6, but I have reset them, removed all the members, and created new ones on my NAS under 7.7

 

I may be wrong, but I think I'm only seeing these errors the first time a backup runs after a reboot. I reboot rarely, so I can't readily verify that observation, but I'll make a point of watching for it next time I do.

Share this post


Link to post
Share on other sites

Thanks for the info!

 

I created backup sets with 7.6 and updated to 7.7 to see if that would cause issues, and so far it hasn't. I also tried rebooting and backing up my system disk multiple times.

 

Is it possible that there was an antivirus running during the first execution, and not in the second? Or maybe this antivirus starts a scan after every reboot?

Share this post


Link to post
Share on other sites

Hi

 

I've tried:

 

1. A brand new full back-up

2. A back-up with Kaspersky swirched off

3. Two back-ups one after the other without closing Retrospect in-between

 

And all give the "ASR Writer" backup failed, error -1017 (insufficient permission) message!!

 

Pete

Share this post


Link to post
Share on other sites

Hi Pete,

 

Developers have suggested that this issue could be caused by using dynamic disks as a backup destination. If you are using a RAID, you ought to attempt a backup to a different destination as a test.

 

The ASR failure will only affect a Disaster recovery disk restoration. Live restores should work just fine.

 

JEtkins

 

Your issue seems different, and from the log you posted it looks like there are a number of writer services that retrospect doesn't have permission to use. Your errors would cause restoration problems, but since you are also able to backup successfully on other occasions, the backup set should contain the data needed for a successful restore. I would still suggest that you might look into anti viruses to see if that’s what is creating these permission conflicts.

 

Share this post


Link to post
Share on other sites

Hi all,

 

Took the plunge back in November and did a clean install of Windows 7 (previous install had been over Vista (I think)). Anyway no error messages!!

 

Pete

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

×