Hi folks, I've Bareos dir and sd installed on different machines. While dir machine (vm) is running around the clock the sd one doesn't because I only need sd twice a day for a few minutes/hours. On the other hand the sd machines consomes much more energy because it's a hw device with big zfs disk pool.
In general, I start all my backup jobs lets say at 12 a.m. and p.m. This I'd like to do by scheduler. So far so good. What I want to do are two things: 1. start the machine with the sd by wakeonlan *before* starting all my (scheduled) bareos jobs, keep it up and running until the last one has finished and shutdown it afterwards 2. I need a solution which boots the sd machine and shuts its down after any job (anyway if backup or restore) which has been startet not by scheduler but manually by WebUI or bconsole. Of course, there are *Run Before* and *Run After *commands which can be used in the job definitions. But if I would use them for each job the sd machine will be booted and shutted down a couple of time during each backup period. So my first idea is to cascade the jobs. But, how to do it in Bareos? May be some of you guys has or has had a similar task and will reply his suggestions/solutions to me. But, any other practical solution would also be greatly apreciated! Many thanks in advance moose -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/e3764cb9-3912-4fd5-8d24-a6e1652961e8%40googlegroups.com.
