VSS and Keriver Restore!

[Amit]

Originally Posted by King of Rapture

Good decision. And, there is another one which I told you in PM, which also use proprietary driver rather than vss.sys

Use both of them and you never know one day which one will come handy. Consider it two insurance policies.

Best regards,

KOR!

That software gives error big time. I've sent you pm. Thank you for all your help KOR.

[aladdin]

Originally Posted by ams963

That software gives error big time. I've sent you pm. Thank you for all your help KOR.

You are the first one who has complained about this. It is a rock solid software. Go to advanced option and select some other driver for locking your hard disk.

Best regards,

KOR!

[Amit]

Originally Posted by King of Rapture

You are the first one who has complained about this. It is a rock solid software. Go to advanced option and select some other driver for locking your hard disk.

Best regards,

KOR!

I am not complaining my friend. Please understand that my particular system is causing this. Anyways, I will try it again. On that note, can I use two imaging software together like you said two insurance policies? Macrium and the other one(if I can get it to work of course)?

[aladdin]

Originally Posted by ams963

I am not complaining my friend. Please understand that my particular system is causing this. Anyways, I will try it again. On that note, can I use two imaging software together like you said two insurance policies? Macrium and the other one(if I can get it to work of course)?

Something is wrong with your setup. You are making backups, have you tried to restore the image. I am not sure if you will be able to restore the image.

I use four imaging programs, everyday one to make an image!

[Amit]

Originally Posted by King of Rapture

Something is wrong with your setup. You are making backups, have you tried to restore the image. I am not sure if you will be able to restore the image.

I use four imaging programs, everyday one to make an image!

I am yet to restore a hot image. I restored cold images with Keriver Restore many times without any problem.

And thanks for confirming. I think I will try using at least two apps.

By the Macrium took 17 minutes to make a hot image of system of size 15 gb.

How does that seem? Is it too slow compared with the time taken with vss hot image?

[aladdin]

Originally Posted by ams963

I am yet to restore a hot image. I restored cold images with Keriver Restore many times without any problem.

And thanks for confirming. I think I will try using at least two apps.

By the Macrium took 17 minutes to make a hot image of system of size 15 gb.

How does that seem? Is it too slow compared with the time taken with vss hot image?

Under your circumstances, you should do only COLD images, like you did with 1-Clk Restore. Have Macrium Reflect available as bootment, and you can than do COLD images with assurance.

Best regards,

KOR!

P.S. Also the COLD images capture your "Restore Points", where as HOT images with VSS don't.

[Amit]

Originally Posted by King of Rapture

Under your circumstances, you should do only COLD images, like you did with 1-Clk Restore. Have Macrium Reflect available as bootment, and you can than do COLD images with assurance.

Best regards,

KOR!

P.S. Also the COLD images capture your "Restore Points", where as HOT images with VSS don't.

But I use XP and as Nick from macrium forum has said I can use vss alternative pssnap.sys of macrium reflect without any problem. It will not backup open files and documents. And it will not backup and restore vss aware apps like ms exchange and ms sq server app.

I think I will be alright. Anyways, I will be switching to linux os in a year's time as support and development of XP comes to an end in 2 years.

[Amit]

Originally Posted by King of Rapture

You are the first one who has complained about this. It is a rock solid software. Go to advanced option and select some other driver for locking your hard disk.

Best regards,

KOR!

Okay I finally got it working. I took a hot image without vss no prob.

[pajenn]

hope you already got vss fixed but if not maybe this might help: http://freetechanswers.blogspot.fi/2...me-shadow.html

i had that bookmarked from some time ago when i was dealing with a vss issue and just came across it again. i don't remember if it worked though.

also an observation: i tried drive snapshot and macrium reflect on a virtual xp machine (just to compare performance) and for some reason macrium failed to get vss to work (and reverted to using pssnap.sys) whereas drive snapshot used vss fine.

[Amit]

Originally Posted by pajenn

hope you already got vss fixed but if not maybe this might help: http://freetechanswers.blogspot.fi/2...me-shadow.html

i had that bookmarked from some time ago when i was dealing with a vss issue and just came across it again. i don't remember if it worked though.

also an observation: i tried drive snapshot and macrium reflect on a virtual xp machine (just to compare performance) and for some reason macrium failed to get vss to work (and reverted to using pssnap.sys) whereas drive snapshot used vss fine.

Okay I'll try that. And thank you for sharing your experience.

[Amit]

Sigh. It did not work. I think I'll go without VSS.

[TomAZ]

Originally Posted by King of Rapture

And, there is another one which I told you in PM, which also use proprietary driver rather than vss.sys
KOR!

I, too, have a VSS problem. Would also love to know this "other" one with the proprietary driver.

[Jim1cor13]

Perhaps the following will help. I ran into this on my wifes tower. It is XP SP2 and I fixed it, but it was not easy. Here is the text of some commands and actions to take. Sorry if any of the following is a repeat of previous solutions, just thought I would add this:

---
Fixing MS VSS errors

Problem

VSS Service Issue

Event Log Error

Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0×80070005.

Volume Shadow Copy Service initialization error: the COM classes cannot be registered [0x80004015].

Error: 0x8000ffff
C:\WINNT\system32>vssadmin list writers
vssadmin 1.0 – Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Error: 0x8000ffff

Resolution

1. Click Start, click Run, type Regedit, and then click OK.
2. Export the contents of the

HKLM\Software\Microsoft\EventSystem key
to a .regfile.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\
key to a .regfile.
3. Locate and then click the following registry subkey and Delete it
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Security
4. Exit Registry Editor.

Click start, Run, type cmd to open a command box

5. Register below DLL’s.

• cd /d %windir%\system32
• net stop vss
• net stop swprv
• regsvr32 ole32.dll
• regsvr32 oleaut32.dll
• regsvr32 vss_ps.dll
• vssvc /register
• regsvr32 /i swprv.dll
• regsvr32 /i eventcls.dll
• regsvr32 es.dll
• regsvr32 stdprov.dll
• regsvr32 vssui.dll (does not work in Windows XP)
• regsvr32 msxml.dll
• regsvr32 msxml3.dll
• regsvr32 msxml4.dll

6. Restart your machine
7. Problem should be resolved
---

Jim