My view is that the policy settings are detailed enough to handle this.
 The old file will be treated as a deleted file (and those policy
settings will take effect - you can still keep a number of versions -
for a given time period).  People move files & directories around on
systems all the time and there is no way that ADSM could keep track of
this.  Also you wouldn't want to have to invoke ADSM commands to
perform tasks such as this.  ADSM should just take care of the old &
the new files according to the predefined policy.

I hope I haven't misunderstood the question!

Regards,
Simon
----------
| From: Fred.Landreville /  mime, , , Fred_Landreville AT RJRI DOT COM
| From: Fred.Landreville /  mime, , , Fred_Landreville AT RJRI DOT COM
| To: ADSM-L /  mime, , , ADSM-L AT VM.MARIST DOT EDU
| Subject: Wish list - new item!
| Date: Friday, 08 October, 1999 3:31PM
|
| 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
|