Thanks Richard, 
This is windows, so It might not behave like the rest
of the world.
 
I'm not sure how it will handle the FSID, Will it retain the 
current FSID 4 and use that fsid for the new drive, or will I 
wind up with "\\servername\j$ FSID 4" and "\\servername\j$ FSID 9"?

 
Do I just issue the command 
Ren filespace servername {\\servername\e$} {\\servername\j$}

or do I need to specify nametype and newnametype?


I haven't done this since ADSM V2 at that time,
the drive you moved the data to just had to have the same
volume label.



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Richard Sims
Sent: Wednesday, July 25, 2007 5:18 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Rename filespace


Doug -

Under normal circumstances (same file system type, etc.) the rename
causes the prevailing filespace to fully represent that client file
system, so you should get a simple incremental.  I've done this many
times in Unix.

    Richard Sims

On Jul 25, 2007, at 7:08 PM, Thorneycroft, Doug wrote:

> Hello,
> I need to  move some data from one drive (E:)  to a new larger
> drive on the same
> server (J:)
> The TSM Filespace name for the E: drive is \\servername\e$ with FSID 4
> The J: drive does not yet exist on the server.
>
> After moving the data to the J: Drive, if I rename filespace \
> \servername\e$ to \\servername\j$
> and Delete the E:drive from the server, will TSM see the J: drive
> as existing data, and perform
> an incremental, or will it back it all up again, treating it as a
> new filespace with a different FSID?