Bacula-users

Re: [Bacula-users] upgade bacula from 1.38.11 to 2.4.4 brings Fatal error: Error getting Volume info: 1990 Invalid Catalog Request:

2009-09-17 03:38:44
Subject: Re: [Bacula-users] upgade bacula from 1.38.11 to 2.4.4 brings Fatal error: Error getting Volume info: 1990 Invalid Catalog Request:
From: "Bartosz.C" <bartosz.c AT gmail DOT com>
Date: Thu, 17 Sep 2009 09:33:10 +0200
Bruno thanks for your assistance.

>It could be 2 things, a pb of right between the director and mysql.
>And trouble with right as bacula should run now director and sd as non root.
>Just check the /var/lib/bacula and dir where you store backup are owned by the bacula user.
>Next try to connect to mysql with bacula user to be sure the database doesn't reject connexion.
Everything is ok and works fine.


I have performed a test, I have install director 1.38 once again on a different pc, I have changed configs on
pc3 - bacula-sd and pc10-15 - bacula-fd to listen this bacula-director 1.38 version, and everytig works fine.
and when I changed configs to listen to bacula 2.4 it fail.
I have no idea what can be wrong.


I discover few more problems. The first one is really big.

1. Scheduled job of bacula on windows bacula-fd failed, but when I run it using bconsole it works fine:
**************************************************************************
Job runned from schedule:
**************

17-wrz 02:28 backup-wro-dir JobId 105: Start Backup JobId 105, Job=wro_mssql_codz.2009-09-17_02.28.00.15

17-wrz 02:28 backup-wro-dir JobId 105: Created new Volume "wro_mssql_codz-0053" in catalog.

17-wrz 02:28 backup-wro-dir JobId 105: Using Device "backup1-file"

17-wrz 02:28 backup1-sd JobId 105: Labeled new Volume "wro_mssql_codz-0053" on device "backup1-file" (/virtual/backup1).

17-wrz 02:28 backup1-sd JobId 105: Wrote label to prelabeled Volume "wro_mssql_codz-0053" on device "backup1-file" (/virtual/backup1) 17-wrz 02:28 backup-wro-dir JobId 105: Max Volume jobs exceeded. Marking Volume "wro_mssql_codz-0053" as Used.

17-wrz 02:28 nyk-wro-srv3-fd JobId 105: Generate VSS snapshots. Driver="VSS Win 2003", Drive(s)="D"

17-wrz 02:28 nyk-wro-srv3-fd JobId 105:����� Could not stat D:\System_Backup\database: ERR=Access is denied.

17-wrz 02:28 nyk-wro-srv3-fd JobId 105: VSS Writer (BackupComplete): "System Writer", State: 0x1 (VSS_WS_STABLE) 17-wrz 02:28 backup1-sd JobId 105: Job write elapsed time = 00:00:12, Transfer rate = 0bytes/second 17-wrz 02:28 nyk-wro-srv3-fd JobId 105: VSS Writer (BackupComplete): "MSDEWriter", State: 0x1 (VSS_WS_STABLE) 17-wrz 02:28 nyk-wro-srv3-fd JobId 105: VSS Writer (BackupComplete): "Registry Writer", State: 0x1 (VSS_WS_STABLE) 17-wrz 02:28 nyk-wro-srv3-fd JobId 105: VSS Writer (BackupComplete): "Event Log Writer", State: 0x1 (VSS_WS_STABLE) 17-wrz 02:28 nyk-wro-srv3-fd JobId 105: VSS Writer (BackupComplete): "COM+ REGDB Writer", State: 0x1 (VSS_WS_STABLE) 17-wrz 02:28 nyk-wro-srv3-fd JobId 105: VSS Writer (BackupComplete): "WMI Writer", State: 0x1 (VSS_WS_STABLE) 17-wrz 02:28 nyk-wro-srv3-fd JobId 105: VSS Writer (BackupComplete): "BITS Writer", State: 0x1 (VSS_WS_STABLE) 17-wrz 02:28 backup-wro-dir JobId 105: Bacula backup-wro-dir 2.4.4 (28Dec08): 17-wrz-2009 02:28:14

Build OS:�������������� i486-pc-linux-gnu debian 5.0

JobId:����������������� 105

