[Bacula-users] Vchanger 1.0.3 Released

2020-05-12 Thread Josh Fisher
Vchanger 1.0.3 was released today. This is mostly a bug fix release, 
correcting the number of slots reported by SIZE/LIST commands, a 
compilation error on FreeBSD, and failure of the launch scripts invoked 
by udev on some platforms.


Also, the locking mechanism to allow multiple instances and 
automatically issuing 'update slots' and other commands to bconsole has 
been redesigned to use POSIX semaphores. Automatic mounts via udev 
scripts should now be very robust and automatically perform the needed 
bconsole 'update slots' command whenever removable disks are attached or 
detached.


Bugs Fixed:
 17 SIZE/​LIST commands return wrong number of slots
 18 Compilation fails on FreeBSD 13 (head)

Enjoy!

Josh Fisher




___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Query regarding Verify Backup

2020-05-12 Thread Heitor Faria
> Hello

Hello Wanderlei and Sachin, 

> You can use Verify Jobs. Take a look in the manual:
> [
> https://www.bacula.org/9.6.x-manuals/en/main/Configuring_Director.html#SECTION00213
> |
> https://www.bacula.org/9.6.x-manuals/en/main/Configuring_Director.html#SECTION00213
> ]

I think the Verify Job is very unpractical for the OP requirements, since you 
can't (e.g.) tell Bacula to Verify a bunch of jobs or all jobs from a tape. It 
is necessary to specify the original jobs to Verify, one by one. 
Perhaps, a btape read test, or even a bscan or bls would be more practical. I 
wish bconsole itself had such a media test command. 

Regards, 
-- 

