Hello Hans,

>One of our LAN servers is running out of disk space. We are going to
>add another hard disk to it, and to level the usage between the old
>and new disks by moving half the data from the old disk to the new one.
>
>As far as I can see, ADSM is going to see all the moved data as
>deleted in one place and created in another. Since we have set our
>management classes to keep 4 copies when the files exist and only
>one copy when the files are deleted, ADSM is going to expire all
>but one copy of our files. It will also take a new copy (on the new
>filespace) that will be the same as the copy it has on the other
>filespace.
>
>Is there a way to keep our old generations across this operation?

Hans, you mentioned a very basic problem in managing data storage of
client server systems. Storage managers have to handle relocation of
data (whatever reason) in a nontricky procedure and users don't
understand the disappearance of their previous file versions.

Regardless to the bypass solutions recommended by Brett there has
to be a simple transparent way to "move" or "rename" the data on the
server.

We encountered the problem some monthes ago and opened a change
request REQNO REQ00044582. The RESPONSE was:

"RECONIZED - IBM agrees with the request and a solution appears to
be a desirable objective. A solution, however, may not presently
appear feasible or implementable. No IBM commitment is made or
implied as to the eventual delivery of an acceptable solution."

IMHO it seems not to be so unfeasible but there was no lobby YET.
Maybe there are other shops with the same problem now?

Because I'm not so familiarly with the internet usenet I'm sending
a CC to your personal address.

Regards
Clemens Milz, Munich/Germany