Job:������������������� wro_mssql_codz.2009-09-17_02.28.00.15

Backup Level:���������� Full

Client:���������������� "nyk-wro-srv3-fd" 2.4.1 (07Jul08) Linux,Cross-compile,Win32

FileSet:��������������� "MSSQL_wro" 2009-09-11 15:06:53

Pool:������������������ "wro_mssql_codz" (From Job resource)

Storage:������� ��������"backup1-main" (From Job resource)

Scheduled time:�������� 17-wrz-2009 02:28:00

Start time:������������ 17-wrz-2009 02:28:02

End time:�������������� 17-wrz-2009 02:28:14

Elapsed time:���������� 12 secs

Priority:�������������� 10

FD Files Written:������ 0

SD Files Written:������ 0

FD Bytes Written:������ 0 (0 B)

SD Bytes Written:������ 0 (0 B)

Rate:������������������ 0.0 KB/s

Software Compression:�� None

VSS:������������������� yes

Storage Encryption:���� no

Volume name(s):��������

Volume Session Id:����� 42

Volume Session Time:��� 1252924911

Last Volume Bytes:����� 656 (656 B)

Non-fatal FD errors:��� 1

SD Errors:������������� 0

FD termination status:OK

SD termination status:OK

Termination:����������� Backup OK -- with warnings

17-wrz 02:28 backup-wro-dir JobId 105: Begin pruning Jobs.

17-wrz 02:28 backup-wro-dir JobId 105: No Jobs found to prune.

17-wrz 02:28 backup-wro-dir JobId 105: Begin pruning Files.

17-wrz 02:28 backup-wro-dir JobId 105: No Files found to prune.

17-wrz 02:28 backup-wro-dir JobId 105: End auto prune.


**************************************************************************************************************
The same job runned from bconsole:
********************

17-wrz 09:06 backup-wro-dir JobId 108: Start Backup JobId 108, Job=wro_mssql_codz.2009-09-17_09.06.54.19

17-wrz 09:06 backup-wro-dir JobId 108: There are no more Jobs associated with Volume "wro_mssql_codz-0053". Marking it purged.

17-wrz 09:06 backup-wro-dir JobId 108: All records pruned from Volume "wro_mssql_codz-0053"; marking it "Purged"

17-wrz 09:06 backup-wro-dir JobId 108: Recycled volume "wro_mssql_codz-0053"

17-wrz 09:06 backup-wro-dir JobId 108: Using Device "backup1-file"

17-wrz 09:06 backup1-sd JobId 108: Recycled volume "wro_mssql_codz-0053" on device "backup1-file" (/virtual/backup1), all previous data lost.

17-wrz 09:06 backup-wro-dir JobId 108: Max Volume jobs exceeded. Marking Volume "wro_mssql_codz-0053" as Used.

17-wrz 09:07 nyk-wro-srv3-fd JobId 108: Generate VSS snapshots. Driver="VSS Win 2003", Drive(s)="D"

17-wrz 09:08 nyk-wro-srv3-fd JobId 108: VSS Writer (BackupComplete): "System Writer", State: 0x1 (VSS_WS_STABLE) 17-wrz 09:07 backup1-sd JobId 108: Job write elapsed time = 00:00:56, Transfer rate = 557.0 K bytes/second 17-wrz 09:08 nyk-wro-srv3-fd JobId 108: VSS Writer (BackupComplete): "MSDEWriter", State: 0x1 (VSS_WS_STABLE) 17-wrz 09:08 nyk-wro-srv3-fd JobId 108: VSS Writer (BackupComplete): "Registry Writer", State: 0x1 (VSS_WS_STABLE) 17-wrz 09:08 nyk-wro-srv3-fd JobId 108: VSS Writer (BackupComplete): "Event Log Writer", State: 0x1 (VSS_WS_STABLE) 17-wrz 09:08 nyk-wro-srv3-fd JobId 108: VSS Writer (BackupComplete): "COM+ REGDB Writer", State: 0x1 (VSS_WS_STABLE) 17-wrz 09:08 nyk-wro-srv3-fd JobId 108: VSS Writer (BackupComplete): "WMI Writer", State: 0x1 (VSS_WS_STABLE) 17-wrz 09:08 nyk-wro-srv3-fd JobId 108: VSS Writer (BackupComplete): "BITS Writer", State: 0x1 (VSS_WS_STABLE) 17-wrz 09:07 backup-wro-dir JobId 108: Bacula backup-wro-dir 2.4.4 (28Dec08): 17-wrz-2009 09:07:52

