[Bacula-users] Tray monitor
Hi, I have configured bacula and everything working as expected, but on my windows xp client the tray monitor does not showing the green light wen bacup is executing ( but I can see in the tray monitor status the running bacup process) I have bacula 5.2.6 Thanks in advance Kovacs Alpar -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] DELL TL2000
Hi all, I have a bacula server configured to use one pool for every client host and for every backup level. In this way, a single client has 3 pool: Full, Incr, Diff What i would like to do is to copy the latest full pool for each client to a tape library. I've tried to configurare a Copy job with no success. Do you have some docs or example that will allow me to copy more then one pool to a tape library at once? Thank you. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] ML6000 does not work al of a sudden
Hi all, please help me track the cause of the problem. Short story is that we used successfully Bacula for years until that day when this error appeared in the messages: - Server OpenIndiana 147 - Bacula 5.0.3 - Tape Library Dell ML6000 connected by FC 27-Feb 19:54 de001bs002-sd JobId 732: Fatal error: Error writing data to spool file. ERR=Disc quota exceeded 27-Feb 19:54 de001bs002-sd JobId 732: Writing spooled data to Volume. Despooling 835,324,011,949 bytes ... 27-Feb 19:54 de001bs002-sd JobId 732: Despooling elapsed time = 00:00:01, Transfer rate = 835.3 G Bytes/second 27-Feb 19:55 de001bs002-sd JobId 732: Fatal error: Fatal despooling error. 27-Feb 19:55 de001bs002-fd JobId 732: Error: bsock.c:393 Write error sending 65536 bytes to Storage daemon:de001bs002:9103: ERR=Broken pipe 27-Feb 19:55 de001bs002-fd JobId 732: Fatal error: backup.c:1024 Network send error to SD. ERR=Broken pipe 27-Feb 19:55 de001bs002-dir JobId 732: Error: Bacula de001bs002-dir 5.0.3 (04Aug10): 27-Feb-2012 19:55:21 Build OS: i386-pc-solaris2.11 solaris 5.11 JobId: 732 Job:BACKUP_A.2012-02-27_17.09.00_03 Backup Level: Full Client: de001bs002-fd 5.0.3 (04Aug10) i386-pc-solaris2.11,solaris,5.11 FileSet:BACKUP_A 2011-11-16 12:28:39 Pool: BACKUP_A (From Job resource) Catalog:MyCatalog (From Client resource) Storage:LTO4-01 (From Job resource) Scheduled time: 27-Feb-2012 17:08:56 Start time: 27-Feb-2012 17:09:02 End time: 27-Feb-2012 19:55:21 Elapsed time: 2 hours 46 mins 19 secs Priority: 10 FD Files Written: 210,602 SD Files Written: 210,602 FD Bytes Written: 834,493,153,036 (834.4 GB) SD Bytes Written: 834,546,185,158 (834.5 GB) Rate: 83624.9 KB/s Software Compression: None VSS:no Encryption: no Accurate: no Volume name(s): 000329 Volume Session Id: 1 Volume Session Time:1330355979 Last Volume Bytes: 64,512 (64.51 KB) Non-fatal FD errors:1 SD Errors: 1 FD termination status: Error SD termination status: Error Termination:*** Backup Error *** Then At another try: Connecting to Director de001bs002:9101 1000 OK: de001bs002-dir Version: 5.0.3 (04 August 2010) Enter a period to cancel a command. *messages 28-Mar 20:26 de001bs002-sd JobId 736: 3304 Issuing autochanger load slot 72, drive 0 command. 28-Mar 20:26 de001bs002-sd JobId 736: 3305 Autochanger load slot 72, drive 0, status is OK. 28-Mar 20:26 de001bs002-sd JobId 736: Volume 000329 previously written, moving to end of data. 28-Mar 20:27 de001bs002-sd JobId 736: Error: Unable to position to end of data on device LTO4-01 (/dev/rmt/0bn): ERR=dev.c:956 ioctl MTEOM error on LTO4-01 (/dev/rmt/0bn). ERR=I/O error. 28-Mar 20:27 de001bs002-sd JobId 736: Marking Volume 000329 in Error in Catalog. 28-Mar 20:27 de001bs002-sd JobId 736: 3307 Issuing autochanger unload slot 72, drive 0 command. 28-Mar 20:28 de001bs002-dir JobId 736: There are no more Jobs associated with Volume 000257. Marking it purged. 28-Mar 20:28 de001bs002-dir JobId 736: All records pruned from Volume 000257; marking it Purged 28-Mar 20:28 de001bs002-dir JobId 736: Recycled volume 000257 28-Mar 20:28 de001bs002-sd JobId 736: 3301 Issuing autochanger loaded? drive 0 command. 28-Mar 20:28 de001bs002-sd JobId 736: 3302 Autochanger loaded? drive 0, result: nothing loaded. 28-Mar 20:28 de001bs002-sd JobId 736: 3304 Issuing autochanger load slot 49, drive 0 command. 28-Mar 20:29 de001bs002-sd JobId 736: 3305 Autochanger load slot 49, drive 0, status is OK. 28-Mar 20:29 de001bs002-sd JobId 736: Recycled volume 000257 on device LTO4-01 (/dev/rmt/0bn), all previous data lost. 28-Mar 20:29 de001bs002-sd JobId 736: Spooling data ... 29-Mar 00:08 de001bs002-sd JobId 736: Fatal error: Error writing data to spool file. ERR=Disc quota exceeded 29-Mar 00:08 de001bs002-sd JobId 736: Writing spooled data to Volume. Despooling 835,324,140,997 bytes ... 29-Mar 00:08 de001bs002-sd JobId 736: Despooling elapsed time = 00:00:01, Transfer rate = 835.3 G Bytes/second 29-Mar 00:09 de001bs002-sd JobId 736: Fatal error: Fatal despooling error. 29-Mar 00:09 de001bs002-fd JobId 736: Error: bsock.c:393 Write error sending 65536 bytes to Storage daemon:de001bs002:9103: ERR=Broken pipe 29-Mar 00:09 de001bs002-fd JobId 736: Fatal error: backup.c:1024 Network send error to SD. ERR=Broken pipe 29-Mar 00:10 de001bs002-dir JobId 736: Error: Bacula de001bs002-dir 5.0.3 (04Aug10): 29-Mar-2012 00:10:02 Build OS: i386-pc-solaris2.11 solaris 5.11 JobId: 736 Job:BACKUP_A.2012-03-28_20.24.51_17 Backup Level: Full Client: de001bs002-fd
Re: [Bacula-users] virtual backup
On Thu, May 03, 2012 at 09:15:26AM +0400, Anton Gorlov wrote: In other words, you use the Full and exactly one Diff to get a VirtualFull of the very time of the Diff. how to specify what one diff to apply? It uses the latest diff and the latest full available. Regards, Adrian -- LiHAS - Adrian Reyer - Hessenwiesenstraße 10 - D-70565 Stuttgart Fon: +49 (7 11) 78 28 50 90 - Fax: +49 (7 11) 78 28 50 91 Mail: li...@lihas.de - Web: http://lihas.de Linux, Netzwerke, Consulting Support - USt-ID: DE 227 816 626 Stuttgart -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] ML6000 does not work al of a sudden
I'm neither familiar with the ML6000 nor with Solaris, but in my experience, it's generally a good idea to take error messages literally, starting with the very first one. So: 27-Feb 19:54 de001bs002-sd JobId 732: Fatal error: Error writing data to spool file. ERR=Disc quota exceeded Find the location and maximum size of spool files in your Bacula configuration, then check whether your filesystem quota settings for that location allow the Bacula Storage Daemon to write that much, and whether there are old spool files lying around and eating up the quota. 27-Feb 19:54 de001bs002-sd JobId 732: Writing spooled data to Volume. Despooling 835,324,011,949 bytes ... 27-Feb 19:54 de001bs002-sd JobId 732: Despooling elapsed time = 00:00:01, Transfer rate = 835.3 G Bytes/second 27-Feb 19:55 de001bs002-sd JobId 732: Fatal error: Fatal despooling error. 27-Feb 19:55 de001bs002-fd JobId 732: Error: bsock.c:393 Write error sending 65536 bytes to Storage daemon:de001bs002:9103: ERR=Broken pipe 27-Feb 19:55 de001bs002-fd JobId 732: Fatal error: backup.c:1024 Network send error to SD. ERR=Broken pipe Those are inherited errors caused by the disk quota problem above. The tape drive probably wasn't even involved up to then. 28-Mar 20:26 de001bs002-sd JobId 736: Volume 000329 previously written, moving to end of data. 28-Mar 20:27 de001bs002-sd JobId 736: Error: Unable to position to end of data on device LTO4-01 (/dev/rmt/0bn): ERR=dev.c:956 ioctl MTEOM error on LTO4-01 (/dev/rmt/0bn). ERR=I/O error. A whole month later. That looks like a completely unrelated problem, possibly a defective tape. Bacula handles that quite gracefully: 28-Mar 20:27 de001bs002-sd JobId 736: Marking Volume 000329 in Error in Catalog. 28-Mar 20:27 de001bs002-sd JobId 736: 3307 Issuing autochanger unload slot 72, drive 0 command. 28-Mar 20:28 de001bs002-dir JobId 736: There are no more Jobs associated with Volume 000257. Marking it purged. 28-Mar 20:28 de001bs002-dir JobId 736: All records pruned from Volume 000257; marking it Purged 28-Mar 20:28 de001bs002-dir JobId 736: Recycled volume 000257 It marks the tape as bad and grabs the next one. Problem solved. 29-Mar 00:08 de001bs002-sd JobId 736: Fatal error: Error writing data to spool file. ERR=Disc quota exceeded Again your disk quota problem. Nothing to do with the tape drive. Finally we did replaced the tape drive. Update tape library and drive firmware and Bacula to latest version But still not working: Unsurprising. Nothing above points to the tape drive being the cause of your problem. Apr 30 15:40:52 de001bs002 scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci8086,3410@9/pci1077,137@0/fp@0,0/tape@w500308c09c25b005,0 (st0): Apr 30 15:40:52 de001bs002 Error for Command: rezero/rewind Error Level: Fatal Apr 30 15:40:52 de001bs002 scsi: [ID 107833 kern.notice]Requested Block: 0 Error Block: 0 Apr 30 15:40:52 de001bs002 scsi: [ID 107833 kern.notice]Vendor: IBM Serial Number: Apr 30 15:40:52 de001bs002 scsi: [ID 107833 kern.notice]Sense Key: Not_Ready Apr 30 15:40:52 de001bs002 scsi: [ID 107833 kern.notice]ASC: 0x3a (medium not present), ASCQ: 0x0, FRU: 0x30 Which operation did that occur with? Medium not present sounds like no tape in the drive to me. What did Bacula log for that incident? and here is the log from Bacula itself That's *not* the log of the same incident. Judging by the timestamps it's from the following day. 01-May 09:47 de001bs002-sd JobId 752: Fatal error: Error writing data to spool file. ERR=Disc quota exceeded Still the disk quota problem. Seems that the problem is that bacula cannot find the end of the tape no more. Not at all. Rather, it seems that your disk spool area is simply full. HTH Tilman -- Tilman Schmidt Phoenix Software GmbH Bonn, Germany -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Error 3915 Bad Job command
Hi, for one year or so I'm using bacula to do my backups and everything works fine. The director is version 5.0.1 on an Ubuntu 10.04 LTS Server. The version which was shipped/updated by the distribution. One SD is also version 5.0.1 on the same machine. The other (main) SD was 5.?.? on my Workstation, a Linux Mint 12 (Ubuntu 11.10 clone). This was also the one, which was shipped with this distribution. Some days ago I updated/reinstalled this Workstation to an Ubuntu 12.04 (bacula version 5.2.6) and now every attempt to store anything via the SD on this machine does not work: 03-May 23:23 vbserver-dir JobId 1486: Start Backup JobId 1486, Job=lpasgg207.2012-05-03_23.23.57_15 03-May 23:27 vbserver-dir JobId 1486: Fatal error: Storage daemon rejected Job command: 3915 Bad Job command. stat=-1 CMD: JobId=1486 job=lpasgg207.2012-05-03_23.23.57_15 job_name=lpasgg207 client_name=lpasgg207-fd type=66 level=70 FileSet=lpasgg207 NoAttr=0 SpoolAttr=0 FileSetMD5=J6/Lb3tny3IJIz+BFnM0GC SpoolData=0 WritePartAfterJob=1 PreferMountedVols=1 SpoolSize=0 Resched=144058568 Does anyone know the reason for this behavior? All (3-4) hits I had in googling this error are very old and point to version mismatchen between director and SD. But I think it's impossible to use the same version, if you have more than 5 or 10 Computers with several operating systems. regards Volker -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error 3915 Bad Job command
Am 04.05.2012 00:25, schrieb Volker Böhm: The director is version 5.0.1 on an Ubuntu 10.04 LTS Server. The version which was shipped/updated by the distribution. One SD is also version 5.0.1 on the same machine. The other (main) SD was 5.?.? on my Workstation, a Linux Mint 12 (Ubuntu 11.10 clone). This was also the one, which was shipped with this distribution. Some days ago I updated/reinstalled this Workstation to an Ubuntu 12.04 (bacula version 5.2.6) and now every attempt to store anything via the SD on this machine does not work: 03-May 23:23 vbserver-dir JobId 1486: Start Backup JobId 1486, Job=lpasgg207.2012-05-03_23.23.57_15 03-May 23:27 vbserver-dir JobId 1486: Fatal error: Storage daemon rejected Job command: 3915 Bad Job command. stat=-1 CMD: JobId=1486 job=lpasgg207.2012-05-03_23.23.57_15 job_name=lpasgg207 client_name=lpasgg207-fd type=66 level=70 FileSet=lpasgg207 NoAttr=0 SpoolAttr=0 FileSetMD5=J6/Lb3tny3IJIz+BFnM0GC SpoolData=0 WritePartAfterJob=1 PreferMountedVols=1 SpoolSize=0 Resched=144058568 Does anyone know the reason for this behavior? All (3-4) hits I had in googling this error are very old and point to version mismatchen between director and SD. And that is indeed the reason. The director and SD should have the same version. It's no problem if the FDs are older. (Except for the unfixed bugs and missing features in that old versions, of course.) But I think it's impossible to use the same version, if you have more than 5 or 10 Computers with several operating systems. No, it's not impossible. First of all, it's quite unusual to have 5 or 10 SDs. Most installations have one or two, and in the majority of cases one of them will be on the same machine as the director. So you only have to make sure that those two or three machines run the same version. Second, you don't have to run the version that comes with the distribution. I'd even say in most cases you shouldn't, as that version is usually outdated. There are packages of the latest stable version available for most common distributions, and you would be well advised to run those instead of the older ones packaged with the distribution, at least on your director and SDs. And finally, if everything else fails, you can always compile exactly the version you need from source. HTH Tilman -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
