Menu
▾
▴
[Bacula-bugs] [bacula 0001734]: Cannot restore from another SD using same Media Type.
|
From: Mantis B. T. <no...@bu...> - 2011-09-28 10:38:34
|
Issue 0001734 is now monitored by user mnalis. ====================================================================== http://bugs.bacula.org/view.php?id=1734 ====================================================================== Reported By: brancaleone Assigned To: ebollengier ====================================================================== Project: bacula Issue ID: 1734 Category: Storage Daemon Reproducibility: always Severity: minor Priority: normal Status: closed Resolution: no change required Fixed in Version: ====================================================================== Date Submitted: 2011-05-11 12:50 BST Last Modified: 2011-09-28 11:38 BST ====================================================================== Summary: Cannot restore from another SD using same Media Type. Description: In our setup we have 1 director, 2 storage daemons and 2 file daemon. Director is named : moinecopix.dom_bureau01-dir Storage 1 is named : moinecopix.dom_bureau01-sd Storage 2 is named : duplicatix.dom_bureau01-sd SD-1 and SD-2 have one Device each, that is a LTO-3 tape drive. They also have the same Media Type defined (LTO3). SD-1 is used for backups, and SD-2 is only used for restore. Setup was working fine in 2.2, we where able to restore file from tapes mounted in SD-2. Since upgrade to 5.0.3, this is not working anymore. When selecting another storage than SD-1 in restore jobs leads to errors. When asked on mailing list, no one could tell me if that's a bug or not : http://www.mail-archive.com/bac...@li.../msg45567.html I have the feeling that is a bug because : - The documentation seems to say that it should be possible : "For example, if you specify a Media Type of "DDS-4" then during the restore, Bacula will be able to choose any Storage Daemon that handles "DDS-4"." - The wizard let me choose another storage daemon for restore. If restore is only possible from SD-1, i think it should not let me change the storage daemon used. - Same setup was working in 2.2.x Steps to Reproduce: - Launch restore wizard in bconsole - Folow the wizard and at the end, choose "mod" option to change the storage daemon used for restore. - Job is canceled and get errors in logs Additional Information: This is the error we get in the logs : 11-May 12:08 moinecopix.dom_bureau01-dir JobId 1478: Start Restore Job RestoreFiles.2011-05-11_12.08.14_18 11-May 12:08 moinecopix.dom_bureau01-dir JobId 1478: Using Device "LTO-3" 11-May 12:08 duplicatix.dom_bureau01-sd JobId 1478: Fatal error: No Volume names found for restore. 11-May 12:08 moinecopix.dom_bureau01-fd JobId 1478: Fatal error: job.c:2031 Bad response to Read Data command. Wanted 3000 OK data , got 3000 error ====================================================================== ---------------------------------------------------------------------- (0005891) ebollengier (administrator) - 2011-05-20 14:56 http://bugs.bacula.org/view.php?id=1734#c5891 ---------------------------------------------------------------------- Sorry you have problems with Bacula, but what you are trying to do is unsupported. This is written in the manual in the Storage section, perhaps it can be more clear, so feel free to submit a documentation patch. "Thus you should probably use the same Media Type specification for all drives where the Media can be freely interchanged. This is not generally an issue if you have a single Storage daemon, but it is with multiple Storage daemons, especially if they have incompatible media" Issue History Date Modified Username Field Change ====================================================================== 2011-05-11 12:50 brancaleone New Issue 2011-05-20 14:56 ebollengier Note Added: 0005891 2011-05-20 14:56 ebollengier Status new => closed 2011-05-20 14:56 ebollengier Assigned To => ebollengier 2011-05-20 14:56 ebollengier Resolution open => no change required ====================================================================== |