Kern Sibbald schrieb: > > There are two ways to accomplish what you want and to handle BackupPC. > > 1. Turn off CatalogFiles in the pool you are using.
Ah, thank you. This is what I was looking for. > 2. Turn off HardLinks (I don't remember the exact directive name) in the > FileSet. This wouldn't help because without hardlinks, the backup of the backuppc pool would be useless. > You probably want to disable both, but both are recommended for normal > backups, so you should be aware of the consequences of turning them off. > > By the way, you should realize that at some point BackupPC can make your > system non-bootable. Fsck works much like the Bacula FD -- it must cache > hard links when working. So if there are too many hard links, it will run out > of RAM and will no longer function. Since fsck is not run on every boot, at > some point, you may be in for a big surprise. I know that a fsck will take long and consumes much memory (BTDT). That's the price for the pool/dedup feature which is very nice if you have many clients with identical data. Most of the clients are backed up with bacula and backuppc. I alreay lost one complete backuppc filesystem due to hardware errors... Ralf ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
