On Wed, Apr 20, 2011 at 5:52 PM, Jérôme Blion <jerome.bl...@free.fr> wrote: > Le 20/04/2011 16:01, Jeremy Maes a écrit : >> Op 20/04/2011 15:29, Ben Schmidt schreef: >>> I'm running a bacula 2.2.6 on a old Server that's just working. One of >>> it's Clients was replaced by a new Server with debian 6.0 today and I >>> can't get bacula running. >>> >>> Server: DIR: 2.2.6, SD: 2.2.6, SLES 10.1 amd64 >>> Client: FD: 5.0.2, debian 6.0 amd64 >>> No SSL/TLS in use. >>> ... >> Old dir with new clients won't work. The communications protocols have >> been updated so the old dir doesn't know how to talk to the new client. >> >> The easiest solution might be to rebuild the old client on the new >> platform, though a complete upgrade to the latest 5.0.3 might be better >> for future-proof-ness. >> >> Regards, >> Jeremy >> > Hello, > > Is there a compatibility matrix available ? >
No but a simple rule. The server (director and storage) must be always >= client. Also the director must be the same version as the storage. John ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
