Hi,
you can prevent fragmentation on filepool-volumes if you define/create them
assigning to the pool and not using scratch-volumes for FILE-Storagepools.
Using a command like ...
define volume <Storagepoolname> <volumename> numberofvolumes=10 
formatsize=20000 wait=yes
... defines 10 volumes with a prefix of 'volumename' ech at 20GB .
It is important to use 'wait=yes' so those 10 volumes will be created 
sequential.
Without 'wait=yes' all 10 volumes would be created in parallel and 
fragmentation possibly will happen.
You can really have filepool-volumes without fragmentation (wait=yes) and 
scratch-volumes
surely are not so recommended.

Cheers Rainer


Christian Svensson schrieb:

Hi,
If I where you I should like this instead.


1) Rename your old Diskpool
2) Create your File Pool with the same name as the old Diskpool
3) Update your Diskpool with HIGH=0 LOW=0 and NEXT=FILEPOOL (Disable Cache also 
if you have any)
4) Wait 2-3 days
5) Delete all Volumes in your DISKPOOL and Delete DISKPOOL

Now will you migrate the data and you can still backup to your new STG POOL 
with any issue an no extra work for you.

But why do you wanna move to FILE CLASS? Do you wanna use De-duplication? You 
know you will delay your backups and get a lot of fragmentation if you don't 
pre-create all Volumes? This has nothing with TSM really, but most of the issue 
is the filesystem, TSM need to create the file first before TSM can save any 
data to that volume, and that will create a delay.
If TSM creates multiple volumes, then will you get fragmentation.
I normally don't recommend anyone to have FILE CLASS as first storage pool. I 
only use that if a customer want to have a VTL but don't have any money to buy 
a real VTL.

Best Regards
Christian Svensson

Cell: +46-70-325 1577
E-mail: Christian.Svensson AT cristie DOT se
Skype: cristie.christian.svensson
________________________________________
Från: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] för Grigori 
Solonovitch [G.Solonovitch AT BKME DOT COM]
Skickat: den 28 juli 2009 12:35
Till: ADSM-L AT VM.MARIST DOT EDU
Ämne: Move data from DISK pool to FILE pool

Dear TSMers,
We have TSM 5.5.1.1 under AIX 5.3.
I need to move data from DISK primary storage pool (raw logical volumes) to 
FILE primary storage pool (JFS2 file system).
There are 3 tape copy pools for DISK primary pool.
I am going to use next procedure:
1) create FILE primary storage pool with appropriate size;
2) move data from DISK primary storage pool to FILE pool by "move data <vol> 
stg=<FILE> reconstruct=no" (volume by volume);
3) delete DISK primary storage pool;
4) rename FILE storage pool to old DISK pool name.
My expectations:
1)     all existing tape copy pools, made for DISK pool, will be still legal 
for FILE primary storage pool (no need to make extra backups and it is possible 
to restore any data in FILE storage pool);
2)     no need to modify any copy groups connected to old DISK pool because of 
the same storage pool name;
3)     expiry process will continue to work normally;
4)     full/incremental backup history will be untouched by data movement.
Am I right?
I will deeply appreciate any comments.
Thank you very much in advance.
Kindest regards,


Grigori G. Solonovitch

Senior Technical Architect

Information Technology  Bank of Kuwait and Middle East  http://www.bkme.com

Phone: (+965) 2231-2274  Mobile: (+965) 99798073  E-Mail: G.Solonovitch AT bkme DOT 
com<mailto:G.Solonovitch AT bkme DOT com>

Please consider the environment before printing this Email


Please consider the environment before printing this Email.

________________________________
"This email message and any attachments transmitted with it may contain confidential 
and proprietary information, intended only for the named recipient(s). If you have 
received this message in error, or if you are not the named recipient(s), please delete 
this email after notifying the sender immediately. BKME cannot guarantee the integrity of 
this communication and accepts no liability for any damage caused by this email or its 
attachments due to viruses, any other defects, interception or unauthorized modification. 
The information, views, opinions and comments of this message are those of the individual 
and not necessarily endorsed by BKME."

--
------------------------------------------------------------------------
Rainer Wolf                          eMail:       rainer.wolf AT uni-ulm DOT de
kiz - Abt. Infrastruktur           Tel/Fax:      ++49 731 50-22482/22471
Universitaet Ulm                     wwweb:        http://kiz.uni-ulm.de