Thanks Clark, I've found the same in the Technical Guide for version 5.1.
----- Original Message ----- From: "Lawrence Clark" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, May 05, 2005 4:49 PM Subject: Re: Migration -> Primary and Copy Pool What comes into play with migration is the NEXT STORAGE POOL parameter: NEXTstgpool Specifies a primary storage pool to which files are migrated. This parameter is optional. The next storage pool must be a primary storage pool. On the next storage pool you define, migration will not trigger copies to the copypool because it does not fit the criteria: COPYSTGpools Specifies the names of copy storage pools where copies of files being stored in the primary storage pool, during a client backup, archive or HSM stores, are also simultaneously written to all listed copy storage pools. When you are migrating, you are not doing a backup, archive, or HSM store........... After you migration , you can schedule a backup of that pool: BACKUP STGPOOL (PRIMARYPOOL) (COPYPOOL) >>-DEFine STGpool--pool_name--DISK--+----------------------+----> '-POoltype--=--PRimary-' >--+-----------------------------+------------------------------> '-DESCription--=--description-' .-ACCess--=--READWrite-------. >--+----------------------------+-------------------------------> '-ACCess--=--+-READWrite---+-' +-READOnly----+ '-UNAVailable-' .-MAXSIze--=--NOLimit-----------. .-CRCData--=--No------. >--+-------------------------------+--+---------------------+---> '-MAXSIze--=--maximum_file_size-' '-CRCData--=--+-Yes-+-' '-No--' .-HIghmig--=--90------. >--+---------------------------+--+---------------------+-------> '-NEXTstgpool--=--pool_name-' '-HIghmig--=--percent-' .-LOwmig--=--70------. .-CAChe--=--No------. >--+--------------------+--+-------------------+----------------> '-LOwmig--=--percent-' '-CAChe--=--+-Yes-+-' '-No--' .-MIGPRocess--=--1------. .-MIGDelay--=--0----. >--+-----------------------+--+-------------------+-------------> '-MIGPRocess--=--number-' '-MIGDelay--=--days-' .-MIGContinue--=--Yes-----. >--+-------------------------+----------------------------------> '-MIGContinue--=--+-Yes-+-' '-No--' >--+-----------------------------------------------------------------------+ ->< | .-COPYContinue--=--Yes-----. | '-+-------------------------------------+--+--------------------------+-' | .-,--------------. | '-COPYContinue--=--+-Yes-+-' | V | | '-No--' '-COPYSTGpools--=----copy_pool_name-+- >>> [EMAIL PROTECTED] 05/05/2005 3:24:32 PM >>> Hi Fellows, The environment: TSM Server 5.1.9.5, AIX 4.3.3 ML 9 Two 3580 LTO1 SCSI tape drives (manual) Both drives defined on the same library. A small costumer used to backup their data directly to tape storage pools, primary and copy, simultaneously coping the data to both storage pools. Until that point nothing weird, just define the copystg option on the primary and everything works like a charm. The strange bahavior appeared when, for performance reasons, they decided to backup their data to disk and than migrate it to tape, the migration to tape works fine, but only goes to one of the storage pools (the primary). Since, nothing has changed on the tape storage pools what the hell is going on? It seems like some limitation for the migration process, but it should work. At least this is what the manuals show. I've checked the migprocess option to ensure that there was only one process, but nothing changed. The backup stg command works fine. Am I missing something? Atenciosamente, . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BRUNO MELO Suporte Informatica Ltda. e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.5 - Release Date: 4/5/2005
