Re: [Bacula-users] Vista 64 - Bacula 2.4.2, VSS and symlink/junction issues

2008-10-27 Thread Bacula User
WildFile = "[a-zA-Z]:/pagefile.sys" WildFile = "[a-zA-Z]:/Users/*/AppData/Local/Microsoft/Outlook/*.oab" WildFile = "[a-zA-Z]:/Users/*/Local*/Applicat*/Microsoft/Outlook/*.oab" WildDir = "c:/DRIVERS" exclude = yes } - O

[Bacula-users] Vista 64 - Bacula 2.4.2, VSS and symlink/junction issues

2008-10-27 Thread Bacula User
Hello, Bacula Users. I apologize for adding yet another thread to this topic. I've seen a number of threads that make mention of these Vista problems, and they seem to drop off sometime around mid-2007. Yet, for me the issues persist, so I'm perplexed. If someone has a link to the definitive

Re: [Bacula-users] Number of files mismatch...again

2007-01-30 Thread bacula user
Hello Jose, On 22 Jan 2007 at 05:12:12 -0800, Jose Molina wrote: > Bacula 1.38.11 on FreeBSD 6, and we're using as a library an HP MSL 2024 > with a HP LTO3 Drive. I am also using freebsd 6.1, bacula 1.38.11_1, and a 24 slot LTO3 tape changer from HP (HP Storageworks MSL2024). I have not experi

[Bacula-users] slow postgres, index/table does not exist

2007-01-30 Thread Bacula User
Hi list, I am using freebsd 6.1, bacula 1.38.11_1, and postgresql-server-7.4.13_1. Each night I dump 913,157,728,765 bytes of 5,395,281 files to tape. I spool data and attributes. I will need to almost triple this amount to deploy bacula. Data goes to tape in under 16.5 hours, but attributes co

[Bacula-users] purging volumes is very slow

2007-01-29 Thread Bacula User
Hello, I am putting bacula through it's paces and have run across some slowness when purging volumes. I am using freebsd 6.1, bacula 1.38.11_1, and postgresql-server-7.4.13_1 on a dual xeon with 2GB of ram. I have three 15-spindle raid5 arrays (5.6 TB each) to manage spooling and database needs.

[Bacula-users] postgres: index/table does not exist

2007-01-29 Thread Bacula User
Hi list, I am using freebsd 6.1, bacula 1.38.11_1, and postgresql-server-7.4.13_1. I run concurrent jobs and the following errors seem to appear when attributes are despooling into the catalog. What do these mean and how do I fix them? Jan 27 10:43:56 postgres: [58-1] ERROR: table "delcandidate

Re: [Bacula-users] concurrent jobs don't spool at the same time

2007-01-09 Thread bacula user
This is a follow up for the archives. My problem was that the Storage declaration in bacula-dir.conf was missing a the required "Maximum Concurrent Jobs = 20" setting. This is adequately explained in the manual at the following location. http://www.bacula.org/rel-manual/Tips_Suggestions.html#SEC