Apologies if I'm being stupid, but I'm having great trouble understanding how Lightsout backup and the Server Essentials 2012 backup work together (or fight with each other). I find the Lightsout documentation on this very unclear, and various threads have left me no wiser. I'd appreciate some help!
Here's the setup:
Lightsout is running nicely on the server. Before backups were set up, I established that the server hibernated when the clients were switched off. The server woke up when a client was powered up. (This behaviour broke when backups were set up.)
The server is Essentials 2012, with a number of client laptops: a mix of Windows 7, 8 & 10.
The Essentials backup window is 22:00 - 07:00.
No backup settings are currently made in Lightsout.
Here's what I'd like to achieve:
At the end of the working day all the clients are put to sleep or hibernate (or switched off completely, I don't care which).
Ten minutes after that, Lightsout hibernates the server.
Sometime during the night (22:00 - 07:00) the server wakes up, then wakes up the various clients in turn, backs them up, and puts them back to sleep / hibernate / shutdown (I don't care which).
Here's what actually happens (when I look at the uptime chart the next morning):
At the end of the day (about 17:15) the clients are put to sleep / hibernate. (I tell the team not to shut down their client laptops because I assume the server can't wake a completely shut down client - is that correct?)
The server does not hibernate.
Approximately 90 minutes after the clients were put to sleep / hibernate, they all wake up simultaneously (around 18:45, but I don't know why this happens). The clients then stay awake all night.
Later, from 22:00, some of the backups take place (but not all of them). The backups are spread wide apart in the 22:00 - 07:00 window with lots of time when nothing is going on at all. The clients do not go back to sleep / hibernate after their backups.
...can anyone suggest what combination of settings I should be using to get the desired behaviour? Here are the sort of things that are confusing me, but I can't find definitive answers (and each experiment I do takes 24 hours to give any results!):
I know I can specify clients' individual backup times in Lightsout, but I don't know how long a client's backup will take, so I could have backups overlapping each other and causing a traffic jam. Should I worry about this?
If I set Lightsout backups, what do I set for the Essentails backup window? What if it's not long enough to get all the backups done?
If I make settings in the Lightsout backup dialog do I have to complete everything in that dialog box? Does this make the Essentials 2012 backup settings redundant? What about the Essentials 22:00 - 07:00 backup window, does that matter any more?
I tried setting client backup times in Lightsout with an end action of 'sleep'. The backups didn't happen at all and clients all spontaneously went to sleep in the middle of the working day (the server / clients clocks all match, I checked).
Can Lightsout wake up a client laptop that is completely shut down?
Thanks for reading this long post and sorry if these seem like stupid questions. I already have WHS2011 / Lightsout running perfectly on another setup (where my backups take place during the day), but nocturnal backups are a new level of complexity for me!
Christopher wrote: << And to clarify, if you want multiple backup drives to be cycled offsite, you MUST connect all of them at the same time when you set up the backups. >>
I'm not clear about this. To the best of my recollection, I never connected both of my backup drives to the server at the same time, For test purposes, I just initiated a recovery (using the WHS Installation Disk) with each of them hooked up. The one that has been offsite and the one that backed up last night were both found by the "Repair an existing installation" procedure.
Perhaps I'm misreading your clarification.
My WHS v1 (home build) starting misbehaving and finally needed a new system disk.
After lots of threads, trial and errors, AF and non-AF drives, and lack of the Server Reinstallation choice it has finally progressed.
Weeks of frustration.
My recent attempts proceeded well but all ended up without the rebuilding of the Storage Pool (6 drives).
The drives are detected and show up as "not added" in Server Storage and as "non managed" in Disk Management.
There is no C:\fs on the SYS volume.
It appears that the RebuildPrimary stage of the reinstallation, mentioned by some posters, was not successful.
Has anyone found a way to force the rebuilding of the Storage Pool on reinstallation?
I have tried X: Files v1.5.5 and the original Microsoft Disk with the same outcome.
[My next step will be to migrate the "shares" and "folders" manually - it would have be quicker to have done this initially.]
I can use all feature using the connector software in my local network. But when on the road, I connect via xxx.homeserver.com. Login works, can access my shared folders, but when I want to access the WHS 2011 Server Dashboard or my WHS 2011 Outlook, I got an error like this: The Computer can't connect with the Remotedesktop-Gatewayserver. Contact your network admin. (translated from german) . On an Windows 7 Home and on a 7 Pro Computer this worked. The same problem happens on my Windows 10 tablet. Only local working with the connector software. Windows 10 is version 1607.
Any suggestions what this is?