Sharing Violation with backup software

Discussion in 'Ghost Security Suite (GSS)' started by HandsOff, Nov 11, 2005.

Thread Status:
Not open for further replies.
  1. HandsOff

    HandsOff Registered Member

    Joined:
    Sep 16, 2003
    Posts:
    1,946
    Location:
    Bay Area, California
    Hi - I have about three questions but I might post them separately to avoid confusion since they are not related.

    I have noticed that I get a few errors in my backup logs when I backup using Dantz Retrospect Express v5.6. It lists files in the ghost folder and states sharing violation.

    What is unusual is that out of all the files on the computer, system files, ect...this is the only one that this happens with.

    My guess is that this error will not effect my ability restore...of course I'm just guessing.

    I am used to seeing a different error message, with other files, but this one is a first for me. It almost appears as though retrospect cannot read the file at all, and not that the file has changed during the program run.

    I will copy some examples. How much of a problem do you think this is?

    +++++++++++++++++++++++++++++++++++++++

    File "$[1]K:\Program Files\GhostSecuritySuite\MDStandard.gsm$[2]": can't read, error -1020 (sharing violation)
    $[*20750] File "$[1]K:\Program Files\GhostSecuritySuite\rdstandard.gsr$[2]": can't read, error -1020 (sharing violation)
    $[*20750] File "$[1]K:\Program Files\GhostSecuritySuite\rdlogs\2005_11_keys.gsd$[2]": can't read, error -1020 (sharing violation)
    $[*20750] File "$[1]K:\Program Files\GhostSecuritySuite\rdlogs\2005_11_other.gsd$[2]": can't read, error -1020 (sharing violation)
    $[*20750] File "$[1]K:\Program Files\GhostSecuritySuite\rdlogs\2005_11_vals.gsd$[2]": can't read, error -1020 (sharing violation)

    +++++++++++++++++++++++++++++++++++++++++++++++++++

    - HandsOff
     
  2. nick s

    nick s Registered Member

    Joined:
    Nov 20, 2002
    Posts:
    1,430
    Hi HandsOff,

    Although I don't use Dantz, I would take the cautious route and disable RD while backing up. If Dantz cannot "read" the RD files, then I doubt it is able to back them up correctly. I have imaged before within Windows (using Image for Windows) with RD enabled and restored without any problems. However, imaging apps are designed to avoid sharing violations. Not sure, though, about Dantz.

    Nick
     
Thread Status:
Not open for further replies.