Kern, That was the problem: bug 697. I commented out my other Storage resources from bacula-dir.conf and it worked. Thanks for the tech support, and for the great program. Kevin Kern Sibbald wrote: On Monday 13 November 2006 04:23, Kevin Christen wrote:Short story: I can backup from an instance of the file daemon to an instance of the storage daemon, but when I try to restore between them I get this error:12-Nov 21:00 tahiti-dir: Start Restore Job RestoreFiles.2006-11-12_20.59.58 12-Nov 21:13 vanuatu-fd: RestoreFiles.2006-11-12_20.59.58 Fatal error:Authorization key rejected by Storage daemon.Please see http://www.bacula.org/rel-manual/faq.html#AuthorizationErrors forhelp.12-Nov 21:13 vanuatu-fd: RestoreFiles.2006-11-12_20.59.58 Fatal error:Failed to authenticate Storage daemon.12-Nov 21:10 tahiti-dir: RestoreFiles.2006-11-12_20.59.58 Fatal error:Socket error on Storage command: ERR=No data available12-Nov 21:10 tahiti-dir: RestoreFiles.2006-11-12_20.59.58 Error: Bacula1.38.9 (02May06): 12-Nov-2006 21:10:06JobId: 19 Job: RestoreFiles.2006-11-12_20.59.58 Client: vanuatu-fd Start time: 12-Nov-2006 21:00:00 End time: 12-Nov-2006 21:10:06 Files Expected: 2,960 Files Restored: 0 Bytes Restored: 0 Rate: 0.0 KB/s FD Errors: 0 FD termination status: SD termination status: Waiting on FD Termination: *** Restore Error *** Long story: Machine A is running bacula 1.38.9 on Gentoo Linux, built from source by Portage. The director daemon is running there. Machine B is running the same version of bacula on Mac OS X built from source. I can backup from B-fd->B-sd, but I can't restore from B-sd->B-fd. A-fd and B-sd work together in either direction. Is there some difference between backup and restore in how authentication between a file daemon and a storage daemon works that would explain this? Are the config files used differently in these two scenarios? Are there any troubleshooting tests I should try?There is a bug report open indicating that Bacula gets confused on a "status all storage" command when there are multiple storage daemons. The report indicates that Bacula contacts the wrong storage daemon. If you turn on a sufficiently high command line debug level in the FD (probably better to enable it in all daemons), you should be able to see which SD the FD is attempting to contact to verify if this is indeed the problem you are seeing. I would first try -d100, and if that is insufficient try a higher level. |
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users