Andy (or anyone else from IBM),
We are beginning to realize how big a problem we have with the newest WinNT
client level. Being a University, we have lots of international faculty
and staff and they of course tend to use international characters. We also
have lots of Macs here. I am speaking of the limitation that the ADSM
WinNT client cannot backup both Mac filenames and filenames containing
international characters. I am assuming that you can have international
characters in a Macintosh filename. Is this a correct assumption, or are
international characters in Mac filenames somehow treated differently than
in non-Mac filenames?
First, let me start by urging IBM to correct the NT client to handle this
as quickly as they can. I understand from your notes that this is not a
simple fix, but one that requires some redesign work. Even so, we need
this support in ADSM soonest.
Second, I have some questions about how to do a workaround. Your prior
note indicates that a workaround would be to have two nodenames, one with
USEUNICODE ON and one OFF. I've got some questions about this:
Q1: When restoring a volume, I see no simple way to restore it to a correct
state. Either nodename you use to do a full restore will yield a problem
with filenames having either special Mac chars or international chars (one
or the other). Would it be possible to do the following:
1. Get a list of special Mac characters (and/or international characters),
2. Code Include/Exclude rules so that the second nodename would ONLY back up
files containing those special characters?
This might make it a bit easier to do a full-volume restore. You could
then restore everything from your primary nodename, and then overwrite the
exceptions from the secondary nodename.
Q2: How does one go about running scheduled backups for two different
nodenames on the same WinNT system? The only thing I could come up with is
using the "-optfile" option in the scheduler definition, but that seemed
pretty klunky since the schedule for one node ends up triggering a backup
for another node.
Q3: Any timeframe for when this will be fixed?
Thank you in advance.
..Paul
--
At 02:20 PM 10/19/98 -0400, you wrote:
At 02:20 PM 10/19/98 -0400, you wrote:
>Hello ADSM users,
>
>This append is intended for all users of the
>ADSM Version 3 Release 1 Level 0.5 Backup-Archive
>Client for Windows.
>
>A fixtest is now available for the Version 3.1.0.5
>Windows client. The following information, extracted
>from the IC21764L.README.1ST file, provides the detail
>on what this fixtest addresses, as well as other issues
>you need to be aware of before installing this code.
>
>*******************************************************
>* IT IS *** CRITICAL *** THAT YOU READ THE README.1ST *
>* FILE BEFORE INSTALLING THIS CLIENT !!! *
>*******************************************************
>* THERE IS NO NEW FUNCTION IN THIS FIXTEST. *
>*******************************************************
>* DO NOT INSTALL THIS FIXTEST unless you are *
>* experiencing one of the problems addressed in this *
>* fixtest (see below). *
>*******************************************************
>
>The fixtest is located on index.storsys.ibm.com in the
>following directories:
>
>Intel platforms:
>
> Directory: /adsm/fixtest/v3r1/win32/intel
>
> README files:
>
> IC21764L.README.1ST - *** READ THIS FILE ***
> IC21764L.README.FTP
>
>
> Single-byte language installation files:
>
> IC21764L.UNPACKSB.BAT
> IC21764LS.EXE
>
> Multi-byte language installation files:
>
> IC21764L.UNPACKMB.BAT
> IC21764LM.EXE
>
>
>DEC Alpha platforms:
>
> Directory: /adsm/fixtest/v3r1/win32/decalpha
>
> README files:
>
> IC21764L.README.1ST - *** READ THIS FILE ***
> IC21764L.README.FTP
>
>
> Installation files:
>
> IC21764L.UNPACKSA.BAT
> IC21764L.EXE
>
>
>!!!!! WARNING !!!!! WARNING !!!!! WARNING !!!!! WARNING !!!!! WARNING !!!!!
>
>BE SURE TO READ THIS ENTIRE FILE BEFORE INSTALLING AND USING THIS
>THIS TESTFIX SOFTWARE.
>
>!!!!! WARNING !!!!! WARNING !!!!! WARNING !!!!! WARNING !!!!! WARNING !!!!!
>
>***************************************************************************
***
>* FIXTEST 5L, IC21764: Expiration of files containing
extended/international *
>* characters fails with "Active Object not Found"
*
>* message
*
>*
*
>* IC21865: "Access Denied" message received during restore to
a *
>* non-existing on Windows 95
*
>*
*
>* IC21926: Slow incremental backup processing continuously
backs *
>* up files containing extended/international
characters *
>*
*
>* IC21933: Query Backup command from cmd line client displays
*
>* object names containing international characters
*
>* incorrectly
*
>*
*
>* IC21935: Object names containing extended/international
*
>* characters displayed from admin commands (such as
*
>* Query Content) issued from the cmd line admin
client *
>* are displayed incorrectly
*
>*
*
>* IC21959: NT client 3.1.0.5 uses NODENAME to create filespace
*
>* during incremental backup if the old style domain
*
>* option specified in dsm.opt file.
*
>*
*
>* IC22005: Cannot expand directory containing
*
>* extended/international character from the GUI
*
>*
*
>* IC22037: Backup/restore of macintosh files produces "Cannot
*
>* create file/directory entry" message
*
>*
*
>* IC22093: Scheduler service loops when a password is missing
or *
>* invalid, fills up server activity log
*
>*
*
>* WARNING: THIS FIXTEST SOFTWARE HAS NOT BEEN FULLY SYSTEM TESTED. It is
*
>* strongly recommended that you not install this fixtest on a
*
>* production machine, at least until you have had the opportunity
*
>* to test it on a non-production machine.
*
>*
*
>* It is also strongly recommended that you not install this
fixtest *
>* on a machine that is not experiencing any of the problems
listed *
>* agove. Except for fixing the problems listed above, this
fixtest *
>* software is functionally equivalent to IP21371, which is the
*
>* Version 3.1.0.5 Final Edition client PTF for Windows NT, 95,
and *
>* 98. THERE IS NO NEW FUNCTION IN THIS FIXTEST.
*
>*
*
>* ADDITIONAL INFORMATION:
*
>*
*
>* ===========================
*
>* INSTALLATION CONSIDERATIONS
*
>* ===========================
*
>* If you already have version 3.1.0.5 of the ADSM
*
>* client (or a different fixtest for 3.1.0.5) installed, you will
*
>* need to uninstall the existing client software before
installing *
>* this fixtest software.
*
>*
*
>* ========================
*
>* INTERNATIONAL FILE NAMES
*
>* ========================
*
>* Once you start to use this client to back up files with
*
>* international characters (accents, umlauts, etc.) in their
names, *
>* you will most likely see older backup versions of the files
*
>* expire (the ones that have garbage characters instead of the
*
>* properly accented characters). This is an unfortunate side
effect *
>* of the related APARs. Providing a fix that could recognize and
*
>* repair the garbage file names would be extremely difficult, and
*
>* significantly extend the amount of time for the availability of
a *
>* fix, probably by many months. As it is, a fix has already been
a *
>* long time in coming.
*
>*
*
>* A circumvention to this is to rename the existing filespaces to
*
>* other names. Thus the next backup will be a full backup. But
the *
>* existing backup versions will remain. After a suitable period
of *
>* time has transpired, you can delete the old filespaces.
*
>*
*
>* If you have file names with international characters (umlats,
*
>* accents, etc.) then the following client option MUST be in
*
>* effect:
*
>*
*
>* USEUNICODEFILENAMES NO
*
>*
*
>* Otherwise the file names will be backed up with junk characters
*
>* in the name, and it will appear as if the prior problems with
*
>* international characters remain.
*
>*
*
>* Note that the default value is NO for all languages except
*
>* English.
*
>*
*
>* ===========
*
>* MAC VOLUMES
*
>* ===========
*
>* In order to back up Mac volumes on NT, you must have the
*
>* following client option set:
*
>*
*
>* USEUNICODEFILENAMES YES
*
>*
*
>* Yes, as you would imagine, this presents a problem if you have
*
>* file names with international characters, and you also have Mac
*
>* volumes on NT. Unfortunately this will remain a restriction
until *
>* such a time that a fully unicode-enabled Win32 client were to
*
>* become available in a future version or release. (Please note
*
>* that this is NOT an announcement.)
*
>*
*
>* A circumvention for this problem is to use two nodes to back up
*
>* the NT system: One node that has USEUNICODEFILENAMES YES to
*
>* back up only Mac volumes, and another with USEUNICODEFILENAMES
NO *
>* to back up the regular files.
*
>*
*
>* Note that the default value is NO for all languages except
*
>* English.
*
>*
*
>* ================================================
*
>* HOW TO VERIFY WHETHER THIS FIX TEST IS INSTALLED
*
>* ================================================
*
>* You can distinguish this fixtest by running the following
command *
>* from an MS-DOS prompt:
*
>*
*
>* DSMC QUIT
*
>*
*
>* This will cause the client to display the following:
*
>*
*
>* ADSTAR Distributed Storage Manager
*
>* Command Line Backup Client Interface - Version 3, Release 1, Level 0.5
L *
>* (C) Copyright IBM Corporation, 1990, 1998, All Rights Reserved.
*
>*
*
>* Note the Level number on the second line is "0.5 L". The "L"
*
>* indicates that you are running this fixtest. Normal PTFs (i.e.
*
>* non-fixtest code) do not have a letter after the level number.
*
>*
*
>* Alternatively you can start the GUI Backup-Archive client
*
>* (DSM.EXE), then choose "Help/About ADSM..." from the menu bar.
*
>* This will show "Version 3, Release 1, Level 0.5L".
*
>***************************************************************************
***
>
>Andy Raibeck
>IBM Storage Systems Division
>ADSM Client Development
>e-mail: storman AT us.ibm DOT com
>
|
