I just went live with bacula 1.38 after running 1.36.3.

When I went live I deleted the old bacula install and droped the bacula database so I could get a fresh start.

I then installed bacula 1.38 and copied the *.conf files back to /etc/bacula

Before I was able to run 2 jobs at the same time even if they are backing up to the same Volume, now that no longer works.

Which is the expected behavior? Should I be able run 2 Jobs that backup to the same Pool or not?

I am able to run 2 backups that use seperate Pools though.


Another Issue I noticed, I have onefs = no in My FileSet, but I got this error when I started the backup:

Client-fd:      Filesystem change prohibited. Will not descend into /boot

Here is the start of my FileSet:

FileSet {
  Name = "Ensim Virt"
  Include {
   Options {
    signature   = SHA1
    compression = GZIP5
    onefs       = no
    hardlinks   = yes
   }
  }



Any hints?



--

  Brandon Evans

"I have a theory that the truth is never told during the nine-to-five hours."
-Hunter S. Thompson


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to