thanks!
Our tech support didn't write down the file name and I believe it was only 1
file, but I will ask if he happens to remember the name.
And I will check out those sites.
----- Original Message -----
From: "Prather, Wanda" <wPrather AT ICFI DOT COM>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Wednesday, May 11, 2011 12:32 PM
Subject: Re: [ADSM-L] restore question
Happens rarely, but I've seen it before. Freaked me out.
Has to do with how Windows creates the under-the-covers 8.3 DOS file names.
TSM backs up and catalogs the filenames with the long-name version, but when
it restores the file, NTFS will still create the 8.3 filenames by default.
Here's how it can happen:
Suppose you have files called
whoop~1.txt
whoopee2001.txt
If whoopee2001.txt gets restored first (totally by accident), NTFS will
create the short name whoop~1.txt for it. Then when it tries to restore
whoop~1.txt, you get the error message you saw, i.e. a file name clash.
(And as I recall, the error message may use the long file name, so it's not
necessarily apparent what the problem is.)
You have to have files of just the right names, just the right length names,
in the same directory, and an accident of restore order to make it happen,
so you rarely see it. (It's most likely to occur in directories where files
are generated by a software package where some developer has brilliantly
decided to use a lot of ~ in the generated filenames, so you may be able to
identify exactly which directory has the issue.)
Simple solutions:
-If it only happens on 1 or 2 files, be confident that TSM is OK, write the
file name down. After you've finished the big restore, go back and find
those files in TSM and restore them to different directories, then drag them
back to where they belong.
-If it happens a lot and you are nervous about the results, or your restore
needs to run a long time unattended, you can disable Windows NTFS 8.3 name
creation, run your restore, then re-enable the NTFS 8.3 name creation. (The
downside of that is if you have users that for some reason regularly refer
to the short 8.3 form of the file name -- again most likely program
developers -- they may have some patching to do after the restore.)
Here are references that may explain it better and help you determine if
this is your problem. The MS article has instructions for turning off 8.3
filename creation:
https://www-304.ibm.com/support/docview.wss?uid=swg21304777
https://www-304.ibm.com/support/docview.wss?uid=swg1IC45443
http://support.microsoft.com/kb/121007
http://support.microsoft.com/kb/121007
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Jeannie Bruno
Sent: Wednesday, May 11, 2011 10:21 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] restore question
Hello. Wondering if anyone else has ever seen this scenario:
We had a 2003 windows server that died last week. Got a new 2008 server
this week. Did the restore for the 'user' drive for all their data. (Used
the TSM gui to do the restore. TSM client version 6.1.2).
But during the restore about 4 hours into it, we got the prompt to 'replace
the existing file?' message for one of the files that was being restored.
Now because this is a brand new server that never had any user data on it,
why would we get prompted this message?
Before we started the restore, we did not choose any of the restore options
for the replacing,etc, because it was a brand new server, i didn't think
this was necessary to do.
anyone know why this happened??
thanks.
____________________
Jeannie Bruno
Systems Analyst
jbruno AT cenhud DOT com
284 South Ave.
Poughkeepsie, NY 12601
845-486-5780
This message contains confidential information and is only for the intended
recipient. If the reader of this message is not the intended recipient, or
an employee or agent responsible for delivering this message to the intended
recipient, please notify the sender immediately by replying to this note and
deleting all copies and attachments. Thank you.
|
