On 11/10/2010 4:12 AM, James Harper wrote: >>> 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.
This is why you have backups. Seriously. When you back up your database, leave a copy on disk. And then copy that copy elsewhere. And not just into Bacula. Same with your configuration files. -- Dan Langille - http://langille.org/ ------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
