Jump to content

Errors After Upgrading to 6.5


craig1327

Recommended Posts

Hello, I recently upgraded from Retrospect 5.6 for Windows to Restrospect 6.5 Single Server. This is on a Windows 2000 Pro machine with a SCSI DLT1 drive.

 

Ever since upgrading, I get many more "sharing violation" errors than I ever received before. In particular, every file in the "registry" directiory \winnt\system32\config\ cannot be backed up do to "can't read, error -1020 (sharing violation)".

 

This never happened with Retrospect 5.6. Is there something I'm doing wrong or a setting that I need to change in order to get things functioning correctly like they used to be.

 

Thanks for any advice.

 

-Craig

Link to comment
Share on other sites

I upgraded to version 6.5.319 but am still having the problem when backing up the server. Below is an excerpt from the log. I tried running the back up as both the "logged in" user and then specifically as an administrator with the same results. Next, I guess I'll try running an unattended back-up to see if running as the built-in system account helps. All of these files backed-up fine under version 5.6.

 

 

File "C:\Documents and Settings\Administrator\NTUSER.DAT": can't read, error -1020 (sharing violation)

File "C:\Documents and Settings\Administrator\ntuser.dat.LOG": can't read, error -1020 (sharing violation)

File "C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat": can't read, error -1020 (sharing violation)

File "C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat.LOG": can't read, error -1020 (sharing violation)

File "C:\winnt\system32\config\default": can't read, error -1020 (sharing violation)

File "C:\winnt\system32\config\default.log": can't read, error -1020 (sharing violation)

File "C:\winnt\system32\config\sam": can't read, error -1020 (sharing violation)

File "C:\winnt\system32\config\sam.log": can't read, error -1020 (sharing violation)

File "C:\winnt\system32\config\security": can't read, error -1020 (sharing violation)

File "C:\winnt\system32\config\security.log": can't read, error -1020 (sharing violation)

File "C:\winnt\system32\config\software": can't read, error -1020 (sharing violation)

File "C:\winnt\system32\config\software.log": can't read, error -1020 (sharing violation)

File "C:\winnt\system32\config\system": can't read, error -1020 (sharing violation)

File "C:\winnt\system32\config\system.alt": can't read, error -1020 (sharing violation)

Link to comment
Share on other sites

1) Check the Retrospect Launcher Service to make sure it is running under the "system account"

 

 

 

2) Make sure you are backing up C: and not a subvolume of the Windows directory

 

 

 

3) Is this a local backup of the disk or is this backup of another computer via filesharing?

 

 

 

These files are normally copied as part of the snapshot using a Microsoft API. Retrospect normally would not attempt to backup these files directly.

 

 

 

If you go to configure>Backup Sets and get properties on the snapshot, does it display "registry" as being backed up?

Link to comment
Share on other sites

1) Check the Retrospect Launcher Service to make sure it is running under the "system account"

 

yes, it is running under the local system account.

 

2) Make sure you are backing up C: and not a subvolume of the Windows directory

 

yes, it is backing up the entire c: (note the other file sharing errors in the documents and settings directory)

 

3) Is this a local backup of the disk or is this backup of another computer via filesharing?

 

it is a local backup of the disk that Retropect is installed on.

 

4)If you go to configure>Backup Sets and get properties on the snapshot, does it display "registry" as being backed up?

 

yes, registry is listed under the "contains" area of the snapshot properties.

Link to comment
Share on other sites

This would indicate that even though you get these errors, the Microsoft API is backing up the registry. For some reason we are not "excluding" files that we would normally skip during the copy phase.

 

Is this happening with any other users on the network?

 

Is Retrospect installed in the default path?

Link to comment
Share on other sites

Nope, it is not happening to any other users, just the server itself.

 

No, Retrospect is not installed in the default path (or drive). So, maybe that is what is confusing it? Interesting since it was never a problem before.

 

Thanks for your help.

 

-Craig

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...