MSc Heitor Faria 
CEO Bacula LATAM 
mobile1: + 1 909 655-8971 
mobile2: + 55 61 98268-4220 
[ https://www.linkedin.com/in/msc-heitor-faria-5ba51b3 ] 
[ http://www.bacula.com.br/ ] 

América Latina 
[ http://bacula.lat/ | bacula.lat ] | [ http://www.bacula.com.br/ | 
bacula.com.br ] 
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Query regarding Verify Backup

2020-05-12 Thread Wanderlei Huttel
Hello

You can use Verify Jobs. Take a look in the manual:
https://www.bacula.org/9.6.x-manuals/en/main/Configuring_Director.html#SECTION00213


You Just need to create a VerifyJob:

Job{
  Name = "Verify_Data"
  Type = Verify
  Level = Data
  JobDefs = "DefaultJob"
  Enabled = no
}

run job=Verify_Data fileset=FileSet_Bacula client=bacula-fd jobid=9


Best regards

*Wanderlei Hüttel*



Em ter., 12 de mai. de 2020 às 04:49, *Sachin* H 
escreveu:

> Hello Experts,
>
> For Audit reasons, we have to somehow prove that the regular backups done
> on tapes are verified. Is there a verify option available? We use Bacula
> version of 7.4.0 running on SLES 12.
> Any pointers will be really appreciated.
>
> Thanks in advance.
>
> Regards,
> Admin
> ___
> 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] Query regarding Verify Backup

2020-05-12 Thread Eric Bollengier via Bacula-users
Hello Heitor,

On 2020-05-12 14:36, Heitor Faria wrote:
>> Hello
> 
> Hello Wanderlei and Sachin, 
> 
>> You can use Verify Jobs. Take a look in the manual:
>> [
>> https://www.bacula.org/9.6.x-manuals/en/main/Configuring_Director.html#SECTION00213
>> |
>> https://www.bacula.org/9.6.x-manuals/en/main/Configuring_Director.html#SECTION00213
>> ]
> 
> I think the Verify Job is very unpractical for the OP requirements, since you 
> can't (e.g.) tell Bacula to Verify a bunch of jobs or all jobs from a tape. 
> It is necessary to specify the original jobs to Verify, one by one. 
> Perhaps, a btape read test, or even a bscan or bls would be more practical. I 
> wish bconsole itself had such a media test command. 

If you run the backup job with the level=data, it will check
automatically the last job present in the catalog. You can schedule this
level after the backup job for example. It is probably better to have a
different priority, then you can run also the verify jobs after the
backup jobs. It is fully automatic.

It is also possible to use a runscript command to fire the verify job
when you want with the when= parameter (the timing is important).

You can also check the job type=verify level=volumetocatalog that can
read a tape and compare all attributes with the catalog data. It works
at the volume level, and it might be better for tapes.

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Query regarding Verify Backup

2020-05-12 Thread Heitor Faria
> Hello Heitor,

Hello Eric,
 
> You can also check the job type=verify level=volumetocatalog that can
> read a tape and compare all attributes with the catalog data. It works
> at the volume level, and it might be better for tapes.

This is nice, but I think it would not verify backup stored data portion (only 
metadata):

"VolumeToCatalog: This level causes Bacula to read the file attribute data 
written to the Volume from the last Job. The file attribute data are compared 
to the values saved in the Catalog database and any differences are reported. 
This is similar to the Catalog level except that instead of comparing the disk 
file attributes to the catalog database, the attribute data written to the 
Volume is read and compared to the catalog database. Although the attribute 
data including the signatures (MD5 or SHA1) are compared, the actual file data 
is not compared (it is not in the catalog)."

I suppose a bad block on the data portion would be undetected? 

Regards,
-- 
MSc Heitor Faria 
CEO Bacula LATAM 
mobile1: + 1 909 655-8971 
mobile2: + 55 61 98268-4220 
[ https://www.linkedin.com/in/msc-heitor-faria-5ba51b3 ] 
[ http://www.bacula.com.br/ ] 

América Latina 
[ http://bacula.lat/ | bacula.lat ] | [ http://www.bacula.com.br/ | 
bacula.com.br ]


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


[Bacula-users] Check size volume using S3 Driver

2020-05-12 Thread Crystian Dorabiatto
Good morning,

Using S3 Driver and Feature Max Volume jobs=1, we can to see:

  Scheduled time: 12-May-2020 09:00:00
  Start time: 12-May-2020 11:29:49
  End time:   12-May-2020 11:53:57
  Elapsed time:   24 mins 8 secs
  Priority:   10
  FD Files Written:   445,194
  SD Files Written:   445,194
  FD Bytes Written:   4,850,167,345 (4.850 GB)
  SD Bytes Written:   4,945,815,820 (4.945 GB)
  Rate:   3349.6 KB/s
  Software Compression:   63.3% 2.7:1
  Comm Line Compression:  3.1% 1.0:1
  Snapshot/VSS:   no
  Encryption: no
  Accurate:   yes
  Volume name(s): daily-s3-19
  Volume Session Id:  20
  Volume Session Time:1589284634
  Last Volume Bytes:  766,368,138 (766.3 MB)
  Non-fatal FD errors:0
  SD Errors:  0
  FD termination status:  OK
  SD termination status:  OK
  Termination:Backup OK

But in volume:

Writing
Vol. jobs 1
Vol. files 0
Vol. bytes 766.3MB
First written 2020-05-12 11:29:49
Last written 2020-05-12 11:52:02

I think the select of volume get the info of  Last Volume Bytes: and not
size of job. Is it right?

Regards
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Query regarding Verify Backup

2020-05-12 Thread Eric Bollengier via Bacula-users
Hello Heitor,

On 2020-05-12 17:14, Heitor Faria wrote:
>  
>> You can also check the job type=verify level=volumetocatalog that can
>> read a tape and compare all attributes with the catalog data. It works
>> at the volume level, and it might be better for tapes.
> 
> This is nice, but I think it would not verify backup stored data portion 
> (only metadata):
> 
> "VolumeToCatalog: This level causes Bacula to read the file attribute data 
> written to the Volume from the last Job. The file attribute data are compared 
> to the values saved in the Catalog database and any differences are reported. 
> This is similar to the Catalog level except that instead of comparing the 
> disk file attributes to the catalog database, the attribute data written to 
> the Volume is read and compared to the catalog database. Although the 
> attribute data including the signatures (MD5 or SHA1) are compared, the 
> actual file data is not compared (it is not in the catalog)."
> 
> I suppose a bad block on the data portion would be undetected? 

On tape it will be detected, it is usually not possible to read a bad
block without an error, the tape drive is supposed to check it.

Note that bls or bscan will not check if the data is consistent, but it
will do the same, read all blocks and trigger hardware errors.

Best Regards,
Eric


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


[Bacula-users] Query regarding Verify Backup

2020-05-12 Thread *Sachin* H
Hello Experts,

For Audit reasons, we have to somehow prove that the regular backups done
on tapes are verified. Is there a verify option available? We use Bacula
version of 7.4.0 running on SLES 12.
Any pointers will be really appreciated.

Thanks in advance.

Regards,
Admin
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Tape Moving Error after server restart

2020-05-12 Thread Martin Simmons
It could be a problem with the driver or the Bacula config.

Have you tried running the btape test command recently?  See
https://www.bacula.org/9.6.x-manuals/en/problems/Testing_Your_Tape_Drive_Wit.html#SECTION0042

__Martin


> On Fri, 8 May 2020 09:25:26 +0200 (CEST), Christian Lehmann said:
> 
> Hi Martin,
> 
> I just tested the umount/eject/run/mount procedure without a restart in 
> between - and the same happens:
> 
> *umount LTO-5HH
> Automatically selected Catalog: Fritzie18-Cat
> Using Catalog "Fritzie18-Cat"
> 3002 Device ""LTO-5" (/dev/nst0)" unmounted.
> *run
> A job name must be specified.
> The defined Job resources are:
>  1: Bacula Catalog
>  2: Bacula Catalog Restore
>  3: Gruppen-LW ohne Chris LTO-5
>  4: ...
> Select Job resource (1-10): 1
> Run Backup job
> JobName:  Bacula Catalog
> Level:Full
> Client:   fritzie15-fd
> FileSet:  Catalog
> Pool: LTO-5HH-Pool (From Job resource)
> Storage:  LTO-5HH (From Job resource)
> When: 2020-05-08 09:18:01
> Priority: 11
> OK to run? (yes/mod/no): yes
> Job queued. JobId=12628
> 
> *mount LTO-5HH
> 3001 Mounted Volume: LTO-5-Tape0017
> 3001 Device ""LTO-5" (/dev/nst0)" is mounted with Volume "LTO-5-Tape0017"
> 
> 08-Mai 09:18 fritzie15-dir JobId 12628: shell command: run BeforeJob 
> "/etc/bacula/make_catalog_backup bacula bacula SockenC7"
> 08-Mai 09:18 fritzie15-dir JobId 12628: Start Backup JobId 12628, 
> Job=Bacula_Catalog.2020-05-08_09.18.07_51
> 08-Mai 09:19 fritzie15-dir JobId 12628: Using Device "LTO-5" to write.
> 08-Mai 09:19 fritzie15-sd JobId 12628: Volume "LTO-5-Tape0017" previously 
> written, moving to end of data.
> 08-Mai 09:19 fritzie15-sd JobId 12628: Error: Unable to position to end of 
> data on Tape device "LTO-5" (/dev/nst0): ERR=tape_dev.c:363 ioctl MTIOCGET 
> error on "LTO-5" (/dev/nst0). ERR=Erfolg.
> 
> 08-Mai 09:19 fritzie15-sd JobId 12628: Marking Volume "LTO-5-Tape0017" in 
> Error in Catalog
> 
> So it seems not to be connected to a reset of the device.
> 
> Thank you very much for your kind assistance,
> 
> Christian
> 
> -Original-Nachricht-
> Betreff: Re: [Bacula-users] Tape Moving Error after server restart
> Datum: 2020-05-08T07:05:36+0200
> Von: "Christian Lehmann" 
> An: "Martin Simmons" 
> 
> Dear Martin,
> 
> I am sorry for answering so late, but due to the COVID-19/Sars-CoV2 situation 
> I had a lot of other issues to solve.
> 
> During the restart no backup was running - just the tape was positioned in 
> the middle of the tape.
> 
> I will test the unmounr/eject/mount procedure without a reboot today and 
> report the results.
> 
> Best,
> 
> Christian
> 
> 
> 
> -Original-Nachricht-
> Betreff: Re: [Bacula-users] Tape Moving Error after server restart
> Datum: 2020-03-20T16:19:57+0100
> Von: "Martin Simmons" 
> An: "Christian Lehmann" 
> 
> Did the restart happen in the middle of a backup?
> 
> Does the backup error occur after you unmount the tape from bconole, eject it
> and then insert and mount it again, without rebooting?
> 
> __Martin
> 
> 
> On Wed, 18 Mar 2020 13:52:09 +0100 (CET), Christian Lehmann said:
> > 
> > Dear all,
> >  
> > from time to time I get an error after I restart the server running my 
> > bacula director and also a storage daemon with an Tandberg LTO-5 HH.
> >  
> > The current bacula version is 9.6.3 (9th March 2020) on a Debian machine.
> >  
> > The situation is:
> >  
> > Bacula has made some backups to a tape in the drive, but the tape isn't 
> > full yet.
> >  
> > Than a restart of the machine is happing (for example due to a Kernel 
> > update). So bacula is shutting down and the tape is rewinded.
> >  
> > After restart, as soon as I initiate a backup job, bacula tries the 
> > positioning to the end of the tape to write the data (in this case I just 
> > run a small backup job of my bacula database).
> >  
> > However, he fails to do so, with the error "ERFOLG" (which is German and 
> > means SUCCESS). So I do not understand what is happening there. Has someone 
> > come accross such a behaviour?
> >  
> > 18-Mär 13:19 fritzie15-dir JobId 12352: shell command: run BeforeJob 
> > "/etc/bacula/make_catalog_backup bacula bacula VERY_SAFE_PASSWORD_XXX"
> > 18-Mär 13:19 fritzie15-dir JobId 12352: Start Backup JobId 12352, 
> > Job=Bacula_Catalog.2020-03-18_13.19.09_03
> > 18-Mär 13:19 fritzie15-dir JobId 12352: Using Device "LTO-5" to write.
> > 18-Mär 13:19 fritzie15-sd JobId 12352: Volume "LTO-5-Tape0027" previously 
> > written, moving to end of data.
> > 18-Mär 13:20 fritzie15-sd JobId 12352: Error: Unable to position to end of 
> > data on Tape device "LTO-5" (/dev/nst0): ERR=tape_dev.c:363 ioctl MTIOCGET 
> > error on "LTO-5" (/dev/nst0). ERR=Erfolg.
> > 18-Mär 13:20 fritzie15-sd JobId 12352: Marking Volume "LTO-5-Tape0027" in 
> > Error in Catalog.
> >  
> > Now, I am a bit afraid, because I do not know, if a restore of the backuped 
> > data would work.
> >  
> > Thank you all in advance!
> >  

Re: [Bacula-users] Query regarding Verify Backup

2020-05-12 Thread Marcin Haba
Hello Sachin,

Some time ago I prepared an article that describes Verify jobs in
details, including diagrams and description about what each of Bacula
components do during particular verify job types. This article is in
Polish, but you can use online translator to read it.

https://www.bacula.pl/artykul/61/zadania-weryfikacji-bacula/

Best regards,
Marcin Haba (gani)

On Tue, 12 May 2020 at 09:49, *Sachin* H  wrote:
>
> Hello Experts,
>
> For Audit reasons, we have to somehow prove that the regular backups done on 
> tapes are verified. Is there a verify option available? We use Bacula version 
> of 7.4.0 running on SLES 12.
> Any pointers will be really appreciated.
>
> Thanks in advance.
>
> Regards,
> Admin
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users



-- 
"Greater love hath no man than this, that a man lay down his life for
his friends." Jesus Christ

"Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie
za przyjaciół swoich." Jezus Chrystus


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Query regarding Verify Backup

2020-05-12 Thread Martin Simmons
> On Tue, 12 May 2020 12:14:33 -0300 (BRT), Heitor Faria said:
> 
> > Hello Heitor,
> 
> Hello Eric,
>  
> > You can also check the job type=verify level=volumetocatalog that can
> > read a tape and compare all attributes with the catalog data. It works
> > at the volume level, and it might be better for tapes.
> 
> This is nice, but I think it would not verify backup stored data portion 
> (only metadata):
> 
> "VolumeToCatalog: This level causes Bacula to read the file attribute data 
> written to the Volume from the last Job. The file attribute data are compared 
> to the values saved in the Catalog database and any differences are reported. 
> This is similar to the Catalog level except that instead of comparing the 
> disk file attributes to the catalog database, the attribute data written to 
> the Volume is read and compared to the catalog database. Although the 
> attribute data including the signatures (MD5 or SHA1) are compared, the 
> actual file data is not compared (it is not in the catalog)."
> 
> I suppose a bad block on the data portion would be undetected? 

Every Bacula block has a checksum, so it should detect media corruption.

__Martin


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users