I had same requirement already in times of V1.
Since then ADSM implemented almost of all
my wishes, but this one remains open for me.

My problem is: 
large chunks of data happen to be moved 
because of various reasons, e.g. regular "file system almost full"  game".
This causes ADSM to 
loose the track of the data, 
evetually expiring old file versions I guaranteed to keep longer,
and forces me me keep 
manual "data move lists" in order to be able to find older backup versions.

Shortly, this makes ADSM inacceptable for medium to long term backup and/or
archive.

Add my voice to IBM your call if you wish!



Salak Juraj

KEBA AG
Gewerbepark Urfahr 14 - 16
Postfach 111
A-4041 Linz
Österreich

Tel. ++43/732/7090-7461
Fax ++43/732/730910
e-mail: sal AT keba.co DOT at
www.keba.co.at



Date:    Fri, 8 Oct 1999 09:31:51 +0200
From:    "Landreville, Frederic" <Fred_Landreville AT RJRI DOT COM>
Subject: Wish list - new item!

Ever had to move a user from one File Server to another?

What happens with ADSM is that once to files are moved, all Object Versions
from the old server are lost and the new file server retakes a new backup of
the same files.

This means that after moving a user's data, and that user request a restore
of a file which is not the latest versions, we cannot give it to her...

Would like to see a MOVE USER DATA command. At the symposium, there was talk
about a possible new function to MOVE NODE, but it would be nice to move
only part of the node...

Any comments on this??? Is this something that would be useful?

Frederic Landreville
RJ Reynolds International