When asked to 'replace' them, did he answer 'yes' or 'yes to all'?

Yes, you can restore to an alternate location that is also a different
server.  You need to set up permission for that server to restore the
'originating' server's data, and on the destination side, you must access
as the 'originating' server.  You can also do command line (virtualname)
too.

Vicki Ortepio, Sr. Staff Specialist
International Partner Solutions Data Centers & Systems Support

Verizon Business
201 Centennial Avenue
Piscataway, New Jersey 08854
USA
Phone:  732.885.4126
VNET:  783.4126
Fax:     732.980.7782

Verizon Business - global capability. personal accountability.

This email is strictly confidential and intended only for use by the
addressee unless otherwise indicated.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Dennis, Melburn IT7
Sent: Friday, December 01, 2006 10:55 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Skipped Files During Restore

I have a user that has been testing out a TSM restore of a fileserver in
case of a disaster, and he's been getting reports that out of the
471,871 files that were selected to be restored only 463,133 files were
actually restored.  The remaining 8,738 files are being skipped.
According to the dsmerror.log report, it is saying the the files already
exist on the target server and were skipped for that reason.  Now how is
this possible if the user is restoring the files to an alternate
location (other than the original server) which is an empty drive?

TSM Server 5.3.3.1
TSM Client 5.3.4.0


Mel Dennis
Backup Systems Engineer
Siemens Business Services
4400 Alafaya Trail
Orlando, FL 32826
MC Q1-108
Tel:  (407) 736-2360
Win:  439-2360
Fax: (407) 243-0260
Email:  melburn.dennis AT siemens DOT com