> > on 07.11 (1st Sunday) bacula did a fullbackup like expected. Next monday > > a incremental like expected. On the following tuesday bacula made > > a fullbackup instead of the incremental, because he didn´t find a prior > fullbackup in the catalog. > > > > The fullbackup on the 7th was the second fullback. The first one was the > > initial fullbackup after the setup and start with bacula. > > > > Where do i have to search for the problem? > > Bacula relies heavily on your clock being correct. > If your clock went backwards since it did the first full, it won't be able to > find the first full. > > Also, if your retention for your first full has expired, it will purge it > even though another backup depends on it existing. > So perhaps your retention for your first full was too low. >
Hmmm... it never occurred to me before but mucking around with the clock on your director could seriously mess with your day! Advancing the clock by one year by mistake would probably purge most peoples catalogues. James ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
