Re: Japanese Filenames
We also have a similar situation at my company. Since we can not dedicate a server specifically for Japanese files, we did set up a specific directory on one of the servers for the Japanese. This directory is then zipped and the zipped file is backed up during our normal processing. Andrew Webster [EMAIL PROTECTED]@VM.MARIST.EDU on 05/14/2001 11:03:14 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Japanese Filenames Hi Paul, Has any body had any experience of this in this type of environment? Unfortunately YES. USEUNICODEFILENAMES NO (The Default) TSM won't backup Japanese filenames unless you run the client on a Japanese NT server. Adding the Japanese codepage to a UK build won't work. USEUNICODEFILENAMES YES TSM will backup Japanese filenames most of the time, but occassionally dies a horrible death on certain filenames. With lots of people with lots of Japanese filenames, the client will fail more than it suceeeds. USEUNICODEFILENAMES is suppose to be used with Macintosh files, any other use is convenently unsupported by Tivoli. You need to do your restores, with the same USEUNICODEFILENAMES setting that was done with the Backup. As you've found. Under Japanese NT, all filenames with show up in Japanese characters in GUI. The same can't be said about the WEB GUI. Tivoli support (especially, the Japanese end) are no help whatsoever. As a company, Tivoli seem to have no concept that people do business in multiple languages, and as a backup product Tivoli need to support it. Recents failures, where the NT server product failed as soon as you run it under Japanese, German etc.. bears testiment to the fact, Tivoli aren't even testing their products under different languages. I'll get off my soap box now The only way out of it, is to build a dedicated Japanese NT server, and back everything up remotely with multiple schedules. The one I set up Tokyo was running 12 backup schedules (that 12 NT services). You need a big box though, preferable with GigE links to whatever you are going to backup. CPU power is also an issue, I had to upgrade from a Dual to a Quad processor to get the backups completed overnight. You'll also have to do your restores from there as well, so need a Remote Console/Control utility to get to the box and not many of them will let you control a Japanese PC from an English workstation. Regards Andrew Webster TSM/Storage Consultant Deutsche Bank, Australia Office : +61 3 9270-4229 Mobile : +61 (0) 40999 6515 Fax: +61 3 9270-4144 E-Mail : [EMAIL PROTECTED] paul.bestow@pho enixsm.com To: [EMAIL PROTECTED] cc: 14/05/2001 Subject: Japanese Filenames 11:32 PM Please respond to ADSM-L Hi all, We are running an NT environment using version 4 TSM client and server code to back up all our data. On our file and print server we have a lots of Japanese filenames. We have installed our NT servers as UK operating systems, but have installed the Japanese code page to facilitate the use of Japanese filenames. When we use TSM gui to back up these filenames they are displayed as invalid files. We have tried turning on USEUNICODEFILENAMES in the client option file, and all these seems to do is instead of the filenames being invalid they appear as question marks. Has any body had any experience of this in this type of environment? http://www.phoenixitgroup.com **Internet Email Confidentiality Footer*** Phoenix IT Group Limited is registered in England and Wales under company number 3476115. Registered Office: Technology House, Hunsbury Hill Avenue, Northampton, NN4 8QS Opinions, conclusions and other information in this message that do not relate to the official business of our firm shall be understood as neither given nor endorsed by it. No contracts may be concluded on behalf of our firm by means of email communications. Confidentiality: Confidential information may be contained in this message. If you are not the recipient indicated (or responsible for delivery of the message to such person), you may not take any action based on it, nor should you copy or show this to anyone; please reply to this email and highlight the error to the sender, then delete the message from your system. Monitoring of Messages: Please note that we reserve the right to monitor and intercept emails sent and received on our network. Warning: Internet email is not 100% secure. We ask you to understand and observe this lack of security when emailing us. We do not accept responsibility for changes made to this message after it was sent Viruses: Although we have taken steps to ensure that this email and any attachments are free from any virus
Re: Japanese Filenames
We also have a large number of Japanese users to manage. Unfortunatly we have Japanese English files scattered over our file servers which run on English NT Servers. We then have another Japanese NT Box that runs our TSM client. This Japanese Client Nt connects to numerous NT Shares on the file servers for backup archive. This tends to work well for us. The biggest problem I have is that the error schedule logs are also written in Japanese so I can't understand a word they say ! regards, Nick. MIKE HANLEY [EMAIL PROTECTED] on 15/05/2001 13:23:54 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Nick Rutherford/HUM/EU/HONDA) Subject: Re: Japanese Filenames We also have a similar situation at my company. Since we can not dedicate a server specifically for Japanese files, we did set up a specific directory on one of the servers for the Japanese. This directory is then zipped and the zipped file is backed up during our normal processing. Andrew Webster [EMAIL PROTECTED]@VM.MARIST.EDU on 05/14/2001 11:03:14 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Japanese Filenames Hi Paul, Has any body had any experience of this in this type of environment? Unfortunately YES. USEUNICODEFILENAMES NO (The Default) TSM won't backup Japanese filenames unless you run the client on a Japanese NT server. Adding the Japanese codepage to a UK build won't work. USEUNICODEFILENAMES YES TSM will backup Japanese filenames most of the time, but occassionally dies a horrible death on certain filenames. With lots of people with lots of Japanese filenames, the client will fail more than it suceeeds. USEUNICODEFILENAMES is suppose to be used with Macintosh files, any other use is convenently unsupported by Tivoli. You need to do your restores, with the same USEUNICODEFILENAMES setting that was done with the Backup. As you've found. Under Japanese NT, all filenames with show up in Japanese characters in GUI. The same can't be said about the WEB GUI. Tivoli support (especially, the Japanese end) are no help whatsoever. As a company, Tivoli seem to have no concept that people do business in multiple languages, and as a backup product Tivoli need to support it. Recents failures, where the NT server product failed as soon as you run it under Japanese, German etc.. bears testiment to the fact, Tivoli aren't even testing their products under different languages. I'll get off my soap box now The only way out of it, is to build a dedicated Japanese NT server, and back everything up remotely with multiple schedules. The one I set up Tokyo was running 12 backup schedules (that 12 NT services). You need a big box though, preferable with GigE links to whatever you are going to backup. CPU power is also an issue, I had to upgrade from a Dual to a Quad processor to get the backups completed overnight. You'll also have to do your restores from there as well, so need a Remote Console/Control utility to get to the box and not many of them will let you control a Japanese PC from an English workstation. Regards Andrew Webster TSM/Storage Consultant Deutsche Bank, Australia Office : +61 3 9270-4229 Mobile : +61 (0) 40999 6515 Fax: +61 3 9270-4144 E-Mail : [EMAIL PROTECTED] paul.bestow@pho enixsm.com To: [EMAIL PROTECTED] cc: 14/05/2001 Subject: Japanese Filenames 11:32 PM Please respond to ADSM-L Hi all, We are running an NT environment using version 4 TSM client and server code to back up all our data. On our file and print server we have a lots of Japanese filenames. We have installed our NT servers as UK operating systems, but have installed the Japanese code page to facilitate the use of Japanese filenames. When we use TSM gui to back up these filenames they are displayed as invalid files. We have tried turning on USEUNICODEFILENAMES in the client option file, and all these seems to do is instead of the filenames being invalid they appear as question marks. Has any body had any experience of this in this type of environment? http://www.phoenixitgroup.com **Internet Email Confidentiality Footer*** Phoenix IT Group Limited is registered in England and Wales under company number 3476115. Registered Office: Technology House, Hunsbury Hill Avenue, Northampton, NN4 8QS Opinions, conclusions and other information in this message that do not relate to the official business of our firm shall be understood as neither given nor endorsed by it. No contracts may be concluded on behalf of our firm by means of email communications. Confidentiality: Confidential information may be contained
Re: Japanese Filenames
USEUNICODEFILENAMES NO (The Default) TSM won't backup Japanese filenames unless you run the client on a Japanese NT server. Adding the Japanese codepage to a UK build won't work. USEUNICODEFILENAMES YES TSM will backup Japanese filenames most of the time, but occassionally dies a horrible death on certain filenames. With lots of people with lots of Japanese filenames, the client will fail more than it suceeeds. USEUNICODEFILENAMES is suppose to be used with Macintosh files, any other use is convenently unsupported by Tivoli. This is not a matter of convenience. USEUNICODEFILENAMES was *never* intended to provide the support you are seeking. It's purpose is strictly for support of Macintosh volumes on NTFS file systems (granted, though, the option would have been better named ENABLEMACFILESUPPORT, or something along those lines). Tivoli support (especially, the Japanese end) are no help whatsoever. As a company, Tivoli seem to have no concept that people do business in multiple languages, and as a backup product Tivoli need to support it. Recents failures, where the NT server product failed as soon as you run it under Japanese, German etc.. bears testiment to the fact, Tivoli aren't even testing their products under different languages. IBM/Tivoli fully understands the need for a global perspective, as we are a global company doing business all over the world. Please do not equate language support issues with have no concept that people do business in multiple languages. This is just not true. Agreed, the recent problems we have had with non-English character sets do not instill the greatest confidence in our NLS support. However, we do in fact have a large number of resources dedicated to NLS support, translation, and testing, and we are continuously working to improve our processes to (among other things) eliminate the kinds of problems you mention. Yes, we have stumbled in this arena, especially recently, but we have also made every effort to respond to the problems in as timely a fashion as possible, because we *do* understand the need for this support. Regarding support for file names comprised of characters from different character sets (i.e. Japanese file names on English systems), this is a long-standing requirement. It isn't here yet because we are ignoring it; rather, the implementation is not trivial. But it is something that we are actively working on and hope to deliver this year. (Standard caveat: this does not constitute a formal announcement or commitment.) Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend
Re: Japanese Filenames
Andy, Taking all you say into consideration, and fully understanding how hard it is to do what we are asking (which in my opinion should have been a major concern before shipping, and not afterwards), I am still unsatisfied. I am not going to bash one software against another, but with all due respect, if you do not support multilingual on English based systems, and some other OS's (such as Netware), then you should state so in letters as large as a 2 story building on the product casing. It's rather not fun in the least, to discover that one can't backup languages on OS's (NT, Novell) after having bought and installed the product. And this after moving from backup software that did just that and didn't blink an eye. I am very glad you have so many resources dedicated to NLS support, but I at least don't care if you have 1000 people working on the issue, I care that it is fixed and fixed FAST. And I am extremely glad that you have learnt to be politicaly correct and state that it's important to you, you'r working on it, and it may be here soon (no guarantees of course). Dissapointed, Mike Glassman Systems Security Admin Israel Airport Authority -Original Message- From: Andy Raibeck [SMTP:[EMAIL PROTECTED]] Sent: â îàé 15 2001 16:27 To: [EMAIL PROTECTED] Subject: Re: Japanese Filenames USEUNICODEFILENAMES NO (The Default) TSM won't backup Japanese filenames unless you run the client on a Japanese NT server. Adding the Japanese codepage to a UK build won't work. USEUNICODEFILENAMES YES TSM will backup Japanese filenames most of the time, but occassionally dies a horrible death on certain filenames. With lots of people with lots of Japanese filenames, the client will fail more than it suceeeds. USEUNICODEFILENAMES is suppose to be used with Macintosh files, any other use is convenently unsupported by Tivoli. This is not a matter of convenience. USEUNICODEFILENAMES was *never* intended to provide the support you are seeking. It's purpose is strictly for support of Macintosh volumes on NTFS file systems (granted, though, the option would have been better named ENABLEMACFILESUPPORT, or something along those lines). Tivoli support (especially, the Japanese end) are no help whatsoever. As a company, Tivoli seem to have no concept that people do business in multiple languages, and as a backup product Tivoli need to support it. Recents failures, where the NT server product failed as soon as you run it under Japanese, German etc.. bears testiment to the fact, Tivoli aren't even testing their products under different languages. IBM/Tivoli fully understands the need for a global perspective, as we are a global company doing business all over the world. Please do not equate language support issues with have no concept that people do business in multiple languages. This is just not true. Agreed, the recent problems we have had with non-English character sets do not instill the greatest confidence in our NLS support. However, we do in fact have a large number of resources dedicated to NLS support, translation, and testing, and we are continuously working to improve our processes to (among other things) eliminate the kinds of problems you mention. Yes, we have stumbled in this arena, especially recently, but we have also made every effort to respond to the problems in as timely a fashion as possible, because we *do* understand the need for this support. Regarding support for file names comprised of characters from different character sets (i.e. Japanese file names on English systems), this is a long-standing requirement. It isn't here yet because we are ignoring it; rather, the implementation is not trivial. But it is something that we are actively working on and hope to deliver this year. (Standard caveat: this does not constitute a formal announcement or commitment.) Regards, Andy Andy Raibeck IBM Tivoli Systems Tivoli Storage Manager Client Development e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend
Japanese Filenames
Hi all, We are running an NT environment using version 4 TSM client and server code to back up all our data. On our file and print server we have a lots of Japanese filenames. We have installed our NT servers as UK operating systems, but have installed the Japanese code page to facilitate the use of Japanese filenames. When we use TSM gui to back up these filenames they are displayed as invalid files. We have tried turning on USEUNICODEFILENAMES in the client option file, and all these seems to do is instead of the filenames being invalid they appear as question marks. Has any body had any experience of this in this type of environment? http://www.phoenixitgroup.com **Internet Email Confidentiality Footer*** Phoenix IT Group Limited is registered in England and Wales under company number 3476115. Registered Office: Technology House, Hunsbury Hill Avenue, Northampton, NN4 8QS Opinions, conclusions and other information in this message that do not relate to the official business of our firm shall be understood as neither given nor endorsed by it. No contracts may be concluded on behalf of our firm by means of email communications. Confidentiality: Confidential information may be contained in this message. If you are not the recipient indicated (or responsible for delivery of the message to such person), you may not take any action based on it, nor should you copy or show this to anyone; please reply to this email and highlight the error to the sender, then delete the message from your system. Monitoring of Messages: Please note that we reserve the right to monitor and intercept emails sent and received on our network. Warning: Internet email is not 100% secure. We ask you to understand and observe this lack of security when emailing us. We do not accept responsibility for changes made to this message after it was sent Viruses: Although we have taken steps to ensure that this email and any attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free.
Re: Japanese Filenames
Hi Paul, Has any body had any experience of this in this type of environment? Unfortunately YES. USEUNICODEFILENAMES NO (The Default) TSM won't backup Japanese filenames unless you run the client on a Japanese NT server. Adding the Japanese codepage to a UK build won't work. USEUNICODEFILENAMES YES TSM will backup Japanese filenames most of the time, but occassionally dies a horrible death on certain filenames. With lots of people with lots of Japanese filenames, the client will fail more than it suceeeds. USEUNICODEFILENAMES is suppose to be used with Macintosh files, any other use is convenently unsupported by Tivoli. You need to do your restores, with the same USEUNICODEFILENAMES setting that was done with the Backup. As you've found. Under Japanese NT, all filenames with show up in Japanese characters in GUI. The same can't be said about the WEB GUI. Tivoli support (especially, the Japanese end) are no help whatsoever. As a company, Tivoli seem to have no concept that people do business in multiple languages, and as a backup product Tivoli need to support it. Recents failures, where the NT server product failed as soon as you run it under Japanese, German etc.. bears testiment to the fact, Tivoli aren't even testing their products under different languages. I'll get off my soap box now The only way out of it, is to build a dedicated Japanese NT server, and back everything up remotely with multiple schedules. The one I set up Tokyo was running 12 backup schedules (that 12 NT services). You need a big box though, preferable with GigE links to whatever you are going to backup. CPU power is also an issue, I had to upgrade from a Dual to a Quad processor to get the backups completed overnight. You'll also have to do your restores from there as well, so need a Remote Console/Control utility to get to the box and not many of them will let you control a Japanese PC from an English workstation. Regards Andrew Webster TSM/Storage Consultant Deutsche Bank, Australia Office : +61 3 9270-4229 Mobile : +61 (0) 40999 6515 Fax: +61 3 9270-4144 E-Mail : [EMAIL PROTECTED] paul.bestow@pho enixsm.com To: [EMAIL PROTECTED] cc: 14/05/2001 Subject: Japanese Filenames 11:32 PM Please respond to ADSM-L Hi all, We are running an NT environment using version 4 TSM client and server code to back up all our data. On our file and print server we have a lots of Japanese filenames. We have installed our NT servers as UK operating systems, but have installed the Japanese code page to facilitate the use of Japanese filenames. When we use TSM gui to back up these filenames they are displayed as invalid files. We have tried turning on USEUNICODEFILENAMES in the client option file, and all these seems to do is instead of the filenames being invalid they appear as question marks. Has any body had any experience of this in this type of environment? http://www.phoenixitgroup.com **Internet Email Confidentiality Footer*** Phoenix IT Group Limited is registered in England and Wales under company number 3476115. Registered Office: Technology House, Hunsbury Hill Avenue, Northampton, NN4 8QS Opinions, conclusions and other information in this message that do not relate to the official business of our firm shall be understood as neither given nor endorsed by it. No contracts may be concluded on behalf of our firm by means of email communications. Confidentiality: Confidential information may be contained in this message. If you are not the recipient indicated (or responsible for delivery of the message to such person), you may not take any action based on it, nor should you copy or show this to anyone; please reply to this email and highlight the error to the sender, then delete the message from your system. Monitoring of Messages: Please note that we reserve the right to monitor and intercept emails sent and received on our network. Warning: Internet email is not 100% secure. We ask you to understand and observe this lack of security when emailing us. We do not accept responsibility for changes made to this message after it was sent Viruses: Although we have taken steps to ensure that this email and any attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
