I am using bacula 1.36.3 both at director and storage deamon but different versions at file deamon. Last night I did status director and there were 78 jobs waiting for execution. But did I miss anything in the conf. file? One more thing I also have some problems with exclusion as I wanted all mp3 to be excluded from the backups from all partitions. I am giving the example below. Is that correct syntax?

FileSet {
 Name = linux-default
 #Ignore Fileset changes = yes
 Include {
 Options {
 signature=SHA1
 verify=pins1
 onefs=no
 sparse=no
 wildfile = *.mp3
 wildfile = *.m4a
 wildfile = *.o
 wildfile = *.obj
 wildfile = *.vob
 wildfile = *.VOB
 Exclude = yes
}
 File = /
 }

 Exclude {
       File = /dev/shm
       File = /dev/pts
       File = /sys
       File = /proc
       File = /tmp
       File = /.journal
       File = /.fsck
       File = /mnt

}
}


----- Original Message ----- From: "Arno Lehmann" <[EMAIL PROTECTED]>
To: "Arunav Mandal" <[EMAIL PROTECTED]>
Cc: <bacula-users@lists.sourceforge.net>
Sent: Wednesday, September 07, 2005 9:00 PM
Subject: Re: [Bacula-users] Concurrent backups


Hello,

Arunav Mandal wrote:

We have 150 clients to backup everynight and I am using 1TB as spool. All setup is on linux. I can see now only one client is doing backups at any given time. How can I do multiple backups at same time.

First: Multiple concurrent jobs work here, so I assume they could work at your place, too.

You seem to know that you have to set Maximum Concurrent Jobs at different locations, even at different hosts.

So I'd suggest the following steps:
- Tell us which version of bacula you use - the director, storage and file daemons should all be of the same version to simplify tracking errors. - Verify the 'status director' output and see if it gives a reason why the jobs are not running.
- If the jobs rune in parallel when you start them from the console, it
might be helpful if you create debug output from the director and capture that in a file. Debug level 400 gives loads of information, so you should reserve some time to analyze the log, find when the director starts the jobs, and see what happens when it encounters parallel jobs.

Apart from that, I'd suggest starting with a small installation for error hunting, something like one DIR, one SD, two clients and small filesets.

Arno

--
IT-Service Lehmann                    [EMAIL PROTECTED]
Arno Lehmann                  http://www.its-lehmann.de




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to