I have a Surface Pro 3 running Windows 10, and it seems that backup fails with error "Backup aborted! - Write operation failed - Nätverksökvägen kan inte hittas" (network path cannot be found), unless I set the energy option to put the computer to sleep after a really long time like two hours. I would expect Reflect to temporarily inactivate standby and hibernate during backups and restores.

Not sure what you would expect write permissions on a network share to do about the target node's energy management settings if the remote machine isn't making appropriate allowance for those operations on its own. 


Regards, Richard V. ("Arvy")

I am of course not talking about the target node. I'm talking about the source node (on which the backup runs).

Sorry if I misunderstood, Henrik, but the only clue to which computer's energy management was involved was the "Write operation failed" message.  I suppose Reflect could and should signal activity to prevent local machine standby.  I'm surprised if it's letting the local drives go to sleep while active.  A write failure seems more like the remote target machine and/or its share connection.

Regards, Richard V. ("Arvy")

I have a HP Stream 8 tablet and I have to set the power to high-power or adjust the timeouts to Never or it will quit when making an image.

Yes, misunderstandings happen easily. It is not the local drive that goes to sleep - the backup destination is on a remote server - it is the client computer itself (or the maybe the network adapter). I don't think it is the target machine or its connection that is the problem. As I said, if set the energy option to put the computer to sleep after a really long time, the backup works, but if I leave it at it's default (15 or 30 minutes - I don't remember exactly), it fails.