My 2 cents:

- Examine the list of files and make sure that the flagged files do indeed
exist on the target machine. While this might sound trivial or obvious,
it's still a good "sanity check".

- Is the user performing restores of inactive files? For example, using
the -INACTIVE option could cause multiple versions of the same file to be
restored, which would account for the messages being seen.

- By default, restore operations restore the data to their original
locations. For Windows, the file names are UNC-based, so if the original
file name is \\source\c$\somefile.txt, then by default, the client will
attempt to restore the file to machine "source". If the target machine has
a different name, then you need to specify a target location for the
restore, e.g.:

   dsmc restore \\source\c$\ \\target\c$\ -subdir=yes

Otherwise the client will try to restore the files to the source machine,
where those files might still exist.

I would recommend that you identify the specific syntax and options used
for the restore (or their GUI equivalents).

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 12/01/2006
08:54:52 AM:

> 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