Answered by:
Changed My Client's 2nd Hard Drive - Getting Incomplete Backup

Question
-
Hi, all. I'm anxious to find the answers to two problems I'm having with my HP WHS system.(1) Did the problem get resolved regarding restoring large files from WHS to a client? I saw that some people reported that problem, but haven't found whether there's a solution. Trying to do a restore dies when WHS encounters a large file.(2) On one of my WHS clients (a fully updated Vista Home Premium system), I have two physical internal hard drives. The OS and software go on the first drive (C:) and my data is on my 2nd drive (F:). I swapped out the 2nd hard drive for a larger one. I quick formatted it using the Windows Disk Management utility, I used the NTFS format (same as the drive I replaced), and I reloaded all the data from an external hard drive.The client seems to be working just fine ... EXCEPT as I tried to do a backup to my HP WHS box, the backups are logged as incomplete. As I looked at the results in the Backup Details window, WHS seems to be looking for the old smaller hard drive. Note that the new hard drive has the same drive letter as the drive it replaced, but I guess that's not enough to satisfy WHS.I figure that WHS doesn't appreciate the change of drives, so I thought the solution would be to reconfigure the backups for this client. However, as I tried to reconfigure the backup configuration for this client and WHS tried to collect information about the system, I get this message: "The computer is not online or Windows Home Server cannot access the computer's hard drive. Please make sure the computer is powered on and connected to your home network."Is there a way to circumvent this problem without removing the affected client from WHS and re-adding it? Have we seen this problem before? Any help would be greatly appreciated. Thanks in advance and have a good one.TonySaturday, August 22, 2009 12:13 AM
Answers
-
Richard ... I thank you for your reply. However, I'm trying to get a clarification for your comment I quoted above.
Bare Metal Restore means to restore one (or more) partitions to a hard drive, either by using the Restore CD or by using ClientRestoreWizard.exe (which is in C:\Program Files\Windows Home Server).
Could you please clarify what you meant by a "bare metal restore"?
If I had to guess, I'm supposing you might have meant that I should have done one of the following: (1) Install the new drive, but don't format it, or (2) Install the drive and format it, but don't assign a drive letter. Could you please clarify?
If I understood "bare metal restore" correctly, using laymen's terms, it seems you might be saying that WHS might allow a client backup reconfiguration if a drive on the WHS client is missing. Presently, though, WHS does not appreciate new drives that have already been incorporated as a functioning part of a client.
Not exactly. I know you can add new drives to a client and re-configure your backups to back them up. Also, if you had disconnected your old drive, then restored your latest backup of that drive to your new drive, that probably would have worked. However, you didn't do that. You replaced (swapped) out the old drive for the new one (which apparently WHS doesn't like).
For those who haven't read all the messages in the thread, that was my problem: I replaced a perfectly good drive in my WHS client with a larger one; I formatted the new drive, assigned a drive letter, started the WHS Console, and then tried to perform a backup, but WHS would not complete the backup and the attempts to reconfigure my backup for that client failed as well. It seemed my only option was to remove the client from WHS and re-add it; that worked, by the way, but it seems there ought to be more flexibility within WHS to allow this type of hardware change.
At the very least, it would have been nice if renaming the client and adding it as another computer would have worked. I tried this, however, WHS easily recognized it was the same system and merely changed the name in the computer list without giving me the chance to add it as a new client.
Thank you again. Richard and all. By the way, I had failed to use the "Vote as helpful" feature until now. Note that if I don't vote on someone's message, it simply means their suggestion didn't help me, but I still sincerely appreciate everyone's inputs. My warm thanks to all !
Sincerely,
Tony, the WHS Novice- Marked as answer by Tony Rony Monday, August 24, 2009 12:50 AM
Monday, August 24, 2009 12:22 AMModerator
All replies
-
Sure Windows Home Server cannot know that your drive change has been intended.
So in the console select the computer on the Computers and Backups tab and select Configure Backup.
The old disk should be unchecked now, the new disk selected.
Confirm the change and all is right.
Regarding large file issues I have seen this sometimes in context with either bad network drivers/components on one of the components or mass storage drivers which caused the ystem to hang up. (If you copy a large file locally on the system and the system does not go into non response, the network remains as potential main cause.)
You might also have disk issues, so check the event logs on client and server.
Best greetings from Germany
OlafSaturday, August 22, 2009 2:40 PMModerator -
Olaf,
I genuinely appreciate your reply.
Regarding the "large files issue," I will try to be more mindful and look for errors on the server and client as you suggested.
Regarding the changed disk, your recommendation did not work on my system. That is one of the things I tried repeatedly, however each time I try to reconfigure the backup and WHS tries to collect information about my client, the progress indicator takes about ten seconds to reach the end, which seems to indicate it was really working, but it always ends with the message, "The computer is not online or Windows Home Server cannot access the computer's hard drive. Please make sure the computer is powered on and connected to your home network. " Fearing that my Zone Alarm might somehow be interfering, I even disabled the firewall, but the results were the same.
Note that I also tried to rename my client. To my surprise, after restarting my client and starting the WHS Console, WHS realized it was the same system and changed the name of my client in the computer list.
I also tried running discovery.exe from "C:\Program Files\Windows Home Server" on the client, but all efforts to include my new hard drive fail with the error message shown above (underscored).
Are there no other ideas regarding this particular issue regarding changing disks on a client?
Thanks very much.
TonySaturday, August 22, 2009 3:10 PM -
Yes, I've seen this problem too. Easily recreatable.
The only work-around I've been able to find is to re-install the original hard drive, configure the backups so that the hard drive isn't backed up, then you can remove the old drive, insert the new drive, then go back into configure backups to enable backups on the new drive.Saturday, August 22, 2009 3:26 PM -
The only work-around I've been able to find is to re-install the original hard drive, configure the backups so that the hard drive isn't backed up, then you can remove the old drive, insert the new drive, then go back into configure backups to enable backups on the new drive.
Richard / All,
This is an excellent idea and I have every confidence it would work. However, what if the old drive were dead? Isn't this one of the main purposes for which WHS was designed? To restore a system after a drive failure?
So, I hope I'm not sounding unappreciative or sarcastic ... That's not my intention at all . But imagine a WHS user's frustration if it's true that a failed drive on a client might render further use of that WHS client's backup unusable.
I'm hoping there's a fix for this that does not require me to remove the client from WHS and resave it. I also recognize the possibility that there's something "wrong"/non-standard with my network or client, but since my system is stable (no BSODs) and seems to work quite well under all other circumstances, this would leave me with the very strong impression that WHS is unimaginably "sensitive," for lack of a better term, and that the slightest deviation from Microsoft's development/test environment can effectively prevent WHS from performing one of its core functions.
Thanks, Richard, and everyone. I'm certainly hoping WHS is not as vulnerable as it presently seems to be. That's not a nasty comment ... Just an objective observation. I truly hope I'm the one who's in the wrong. Thanks very much for everyone's contribution.
Sincerely,
TonySaturday, August 22, 2009 3:47 PM -
I think it's been bugged on the connect website - so hopefully Microsoft will come up with a fix for this. I agree, while it's fine for failing drives, if you get one that just goes dead, you're a bit stuck.
However, I don't think it's a total disaster, as the following would be true:
1: You've restored your latest backup onto the new hard drive, giving you a working OS
2: Deleting all your old backups, then reinstalling the connector software will get you back into a working state.
It's not ideal, as I like to keep as one of my backups a completely clean OS install with just Office, Anti-virus and other default apps installed, and you'd lose this. But it's not the end of the world. The backup would have done its job of rescuing your desktop PC from a total hard drive failure.Saturday, August 22, 2009 3:50 PM -
I think it's been bugged on the connect website - so hopefully Microsoft will come up with a fix for this.
Richard ... I sincerely appreciate your reply. I recognize that WHS is a complex "beast" (not meant negatively) and I certainly cannot do better myself. I will be patient and hope something becomes of this.
But it's not the end of the world. The backup would have done its job of rescuing your desktop PC from a total hard drive failure.
Um, can you show me where this "connect website" is located? I seem to remember references to this in other forum posts, but don't know anything about it. I'd like to check myself to make sure that this issue is being tracked.
Thank you again, Richard. I appreciate your help ... And Olaf, too.
Tony
Saturday, August 22, 2009 4:51 PM -
You could also try to uninstall the Connector software, delete the remains in the clients registry and reinstall the connector software after client reboot.
The Connect site is described in the sticky thread on top of this forum.
Best greetings from Germany
OlafSaturday, August 22, 2009 5:05 PMModerator -
You could also try to uninstall the Connector software, delete the remains in the clients registry and reinstall the connector software after client reboot.
Olaf ... That sounds like a good idea. Even though my knowledge of a PC's inner workings is very modest, I'd certainly be willing to give this a try if you'd be so kind as to direct me to the correct area of the registry. The registry is not something I often play with, but I'll be sure to make a system restore point first and hopefully that will be adequate protection in case I make improper edits to the registry.
Thank you again for your help.
With great appreciation,
Tony
Saturday, August 22, 2009 5:18 PM -
Olaf ... That sounds like a good idea. Even though my knowledge of a PC's inner workings is very modest, I'd certainly be willing to give this a try if you'd be so kind as to direct me to the correct area of the registry. The registry is not something I often play with, but I'll be sure to make a system restore point first and hopefully that will be adequate protection in case I make improper edits to the registry.
Thank you again for your help.
With great appreciation,
Tony
The registry path is HKLM\Software\Microsoft\Windows Home Server.Saturday, August 22, 2009 7:38 PMModerator -
For #2. Did you try restoring the data to the new drive with WHS. I think you should be able to run ClientRestoreWizard. It sounds like you just copied the data back from and external drive. Maybe it will recognize the drive after the restore???Saturday, August 22, 2009 8:33 PM
-
KCXLT,
Actually, filling the new drive from my WHS backup did occur to me, but I opted for using a USB-connected external drive because I assumed that might be faster than going through my 10/100 speed network.
However, that gives me an idea. I used the Restore CD (is that the correct name for it?) just once before long ago and it worked fine. I wonder whether using the Restore CD and retrieving just one file (if that's possible) might initiate a process that begins with recognizing and accepting the "identity" of the new drive. I don't frankly recall whether the restore process is an all-or-nothing affair.
First I'll try it from the WHS Console, but I don't think that will do the trick. I somehow think that using the Restore CD might work, IF it allows a partial restore. I'll see and report back.
Thank you, and thank you to Kariya21 too.
Tony
Saturday, August 22, 2009 9:29 PM -
Yes, you can restore single partitions with the restore CD.Saturday, August 22, 2009 10:07 PM
-
Yes, you can restore single partitions with the restore CD.
Richard, Olaf, KCXLT, and Kariya21,
I'm fixed, but I had to do it the hard way: Remove the client computer from the WHS environment and re-add it. For me, that was a scary proposition. Even though I've never had a sudden and total failure of a hard drive in all my 20-plus years of using them, wiping out my only backup while preparing another one was a scary proposition.
Uninstalling the Connector software from my client and re-installing it still would not allow WHS to accept my new hard drive that I use as my data volume. I wonder whether it would have worked if I removed the old drive from the backup configuration at any time prior to installing the new drive.
I'm a former Solaris/UNIX sys admin and if I hadn't gotten so flustered, I would have made excellent notes about my experience to share with you. However, when I get frustrated as I began to get, I started to try "undocumented/unsupported" ideas that you'd consider risky, perhaps, and that's when I stopped taking notes.
On my system (a fully updated Vista Home Premium system), some software that I install actually installs properly, but after clicking the Finish button for the program's installer, I occasionally get a Windows message saying the installation failed, and that was exactly the case each time I installed the WHS Connector software; it was a major distraction and annoyance since it seems the Connector actually was properly installing.
Here's one odd thing ... After removing the WHS Connector from the client and removing the client from WHS, I was not able to re-install the Connector software from the WHS server. I used the CD that came with my HP EX470 and then I re-added the client to WHS; that new backup took a really long time, of course, but initially there was no problem.
However, for that initial backup, I intentionally did not include my data volume, Drive F:. After the initial backup of C: and D: (my system's factory configuration partition) completed, I made some adjustments to the arrangement of my data. Then I reconfigured the backup to include F: (my data volume) and proceeded to perform another backup. These backups repeatedly failed with this message: Backup failed because your computer restarted while the backup was running . That's not true, though; I was actually running the Console on the system being backed up. The backup worked properly for D: (the factory configuration partition), but the backup was dying as it was examining C: for changed sectors.
That consistent behavior (it died the same way three times) gave me no clues, but through some things I've read, I realized that if the Connector software is not the most current version, this might be the cause. The error msg included a link to where I could download WHSConnectorInstall.exe, and re-install the current version did the trick.
I know it's easier said than done, but non-savvy users (that includes me) might not be so keenly aware that these two components (the Connector and WHS itself) are separate, nor would they necessarily realize that one sits on the client and the other is on the server. Even though I know "enough to be dangerous," I forget that myself sometimes. In plain language, I'm simply saying that I wish using WHS were not so tricky.
Note, also, that I use WHS only for local backups. I haven't tried any remote backups, I don't have any shares, etc ... Only backups. I suspect that WHS might be far more popular if it weren't so tricky to use. I also am seriously disappointed by realizing that installing a new hard drive would cause as many problems for me as it did. I surely realize it might not be fair for me to expect WHS to be as foolproof as using a fork and spoon, but in my humble opinion, it's presently much more complicated than it ought to be.
I thank you all for your help. I'm back on track, for now, but I surely hope to not have difficulties like that any time soon. Thank you again, folks. I sincerely appreciate all your help. Have a good one!
Tony
- Proposed as answer by kariya21Moderator Monday, August 24, 2009 12:07 AM
Sunday, August 23, 2009 5:36 PM -
I'd need to test it - might get chance tomorrow or Tuesday, but I think if you suffered a total failure of a hard drive, a bare metal restore onto that drive keeps the status quo, and the backups will be happy and still be able to be configured.
I think this problem only arises if you have a working drive, shut down your PC, and swap the drive for a new one, without doing a restore back onto it from the home server.- Edited by Richard D Holland Sunday, August 23, 2009 6:14 PM Typo
Sunday, August 23, 2009 6:14 PM -
... I think if you suffered a total failure of a hard drive, a bare metal restore onto that drive keeps the status quo, and the backups will be happy and still be able to be configured.
Richard ... I thank you for your reply. However, I'm trying to get a clarification for your comment I quoted above.
Could you please clarify what you meant by a "bare metal restore"?
If I had to guess, I'm supposing you might have meant that I should have done one of the following: (1) Install the new drive, but don't format it, or (2) Install the drive and format it, but don't assign a drive letter. Could you please clarify?
If I understood "bare metal restore" correctly, using laymen's terms, it seems you might be saying that WHS might allow a client backup reconfiguration if a drive on the WHS client is missing. Presently, though, WHS does not appreciate new drives that have already been incorporated as a functioning part of a client.
For those who haven't read all the messages in the thread, that was my problem: I replaced a perfectly good drive in my WHS client with a larger one; I formatted the new drive, assigned a drive letter, started the WHS Console, and then tried to perform a backup, but WHS would not complete the backup and the attempts to reconfigure my backup for that client failed as well. It seemed my only option was to remove the client from WHS and re-add it; that worked, by the way, but it seems there ought to be more flexibility within WHS to allow this type of hardware change.
At the very least, it would have been nice if renaming the client and adding it as another computer would have worked. I tried this, however, WHS easily recognized it was the same system and merely changed the name in the computer list without giving me the chance to add it as a new client.
Thank you again. Richard and all. By the way, I had failed to use the "Vote as helpful" feature until now. Note that if I don't vote on someone's message, it simply means their suggestion didn't help me, but I still sincerely appreciate everyone's inputs. My warm thanks to all !
Sincerely,
Tony, the WHS Novice
Sunday, August 23, 2009 7:58 PM -
Richard ... I thank you for your reply. However, I'm trying to get a clarification for your comment I quoted above.
Bare Metal Restore means to restore one (or more) partitions to a hard drive, either by using the Restore CD or by using ClientRestoreWizard.exe (which is in C:\Program Files\Windows Home Server).
Could you please clarify what you meant by a "bare metal restore"?
If I had to guess, I'm supposing you might have meant that I should have done one of the following: (1) Install the new drive, but don't format it, or (2) Install the drive and format it, but don't assign a drive letter. Could you please clarify?
If I understood "bare metal restore" correctly, using laymen's terms, it seems you might be saying that WHS might allow a client backup reconfiguration if a drive on the WHS client is missing. Presently, though, WHS does not appreciate new drives that have already been incorporated as a functioning part of a client.
Not exactly. I know you can add new drives to a client and re-configure your backups to back them up. Also, if you had disconnected your old drive, then restored your latest backup of that drive to your new drive, that probably would have worked. However, you didn't do that. You replaced (swapped) out the old drive for the new one (which apparently WHS doesn't like).
For those who haven't read all the messages in the thread, that was my problem: I replaced a perfectly good drive in my WHS client with a larger one; I formatted the new drive, assigned a drive letter, started the WHS Console, and then tried to perform a backup, but WHS would not complete the backup and the attempts to reconfigure my backup for that client failed as well. It seemed my only option was to remove the client from WHS and re-add it; that worked, by the way, but it seems there ought to be more flexibility within WHS to allow this type of hardware change.
At the very least, it would have been nice if renaming the client and adding it as another computer would have worked. I tried this, however, WHS easily recognized it was the same system and merely changed the name in the computer list without giving me the chance to add it as a new client.
Thank you again. Richard and all. By the way, I had failed to use the "Vote as helpful" feature until now. Note that if I don't vote on someone's message, it simply means their suggestion didn't help me, but I still sincerely appreciate everyone's inputs. My warm thanks to all !
Sincerely,
Tony, the WHS Novice- Marked as answer by Tony Rony Monday, August 24, 2009 12:50 AM
Monday, August 24, 2009 12:22 AMModerator