Re: [Bacula-users] Client console restrictions

2006-06-15 Thread David Rodriguez Demelos

Hi,

I think I have found the problem:
In bacula-dir.conf file I have configured de brandy2 client console
resource like this (rest of my clients are similar):

Console {
  Name = Brandy2-con
  Password = 
  JobACL = Brandy2, RestoreFiles-Linux
  ClientACL = brandy2-fd
  StorageACL = FDA
  ScheduleACL = *all*
  PoolACL = *all*
  FileSetACL = Linux
  CatalogACL = MyCatalog
  CommandACL = run, q, quit, restore, status
}


I have a job RestoreFiles-Linux for restore all linux clients.
Including this job to console resource in bacucula-dir.conf file, when you
launch a different client restore job, bacula don't acccept this client job,
but it accept the RestoreFiles-Linux job and restore another client selected
files using this job (RestoreFiles-Linux). But if you don't put this job in
console resource, from client console can not restore files.
I have tryed configure one FileSet and one restore job for ech client, but
don't work, because it choose corresponding restore job and restore equally.

I don't know which is the solution. Somebody can help me?

Thanks.
--
View this message in context: 
http://www.nabble.com/Client-console-restrictions-t1773302.html#a4882125
Sent from the Bacula - Users forum at Nabble.com.



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


Re: [Bacula-users] Client console restrictions

2006-06-13 Thread David Rodriguez Demelos

On Monday 12 June 2006 13:09, David Rodriguez Demelos wrote:
 I'm a new bacula user and I have a little problem with client console.
 I have configured the client console restrictions in bacula-dir.conf like
 this:

 ...

 Console {
   Name = Client Name
   Password = 
   JobACL = Job Client Name, RestoreFiles-Linux
   ClientACL = client-fd
   StorageACL = My Storage
   ScheduleACL = *all*
   PoolACL = *all*
   FileSetACL = Linux
   CatalogACL = MyCatalog
   CommandACL = run, q, quit, restore, status
 }

 ...

 With this configuration I want the client console only can use its jobs.
 When I execute run jobs from client it work ok, but when I execute a
 restore job from client with bconsole program and select the option number
 3 (Enter list of comma separated JobIds to select), I can select a other
 client job. Bacula launch a error message (bacula can not use this job),
 but the restore process continue and finally it restore this backup in the
 first client computer. This is very dangeraous, because any client can get
 another client data.

Bacula should not allow the user to use JobIds from another client, so this
sounds like a bug.  However, you will need to provide me with specific
output
showing this problem as well as a bit of information about your setup.  
Please see the Support Page of the Bacula web site.  In particular without
knowing what Bacula version you are using, I cannot even start ...

 How I can configure this for to solve this problem?

 Thanks.
 --
 View this message in context:
 http://www.nabble.com/Client-console-restrictions-t1773302.html#a4826704
 Sent from the Bacula - Users forum at Nabble.com.



 ___
 Bacula-users mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/bacula-users

-- 
Best regards,

