Recent content by azler

Does anyone have any more tricks I can try to use to get past this problem? I really dont want to give up on this. Rob

It is supported by Server 2008 but the commands you can run are limited. I do believe that /Cleanup-Image /RestoreHealth are for server 2008 r2. I ram the command on a server 2008 R2 and that option is there on Server 2008 you just get the DISM is not recognised as a command.

Thats interesting I didnt know you could use that with server 2008. Just mounted the VHDX file on widnows 8 and tried to run it from CMD: DISM /Image:G:\ /Cleanup-Image /RestoreHealth & Got a error about it not working on this type. Dism is not part of the server 2008 build so I cant use it...

I did verify the backup with acronis after completion and it said it was fine.. Its strange the sfc / startrep wont work correctly though..

I feel it might. Whats the next step in troubleshooting this? Could it still be a driver issue? I cant get it to produce a ntbtlog.txt file to see the last driver loaded.. This is seriously driving me mad now. The system was working and online when this backup was taken.. So I cant see if...

More info:

Unfortunately this was not the case due to storage and it was decided that a full week of full backups would be fine as any older would be useless with Ad changes / The exchange stuff that was running on in. Not how I would have done it but I didnt design the backup system.. Right I am now...

I have already done that and managed to pull the raw files outs which I can. I want to boot from it to export other configuration settings which you cant do from the raw file system for specific programs / services which were running on it. A new server is on order and I am hoping to be able...

You are not late to this thread at all! The more input the better. The 2008 SBS started life as a full production server happily working away. I was away when it all went tits up so someone else had to try and figure this out until I returned. From what he has told me it was a scheduled reboot...

I would suggest it being a 3rd part app but without any mini dumps I cant figure out what. Yea the USB3 is just external storage where the VMDK file resided and vmware workstation just points to that. I do have other VM's running from the USB this way and they work fine.

I cant see it being either.. If it was a faulty disk that broke it in the first place I would expect that error. But not it is a vmdk file which has had chckdisk ran on it it should have resolved that issue? & the VM does not know its booting off a USB drive as vmware workstation should mask...

Thank you I appreciate it. I have been very persistent with it and invested a lot of hours so far which normally I would have given up but with it being a SBS there is still some stuff I would like to retrieve. Do you think this is a windows issue or because im trying to migrate it to a vm...

I booted into a Windows 7 PE mode, Right click on the driver, Properties, Tools & ran it from there. I checked both options available and ran it. I have run it from the cmd in a previous attempt and i am sure it was the same result but I think this is a new restore since then so I will try...

I hope this is the right forum but I think my error is fairly generic across all the windows OS's. I have found myself is a fairly irritating position. My SBS 2008 server has failed and causing me a whole lot of pain in the process. There was a fairly comprehensive backup plan in place...