From: Luis P. <lui...@gm...> - 2010-11-23 21:32:31
|
On Tue, Nov 23, 2010 at 12:22, Pavel Hofman <pav...@iv...> wrote: > Luis Paulo napsal(a): >> On Wed, Nov 10, 2010 at 16:16, Luis Paulo <lui...@gm...> wrote: >>>>> Setting $Conf{BackupsDisable} = 2; for all clients won't do what you want? >>>>> >>>>> See http://your_server/backuppc/index.cgi?action=view&type=docs#item__conf_backupsdisable_ >>>>> >>>>> With web gui select for each client -> Edit Config -> Schedule -> On >>>>> blackouts set BackupsDisable to 2. >>>> Luis, >>>> >>>> Thanks a lot for your help. Setting this option for all clients (i.e. in >>>> the main config) is perfect, but is there a way to tell backuppc (while >>>> running a backup job) to reload its configuration (re-read the config >>>> files) so that next backup jobs already reflect the changed >>>> configuration? In my experience I always had to restart backuppc. >>>> >>>> Thanks a lot, >>>> >>>> Pavel. >>>> >>> You're probably right, but I'm not sure you need to reload/restart >>> backuppc (mostly if you change clients .pl). >>> Any way, I found this: >>> http://www.mail-archive.com/bac...@li.../msg19741.html >>> > > > Hi Luis, > > I apologize for late reply, it took me a while to test your solution. > Thanks a lot, it works as advertised :-) Now our offline-copy script > disables futher backups, and re-enables them after the external drives > are fully synchronized and removed from the raid array. > > Pavel. > Great it works, thank you for replying back. Could you be kind enough to clarify if * you only change BackupsDisable directive * or if you use also the "BackupPC_serverMesg server reload" command Regards Luis |