We are in the process of expanding disk space on our primary NT file server.  We
have added an  additional drive as opposed to increasing the existing space.  We
want to move a rather large group folder with many additional folders and files
totaling approximately 50 gb from the existing D drive to the new F drive.   I
have a couple of concerns with the first backup I run after this has been done.
I am going to take a 50 gb hit of additional ADSM storage after this folder(s)
has been moved, since this will be a new folder on a new drive.  At least as far
as ADSM sees it anyway.  Is there any way of avoiding this?  My other concern is
with our existing policy for this server, the original folder will remain in the
ADSM system for 180 days.  I know I can bind a new management class to the
original folder so it will drop off sooner once it is deleted.  However, for a
short period of time, both sets of folders will exist with the same name on
different drives.  If I bind the new management class to one, won't it actually
bind it to both?  If anyone can shed some light on this for me or let me know if
I am just completely missing the boat on something here, I would appreciate
hearing from you.  Thanks!


Terry Taylor
Sr. Tech Specialist
Champion International