On Wednesday 07 November 2012 16:38:13 Simone Caronni wrote:
On 7 November 2012 17:24, John Drescher dresche...@gmail.com 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
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
to update the
database to the correct schema version.
- Original Message -
From: Gary Stainburn g...@ringways.co.uk
To: bacula-users Bacula-users@lists.sourceforge.net
Sent: Wednesday, November 7, 2012 8:51:30 AM
Subject: [Bacula-users] Restoring the catalog database - F14 to F17
As part
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
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.
On 7 November 2012 17:24, John Drescher dresche...@gmail.com 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
