On Jan 14, 2009, at 1:26 PM, Michael Galloway wrote: > On Wed, Jan 14, 2009 at 10:53:13AM -0500, John Drescher wrote: >>>> 3. There is no database backup as such. What we do is just take the >>>> system level full backup.
I usually advise against system level full backups. I recommend a proper database backup. For example, in PostgreSQL, this would involve running pg_dump and creating a text file. Or perhaps using PITR and backing up the WAL logs. In all cases, ensure that whatever database backup you are doing can get you back to a known good position. >>>> I believe he was suggesting that the Bacula catalog database >>>> might be stored >>> on the same file system that is being backed up. Since Bacula must >>> write to >>> its catalog database frequently during a backup, that would cause >>> disk >>> thrashing and greatly affect performance. >>> >> >> Exactly. >> > > so, would it be considered a 'best practice' to have the catalog > database server that is on > a separate machine that the bacula server? I don't have mine on a different server, but I may not be backing up as much as you have. I guess it depends. It also depends on whether or not you run concurrent jobs. And if you spool attributes, most of the database access occurs after the Volumes have been written. -- Dan Langille http://langille.org/ ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
