We don't need the File Records in backup because :
1. Each of our production servers (hundreds of them) being backed up, has number of files in the range of hundred-thousands. 2. With Catalog Files = Yes (default), the database (PostGreSQL) hogs the CPUs on the host, with say 100 concurrent weekly Full backup jobs, putting a lot of stress on the server. 3. Last but not the least, there is hardly a need to precisely locate a single file during restoration. The restore is always in bulk at top dir level. With Catalog Files = No (in pool resource def) , we have already seen a big performance enhancement on the DB server. Bu there is a flip side, Virtual Full backup can no longer be achieved. -Yateen S Bhagat From: Dan Langille <d...@langille.org> Sent: Wednesday, October 4, 2023 12:43 AM To: fk+bacula--- via Bacula-users <bacula-users@lists.sourceforge.net> Subject: Re: [Bacula-users] Running backup job without file records in catalog CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information. On Thu, Sep 28, 2023, at 6:17 AM, Yateen Shaligram Bhagat (Nokia) wrote: Hi All, I would like to know if we can define a backup job (real or virtual) that DOES NOT put the file records in the catalog at all. Why? Whenever an unusual question arises, it helps to explain the background, the goal, the objective, etc. Thanks. -- Dan Langille d...@langille.org<mailto:d...@langille.org>
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
