> On Wed, 24 Oct 2012 00:27:59 -0700, trexman said:
>
> Ok, here is the log output:
>
> 28-Okt 23:56 uxepv21-dir JobId 618: Created new Volume "Voltestjob-Diff-3722"
> in catalog.
> 28-Okt 23:56 uxepv21-dir JobId 618: Using Device "testjob"
> 23-Okt 03:42 uxepv21-fd JobId 618: Warning: DIR
On 7 November 2012 17:24, John Drescher wrote:
> I would restore the old database from a sql dump then run the upgrade
> scripts to fix the version problem.
>
Exactly. What you are doing (going from a 5.0.3 director to a 5.2.11
director) is not a restore of the old server, but an upgrade.
You s
btw, the File Daemon should have the following as the working directory in
/etc/bacula/bacula-fd.conf
FileDaemon {
WorkingDirectory = /var/spool/bacula
}
Regards,
--Simone
On 7 November 2012 17:34, Simone Caronni wrote:
> Hello,
>
> I'm the current mantainer of Bacula in Fedora, I stepped i
Hello,
I'm the current mantainer of Bacula in Fedora, I stepped in as a mantainer
during the Fedora 15 cycle. One of the first thing I did was close all the
old bugs, including the one you mention.
I don't have the symptoms you describe.
The log file should be created automatically; and I don't h
> By ignoring the old catalog and just creating a new installation I can get the
> director working. The message does indeed refer to differences in catalog
> database versions.
>
> However, I need to import the old catalog into the new server. Can anyone
> point me in the right direction please.
>
By ignoring the old catalog and just creating a new installation I can get the
director working. The message does indeed refer to differences in catalog
database versions.
However, I need to import the old catalog into the new server. Can anyone
point me in the right direction please.
(Sorry i
On 11/6/2012 6:36 PM, Stephen Thompson wrote:
>
> A quick test of this scenario seems to work.
> Leaving "Prefer Mounted Volumes = yes" (default).
> Setting both drives in autochanger to have 1/2 of the the total
> concurrently limit. This per device setting seems to allow for multiple
> drives u
I believe that is letting you know the database schema is not at the correct
version. So in the process of moving to F17 you probably went to a newer
version of bacula if installing from repositories. In the /etc/bacula folder
there should be a update_bacula_tables script you can run to update
Zitat von Sven Tegethoff :
>> * This means that I've 4 volumes damaged? I tried this night with a
>> new volume and the backup finished correctly.
>
> All the logs tell us is that the tape drive could not write to the tape
> - without further investigation, it's impossible to say whether the
>
As part of trying to build my new server I've taken the pg_dump output from
the old server and used that to build thedatabase on the new server. However
I get the following log entries.
Can someone point me to the correct process for importing data.
ta
07-Nov 15:42 bacula-dir JobId 0: Fatal er
> * This means that I've 4 volumes damaged? I tried this night with a
> new volume and the backup finished correctly.
All the logs tell us is that the tape drive could not write to the tape
- without further investigation, it's impossible to say whether the
tapes are at fault, the tape drive i
On Wednesday 07 November 2012 12:51:35 Felix Schwarz wrote:
> Hi Gary,
>
> PostgreSQL is supported. The README.Fedora file in
> /usr/share/doc/bacula-common-5.2.11/ contains all the details.
>
> fs
>
Thanks for this Felix.
I've worked through it, including restoring the backup from the old server,
I need some help,
I 've 5 volumes in a Daily pool
Pool {
Name = Daily
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 5 days
Maximum Volume Bytes = 800G
Volume Use Duration = 23h
Maximum Volumes = 5
}
so I can do everyday for 5 days a backup and this has worke
Hi Gary,
PostgreSQL is supported. The README.Fedora file in
/usr/share/doc/bacula-common-5.2.11/ contains all the details.
fs
--
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, upda
Hi folks.
I'm just replacing my old Fedora 14 based director / storage server with a
Fedora 17 due to the HDD failing.
However, a yum search bacula shows that the RPM's have changed. I no longer
see ones configured for Postgresql. Are they no longer required or is
Postgresql no longer supporte
On Tue, Nov 06, 2012 at 04:15:18PM +0100, lst_ho...@kwsoft.de wrote:
>
> from my knowledge the jobs are created but take on hold as long as
> other jobs with different priority are running. So it looks like the
> catalog connections are established as part of the job creation. That
> said yo
16 matches
Mail list logo
