The table 'File' is full
I've tried starting mysqld with the big-tables option, but that shouldn't
be needed with this version of mysql, and in any event it doesn't make any
difference. The /var/bacula filesystem has plenty of free space (about
8GB). The bacula mysql database is about
I think I've figured this out. What clue'd me in was you saying in a
simple test without PKI :-)
My test yesterday was without PKI. I was thinking about your setup, not
mine. :)
But I didn't have ACL support turned on.
Here's my fileset from yesterday's test, which did back up and restore
I was wondering if you had gotten a chance to look at this? I was
going to file a bug report but wanted to check with you first.
Not yet. I've scheduled to look at this (and another HFS+ resource fork
problem) on Thursday.
-- Jorj
pgpREItM3DPAx.pgp
Description: PGP signature
containing resource forks should work properly with either version of
bacula that I have tested. What I am seeing however is that these
files are listed with a size of zero in both bconsole (during setup
of a restore job, by doing a dir during file selection) and also on
the client
I have another question, related to this one...
Can i backup fork ressources on a Windows 2000 server (forks are
supported by this server) ?
They're called alternate data streams under Windows, and are a feature
of the NTFS filesystem (not really the OS). I don't think they're
supported in
Thinking out loud about how to implement this: would you consider a
directive that specified a script to be run whenever a Bacula component
needed to open or reference the config file that would supply the name
of a file to read for the information? The idea would be similar to the
OK, neat. Does that also allow regeneration of the file while the daemon
is running, eg, what happens if you issue a reload command? Do you get a
updated file?
Yes. Whenever Bacula tries to open a configuration file, it instead
opens a pipe.
Reason for the question: in a larger environment,
Out of curiosity, what -- down the line -- would the -sd require a
database for? Config info?
Config info in the database -- never. Only people who have never done a bare
metal recovery would think of such an implementation :-).
bscan built into the SD. However, I *might* do that
For example, starting the director like this:
# bacula-dir -c '|/usr/local/sbin/generate-dir-config'
Maybe I am missing some important point, but by now I can't see any mayor
benefits of your solution compared with:
# /usr/local/sbin/generate-dir-config
Can you explain what you mean by one of the lite mechanisms?
SQLite or SQLite3. I don't believe they have any remote access directly.
I see no need to have each Storage daemon have its own database.
The only reason I mention it is because of the non-remote-access
database methods.
-- Jorj
What: The ability to read a configuration file as stdout from an executable
Why: The configuration files (particularly for the Director) are very
complex. In my case I find it easier to have a program generate them
from meta-information about the clients.
Notes:
The attached
# bacula-dir -c '|/usr/local/sbin/generate-dir-config'
... would cause it to run /usr/local/sbin/generate-dir-config to
generate a new configuration file.
Hey, that sounds pretty useful. When you say globally, I assume you
mean that I can just toss a similar line into
Maybe I am missing some important point, but by now I can't see any mayor
benefits of your solution compared with:
# /usr/local/sbin/generate-dir-config /etc/bacula/bacula-dir.conf
bacula-dir -c /etc/bacula/bacula-dir.conf
It's subtle. You're missing the 'reload' command.
-- Jorj
Bacula does its normal HMAC-MD5 password authentication
I never meant to imply that it did not, although my message was
obviously interpreted that way by at least two people.
The FD address cannot be part of the certificate (CN or any other field)
if roaming FDs are ever to be supported.
On Thu, Mar 15, 2007 at 12:04:00AM +0100, Kern Sibbald wrote:
On Wednesday 14 March 2007 22:29, Landon Fuller wrote:
On Mar 14, 2007, at 13:41, Jorj Bauer wrote:
Let's take the DNS security issue off the table for the moment.
As I mentioned at some point, that's mostly paranoia. As you
I didn't actually craft this patch to address any TLS weakness; I wrote
it to address a feature flaw/conflict.
Let's take the DNS security issue off the table for the moment.
As I mentioned at some point, that's mostly paranoia. As you say, you'd
have to compromise both DNS and one of the root
).
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Jorj Bauer | [EMAIL PROTECTED]
IT Director | 3330 Walnut St.
School of Engineering and Applied Science |Levine Building, Room 160
University of Pennsylvania
17 matches
Mail list logo
