Bacula-users

[Bacula-users] upgrade 2.0.3 > 2.4.4

2009-02-12 12:05:34
Subject: [Bacula-users] upgrade 2.0.3 > 2.4.4
From: François Mehault <Francois.Mehault AT netplus DOT fr>
To: "bacula-users AT lists.sourceforge DOT net" <bacula-users AT lists.sourceforge DOT net>
Date: Thu, 12 Feb 2009 17:59:04 +0100

Hi All !

 

I want to upgrade my Bacula (currently in v 2.0.3) in 2.4.4. So, I install the Bacula v 2.4.4 on another OS just to see the difference.

Then I realized a dump of the catalogue database in my Bacula v 2.0.3 and 2.4.4 to compare. I did a diff on my two dump and there is one thing which is strange

 

 

Bacula 2.0.3

 

 

DROP TABLE IF EXISTS `File`;

CREATE TABLE `File` (

  `FileId` int(10) unsigned NOT NULL auto_increment,

  `FileIndex` int(10) unsigned default '0',

  `JobId` int(10) unsigned NOT NULL,

  `PathId` int(10) unsigned NOT NULL,

  `FilenameId` int(10) unsigned NOT NULL,

  `MarkId` int(10) unsigned default '0',

  `LStat` tinyblob NOT NULL,

  `MD5` tinyblob,

  PRIMARY KEY  (`FileId`),

  KEY `JobId` (`JobId`),

  KEY `JobId_2` (`JobId`,`PathId`,`FilenameId`)

) ENGINE=MyISAM AUTO_INCREMENT=785251836 DEFAULT CHARSET=latin1;

 

 

 

Bacula 2.4.4

 

 

 

DROP TABLE IF EXISTS `File`;

SET @saved_cs_client     = @@character_set_client;

SET character_set_client = utf8;

CREATE TABLE `File` (

  `FileId` int(10) unsigned NOT NULL auto_increment,

  `FileIndex` int(10) unsigned default '0',

  `JobId` int(10) unsigned NOT NULL,

  `PathId` int(10) unsigned NOT NULL,

  `FilenameId` int(10) unsigned NOT NULL,

  `MarkId` int(10) unsigned default '0',

  `LStat` tinyblob NOT NULL,

  `MD5` tinyblob,

  PRIMARY KEY  (`FileId`),

  KEY `JobId` (`JobId`,`PathId`,`FilenameId`)

) ENGINE=MyISAM AUTO_INCREMENT=199415 DEFAULT CHARSET=latin1;

SET character_set_client = @saved_cs_client;

 

 

More precisely:

 

Bacula 2.0.3

 

PRIMARY KEY  (`FileId`),

  KEY `JobId` (`JobId`),

  KEY `JobId_2` (`JobId`,`PathId`,`FilenameId`)

 

 

Bacula 2.4.4

 

PRIMARY KEY  (`FileId`),

  KEY `JobId` (`JobId`,`PathId`,`FilenameId`)

 

 

The two Bacula are on FreeBSD 7, for each I look in

 

/usr/ports/sysutils/bacula-server/work/bacula-2.0.3/updatedb

 

And

 

/usr/ports/sysutils/bacula-server/work/bacula-2.4.4/updatedb

 

 

For the first, about mysql I can see:

 

-rwxr-xr-x  1 root  wheel   3.2K Nov  3  2005 update_mysql_tables_8_to_9

 

And for the second

 

-rwxr-xr-x  1 root  wheel   2.4K Apr  1  2007 update_mysql_tables_9_to_10

 

I opened update_mysql_tables_9_to_10 and can read

 

echo "This script will update a Bacula MySQL database from version 9 to 10"

echo " which is needed to convert from Bacula version 1.38.x to 2.0.x or higher"

echo "Depending on the size of your database,"

echo "this script may take several minutes to run."

 

So I conclude I don’t need to execute any script to upgrade my catalogue database to pass in 2.4.4, but there is the first thing that I find strange :s

 

It could raise problem?

 

Thanks

 

François

 

 

 

 

 

 

 

 

 

------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Bacula-users] upgrade 2.0.3 > 2.4.4, François Mehault <=