My SQL guy sent me the following email about the restore:

"ok, got it to work finally.  after upgrading the client, it still
wouldn't restore to my SQL 7 instance.  so i tried the SQL 2000 instance,
and that gave me an error that the path was incorrect (it was trying to
restore to the D drive, which is where it was stored on ADMNT30, but i
didn't have a D drive on DSS7).  so i tried to do a relocate files in the
TDP client, but the files and paths aren't there!  why?  i don't know,
they should be.  so, on DSS7, i have a small seperate hard drive i had
marked as E, i wiped it out, and renamed it D, and did the restore, and it
seems to be working.  what a pain in the.... !"

Is there a workaround for this issue ?  Does it always have to go back to
the same drive-letter/path ?




Del Hoobler <hoobler AT US.IBM DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
10/05/2004 02:06 PM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: MS-SQL TDP weirdness






Zoltan,

No... there were things added. (See README for details.)
In addition, if you backed up with newer version,
and tried restoring with an older version (like 2.2.1),
there could be problems with meta data alignment,
which might result in weird stripe values.
Bottom line, make sure you are running with 5.2.1
on the restore machine and let us know what happens.

Thanks,

Del

----------------------------------------------------


"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 10/05/2004
01:42:40 PM:

> We did check and everything is the default, which should be *1*.
>
> We checked and the TDP is V2.2.1.  He is installing the 5.2.1
> upgrade/update, although I thought it was simply a "version realignment"
?
>