[pkg-bacula-devel] Status/The database update

Carsten Leonhardt leo at debian.org
Thu Feb 22 13:45:15 GMT 2024


Sven Hartge <sven at svenhartge.de> writes:

> On 08.02.24 15:37, Carsten Leonhardt wrote:
>
>> I upgraded another installation.
>
> I upgraded my main-work installation.
>
> The File table contains ~1 billion entries and the whole migration
> took about 27 hours with a peak at 600GB, settling down to 350GB in
> the end.
>
> I needed to move the database directory for MariaDB over to our Netapp
> AFF400 (luckily my DB server has dual 10G NICs) to have enough space
> for this, as the server itself only has 440GiB for /var/lib/mysql.

Hm, when I did my last upgrade to v13 I actually forgot about the space
requirements, but it went through anyway. I wonder if we should have
some fat in-your-face warning before the actual upgrade starts, maybe
with debconf. Like when you want to remove your currently running linux
kernel.

> I had one error during the upgrade:
>
> mysql said: ERROR 1060 (42S21) at line 1: Duplicate column name
> FileMediaId'
>
> That is from the 13.0.0 upgrade file, but the rest of the changes went
> in without a problem, I manually checked. And this error was also
> inconsequential because the added column was already exactly in the
> format it would have been added.

That's really strange, because I don't find any mention of FileMediaId
before our 13.x release.

git log -SFileMediaId

I suppose the update didn't abort?

- Carsten



More information about the pkg-bacula-devel mailing list