Build OS:�������������� i486-pc-linux-gnu debian 5.0

JobId:����������������� 108

Job:������������������� wro_mssql_codz.2009-09-17_09.06.54.19

Backup Level:���������� Full

Client:���������������� "nyk-wro-srv3-fd" 2.4.1 (07Jul08) Linux,Cross-compile,Win32

FileSet:��������������� "MSSQL_wro" 2009-09-11 15:06:53

Pool:������������������ "wro_mssql_codz" (From Job resource)

Storage:��������������� "backup1-main" (From Job resource)

Scheduled time:�������� 17-wrz-2009 09:06:52

Start time:������������ 17-wrz-2009 09:06:56

End time:������������� 17-wrz-2009 09:07:52

Elapsed time:���������� 56 secs

Priority:�������������� 10

FD Files Written:������ 10

SD Files Written:������ 10

FD Bytes Written:������ 31,194,634 (31.19 MB)

SD Bytes Written:������ 31,196,351 (31.19 MB)

Rate:��������� ���������557.0 KB/s

Software Compression:�� 88.4 %

VSS:������������������� yes

Storage Encryption:���� no

Volume name(s):�������� wro_mssql_codz-0053

Volume Session Id:����� 47

Volume Session Time:��� 1252924911

Last Volume Bytes:����� 31,263,775 (31.26 MB)

Non-fatal FD errors:��� 0

SD Errors:������������� 0

FD termination status:OK

SD termination status:OK

Termination:����������� Backup OK

17-wrz 09:07 backup-wro-dir JobId 108: Begin pruning Jobs.

17-wrz 09:07 backup-wro-dir JobId 108: No Jobs found to prune.

17-wrz 09:07 backup-wro-dir JobId 108: Begin pruning Files.

17-wrz 09:07 backup-wro-dir JobId 108: No Files found to prune.

17-wrz 09:07 backup-wro-dir JobId 108: End auto prune.

*****************************************************************************************

2. bconsole -> status -> (1)director
****************
backup-wro-dir Version: 2.4.4 (28 December 2008) i486-pc-linux-gnu debian 5.0
Daemon started 16-wrz-09 08:51, 18 Jobs run since started.
�Heap: heap=1,282,048 smbytes=89,566 max_bytes=167,540 bufs=724 max_bufs=879

Scheduled Jobs:
Level��������� Type���� Pri� Scheduled��������� Name�������������� Volume
======================================================
Full���������� Backup��� 10� 18-wrz-09 01:03��� waw_fw_tyg�������� *unknown*
Full���������� Backup��� 10� 18-wrz-09 01:04��� wro_fw_tyg�������� *unknown*
Full���������� Backup��� 10� 18-wrz-09 01:05��� wro_fw_network_tyg *unknown*
Full���������� Backup��� 10� 18-wrz-09 01:06��� trn_fw_tyg�������� *unknown*
Full���������� Backup��� 11� 18-wrz-09 01:10��� BackupCatalog����� backup-label
Full���������� Backup��� 10� 18-wrz-09 02:01��� wro_fb_codz������� *unknown*
Full���������� Backup��� 10� 18-wrz-09 02:02��� waw_mssql_sym_codz *unknown*
Full���������� Backup��� 10� 18-wrz-09 02:03��� wro_mysql_codz���� *unknown*
Incremental��� Backup��� 10� 18-wrz-09 02:17��� TygodniowyMax����� *unknown*
Full���������� Backup��� 10� 18-wrz-09 02:28��� wro_mssql_codz���� *unknown*
Full���������� Backup��� 10� 18-wrz-09 02:31��� wro_srv2_codz����� *unknown*
Full���������� Backup��� 10� 18-wrz-09 02:32��� wro_srv3_codz����� *unknown*
====
***************************************************************************************

Is it normal to see *unknown* below Volume field?


Bartosz.



On Thu, Sep 17, 2009 at 7:49 AM, Bruno Friedmann <bruno AT ioda-net DOT ch> wrote:
Hi, with all your informations, it seems you get the right package.

