From: Matthias W. <bac...@il...> - 2003-04-15 09:00:54
|
hello kern, another feature request: at the moment schedule times just can be defined as day of week/month and so on. what does not work is: make a full backup every (approximately) 2 weeks. reason for this: if i do not want to define schedule times for each client separately, i have a full backup run for all clients at the same time and therefor need a lot of tapes. but if bacula could make some kind of calculation each day before it plans the backup jobs (information about full, incremental, ... jobs per client is still in the database) it could take a bit care of not running all backup jobs the same night. yes i always compare with amanda, but this is what amanda does nearly perfectly. amamanda goes further: it calls the client to calculate his backup size and afterwards decides which clients to take into next backup run. i think for bacula it would be enough to lookup the database, cause most of the servers and clients in production use dont change significantly in size of their backup (is my experience) and a question: i cannot use bacula for production in its 1.29 release and im thinking of getting 1.30b for production (if tests not fail). currently i am using some cvs snapshot from 20030411 and it works just fine. the question is: what do you think how often there will be incompatibility arise between old clients and new server? (like the actual code changes between 1.29 and 1.30) best regards, matthias wamser -- _ __ _ ___ __ _ _ _ _ _ _ __ / / / Matthias Wamser / mailto:mw...@il... \ / ILK Internet GmbH / fon +49 721 9100 0 \ \ Akademiestrasse 25-27 / fax +49 721 9100 191 \ \ D-76133 Karlsruhe / www http://www.ilk.de \ _ _ _ _ _ _ _ _ / \ _ _ _ _ _ |