> 07.11.2007 02:41,, Doug Sampson wrote::
> > I am testing the restore function of Bacula 2.2.5 on 
> FreeBSD 6.2 and in the
> > process of restoring ~20,000 files recursively from the 
> /var directory, I am
> > seeing numerous error messages as follows:
> > 
> > <..snip..>
> > 06-Nov 17:37 aries-fd JobId 2326: Warning: restore.c:588 
> Can't restore ACL
> > of
> > 
> /tmp/bacula-restores/var/db/portsnap/files/49aef80a863cf2a80ab
> 801b5f23f311d4
> > d005adb8a96f5477bb50deef559fc75.gz
> 
> Which file system is that? I suspect it's ZFS - ZFS ACLs are not 
> exactly supported at the moment. As far as I know, as long as you 
> don't use ACLs, there's nothing to be feared. Attila Fülöp wrote
> 
> "Just a few further notes: Unless you are using ACL on your zfs your
> data schould be save. You just have to live with the annoying error
> messages. You can check for this: "find /zfs_mount_point -acl" prints
> all files with ACL, "ls -V file_with_acl" show the associated ACL."
> 
> He has a possible patch to fully support ZFS, but that needs 
> work. See 
> the thread "solaris zfs" in the list archives...
> 

The file system on this FreeBSD machine is UFS2. Default file system as with
all FreeBSD machines. So it isn't the ZFS file system, what is causing these
errors?

> > <..snip..>
> > 
> > [EMAIL PROTECTED]:/tmp/bacula-restores# tail /var/log/messages
> > Nov  6 17:23:16 aries postgres[24308]: [11-1] ERROR:  unrecognized
> > configuration parameter "standard_conforming_strings"
> > Nov  6 17:25:41 aries postgres[24316]: [11-1] ERROR:  unrecognized
> > configuration parameter "standard_conforming_strings"
> > Nov  6 17:26:11 aries postgres[24316]: [12-1] ERROR:  table 
> "delcandidates"
> > does not exist
> > Nov  6 17:26:11 aries postgres[24316]: [13-1] ERROR:  index 
> "delinx1" does
> > not exist
> > Nov  6 17:26:11 aries postgres[24316]: [14-1] ERROR:  index 
> "delinx1" does
> > not exist
> > Nov  6 17:30:35 aries postgres[24328]: [11-1] ERROR:  unrecognized
> > configuration parameter "standard_conforming_strings"
> > Nov  6 17:37:44 aries postgres[24328]: [12-1] ERROR:  table 
> "delcandidates"
> > does not exist
> > Nov  6 17:37:44 aries postgres[24328]: [13-1] ERROR:  index 
> "delinx1" does
> > not exist
> > Nov  6 17:37:44 aries postgres[24328]: [14-1] ERROR:  index 
> "delinx1" does
> > not exist
> > 
> > Is the Bacula database corrupted? Why aren't the ACLs not 
> being restored?
> 
> The catalog thing is a different problem. Which version of Bacula do 
> you run, and which PostgreSQL version? You should check the version 
> requirements, or perhaps verify that your catalog holds all 
> the tables 
> and indexes needed. Just compare what the script to create the tables 
> does, and what you actually have in your catalog.
> 

Bacula 2.2.5 and PGSQL 7.4.18. I am seeing the same errors on another
FreeBSD 6.2 machine with Bacula 2.2.5 and PGSQL 8.0.14 installed. Oh, and
both machines are legacy machines- both used to run 5.x version of FreeBSD
with older version of Bacula (version 1.3x.x) prior to being upgraded where
they are now (through upgrades-- not fresh installs). I've gone through each
iterations of the Bacula software (1.36, 1.38, 2.0 and now 2.2 with the same
database on each of these two machines. I was really sure that the data came
through ok so far but...

Um, I will need to review the script.

~Doug

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to