It could be 2 things, a pb of right between the director and mysql.
And trouble with right as bacula should run now director and sd as non root.

Just check the /var/lib/bacula and dir where you store backup are owned by the bacula user.

Next try to connect to mysql with bacula user to be sure the database doesn't reject connexion.
( it normally issue a error in this case )
su bacula; mysql bacula;
mysql>select * from Version;

Otherwise, I don't have a idea ...
Perharps starting daemon in foreground with some level of debug, would give more informations.



Bartosz.C wrote:
>>> Just check if you have the right director !
>>> Normally if the wrong ( using an empty sqlite db ) a list media should
> show empty
> dpkg -l | grep bacula
> ii �bacula-common � � � � � � � � � � 2.4.4-1 � � � � � � � � �network
> backup, recovery and verification - common support fil
> ii �bacula-console � � � � � � � � � �2.4.4-1 � � � � � � � � �network
> backup, recovery and verification - text console
> ii �bacula-director-common � � � � � �2.4.4-1 � � � � � � � � �network
> backup, recovery and verification - Director common fi
> ii �bacula-director-mysql � � � � � � 2.4.4-1 � � � � � � � � �network
> backup, recovery and verification - MySQL storage for
> ii �bacula-fd � � � � � � � � � � � � 2.4.4-1 � � � � � � � � �network
> backup, recovery and verification - file daemon
> ii �bacula-sd � � � � � � � � � � � � 2.4.4-1 � � � � � � � � �network
> backup, recovery and verification - storage daemon
> ii �bacula-sd-mysql � � � � � � � � � 2.4.4-1 � � � � � � � � �network
> backup, recovery and verification - MySQL SD tools
>
> dpkg -l | grep mysql
> ii �bacula-director-mysql � � � � � � 2.4.4-1 � � � � � � � � �network
> backup, recovery and verification - MySQL storage for
> ii �bacula-sd-mysql � � � � � � � � � 2.4.4-1 � � � � � � � � �network
> backup, recovery and verification - MySQL SD tools
> ii �libdbd-mysql-perl � � � � � � � � 4.007-1 � � � � � � � � �A Perl5
> database interface to the MySQL database
> ii �libmysqlclient15off � � � � � � � 5.0.51a-24+lenny2 � � � �MySQL
> database client library
> ii �mysql-client-5.0 � � � � � � � � �5.0.51a-24+lenny2 � � � �MySQL
> database client binaries
> ii �mysql-common � � � � � � � � � � �5.0.51a-24+lenny2 � � � �MySQL
> database common files
> ii �mysql-server � � � � � � � � � � �5.0.51a-24+lenny2 � � � �MySQL
> database server (metapackage depending on the latest ver
> ii �mysql-server-5.0 � � � � � � � � �5.0.51a-24+lenny2 � � � �MySQL
> database server binaries
>
> In etch-n-half distribution I had:
> dpkg -l | grep bacula
> ii �bacula-common � � � � � � � � � � �1.38.11-8
> Network backup, recovery and verification (C
> ii �bacula-console � � � � � � � � � � 1.38.11-8
> Network backup, recovery and verification (M
> ii �bacula-director-common � � � � � � 1.38.11-8
> Network backup, recovery and verification (D
> ii �bacula-director-mysql � � � � � � �1.38.11-8
> Network backup, recovery and verification (D
> ii �bacula-fd � � � � � � � � � � � � �1.38.11-8
> Network backup, recovery and verification (F
>
> It looks pretty the same like new one - except number of the versions.
> So your question confuse me now I really do not know, do I have a right
> bacula-director? :)
>
>
>>> Did you ensure that the database have been updated by the script
>>> a mysql sql select * from Version; should return 10 for a 2.4.4 version.
> No, the data base was not updated, I deleted it and created new one.
> I simply have changed distribution from etch-n-half to lenny so everything
> consider databases has been started from the beginning.
> And database is empty (or was empty since last Friday). Its really weird for
> me - cause all worked fine on �previous version.
> (except bugs of course - which by the way help me to make decision to
> upgrade the backup system)
>
> I will be grateful for any clue.
> Bartosz.
>
>
> On Mon, Sep 14, 2009 at 5:06 PM, Bruno Friedmann <bruno AT ioda-net DOT ch> wrote:
>
>> Hi Bartosz,
>>
>> Just two remarks, I've seen you are using the debian packages, and
>> sometimes ago, another user have just made
>> an update on this os. Result he was going from bacula-mysql to
>> bacula-sqlite ...
>>
>> Just check if you have the right director !
>> Normally if the wrong ( using an empty sqlite db ) a list media should show
>> empty ...
>>
>> Ok we admit you have the good director/mysql.
>> Did you ensure that the database have been updated by the script
>> a mysql sql select * from Version; should return 10 for a 2.4.4 version.
>>
>> If not, try to find the upgrade script update_bacula_tables normally in
>> /usr/lib[64]/bacula
>>
>> Hope this help a bit
>>
>>
>> Bartosz.C wrote:
>>> Hi,
>>> I have more or less working version of bacula 1.38.11 which looks like:
>>>
>>> pc1 - bacula-fd, bacula-console,bacula-director-mysql, mysql
>>> pc2 - bacula-sd
>>> pc5-10 - bacula-fd writing to pc2
>>> pc3 - bacula-sd
>>> pc10-15 - bacula-fd writing to pc3
>>>
>>> I decided to change it to 2.4.4 cause to many bugs in previous version
>>> and now it looks like
>>> pc1 - bacula-fd,
>>> pc2 - bacula-sd, bacula-console,bacula-director-mysql, mysql
>>> pc5-10 - bacula-fd writing to pc2
>>> pc3 - bacula-sd
>>> pc10-15 - bacula-fd writing to pc3
>>>
>>> I have copied all configs to new server, and everything is working
>>> fine exept backups from pc10-15,
>>> Now I'm getting error:
>>>
>>>
>> *************************************************************************************
>>> 14-wrz 13:53 backup-wro-dir JobId 63: No prior Full backup Job record
>> found.
>>> 14-wrz 13:53 backup-wro-dir JobId 63: No prior or suitable Full backup
>>> found in catalog. Doing FULL backup.
>>> 14-wrz 13:53 backup-wro-dir JobId 63: Start Backup JobId 63,
>>> Job=TygWymiatacz.2009-09-14_13.53.17.03
>>> 14-wrz 13:53 backup-wro-dir JobId 63: Using Device "backup3-trn_file"
>>> 14-wrz 13:53 backup-wro-dir JobId 63: Fatal error: catreq.c:344
>>> Invalid Catalog request: CatReq
>>> Job=TygWymiatacz.2009-09-14_13.53.17.03 UpdateMedia
>>> VolName=TygWymiatacz-0003 VolJobs=0 VolFiles=0 VolBlocks=0 VolBytes=1
>>> VolMounts=1 VolErrors=0 VolWrites=1 MaxVolBytes=0 EndTime=1252928894
>>> VolStatus=Append Slot=0 relabel=1 InChanger=0 VolReadTime=0
>>> VolWriteTime=0 VolParts=0
>>> 14-wrz 13:48 fw-trn-sd: TygWymiatacz.2009-09-14_13.53.17.03 Fatal
>>> error: Error getting Volume info: 1990 Invalid Catalog Request: CatReq
>>> Job=TygWymiatacz.2009-09-14_13.53.17.03 UpdateMedia
>>> VolName=TygWymiatacz-0003 VolJobs=0 VolFiles=0 VolBlocks=0 VolBytes=1
>>> VolMounts=1 VolErrors=0 VolWrites=1 MaxVolBytes=0 EndTime=1252928894
>>> VolStatus=Append Slot=0 relabel=1 InChanger=0 VolReadTime=0
>>> VolWriteTime=0 VolParts=0
>>> 14-wrz 13:48 fw-trn-sd: Marking Volume "" in Error in Catalog.
>>> 14-wrz 13:53 backup-wro-dir JobId 63: Fatal error: catreq.c:344
>>> Invalid Catalog request: CatReq
>>> Job=TygWymiatacz.2009-09-14_13.53.17.03 UpdateMedia
>>> VolName=TygWymiatacz-0003 VolJobs=0 VolFiles=0 VolBlocks=0 VolBytes=0
>>> VolMounts=0 VolErrors=0 VolWrites=0 MaxVolBytes=0 EndTime=1252928894
>>> VolStatus=Error Slot=0 relabel=0 InChanger=0 VolReadTime=0
>>> VolWriteTime=0 VolParts=0
>>> 14-wrz 13:47 wymiatacz-fd JobId 63: Fatal error: job.c:1817 Bad
>>> response to Append Data command. Wanted 3000 OK data
>>> , got 3903 Error append data
>>>
>>> 14-wrz 13:48 fw-trn-sd: TygWymiatacz.2009-09-14_13.53.17.03 Fatal
>>> error: Error getting Volume info: 1990 Invalid Catalog Request: CatReq
>>> Job=TygWymiatacz.2009-09-14_13.53.17.03 UpdateMedia
>>> VolName=TygWymiatacz-0003 VolJobs=0 VolFiles=0 VolBlocks=0 VolBytes=0
>>> VolMounts=0 VolErrors=0 VolWrites=0 MaxVolBytes=0 EndTime=1252928894
>>> VolStatus=Error Slot=0 relabel=0 InChanger=0 VolReadTime=0
>>> VolWriteTime=0 VolParts=0
>>> 14-wrz 13:48 fw-trn-sd: TygWymiatacz.2009-09-14_13.53.17.03 Fatal
>>> error: Job 63 canceled.
>>> 14-wrz 13:53 backup-wro-dir JobId 63: Error: Bacula backup-wro-dir
>>> 2.4.4 (28Dec08): 14-wrz-2009 13:53:22
>>> � Build OS: � � � � � � � i486-pc-linux-gnu debian 5.0
>>> � JobId: � � � � � � � � �63
>>> � Job: � � � � � � � � � �TygWymiatacz.2009-09-14_13.53.17.03
>>> � Backup Level: � � � � � Full (upgraded from Incremental)
>>> � Client: � � � � � � � � "wymiatacz-fd" 2.4.4 (28Dec08)
>>> i486-pc-linux-gnu,debian,5.0
>>> � FileSet: � � � � � � � �"SystemOnly_trn" 2009-09-12 01:02:00
>>> � Pool: � � � � � � � � � "TygWymiatacz" (From Job resource)
>>> � Storage: � � � � � � � �"backup3-trn" (From Job resource)
>>> � Scheduled time: � � � � 14-wrz-2009 13:53:07
>>> � Start time: � � � � � � 14-wrz-2009 13:53:21
>>> � End time: � � � � � � � 14-wrz-2009 13:53:22
>>> � Elapsed time: � � � � � 1 sec
>>> � Priority: � � � � � � � 10
>>> � FD Files Written: � � � 0
>>> � SD Files Written: � � � 0
>>> � FD Bytes Written: � � � 0 (0 B)
>>> � SD Bytes Written: � � � 0 (0 B)
>>> � Rate: � � � � � � � � � 0.0 KB/s
>>> � Software Compression: � None
>>> � VSS: � � � � � � � � � �no
>>> � Storage Encryption: � � no
>>> � Volume name(s):
>>> � Volume Session Id: � � �2
>>> � Volume Session Time: � �1252925453
>>> � Last Volume Bytes: � � �0 (0 B)
>>> � Non-fatal FD errors: � �0
>>> � SD Errors: � � � � � � �0
>>> � FD termination status: �Error
>>> � SD termination status: �Error
>>> � Termination: � � � � � �*** Backup Error ***
>>>
>> ************************************************************************************************
>>> And rest of error looks exactly the same.
>>> my configs concider this case:
>>>
>> ************************************************************************************************
>>> bacula-dir.conf (192.168.100.99)
>>> ********************
>>> FileSet {
>>> � Name = "SystemOnly_trn"
>>> � Include {
>>> � � Options {
>>> � � � signature = MD5
>>> � � � _onefs_ = no
>>> � � }
>>> � � File = /
>>> � }
>>> � Exclude {
>>> � � File = /proc
>>> � � File = /dev
>>> � � File = /tmp
>>> � � File = /.journal
>>> � � File = /.fsck
>>> � � File = /sys
>>> � � File = /home
>>> � }
>>> }
>>>
>>> Client {
>>> � Name = wymiatacz-fd
>>> � Address = 192.168.100.100
>>> � FDPort = 9102
>>> � Catalog = MyCatalog
>>> � Password = "password_for_fd" � � � � �# password for FileDaemon
>>> � File Retention = 30 days � � � � � �# 30 days
>>> � Job Retention = 6 months � � � � � �# six months
>>> � AutoPrune = yes � � � � � � � � � � # Prune expired Jobs/Files
>>> }
>>>
>>> Storage {
>>> � Name = backup3-trn
>>> � Maximum Concurrent Jobs = 10
>>> � Address = 192.168.100.101
>>> � SDPort = 9103
>>> � Password = "password_for_sd"
>>> � Device = backup3-trn_file
>>> � Media Type = File
>>> }
>>>
>>> Pool {
>>> � Name = TygWymiatacz
>>> � Pool Type = Backup
>>> � Recycle = yes
>>> � AutoPrune = yes
>>> � Volume Retention = 6 days
>>> � Maximum Volume Jobs = 1
>>> � Label Format = TygWymiatacz-
>>> � Maximum Volumes = 8
>>> }
>>>
>>> Job {
>>> � Name = "TygWymiatacz"
>>> � Client = wymiatacz-fd
>>> � Storage = backup3-trn
>>> � Pool = TygWymiatacz
>>> � Level = Incremental
>>> � Type = Backup
>>> � FileSet="SystemOnly_trn"
>>> � Schedule = "TygWymiatacz"
>>> � Write Bootstrap = "/var/lib/bacula/BackupCatalog.bsr"
>>> � Priority = 10
>>> � Messages = Standard
>>> }
>>>
>>> Schedule {
>>> � Name = "TygWymiatacz"
>>> � Run = Full sun at 1:02
>>> � Run = Incremental mon-sat at 1:02
>>> }
>>>
>> ************************************************************************************************
>>> bacula-fd (192.168.100.100)
>>> ****************
>>> Director {
>>> � Name = backup-wro-dir
>>> � � Password = "password_for_fd"
>>> � � }
>>> Director {
>>> � Name = wymiatacz-mon
>>> � Password = "OWQrB2VMaoOQuB5qra+kWGzrfJ5nMfK+GVMvu1snxK7E"
>>> � Monitor = yes
>>> }
>>>
>>> FileDaemon { � � � � � � � � � � � � �# this is me
>>> � Name = wymiatacz-fd
>>> � FDport = 9102 � � � � � � � � �# where we listen for the director
>>> � WorkingDirectory = /var/lib/bacula
>>> � Pid Directory = /var/run/bacula
>>> � Maximum Concurrent Jobs = 20
>>> � FDAddress = 192.168.100.100
>>> }
>>>
>>> Messages {
>>> � Name = Standard
>>> � director = backup-wro-dir = all, !skipped, !restored
>>> }
>>>
>>>
>> ************************************************************************************************
>>> bacula-sd (192.168.100.101)
>>> ****************
>>> Storage { � � � � � � � � � � � � � � # definition of myself
>>> � Name = fw-trn-sd
>>> � SDPort = 9103 � � � � � � � � �# Director's port
>>> � WorkingDirectory = "/var/lib/bacula"
>>> � Pid Directory = "/var/run/bacula"
>>> � Maximum Concurrent Jobs = 20
>>> � SDAddress = 192.168.100.101
>>> }
>>>
>>> Director {
>>> � � Name = backup-wro-dir
>>> � � Password = "password_for_sd"
>>> }
>>>
>>> Device {
>>> � � Name = backup3-trn_file
>>> � � Media Type = File
>>> � � Archive Device = /virtual/backup
>>> � � LabelMedia = yes;
>>> � � Random Access = yes;
>>> � � AutomaticMount = yes;
>>> � � RemovableMedia = no;
>>> � � AlwaysOpen = yes;
>>> }
>>>
>>> Messages {
>>> � � Name = Standard
>>> � � director = backup-wro-dir = all, debug
>>> }
>>>
>> ************************************************************************************************
>>> additional information:
>>> When I try bconsole -> status -> all, I don't get any errors,
>>> bacula-director can communicate with all clients and storages
>>> properly.
>>>
>>>
>>> What can I do to start it working again?
>>>
>>
>>


------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users