Bacula-users

Re: [Bacula-users] "column "volabytes" does not exist"

2015-10-15 13:22:32
Subject: Re: [Bacula-users] "column "volabytes" does not exist"
From: Doug Sampson <dougs AT dawnsign DOT com>
To: 'Phil Stracchino' <phils AT caerllewys DOT net>, "bacula-users AT lists.sourceforge DOT net" <bacula-users AT lists.sourceforge DOT net>
Date: Thu, 15 Oct 2015 17:21:04 +0000
> >> You could manually revert the version table in the DB to the previous
> >> version, run the update script again, and record the errors this time.
> >
> > How does one accomplish this? Is there a secret trick to revise the
> version?
> 
> This query should do it, assuming your Bacula schema is named 'bacula'
> and you haven't skipped any intervening DB versions before the current 15:
> 
> update bacula.Version set VersionId = 14;

Forgive my ignorance but at this point, I am unsure which choice to choose:


*update bacula.Version set VersionId = 14;
Automatically selected Catalog: MyCatalog
Using Catalog "MyCatalog"
Update choice:
     1: Volume parameters
     2: Pool from resource
     3: Slots from autochanger
     4: Long term statistics
     5: Snapshot parameters
Choose catalog item to update (1-5):  


#1?

~D

------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users