Power-off scheduler

I agree..this feature was in the original Readynas DUOs I had where you specified on and off times.

I used to have an on set once a week to fire it into life to do backups then had an off set every night such that if I turned the Duo on for something it would go off that evening and wake up again for its next backup job. Without the ability to specify off's it comes on does its backup and goes off but if I want to turn it on again then I have to leave it running all week until after the next on/off period so it goes off again

Martin

icy wrote:
The os4 power manager allows to program shutdown. This feature is missing in the Os6 manager that only allows power-up. Once powered-up a manual shutdown shoud be made.

I am not sure I completely understand the last sentence here.

I think there is a case for power-up by itself (turn on the NAS at 4:00 am, so the scheduled backup will run). It makes perfect sense for me to want the NAS turned on, whether it was turned off manually or on a programmed schedule (or by a loss of power). And programmed power-down by itself also makes sense.

This should work like similar programmed devices (for instance a programmed light switched). If I turn on the lights manually, the next programmed "off" still occurs. If I turn them off manually, the next programmed "on" does the same. There's also a "manual" button that allows me to disable/re-enable all programmed actions without deleting the schedule.

icy wrote:
The system should delay the shutdown if backup/reshape/tasks are running, but not when data are read/write from external connection.

I agree there ought to be an optional way to do this, but I don't think the system can accurately predict how long those ongoing tasks will take. Also, if there are several backup jobs scheduled, you want them all to complete - not just the ones that happen to be running when the shutdown time arrives.

Of course if there's a problem, the activities might never complete - and the admin should be alerted if that appears to be the case.

More explicit logging would be helpful. If I shut down the system during a backup (or a scrub) - programmed or not - there should be a log entry telling me that what was being aborted. On power up, the log should identify scheduled actions that were missed.

StephenB wrote:

icy wrote: The os4 power manager allows to program shutdown. This feature is missing in the Os6 manager that only allows power-up. Once powered-up a manual shutdown shoud be made. I am not sure I completely understand the last sentence here. I think there is a case for power-up by itself (turn on the NAS at 4:00 am, so the scheduled backup will run). It makes perfect sense for me to want the NAS turned on, whether it was turned off manually or on a programmed schedule (or by a loss of power). And programmed power-down by itself also makes sense. This should work like similar programmed devices (for instance a programmed light switched). If I turn on the lights manually, the next programmed "off" still occurs. If I turn them off manually, the next programmed "on" does the same. There's also a "manual" button that allows me to disable/re-enable all programmed actions without deleting the schedule.

that's exactly what i meant. Sorry for the imprecision :)

StephenB wrote:

icy wrote: The system should delay the shutdown if backup/reshape/tasks are running, but not when data are read/write from external connection. I agree there ought to be an optional way to do this, but I don't think the system can accurately predict how long those ongoing tasks will take. Also, if there are several backup jobs scheduled, you want them all to complete - not just the ones that happen to be running when the shutdown time arrives. Of course if there's a problem, the activities might never complete - and the admin should be alerted if that appears to be the case. More explicit logging would be helpful. If I shut down the system during a backup (or a scrub) - programmed or not - there should be a log entry telling me that what was being aborted. On power up, the log should identify scheduled actions that were missed.

My idea only concerns the currently running "tasks". Not the planned one. I don't want my nas to brick himself, if it trigger a shutdown 1 sec after a firmware upgrade was manually launched^.^'

If a running job take an eternity to execute, the nas should never shutdown. That seem logical to me, and is indeed an admin(me:D) concern :p

Like you suggested, scheduled jobs that was not run, should resume (if possible) and be logged (+ mail spam ) whatever the reason: power-off, crash, bad config etc...
But I think this should be made with an other "new feature" request ;-)