Although I solved the problem this is a heads up in case someone has simmilar problems you may have an idea.
For several days after I upgraded my bacula-dir to 1.38.11 I was unable to get one machine backed up. It didn't occur to me it may be a conflict with the new server and the old client and storage. The jobs were greating creating according to the schedule, but they either stayed as 'C' or turned into 'R', but a status client=<clien> didn't show the job running. I upgraded both the client for that machine and the storage daemon that client used. I have other 1.38.9 clients working with the upgraded bacula-dir and a storage daemon in the same machine as the bacula-dir. Does the storage daemon needs to be at the same level as the bacula-dir? ------------------------------------------------------------------------- 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
