How to remove 'stuck' backup

vendredi 7 mai 2010 20:19

0

A PC that backed up successfully yesterday with a manual backup. This afternoon I have found it saying backing up 28% that never advances. I have tried stopping the backup but I get a message saying that it was unable to connect to the backup service. I Similarly cannot remove the computer for the same reason. Re-booting does not clear it.

My server has been subject to random shutdowns without an automatic restart and this might have happened during its backup. I have changed power supply, discs, motherboard and SATA cables to resolve the shutting down. The server itself has a critical error but it will not tell me what it is.

Current set-up is Intel 160Gb SSD as main disc connected to 6Gb/s port, 3 2TB WD discs, Core i5 660, 4GB RAM, 16TB DroboPro connected via iSCSI but not in the pool; used as a backup of the data via sync with the Vail files. DroboPro shared to allow media access.

Many thanks, just trying to avoid third build this week.

Ian

Toutes les réponses

vendredi 7 mai 2010 20:47

1

Ian,

Do you see the 28% on the Dashboard, Launchpad, or both? Also, did you reboot the client or the server? If you could gather the logs on the server and client then file a bug on Connect, it would be greatly appreciated. Please let us know if you have any questions on collecting the logs.

Connect: http://connect.microsoft.com/WindowsHomeServer

Thanks for using the Vail beta!
Robert Dhaene [MSFT]
Post is "AS IS" and confers no rights.
vendredi 7 mai 2010 21:11

0

Dear Robert,

Thanks so much for the quick reply. I bounced the PC and that has made things somewhat better as I was able to start a manual backup from the launchpad on that machine. However the dashboard still shows stuck at 28%. The backup went rapidly to 25% (last checkpoint I assume) and has taken some 2 minutes to continue onto 30%. I will let that finish and bounce the server when I can (need to be careful as someone is in the theater watching a movie on AppleTV that is streaming from iTunes running on Vail with its library currently on the DroboPro connected to Vail. They will be grumpy if I drop the server right now.

By the way I am delighted about the disc performance on Vail. To test it I played a high def movie on AppleTV served from Vail, also played a ripped ISO Blu-Ray image from the iSCSI share on Vail whilst backing up my PC. Neither movie even skipped a beat and the backup did not slow down. Hail the chunks.

I will collect logs now.

Ian
vendredi 7 mai 2010 21:40

Modérateur

0

I believe there is a known issue with regards to leaving the dashboard open during a backup. That said, can you please file a bug report on Connect , with logs from server and affected client?

I'm not on the WHS team, I just post a lot. :)
vendredi 7 mai 2010 21:52

0

I am having difficulty getting the C:\Users\Administrator\AppData\Local\Temp\2\ColoradoLogs.zip to be uploaded on connect. It sits there for about 5 minutes then page cannot be displayed. Also I did not see a CAB ID using the collector tool.

Ian
vendredi 7 mai 2010 22:06

0

The log collector finishes saying that it failed to send the report, thus no CAB ID. Also I cannot attache the Colorado zip file to my Connect bug report.

Ian
lundi 10 mai 2010 14:56

0

Ian,

I found your bug on Connect, and have a quick question. When you restarted the backup from the Launchpad, the percentage completed increased on the Launchpad but still says 28% on the Dashboard? Also, would you mind attempting the log collector again and see if a CAB number is listed on the CMD shell window that is opened?
Robert Dhaene [MSFT]
Post is "AS IS" and confers no rights.
lundi 10 mai 2010 15:11

0

Dear Robert,

Yes, the launchpad backup progressed and finished yet the dashboard still showed the original locked on 28%. However yesterday I was pleased to see that it had cleared itself, perhaps by going through an auto cycle.

I tried to run the collector tool again yesterday for another bug but it is still failing trying to send the report. Do you have any suggestions for the collector as I have another bug where I cannot add a fifth client and another client who keeps having a service stop. I have not managed to get remote access to work yet, perhaps this is related to the connector issue.

Thanks,

Ian
lundi 10 mai 2010 15:37

0

"still failing trying to send the report"

The Vail Log Collector.doc has a Note about a registry correction when the report "does not send".

Vail Log Collector

You might take a look at that -

--
Don

"dremmel" wrote in message news:795749fb-7cdd-4469-a89a-72fee425c2b9...

Dear Robert,

Yes, the launchpad backup progressed and finished yet the dashboard still showed the original locked on 28%. However yesterday I was pleased to see that it had cleared itself, perhaps by going through an auto cycle.

I tried to run the collector tool again yesterday for another bug but it is still failing trying to send the report. Do you have any suggestions for the collector as I have another bug where I cannot add a fifth client and another client who keeps having a service stop. I have not managed to get remote access to work yet, perhaps this is related to the connector issue.

Thanks,

Ian
lundi 10 mai 2010 20:07

0

Dear Don,

Do you mean the instruction in the Collecter tool notes referring to checking that the registry entry dontshowui is not set to 1? I did check and it is set to zero.

Ian
lundi 10 mai 2010 20:25

0

Yes that is what I meant, also, it resets itself back to 1 so every time before I run the Collector tool I check that it is "0".

--
Don

"dremmel" wrote in message news:8775c0d6-3538-4c68-904f-96f8df63a1cb...

Dear Don,

Do you mean the instruction in the Collecter tool notes referring to checking that the registry entry dontshowui is not set to 1? I did check and it is set to zero.

Ian