[Bacula-users] Interest in mirroring to off site cloud services?
Hello all, I'm generally curious if there is an interest amid the Bacula community in mirroring backups to off site cloud services, especially in light of the growing interest in these services and the economies of scale they offer e.g., Amazon S3, Microsoft Windows Azure blog storage, OpenStack Object Storage, Google Cloud Storage (just to name a few)? Searching this Bacula Users mailing list archives, it seems a question about this pops up once in a while. In this vein, I noticed the Amanda community seems to be going this direction starting with S3 and more recently the Zmanda announcement this month about Google Cloud Storage. Cheers, -Hydro -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula Mac OS X 10.7 Lion (changes to the HFS file system?)
Hello all -- Do I dare ask if anyone has yet tried backing up, with Bacula, a Mac OS X 10.7 Lion or Lion Server? John Siracusa of Ars Technica has written what appears to be one of the most detailed reports about Lion starting on this page with table of contents: http://arstechnica.com/apple/reviews/2011/07/mac-os-x-10-7.ars This subchapter heading strikes me as most important with respect to Bacula and OS X 10.7 titled *File system changes in Lion* with some notable highlights I've excerpted particularly about Core Storage and the new disc encryption system Apple has come out with which logically should not be a problem for Bacula backups given how transparent it is to software (one concern might be what *other* changes have taken place to the file system in Lion that Bacula might want to address, which changes have not been presented in Siracusa's Ars article?): http://arstechnica.com/apple/reviews/2011/07/mac-os-x-10-7.ars/13#lion-file-system Nevertheless, there are some file system changes in Lion—some significant ones, in fact. The biggest is the introduction of Apple's first real crack at creating a logical volume manager: Core Storage. ... Core Storage's purpose in Lion is discreetly hidden in the Logical Volume Family tier of the layer cake. Logical Volume Families don't just export Logical Volumes, they also contain properties that apply to them. One such set of properties in Lion enables full disk encryption. ... Though Apple is using the name FileVault to brand this feature, it has absolutely nothing to do with the feature of the same name from earlier versions of Mac OS X. The earlier incarnation of FileVault encrypted an individual user's home directory by storing it in an encrypted disk image file. This presented all sorts of complications to common operations, and FileVault earned a horrible reputation for poor compatibility with existing software (including Apple's own, like Time Machine). Lion's FileVault doesn't just encrypt users' home directories, and it doesn't use encrypted disk image files. Instead, it's Apple's implementation of whole disk encryption. This means that every byte of data that makes up the volume is encrypted. Furthermore, this encryption is completely transparent to all software (including the implementation of HFS+ itself) because it takes place at a layer above the volume format—a layer that application software does not see at all. Having used a third-party whole-disk encryption product for years, I can tell you that this approach works amazingly well. - Hydro -- 10 Tips for Better Web Security Learn 10 ways to better secure your business today. Topics covered include: Web security, SSL, hacker attacks Denial of Service (DoS), private keys, security Microsoft Exchange, secure Instant Messaging, and much more. http://www.accelacomm.com/jaw/sfnl/114/51426210/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula on an Apple Xserve - alleged problem posted in Apple forums
Hello all, Its been a while since I've posted to this mailing list. I happened to be reading Apple Support Communities where about a year ago someone with the alias of BoeroBoy posted this comment about Bacula: https://discussions.apple.com/message/11628649?messageID=11628649. Anyway we had someone investigating Bacula and apparently she can't get 2 of the 3 processes working on an XServe. So it looks like we may try Retrospect. I signed up for an Apple ID to try and add to this thread and / or contact the person who posted this, as a followup but the thread has been archived and no longer can be commented on, and Apple Communities won't allow me to privately contact the poster. I have a few Xserves and am unaware of any problems getting Bacula daemons running on Mac OS X. But, its always good to followup and make sure something unexpected hasn't changed. The problem is that I don't know what version of Bacula this person tried with, and the comment looks vague. Anyone know who BoeroBoy might be or if anyone else with Xserves are having problems (Mac OS X version 10.6)? Cheers, -Hydro -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Mac OS X Leopard and Bacula 2.2.8 (ACLs)
On 2/4/08, Martin Simmons [EMAIL PROTECTED] wrote: On Sat, 2 Feb 2008 00:17:29 -1000, Hydro Meteor said: I wonder what would need to be done in the Bacula source to properly capture and restore ACL metadata on file systems mounted to Mac OS X Leopard (or Tiger for that matter) operating systems? Does anyone have any suggestions? It looks like Apple's acl_get_file does not support the ACL_TYPE_DEFAULT and ACL_TYPE_ACCESS types of query. Someone else has enjoyed this problem too: http://xarchiver.blogspot.com/2007/04/mac-os-x-acls-added.html Martin, thank you for pointing this out. I sent an email to Rob Braun (who is the author of the page on the blog your URI links to) to ask him if his statements made in April 2007 (about ACL API discrepancies on Mac OS X Tiger 10.4) continue to apply now on Mac OS X Leopard 10.5 ... I have not received a response from him yet but if I do receive one I will share it on this mailing list. One way or another, there ought to be a way to get to the bottom of what Apple has done (differently) with POSIX ACLs and then hopefully they can be incorporated into Bacula. Many of us want to use Bacula for back up and restore purposes (including very importantly that Bacula is open source / GPL) on Mac OS X and we do not want to become dependent on Apple's closed-source Time Machine software. Time Machine is probably going to be fine for mass consumers but for those of us running professional systems on OS X Server we will want control of our file system backup and recovery with Bacula. Cheers, Hydro __Martin - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula 2.2.8 wont start (MacOS X)
Oops hello to everyone and especially Piero Giobbi, I must be dreaming or
having a temporary lapse of amnesia. Of course the Storage Daemon has an
Archive Device directive (it has been a while since I looked at Bacula
configuration files so I forgot about it).
So, I just added /tmp to the Archive Device directive in the Storage
Daemon configuration file, and great news -- Bacula 2.2.8 daemons
(Director, Storage, File) are all running on Leopard Server 10.5.1
Even though you have MySQL running on your Leopard system, please let me
know if I can provide some tips / suggestions for how to get Bacula
2.2.8running on your system. Glancing at your output from the error
you
encountered, it looks to be for sure some problem related to when you ran
./configure (when specifying the configuration arguments required for
building against MySQL). Take a look at libsql in your make output -- I bet
you'll find some errors there. For example, I don't have MySQL or sqlite on
my system, so I got these complaints when running make:
Making libsql.a ...
/usr/bin/ar rc libsql.a mysql.o bdb.o bdb_create.o bdb_get.o bdb_update.o
bdb_delete.o bdb_find.o bdb_list.o sql.o sql_cmds.o sql_create.o
sql_delete.o sql_find.o sql_get.o sql_list.o sql_update.o sqlite.o
postgresql.o
ranlib: file: libsql.a(mysql.o) has no symbols
ranlib: file: libsql.a(bdb.o) has no symbols
ranlib: file: libsql.a(bdb_create.o) has no symbols
ranlib: file: libsql.a(bdb_get.o) has no symbols
ranlib: file: libsql.a(bdb_update.o) has no symbols
ranlib: file: libsql.a(bdb_delete.o) has no symbols
ranlib: file: libsql.a(bdb_find.o) has no symbols
ranlib: file: libsql.a(bdb_list.o) has no symbols
ranlib: file: libsql.a(sqlite.o) has no symbols
ranlib libsql.a
ranlib: file: libsql.a(mysql.o) has no symbols
ranlib: file: libsql.a(bdb.o) has no symbols
ranlib: file: libsql.a(bdb_create.o) has no symbols
ranlib: file: libsql.a(bdb_get.o) has no symbols
ranlib: file: libsql.a(bdb_update.o) has no symbols
ranlib: file: libsql.a(bdb_delete.o) has no symbols
ranlib: file: libsql.a(bdb_find.o) has no symbols
ranlib: file: libsql.a(bdb_list.o) has no symbols
ranlib: file: libsql.a(sqlite.o) has no symbols
Make of cats is good
When I made Bacula 2.2.3 on Tiger Server 10.4.10 against PostgreSQL 8.1.9, I
didn't have these ranlib no symbols results. So something has changed.
By the way, I have just about all of my dependencies for Bacula installed as
MacPorts. Do you use MacPorts for installing MySQL?
Cheers,
Hydro
On 2/1/08, Hydro Meteor [EMAIL PROTECTED] wrote:
Piero,
This is a difficult one to diagnose because it depends on how you
configured Bacula on your system with Leopard and MySQL. Moments ago, I just
ran configure, make and make install with Bacula 2.2.8 on Mac OS X Server
10.5.1 (Leopard Server) and I am using PostgreSQL, not MySQL. I had no
problems getting the File and Director daemons to run on Leopard Server
10.5.1 but the Storage Daemon gave me an error because I didn't assign an
Archive Device in the storage daemon configuration file, as in:
Device {
Name = FileStorage
Media Type = File
Archive Device =
LabelMedia = yes; # lets Bacula label unlabeled
media
Random Access = Yes;
AutomaticMount = yes; # when device opened, read it
RemovableMedia = no;
AlwaysOpen = no;
}
So when I ran the bacula start script, I got:
Starting the Bacula Storage daemon
01-Feb 10:29 bacula-sd: ERROR TERMINATION at lex.c:735
Config error: expected a name, got T_EOL: =
: line 48, col 20 of file /opt/local/etc/bacula/bacula-
sd.conf
Archive Device =
Starting the Bacula File daemon
Starting the Bacula Director daemon
Hmm ... it amazing how much has changed from Bacula 2.2.3 to 2.2.8 because
I have never heard of the Archive Device directive yet. Ugh! This means I
need to read more documentation but I am guessing its for the better. I will
for now comment out this line until I know more about it. Nonetheless, the
good news is that I can tell you with certainty that Bacula compiles and
runs on Leopard Server 10.5.1 and so I would guess also Leopard
(non-Server) 10.5.1
I am about to do some testing with Leopard's Access Control Lists (ACLs)
with Bacula to see if files that have ACLs can be backed up and restored
perfectly.
Cheers,
Hydro
On 1/27/08, Piero Giobbi [EMAIL PROTECTED] wrote:
Hi all.
Just compiled latest bacula with Leopard and latest Mysql, the build
went
well. Now when i configured all up and starting up bacula i get this
error:
sh-3.2# /usr/local/bacula/bin/bacula start
Starting the Bacula Storage daemon
Starting the Bacula File daemon
Starting the Bacula Director daemon
dyld: Library not loaded:
/usr/local/mysql/lib/mysql/libmysqlclient_r.15.dylib
Referenced from: /usr/local/bacula/bin/bacula-dir
Reason: image not found
/usr/local/bacula/bin/bacula-ctl-dir: line 197
Re: [Bacula-users] Bacula 2.2.8 wont start (MacOS X)
Piero,
This is a difficult one to diagnose because it depends on how you configured
Bacula on your system with Leopard and MySQL. Moments ago, I just ran
configure, make and make install with Bacula 2.2.8 on Mac OS X Server
10.5.1(Leopard Server) and I am using PostgreSQL, not MySQL. I had no
problems
getting the File and Director daemons to run on Leopard Server 10.5.1 but
the Storage Daemon gave me an error because I didn't assign an Archive
Device in the storage daemon configuration file, as in:
Device {
Name = FileStorage
Media Type = File
Archive Device =
LabelMedia = yes; # lets Bacula label unlabeled media
Random Access = Yes;
AutomaticMount = yes; # when device opened, read it
RemovableMedia = no;
AlwaysOpen = no;
}
So when I ran the bacula start script, I got:
Starting the Bacula Storage daemon
01-Feb 10:29 bacula-sd: ERROR TERMINATION at lex.c:735
Config error: expected a name, got T_EOL: =
: line 48, col 20 of file /opt/local/etc/bacula/bacula-sd.conf
Archive Device =
Starting the Bacula File daemon
Starting the Bacula Director daemon
Hmm ... it amazing how much has changed from Bacula 2.2.3 to 2.2.8 because I
have never heard of the Archive Device directive yet. Ugh! This means I need
to read more documentation but I am guessing its for the better. I will for
now comment out this line until I know more about it. Nonetheless, the good
news is that I can tell you with certainty that Bacula compiles and runs on
Leopard Server 10.5.1 and so I would guess also Leopard (non-Server) 10.5.1
I am about to do some testing with Leopard's Access Control Lists (ACLs)
with Bacula to see if files that have ACLs can be backed up and restored
perfectly.
Cheers,
Hydro
On 1/27/08, Piero Giobbi [EMAIL PROTECTED] wrote:
Hi all.
Just compiled latest bacula with Leopard and latest Mysql, the build went
well. Now when i configured all up and starting up bacula i get this
error:
sh-3.2# /usr/local/bacula/bin/bacula start
Starting the Bacula Storage daemon
Starting the Bacula File daemon
Starting the Bacula Director daemon
dyld: Library not loaded:
/usr/local/mysql/lib/mysql/libmysqlclient_r.15.dylib
Referenced from: /usr/local/bacula/bin/bacula-dir
Reason: image not found
/usr/local/bacula/bin/bacula-ctl-dir: line 197: 42268
Trace/BPT trap ${BACDIRBIN}/bacula-dir $2 ${OPTIONS} -v -c
${BACDIRCFG}/bacula-dir.conf
Anyone know whats wrong?
thx.
p
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula 2.2.8 wont start (MacOS X)
Hello again Piero, Sorry I don't have a MySQL installation with Bacula, otherwise I could help you solve your MySQL problem with Bacula on Leo. All I can do is say that there is for sure hope, because I have Bacula 2.2.8 on Leopard 10.5.1 built against Postgres running perfect so far. I am about to research the details of Leopard's use of extended attributes (EAs) including Access Control List (ACL) metadata information that is stored in some files on the HFS file systems. By the way, I should also let you know that the disk volumes that I attach to my Mac that runs Leopard Server 10.5.1 are all HFSX journaled (that is, case-sensitive). You might know that you can now have the option, with Leopard, to install your boot disc volumes from the Apple Leopard DVD discs as HSFX (case sensitive). This is great news because in Tiger we only had the option of formatting non-boot-discs with HFSX. I'm pretty sure that the HFSX case sensitive option for the Mac OS X boot discs were required in order for Apple to get Mac OS X to be fully UNIX certified: http://www.apple.com/macosx/technology/unix.html UNIX certification. Leopard is an Open Brand UNIX 03 Registered Product, conforming to the SUSv3 and POSIX 1003.1 specifications for the C API, Shell Utilities, and Threads. Since Leopard can compile and run all your existing UNIX code, you can deploy it in environments that demand full conformance — complete with hooks to maintain compatibility with existing software. Now that Apple is well past its move to Intel architecture, and it is now UNIX certified and fully 64-bit capable, and considering the competing products for virtual systems on Mac OS X (VMWare's Fusion and Parallels), I foresee Apple becoming stronger and stronger with time. I am currently running Bacula on an Xserve in case you're wondering about my hardware et up. What hardware are you attempting to run Bacula on? Is your hardware Intel or PowerPC based? Cheers, Hydro On 2/1/08, Piero Giobbi [EMAIL PROTECTED] wrote: Hi again! No im not running Macports, my next step is to use that instead (with bacula 2.2.6) but i rather get this running! Im on the same track, something is fishy with bacula - mysql, maybe bacula can't find this file: dyld: Library not loaded: /usr/local/mysql/lib/mysql/libmysqlclient_r.15.dylib p 1 feb 2008 kl. 12.18 skrev Hydro Meteor: Oops hello to everyone and especially Piero Giobbi, I must be dreaming or having a temporary lapse of amnesia. Of course the Storage Daemon has an Archive Device directive (it has been a while since I looked at Bacula configuration files so I forgot about it). So, I just added /tmp to the Archive Device directive in the Storage Daemon configuration file, and great news -- Bacula 2.2.8 daemons (Director, Storage, File) are all running on Leopard Server 10.5.1 Even though you have MySQL running on your Leopard system, please let me know if I can provide some tips / suggestions for how to get Bacula 2.2.8running on your system. Glancing at your output from the error you encountered, it looks to be for sure some problem related to when you ran ./configure (when specifying the configuration arguments required for building against MySQL). Take a look at libsql in your make output -- I bet you'll find some errors there. For example, I don't have MySQL or sqlite on my system, so I got these complaints when running make: Making libsql.a ... /usr/bin/ar rc libsql.a mysql.o bdb.o bdb_create.o bdb_get.o bdb_update.o bdb_delete.o bdb_find.o bdb_list.o sql.o sql_cmds.o sql_create.o sql_delete.o sql_find.o sql_get.o sql_list.o sql_update.o sqlite.o postgresql.o ranlib: file: libsql.a(mysql.o) has no symbols ranlib: file: libsql.a(bdb.o) has no symbols ranlib: file: libsql.a(bdb_create.o) has no symbols ranlib: file: libsql.a(bdb_get.o) has no symbols ranlib: file: libsql.a(bdb_update.o) has no symbols ranlib: file: libsql.a(bdb_delete.o) has no symbols ranlib: file: libsql.a(bdb_find.o) has no symbols ranlib: file: libsql.a(bdb_list.o) has no symbols ranlib: file: libsql.a(sqlite.o) has no symbols ranlib libsql.a ranlib: file: libsql.a(mysql.o) has no symbols ranlib: file: libsql.a(bdb.o) has no symbols ranlib: file: libsql.a(bdb_create.o) has no symbols ranlib: file: libsql.a(bdb_get.o) has no symbols ranlib: file: libsql.a(bdb_update.o) has no symbols ranlib: file: libsql.a(bdb_delete.o) has no symbols ranlib: file: libsql.a(bdb_find.o) has no symbols ranlib: file: libsql.a(bdb_list.o) has no symbols ranlib: file: libsql.a(sqlite.o) has no symbols Make of cats is good When I made Bacula 2.2.3 on Tiger Server 10.4.10 against PostgreSQL 8.1.9, I didn't have these ranlib no symbols results. So something has changed. By the way, I have just about all of my dependencies for Bacula installed as MacPorts. Do you use MacPorts for installing MySQL? Cheers, Hydro On 2/1/08, Hydro Meteor [EMAIL PROTECTED
[Bacula-users] Any Bacula admins running Client / Director on Mac OS X 10.5 Leopard?
Greetings all -- Are there any folks running Bacula Client and/or Director on Mac OS X 10.5.x (Leopard)? If so, any experiences / concerns / gotchyas? Especially with regard to extended attributes (EAs) in the form of ACLs that Apple is now instituting on root HFS filesystems that mount to Leopard? I noticed that Kern kindly made a change to source not too long ago to help fix a problem that was encountered when building Bacula (Client) on Leopard. In a day or so I plan on putting a full effort into building at least Client on Leopard Server running on an Xserve. I'd be happy to share / compare notes with anyone else who is interested (would like to do so on the mailing list so that others in the community can benefit). Cheers, Hydro - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Is migration across different Media Types really all that undesirable?
Hello all -- Reading the current Bacula User's Guide regarding Migration, I found this sentence: Bacula permits pools to contain Volumes with different Media Types. However, when doing migration, this is *a very undesirable condition*. For migration to work properly, you should use pools containing only Volumes of the same Media Type for all migration jobs. For example, I have migration resources set up to test migrating Volumes across Devices (defined as Device Resources in the Storage Daemon Configuration) across different Media Types such as from File (e.g., hard drive) to DVD media type. I only have done one simple test but it seemed to work fine. Why is this a very undesirable condition? Best, -H - 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
[Bacula-users] Migration purging seems not to work
Hi all, I just recently set up a migration resources in my Director configuration file to migrate from File (hard drive) to DVD. The simple test I tried worked fine (the DVD+RW was written to just perfectly). The Bacula User's Guide states: As part of this process, *the File catalog records associated with the first backup job are purged*. In other words, Migration moves Bacula Job data from one Volume to another by reading the Job data from the Volume it is stored on, writing it to a different Volume in a different Pool, and then purging the database records for the first Job. Strangely, my original backup job (of the File on the hard drive) was not purged. Is not the purge supposed to take place once the migration has succeeded (e.g., after the DVD was successfully written to)? I wonder why mine simple test situation indicated no purging took place? Thanks for any suggestions, -H - 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
Re: [Bacula-users] Is migration across different Media Types really all that undesirable?
On Nov 7, 2007 1:32 AM, Arno Lehmann [EMAIL PROTECTED] wrote: Hi, 07.11.2007 12:11,, Hydro Meteor wrote:: Hello all -- Reading the current Bacula User's Guide regarding Migration, I found this sentence: Bacula permits pools to contain Volumes with different Media Types. However, when doing migration, this is *a very undesirable condition*. For migration to work properly, you should use pools containing only Volumes of the same Media Type for all migration jobs. For example, I have migration resources set up to test migrating Volumes across Devices (defined as Device Resources in the Storage Daemon Configuration) across different Media Types such as from File (e.g., hard drive) to DVD media type. I only have done one simple test but it seemed to work fine. Why is this a very undesirable condition? What you do is not undesirable. What IS undesirable is if your migration source pool contains volumes of different media types. Like you run incremental backups to a pool using file storage device and tape device, and later migrate jobs from both these storages to DVD. That's probably undesirable because Bacula has to reserve many devices to migrate, I suspect. Arno, Thank you for clarifying this as it was somewhat ambiguous in the User's Guide. Cheers! Arno Best, -H - 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 -- Arno Lehmann IT-Service Lehmann www.its-lehmann.de - 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 - 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
Re: [Bacula-users] Migration purging seems not to work
On Nov 7, 2007 1:26 AM, Arno Lehmann [EMAIL PROTECTED] wrote: Hello, 07.11.2007 12:17,, Hydro Meteor wrote:: Hi all, I just recently set up a migration resources in my Director configuration file to migrate from File (hard drive) to DVD. The simple test I tried worked fine (the DVD+RW was written to just perfectly). Good to hear - I'm planning a similar (test) setup here :-) Credit goes to Richard Mortimer who had suggested this strategy in an off-list email! The Bacula User's Guide states: As part of this process, *the File catalog records associated with the first backup job are purged*. In other words, Migration moves Bacula Job data from one Volume to another by reading the Job data from the Volume it is stored on, writing it to a different Volume in a different Pool, and then purging the database records for the first Job. Strangely, my original backup job (of the File on the hard drive) was not purged. Is not the purge supposed to take place once the migration has succeeded (e.g., after the DVD was successfully written to)? Note the difference between File records and Job records - the File records should be purged, the Job records remain in the catalog. At least that's how I read the above manual paragraph. I wonder why mine simple test situation indicated no purging took place? Have you actually checked for the File records, or only the Job records? Hi Arno, I use the very nice Bacuview program to display the contents of the Catalog. It shows all jobs saved in the Catalog and indeed you are right, the Job records are not purged. But, interestingly enough, Bacuview also gives me a view of the media records which has a table that looks like this: *NameSlotStatusJobsBytesExpiresRetentionPool NamePool TypeMedia* So, the file that was original saved (which should be purged) has the name of filetest and it still exists in the Catalog (not purged), as in: Name: filetest1 Slot: - Status: Used Jobs: 1 Bytes: 54.3 MB Expires: 2008-11-06 Retention: 365 days Pool Name: thefullPool Pool Type: Backup Media: HardDisc Note that the Jobs field is not the same as the JobID when presented by Bacuview (there are separate views for the Jobs IDs). Maybe the file (in the example above named filetest1) has not been purged because its retention is set for one year and therefore in a situation whereby teh retention is set to some value, it overrides the ability of the migration job to purge it from the Catalog? Also, the actual file on the hard drive where it is saved (the archive) also still exists and was not deleted (I presume then that migration merely copies the archive but does not delete the original archive itself). This isn't a big deal because the original archive copy can be deleted later. By the way, the file filetest1 was successfully migrated to dvdtest1 and an additional record shows up for the same table courtesy of Bacuview: Name: dvdtest1 Slot: - Status: Append Jobs: 1 Bytes: 54.3 MB Expires: 2008-11-06 Retention: 365 days Pool Name: DVDFullPool Pool Type: Backup Media: DVD If I understand what the User's Guide is saying, in theory then, using the above examples, filetest1 meta data should be entirely purged from the Catalog as it is in essence deprecated in favor of dvdtest1, true? What if there is a bug or some problem in getting the Catalog to purge the deprecated file meta data (let's say for example that perhaps file retention length does not in fact override migration's ability to purge and there is some other unknown reason as to why it is not purged even though the User's Guide says it should be)? In such a case the purging could and should be done manually true? For example, the original file on the hard drive and the clone of the file on the DVD could have their SHA1 checksums computed and compared. If the checksums match, then it would be safe to both delete the original file on the hard drive and delete its catalog meta data (e.g., on the Bacula Console run a delete -- Volume on the MediaID or the Volume name of the deprecated original volume)? I suppose this is somewhat of an obvious question but migration seems to be an interesting little animal with some new challenges. Cheers, -H Arno Thanks for any suggestions, -H - 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
Re: [Bacula-users] Migration purging seems not to work
Hello again Arno and friends ... On 11/7/07, Arno Lehmann [EMAIL PROTECTED] wrote: Hi, 07.11.2007 19:12,, Hydro Meteor wrote:: On Nov 7, 2007 1:26 AM, Arno Lehmann [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hello, 07.11.2007 12:17,, Hydro Meteor wrote:: Hi all, I just recently set up a migration resources in my Director configuration file to migrate from File (hard drive) to DVD. The simple test I tried worked fine (the DVD+RW was written to just perfectly). Good to hear - I'm planning a similar (test) setup here :-) Credit goes to Richard Mortimer who had suggested this strategy in an off-list email! The Bacula User's Guide states: As part of this process, *the File catalog records associated with the first backup job are purged*. In other words, Migration moves Bacula Job data from one Volume to another by reading the Job data from the Volume it is stored on, writing it to a different Volume in a different Pool, and then purging the database records for the first Job. Strangely, my original backup job (of the File on the hard drive) was not purged. Is not the purge supposed to take place once the migration has succeeded (e.g., after the DVD was successfully written to)? Note the difference between File records and Job records - the File records should be purged, the Job records remain in the catalog. At least that's how I read the above manual paragraph. I wonder why mine simple test situation indicated no purging took place? Have you actually checked for the File records, or only the Job records? Hi Arno, I use the very nice Bacuview program to display the contents of the Catalog. It shows all jobs saved in the Catalog and indeed you are right, the Job records are not purged. But, interestingly enough, Bacuview also gives me a view of the media records which has a table that looks like this: Well, that table still doesn't hold any information about the file records :-) Great point, I missed that. Thanks for pointing it out. * NameSlotStatusJobsBytesExpiresRetention Pool NamePool TypeMedia * So, the file that was original saved (which should be purged) has the name of filetest and it still exists in the Catalog (not purged), as in: Name: filetest1 Slot: - Status: Used Jobs: 1 Bytes: 54.3 MB Expires: 2008-11-06 Retention: 365 days Pool Name: thefullPool Pool Type: Backup Media: HardDisc This is a volume file. You need to check what the catalog knows about its contents. I don't use bacuview, but in bconsole, there is a query for this. Ah yes, I like Bacuview but was becoming a little too reliant on it and I can understand why Bacuview doesn't provide a view of Volume File contents (it could be tens of thousands of lines long depending on how deep and wide the file system resource tree is that was being backed up on the Client) -- probably too much to view in a web browser. I had not previously used the *query* Bacula Console command, thank you for calling my attention to it. I suspect you'll find the original job is still known to be stored on this volume, the job will be marked as being migrated (status M). Yep, you are right. I ran another migration test and afterwards, M was the value of the JobID's type, as in: *list jobs | jobid | name | starttime | type | level | jobfiles | jobbytes | jobstatus | *|18 | Backup LeClient-fd | 2007-11-08 00:40:59 | M| F | 1,665 | 56,538,141 | T|* Note: the number of job bytes in this example (where JobID was written to another hard drive, not a tape or another other medium) is 56,538141 yet after I successfully ran a migration job, the number of jobbytes for the JobID 20 is slightly more than that of JobID 18: |20 | Backup LeClient-fd | 2007-11-08 00:40:59 | B| F | *1,665* | *56,827,921* | T | |19 | migrate-volume| 2007-11-08 00:52:30 | g| F | 0 | 0 | T | Is this because JobID 20 was written to DVD+RW and there are additional bytes of information when writing to DVD+RW (for example the DVD is split into part files and so maybe there are bytes required to keep track of the parts or other DVD-specific structures)? A difference from JobID 18 to JobID 20 of 289,780 bytes (283KB) is not necessarily insignificant. Arno, another thing that is interesting is that JobID 20 must have been spawned by the migration process (JobID 19) because manually, I only executed JobID 19 (the migration) and not directly JobID 20. I guess this makes sense in that JobID 19
[Bacula-users] What is the strategy for MaximumPartSize?
Hello all, This question probably has an obvious answer that I'm missing, but with regard to DVD backups, the Device Resource in the Storage Daemon Configuration has an optional Directive named MaximumPartSize. From the Bacula Usesr's Guide, I think I understand that setting a value for this Directive (e.g., 800 MB) is a way of controlling how many bytes (from the Client backup target) ends up in the Bacula spool directory at one time (before the bytes get copied to the DVD optical disc). Is this a correct assessment that MaximumPartSize in essence acts as a sort of flow control from backup target on the client to the spool to the DVD disc that requires mounting? Thanks, -H - 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
[Bacula-users] Exampels for non-rewritable DVD?
Hello all -- For those who are backing up to non-rewritable DVD optical media (such as DVD-R and DVD+R), would anyone be willing to share examples of the Device Resource example for such? The reason I ask is that while I have a Device Resource for DVD+RW working fine, I have been unsuccessful thus far getting Bacula to back up to a DVD+R disc (although I ran the growisofs and dvd-handler script on a blank DVD+R disc dropped into my machine, and I was successful in getting Bacula to write a label (as a part 1 file) on to DVD+R but nothing further). I also discovered that DVD+R discs should not be de-iced before writing to them with Bacula via dvd-handler (well, at least not manually as part of a separate process like DVD+RW discs can be). I was hoping that the same Storage Daemon Device Resource used for DVD+RW could be used for DVD+R discs but no such luck (in fact the directives such as MaximumPartSize and WritePartCommand do not seem to make sense in the context of a non-rewitable DVD optical disc since apparently DVD+R (or DVD-R) are not multi-session capable, so how does one best use non-rewritable optical media with Bacula? Is the best approach to in fact use Volume Migration (write the Volume to hard drive first and then move it in one fell swoop over to DVD+R or DVD-R)? Thank you, -H - 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
Re: [Bacula-users] Bacula-usersDVD+RW overwrites
On 11/5/07, Wes Hardaker [EMAIL PROTECTED] wrote: HM == Hydro Meteor [EMAIL PROTECTED] writes: HM For those in Bacula DVD userland who are using DVD+RWs, it strikes me as if HM 1,000 overwrites is really not all that bad. I do use DVD+RW to back up important parts of my server (and it uses a disk cache for anything not on it). I've learned a few things during using this process. For one thing, the default dvd-handler doesn't turn on the -dvd-compat flag which was causing me problems with a part not getting written and then later readable. I'm not entirely sure what it does, but I turned it on a week or two ago and suddenly my backups are much more reliable. (I've been meaning to post here with the experience, but I was waiting to make sure it made a difference. I'm positive it has at this point though I don't feel comfortable yet it's completely solved it) In dvd-handler line 112 add the flag to the list of default flags: self.growparams = -dvd-compat -A 'Bacula Data' -input-charset=default -i so-level 3 -pad + \ -p 'dvd-handler / growisofs' -sysid 'BACULADATA' -R Wes, thank you for posting about this and your experiences. Once I get my system entirely automated I will then be able to make an assessment to determine if your suggested modification to dvd-handler makes a difference. Then we can compare notes. Hopefully other Bacula DVD proponents can also consider this if they are having stability problems writing to DVD+RW. Cheers, -H -- In the bathtub of history the truth is harder to hold than the soap, and much more difficult to find. -- Terry Pratchett - 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
Re: [Bacula-users] Running Bacula with Virtual Machines! + partially blanking DVD+RW (trouble)
On 11/1/07, Arno Lehmann [EMAIL PROTECTED] wrote: Hi, 01.11.2007 16:43,, Hydro Meteor wrote:: Hello all -- I'm not sure how many others have run into this problem, but according to the Bacula User's Guide, there are two ways to blank an unformatted (fresh from the spindle) DVD disc (in my case I'm using / testing DVD+RW discs): 1.) Not the entire disc: # dd if=/dev/zero bs=1024 count=512 | growisofs -Z /dev/xxx=/dev/fd/0 2.) The entire disc: # growisofs -Z /dev/xxx=/dev/zero ... Getting back the aforementioned, what I find a bit strange however is that partially blanking a new DVD+RW out of the box yields error for me, as in (where /dev/cdrom is how Debian, as standard practice, see the mapped SuperDrive on the Xserve): ... However, if I formatted an entire DVD+RW disc, I had no problems getting the Storage Daemon to complete a backup job writing to the fully blanked DVD. Oh god... that is a really difficult question, I think. When I was working on the dvd-handler script, I tried lots of things. What you see dvd-handler doing is, basically, what I found worked for me. Sorry to ask a painful question :-) ... but in your answer, I have many more times appreciation of what you must have gone through (the pain and the suffering). I worked with - if I recall correctly - three different DVD writer drives, DVD+R, DVD-R, DVD+RW, and DVD-RW. I juggled dozens of different disk around, and managed to make some unusable, some unreadable by some, but not all my, DVD drives, and so on. I also read lots and lots of stuff on DVD formats, the differences between + and - media, the different ways of formatting, and so on. In the end, I didn't understand anything :-) , heh! I can understand -- there's lots to collect. Also, you probably started this project before you would have the benefits of community organized information sources such as Wikipedia, true? read through my notes, and implemented what worked in most of my test cases. For example, I found that to effectively blank a DVD for use in one drive, I needed a minimum size of data overwritten, while other drives (or the drivers handling them) accepted a disk as empty when only the first few sectors were blanked. Question: how do DVD disc media vendors (TDK, Verbatim, et al) ship DVD media? I have no idea :-) There is a difference between an unsed disk and a blanked or a formatted one. I don't recall the details now, but Restricted Overwrite was one example of how you can handle the same type of media in different ways... I presume that they do not fill the bits on their DVDs with ASCII NULL characters (which is what happens when utilizing the /dev/zero device), true? I guess you're right there. The actual disk contents is probably simply invalid to all the interpretation layers above physical. If you want to know more, you might try to use the dvd-handler test command - I believe it reports an excerpt of the actual disk status. Naturally, dvd+rw-mediainfo, which is used by dvd-handler, has much more information to print. Arno and friends, it was the dvd+rw-mediainfo (running in Debian as the Guest Operating System under Parallels as a virtual machine) that gave me the info which then gave me hints and clues. For example, I am using TDK 4.7GB DVD+RW discs. When I rand the dvd+rw-mediainfo after inserting a new TDK DVD+RW out of the spindle, I got the following output: $ dvd+rw-mediainfo /dev/cdrom INQUIRY:[MATSHITA][DVD-R UJ-85J ][FDSA] GET [CURRENT] CONFIGURATION: Mounted Media: 1Ah, DVD+RW Media ID: PHILIPS/041 Current Write Speed: 4.0x1385=5540KB/s Write Speed #0:4.0x1385=5540KB/s Write Speed #1:2.4x1385=3324KB/s Speed Descriptor#0:01/2295103 [EMAIL PROTECTED]/s [EMAIL PROTECTED] =5540KB/s Speed Descriptor#1:01/2295103 [EMAIL PROTECTED]/s [EMAIL PROTECTED] =3324KB/s READ DVD STRUCTURE[#0h]: Media Book Type: 00h, DVD-ROM book [revision 0] Legacy lead-out at:2295104*2KB=4700372992 READ DISC INFORMATION: Disc status: blank Number of Sessions:1 State of Last Session: empty Next Track: 1 Number of Tracks: 1 READ FORMAT CAPACITIES: unformatted: 2295104*2048=4700372992 26h(0):2295104*2048=4700372992 READ TRACK INFORMATION[#1]: Track State: blank Track Start Address: 0*2KB Free Blocks: 2295104*2KB Track Size:2295104*2KB READ CAPACITY: 0*2048=0 The output correctly identifies my Apple Xserve's OEM DVD burner (their SuperDrive) as being from Matshita (I think a division of Panasonic). It was in this output that I found a useful hint -- to use a block size of 2048 bytes instead of the typical (and recommended in the Bacula User's
Re: [Bacula-users] DVD+RW: is reformatting the same as blanking?
Arno, et all: Thanks for the pointers to these sites. The depths of the optical media world is one that most people can usually take for granted but when one finds oneself in the Bacula DVD business, then these depths are important to understand (such as these terms). Cheers, -H On 11/1/07, Arno Lehmann [EMAIL PROTECTED] wrote: Hi, 01.11.2007 17:55,, Hydro Meteor wrote:: Hello all -- I'm trying to get my semantic understanding correct. The Bacula User's Guide regarding DVD use states the following: Reformatting DVD+RW 10-20 times can apparently make the medium unusable. Normally you should not have to format or reformat DVD+RW media. If it is necessary, current versions of growisofs will do so automatically. Is reformatting the same as blanking (meaning, writing ASCII NULL characters to, say, the entire disc if blanking the entire disc)? Thanks for any clarification on the terminology. Using some of my older notes, and my old friend google, the best thing I can offer are some links: http://www.mail-archive.com/[EMAIL PROTECTED]/msg11301.html and http://fy.chalmers.se/~appro/linux/DVD+RW/ on the latter page, go to the paragraph starting with Formatting the BD and DVD+RW media. Hope this helps, Arno Cheers. - 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 -- Arno Lehmann IT-Service Lehmann www.its-lehmann.de - 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 - 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
Re: [Bacula-users] DVD+RW overwrites
On 11/1/07, John Drescher [EMAIL PROTECTED] wrote: For those in Bacula DVD userland who are using DVD+RWs, it strikes me as if 1,000 overwrites is really not all that bad. For example, if I have a dedicated DVD+RW disc for incremental backups that I re-use (and blank out completely) once every Wednesday (such as in between Full backups run once every Sunday), that's about 52 Wednesdays per year (and about 1,000 read/write mounts gets me about 19 years). Unless of course one has to conduct numerous restores from the Wednesday DVD+RW disc, how would this add up quickly? Do Bacula sys admins who are using DVD+RW media re-use the same discs for many days of the week ( e.g., appending incrementals to the same disc for, say, an entire week or more)? I might be missing something as I'm a bit bleary eyed from too much Bacula DVD testing today. I use a lot of DVD+RW and I can say that with DVD players DVD+RW media becomes useless in less than 100 passes but this media is still good enough for data as long as you read it on the writer that burned it. I think the one thing that you are not considering here is that with bacula the whole dvd is not written in one pass and so it gets mounted a few times during the write operation. I believe this process will reduce this 1000 number significantly but I have never tested that. John, thank you for sharing your experiences. Its a good reminder that 1,000 is probably quite liberal. I wonder if Kern (or whomever maintains the Bacula User's Guide) would consider revising to incorporate your experiences? The good news is that for basic servers where DVD capacities are fine, DVD+RWs are quite cheap at about $1 USD per disc. Cheers, -H John - 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
Re: [Bacula-users] Running Bacula with Virtual Machines! + partially blanking DVD+RW (trouble)
On 11/2/07, Arno Lehmann [EMAIL PROTECTED] wrote: Hi, 02.11.2007 16:28,, Hydro Meteor wrote:: On 11/1/07, *Arno Lehmann* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: ... Sorry to ask a painful question :-) It actually didn't hurt, it just reminded me that sometimes I try to work on things without actually understanding enough of the problem :-) Ok, now I don't feel as badly about asking a painful question! ... but in your answer, I have many more times appreciation of what you must have gone through (the pain and the suffering). It wasn't that bad, actually. It took some time, but I did learn a lot, after all, I got paid for that work :-) Great for you! Its always great if you can get paid for learning (instead of paying tuition to the school or educator). ... In the end, I didn't understand anything :-) , heh! I can understand -- there's lots to collect. Also, you probably started this project before you would have the benefits of community organized information sources such as Wikipedia, true? Well, kind of... there was information available, but I think I was slowed down a bit by not really understanding the technological issues. I might have had better results with more time (rather obvious) or if I restricted my attempt to get results to only one type of media (like DVD+RW) but, contributing to an open source project, I decided that, whatever I came up with, should be as universally usable as possible. Thank you, that is quite noble to do (because not everyone is going to use DVD+RW that's for sure). ... Arno and friends, it was the dvd+rw-mediainfo (running in Debian as the Guest Operating System under Parallels as a virtual machine) that gave me the info which then gave me hints and clues. For example, I am using TDK 4.7 GB DVD+RW discs. When I rand the dvd+rw-mediainfo after inserting a new TDK DVD+RW out of the spindle, I got the following output: $ dvd+rw-mediainfo /dev/cdrom INQUIRY:[MATSHITA][DVD-R UJ-85J ][FDSA] GET [CURRENT] CONFIGURATION: Mounted Media: 1Ah, DVD+RW Media ID: PHILIPS/041 Current Write Speed: 4.0x1385=5540KB/s Write Speed #0:4.0x1385=5540KB/s Write Speed #1:2.4x1385=3324KB/s Speed Descriptor#0:01/2295103 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#1:01/2295103 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s READ DVD STRUCTURE[#0h]: Media Book Type: 00h, DVD-ROM book [revision 0] Legacy lead-out at:2295104*2KB=4700372992 READ DISC INFORMATION: Disc status: blank Number of Sessions:1 State of Last Session: empty Next Track: 1 Number of Tracks: 1 READ FORMAT CAPACITIES: unformatted: 2295104*2048=4700372992 26h(0):2295104*2048=4700372992 READ TRACK INFORMATION[#1]: Track State: blank Track Start Address: 0*2KB Free Blocks: 2295104*2KB Track Size:2295104*2KB READ CAPACITY: 0*2048=0 The output correctly identifies my Apple Xserve's OEM DVD burner (their SuperDrive) as being from Matshita (I think a division of Panasonic). It was in this output that I found a useful hint -- to use a block size of 2048 bytes instead of the typical (and recommended in the Bacula User's Guide) of 1024 bytes, as the value of the bs= option in the dd command, like this: That is really astonishing... as far as I recall, all DVD and CD technologies use 2k block sizes, and I believe this is required by the standards they follow. So, 2k blocks for dd should have been used from the start :-) For a moment I thought my eyes went buggy and I had made a mistake in my assertion, but since you also found that astonishing I thought I'd double check. Yep, here it is: http://www.bacula.org/rel-manual/DVD_Volumes.html#SECTION00274 # Bacula only accepts to write to blank DVDs. To quickly blank a DVD+/-RW, run this command: dd if=/dev/zero bs=1024 count=512 | growisofs -Z /dev/xxx=/dev/fd/0 Then, try to mount the device, if it cannot be mounted, it will be considered as blank by Bacula, if it can be mounted, try a full blank (see below). Based on this email thread, the line of interest should be corrected to state: dd if=/dev/zero bs=2048 count=512 | growisofs -Z /dev/xxx=/dev/fd/0 I think this is an important correction to make especially for people who are not familiar with writing to optical media with low level command line tools. What is the proper procedure to kindly ask Kern to update this for a future revision of the Bacula User's Guide? Also, I think it might help to distinguish (for emphasis purposes
Re: [Bacula-users] Bacula for MacOSX
Matthias, I'm backing up Intel Xserves running Mac OS X Server 10.4.10 (not Leopard yet) with Bacula. Indeed be sure to understand HFS+ from Apple's on-line documentation. Be sure to include the Bacula Directive for HFS+ Support as in: hfsplussupport = yes Especially if you want to back up resource forks (am not sure about ACLs but what I would do if I were you is test it). I am not backing up hard disc volumes that have resource forks on them so I'm not sure about ACLs (what I do instead is I use Apple's command-line tools such as hdiutil to take device or block-level snapshots of the Xserve's boot disc) but I use Bacula to back up non-boot disc volumes (e.g., used for data and applications). Bacula also has a really cool Verify Job option that lets you take a file system snapshot and compare future backup jobs against the snapshot to see what if anything has changed (a nice Tripwire-like feature). Go for it! Bacula rocks! Who needs Time Machine in Leopard anyway ;-) -Hydro On 10/27/07, Matthias Schuendehuette [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have some questions regarding the filesystem support on MacOS 10.4.x a.k.a. 'Tiger': What does HFS+ support mean? Are Resource Forks backed up? (I think 'yes') Are BSDs extended attributes (chflags(1)) backed up? Are ACLs backed up? TIA - Matthew - -- Ciao/BSD - Matthias Matthias Schuendehuettemsch [at] snafu.de, Berlin (Germany) PGP-Key at pgp.mit.edu and wwwkeys.de.pgp.net ID: 0xDDFB0A5F -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (Darwin) iD8DBQFHI7VHf1BNcN37Cl8RAogEAJkBirRwDV+9iUYhg8pFwP7ir4z16QCeLF76 TNHXTCdVtVBkujRXueBr4WA= =9eAV -END PGP SIGNATURE- - 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 - 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
[Bacula-users] Running Bacula with Virtual Machines! + partially blanking DVD+RW (trouble)
Hello all -- I'm not sure how many others have run into this problem, but according to the Bacula User's Guide, there are two ways to blank an unformatted (fresh from the spindle) DVD disc (in my case I'm using / testing DVD+RW discs): 1.) Not the entire disc: # dd if=/dev/zero bs=1024 count=512 | growisofs -Z /dev/xxx=/dev/fd/0 2.) The entire disc: # growisofs -Z /dev/xxx=/dev/zero It could be merely the environment I'm using: Bacula 2.2.3, growisofs 7.0with the Bacula patch from Debian, running on a Debian 4.0r1 system as (and yes this may sound convoluted but it works) a Guest Operating System as a virtual machine using Parallels Desktop 3.0 for the Mac, running on top of Mac OS X Server 10.4.10 (the Host Operating System) on an Intel Xserve (with Apple's internal build-to-order slot-loading SuperDrive option). I had at first tried to get a patched version of growisofs to work natively on Mac OS X Server but was unsuccessful (but I would like to re-visit this so that I could remove the extra workaround I have come up with). So what's really cool is that Parallels offers Bridged Ethernet capabilities such that I can give my Debian Guest OS its own static IP address on the same LAN as my Xserve (even though the Mac OS X Server Host OS has its own separate static IP address). So I have the Bacula Director and File Daemons running on Mac OS X Server, which communicate over the wire (thanks to Bridged Ethernet by Parallels) with the Storage Daemon running inside the Debian Guest OS via Parallels (just as if Debian were running on its own dedicated hardware attached to the same subnet). Parallels maps the Xserve slot-loading SuperDrive at a low level perfectly, provisioning it to the Guest OS (Debian). So all of the command-line tools that Bacula Storage Daemons leverages (mkisofs, growisofs, dvd-handler, etc.) work quite well. Getting back the aforementioned, what I find a bit strange however is that partially blanking a new DVD+RW out of the box yields error for me, as in (where /dev/cdrom is how Debian, as standard practice, see the mapped SuperDrive on the Xserve): Executing 'builtin_dd if=/dev/fd/0 of=/dev/cdrom obs=32k seek=0' 512+0 records in 512+0 records out 524288 bytes (524 kB) copied:-[ GET EVENT failed with SK=5h/ASC=24h/ACQ=00h]: Input/output error /dev/cdrom: pre-formatting blank DVD+RW... , 0.126177 seconds, 4.2 MB/s /dev/cdrom: Current Write Speed is 4.1x1352KBps. builtin_dd: 256*2KB out @ average 0.4x1352KBps /dev/cdrom: flushing cache /dev/cdrom: stopping de-icing :-[ STOP DE-ICING failed with SK=4h/ASC=44h/ACQ=00h]: Input/output error /dev/cdrom: writing lead-out Note: the first I/O error in the output above (regarding GET EVENT is something that I always see such as when following Richard Mortimer's excellent Bacula DVD tips web pagehttp://bridge.oldelvet.org.uk/bacula/BaculaDVDSetup.htmlfor creating stand-alone tests with both growisofs and dvd-handler and have been able to ignore). Fascinating, what does de-icing mean? For whatever reason, the de-icing process ran into an I/O error. Even so, I tried to request the Storage Daemon (via the Bacula Console) to back up to this disc that was not properly de-iced, and I had subsequent fatal errors. However, if I formatted an entire DVD+RW disc, I had no problems getting the Storage Daemon to complete a backup job writing to the fully blanked DVD. Question: how do DVD disc media vendors (TDK, Verbatim, et al) ship DVD media? I presume that they do not fill the bits on their DVDs with ASCII NULL characters (which is what happens when utilizing the /dev/zero device), true? I hope this might be helpful to others, though I expect that I'm probably the only person on the planet who has such a unique configuration using Bacula with virtual machines on Apple Xserve hardware. I'd be happy to provide more details about this unusual configuration if there are others who are interested (I imagine with time as virtual machine technology increases there will be other Bacula administrators who will want the option of running Bacula on virtual machines). Cheers, Hydro P.S. A big thanks to Richard and also Dave Green in New Zealand who has also been climbing the Bacula DVD learning curve. - 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
[Bacula-users] DVD+RW: is reformatting the same as blanking?
Hello all -- I'm trying to get my semantic understanding correct. The Bacula User's Guide regarding DVD use states the following: Reformatting DVD+RW 10-20 times can apparently make the medium unusable. Normally you should not have to format or reformat DVD+RW media. If it is necessary, current versions of growisofs will do so automatically. Is reformatting the same as blanking (meaning, writing ASCII NULL characters to, say, the entire disc if blanking the entire disc)? Thanks for any clarification on the terminology. Cheers. - 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
[Bacula-users] DVD+RW overwrites
Hello all - The Bacula User's Guide for use of DVD specifically DVD+RW has this to say: DVD+RW supports only about 1000 overwrites. Every time you mount the filesystem read/write will count as one write. This can add up quickly, so it is best to mount your DVD+RW filesystem read-only. Bacula does not need the DVD to be mounted read-write, since it uses the raw device for writing. For those in Bacula DVD userland who are using DVD+RWs, it strikes me as if 1,000 overwrites is really not all that bad. For example, if I have a dedicated DVD+RW disc for incremental backups that I re-use (and blank out completely) once every Wednesday (such as in between Full backups run once every Sunday), that's about 52 Wednesdays per year (and about 1,000 read/write mounts gets me about 19 years). Unless of course one has to conduct numerous restores from the Wednesday DVD+RW disc, how would this add up quickly? Do Bacula sys admins who are using DVD+RW media re-use the same discs for many days of the week (e.g., appending incrementals to the same disc for, say, an entire week or more)? I might be missing something as I'm a bit bleary eyed from too much Bacula DVD testing today. Cheers. -H - 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
[Bacula-users] Client-only configure option (but why no analogous Storage-only option?)
Hi all, I noticed in the Bacula User's guide there is a configure option (when building Bacula from Source): --enable-client-only Described as: This option causes the make process to build only the File daemon and the libraries that it needs. None of the other daemons, storage tools, nor the console will be built. Likewise a make install will then only install the File daemon. To cause all daemons to be built, you will need to do a configuration without this option. This option greatly facilitates building a Client on a client only machine. This is fantastic. But why is there also not an equivalent option for building only the Storage Daemon? For example, I will be running the Storage Daemon only on a Debian Linux machine. The Storage Daemon need not communicate directly with the Catalog (e.g., PostgreSQL database) so I don't want to be required to build an entire Bacula system (e.g. including requisite database) for my Debian machine which will only run the Storage Daemon. Thanks for shedding any light on this! - 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
[Bacula-users] Bacula is like heaven!
Hi all -- Just a note to say a big thank you for the Bacula community and its founders! I just got a Verify Job to work successfully with SHA1 signature and verify = pins1 and it is really sweet, it works just great! Before I discovered Bacula, I was thinking I would need to learn Tripwire for monitoring file systems security-wise but Bacula is just what the doctor ordered. The fun is just beginning (for this Bacula newbie)! Cheers, -H - 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
[Bacula-users] Bacula Console: how to clear irrelevant history (yielded from status command)
Hello all -- I may have missed the answer to my question in the Bacula User's Guide (but I also looked on the Wiki and in the FAQ). I am trying to figure out how to clear out, non-relevant information which I see after running a status command. For example: *status Client Yields old terminated jobs that I've since deleted from my Catalog (or were in a previous Catalog that I was merely testing with) -- Terminated Jobs: JobId LevelFiles Bytes Status FinishedName == 1 Full 1,66456.53 M OK 30-Sep-07 03:34 Client1 21,66456.53 M OK 30-Sep-07 03:35 RestoreFiles 1 Full 1,66456.53 M OK 18-Oct-07 04:32 Backup_apple-fd 2 Incr 0 0 OK 18-Oct-07 11:52 Backup_apple-fd When querying the Catalog, I don't see these jobs anymore (which is expected) but it is somewhat annoying to see the irrelevant history returned from the status command. The answer is probably quite simple but I haven't stumbled upon the answer yet. Thank you for any pointers. -H - 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
Re: [Bacula-users] Bacula Console: how to clear irrelevant history (yielded from status command)
On 10/18/07, Eric Böse-Wolf [EMAIL PROTECTED] wrote: delete the files in the working directory of your daemons. Sorry, but that is too vague. The Bacula Working Directory has several files (state files and .bsr files) and I don't think it is wise to merely randomly delete them without prudence. Can you be more specific? Thanks. -H - 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
Re: [Bacula-users] Bacula Console: how to clear irrelevant history (yielded from status command)
On 10/18/07, C M Reinehr [EMAIL PROTECTED] wrote: On Thursday 18 October 2007 08:58, Eric Böse-Wolf wrote: delete the files in the working directory of your daemons. I think you're talking about the *.state files. It might be better to make that clear before he accidently deletes his database and bootstrap files. CMR, thanks for the clarification. I didn't want to delete the state files without first knowing if was ok to do so. And most certainly didn't want to delete the Bootstrap files. Cheers, -H cmr -- Debian 'Etch' - Registered Linux User #241964 More laws, less justice. -- Marcus Tullius Ciceroca, 42 BC - 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 - 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
Re: [Bacula-users] Bacula Console: how to clear irrelevant history (yielded from status command)
Especially for newcomers, I think it might be worthwhile adding this to the FAQ and/or the Wiki because people will most definitely want to perform testing including changing their Bacula namespaces (e.g. Client names, etc.) after running through the Tutorials such as Chapter 9 in the User's Guide (A Brief Tutorial). -H On 10/18/07, Hydro Meteor [EMAIL PROTECTED] wrote: On 10/18/07, C M Reinehr [EMAIL PROTECTED] wrote: On Thursday 18 October 2007 08:58, Eric Böse-Wolf wrote: delete the files in the working directory of your daemons. I think you're talking about the *.state files. It might be better to make that clear before he accidently deletes his database and bootstrap files. CMR, thanks for the clarification. I didn't want to delete the state files without first knowing if was ok to do so. And most certainly didn't want to delete the Bootstrap files. Cheers, -H cmr -- Debian 'Etch' - Registered Linux User #241964 More laws, less justice. -- Marcus Tullius Ciceroca, 42 BC - 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 - 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
[Bacula-users] Separate (PostgreSQL) database required for Verify Catalog?
Hi all,
I'm trying to set up a Verify Job configuration and noticed in the Bacula
User's Guide, which provides an example Catalog for running a Verify Job,
the following:
Catalog {
Name = Bacula
dbname = verify; user = bacula; password =
}
This example implies that a separate database named verify should be used
as well as a user and password to connect to such a database. However, when
I looked at (I'm using PostgreSQL 8.1.9) the scripts for making / creating /
deleting, etc. (such as create_postgresql_database, make_catalog_backup,
etc.) there are no scripts specific for managing a verify-specific database.
Rather than requiring a separate Verify database, is it possible for the
main Catalog Resource used by the Director to be shared for Verify Jobs?
Thank you,
-H
-
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
[Bacula-users] Schedule Resource Job overrides question
Hello all --
In the Director Daemon configuration file (bacula-dir.conf), I am defining a
simple backup Job Resource that points to a Schedule Resource. My Schedule
Resource contains three backup types (with corresponding Pool Resources that
I have also in the configuration file):
# When to do the backups
Schedule {
Name = Cycles
Run = Full Pool=fpool 1st sun at 03:00
Run = Differential Pool=dpool sat at 03:00
Run = Incremental Pool=ipool mon-sun at 02:30
}
I took this from an example (somewhere within the Bacula User's Guide) and
what I am wondering if the names after Run = text (e.g. Full,
Differential, and Incremental) refer to the Level? I presume its the
Level override by default but the User's Guide doesn't state so explicitly.
I just want to be sure that I can get away with this and don't need to say
something like:
Run = Level = Full Pool=fpool 1st sun at 03:00
Especially since the Pool Resource does not include the option for a Level
Directive (so its much more convenient to configure the Level as a Job
override in the Schedule Resource)!
Much thanks!
-H
-
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
[Bacula-users] Backup Job Storage Directive by reference (to the Pools through the Schedule)?
Hello all -- I want to configure a simple Backup Job Resource which does not include Storage Directive. In fact, I have three Pools (each Pool contains its own Storage Directive instance). The Pools are indirectly referred to the Backup Job Resource via the Schedule Resource that the Job refers to (e.g., with Pool= overrides in the Schedule Resource). Is it therefore logically correct for me to not include a Storage Directive in the Backup Job Resource definition (especially considering that I have multiple Storage Resources which are referred to by Pools which Pools are referred to by the Schedule Resource's Job overrides)? I hope I posed this question correctly and not too ambiguously -- Bacula is a very powerful and at times abstract system and I've learned by studying it that there is quite a bit of referential indirection possible among the various Resource data structures. Much thanks! -H - 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
Re: [Bacula-users] Schedule Resource Job overrides question
Philip,
Thank you very much for checking my logic. I also think its logically makes
sense to take your suggestion of including the multiple pools within the Job
resource as you suggest (instead of relying solely on indirect reference to
these pools via the Schedule Resource Job overrides) -- even if its a
duplicate effort, for human readability it is useful!
Cheers,
-H
On 10/10/07, Philip Clifton [EMAIL PROTECTED] wrote:
No, you don't need to put in the Level part. As a side note, you can
also designate the pools you want in the Job resource. ie:
Job {
Name = vps2
JobDefs = Default
Client = vps2-fd
FileSet = vps2
Full Backup Pool = vps2-full
Incremental Backup Pool = vps2-inc
Storage = vps2
}
Philip Clifton [EMAIL PROTECTED]
4-8-4/IntuiWORX - Intuitive, Innovative Software Development
http://www.intuiworx.com
Hydro Meteor wrote:
Hello all --
In the Director Daemon configuration file (bacula-dir.conf), I am
defining a simple backup Job Resource that points to a Schedule
Resource. My Schedule Resource contains three backup types (with
corresponding Pool Resources that I have also in the configuration
file):
# When to do the backups
Schedule {
Name = Cycles
Run = Full Pool=fpool 1st sun at 03:00
Run = Differential Pool=dpool sat at 03:00
Run = Incremental Pool=ipool mon-sun at 02:30
}
I took this from an example (somewhere within the Bacula User's Guide)
and what I am wondering if the names after Run = text ( e.g.
Full, Differential, and Incremental) refer to the Level? I
presume its the Level override by default but the User's Guide doesn't
state so explicitly. I just want to be sure that I can get away with
this and don't need to say something like:
Run = Level = Full Pool=fpool 1st sun at 03:00
Especially since the Pool Resource does not include the option for a
Level Directive (so its much more convenient to configure the Level as
a Job override in the Schedule Resource)!
Much thanks!
-H
-
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
-
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
[Bacula-users] What is mac table in Bacula Catalog (PostgreSQL)?
Hello all -- Does anyone know what the mac table is in the Bacula Catalog? When I run the drop_bacula_tables (using PostgreSQL 8.1.9 for my Bacula Catalog), I receive an error about a missing table although the end of the script finishes and everything is asserted to be just fine. I guess I can ignore this error? (output from command-line and error highlighted below) ... Thanks, -H $ ./drop_bacula_tables DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE psql:stdin:19: ERROR: table mac does not exist DROP TABLE DROP TABLE DROP TABLE Deletion of Bacula PostgreSQL tables succeeded. Dropped PostgreSQL tables - 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
Re: [Bacula-users] Optical DVD low reliability?
John and Eric, Thank you both for your feedback (also valuable to the Bacula community particularly those who are new to Bacula). There is indeed more to using optical media than at first what meets the eye but if it is indeed true that using optical DVD is still somewhat beta-like in a Bacula-specific context then I am all all for pushing things forward and doing some of my own testing and reporting back the results to the Bacula community. I'll be using an Apple Xserve Intel machine (current version of this machine) which supports a variety of DVD formats (read-only and read/write) but not DVD-RAM. Cheers, -Hydro On 10/2/07, Eric Böse-Wolf [EMAIL PROTECTED] wrote: Hello Hydro, Hydro Meteor [EMAIL PROTECTED] writes: DVD media is not recommended for serious or important backups because of its low reliability. I wonder how long ago this statement was written and if this still remains true today ( e.g., have there been improvements to DVD optical media over time)? DVD-RAM was built with the intention that it keeps data save for 30 years. DVD-RAM has a defect management. DVD-RAM has a metallic dye different to DVD-R, DVD+R, DVD-RW, DVD+RW, CD-R, CD-RW. DVD-RAM is much slower (! 3x or 5x) than the other optical formats. DVD-RAM is available in catridges to protect the media against physical harm, there are even DVD-RAM burners which accepts directly the catridge. But it is, as any phase change media, not suited for archival long term backup. See: http://en.wikipedia.org/wiki/Dvd-ram The information of the metallic dye was only on german wikipedia: http://de.wikipedia.org/wiki/DVD-RAM mfg Eric - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Optical DVD low reliability?
Hello all -- I have been reading more thoroughly on using Bacula to back up to optical DVD. In Chapter 3 (page 22) of the current Bacula PDF guide, there is this statement: DVD media is not recommended for serious or important backups because of its low reliability. I wonder how long ago this statement was written and if this still remains true today (e.g., have there been improvements to DVD optical media over time)? I wonder how current Bacula users who have decided to back up to optical DVD media have found it to be in terms of reliability? Are there any independent reliability studies around? Besides the low reliability concern, are there any other reasons to avoid using optical DVD with Bacula other than what has been written in Chapter 24 titled DVD Volumes of the current Bacula User's Guide? Thank you! -H - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Incremental / Differential logical analysis
On 9/17/07, Arno Lehmann [EMAIL PROTECTED] wrote: Hi, 18.09.2007 10:36,, Eric Böse-Wolf wrote:: Hydro Meteor [EMAIL PROTECTED] writes: Martin, Thank you for checking my logic. I wonder if it would be worthwhile to the Bacula community to have some simple diagrams that accompany the User's Guide, such a diagram that shows a timeline and how Bacula Jobs operate along such a timeline? I'd be pleased contribute some graphics to the documentation if that's something other people would also be interested in. Personally, I don't see the need for this - the underlying logic is quite clear to me - but of course it might help you and others. Probably with time if any person spends enough time with Bacula, they will be able to navigate Bacula configuration files with much ease as they have the logic all mapped out in their heads. The Tutorial for newcomers is really quite nice and it does get someone up and running and testing Bacula rather swiftly but I think that sometimes diagrams that map out abstractions and visualize logic constructs (such as visualizing multiple Backup Level types with a few scenarios for Full, Differential, Incremental, etc.) might be useful. Last year I attended one of Dr. Edward Tufte's http://www.edwardtufte.com/tufte/ seminars and one of the things Tufte said in his lecture which I thought was very insightful was that different people have different cognitive styles. In my case I probably have a cognitive style preference for having some abstractions laid out visually. This isn't an advertisement for Dr. Tufte's books but some of his books are really quite good such as Beautiful Evidence, which I recommend. As I continue to work out a Bacula operational system on my Xserve, I will create a few timeline graphic flow charts and once I have them refined I'd be pleased to contribute them to the Bacula Wiki and/or User's Guide. I would really appreciated it. I noticed: If I have two Jobs, both on the same Client with the same FileSet but with different schedules, Bacula will make two Full Backups as the individual job has never had a Full Backup before, even if the other job did a Full backup a few days ago. Maybe thats something, that could be mentioned, too. That's just what a job is for - a job is an independent entity and never refers to data from other jobs. I don't know if the manual is very clear on this, but again, I never had problems understanding this. But you are right - from time to time, people don't understand this, set up one job for full, one for differential, and one for incremental backups and wonder why it does not work as expected. Some introduction to the concepts of jobs in relation to client, fileset and schedule definition would probably be a good addition to the manual. The basic idea would be to point out that filesets, schedules and even client definitions can be used in many jobs, but that each job is independent from any other jobs and thus holds its own, complete set of backed up data, even though that data can overlap with the data from other jobs. Now someone needs to write that up in a two-page text that clearly describes this to novice users :-) This conceptualization might indeed be ripe for a combined text and visual explanation. I use tools like Visio which can export graphics in open formats such as SVG and PDF. Cheers! Arno -- Arno Lehmann IT-Service Lehmann www.its-lehmann.de - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Incremental / Differential logical analysis
Hello all,
I am trying to ensure I have a strict understanding of the Bacula User's
Guide with respect to how Differential and Incremental Backups work, but I
would like to take an example to see if I have worked through my logic
correctly ...
Lets say I have this FileSet definition which is fixed throughout the
example herein:
# List of files to be backed up
FileSet {
Name = Full Set
Include {
Options {
signature = MD5
}
File = /Users/admini/bacula-2.2.3
}
Exclude {
File = /proc
File = /tmp
File = /.journal
File = /.fsck
}
}
Assuming this FileSet definition does not change. I then:
1. Make the first Full backup of the Included File (which is a directory
named /Users/admini/bacula-2.2.3)
2. After a period of time, let's say that one file underneath the the
directory /Users/admini/bacula-2.2.3 is modified, such as:
/Users/admini/bacula-2.2.3/A
3. After the modification, I ask Bacula to make an Incremental backup to a
Volume labeled INC1 which only contains this single change:
/Users/admini/bacula-2.2.3/A
4. After the Incremental backup, another file is in the Included directory
is changed:
/Users/admini/bacula-2.2.3/B
5. After this change, I perform a Differential backup. The Volume created by
the Differential backup is labeled DIFF1 and contains only but both (merge
so-to-speak) these files:
/Users/admini/bacula-2.2.3/A
/Users/admini/bacula-2.2.3/B
6. Ok, after the DIFF1 Volume was created, two files are changed (one of
which was previously changed and resides in the DIFF1 Volume) and a new file
is added:
/Users/admini/bacula-2.2.3/A (2)
/Users/admini/bacula-2.2.3/C
/Users/admini/bacula-2.2.3/ADDEDFILE
7. After the files modified and added in step 6 above, I perform a second
Incremental backup to a different Volume named INC2. It is my understanding
from the Bacula User's Guide that this INC2 will only contain what has
changed since the time of the previous Differential, which will then be:
The most recent version (second modification which I denote with (2) ) of:
/Users/admini/bacula-2.2.3/A (2)
and the new modification to:
/Users/admini/bacula-2.2.3/C
and the file that was added:
/Users/admini/bacula-2.2.3/ADDEDFILE
Is my analysis using the above examples and understanding of how Bacula
works correct? I wasn't totally clear on what happens if files are added to
an Included File where the Included File is itself a directory. It is clear
however that any files which are deleted remain in the Catalog until the
next Full backup volume is created.
Thank you very much!
-H
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Incremental / Differential logical analysis
Martin,
Thank you for checking my logic. I wonder if it would be worthwhile to the
Bacula community to have some simple diagrams that accompany the User's
Guide, such a diagram that shows a timeline and how Bacula Jobs operate
along such a timeline? I'd be pleased contribute some graphics to the
documentation if that's something other people would also be interested in.
Cheers,
-H
On 9/17/07, Martin Simmons [EMAIL PROTECTED] wrote:
On Sun, 16 Sep 2007 20:21:21 -1000, Hydro Meteor said:
Hello all,
I am trying to ensure I have a strict understanding of the Bacula User's
Guide with respect to how Differential and Incremental Backups work, but
I
would like to take an example to see if I have worked through my logic
correctly ...
Lets say I have this FileSet definition which is fixed throughout the
example herein:
# List of files to be backed up
FileSet {
Name = Full Set
Include {
Options {
signature = MD5
}
File = /Users/admini/bacula-2.2.3
}
Exclude {
File = /proc
File = /tmp
File = /.journal
File = /.fsck
}
}
Assuming this FileSet definition does not change. I then:
1. Make the first Full backup of the Included File (which is a directory
named /Users/admini/bacula-2.2.3)
2. After a period of time, let's say that one file underneath the the
directory /Users/admini/bacula-2.2.3 is modified, such as:
/Users/admini/bacula-2.2.3/A
3. After the modification, I ask Bacula to make an Incremental backup to
a
Volume labeled INC1 which only contains this single change:
/Users/admini/bacula-2.2.3/A
4. After the Incremental backup, another file is in the Included
directory
is changed:
/Users/admini/bacula-2.2.3/B
5. After this change, I perform a Differential backup. The Volume
created by
the Differential backup is labeled DIFF1 and contains only but both
(merge
so-to-speak) these files:
/Users/admini/bacula-2.2.3/A
/Users/admini/bacula-2.2.3/B
6. Ok, after the DIFF1 Volume was created, two files are changed (one of
which was previously changed and resides in the DIFF1 Volume) and a new
file
is added:
/Users/admini/bacula-2.2.3/A (2)
/Users/admini/bacula-2.2.3/C
/Users/admini/bacula-2.2.3/ADDEDFILE
7. After the files modified and added in step 6 above, I perform a
second
Incremental backup to a different Volume named INC2. It is my
understanding
from the Bacula User's Guide that this INC2 will only contain what has
changed since the time of the previous Differential, which will then be:
The most recent version (second modification which I denote with (2) )
of:
/Users/admini/bacula-2.2.3/A (2)
and the new modification to:
/Users/admini/bacula-2.2.3/C
and the file that was added:
/Users/admini/bacula-2.2.3/ADDEDFILE
Is my analysis using the above examples and understanding of how Bacula
works correct? I wasn't totally clear on what happens if files are added
to
an Included File where the Included File is itself a directory. It is
clear
however that any files which are deleted remain in the Catalog until the
next Full backup volume is created.
Yes, pretty much correct. The only problem is if ADDEDFILE has both its
creation and modification dates older than the Differential backup. This
won't usually happen on Unix, but can easily happen on Windows.
__Martin
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Seeking clarification: Priority Directive implemented or not for Client resource?
Hello all, I have continued my intense reading through the mostly excellent Bacula User's Guide and found on page 170 (Chapter 11: Configuring the Director) the section about the Priority Directive: Priority = number The number specifies the priority of this client relative to other clients that the Director is processing simultaneously. The priority can range from 1 to 1000. The clients are ordered such that the smaller number priorities are performed first (not currently implemented). The last sentence says with parentheses (not currently implemented). So, am curious, if the Clients are not ordered because this ordering is not implemented, then how does the Priority Directive work for Clients, if it works at all for Clients? Should the Priority Directive be ignored for Client resources? Note: I did notice that the sample Bacula Director configuration file ( bacula-dir.conf) which is created during configure / make install, does provide a Priority Directive value (10 and 11) for example DefaultJob and Catalog Backup Jobs but I also understand from the User's Guide that the context for the Priority Directive is different for these resources compared to the Client resource. This inconsistency at first-glance (of Priority Directive for Client resources not currently implemented, being different in behavior than for DefaultJob and BackupCatalog Job) is a little bit confusing but understandable that the context is different for different types of resources. Thanks for any clarifications / insights regarding the Client resource Priority Directive. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Seeking clarification: Maximum Concurrent Jobs (File Daemon)
Hello all,
In the Bacula User's Guide I discovered, in Chapter 12.1 (The Client
Resource), that the Maximum Concurrent Jobs default value is 2:
Maximum Concurrent Jobs = number where number is the maximum number of
Jobs that should run concurrently. The default is set to 2, but you may
set it to a larger number. Each contact from the Director (e.g. status
request, job start request) is considered as a Job, so if you want to be
able to do a status request in the console at the same time as a Job is
running, you will need to set this value greater than 1.
However, in the sample File Daemon configuration file (bacula-fd), a Maximum
Concurrent Jobs value is set to 20. That's an order of magnitude more than
2. Wow that's a big difference!
Here's an example after a fresh configure / make install on my Xserve:
#
# Global File daemon configuration specifications
#
FileDaemon { # this is me
Name = xserve-fd
FDport = 9102 # where we listen for the director
WorkingDirectory = /opt/local/var/bacula/working
Pid Directory = /opt/local/var/run
Maximum Concurrent Jobs = 20
}
I am curious, is the documentation outdated and should the default value
really be 20? Is there possibly a typographical error where 2 meant to be
typed as 20? Did the core Bacula maintainers (Kern, et al?) change their
mind based on real world user experiences from a default of 2 to 20?
Also, since I am coming up the learning curve with Bacula, I probably don't
understand enough yet about the entirety of Bacula and how the daemons
interoperate, but it seems a little bit strange that the Client Resource
which is also synonymous with the File Daemon has two different default
values for Maximum Concurrent Jobs based on context (in the Bacula Director
configuration context the Maximum Concurrent Jobs default value for the
Client resource is 1 but in the Bacula File Daemon configuration context the
Client's Maximum Concurrent Jobs default value is 2 (or maybe now its 20)?).
I wonder if there might be a better way to more clearly articulate the
abstract differences with respect to the context of the configuration files
for the daemons? I'd be happy to contribute some documentation to this
effect if the Bacula community would find it helpful especially for bringing
new members of the community up the learning curve somewhat faster.
Thank you for any clarification.
-H
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Duplicate Address field values ok?
On 9/13/07, Arno Lehmann [EMAIL PROTECTED] wrote:
Hi,
10.09.2007 23:57,, Hydro Meteor wrote::
Hello again Arno,
Today I just pulled down Kern's update to Bacula (version 2.2.3) and I
installed it effortlessly on my Xserve. I am running all three Bacula
daemons on the same Xserve machine. I edited the bconsole.conf file (to
change its address field by changing its value to the static IP
address of my Xserve). I did the same for all of the Address fields in
the Bacula Director configuration file (bacula-dir.conf).
Even so, when I ran bconsole for the first time, I received this
message:
10-Sep 21:24 apple-xserve-dir: - Console-.2007-09-10_21.24.24 Error:
bsock.c:182 gethostbyname() for host apple-xserve failed:
ERR=Authoritative answer for host not found.
This *might* have been an old message still spooled - look at the time
stamp. It is possible that this was from before your configuration change.
Thank you Arno, I believe you are correct. This message has since not
duplicated so it was probably an old message spooled.
Where apple-xserve is the host name of my machine. But none of my
Address fields in the config files have the value of apple-xserve any
more. I wonder what file the console is reading which causes it to
continue to attempt to use gethostbyname() with the name apple-xserve
instead of my server's IP address?
How would I discover this, any ideas?
Does it happen again, or was this a one-time problem?
Appears to be a one-time problem.
As long as you use IP addresses only in the configuration files, I
don't see where name resolving can fail...
Thank you very much ... its a joy and a challenge to learn about Bacula!
Cheers,
-H
Thanks!
-H
On 9/9/07, *Arno Lehmann* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
Hi,
10.09.2007 05:12,, Hydro Meteor wrote::
Hello,
In Chapter 6.3.4 of the Bacula User's Guide, with regard to
naming
resources, the Guide states that:
Each of your Bacula components must have a unique name.
This is especially necessary when backing up a fleet machines.
I didn't see any similar requirements that the Address fields of
resources also be unique. Can anyone confirm this? For example,
would
the following (in the bacula-dir.conf file) have any conflicts?
# Client (File Services) to backup
Client {
Name = myunique-machine-name-1
Address = 192.168.1.25 http://192.168.1.25
http://192.168.1.25
FDPort = 9102
Catalog = MyCatalog
Password = YxR21sehW8stTml8RUKYAfln3WSVPoyvJVJ276RqXRmY
# password for FileDaemon
File Retention = 30 days# 30 days
Job Retention = 6 months# six months
AutoPrune = yes # Prune expired
Jobs/Files
}
and
# Client (File Services) to backup
Client {
Name = myunique-machine-name-2
Address = 192.168.1.25 http://192.168.1.25
http://192.168.1.25
FDPort = 9102
Catalog = MyCatalog
Password = YxR21sehW8stTml8RUKYAfln3WSVPoyvJVJ276RqXRmY
# password for FileDaemon
File Retention = 30 days# 30 days
Job Retention = 6 months# six months
AutoPrune = yes # Prune expired
Jobs/Files
}
As much as it would be ideal to use a FQDN for the Address
fields, there
are some scenarios where this isn't possible and there is a
concern from
my colleague, about a collision in the Address fields. Hopefully
as
interpreted from the User's Guid, the uniqueness of the Name
fields is
all that's required (but better to check ahead of time to be safe
than
sorry later).
I think what you intend to do would work. It's even a procedure I
suggested a few times, and nobody complained that it didn't work :-)
Although, in most cases, I suspect you won't need this sort of
setup.
Would yo mind explaining why you think you need this?
Arno
--
Arno Lehmann
IT-Service Lehmann
www.its-lehmann.de http://www.its-lehmann.de
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
mailto:Bacula-users
Re: [Bacula-users] Seeking clarification on Volume Retention Period
On 9/11/07, Martin Simmons [EMAIL PROTECTED] wrote: On Tue, 11 Sep 2007 17:16:23 -1000, Hydro Meteor said: Hello all, From the User's Guide (Terminology Chapter 1.6), regarding the Retention Period, an except that I have a question about: The Volume Retention Period is the minimum of time that a Volume will be kept before it is reused. Bacula will normally never overwrite a Volume that contains the only backup copy of a file. Under ideal conditions, the Catalog would retain entries for all files backed up for all current Volumes. Once a Volume is overwritten, the files that were backed up on that Volume are automatically removed from the Catalog. However, if there is a very large pool of Volumes or a Volume is never overwritten, the Catalog database may become enormous. To keep the Catalog to a manageable size, the backup information should be removed from the Catalog after the defined File Retention Period. Bacula provides the mechanisms for the catalog to be automatically pruned according to the retention periods defined. I just want to make sure I understand this sentence: To keep the Catalog to a manageable size, the backup information should be removed from the Catalog after the defined File Retention Period. The backup information that should be removed is information about any Volume or Pool of Volumes correct? I think not. Firstly, remember that there are two kinds of information in the catalog: - Mostly static stuff about the pools and volumes. This is never pruned automatically and you don't generally remove it from the catalog unless the volumes have been destroyed or you want Bacula to forget about them. - Dynamic stuff about jobs that have run. This consists of the list jobs with the media contains them and also a list of the files in each job. The Volume, Job and File retention periods control pruning of the dynamic information. The sentence you quoted is talking about the list of the files in each job, which is almost always the largest part of the catalog. Hello Martin, Thank you for the clarification and separating out the mostly static from the highly dynamic information that is stored in the Catalog (database). This makes a lot of sense. Indeed, I will not want to purposefully delete the static info about the volumes and pools (unless as you said they are destroyed and there is a good reason for Bacula to not remember they exist). I can understand how therefore its really critical to also back up the Catalog itself! Cheers, -H Secondly, what do Bacula users do, strategically, when it comes to archiving data into perpetuity? For example, what if a government agency or a law firm wanted to use Bacula to back up files to Volumes which Volumes should neverbe overwritten? Of course the Catalog still needs to be pruned, but even so, have I understood correctly that even if a Volume has been pruned out of the Catalog, it can later be scanned (using the bscan tool) and data extracted (using the bextract tool)? In doing so, no Volumes are ever overwritten but they are still recoverable in the future and at the same time the Catalog database won't grow to mammoth proportions? Yes, you are correct about bextract and bscan. However, the Bacula terminology prune only applies to the job and file information. To remove a volumes from the catalog, you need to use delete. __Martin - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Seeking clarification on Volume Retention Period
Hello all, From the User's Guide (Terminology Chapter 1.6), regarding the Retention Period, an except that I have a question about: The Volume Retention Period is the minimum of time that a Volume will be kept before it is reused. Bacula will normally never overwrite a Volume that contains the only backup copy of a file. Under ideal conditions, the Catalog would retain entries for all files backed up for all current Volumes. Once a Volume is overwritten, the files that were backed up on that Volume are automatically removed from the Catalog. However, if there is a very large pool of Volumes or a Volume is never overwritten, the Catalog database may become enormous. To keep the Catalog to a manageable size, the backup information should be removed from the Catalog after the defined File Retention Period. Bacula provides the mechanisms for the catalog to be automatically pruned according to the retention periods defined. I just want to make sure I understand this sentence: To keep the Catalog to a manageable size, the backup information should be removed from the Catalog after the defined File Retention Period. The backup information that should be removed is information about any Volume or Pool of Volumes correct? Secondly, what do Bacula users do, strategically, when it comes to archiving data into perpetuity? For example, what if a government agency or a law firm wanted to use Bacula to back up files to Volumes which Volumes should neverbe overwritten? Of course the Catalog still needs to be pruned, but even so, have I understood correctly that even if a Volume has been pruned out of the Catalog, it can later be scanned (using the bscan tool) and data extracted (using the bextract tool)? In doing so, no Volumes are ever overwritten but they are still recoverable in the future and at the same time the Catalog database won't grow to mammoth proportions? Thanks to anyone for helping to clarify this situation (the archiving of records into perpetuity is a big problem in the world today especially due to the changing legal statutes worldwide when it comes to saving documents). Cheers, -H - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Duplicate Address field values ok?
On 9/9/07, Arno Lehmann [EMAIL PROTECTED] wrote:
Hi,
10.09.2007 05:12,, Hydro Meteor wrote::
Hello,
In Chapter 6.3.4 of the Bacula User's Guide, with regard to naming
resources, the Guide states that:
Each of your Bacula components must have a unique name.
This is especially necessary when backing up a fleet machines.
I didn't see any similar requirements that the Address fields of
resources also be unique. Can anyone confirm this? For example, would
the following (in the bacula-dir.conf file) have any conflicts?
# Client (File Services) to backup
Client {
Name = myunique-machine-name-1
Address = 192.168.1.25 http://192.168.1.25
FDPort = 9102
Catalog = MyCatalog
Password = YxR21sehW8stTml8RUKYAfln3WSVPoyvJVJ276RqXRmY
# password for FileDaemon
File Retention = 30 days# 30 days
Job Retention = 6 months# six months
AutoPrune = yes # Prune expired Jobs/Files
}
and
# Client (File Services) to backup
Client {
Name = myunique-machine-name-2
Address = 192.168.1.25 http://192.168.1.25
FDPort = 9102
Catalog = MyCatalog
Password = YxR21sehW8stTml8RUKYAfln3WSVPoyvJVJ276RqXRmY
# password for FileDaemon
File Retention = 30 days# 30 days
Job Retention = 6 months# six months
AutoPrune = yes # Prune expired Jobs/Files
}
As much as it would be ideal to use a FQDN for the Address fields, there
are some scenarios where this isn't possible and there is a concern from
my colleague, about a collision in the Address fields. Hopefully as
interpreted from the User's Guid, the uniqueness of the Name fields is
all that's required (but better to check ahead of time to be safe than
sorry later).
I think what you intend to do would work. It's even a procedure I
suggested a few times, and nobody complained that it didn't work :-)
Although, in most cases, I suspect you won't need this sort of setup.
Would yo mind explaining why you think you need this?
Hi Arno,
Thank you for your helpful response to my question. No worries, I don't mind
explaining. There are situations where, among a fleet of machines that are
distributed physically, these machines may be sitting behind their routers
(with stateful firewalls) whereby the machines need to have their own static
IP address issued by the router on the subnet of their LAN (e.g.,
192.168.0.25) but the routers themselves may have WAN addresses that are
dynamic. Using a dynamic DNS service, the routers can be reached globally
and then since the machines on their LAN have a static IP address, we can
use Network Address Translation (NAT) and port forwarding to reach these
machines (e.g., run a Bacula Director on a machine in Brussels and speak to
a Bacula File Daemon running on a machine in Montreal where the machine in
Montreal courtesy of NAT / Port forwarding). The machine in Montreal will
not be capable of true reverse DNS since its IP address is static but in the
router's LAN's subnet. And this is the problem since Bacula uses the
gethostbyname() function that requires a true reverse DNS lookup. There may
be more sophisticated routers now that can do some tricks to work around
this problem but I haven't had time to look into that yet and I have to
allow for a lower common denominator that some machines in given locations
may not always have a more sophisticated DNS system to then work around the
gethostbyname() function of Bacula that wants true reverse DNS to work on
that machine! In this scenario, it would be possible for two different
physical machines to have, conceivably, the same LAN-based IP address (such
as 192.168.0.25 as given in the example above) and therefore my concern
about uniqueness in the Address field. The Name field most certainly can be
unique (there are many ways to create a global namespace that virtually
eliminates the odds of a namespace collision).
Cheers,
-H
Arno
--
Arno Lehmann
IT-Service Lehmann
www.its-lehmann.de
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Dropping PostgreSQL Tables -- error noted
Hello all, I'm not sure if this is a bug or not, but I'm running Bacula 2.2.1 (granted I see that 2.2.3 just came out today so I'll download and install to see how it works), but after going through the Bacula Tutorial (and I'm using PostgreSQL 8.1.9), running drop_bacula_tables (after I had successful run a backup test and restore per chapter 9 of the tutorial), which calls drop_postgresql_tables, there results of dropping the tables yields and error regarding a table allegedly named mac (as can be seen from my output below. I'm not sure what the mac table's purpose is and if it should have been created in the first place (with the make tables scripts)? I took a look at the make_postgresql_tables and I didn't see a table named mac or MAC listed. Should then drop_postgresql_tables be updated to no longer attempt to drop the mac table? Thanks, -H DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE DROP TABLE psql:stdin:19: ERROR: table mac does not exist DROP TABLE DROP TABLE DROP TABLE Deletion of Bacula PostgreSQL tables succeeded. Dropped PostgreSQL tables - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] initgroups error (Bacula 2.2.1)
As a followup to this message, I retraced my notes with regard to the configuration options that I passed to ./configure and was reminded that I had explicitly set the user and groups to the appropriate non-root user and non-root group on my system: --with-dir-user=admini --with-dir-group=staff --with-sd-user=admini --with-sd-group=staff --with-fd-user=admini --with-fd-group=staff I believe this has solved the problem (e.g., I still need to start the bacula start script as the root user but then I noticed the PIDs were running correctly with the user admini). There has been other references in the documentation such that the file daemon really needs to run as the root user so I'm wondering if I will get myself into trouble having configured with the configure options for the file daemon also specifying the non-root-user and non-root group? Thank you. On 9/9/07, Hydro Meteor [EMAIL PROTECTED] wrote: Hi, I've installed Bacula 2.2.1 on an Apple Intel Xserve running Mac OS X Server 10.4.10 I am in the process of moving through the Tutorial (Chapter 9 in the User's Guide) -- I have not touched / edited / modify the default configuration files. This is a fresh install! I had hoped to be able to (per Chapter 9), run all of the Bacula daemons as a non-root user (on my system named admini). The non-root user (admini) has a different group (gid) than the root user, the group named staff. When running the bacula script which starts all of the daemons, I'm receiving the following error regarding initgroups. I'm trying to track this down: admini$ ./bacula start Starting the Bacula Storage daemon 09-Sep 19:44 xserve-sd: ERROR TERMINATION at bsys.c:698 Could not initgroups for group=staff, userid=admini: ERR=Operation not permitted Starting the Bacula File daemon 09-Sep 19:44 xserve-fd: ERROR TERMINATION at bsys.c:698 Could not initgroups for group=staff, userid=admini: ERR=Operation not permitted Starting the Bacula Director daemon 09-Sep 19:44 bacula-dir: ERROR TERMINATION at bsys.c:698 Could not initgroups for group=staff, userid=admini: ERR=Operation not permitted I'll continue to try and track this down to find out what I need to change on my systems such as privileges of Bacula configuration files and/or executable files and directories (so that a user with a primary group that is not the same as a root user's primary group) may run the daemons. Granted once I'm into production mode, the file daemon will indeed by run as the root user from what I've grokked of the Bacula documentation. In the mean time, if anyone has run into this problem before and has any suggestions, I'd be appreciative (I did a search on the mailing list archives for the past year on initgroups and virtually nothing showed up). Thank you, -H - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] initgroups error (Bacula 2.2.1)
On 9/9/07, Arno Lehmann [EMAIL PROTECTED] wrote: Hi, 09.09.2007 22:32,, Hydro Meteor wrote:: As a followup to this message, I retraced my notes with regard to the configuration options that I passed to ./configure and was reminded that I had explicitly set the user and groups to the appropriate non-root user and non-root group on my system: --with-dir-user=admini --with-dir-group=staff --with-sd-user=admini --with-sd-group=staff --with-fd-user=admini --with-fd-group=staff I believe this has solved the problem ( e.g., I still need to start the bacula start script as the root user but then I noticed the PIDs were running correctly with the user admini). That's as it should be. There has been other references in the documentation such that the file daemon really needs to run as the root user so I'm wondering if I will get myself into trouble having configured with the configure options for the file daemon also specifying the non-root-user and non-root group? Probably, yes. The FD needs permissions to access all the files you want to back up. As long as the file set you use is restricted to files accessible by admini:staff, that's ok. Once you try to store system configuration data or the OS files, or even regular user data, you'll probably find that the FD needs more permissions. Usually, that's when you decide to run it as root :-) Arno, Thanks for your reconfirmation. I ended up changing my mind and decided to re-install Bacula such that only root will run FD. I'm pleased to say that I my first attempt after re-installing worked out great (all three Bacula daemons are running fine and speaking to my PostgreSQL 8.1.9 database). I have to do some test running now but at least my daemons are running without any errors. Thanks again! -H Arno [snip] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Duplicate Address field values ok?
Hello,
In Chapter 6.3.4 of the Bacula User's Guide, with regard to naming
resources, the Guide states that:
Each of your Bacula components must have a unique name.
This is especially necessary when backing up a fleet machines.
I didn't see any similar requirements that the Address fields of resources
also be unique. Can anyone confirm this? For example, would the following
(in the bacula-dir.conf file) have any conflicts?
# Client (File Services) to backup
Client {
Name = myunique-machine-name-1
Address = 192.168.1.25
FDPort = 9102
Catalog = MyCatalog
Password = YxR21sehW8stTml8RUKYAfln3WSVPoyvJVJ276RqXRmY #
password for FileDaemon
File Retention = 30 days# 30 days
Job Retention = 6 months# six months
AutoPrune = yes # Prune expired Jobs/Files
}
and
# Client (File Services) to backup
Client {
Name = myunique-machine-name-2
Address = 192.168.1.25
FDPort = 9102
Catalog = MyCatalog
Password = YxR21sehW8stTml8RUKYAfln3WSVPoyvJVJ276RqXRmY #
password for FileDaemon
File Retention = 30 days# 30 days
Job Retention = 6 months# six months
AutoPrune = yes # Prune expired Jobs/Files
}
As much as it would be ideal to use a FQDN for the Address fields, there are
some scenarios where this isn't possible and there is a concern from my
colleague, about a collision in the Address fields. Hopefully as interpreted
from the User's Guid, the uniqueness of the Name fields is all that's
required (but better to check ahead of time to be safe than sorry later).
Than you.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula 2.2.1 made on a Mac Intel Xserve successful
Hello all, I just successfully went through a configure, make and make install process on an Intel Apple Xserve running Mac OS X Server 10.4.10 ... using PostgreSQL 8.1.9 as a back end for Bacula (I have yet to configure the database in the PostgreSQL cluster for Bacula but that's next). All of the binaries and configuration files that should have been made appear to have been made (as I understand this is dependent on the options given to configure). In the User's Guide (current version) Section 7.19titled Other Make Notes there is a list of file that should be, more or less, installed if successful after a make install. One of them is a file named merely: fd The file fd did not make on my system but I don't know what fd is or does. Thus, I can not know if fd missing from my make install is an error (should I expect it to be there?) or if it is correctly absent (such as based on my configuration). I take it that fd has to do with the file daemon but is there a deeper explanation of what this file is? I have confirmed the existence of these binary files but nothing else with fd in its name resultant from the Bacula make install: bacula-fd bacula-ctl-fd Thank you for any further clarifications to the User's Guide. Cheers. -H - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Simple high level question
Hi, I am about to install Bacula for the first time on an Apple Intel Xserve running Mac OS X Server 10.4.10. Something I had in mind was using a dedicated disc volume to run Bacula director and the other critical components such as File Server, Database Server and Storage Server. This dedicated disc volume would only purposefully be rebooted to based on a cron schedule which cron would be running of operating system booted from the main Xserve's internal disc volume that is normally used to boot and run the server. The reason I want to do this is that I want to backup multiple disc volumes that the Xserve uses (including its internal normally booted from disc) and to do so when the normally running applications and data are not being used operationally. Is there any reason why I could not do reboot to this dedicated disc volume which would then run all of the core Bacula daemons and to do its business of backing up and then once the backup processes have been completed, I could write a script which would then reboot the Xserve back to its normal operations state (using its internal disc drive)? Maybe this sound convoluted but I don't have another machine at the moment that can be used to run Bacula for command and control of the Xserve externally but on the same subnet. Thanks for any feedback. Cheers. - 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
[Bacula-users] 64-bit Bacula with 64-bit PostgreSQL on Intel Xserve / Mac OS X Server?
Hi, I noticed in the wonderfully documented Bacula User's Guide, that Bacula can be made to work in a 64-bit context: If you have over 4 billion file entries stored in your database, the database FileId is likely to overflow. This is a monster database, but still possible. Bacula's FileId fields have been modified so that they can be upgraded from 32 to 64 bits in version 1.39 or later, but you must manually do so. I plan on using PostgreSQL as the storage system for Bacula. Indeed 4 billion is of monster proportions but not necessarily for all applications (I work with physics packages that dump out copious number of files on the file system). I can corroborate that PostgreSQL (at least version 8.1) database clusters can suffer from transaction ID wraparound problems on every 4 billionth transaction if the databases in the cluster are never analyzed and vacuumed for example. I'm running Mac OS X Server 10.4.10 in Intel Xserves (Intel Woodcrest CPUs, quad core). I'm guessing its a pipe dream at this moment to think that I'll be able to build a true 64-bit version of PostgreSQL to eschew the 4 billion transaction issue and to also build Bacula as a 64-bit application if I want to stick with Mac OS X Server (if Apple is on schedule we have a full 64-bit UNIX / that is fully POSIX compliant in the form of Mac OS X Server 10.5Leopard due to arrive in the next 58 days). In the mean time do I need to wait for 64-bit UNIX from Apple to then build a 64-bit PostgreSQL and 64-bit Bacula, or has anyone figured a workaround until currently? Thank you for any feedback. - 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
[Bacula-users] Best practice for a newbie -- 1.39 or not?
Hello all, I've been catching up reading the mailing list for the past several days. I see some of the Bacula gurus have oft referred to Bacula 1.39 soon to become named 1.40 and it almost seems as if that 1.39 / 1.40 might be the best version to use for a newbie such as myself. However, with 1.38 at least there is the corresponding and awesome 1.38 manual that I have been and can continue to use (since I've until now built and installed 1.38 on Ubuntu, Mac OS X client and Mac OS X Server). However, I'm wondering if the recommendation at this point in time is to just go for it and use 1.39 on my systems so I can train myself to work with the latest and greatest? Of course on sourceforge 1.39 is still listed as Beta but I'm wondering how soon Beta is going to be removed from its description? Are we, for example, days or just a few weeks away (in which case 1.39 is not likely to change materially)? Thanks for any suggestions! - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula scripting with Ruby?
On 11/28/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: On Sat, Nov 25, 2006 at 09:43:25PM -1000, Hydro Meteor wrote: I am curious however if anyone has done any Bacula scripting with Ruby? Though I have nothing against Python, I have recently become enamored with Ruby (and of course Ruby seems to be getting a shot of interest these days thanks in part to the Ruby on Rails project). I've done a bit of work in that area, using both Ruby on Rails and Ruby by its self. I've used the Rails framework to develop Bacuview, a Bacula status monitor which provides a web-based view into the status of a Bacula backup system, with pages provided to display the status of the jobs, the clients, the media, and the pools in the system. For details, see: http://bacuview.rubyforge.org/ John, I am about to download and try out both BacuView based on Rails and BacuWatch. What a great idea (perfect for platforms that don't support GTK and therefore which don't allow for the GUI-based monitoring and control tools that Kern already put together for Bacula). Thanks for sharing this with the Bacula community! Cheers! Using ruby on its own, I've developed Bacuwatch, a program used to keep a watch on a group of Bacula jobs. Typically, it is run from a cron job, and is configured to send an email message with a single line status report on each backup job to the Bacula administrator and optionally to send a more detailed report on each job to the user of the machine which that job backs up. -- John Kodis. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula and Large File Support (LFS) on Mac OS X 10.4.8 Intel
On 11/27/06, Erich Prinz [EMAIL PROTECTED] wrote: Thanks Martin, that got it. So yes, running 1.36.x on OS X 10.4.x shows that large file support is enabled. Erich Thanks Erich (and all others) for beating me to the punch and solving this question. Its a good one to solve with certainty and to know that the next version of Bacula (its configure script) can look at the target platform its being built on, detect that its Darwin (OS X) and then essentially assume large file support from there on out. Cheers! On Nov 27, 2006, at 2:15 PM, Martin Simmons wrote: On Mon, 27 Nov 2006 07:50:48 -0600, Erich Prinz said: snip running a status in bconsole (even with -dnn) doesn't yield the output you suggest below. Likely a nuance with BSD. Older versions of Bacula only report the sizes for debug0, so try doing this first: setdebug client level=1 __Martin You can check if a particular client has large file support despite what the configure output says by doing a: status client=xxx in the console. If you get a line such as: Sizeof: off_t=8 size_t=4 debug=0 trace=0 in the output, you have large file support. If it says: Sizeof: off_t=4 size_t=4 debug=0 trace=0 you do not have large file support. On Ubuntu the value for Large File Support: was yes. Furthermore, when I tried to re-configure on Mac OS X (being sure to run configure a second time after a make distclean to clear any configure cache), I then explicitly added this configure option: --enable-largefile But the end result was the same: Large file support: no What should I do? I will most definitely need to back up and restore files that are in excess of 2 GB in size. In Bacula, is Large File Support limited to certain file systems or operating systems? The Mac I tried configuring for is one of the quite new Intel iMacs (with Intel Core 2 Dueo Merom chip inside and apparently Merom is a 64-bit chip and apparently Mac OS X 10.4.x Tiger has some 64-bit capability but I'm not clear on exactly where the lines are drawn between 32-bit and 64-bit in Tiger and on these new iMacs). Would CPU architecture in any way affect the outcome of Bacula? Might I be in new territory if I am understanding this [1] document about Large File System support correctly. Any further suggestions or comparisons (Erich?) from people who are running Bacula on Mac OS X (Apple Intel and PowerPC)? Cheers, -H [1] http://en.wikipedia.org/wiki/Large_file_support -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php? page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php? page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php? page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Illegal byte sequence (on Mac OS X when running configure, doing make of dependencies)
As an update to my push for getting Bacula into use on Mac OS X (in this case the Intel iMac with Core 2 Duo), I was looking through my output in more detail and trying to make some human sense parsing what I observed and comparing to Ubuntu Linux (the comparison I believe is good because, if I understand the history correctly, Kern created Bacula on Linux so naturally there is going to be more knowledge and experience around Linux distros running Bacula). I found this output from ./configure on the Mac's command line but which was missing from the command line output of configure (same version of Bacula and nearly identical configure options presented to configure on both Mac and Ubuntu): cut: stdin: Illegal byte sequence I am wondering if this Illegal byte sequence might come back to haunt me later on when running one of the Bacula daemons in a critical situation whether it be the Director, Storage, backing up, restoring, etc.? More specifically, the Illegal byte sequence alert was output four times sequentially on the command line (see larger excerpt below and comparative larger excerpt from Ubuntu). I didn't post this to the Bacula bugs mailing list because I don't really know if this is a bug or not. Best regards, configure on Mac OS X 10.4.8 - Intel Core 2 Duo and on Mac OS X Server 10.4.8 - PowerPC G4 is the same (with cut error repeated four times): Doing make of dependencies ==Entering directory /Users/hydro/Desktop/source/bacula- 1.38.11/src make[1]: Nothing to be done for `depend'. ==Entering directory /Users/hydro/Desktop/source/bacula-1.38.11/scripts make[1]: `depend' is up to date. ==Entering directory /Users/hydro/Desktop/source/bacula- 1.38.11/src/lib ==Entering directory /Users/hydro/Desktop/source/bacula-1.38.11/src/findlib ==Entering directory /Users/hydro/Desktop/source/bacula-1.38.11/src/filed ==Entering directory /Users/hydro/Desktop/source/bacula- 1.38.11 /src/console ==Entering directory /Users/hydro/Desktop/source/bacula-1.38.11 /src/tray-monitor ==Entering directory /Users/hydro/Desktop/source/bacula-1.38.11/src/cats ==Entering directory /Users/hydro/Desktop/source/bacula- 1.38.11/src/dird ==Entering directory /Users/hydro/Desktop/source/bacula-1.38.11/src/stored ==Entering directory /Users/hydro/Desktop/source/bacula-1.38.11/src/tools cut: stdin: Illegal byte sequence cut: stdin: Illegal byte sequence cut: stdin: Illegal byte sequence cut: stdin: Illegal byte sequence Output on Ubuntu (Dapper Drake 6.06) on Intel (i386) running Centrino on a laptop (no cut error): Doing make of dependencies ==Entering directory /home/hydro/Desktop/bacula-1.38.11/src make[1]: Entering directory `/home/hydro/Desktop/bacula-1.38.11/src' make[1]: Nothing to be done for `depend'. make[1]: Leaving directory `/home/hydro/Desktop/bacula- 1.38.11/src' ==Entering directory /home/hydro/Desktop/bacula-1.38.11/scripts make[1]: Entering directory `/home/hydro/Desktop/bacula-1.38.11/scripts' make[1]: `depend' is up to date. make[1]: Leaving directory `/home/hydro/Desktop/bacula- 1.38.11/scripts' ==Entering directory /home/hydro/Desktop/bacula-1.38.11/src/lib make[1]: Entering directory `/home/hydro/Desktop/bacula-1.38.11/src/lib' make[1]: Leaving directory `/home/hydro/Desktop/bacula- 1.38.11/src/lib' ==Entering directory /home/hydro/Desktop/bacula-1.38.11/src/findlib make[1]: Entering directory `/home/hydro/Desktop/bacula-1.38.11/src/findlib' make[1]: Leaving directory `/home/hydro/Desktop/bacula- 1.38.11/src/findlib' ==Entering directory /home/hydro/Desktop/bacula-1.38.11/src/filed make[1]: Entering directory `/home/hydro/Desktop/bacula-1.38.11/src/filed' make[1]: Leaving directory `/home/hydro/Desktop/bacula- 1.38.11/src/filed' ==Entering directory /home/hydro/Desktop/bacula-1.38.11/src/console make[1]: Entering directory `/home/hydro/Desktop/bacula-1.38.11/src/console' make[1]: Leaving directory `/home/hydro/Desktop/bacula- 1.38.11/src/console' ==Entering directory /home/hydro/Desktop/bacula-1.38.11/src/cats make[1]: Entering directory `/home/hydro/Desktop/bacula-1.38.11/src/cats' make[1]: Leaving directory `/home/hydro/Desktop/bacula- 1.38.11/src/cats' ==Entering directory /home/hydro/Desktop/bacula-1.38.11/src/dird make[1]: Entering directory `/home/hydro/Desktop/bacula-1.38.11/src/dird' make[1]: Leaving directory `/home/hydro/Desktop/bacula- 1.38.11/src/dird' ==Entering directory /home/hydro/Desktop/bacula-1.38.11/src/stored make[1]: Entering directory `/home/hydro/Desktop/bacula-1.38.11/src/stored' make[1]: Leaving directory `/home/hydro/Desktop/bacula- 1.38.11/src/stored' ==Entering directory /home/hydro/Desktop/bacula-1.38.11/src/tools make[1]: Entering directory `/home/hydro/Desktop/bacula-1.38.11/src/tools' make[1]: Leaving directory `/home/hydro/Desktop/bacula- 1.38.11/src/tools' - Take Surveys. Earn Cash. Influence the Future of
Re: [Bacula-users] Bacula and Large File Support (LFS) on Mac OS X 10.4.8 Intel
On 11/27/06, Erich Prinz [EMAIL PROTECTED] wrote: Running 10.4.8 on this end. What I can do is run a job with a large file and let you know the results. The configure options in the previous post don't included that option and per Kern's post on the subject, it appears it is on by default (which would make sense for Apple to do given the heavy use of video on the platform.) Erich, thank you for running a controlled test of a large file. I will do the same but am not quite there yet (am still reading through the manual and meticulously documenting my own installations -- both Ubuntu Linux and Mac OS X -- in parallel). It does make sense that large files are supported by Apple since OS X is notoriously used by media companies and Hollywood producers operating on large files easily over 2 GB in size. But, I think its good to test out in purely a Bacula context nonetheless (and ideally find out what can be done so that the next version of Bacula could, for example, detect the Mac OS X (Darwin) platform and output a yes for large file support. Cheers. Erich On Nov 27, 2006, at 12:11 AM, Hydro Meteor wrote: On 11/26/06, Erich Prinz [EMAIL PROTECTED] wrote: Can't help on this one. PPC only on this end. Hi Erich, A Bacula News Bulletin just in ... I just moments ago tried on Mac OS X Server 10.4.8 running on a PowerPC Mac, the exact same configure options on the same original source of Bacula ( 1.38.11) and thus explicitly requiring the large file system. The result output by configure was exactly the same (Large file system: no). Odd that it was explicit in the configure options but not found when running. Agreed. Maybe this is a bug in the configure script that manifests only on Mac OS X? Erich, what version of Mac OS X are you running on your PowerPC Mac (s)? I am wondering if you you have a moment if you could also try to run configure (in an isolated directory so as not to mess up your environment) and to see if you also do not receive the option to enable Large file support? If its not a major hassle to you? Have you attempted to run a backup on a single file over 2 GB just to see what would happen? Just curious. Not yet but I am surely going to try this -- will be one of the first things I do is not only try to backup a file over 2 GB but also restore. Will update the mailing list with the results when I find them. -H Erich On Nov 26, 2006, at 10:30 PM, Hydro Meteor wrote: As a followup I have copied and pasted what appears to be a relevant section of my config.log output on the same iMac which I tried to enable large file support for. If anyone who is more familiar with the inner workings of Bacula (Kern?) could shed some additional light on what would be a good next step to take (in order to make sure Bacula can operate on large files on Mac OS X), that would be greatly appreciated! configure:17157: checking for CFLAGS value to request large file support configure:17222: result: no configure:17224: checking for LDFLAGS value to request large file support configure:17234: result: no configure:17236: checking for LIBS value to request large file support configure:17246: result: no configure:17291: checking for _FILE_OFFSET_BITS configure:17308: result: 64 configure:17317: checking for _LARGEFILE_SOURCE configure:17334: result: 1 configure:17343: checking for _LARGE_FILES configure:17360: result: 1 On 11/26/06, Hydro Meteor [EMAIL PROTECTED] wrote: Hello, I was able to ./configure Bacula 1.38.11 on a Mac running Mac OS X 10.4.8 without any problems today (in a manner almost exactly the same as my Ubuntu Linux configuration). In both cases, I did not explicitly provide configure with the option of disabling large file support, and I also did not explicitly provide configure with he option of enabling large file system support (but according to the current manual, --enable-largefile is the default). Despite accepting the default (enabled), I noticed that my output was different after running configure. On the Mac, configure reported a value of no assigned as in: Large file support: no On Ubuntu the value for Large File Support: was yes. Furthermore, when I tried to re-configure on Mac OS X (being sure to run configure a second time after a make distclean to clear any configure cache), I then explicitly added this configure option: --enable-largefile But the end result was the same: Large file support: no What should I do? I will most definitely need to back up and restore files that are in excess of 2 GB in size. In Bacula, is Large File Support limited to certain file systems or operating systems? The Mac I tried configuring for is one of the quite new Intel iMacs (with Intel Core 2 Dueo Merom chip inside and apparently Merom is a 64-bit chip and apparently Mac OS X 10.4.x Tiger has some 64-bit capability but I'm not clear
[Bacula-users] Bacula and Large File Support (LFS) on Mac OS X 10.4.8 Intel
Hello, I was able to ./configure Bacula 1.38.11 on a Mac running Mac OS X 10.4.8without any problems today (in a manner almost exactly the same as my Ubuntu Linux configuration). In both cases, I did not explicitly provide configure with the option of disabling large file support, and I also did not explicitly provide configure with he option of enabling large file system support (but according to the current manual, --enable-largefile is the default). Despite accepting the default (enabled), I noticed that my output was different after running configure. On the Mac, configure reported a value of no assigned as in: Large file support: no On Ubuntu the value for Large File Support: was yes. Furthermore, when I tried to re-configure on Mac OS X (being sure to run configure a second time after a make distclean to clear any configure cache), I then explicitly added this configure option: --enable-largefile But the end result was the same: Large file support: no What should I do? I will most definitely need to back up and restore files that are in excess of 2 GB in size. In Bacula, is Large File Support limited to certain file systems or operating systems? The Mac I tried configuring for is one of the quite new Intel iMacs (with Intel Core 2 Dueo Merom chip inside and apparently Merom is a 64-bit chip and apparently Mac OS X 10.4.x Tiger has some 64-bit capability but I'm not clear on exactly where the lines are drawn between 32-bit and 64-bit in Tiger and on these new iMacs). Would CPU architecture in any way affect the outcome of Bacula? Might I be in new territory if I am understanding this [1] document about Large File System support correctly. Any further suggestions or comparisons (Erich?) from people who are running Bacula on Mac OS X (Apple Intel and PowerPC)? Cheers, -H [1] http://en.wikipedia.org/wiki/Large_file_support - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula and Large File Support (LFS) on Mac OS X 10.4.8 Intel
As a followup I have copied and pasted what appears to be a relevant section of my config.log output on the same iMac which I tried to enable large file support for. If anyone who is more familiar with the inner workings of Bacula (Kern?) could shed some additional light on what would be a good next step to take (in order to make sure Bacula can operate on large files on Mac OS X), that would be greatly appreciated! configure:17157: checking for CFLAGS value to request large file support configure:17222: result: no configure:17224: checking for LDFLAGS value to request large file support configure:17234: result: no configure:17236: checking for LIBS value to request large file support configure:17246: result: no configure:17291: checking for _FILE_OFFSET_BITS configure:17308: result: 64 configure:17317: checking for _LARGEFILE_SOURCE configure:17334: result: 1 configure:17343: checking for _LARGE_FILES configure:17360: result: 1 On 11/26/06, Hydro Meteor [EMAIL PROTECTED] wrote: Hello, I was able to ./configure Bacula 1.38.11 on a Mac running Mac OS X 10.4.8without any problems today (in a manner almost exactly the same as my Ubuntu Linux configuration). In both cases, I did not explicitly provide configure with the option of disabling large file support, and I also did not explicitly provide configure with he option of enabling large file system support (but according to the current manual, --enable-largefile is the default). Despite accepting the default (enabled), I noticed that my output was different after running configure. On the Mac, configure reported a value of no assigned as in: Large file support: no On Ubuntu the value for Large File Support: was yes. Furthermore, when I tried to re-configure on Mac OS X (being sure to run configure a second time after a make distclean to clear any configure cache), I then explicitly added this configure option: --enable-largefile But the end result was the same: Large file support: no What should I do? I will most definitely need to back up and restore files that are in excess of 2 GB in size. In Bacula, is Large File Support limited to certain file systems or operating systems? The Mac I tried configuring for is one of the quite new Intel iMacs (with Intel Core 2 Dueo Merom chip inside and apparently Merom is a 64-bit chip and apparently Mac OS X 10.4.x Tiger has some 64-bit capability but I'm not clear on exactly where the lines are drawn between 32-bit and 64-bit in Tiger and on these new iMacs). Would CPU architecture in any way affect the outcome of Bacula? Might I be in new territory if I am understanding this [1] document about Large File System support correctly. Any further suggestions or comparisons (Erich?) from people who are running Bacula on Mac OS X (Apple Intel and PowerPC)? Cheers, -H [1] http://en.wikipedia.org/wiki/Large_file_support - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula and Large File Support (LFS) on Mac OS X 10.4.8 Intel
On 11/26/06, Erich Prinz [EMAIL PROTECTED] wrote: Can't help on this one. PPC only on this end. Hi Erich, A Bacula News Bulletin just in ... I just moments ago tried on Mac OS X Server 10.4.8 running on a PowerPC Mac, the exact same configure options on the same original source of Bacula (1.38.11) and thus explicitly requiring the large file system. The result output by configure was exactly the same (Large file system: no). Odd that it was explicit in the configure options but not found when running. Agreed. Maybe this is a bug in the configure script that manifests only on Mac OS X? Erich, what version of Mac OS X are you running on your PowerPC Mac(s)? I am wondering if you you have a moment if you could also try to run configure (in an isolated directory so as not to mess up your environment) and to see if you also do not receive the option to enable Large file support? If its not a major hassle to you? Have you attempted to run a backup on a single file over 2 GB just to see what would happen? Just curious. Not yet but I am surely going to try this -- will be one of the first things I do is not only try to backup a file over 2 GB but also restore. Will update the mailing list with the results when I find them. -H Erich On Nov 26, 2006, at 10:30 PM, Hydro Meteor wrote: As a followup I have copied and pasted what appears to be a relevant section of my config.log output on the same iMac which I tried to enable large file support for. If anyone who is more familiar with the inner workings of Bacula (Kern?) could shed some additional light on what would be a good next step to take (in order to make sure Bacula can operate on large files on Mac OS X), that would be greatly appreciated! configure:17157: checking for CFLAGS value to request large file support configure:17222: result: no configure:17224: checking for LDFLAGS value to request large file support configure:17234: result: no configure:17236: checking for LIBS value to request large file support configure:17246: result: no configure:17291: checking for _FILE_OFFSET_BITS configure:17308: result: 64 configure:17317: checking for _LARGEFILE_SOURCE configure:17334: result: 1 configure:17343: checking for _LARGE_FILES configure:17360: result: 1 On 11/26/06, Hydro Meteor [EMAIL PROTECTED] wrote: Hello, I was able to ./configure Bacula 1.38.11 on a Mac running Mac OS X 10.4.8 without any problems today (in a manner almost exactly the same as my Ubuntu Linux configuration). In both cases, I did not explicitly provide configure with the option of disabling large file support, and I also did not explicitly provide configure with he option of enabling large file system support (but according to the current manual, --enable-largefile is the default). Despite accepting the default (enabled), I noticed that my output was different after running configure. On the Mac, configure reported a value of no assigned as in: Large file support: no On Ubuntu the value for Large File Support: was yes. Furthermore, when I tried to re-configure on Mac OS X (being sure to run configure a second time after a make distclean to clear any configure cache), I then explicitly added this configure option: --enable-largefile But the end result was the same: Large file support: no What should I do? I will most definitely need to back up and restore files that are in excess of 2 GB in size. In Bacula, is Large File Support limited to certain file systems or operating systems? The Mac I tried configuring for is one of the quite new Intel iMacs (with Intel Core 2 Dueo Merom chip inside and apparently Merom is a 64-bit chip and apparently Mac OS X 10.4.x Tiger has some 64-bit capability but I'm not clear on exactly where the lines are drawn between 32-bit and 64-bit in Tiger and on these new iMacs). Would CPU architecture in any way affect the outcome of Bacula? Might I be in new territory if I am understanding this [1] document about Large File System support correctly. Any further suggestions or comparisons (Erich?) from people who are running Bacula on Mac OS X (Apple Intel and PowerPC)? Cheers, -H [1] http://en.wikipedia.org/wiki/Large_file_support -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php? page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your
[Bacula-users] Backing up an entire disk partition?
Hopefully this doesn't come across as a question with an obvious answer, but I'm wondering if there is any reason why one can not or should not use Bacula to back up (and restore later if necessary such as if there is a physical disk failure) an entire disk partition of a platform (at the moment specifically I'm thinking of a machine or machines with Ubuntu Linux installed -- Dapper Drake or Edgy -- but later would want to extend to Mac OS X and FreeBSD if feasible)? The reason I ask is that I've noticed that Bacula hasn't gotten too much attention it seems on the Ubuntu wiki with regard to backup and recovery solutions and I have seen several on various mailing lists suggest using a lower level disk imaging technology for backing up entire partitions such as parted and partedimage of which there are also graphical front ends (such as QParted). Has anyone had experiences backing up entire partitions of any platform (be it Linux (Ubuntu or not), Mac OS X, FreeBSD, et al)? Cheers. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Backing up an entire disk partition?
Oops, looks like I was able to answer my own question for the most part as I had missed parts in the current manual describing configuring to back up a raw partition (sparse = yes). Even so, it would be interesting to hear from anyone who has some experiences and scar tissue from doing so in a production environment. Even more specifically, besides flavors of Linux, it would be interesting to hear of anyone who has any direct experiences with HFSX (the version of the HFS+ Apple file system that is case sensitive). I can't imagine case sensitivity being a problem since Apple's HFS+ deviates from most of the world's modern day file systems which are typically case sensitive. -H On 11/25/06, Hydro Meteor [EMAIL PROTECTED] wrote: Hopefully this doesn't come across as a question with an obvious answer, but I'm wondering if there is any reason why one can not or should not use Bacula to back up (and restore later if necessary such as if there is a physical disk failure) an entire disk partition of a platform (at the moment specifically I'm thinking of a machine or machines with Ubuntu Linux installed -- Dapper Drake or Edgy -- but later would want to extend to Mac OS X and FreeBSD if feasible)? The reason I ask is that I've noticed that Bacula hasn't gotten too much attention it seems on the Ubuntu wiki with regard to backup and recovery solutions and I have seen several on various mailing lists suggest using a lower level disk imaging technology for backing up entire partitions such as parted and partedimage of which there are also graphical front ends (such as QParted). Has anyone had experiences backing up entire partitions of any platform (be it Linux (Ubuntu or not), Mac OS X, FreeBSD, et al)? Cheers. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula scripting with Ruby?
Hello all ... I have successfully configured and made / installed the current version of Bacula on Ubuntu Dapper Drake with Postgresql 8.1.3 (a nice first step for a newbie), and I included in configure the python option (since python does make for a nice scripting language). I am curious however if anyone has done any Bacula scripting with Ruby? Though I have nothing against Python, I have recently become enamored with Ruby (and of course Ruby seems to be getting a shot of interest these days thanks in part to the Ruby on Rails project). I'll probably end up doing some Bacula scripting with Ruby and will share what I learn in the process. Would be fun to connect with any other Bacula / Ruby enthusiasts out there in the ether. Cheers. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Mac OS X and readline disabled requirement (deprecated information in the documentation?)
Hello,
According to the documentation for Bacula 1.38.11 (24 July 2006), on page 61
of the PDF document, it says this about Mac OS X client:
MacOS X 10.3 is reported to work with the Client only as long as readline
support is disabled.
This may be true for 10.3, but I'm not so sure its true for 10.4 (and
Leopard -- 10.5 is just around the corner). The reason I mention this is
that the MacPorts (formerly Darwin Ports) Bacula Portfile has configuration
arguments as follows (copied and pasted) and there is no explicit disabling
of the readline option (although its also not explicitly enabled either):
configure.args --mandir=${prefix}/share/man
--with-pid-dir=${prefix}/var/run \
--with-subsys-dir=${prefix}/var/run/subsys
\
--sysconfdir=${prefix}/etc/${name} \
--with-libintl-prefix=${prefix}
--with-openssl=${prefix} \
--with-libiconv-prefix=${prefix}
--with-sqlite3=${prefix} \
--without-postgresql --without-mysql \
--disable-gnome --disable-wx-console
--disable-tray-monitor
Any ideas what the reality is for Mac OS X 10.4? Maybe a documenation update
is in order?
Cheers.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula 1.38.11 ok for Mac OS X Server 10.4.x?
With apologies if this is a redundant question but I was unsuccessful when searching the Bacula mailing list archives on gname in finding any relevant information to my question. I am wondering if there is any reason why the current release of Bacula ( 1.38.11) can not work (or does not work) on Mac OS X Server (specifically Mac OS X Server 10.4.x)? In the Bacula 1.38.11 documentation, in the Quick Start section, the supported operating systems state Mac OS X (client) which would indicate logically not server (since Mac OS X Server is not mentioned). It would be great to be able to back up data on storage devices attached to and managed by some Xserves that I have to admin. Thanks much, Hydro - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula 1.38.11 ok for Mac OS X Server 10.4.x?
Erich, Thank you for your reply. Great to know it works fine on Mac OS X Server. It would be good to introduce this information into the next version of the Bacula Documentation. I won't be using MySQL but instead will be using Postgres, but thanks much for your suggestion in the event someone on Mac OS X Server desires to use MySQL. Best regards, -Hydro On 11/23/06, Erich Prinz [EMAIL PROTECTED] wrote: It does work on X Server. There are at least three people on this list with X Server (in the multiples of servers by the way) that use Bacula. I'm not one of them :-) Make sure you build out your configure script to point to the appropriate location of MySQL (which is really the only difference between the X client and X Server as far as Bacula is concerned.) Erich On Nov 23, 2006, at 10:21 AM, Hydro Meteor wrote: With apologies if this is a redundant question but I was unsuccessful when searching the Bacula mailing list archives on gname in finding any relevant information to my question. I am wondering if there is any reason why the current release of Bacula ( 1.38.11) can not work (or does not work) on Mac OS X Server (specifically Mac OS X Server 10.4.x)? In the Bacula 1.38.11 documentation, in the Quick Start section, the supported operating systems state Mac OS X (client) which would indicate logically not server (since Mac OS X Server is not mentioned). It would be great to be able to back up data on storage devices attached to and managed by some Xserves that I have to admin. Thanks much, Hydro -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php? page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
