Hello Harmeet Thanks for the prompt response.
I tried that on a test volume with odd chars in the filenames - and it works! I changed from "en" to "en.UTF-8". Oddly enough though the bit after the . is supposed to refer to NFS. Anyway, thanks again, much appreciated! Thanks Steven On 7 February 2011 01:33, Harmeet Sian <[email protected]> wrote: > Hi Steven, > > I had a similar issue with one of our clients. > > " Observed in dsmerror.log > 06-09-2010 09:39:17 ANS1626E An unexpected error was encountered when > processing a TSM operation using a hardware or snapshot function. > TSM function name : NAHWInterface::naPerformSnapDiff > TSM function : Error invoking ONTAP API snapdiff-iter-next: > Parsing error in results: Input is not proper UTF-8, indicate encoding ! > Bytes: 0xA0 0x2F 0x43 0x61 > TSM return code : 13001 > TSM file : NAHWInterface.cpp (6781) > 06-09-2010 09:39:17 ANS5250E An unexpected error was encountered. > TSM function name : baPerformSnapDiff > TSM function : failed to perform snapdiff > TSM return code : 653 > TSM file : backsnap.cpp (4786) > 06-09-2010 09:39:17 ANS2832E Incremental by snapshot difference failed for > \\10.0.5.152\student. Please see error log for details. > 06-09-2010 09:39:19 ANS5283E The operation was unsuccessful. " > > Here is IBM's response. > > "Based on these details and additional information that IBM SW Support has > access to, we suggest you have encountered a unicode issue. > The On-Tap API doesn't seem to support extended ASCII alphabet, however IBM > suggests you confirm that with Net-App (?) N-Series support. > We suggest you may need to add the following to the volume via the On-Tap > command line option: > > "Vol lang en_US.UTF-8" needs to be added to the volume. > > We understand that it does require a reboot for the option to take effect. > IBM suggests you may need to confirm this with NetApp. > > Please let us know how you go with this suggestion. > > Regards, > > Tivoli Support Team > IBM Support Center" > > > Ended up working for me. 1 year of happy backups from N3600 to TSM :) > > > > Harmeet Sian > Senior Systems Engineer > the missing link network integration pty ltd > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of > Steven Langdale > Sent: Sunday, 6 February 2011 9:52 PM > To: [email protected] > Subject: [ADSM-L] Snapdiff backups of filers - Getting errors > > Hello all. > > I'm attempting to do snapdiff backups on an N series we have here. > > TSM Server: 5.5.3 > TSM Client: 6.2.2.0 > Wwindows Proxy: 2003 SP2 + pretty recent patches. > > Snapdiffs on my 2 test voulmes work perfectly (after having to do a net use > to them as a pre-exec), but larger volumes with much more data are failing > with this (the ?'s are mine): > > 02/06/2011 09:05:10 ANS1626E An unexpected error was encountered when > processing a TSM operation using a hardware or snapshot function. > TSM function name : NAHWInterface::naPerformSnapDiff > TSM function : Error invoking ONTAP API snapdiff-iter-next: Parsing > error in results: Input is not proper UTF-8, indicate encoding ! > Bytes: 0xB4 0x73 0x20 0x47 > > TSM return code : 13001 > TSM file : NAHWInterface.cpp (6777) > 02/06/2011 09:05:10 ANS5250E An unexpected error was encountered. > TSM function name : baPerformSnapDiff > TSM function : failed to perform snapdiff > TSM return code : 653 > TSM file : backsnap.cpp (5173) > 02/06/2011 09:05:10 ANS2832E Incremental by snapshot difference failed for > \\???????\vol01$. Please see error log for details. > 02/06/2011 09:05:12 ANS5283E The operation was unsuccessful. > > I've tried both of the testflags that have come up in my hunting about : > > TESTFLAG SNAPDIFFNAMEFILTEROFF > TESTFLAG SNAPDIFFONTAPFAP > > But still no joy. IBM article > http://www-01.ibm.com/support/docview.wss?uid=swg21408335 is saying this > is a NETAPP issue and there is no workaroud but people who are using the > testflags seem to be getting successful backups. > > Has anyone actually got this to work reliably? > > Many thanks > > Steven > > ______________________________________________________________________ > This email has been scanned by The Missing Link's Email Security System - > Powered by MessageLabs. For more information please email > [email protected]______________________________________________________________________ > > CAUTION - This message may contain privileged and confidential information > intended only for the use of the addressee named above. If you are not the > intended recipient of this message you are hereby notified that any use, > dissemination, distribution or reproduction of this message is prohibited. > If you have received this message in error please notify The Missing Link > immediately. Any views expressed in this message are those of the individual > sender and may not necessarily reflect the views of The Missing Link. >
