Hi to all: I've the bacula catalog under Postgresql and the database was created with UTF8 encoding. Now, trying to protect one 'old' client ( REDHAT 3 ) I get errors from backup job - better said, the errors are raised in the database - claiming for some characters not valid fro UTF8 encoding, example
" Fatal error: sql_create.c:845 sql_create.c:845 query SELECT FilenameId FROM Filename WHERE Name='Nenúfares.jpg' failed: " IIUC, here I have three possible ways taking in mind that the environment to protect could include UTF8 clients, ISO-8859-1, Windows machines -By now I don't know default enconding, etc... 1.- Recreate catalog using SQL_ASCII ( the environment to protect could include UTF8 clients, ISO-8859-1, Windows machines -By now I don't know default enconding, etc... ) 2.- May be, forcing character set in the bacula-fd client processes I get at least a 'buggy chars' but storable in the database ( ? ) ( This can be accomplished in Oracle at the risk of lose this characters if you export/import data ) 3.- Touch database config to force character set from UTF8 to SQL_ASCII, but I don't know how Postgresql stores characters and then, I've no knowledge about implications of this movement. Based in your experience, and if you have get this issue before, what should be the correct way? If you know more ways info is wellcome, of course. Best Regards D. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
