Hello Kern;
I was using these lines in the Device resource:
Control Device = /dev/sg1
Alert Command = "/opt/bacula/scripts/tapealert %l"
…which was causing the error.
Nevertheless, after upgrade bacula to 9.0.5, as you suggested,
the error has gone away. Everything seems to be working Ok now. Even I’ve
re-activated the tape alert commands (using the new alert command for Bacula
9.0.0) and I’ve not received any errors. I have made several backups and
restores and it seems ok. Now I’m backing up a large drive almost 3TB and so
far it’s going well.
Jaime Ferrer
Ingesoft Ltda.
De: Kern Sibbald [mailto:k...@sibbald.com]
Enviado el: lunes, 06 de noviembre de 2017 17:36
Para: Jaime Ferrer; bacula-users@lists.sourceforge.net
Asunto: Re: [Bacula-users] Backup error with LTO-7
Hello Jaime,
Well in the Device resource that you show below, nothing is defined for the
Alert Command so I am not sure which one you had enabled. The first one that
is labeled "New alert command in Bacula 9.0.0" is the correct one to enable but
there seems to be some strange characters in the text that would need changing.
Perhaps you pointed the alert command to the wrong drive?
Another possibility is that you do not have the tapeinfo program loaded or that
it is not compatible with the version I was using.
In any case, if you are not having problems with the Alert Command turned off,
and the btape test command passed, you can be sure that nothing is wrong.
Best regards,
Kern
On 11/06/2017 03:13 PM, Jaime Ferrer wrote:
Thanks Kern and Andrew for your Replies.
So, I changed the cassette and the problems continued. Running
the test command in btape always ends successfully. So, reading your email, I
commented out the tape alert parameters, and now backup and restores ends
successfully. Now I will update Bacula to the latest version as you suggested,
since I’m using a stand alone drive.
Below is the device configuration for the LTO-7, since I think
that I got something wrong with the Alert command configuration.
Device {
Name = LTO-7 #
Drive Index = 0
Media Type = LTO-7
Archive Device = /dev/nst0
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
# Maximum File Size = 5G
RandomAccess = no;
AutoChanger = no;
# #
# # New alert command in Bacula 9.0.0
# # Note: you must have the sg3_utils (rpms) or the
# # sg3-utils (deb) installed on your system.
# # and you must set the correct control device that
# # corresponds to the Archive Device
#Control Device = /dev/sg1 # must be SCSI ctl for /dev/nst0 <-- this is the
line that I commented out
#Alert Command = "/opt/bacula/scripts/tapealert %l" <-- this is the line that I
commented out
#
# #
# # Enable the Alert command only if you have the mtx package loaded
# # Note, apparently on some systems, tapeinfo resets the SCSI controller
# # thus if you turn this on, make sure it does not reset your SCSI
# # controller. I have never had any problems, and smartctl does
# # not seem to cause such problems.
# #
# Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
# If you have smartctl, enable this, it has more info than tapeinfo
# Alert Command = "sh -c 'smartctl -H -l error %c'"
}
And a copy of the lsscsi –g output:
[0:0:5:0] tape HP Ultrium 7-SCSI G9Q1 /dev/st0 /dev/sg1
Kindest Regards.
Jaime Ferrer
De: Kern Sibbald [mailto:k...@sibbald.com]
Enviado el: domingo, 05 de noviembre de 2017 5:41
Para: Jaime Ferrer;
bacula-users@lists.sourceforge.net<mailto:bacula-users@lists.sourceforge.net>
Asunto: Re: [Bacula-users] Backup error with LTO-7
Hello,
Thanks for being a long term Bacula users. I agree with Andrew, it looks like
it may be a media problem rather than a drive problem. When reviewing Bacula
output, I like to see the full job log including the Bacula sign on line to be
sure what version it is.
In your case, particularly if this is a stand-alone drive, I would *strongly*
recommend upgrading to Bacula version 9.0.5, which was just released, because
it has some important fixes that correct Bacula behavior with stand-alone
drives (as opposed to autochangers).
Also, if you continue to have errors after trying a different cassette, it
would be useful to see your Storage Daemon Device resource to see what you are
calling to get the tape alert messages. The code between older Bacula's and
version 9.0.x changed rather significantly in that area, and you really need
the new Device configurations (bacula-sd.conf) for getting correct Alerts.
From what I see, it looks like you have it setup correctly but it is worth
verifying.
Best regards,
Kern
On 11/04/2017 11:07 PM, Jaime Ferrer wrote:
Hi;
I have been working with bacula for almost 10 years. It’s a
great program and I’ve installed in several servers without issues, Also It has
saved me several times! 😉 . Recently I’ve been preparing a Bacula server with
the latest version 9.0.4 with a HP Ultrium 7 tape drive. After running
successfully the btape test run, I performed the first backup and restore to
test the unit. During the first backup its fails with the following error:
JobId 28: Elapsed time=00:04:54, Transfer rate=20.13 M Bytes/second 30-Oct
13:16 local-sd JobId 28: Fatal error: Alert: Volume="TEST3" alert=3: ERR=The
operation has stopped because an error has occurred while reading or writing
data which the drive cannot correct. The drive had a hard read or write error
30-Oct 13:16 local-sd JobId 28: Fatal error: Alert: Volume="TEST3" alert=5:
ERR=The tape is damaged or the drive is faulty. Call the tape drive supplier
helpline. The drive can no longer read data from the tape 30-Oct 13:16
local-sd JobId 28: Warning: Disabled Device "LTO-7" (/dev/nst0) due to tape
alert=39.
local-sd JobId 28: Warning: Alert: Volume="TEST3" alert=39: ERR=The tape drive
may have a fault. Check for availability of diagnostic information and run
extended diagnostics if applicable. The drive may have had a failure which
may be identified by stored diagnostic information or by running extended
diagnostics (eg Send Diagnostic). Check the tape drive users manual for
instructions on running extended diagnostic tests and retrieving diagnostic
data.
FileSet: "Full Set" 2017-09-29 19:01:12
Pool: "TEST" (From Job resource)
Catalog: "MyCatalog" (From Client resource)
Storage: "LTO-7" (From Pool resource)
Scheduled time: 30-Oct-2017 13:10:55
Start time: 30-Oct-2017 13:11:03
End time: 30-Oct-2017 13:16:12
Elapsed time: 5 mins 9 secs
Priority: 11
FD Files Written: 190,214
SD Files Written: 190,214
FD Bytes Written: 5,891,151,955 (5.891 GB)
SD Bytes Written: 5,919,950,296 (5.919 GB)
Rate: 19065.2 KB/s
Software Compression: None
Comm Line Compression: None
Snapshot/VSS: no
Encryption: no
Accurate: no
Volume name(s): TEST3
Volume Session Id: 1
Volume Session Time: 1509379838
Last Volume Bytes: 17,790,732,288 (17.79 GB)
Non-fatal FD errors: 0
SD Errors: 1
FD termination status: OK
SD termination status: Error
Termination: *** Backup Error ***
As the error implies I ran the HP LTT tools but as far as I went all drive
diagnostics seems to be ok.
Looking into the failed backup job, it’s seems that the job failed just after
files are backed up, since all test jobs have the same size, around 5GB which
is the size of the test files. Also I can restore it back but finished with the
same error. The files are not stored in the catalog since the backup job fails,
so I had to restore all files at once.
30-Oct 13:20 local-dir JobId 29: Using Device "LTO-7" to read.
30-Oct 13:20 local-sd JobId 29: Ready to read from volume "TEST3" on Tape
device "LTO-7" (/dev/nst0).
30-Oct 13:20 local-sd JobId 29: Forward spacing Volume "TEST3" to addr=2:0
30-Oct 13:22 local-sd JobId 29: Elapsed time=00:01:37, Transfer rate=61.03 M
Bytes/second 30-Oct 13:22 local-sd JobId 29: Fatal error: Alert:
Volume="TEST3" alert=3: ERR=The operation has stopped because an error has
occurred while reading or writing data which the drive cannot correct. The
drive had a hard read or write error 30-Oct 13:22 .local-sd JobId 29: Fatal
error: Alert: Volume="TEST3" alert=5: ERR=The tape is damaged or the drive is
faulty. Call the tape drive supplier helpline. The drive can no longer read
data from the tape 30-Oct 13: .local-sd JobId 29: Warning: Disabled Device
"LTO-7" (/dev/nst0) due to tape alert=39.
30-Oct 13:22 .local-sd JobId 29: Warning: Alert: Volume="TEST3" alert=39:
ERR=The tape drive may have a fault. Check for availability of diagnostic
information and run extended diagnostics if applicable. The drive may have
had a failure which may be identified by stored diagnostic information or by
running extended diagnostics (eg Send Diagnostic). Check the tape drive users
manual for instructions on running extended diagnostic tests and retrieving
diagnostic data.
30-Oct 13:22 APSSCL0SRV010.apsa.local-dir JobId 29: Error: Bacula .local-dir
9.0.4 (06Sep17):
Build OS: x86_64-pc-linux-gnu redhat (Core)
JobId: 29
Job: RestoreFiles.2017-10-30_13.19.42_04
Restore Client: .local-fd
Start time: 30-Oct-2017 13:19:44
End time: 30-Oct-2017 13:22:23
Files Expected: 190,214
Files Restored: 190,214
Bytes Restored: 5,891,133,870
Rate: 37051.2 KB/s
FD Errors: 0
FD termination status: OK
SD termination status: Error
Termination: *** Restore Error ***
Testing a HP Ultirum 6 unit, Bacula works flawlessly.
So I’m starting to doubt about this unit despite its diagnostics seems to be
ok. Also I will upgrade the firmware and also driver from HPe site, and test.
Also perform a tar test round.
But meanwhile, I’m wondering if one of you have experienced something like
this? Are LTO-7 compatible with Bacula? Are there some special
parameters/config for this units (LTO-7) ?
Thanks in advance.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net<mailto:Bacula-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/bacula-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
