Hello Dan,
The encoding that Unix/Linux/Bacula uses is not ASCII but UTF-8, so from the
PostgreSQL document, it appears that what you really want is to set the
character encoding to "UNICODE" (a bit of a pity that they do not
distinguish as there are a number of different forms of Unicode).
On Wednesday 26 October 2005 06:02, Dan Langille wrote:
> On 25 Oct 2005 at 15:04, Kern Sibbald wrote:
> > On Tuesday 25 October 2005 14:40, Michael Galloway wrote:
> > > good day all ...
> > >
> > > i'm still having problems with unicode sequences in filenames. for
> > > example:
> > >
> > > 24-Oct 16:02 lance-dir: Start Backup JobId 16,
> > > Job=AspenHome.2005-10-24_16.02.48 24-Oct 16:02 lance-dir: Recycled
> > > volume "AspenHome-0001"
> > > 24-Oct 16:06 lance-sd: Recycled volume "AspenHome-0001" on device
> > > "AspenHomeFileStorage" (/backups/aspen/home), +all previous data lost.
> > > 24-Oct 17:31 lance-dir: AspenHome.2005-10-24_16.02.48 Fatal error:
> > > sql_create.c:826 sql_create.c:826 query SELECT +FilenameId FROM
> > > Filename WHERE Name='About EuG?ne.doc' failed:
> > > ERROR: invalid byte sequence for encoding "UNICODE": 0xe86e65
> > >
> > > 24-Oct 17:31 lance-dir: sql_create.c:826 SELECT FilenameId FROM
> > > Filename WHERE Name='About EuG?ne.doc' 24-Oct 17:31 lance-dir:
> > > AspenHome.2005-10-24_16.02.48 Fatal error: sql_create.c:851
> > > sql_create.c:851 insert INSERT+INTO Filename (Name) VALUES ('About
> > > EuG?ne.doc') failed: ERROR: invalid byte sequence for encoding
> > > "UNICODE": 0xe86e65
> > >
> > > 24-Oct 17:31 lance-dir: sql_create.c:851 INSERT INTO Filename (Name)
> > > VALUES ('About EuG?ne.doc') 24-Oct 17:31 lance-dir:
> > > AspenHome.2005-10-24_16.02.48 Fatal error: sql_create.c:853 Create db
> > > Filename record +INSERT INTO Filename (Name) VALUES ('About
> > > EuG?ne.doc') failed. ERR=ERROR: invalid byte sequence for encoding
> > > +"UNICODE": 0xe86e65
> > >
> > > 24-Oct 17:31 lance-dir: AspenHome.2005-10-24_16.02.48 Fatal error:
> > > catreq.c:427 Attribute create error. +sql_create.c:853 Create db
> > > Filename record INSERT INTO Filename (Name) VALUES ('About EuG?ne.doc')
> > > failed. +ERR=ERROR: invalid byte sequence for encoding "UNICODE":
> > > 0xe86e65
> > >
> > >
> > > i appreciate that bacula is not unicode compatible. but is there anyway
> > > to configure bacula to drop/ignore/flag/do something with the unicode
> > > filenames that will let the backup complete? i really have little
> > > control over how users name files in their home directories and it
> > > would be nice if i could get a successful backup of my home directory
> > > filesyste.
> >
> > Hello,
> >
> > Bacula does work with Unicode names. It works in UTF-8 (Unicode), which
> > is what all Unix/Linux machines typically use as a default as well as
> > MySQL and SQLite. I've seen some cases similar to yours on PostgreSQL,
> > where it is apparently using 16 bit Unicode. I suspect you are using
> > PostgreSQL, and if so you need to reconfigure it to use UTF-8. When you
> > figure out how to do so and get it to work, please let me know so that I
> > can add it to the document.
>
> It seems I'm all wrong with respect to my previous message... at
> least as far as testing goes.
>
> Micheal sent me the file name in question. I created the file. And
> backed it up under PostgreSQL 7.4.7 using a database encoding of
> SQL_ASCII. However, I was unable to restore the file. It's there,
> but I can't restore it.
>
> bacula=# select * from filename where name like 'hotel-%';
> filenameid | name
> ------------+----------------------
> 736771 | hotel-Schnbrunn.txt
>
> In my unix shell, the filename looks like this:
>
> hotel-Sch\224nbrunn.txt
>
> When I try to restore it:
>
> $ ls
> hotel-Schnbrunn.txt
> junk.txt
> $ mark ho*
> 1 files marked.
> $ ls
> *hotel-Schnbrunn.txt
> junk.txt
> $ done
>
> But when the job is done:
>
> 25-Oct 23:52 polo-sd: Ready to read from volume "DLT7000-024" on
> device /dev/nsa0.
> 25-Oct 23:52 polo-sd: Forward spacing to file:block 128:0.
> *mes
> 25-Oct 23:53 polo-sd: End of Volume at file 3 on device /dev/nsa0,
> Volume "DLT7000-024"
> 25-Oct 23:53 polo-sd: End of all volumes.
> 25-Oct 23:53 bacula-dir: Bacula 1.36.3 (22Apr05): 25-Oct-2005
> 23:53:18
> JobId: 6250
> Job: RestoreFiles.2005-10-25_23.50.23
> Client: polo-fd
> Start time: 25-Oct-2005 23:50:25
> End time: 25-Oct-2005 23:53:18
> Files Expected: 1
> Files Restored: 0
> Bytes Restored: 0
> Rate: 0.0 KB/s
> FD Errors: 0
> FD termination status: OK
> SD termination status: OK
> Termination: Restore OK -- warning file count mismatch
>
> 25-Oct 23:53 bacula-dir: Begin pruning Jobs.
> 25-Oct 23:53 bacula-dir: Pruned 5 Jobs for client polo-fd from
> catalog.
> 25-Oct 23:53 bacula-dir: Begin pruning Files.
> 25-Oct 23:53 bacula-dir: No Files found to prune.
> 25-Oct 23:53 bacula-dir: End auto prune.
>
> I have no idea why it was not restored.
--
Best regards,
Kern
(">
/\
V_V
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
