Alan Brown wrote:
>>> "waiting to reserve a device" means that all available tape drives are
>>> in use by jobs using other Pools.
>>
>>
>> What does it mean when the "tape device" is actually a hard disk
>> directory with different files in there, one for each "tape"?
>
>
> Effectively the same thing.
Do you mean that Bacula has opened a file with a particular name in that
directory ("mounted a tape") and is stuck writing to that one file???
>> Running Jobs:
>> JobId Level Name Status
>> ======================================================================
>> 570 Full BackupCatalog.2006-12-28_21.05.00 is waiting on Storage
>> FileDiskB
>> ====
>>
>> > What does "status storage" show?
>>
>> 3) "status storage" shows this for the jammed up catalog backup:
>> *status storage
>> The defined Storage resources are:
>> 1: FileDiskA
>> 2: FileDiskB
>
>
>> Connecting to Storage daemon FileDiskB at lilac:9103
>> lilac-sd Version: 1.38.2 (20 November 2005) i686-redhat-linux-gnu redhat
>> (Stentz)
>> Daemon started 28-Dec-06 20:59, 4 Jobs run since started.
>> Running Jobs:
>> Backup Job Ngorongoro-SystemState.2006-12-28_21.00.00 waiting for Client
>> connection.
>> Incremental Backup job Ngorongoro-SystemState JobId=564 Volume=""
>> pool="PoolIncDiskB" device=""FileStorageDiskB" (/var/spool/bacula2)"
>> Files=0 Bytes=0 Bytes/sec=0
>> FDSocket closed
>> Backup Job Ngorongoro.2006-12-28_21.00.02 waiting for Client connection.
>> Incremental Backup job Ngorongoro JobId=566 Volume=""
>> pool="PoolIncDiskB" device=""FileStorageDiskB" (/var/spool/bacula2)"
>> Files=0 Bytes=0 Bytes/sec=0
>> FDSocket closed
>
>
> Why are these two still listed as running? BackupCatalog shouldn't start
> until these have finished.
That's a good question!
This backup scheme works fine when the ngorongoro machine is powered on.
All the backup jobs run in order, and then the catalog backup runs last.
The problems only arise when ngorongoro (a Windows XP client) is powered
down at the time bacula runs.
> Can the clients see the -sd port on the -sd machine?
> Do the configured passwords match?
> Why do these 2 jobs have null volumes?
They don't when ngorongoro is powered on. Could it be that bacula's
autolabelling has a bug and that it only gets properly triggered when
the client file daemon connects back to the storage daemon. Since this
never happens, the storage daemon gets "left in limbo"?
> Try mounting them and see if that fixes it.
Sorry to be silly, but what command should I use and when? i.e. should I
mount the volume before the backup, or before the catalog job is
scheduled to run, or should I wait until things have got stuck?
Chris.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