Kern

  (
  /\
  V_V 









Hi, tanks Kern for your attention.
My bacula server version is 1.38.9 and it is installed in Red Hat EL4. I
have a windows 2003 client (Davidov) and Red Hat EL4 client (brandy2) with
version 1.38.9 too. Furthermore I have two Debian clients (Corleone and LIA)
with version 1.36.3. I have the problem in all my clients.

I have configured my bacula-dir.conf file like this:


#
# Default Bacula Director Configuration file
#
#  The only thing that MUST be changed is to add one or more
#   file or directory names in the Include directive of the
#   FileSet resource.
#
#  For Bacula release 1.38.9 (02 May 2006) -- redhat Enterprise 3.0
#
#  You might also want to change the default email address
#   from root to your address.  See the mail and operator
#   directives in the Messages resource.
#
#
  Director  ##

Director {# define myself
  Name = bacula-dir
  Description = Director de Bacula
  DIRport = 9101# where we listen for UA connections
  QueryFile = /etc/bacula/query.sql
  WorkingDirectory = /var/bacula
  PidDirectory = /var/run
  Maximum Concurrent Jobs = 20
  Password =  # Console password
  Messages = Standard
}



  JobDefs  ##

JobDefs {
  Name = Default
  Type = Backup
  Level = Full 
  Schedule = Setmanal
  Storage = FDA
  Messages = Standard
  Full Backup Pool = Full
  Pool = Full
  Priority = 10
  Maximum Concurrent Jobs = 20
}



###  Jobs  

##
# Bacula Job #
##

Job {
  Name = Bacula
  Client = bacula-fd
  JobDefs = Default
  FileSet = Linux
  Write Bootstrap = /var/bacula/Bacula.bsr
}



###
# Brandy2 Job #
###

Job {
  Name = Brandy2
  Client = brandy2-fd
  JobDefs = Default
  FileSet = Linux
  Write Bootstrap = /var/bacula/Brandy2.bsr
}




# Corleone Job #


Job {
  Name = Corleone
  Client = corleone-fd
  JobDefs = Default
  FileSet = Linux
  Write Bootstrap = /var/bacula/Corleone.bsr
}



###
# LIA Job #
###

Job {
  Name = LIA
  Client = LIA-fd
  JobDefs = Default
  FileSet = Linux
  Write Bootstrap = /var/bacula/LIA.bsr
}



###
# Davidov Job #
###

Job {
  Name = Davidov
  Client = davidov-fd
  JobDefs = Default
  FileSet = Windows
  Write Bootstrap = /var/bacula/Davidov.bsr
}



#
# BackupCatalog Job #
#

Job {
  Name = BackupCatalog
  Type = Backup
  JobDefs = Default
  Level = Full
  Client = bacula-fd
  FileSet=Catalog
  Schedule = Setmanal-Despres-Backup
  Storage = FDA
  Messages = Standard
  Pool = Full
  # This creates an ASCII copy of the catalog
  RunBeforeJob = /etc/bacula/make_catalog_backup bacula bacula
  # This deletes the copy of the catalog
  RunAfterJob  = /etc/bacula/delete_catalog_backup
  Write Bootstrap = /var/bacula/BackupCatalog.bsr
  Priority = 11   # run after main backup
  Maximum Concurrent Jobs = 20
}



##

Re: [Bacula-users] Client console restrictions

2006-06-12 Thread Kern Sibbald
On Monday 12 June 2006 13:09, David Rodriguez Demelos wrote:
 I'm a new bacula user and I have a little problem with client console.
 I have configured the client console restrictions in bacula-dir.conf like
 this:

 ...

 Console {
   Name = Client Name
   Password = 
   JobACL = Job Client Name, RestoreFiles-Linux
   ClientACL = client-fd
   StorageACL = My Storage
   ScheduleACL = *all*
   PoolACL = *all*
   FileSetACL = Linux
   CatalogACL = MyCatalog
   CommandACL = run, q, quit, restore, status
 }

 ...

 With this configuration I want the client console only can use its jobs.
 When I execute run jobs from client it work ok, but when I execute a
 restore job from client with bconsole program and select the option number
 3 (Enter list of comma separated JobIds to select), I can select a other
 client job. Bacula launch a error message (bacula can not use this job),
 but the restore process continue and finally it restore this backup in the
 first client computer. This is very dangeraous, because any client can get
 another client data.

Bacula should not allow the user to use JobIds from another client, so this 
sounds like a bug.  However, you will need to provide me with specific output 
showing this problem as well as a bit of information about your setup.  
Please see the Support Page of the Bacula web site.  In particular without 
knowing what Bacula version you are using, I cannot even start ...

 How I can configure this for to solve this problem?

 Thanks.
 --
 View this message in context:
 http://www.nabble.com/Client-console-restrictions-t1773302.html#a4826704
 Sent from the Bacula - Users forum at Nabble.com.



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

-- 
Best regards,

Kern

  (
  /\
  V_V


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