Hi Thomas,
thanks for your help! As the Server is not running in production, the device has no clients with SEP Client installed. (only the SEP client + SEPM on the server).
It behaves like this:
a) Only SEPM on the server: Everything is fine (disks are going into sleep-mode)
b) SEPM + SEP client: No sleep.
Follwing up on your hint regarding the lack in function SEP 12 SMB. I downloaded the trial of SEP yesterday (so the full version), deinstalled SEP SBE and installed the full version SPEM ans SEP client (only on the server again).
--> Here everything is the same (no sleep when client installed)!
BUT: If I set the 'heartbeat' intervall longer (5h) the plates are going into sleep-mode :-)
I was then interessted if the 'heartbeat'-signal wakes up the server-data drives and tried the following: Setting the 'timeout' for sleep-mode of the harddisks to 2min (so switching of after 2min IDLE) and the heartbeat intervall to 5min. Results: The disks are going into sleep after 2min, but waking up after a few minutes. :-(
So, the big questions:
1) Is it the server, restarting the disks after getting the data from the clients, or is it the client itself:
I installed a client on on PC, conected to the server and w/o the client on the server. Here everything is OK --> seems that the client intself causes the problem
2) How to handle this? What exaclty is the client sending upon a hearbeat signal? The error occurs independent of the choosen mode (push or pull).
Does anyone know what to do, or how to configure to let the poor harddisks sleep upon a heartbeat signal?
Many thanks!
Cheers
Steven