ShadowProtect Desktop Edition question

Discussion in 'backup, imaging & disk mgmt' started by n8chavez, Jun 16, 2008.

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

    lodore Registered Member

    Joined:
    Jun 22, 2006
    Posts:
    9,065
    did you create the image with the installed version of shadow protect desktop or from the cd?
    there is a reason why im asking.
     
  2. n8chavez

    n8chavez Registered Member

    Joined:
    Jul 19, 2003
    Posts:
    3,336
    Location:
    Location Unknown
    The installed version. But there shouldn't be a difference, should there?
     
  3. lodore

    lodore Registered Member

    Joined:
    Jun 22, 2006
    Posts:
    9,065
    do you also have ATI installed?
    sometimes the ATI volume shadow copy service can cause problems with shadow protect desktop creating images. its been discussed at wilders before.
    there is a solution at the shadow protect desktop forums.
    im sure someone can find you the link.
     
  4. n8chavez

    n8chavez Registered Member

    Joined:
    Jul 19, 2003
    Posts:
    3,336
    Location:
    Location Unknown
    No, it wasn't installed at the time I made hte SP image.
     
  5. lodore

    lodore Registered Member

    Joined:
    Jun 22, 2006
    Posts:
    9,065
    have you had it installed previosly on that machine and may still have remaindents of it?
     
  6. n8chavez

    n8chavez Registered Member

    Joined:
    Jul 19, 2003
    Posts:
    3,336
    Location:
    Location Unknown
    The snapman driver was still there after uninstalling ATI. But I manually deleted it and flushed any Acronis reference from my registry.
     
  7. Peter2150

    Peter2150 Global Moderator

    Joined:
    Sep 20, 2003
    Posts:
    20,590
    What options did you select on restore.
     
  8. grnxnm

    grnxnm Registered Member

    Joined:
    Sep 1, 2006
    Posts:
    391
    Location:
    USA
    If the ShadowProtect backup image file that you created passed a verify after you created the image, but failed a CRC test when you tried to use it at restore time, then this means that the image file went bad, while it was sitting on your disk, sometime between the time you successfully verified and the time you attempted to restore. This has nothing whatsoever to do with ShadowProtect. It's most likely a hardware issue with the device on which the image is stored, or file system corruption within the file system on which the image file is stored.
     
  9. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,115
    Location:
    NSW, Australia
    n8,

    I'm unfamiliar with those errors. Did the error occur during the verify process immediately prior to restoring the image or did the error occur during the restore?

    I understand the image did verify when it was created. Did you verify again prior to restoring the image?
     
  10. grnxnm

    grnxnm Registered Member

    Joined:
    Sep 1, 2006
    Posts:
    391
    Location:
    USA
    The verify and restore operations are basically identical (see sbrun.exe syntax in the job detail view when it's executing). The only difference is that a verify doesn't send the image data anywhere (it goes to NULL) but the restore sends the data to the target volume.

    In essence, a restore IS also a verify as it does all of the same operations as the verify (read, decrypt, decompress, verify CRC).
     
  11. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,115
    Location:
    NSW, Australia
    Thanks. That's what I'm interested in knowing here. Whether n8 verified the image before restoring it. I suspect it wasn't verified at the last minute and the restore process hosed the partition.
     
  12. grnxnm

    grnxnm Registered Member

    Joined:
    Sep 1, 2006
    Posts:
    391
    Location:
    USA
    When you have backup image files that go bad while they're sitting on your disk (which files were, at some time, verified as being good), it's almost always caused by either hardware failure or file system corruption. You should carefully analyze your system event log for any entries from disk, ftdisk, dmio, ntfs, fastfat, or any other storage-related drivers (such as your RAID/SCSI miniport driver, if one is installed). Very often in these cases users will discover that they have event log entries indicating hardware failure. You should also do a chkdsk of all volumes on your machine ("chkdsk X: /F /R" -> replace X: with the drive letter of the volume you are repairing -> do this for each volume on your machine). The point is that when stuff like this happens you need to take it as a serious warning sign that your system is becoming unstable, either in the hardware or in the file system(s).
     
  13. n8chavez

    n8chavez Registered Member

    Joined:
    Jul 19, 2003
    Posts:
    3,336
    Location:
    Location Unknown
    I created a image of my active partitipn with SP and I got a weird looking log. I'm kinda worried about it; I need my images to be good and restoreable. I've uninstalled and reinstalled to no avail. Could someone help me with the highlighted issues.

    The image verification log looks like this, but I'm not sure it it finished successfully or not.

     

    Attached Files:

    • sp.png
      sp.png
      File size:
      40.6 KB
      Views:
      5
  14. Peter2150

    Peter2150 Global Moderator

    Joined:
    Sep 20, 2003
    Posts:
    20,590
    Hi n8chaves

    No it didn't finish correctly. Problem is with your VSS service. Google that expression Vss service is in a bad state and you should be able to find the fix.

    Pete
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.