Re: Which changes will break a job
Arno Lehmann <[email protected]>
| Newsgroups | gmane.comp.bacula.user |
|---|---|
| Organization | IT-Service Arno Lehmann |
| Message-ID | <[email protected]> |
Hello Mehrdad, Am 24.09.2024 um 11:43 schrieb Mehrdad R.: > Hi Guys > Testing bacula and i was wondering about what the Subject says > Which changes will break a job(by Break i men the job will fail and u > need to create a new job to have the new setup) In general, Jobs will not break if you change their configuration. You can change all aspects of them, and Bacula internally will try to ensure that restores will be done the right way. However, if you change File Set or Client you will create a new sequence of backups, but I wouldn't call that breakage... probably "configuration changes too well hidden" :-) If you manage to change Jobs in a way they actually fail running, for example be ending up without a valid storage or with a Run Script, you will be able to recover from that just fixing those problems. > aside from stuff like > Changing Storage client and device, i was thinking about stuff like > changes in schedule(i.e different days on diff or full backups, > changing hours), pools meaning changes VolumeRetention, Job retention > etc None of this should break a Job; some of this may surely have unwanted consequences, if you do not think about the effects first, but that's something you should always do with Bacula. > Anything else that will cause a working job to fail in the way of > changing Jobs set up Nothing comes to min, but perhaps others have ideas or even examples. Cheers, Arno > Regards /Mehrdad > > > _______________________________________________ > Bacula-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/bacula-users -- Arno Lehmann IT-Service Lehmann Sandstr. 6, 49080 Osnabrück _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users