Jump to content
Sign in to follow this  
stavroska

Can't save Catalog File, error -1103 (write protected)

Recommended Posts

Hi there,

 

I am getting the following error:

 

---------------------------------

- 17.03.2005 22:40:17: Copying Disk (D:)

Can't save Catalog File, error -1103 (write protected)

17.03.2005 23:11:00: Execution incomplete

Completed: 216 files, 2.372 KB

--------------------------------

same script will run without problems for 2-3 days then fail and run without problems the following day.

As I have more sites the same behaviour occurs on 3 sites with different hardware all on W2K server running Retrospect 7 with the latest patches.

 

doh.gif

Share this post


Link to post
Share on other sites

Nate,

 

Backup media is LTO or AIT in resp. Exabyte and Sony autoloaders.

Catalog files are saved on the Backup Server disk RAID 5, not the system volume with plenty of space.

 

Thanks

Stavros

Share this post


Link to post
Share on other sites

Hi

 

Are you running multiple executions at once?

 

Make sure you have the latest Windows drivers installed for the RAID. For the moment I would move the catalog files to a different disk and see if the problems continue. All you need to do is move the catalog file and then double click on it so Retrospect can see the location is changed.

 

Thanks

nate

Share this post


Link to post
Share on other sites

 

Nate,

 

the problem is still around...

What really puzzles me is that it gets the error on one disk snapshot but not the next one.

Where does retrospect write the snapshot? (I presume on tape) so how can it be write protected and not in the same job?

 

from the log:

--------------------------------------------------------------------

 

 

- 31.05.2005 22:00:03: Copying Disk (C:)

Can't save Snapshot in Daily Set B, error -1103 (write protected)

31.05.2005 22:03:55: Comparing Disk (C:)

File "C:\WINNT\system32\Perflib_Perfdata_528.dat": different data size (set: 0, vol: 16.384)

File "C:\WINNT\system32\ias\ias.ldb": different data size (set: 0, vol: 64)

31.05.2005 22:04:19: 2 execution errors

Completed: 266 files, 71,0 MB

Performance: 82,6 MB/minute (47,3 copy, 354,8 compare)

Duration: 00:04:15 (00:02:32 idle/loading/preparing)

 

 

- 31.05.2005 22:04:20: Copying Disk (D:)

31.05.2005 22:50:11: Snapshot stored, 18,2 MB

31.05.2005 22:50:18: Comparing Disk (D:)

31.05.2005 22:50:43: Execution completed successfully

Completed: 207 files, 2.195 KB

Performance: 3,2 MB/minute (2,2 copy, 6,1 compare)

Duration: 00:46:23 (00:45:02 idle/loading/preparing)

Share this post


Link to post
Share on other sites

Hi

 

It is a really rare problem and I don't think Retrospect is directly at fault in this case. There must be something about your setup that lends itself to this kind of error.

 

Are you using Retrospect 7.0.301? Where do you store your catalog files? Can you try keeping them on a different disk.

 

Thanks

nate

Share this post


Link to post
Share on other sites

Given the number of responses I was pretty sure it is a rare problem...

 

Yes, we are using 7.0.301.

Catalog files are on a different volume but not disk as we are using a RAID 5 array.

Share this post


Link to post
Share on other sites

Hi

 

For the moment try moving your catalog files to the system volume and see if that makes a difference. That will narrow things down.

 

Is the tape drive on a dedicated SCSI card or is it on the same controller as the RAID?

 

Thanks

nate

Share this post


Link to post
Share on other sites

Hi

 

The tape is on a dedicated SCSI card.

Moving the catalog files to the system drive... I can do this only on one of the servers... due to the size. Will do that and see what gives!

How will it narrow things down??

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  

×