[Bacula-users] Bacula for OSX 10.9
I'm interested in perhaps deploying this in my k-8 school, but I have not found a good tutorial of how to install it. Or if it even works right on Mac. Anyone have some insights on this? My idea would be to back about 30 macs to an Ubuntu server. Thanks! Sent from my iSomething -- -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Restore from dead client
Dan,
Appreciate the reply Yes this is exactly what I want to do.
However when I try to just do a "simple" restore, the job finishes
with the error previously given.
Any suggestions to do this would be appreciated.
Thanks--Kenny
On Sat, Sep 6, 2014 at 5:51 PM, Dan Langille wrote:
>
> On Sep 5, 2014, at 5:48 PM, Kenny Noe wrote:
>
> Birre,
>
> Thanks for the reply. I guess this is where I get lost...
>
>
>
> The fifo is reading a file that was created in the pre-process called
> mail.tar. The mail.tar is made from the following directories /opt/zimbra
> and /var/mail/zimbra. This is where the Zimbra files and mailstore were
> kept.
>
> This pre-process is a script that has this :
>
> MailBackup.bash
> #!/bin/bash
>
> exec >/dev/null
>
> MKDIR="/bin/mkdir"
> MKFIFO="/usr/bin/mkfifo"
> RM="/bin/rm"
> TAR="/bin/tar"
>
> DEFCODE=0
> DUMPBASE="/data/backups"
>
> errCode=${DEFCODE}
> mailDir="/var/mail/zimbra"
> zimbraDir="/opt/zimbra"
>
> Main()
>{
>service zimbra stop
>
>RunMailRestore
>
>service zimbra start
>
>ExitScript ${errCode}
>}
>
> RunMailRestore()
>{
>EXTENSION=".tar"
>
>dumpDir="${DUMPBASE}/mail"
>fifoDir="${dumpDir}/fifo"
>
>RebuildFifoDir
>
>${MKFIFO} ${fifoDir}/mail${EXTENSION}
>
>${TAR} -xpf ${fifoDir}/mail${EXTENSION} 2>&1 }
>
> RebuildFifoDir()
>{
>if [ -d ${fifoDir} ]
>then
> ${RM} -rf ${fifoDir}
>fi
>
>${MKDIR} -p ${fifoDir}
>}
>
> ExitScript()
>{
>exit ${1}
>}
>
> Main
>
> The restore script simply does a tar xpf instead of a tar cpf.
>
>
> Perhaps instead of doing that, just restore the data, and then do the tar
> xpf later.
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-dir stuck trying to mount the wrong volume
On 9/6/2014 2:59 PM, Kern Sibbald wrote: ... > perhaps I am overly sensitive I've been dealing with other people's software for a living for close to two decades now and familiarity brings contempt. So yeah, I don't like software -- with very few exceptions, and bacula isn't one of them, I am jaded and sarcastic, and I don't like your position in the bareos debacle. So you're to some (large) extent correct on all counts. Keep telling us about wonderful features of your product that you won't document because I looked at you funny, see how many fans that wins you. Dimitri -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Restore from dead client
On Sep 5, 2014, at 5:48 PM, Kenny Noe wrote:
> Birre,
>
> Thanks for the reply. I guess this is where I get lost...
>
>
>
> The fifo is reading a file that was created in the pre-process called
> mail.tar. The mail.tar is made from the following directories /opt/zimbra
> and /var/mail/zimbra. This is where the Zimbra files and mailstore were kept.
>
> This pre-process is a script that has this :
>
> MailBackup.bash
> #!/bin/bash
>
> exec >/dev/null
>
> MKDIR="/bin/mkdir"
> MKFIFO="/usr/bin/mkfifo"
> RM="/bin/rm"
> TAR="/bin/tar"
>
> DEFCODE=0
> DUMPBASE="/data/backups"
>
> errCode=${DEFCODE}
> mailDir="/var/mail/zimbra"
> zimbraDir="/opt/zimbra"
>
> Main()
>{
>service zimbra stop
>
>RunMailRestore
>
>service zimbra start
>
>ExitScript ${errCode}
>}
>
> RunMailRestore()
>{
>EXTENSION=".tar"
>
>dumpDir="${DUMPBASE}/mail"
>fifoDir="${dumpDir}/fifo"
>
>RebuildFifoDir
>
>${MKFIFO} ${fifoDir}/mail${EXTENSION}
>
>${TAR} -xpf ${fifoDir}/mail${EXTENSION} 2>&1 }
>
> RebuildFifoDir()
>{
>if [ -d ${fifoDir} ]
>then
> ${RM} -rf ${fifoDir}
>fi
>
>${MKDIR} -p ${fifoDir}
>}
>
> ExitScript()
>{
>exit ${1}
>}
>
> Main
>
> The restore script simply does a tar xpf instead of a tar cpf.
Perhaps instead of doing that, just restore the data, and then do the tar xpf
later.
signature.asc
Description: Message signed with OpenPGP using GPGMail
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Restore from dead client
On Sep 5, 2014, at 11:56 AM, Kenny Noe wrote: > Just to update my plea for help. > > My Bacula server is hosted on a Ubuntu 11.10 server > Bacula Version is 5.2.2 > Problem - Unable to perform a restore of a backup to a different > client / location > > The error given is : > > 05-Sep 09:48 BS01-DIR1 JobId 12852: Start Restore Job > Restore_mail_bluewhale.2014-09-05_09.48.35_24 > 05-Sep 09:48 BS01-DIR1 JobId 12852: Using Device "File_bluewhale" > 05-Sep 09:48 BS01-FD1 JobId 12852: shell command: run > ClientRunBeforeJob "/nas/users/admin/scripts/MailRestore.bash" > 05-Sep 09:48 BS01-FD1 JobId 12852: ClientRunBeforeJob: zimbra: > unrecognized service > 05-Sep 09:48 BS01-FD1 JobId 12852: ClientRunBeforeJob: zimbra: > unrecognized service This error might be relevant. > 05-Sep 09:48 BS01-SD1 JobId 12852: Ready to read from volume > "mail-0386" on device "File_bluewhale" (/nas/bacula/bluewhale). > 05-Sep 09:48 BS01-SD1 JobId 12852: Forward spacing Volume "mail-0386" > to file:block 0:219. > 05-Sep 10:11 BS01-SD1 JobId 12852: End of Volume at file 28 on device > "File_bluewhale" (/nas/bacula/bluewhale), Volume "mail-0386" > 05-Sep 10:11 BS01-SD1 JobId 12852: End of all volumes. > 05-Sep 09:49 BS01-FD1 JobId 12852: Error: create_file.c:292 Could not > open /nas/users/admin/backups/data/backups/mail/fifo/mail.tar: > ERR=Interrupted system call > 05-Sep 10:11 BS01-FD1 JobId 12852: shell command: run ClientAfterJob > "/nas/users/admin/scripts/MailCleanup.bash" > 05-Sep 10:11 BS01-FD1 JobId 12852: ClientAfterJob: zimbra: unrecognized > service It repeats here. > 05-Sep 10:11 BS01-DIR1 JobId 12852: Bacula BS01-DIR1 5.2.2 (26Nov11): > Build OS: x86_64-unknown-linux-gnu ubuntu 11.10 > JobId: 12852 > Job:Restore_mail_bluewhale.2014-09-05_09.48.35_24 > Restore Client: besc-bs01 > Start time: 05-Sep-2014 09:48:37 > End time: 05-Sep-2014 10:11:05 > Files Expected: 1 > Files Restored: 0 > Bytes Restored: 0 > Rate: 0.0 KB/s > FD Errors: 1 > FD termination status: OK > SD termination status: OK > Termination:Restore OK -- warning file count mismatch > > > I get a zero size mail.tar file in the destination location, so I know > the changes in location works. Should I post mf conf files?? Please > advise... > > Thanks--kenny > > On Fri, Sep 5, 2014 at 10:48 AM, Kenny Noe wrote: >> Hi again Apologies for the late reply... I'm juggling several >> offices and am back to this now. >> >> Martin - Thanks for the reply. I have investigated the pre-process >> script and it does the following : Stop the Zimbra Mail service and >> runs the tar cmd to create the mail.tar file. Then Bacula uses fifo >> to backup the tar file into a volume in the SD Catalog. I've tried to >> restore to the local server and still get the same error. >> >> Any one have thoughts?? I REALLY need to get this file restored... >> >> Appreciate all the help. >> >> Sincerely, >> >> --Kenny >> >> On Thu, Aug 14, 2014 at 11:42 AM, Martin Simmons >> wrote: >>> The error is >>> >>> 12-Aug 09:51 BS01-FD1 JobId 12560: Error: create_file.c:292 Could not open >>> /nas/bacula/data/backups/mail/fifo/mail.tar: ERR=Interrupted system call >>> >>> which is strange. >>> >>> Is /nas/bacula/data/backups/mail/fifo/mail.tar a normal file or are you >>> trying >>> to restore into a FIFO? You could try restoring into a file on the local >>> disk. >>> >>> __Martin >>> >>> On Tue, 12 Aug 2014 10:25:12 -0400, Kenny Noe said: Phil, Thanks for the reply. So now the job runs and reports successful but all I get is a empty file. Here is the output from the log file : 12-Aug 09:50 BS01-DIR1 JobId 12560: Start Restore Job Restore_mail_bluewhale.2014-08-12_09.50.07_59 12-Aug 09:50 BS01-DIR1 JobId 12560: Using Device "File_bluewhale" 12-Aug 09:50 BS01-FD1 JobId 12560: shell command: run ClientRunBeforeJob "/nas/users/admin/scripts/MailRestore.bash" 12-Aug 09:50 BS01-FD1 JobId 12560: ClientRunBeforeJob: zimbra: unrecognized service 12-Aug 09:50 BS01-FD1 JobId 12560: ClientRunBeforeJob: zimbra: unrecognized service 12-Aug 09:50 BS01-SD1 JobId 12560: Ready to read from volume "mail-0386" on device "File_bluewhale" (/nas/bacula/bluewhale). 12-Aug 09:50 BS01-SD1 JobId 12560: Forward spacing Volume "mail-0386" to file:block 0:219. 12-Aug 10:12 BS01-SD1 JobId 12560: End of Volume at file 28 on device "File_bluewhale" (/nas/bacula/bluewhale), Volume "mail-0386" 12-Aug 10:12 BS01-SD1 JobId 12560: End of all volumes. 12-Aug 09:51 BS01-FD1 JobId 12560: Error: create_file.c:292 Could not open /nas/bacula/data/backups/mail/fifo/mail.tar: ERR=Interrupted system call 12-Aug 10:12 BS01-FD1 JobId 12560: shell command: run ClientAfterJob "/nas/users/admin/sc
Re: [Bacula-users] bacula-dir stuck trying to mount the wrong volume
Hello, Yes, I likely chimed in with the statement you said, and it seems like most everything you say is correct -- I cannot find the documentation on these features. I now remember why I didn't answer you the last time and why I probably won't this time either. It is because when I read what you write to me, perhaps I am overly sensitive, but I get the feeling that you don't like Bacula, you don't like me, and you are being sarcastic. I hope I am completely wrong on all those points, but that is how I take it, so the best response is just silence. Kern On 09/06/2014 06:43 PM, Dmitri Maziuk wrote: > On 9/6/2014 3:10 AM, Kern Sibbald wrote: > >> Can you tell me what my explanation of the disk autochanger was and why >> it did not make sense to you? > > The goal was to write file volumes -- same pool, same backup set, to a > set of filesystems (hosted on removable disks). The thread went on a > for a couple of weeks and the conclusion was vchanger is the only way > to do it. > > As I recall somewhere in the middle you chimed in with "there's > virtual autochanger and it works" or something along those lines. > Pretty much what you wrote again in the message I'm replying to. I > haven't seen any documentation on how it works or what it does, so a) > I believe you and b) it's of no use to me. > > Similarly, you've documented how to use symlinks for this? Great! > Where? "Basic Volume Management - Backing Up to Multiple Disks" from > 7.0 looks the same as it ever was. Is that in the enterprise manual only? > > Dimitri > -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-dir stuck trying to mount the wrong volume
On 9/6/2014 3:10 AM, Kern Sibbald wrote: > Can you tell me what my explanation of the disk autochanger was and why > it did not make sense to you? The goal was to write file volumes -- same pool, same backup set, to a set of filesystems (hosted on removable disks). The thread went on a for a couple of weeks and the conclusion was vchanger is the only way to do it. As I recall somewhere in the middle you chimed in with "there's virtual autochanger and it works" or something along those lines. Pretty much what you wrote again in the message I'm replying to. I haven't seen any documentation on how it works or what it does, so a) I believe you and b) it's of no use to me. Similarly, you've documented how to use symlinks for this? Great! Where? "Basic Volume Management - Backing Up to Multiple Disks" from 7.0 looks the same as it ever was. Is that in the enterprise manual only? Dimitri -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Socket error after upgrade to 7.x
On 09/06/14 12:45, Kern Sibbald wrote: > Hello, Hello. > It seems to me that was because your system does not support IPv6, for > which Bacula was checking. That might absolutely be the case. Any way to disable IPv6 check in Bacula? > You didn't mention the exact 7.0.x version, > but it seems to me that this was quickly fixed. In FreeBSD's port tree we've got 7.0.4 available and that's what I'm using. bye & Thanks av. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Socket error after upgrade to 7.x
Hello, It seems to me that was because your system does not support IPv6, for which Bacula was checking. You didn't mention the exact 7.0.x version, but it seems to me that this was quickly fixed. Best regards, Kern On 09/06/2014 12:21 PM, Andrea Venturoli wrote: > Hello. > > I've got several Bacula setup on FreeBSD 8.4. > > After the upgrade to 7.x all jobs results switched from "Ok" to "Ok with > warning". > > I believe it's due to the following error: >> Error: bsock.c:226 Socket open error. proto=28 port=9103. ERR=Protocol not >> supported > However I don't have a clue where it comes from. > Any hint? > > bye & Thanks > av. > > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Socket error after upgrade to 7.x
Hello. I've got several Bacula setup on FreeBSD 8.4. After the upgrade to 7.x all jobs results switched from "Ok" to "Ok with warning". I believe it's due to the following error: > Error: bsock.c:226 Socket open error. proto=28 port=9103. ERR=Protocol not > supported However I don't have a clue where it comes from. Any hint? -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Socket error after upgrade to 7.x
Hello. I've got several Bacula setup on FreeBSD 8.4. After the upgrade to 7.x all jobs results switched from "Ok" to "Ok with warning". I believe it's due to the following error: > Error: bsock.c:226 Socket open error. proto=28 port=9103. ERR=Protocol not > supported However I don't have a clue where it comes from. Any hint? bye & Thanks av. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bacula-dir stuck trying to mount the wrong volume
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/05/2014 09:16 PM, Dimitri Maziuk wrote: > On 09/05/2014 01:41 PM, Josh Fisher wrote: >> >> On 9/5/2014 1:48 PM, Dimitri Maziuk wrote: >>> I've another bacula setup that writes to a single filesystem. It's been >>> running with about zero problems (knock on wood) and zero maintenance >>> for years: auto-labelling works, volume recycling works, the only >>> problems are spinning rust and lsi's ugly raid manglement software. >> >> The whole point of vchanger is to use multiple filesystems as a single >> autochanger. For a single filesystem I would recommend Bacula's >> built-in disk autochanger capability or else Bacula's standard disk >> storage handling. > > Right, that's my point: when you use bacula's standard disk storage > handling you get > - automatic volume labeling, > - automatic volume recycling, > and generally near zero maintenance overhead. > > With vchanger I > - have a job split over different disks, > - need to manually fix the catalog every time I sneeze, > - get into weird "intervention needed" loops where bacula "mounts" a > volume it's just filled up and complains it couldn't write to some other > volume it shouldn't have tried in the first place. > > Ergo, if you want to use multiple filesystems, the smart move would be > to "fake" the standard disk storage over multiple filesystems. > > (As for built-in disk autochanger, Kern's explanation of it never made > much sense to me: maybe it's useful for debugging or something...) Can you tell me what my explanation of the disk autochanger was and why it did not make sense to you? By the way the built-in disk autochanger is typically called the "virtual autochanger". Providing you use pools and media types correctly the virtual autochanger can actually handle multiple filesystems. Even without, I have documented in the manual how to use multiple filesystems with symlinks (a slight bit more annoying to setup). I ran very small data center in that configuration for about 10 years. The only maintenance was to update Bacula and add additional disk drives when the user's data volume increased. A very large number of our enterprise clients are using the virtual autochanger with a lot of success. As you say, once you install it, it just runs. I have absolutely nothing against vchanger, because a lot of people are very happy with it. However, it is not a Bacula product, and it seems that it works like a tape autochanger which requires much more maintenance than the virtual autochanger, which is just a simple extension of individual disk Devices. Best regards, Kern -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlQKwWcACgkQNgfoSvWqwEi5vQCff51zbNhqAX/FHugOSq9W7HXz /bAAoOwykZVB4I0c+66tiOebi8cLv8ms =VJKk -END PGP SIGNATURE- -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error: block.c:255 Write errors?
Hello, I was about to write to you based on your first email containing only the error that tape errors should be extremely rare and even non-existent. The exception is when tapes fill, the information that Bacula gets depends on the tape drive. In from what I see below, as already commented by others, this seems to be a somewhat normal "end of tape" condition, where Bacula receives a return indicating that the block was not written. Unfortunately, the error it gets is generally not distinguishable from an end of tape condition. In that case it then writes an end of file mark and attempts to re-read the last good block. If it succeeds as it did in your case, there is probably a 99.999% chance that the tape is perfectly valid. The only other thing to check is to see if the amount of data that was written on the volume corresponds roughly to what you expect -- generally there is a 2/1 compression done by the tape drive, but that is rather general it can vary from 1/1 (already compressed data) to 3/1 for pure text. Best regards, Kern On 09/05/2014 10:12 PM, Stephen Thompson wrote: > Huh, maybe this is a misdiagnosis of the end of tape and a write error > only in the sense that there is no tape left. > > 05-Sep 00:41 SD_L100_ JobId 389348: Error: block.c:255 Write error at > 610:412 on device "L100-Drive-0" (/dev/L100-Drive-0). ERR=Input/output > error. > 05-Sep 00:41 SD_L100_ JobId 389348: Re-read of last block succeeded. > 05-Sep 00:41 SD_L100_ JobId 389348: End of medium on Volume "IM0161" > Bytes=1,090,307,051,520 Blocks=520,103 at 05-Sep-2014 00:41. > > > On 09/05/2014 09:42 AM, Stephen Thompson wrote: >> Hello, >> >> I sporadically get these types of alerts for one on my bacula tape >> libraries... >> >> 05-Sep 00:41 lawson-sd_L100_ JobId 389348: Error: block.c:255 Write >> error at 610:412 on device "L100-Drive-0" (/dev/L100-Drive-0). >> ERR=Input/output error. >> >> Am I correct in assuming that this was indeed a tape write error, but >> that bacula will attempt a 2nd write of the same block of data and if >> that 2nd attempt succeeds proceed on and ultimately have a successfully >> run job (one that can be restored without issue)? >> >> In other words, should this error worry me if it doesn't happen often? >> It does consistently happen -- with 100's of jobs a night, it probably >> happens 3-4 times a week. >> >> thanks, >> Stephen >> >> >> -- >> Slashdot TV. >> Video for Nerds. Stuff that matters. >> http://tv.slashdot.org/ >> ___ >> Bacula-users mailing list >> Bacula-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bacula-users >> > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
