The only limitation of this kind is with regard to Centera pools. You cannot migrate data into, or out of, a Centera disk pool (this is mentioned in the Admin Guide).
I did a simple test of disk -> disk migration using my local workstation disk drives (SATA), and it worked fine. What do Q STG F=D show and Q PR show at the time migration is running? Did you examine the activity log for any related messages issued from the time migration started that might point to a problem? Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <[email protected]> wrote on 2005-02-20 13:35:21: > At the moment i try to install and configure our new TSM environment wth TSM > 5.3, Windows 2003, FC and ATA Disk at 2 EMC Clariion - no tapes > The storagepool hirarchy should be the following: > > 1) Fast small FC Disks (RAID 5) for daily small and medium Files > next to > 2) ATA Disk (RAID 5) with migdelay = 10 days (daily changed files should > expire before migration to sequentail pool) > next to > 3) large ATA squential Pool as last part of the chain and for large, daily > Files (TDP full ?) > > In my first tests i had trouble with migration from 1 to 2: > mig process were starting, but doing nothing. > The process could not be canceled. > Everything else was ok (1->3, direct ->2, 2->3) > > I am not sure whether it is possible to do migration from disk to disk. > Anyone had the same experience, TSM bug? > Kind regards, > Stefan Holzwarth
