Mandi! Phil Stracchino
  In chel di` si favelave...

> Is it *feasible* to install enough of a local development environment on 
> these legacy servers to locally compile a 7.x client for them?

Sure, i can try to ''backport'' bacula debian packages and deploy on these
servers but... first... how can i verbosely debug these troubles, being
sure that is a ''version trouble''.

I say that because i know that bacula try to have maximal compatibility with
file daemons, and so:

1) i'm not still sure is a compatibility trouble.

2) i don't know if there's an option/config file settings that can restiore
back compatibility.

For example on director the filedaemon is defined as:

Client {
  Name = opitergium-fd
  Description = "Opitergium Bacula File Daemon"

  Address = opitergium.od.lnf.it
  FDPort = 9102
  Password = "unknown"

  Catalog = BaculaLNF                                    # Catalog da usare

  Maximum Concurrent Jobs = 5

  File Retention = 28 days                              # Tempi di expire, 
bassi, tanto fa...
  Job Retention = 28 days
  AutoPrune = yes
}

and on the client:

Director {
  Name = lnfbacula-dir
  Password = "unknown"
}

# "Global" File daemon configuration specifications
#
FileDaemon {                            # this is me
  Name = opitergium-fd

  FDAddress = opitergium.od.lnf.it
  FDport = 9102                         # where we listen for the director

  WorkingDirectory = /var/lib/bacula
  Pid Directory = /var/run/bacula

  Maximum Concurrent Jobs = 20
}


pretty standard...

-- 
  Mentre il cuore d'Italia, da Palermo ad Aosta
  si gonfiava in un coro di vibrante protesta           (F. De Andre`)




_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to