Server bacula-sd

97 views
Skip to first unread message

Emanuel Castelo

unread,
Aug 27, 2021, 12:37:20 PM8/27/21
to Bacula Backup-Pt-Br

Bom dia,

Estou com um problema há algum tempo com minha unidade de fita. Meu servidor bacula-sd parou e não subiu mais, tive que reinstalar o sistema operacional e o bacula-sd novamente.

Depois disso não consigo mais fazer o backup e restauração das fitas, aparentemente pelo que vejo nos logs me parece um problema de label. Não consigo identificar o que aconteceu.

O meu bacula-dir está em outro servidor e nesse eu não tive problemas, está funcionando normalmente e o banco a princípio está normal.

Seguem os logs do server:
  1. 27-Aug 10:21 bextract JobId 0: Error: [SE0203] The Volume=000018L5 on device="Drive-1" (/dev/tape/by-id/scsi-35001438016074078-nst) appears to be unlabeled.
  2. bextract: acquire.c:279-0 Read acquire: Read label block failed: requested Volume "000018L5" on Tape device "Drive-1" (/dev/tape/by-id/scsi-35001438016074078-nst) is not a Bacula labeled Volume, because: ERR=[SE0203] The Volume=000018L5 on device="Drive-1" (/dev/tape/by-id/scsi-35001438016074078-nst) appears to be unlabeled.
  3. 27-Aug 10:21 bextract JobId 0: Warning: acquire.c:279 Read acquire: Read label block failed: requested Volume "000018L5" on Tape device "Drive-1" (/dev/tape/by-id/scsi-35001438016074078-nst) is not a Bacula labeled Volume, because: ERR=[SE0203] The Volume=000018L5 on device="Drive-1" (/dev/tape/by-id/scsi-35001438016074078-nst) appears to be unlabeled.
  4. 27-Aug 10:21 bextract JobId 0: No slot defined in catalog (slot=0) for Volume "000018L5" on "Drive-1" (/dev/tape/by-id/scsi-35001438016074078-nst).
  5. 27-Aug 10:21 bextract JobId 0: Cartridge change or "update slots" may be required.
  6. Mount Volume "000018L5" on device "Drive-1" (/dev/tape/by-id/scsi-35001438016074078-nst) and press return when ready:
------------------

  1. 3935 Device ""Drive-0" (/dev/tape/by-id/scsi-35001438016074075-nst)" is blocked labeling a Volume.
  2. No VolName for Slot=1 InChanger set to zero.
  3. Connecting to Storage daemon TapeLibrary at 192.168.255.54:9103 ...
  4. 3935 Device ""Drive-0" (/dev/tape/by-id/scsi-35001438016074075-nst)" is blocked labeling a Volume.
  5. No VolName for Slot=3 InChanger set to zero.
  6. Connecting to Storage daemon TapeLibrary at 192.168.255.54:9103 ...
  7. 3935 Device ""Drive-0" (/dev/tape/by-id/scsi-35001438016074075-nst)" is blocked labeling a Volume.
  8. No VolName for Slot=5 InChanger set to zero.
  9. Connecting to Storage daemon TapeLibrary at 192.168.255.54:9103 ...
  10. 3935 Device ""Drive-0" (/dev/tape/by-id/scsi-35001438016074075-nst)" is blocked labeling a Volume.
  11. No VolName for Slot=6 InChanger set to zero.
  12. Connecting to Storage daemon TapeLibrary at 192.168.255.54:9103 ...
  13. 3935 Device ""Drive-0" (/dev/tape/by-id/scsi-35001438016074075-nst)" is blocked labeling a Volume.
  14. No VolName for Slot=7 InChanger set to zero.
  15. Connecting to Storage daemon TapeLibrary at 192.168.255.54:9103 ...
  16. 3935 Device ""Drive-0" (/dev/tape/by-id/scsi-35001438016074075-nst)" is blocked labeling a Volume.
  17. No VolName for Slot=9 InChanger set to zero.
  18. Connecting to Storage daemon TapeLibrary at 192.168.255.54:9103 ...
  19. 3935 Device ""Drive-0" (/dev/tape/by-id/scsi-35001438016074075-nst)" is blocked labeling a Volume.
  20. No VolName for Slot=10 InChanger set to zero.
  21. Connecting to Storage daemon TapeLibrary at 192.168.255.54:9103 ...
  22. 3935 Device ""Drive-0" (/dev/tape/by-id/scsi-35001438016074075-nst)" is blocked labeling a Volume.
  23. No VolName for Slot=12 InChanger set to zero.
Alguem já passou por uma situação dessa? Alguma dica do que eu possa fazer?

Agradeço!
Reply all
Reply to author
Forward
0 new messages