Hey, all. Is there ever a situation where the File.FileIndex (in MySQL schema v16, at least), will have a negative value? If so, what exactly does the negative value mean?
I'm in the process of migrating my director and database from Bacula v9.4.3 with MySQL 5.1 (I know, it's ancient), to a new host with Bacula v9.6.6 with MariaDB 10.1. Due to a bit of weirdness in my long-past upgrade from bacula's MySQL schema v14 to v16, I apparently messed up and didn't get File.FileIndex converted from an "int unsigned" to "int" (default signed). So, if I import using a mysqldump that includes the "create table" statements, and end up with an unsigned int, my bacula 9.6.6 host throws an "Out of range value for column 'FileIndex'" error when it copies from the 'batch' temporary table into 'File'. From what I can see, some of the FileIndex values in the 'batch' temp table, are negative. Obviously I can fix the schema, and it will be able to handle negative numbers going forward. I was just trying to figure out if that was the right thing to do. It seems like FileIndex is supposed to be used as the order of the files backed up within a job (eg. first file in the job is "1", second file is "2", and so on), which makes negative numbers seem like they either have some special meaning, or there is something else broken here. Thanks, Lloyd -- Lloyd Brown HPC Systems Administrator Office of Research Computing Brigham Young University http://marylou.byu.edu _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
