jmwills Posted August 28, 2012 Share Posted August 28, 2012 Good find. That's one reason why I like to create a restore point prior to joining clients to the server. Link to comment Share on other sites More sharing options...
Jason Posted August 28, 2012 Author Share Posted August 28, 2012 Good find. That's one reason why I like to create a restore point prior to joining clients to the server. A restore point on the SERVER or the CLIENT? Link to comment Share on other sites More sharing options...
jmwills Posted August 28, 2012 Share Posted August 28, 2012 Both...however, I can restore the server from a backup. Or just as easily create a snapshot as mine is a VM. Link to comment Share on other sites More sharing options...
ikon Posted August 28, 2012 Share Posted August 28, 2012 Glad to hear it's working. Link to comment Share on other sites More sharing options...
Jason Posted August 29, 2012 Author Share Posted August 29, 2012 Oh well. Spoke too soon. Appears my same client PC didn't wake again last night @ 2:24 AM for its scheduled backup window. Am starting to suspect a connectivity issue between the client and server. Not a lack of network connectivity on the client, but more an issue with the client's connector not establishing connectivity with the WHS2011 in a timely manner (and giving up). Also, I never had this issue until I virtualized my WHS2011 as a hyper-v VM on my WS2008R2 server box. Perhaps something is delaying the client's ability to locate the WHS2011 VM. I never have an issue doing manual backups of this client to the server; only seems to be challenging during the auto/scheduled backup task. Has anyone else experienced this? Link to comment Share on other sites More sharing options...
ikon Posted August 29, 2012 Share Posted August 29, 2012 It's tempting to blame it on the virtualization but, of course, that doesn't explain why the other clients work properly. Is there anything new in the logs?: Link to comment Share on other sites More sharing options...
jmwills Posted August 29, 2012 Share Posted August 29, 2012 What are the differences in the models of NICs on all the systems? Could it be the trouble one needs a driver update? Link to comment Share on other sites More sharing options...
gcoupe Posted August 29, 2012 Share Posted August 29, 2012 As I said over here, since it's a laptop, WOL is irrelevant if you're using WiFi. More likely is that you need to have your laptop plugged into your mains adaptor overnight for the scheduled task to run... Link to comment Share on other sites More sharing options...
ikon Posted August 29, 2012 Share Posted August 29, 2012 That makes a lot of sense. Link to comment Share on other sites More sharing options...
gcoupe Posted August 30, 2012 Share Posted August 30, 2012 (edited) I've now tracked down the reference to the need for laptops to be plugged in for the backup to occur. It is in Microsoft's Technical Brief for Client PC Backups. The money quote: Laptops and other battery-powered computers must be plugged in to AC power to be automatically backed up. Although the home computer on battery power will be awakened, Windows Home Server will recognize it as battery-powered and automatic backup will not initiate. Edited August 30, 2012 by gcoupe Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now