Re: [Bacula-users] Upgrading Debian Jessie 5.2.6 to 7.4.x?
On 08/02/2016 06:12 PM, Konstantin Khomoutov wrote: > On Tue, 2 Aug 2016 11:23:31 -0400 > "John Stoffel" wrote: > >> Debian is a great release, but boy are they stuck in the past for some >> projects. It's time to upgrade my bacula on mysql to the latest >> release. Any suggestions on the easiest way to do this? >> >> Ideally, I'd prefer to just install packages from a repository and >> have it do all the upgrade work for me. I've got a very simple setup >> where it's just two clients, one Linux, one Windows 10, and a set of >> disks volumes I write my bacula volumes to. >> >> I see that Debian Testing is starting to have the latest packages, but >> unfortunately the jessie-backports isn't supporting anything newer. >> Bummers. >> >> I guess I could just install sid/testing packages. > By the way, why do you _need_ to upgrade Bacula? Well, it is rare that anyone _need_s to upgrade Bacula, and I think most messages said that the particular person in question *should* upgrade. If a user is technical and happy with the Bacula installation, there is no need to upgrade, but if you: - Need support - Want important (in some cases critical) security fixes - Want new features - Want performance improvements - You run into a blocking bug (that is already fixed or will be fixed in a current version). ... Then it may make sense to upgrade. Best regards, Kern > I'm backing a dozen of servers some of which stuck to Bacula 5.0.2 (and > even older), with the master server (which hosts the director and SD) > still running Wheezy. I have no issues with this setup. The servers > being backed up are Windows and Debian machines. > > -- > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Upgrading Debian Jessie 5.2.6 to 7.4.x?
Hi! Only for displaying the progress of the job in the "status dir" in bconsole pay the upgrade process, more features help too... I used to compile always from source in Debian/Ubuntu for my DIR/SD daemons until I discover FreeBSD and the lack of systemd support. I love it. (7.4.2 from ports) Thanks to Dan Langille for show me the light. J. 2016-08-03 9:59 GMT+02:00 Kern Sibbald : > On 08/02/2016 06:12 PM, Konstantin Khomoutov wrote: > > On Tue, 2 Aug 2016 11:23:31 -0400 > > "John Stoffel" wrote: > > > >> Debian is a great release, but boy are they stuck in the past for some > >> projects. It's time to upgrade my bacula on mysql to the latest > >> release. Any suggestions on the easiest way to do this? > >> > >> Ideally, I'd prefer to just install packages from a repository and > >> have it do all the upgrade work for me. I've got a very simple setup > >> where it's just two clients, one Linux, one Windows 10, and a set of > >> disks volumes I write my bacula volumes to. > >> > >> I see that Debian Testing is starting to have the latest packages, but > >> unfortunately the jessie-backports isn't supporting anything newer. > >> Bummers. > >> > >> I guess I could just install sid/testing packages. > > By the way, why do you _need_ to upgrade Bacula? > Well, it is rare that anyone _need_s to upgrade Bacula, and I > think most messages said that the particular person in question > *should* upgrade. > > If a user is technical and happy with the Bacula installation, there is > no need to upgrade, but if you: > - Need support > - Want important (in some cases critical) security fixes > - Want new features > - Want performance improvements > - You run into a blocking bug (that is already fixed or >will be fixed in a current version). > ... > > Then it may make sense to upgrade. > > Best regards, > Kern > > I'm backing a dozen of servers some of which stuck to Bacula 5.0.2 (and > > even older), with the master server (which hosts the director and SD) > > still running Wheezy. I have no issues with this setup. The servers > > being backed up are Windows and Debian machines. > > > > > -- > > ___ > > Bacula-users mailing list > > Bacula-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/bacula-users > > > > > > -- > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > -- _ Francisco Javier Funes Nieto [esen...@gmail.com] CANONIGOS Servicios Informáticos para PYMES. Cl. Cruz 2, 1º Oficina 7 Tlf: 958.536759 / 661134556 Fax: 958.521354 GRANADA - 18002 -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Upgrading Debian Jessie 5.2.6 to 7.4.x?
Em 02/08/2016 13:12, Konstantin Khomoutov escreveu: By the way, why do you _need_ to upgrade Bacula? Old DIR and SD server won't backup newer FD clients. In my case a 5.2 server was unable to backup a 7.4 client running on latest xenial. -- *Marcio Merlone* -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] List Volumes without Job ?
Hi There, I am switching from bacula tape to disk based backup. I'm as good as finished and testing the system now. In this phase i recognized that it would be helpful if I could purge and truncate volumes with no jobs on it. So far I was not able to find a way to list volumes with 0 jobs on it and then purge and truncate them with some script. I tried "select VolumeName,VolJobs from Media;" but even after I have purged the jobs from a client it still shows the same amount of jobs. if it would show 0 Jobs that would be easy to script . or do I mix s'thing up ? I think it is a bit cumbersome to purge and truncate volumes. maybe there is an easy way out there ? Thanks for helping me out. --> David +-- |This was sent by d...@espros.ch via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] List Volumes without Job ?
Hello David, You can use the "prune" command for this purpose. Bacula will only prune volumes with no jobs (and files consequently) associated to it. I would recommend you to use the prune command instead of the purge command since the former respects the retention periods and the latter do not. You can have an admin job configured to run a prune of all your volumes and then the truncate. This admin job should be run while no other job is running (whenever this can be possible). This should work fine :-) Best regards, Ana On Wed, Aug 3, 2016 at 4:01 PM, dave wrote: > Hi There, > > I am switching from bacula tape to disk based backup. I'm as good as > finished and testing the system now. > > In this phase i recognized that it would be helpful if I could purge and > truncate volumes with no jobs on it. > > So far I was not able to find a way to list volumes with 0 jobs on it and > then purge and truncate them with some script. I tried "select > VolumeName,VolJobs from Media;" but even after I have purged the jobs from > a client it still shows the same amount of jobs. if it would show 0 Jobs > that would be easy to script . or do I mix s'thing up ? > > I think it is a bit cumbersome to purge and truncate volumes. maybe there > is an easy way out there ? > > Thanks for helping me out. > --> David > > +-- > |This was sent by d...@espros.ch via Backup Central. > |Forward SPAM to ab...@backupcentral.com. > +-- > > > > > -- > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Upgrading Debian Jessie 5.2.6 to 7.4.x?
John> Debian is a great release, but boy are they stuck in the past John> for some projects. It's time to upgrade my bacula on mysql to John> the latest release. Any suggestions on the easiest way to do John> this? John> Ideally, I'd prefer to just install packages from a repository John> and have it do all the upgrade work for me. I've got a very John> simple setup where it's just two clients, one Linux, one Windows John> 10, and a set of disks volumes I write my bacula volumes to. John> I see that Debian Testing is starting to have the latest John> packages, but unfortunately the jessie-backports isn't John> supporting anything newer. Bummers. John> I guess I could just install sid/testing packages. It seems that a new package, with support for upgrading from the 5.2.6 Debian Jessie release, will be out for testing in a couple of weeks, so it might be that my issue will be solved then. I love Debian for being stable, but sometimes they need to push forward a little more quickly, esp when upstream is evolving rapidly, but is also quite isolated from other packages. So I'll probably sit tight for a while and try an upgrade later this month or in September to see how it goes. John -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula btape multivolume fill test help requested
Hello, I'm having trouble installing bacula 7.4.3 on a SuSE LEAP 42.1 64 bit system with kernel 4.1.26-21-default on an LTO6 tape library. Btape's "test" and "autochanger" tests successful, but the multi-volume "fill" test is failing. I was hoping some kind person could make some suggestions about how to fix this. I interpret btape to be saying it is having trouble re-reading the last block it wrote to a tape after loading a tape. Maybe it's having trouble positioning to the correct spot on the tape. I decided this isn't an issue with the physical end of tape, because I tried setting "Maximum Volume Size = 10G" (which makes the fill test run a lot faster,) and encountered the exact same problem. At one point, I also unsuccessfully tried using stinit to change tape drive properties with guidance from: http://www.bacula.org/5.2.x-manuals/en/problems/problems/Testing_Your_Tape_Drive.html#SECTION00434000 manufacturer=IBM model = "ULTRIUM-TD6" { scsi2logical=1 sysv=0 read-ahead=1 buffering=1 async-writes=1 mode1 blocksize=0 compression=1 } I google'd this problem and found that some people with FreeBSD fixed a similar problem by setting "BSF at EOM = yes". That isn't my problem however, because When I set that option in bacula-sd.conf, btape's "test" fails. Here's some output from mt on the tape drive: mt -f /dev/st0 status drive type = Generic SCSI-2 tape drive status = 1509949440 sense key error = 0 residue count = 0 file number = 0 block number = 0 Tape block size 0 bytes. Density code 0x5a (unknown). Soft error count since last status=0 General status bits on (4101): BOT ONLINE IM_REP_EN Here's the output from btape fill: . . . Wrote block=960, file,blk=504,6280 VolBytes=2,516,582,137,856 rate=144.8 MB/s Wrote block=9605000, file,blk=504,11280 VolBytes=2,517,892,857,856 rate=144.8 MB/s 02-Aug 21:20 btape JobId 0: End of Volume "TestVolume1" at 504:14969 on device "TAPE01" (/dev/nst0). Write of 262144 bytes got -1. 02-Aug 21:20 btape JobId 0: Re-read of last block succeeded. btape: btape.c:2712-0 Last block at: 504:14968 this_dev_block_num=14969 btape: btape.c:2747-0 End of tape 504:0. Volume Bytes=2,518,859,907,072. Write rate = 144.7 MB/s 02-Aug 21:20 btape JobId 0: End of medium on Volume "TestVolume1" Bytes=2,518,859,907,072 Blocks=9,608,688 at 02-Aug-2016 21:20. 02-Aug 21:20 btape JobId 0: 3307 Issuing autochanger "unload slot 1, drive 0" command for vol TestVolume1. 02-Aug 21:22 btape JobId 0: 3304 Issuing autochanger "load slot 2, drive 0" command for vol TestVolume2. 02-Aug 21:23 btape JobId 0: 3305 Autochanger "load slot 2, drive 0", status is OK for vol TestVolume2. Wrote Volume label for volume "TestVolume2". 02-Aug 21:24 btape JobId 0: Wrote label to prelabeled Volume "TestVolume2" on tape device "TAPE01" (/dev/nst0) 02-Aug 21:24 btape JobId 0: New volume "TestVolume2" mounted on device "TAPE01" (/dev/nst0) at 02-Aug-2016 21:24. btape: btape.c:2315-0 Wrote 1000 blocks on second tape. Done. Done writing 0 records ... Wrote End of Session label. btape: btape.c:2384-0 Wrote state file last_block_num1=14968 last_block_num2=1001 btape: btape.c:2402-0 21:24:11 Done filling tapes at 0:1003. Now beginning re-read of first tape ... btape: btape.c:2480-0 Enter do_unfill 02-Aug 21:24 btape JobId 0: 3307 Issuing autochanger "unload slot 2, drive 0" command for vol TestVolume1. 02-Aug 21:25 btape JobId 0: 3304 Issuing autochanger "load slot 1, drive 0" command for vol TestVolume1. 02-Aug 21:26 btape JobId 0: 3305 Autochanger "load slot 1, drive 0", status is OK for vol TestVolume1. 02-Aug 21:26 btape JobId 0: Ready to read from volume "TestVolume1" on tape device "TAPE01" (/dev/nst0). Rewinding. Reading the first 1 records from 0:0. 1 records read now at 1:1251 Reposition from 1:1251 to 504:14968 Reading block 14968. The blocks differ at byte 0 The last block written and the block that was read back differ. The test FAILED This must be corrected before you use Bacula to write multi-tape Volumes. 02-Aug 21:28 btape JobId 0: 3307 Issuing autochanger "unload slot 1, drive 0" command for vol TestVolume2. 02-Aug 21:30 btape JobId 0: 3304 Issuing autochanger "load slot 2, drive 0" command for vol TestVolume2. 02-Aug 21:31 btape JobId 0: 3305 Autochanger "load slot 2, drive 0", status is OK for vol TestVolume2. 02-Aug 21:31 btape JobId 0: Ready to read from volume "TestVolume2" on tape device "TAPE01" (/dev/nst0). Reposition from 0:0 to 0:1 Reading block 1. The first block on the second tape matches. Reposition from 0:2 to 0:1001 Reading block 1001. The blocks differ at byte 0 The last block written and the block that was read back differ. The test FAILED This must be corrected before you use Bacula to write multi-tape Volumes. btape: btape.c:2407-0 do_unfill failed. Here's the pertinent parts of bacula-sd.conf: Device { Name = TAPE01 Media Type = LTO Archive Device =