Re: [Bacula-users] Identify corrupted volume files

2019-08-15 Thread Martin Simmons 
bls -j will do some checks the volume without using the catalog and should
detect corruption (see
https://www.bacula.org/9.4.x-manuals/en/utility/Volume_Utility_Tools.html#SECTION00251000).

__Martin


> On Wed, 14 Aug 2019 16:48:35 -0300, José Queiroz said:
> 
> Thanks for the response, Pedro and Heitor.
> 
> Some of these volumes were recent, but most of them were historical, and
> were purged/pruned from the catalogs.
> Is there a way to verify them without using the catalogs? In fact, I only
> need to know if the volumes are consistent/readable.
> 
> Em seg, 12 de ago de 2019 às 17:20, Pedro Oliveira 
> escreveu:
> 
> > Hi Jose,
> >
> > you can create a new verify job and check the catalog against the disk or
> > create a script and use the bscan and  bls volume utility tools, please
> > check the following urls:
> >
> > *Verify*Run a verify Job. In general, *verify* jobs permit you to compare
> > the contents of the catalog to the file system, or to what was backed up.
> > In addition, to verifying that a tape that was written can be read, you can
> > also use *verify* as a sort of tripwire intrusion detection.
> >
> > For a *Verify* Job, the Level may be one of the following:
> >
> > *DiskToCatalog*This level causes Bacula to read the files as they
> > currently are on disk, and to compare the current file attributes with the
> > attributes saved in the catalog from the last backup for the job specified
> > on the *VerifyJob* directive. This level differs from the
> > *VolumeToCatalog* level described above by the fact that it doesn't
> > compare against a previous Verify job but against a previous backup. When
> > you run this level, you must supply the verify options on your Include
> > statements. Those options determine what attribute fields are compared.
> >
> > This command can be very useful if you have disk problems because it will
> > compare the current state of your disk against the last successful backup,
> > which may be several jobs.
> >
> >
> > https://www.bacula.org/9.4.x-manuals/en/main/New_Features_in_7_4_0.html#SECTION00621000
> >
> >
> > https://www.bacula.org/9.4.x-manuals/en/utility/Volume_Utility_Tools.html#SECTION00271000
> >
> > Best
> > Pedro
> >
> > José Queiroz  escreveu no dia segunda, 12/08/2019 à(s)
> > 19:22:
> >
> >> Hi,
> >>
> >> I had a massive disk fault that corrupted some of my backup volumes.
> >> As I'm very short on disk space, I want to find which of the volumes were
> >> affected by the disk fault, to discard them.
> >> Is there any tool I can use to do that?
> >>
> >> Thanks in advance.
> >> ___
> >> Bacula-users mailing list
> >> Bacula-users@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/bacula-users
> >>
> >
> >
> > --
> > --
> > Cumprimentos,
> >
> > Pedro Oliveira
> >
> > Rua Antonio Botto | Nº 23 | 1º A | 2950-565 Quinta do Anjo
> >
> > tel +351 218 440 100 | mobile +351 916 111 464
> >
> > website   |
> >   
> > 
> >
> >
> > *Aviso de Confidencialidade:* Esta mensagem é exclusivamente destinada ao
> > seu destinatário, podendo conter informação CONFIDENCIAL, cuja divulgação
> > está expressamente vedada nos termos da lei. Caso tenha recepcionado
> > indevidamente esta mensagem, solicitamos-lhe que nos comunique esse mesmo
> > facto por esta via ou para o telefone +351 916111464  devendo apagar o seu
> > conteúdo de imediato.
> >
> > This message is intended exclusively for its addressee. It may contain
> > CONFIDENTIAL information protected by law. If this message has been
> > received by error, please notify us via e-mail or by telephone
> > +351916111464 and delete it immediately.
> >
> >
> >
> 


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

[Bacula-users] Restore job failure reasons

2019-08-15 Thread William Muriithi 
Hello

We have a bacula server that been running fine for a while.  I have previously 
done test restore to ensure that the backups are usable with success until now.

So this being the first time I have seen a failed restore, I am trying to 
figure out why it failed and haven't gone far using google.  The job that I was 
trying to restore had completed successfully, so all I could think of it tape 
issue.

Would there be another cause that I can investigate?  Anyone else seen this 
error before? 

15-Aug 02:37 bacula-dir JobId 13304: Using Device "ULTRIUM-HH7" to read.
15-Aug 02:37 backup-sd JobId 13304: 3307 Issuing autochanger "unload slot 1, 
drive 0" command.
15-Aug 02:39 backup-sd JobId 13304: 3304 Issuing autochanger "load slot 10, 
drive 0" command.
15-Aug 02:40 backup-sd JobId 13304: 3305 Autochanger "load slot 10, drive 0", 
status is OK.
15-Aug 02:40 backup-sd JobId 13304: Ready to read from volume "000317L6" on 
device "ULTRIUM-HH7" (/dev/nst0).
15-Aug 02:40 backup-sd JobId 13304: Forward spacing Volume "000317L6" to 
file:block 2408:1.
15-Aug 02:47 backup-sd JobId 13304: Error: block.c:1045 Read error on fd=7 at 
file:blk 3193:0 on device "ULTRIUM-HH7" (/dev/nst0). ERR=Input/output error.
15-Aug 02:47 backup-sd JobId 13304: End of Volume at file 3193 on device 
"ULTRIUM-HH7" (/dev/nst0), Volume "000317L6"
15-Aug 02:47 backup-sd JobId 13304: Fatal error: acquire.c:75 Acquire read: 
num_writers=1 not zero. Job 13304 canceled.
15-Aug 02:47 backup-sd JobId 13304: Fatal error: mount.c:876 Cannot open 
Dev="ULTRIUM-HH7" (/dev/nst0), Vol=000317L6
15-Aug 02:47 backup-sd JobId 13304: End of all volumes.

Regards,
William

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