[Bacula-users] Wrong storage proposed while restoring

2013-06-24 Thread stefano scotti
Hello list,

I have this annoying situation: while restoring, after selecting the
destination client, bacula proposes the following restore job parameters:

JobName: RestoreFiles
Bootstrap:   /var/lib/bacula/hagrid-dir.restore.11.bsr
Where:   /home/restores
Replace: always
FileSet: client_3
Backup Client:   client_1-fd
Restore Client:  client_1-fd
Storage:  client_2
When:2013-06-24 12:55:17
Catalog: client_1
Priority:10
Plugin Options:  *None*


But the storage is wrong! it should be the storage of client_1, not
client_2.
This mismatching cause the job to fail.
I have to modify manually this parameter every time i have to restore a
file.

Actually the Storage parameter seems to be taken randomly by bacula,
sometime is client_1, sometime client_2, sometime client_3, etc...

Is it an intended behaviour? and if it is, why?

Thank you very much.
--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Wrong storage proposed while restoring

2013-06-24 Thread Bruno Friedmann
On Monday 24 June 2013 13.02:32 stefano scotti wrote:
 Hello list,
 
 I have this annoying situation: while restoring, after selecting the
 destination client, bacula proposes the following restore job parameters:
 
 JobName: RestoreFiles
 Bootstrap:   /var/lib/bacula/hagrid-dir.restore.11.bsr
 Where:   /home/restores
 Replace: always
 FileSet: client_3
 Backup Client:   client_1-fd
 Restore Client:  client_1-fd
 Storage:  client_2
 When:2013-06-24 12:55:17
 Catalog: client_1
 Priority:10
 Plugin Options:  *None*
 
 
 But the storage is wrong! it should be the storage of client_1, not
 client_2.
 This mismatching cause the job to fail.
 I have to modify manually this parameter every time i have to restore a
 file.
 
 Actually the Storage parameter seems to be taken randomly by bacula,
 sometime is client_1, sometime client_2, sometime client_3, etc...
 
 Is it an intended behaviour? and if it is, why?
This is how is defined your default restore object.
You could prepare one type of restore ( one per client with correct 
definitions for that client) and then just fire-up the restore.

 
 Thank you very much.
-- 

Bruno Friedmann 
Ioda-Net Sàrl www.ioda-net.ch
 
openSUSE Member  Ambassador
GPG KEY : D5C9B751C4653227
irc: tigerfoot

--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Wrong storage proposed while restoring

2013-06-24 Thread James Harper
 Hello list,
 
 I have this annoying situation: while restoring, after selecting the 
 destination
 client, bacula proposes the following restore job parameters:
 
 JobName: RestoreFiles
 Bootstrap:   /var/lib/bacula/hagrid-dir.restore.11.bsr
 Where:   /home/restores
 Replace: always
 FileSet: client_3
 Backup Client:   client_1-fd
 Restore Client:  client_1-fd
 Storage:  client_2
 When:2013-06-24 12:55:17
 Catalog: client_1
 Priority:10
 Plugin Options:  *None*
 
 
 But the storage is wrong! it should be the storage of client_1, not client_2.
 This mismatching cause the job to fail.
 I have to modify manually this parameter every time i have to restore a file.
 
 Actually the Storage parameter seems to be taken randomly by bacula,
 sometime is client_1, sometime client_2, sometime client_3, etc...
 
 Is it an intended behaviour? and if it is, why?
 

What is the definition of your RestoreFiles job?

James


--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Wrong storage proposed while restoring

2013-06-24 Thread stefano scotti
2013/6/24 James Harper james.har...@bendigoit.com.au

  Hello list,
 
  I have this annoying situation: while restoring, after selecting the
 destination
  client, bacula proposes the following restore job parameters:
 
  JobName: RestoreFiles
  Bootstrap:   /var/lib/bacula/hagrid-dir.restore.11.bsr
  Where:   /home/restores
  Replace: always
  FileSet: client_3
  Backup Client:   client_1-fd
  Restore Client:  client_1-fd
  Storage:  client_2
  When:2013-06-24 12:55:17
  Catalog: client_1
  Priority:10
  Plugin Options:  *None*
 
 
  But the storage is wrong! it should be the storage of client_1, not
 client_2.
  This mismatching cause the job to fail.
  I have to modify manually this parameter every time i have to restore a
 file.
 
  Actually the Storage parameter seems to be taken randomly by bacula,
  sometime is client_1, sometime client_2, sometime client_3, etc...
 
  Is it an intended behaviour? and if it is, why?
 

 What is the definition of your RestoreFiles job?

 James


Here it is:

Job {
  Name = RestoreFiles
  Type = Restore
  Client=client_3-fd
  FileSet=client_3-fd
  Storage = client_3
  Pool = client_3
  Messages = Standard
  Where = /home/restores
}
--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users