Backup may fail for various reasons. One could be the fact, that the updated creates a copy of the old OS folders on the same drive and therfor free disk space gets exhausted to a point, that a volume snapshot is no longer possible.
Just for this post I enforced the update to build 1607 to my home PC, which is connected with Windows Home Server 2011 and did not automatically receive the patch yet by installing the update from an external media.
After that I faced some issues with network connectivity (may be something between Windows, network card drivers and ESET Endpoint security. While I was still troubleshooting, it started to work again.)
Windows Home Server Connector never ceased to work properly with existing connectivity, Dashboard works and backup could be launched and completed successfully too.
For your issues I would recommend to check the event log for more detailed error messages, since those would allow better support.
Also you can try to:
- check free disk space (should be more than 10% on each backed up volume including the hidden one)
- eventually configure backup to exclude the first drive
- run chkdsk /f from an administrative cmd prompt against the volume, on which backup fails
Regarding the dashboard:
- Can you connect via Remote Desktop client to your server? (user name: YourServer\Administrator, password the dashboard password)
- Does the dashboard launch from there?
- Is the network set to private network, and does no 3rd party security software interfer with the communication?
If there are indeed connectivity issues you can try to disable TCP/IP v6 on the clients network connection properties.
Best greetings from Germany
Olaf
