Jump to content
19ce03cb-2e19-491c-995e-7b012f122e5c

Writer "asr Writer" Backup Failed, Error -1001

Recommended Posts

I have a problem with my backups on two Windows 2008 Server 64bit machines:

 

+ Executing Immediate Backup at 10.04.2011 13:39 (Execution unit 1)

To Backup Set S_aria...

T-10: MapError: unknown Windows error -1'017

T-10: VssWAddComponentToSnapshot: UGetComponentInfo failed., osErr -1017, error -1001

 

- 10.04.2011 13:39:23: Copying Local Disk (C:) on S_aria

Writer "ASR Writer" backup failed, error -1001 ( unknown Windows OS error).

10.04.2011 14:20:49: Snapshot stored, 145.7 MB

10.04.2011 14:21:09: Comparing Local Disk (C:) on S_aria

10.04.2011 14:37:58: Execution completed successfully

Completed: 66306 files, 19.0 GB

Performance: 715.2 MB/minute (505.7 copy, 1160.5 compare)

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

 

The windows event log looks fine (no errors).

Is there any information about these errors?

Any help would be nice.

Thank you,

 

Jan

Share this post


Link to post
Share on other sites

No help - just a "me too".

 

I've just added a Windows 2008 R2 (64) server and when I tried my first immediate backup I started getting the same errors.

 

Server Retrospect:

Multi Server

Version 7.7.341 (32-Bit)

 

Client Version: 7.7.114

 

 

+ Executing Immediate Backup at 4/10/2011 9:06 AM (Execution unit 1)

To Backup Set S - gisserver2...

T-16: MapError: unknown Windows error -1,017

T-16: VssWAddComponentToSnapshot: UGetComponentInfo failed., osErr -1017, error -1001

 

- 4/10/2011 9:06:15 AM: Copying gisserver2_c (C:) on S - gisserver2

Writer "ASR Writer" backup failed, error -1001 ( unknown Windows OS error).

4/10/2011 9:47:21 AM: Snapshot stored, 226.7 MB

4/10/2011 9:48:29 AM: Execution completed successfully

Completed: 122143 files, 46.6 GB

Performance: 1699.1 MB/minute

Duration: 00:42:14 (00:14:11 idle/loading/preparing)

Share this post


Link to post
Share on other sites

I'm also getting a bunch of inscrutable "not enough resources" errors. Not enough resources where?

The client is a Win2008 R2 Server with ample free space and 16gb of memory. The retrospect server is Win7, has 4GB and a wide open set of LTO-4 Tapes.

 

 

File "E:\temp\tablet\recovery.SNA": can't read, error -1019 ( not enough resources)

File "E:\temp\tablet\recovery.sn1": can't read, error -1019 ( not enough resources)

File "E:\temp\tablet\recovery.sn2": can't read, error -1019 ( not enough resources)

File "E:\temp\tablet\recovery.sn3": can't read, error -1019 ( not enough resources)

File "E:\WRMP\TaskTime-FINAL_2.xls": can't read, error -1019 ( not enough resources)

File "E:\System Volume Information\8{3808876b-c176-4e48-b7ae-04046e6cc752}": can't read, error -1019 ( not enough resources)

File "E:\System Volume Information\tracking.log": can't read, error -1019 ( not enough resources)

T-301: FEncStart: unable to start encryption handler thread

T-304: FEncStart: unable to start encryption handler thread

Trouble reading files, error -1019 ( not enough resources)

4/10/2011 1:08:24 PM: Snapshot stored, 49.1 MB

Edited by oscart

Share this post


Link to post
Share on other sites

After changing back to the old 7.6 Version of Retrospect Multiserver the backup worked fine on both servers without any errors.

I believe the ASR Writer error is caused by the hidden EFI-Partition on our two new blade servers, because

on our older blade servers (windows 2003)I had never two deal with these kind of problems.

Retrospect (ASR Writer) has no access to this Partition (which has no drive letter and you can't assign one with the disk management tool).

The second problem is that I can't set the windows partition active.

There is also no option in the disk management tool (greyed out).

It's possible that there is a workaround but I don't know one.

 

Please correct me if I'm totaly wrong.

 

I must clearly say that I'm not very happy with the current 7.7 version of retrospect at this time.

There is really much work to do in the future to get a good and stable software.

 

@oscart:

I had many of these -1019 errors on our windows 2003 Retrospect server (4GB RAM) if I tried to backup big DB-Dumps (10 to 60 GB).

After changing the registry setting for the Kernal Memory I get rid of these errors, but I don't think this will work the same way under Windows 7.

Share this post


Link to post
Share on other sites

 

@oscart:

I had many of these -1019 errors on our windows 2003 Retrospect server (4GB RAM) if I tried to backup big DB-Dumps (10 to 60 GB).

After changing the registry setting for the Kernal Memory I get rid of these errors, but I don't think this will work the same way under Windows 7.

 

This is for a windows 2008 server. You don't happen to remember the registry key off hand? If not I'll start digging around msdn looking for it.

 

Thanks

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

×