Bruno, That is because simultaneous write only comes into play during certain operations. Simultaneous write is not implemented for migration operations performed by the server.
Read the section of the Adminstrator's Guide entitled "Using the Simultaneous Write Function to Protect Your Data". Here's an excerpt from that section of the manual that applies to your question... Simultaneous write is supported for the following operations: - Backup and archive operations by Tivoli Storage Manager backup-archive clients or application clients using the Tivoli Storage Manager API - Migration operations by Hierarchical Space Management (HSM) clients - Import operations that involve copying exported file data from external media to a primary storage pool associated which is configured for simultaneous write configuration -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bruno Melo - Suporte Informática Sent: Thursday, May 05, 2005 3:52 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Migration -> Primary and Copy Pool I know that Jean. :-) I'll try to explain better, the next storage pool defined on the disk storage pool is the tape primary pool. And in the tape primary pool there is a copy storage pool defined. The problem is that the data that is going to the tape primary storage pool isn't going to the copy storage pool simultaneously. ----- Original Message ----- From: "William Jean" <[EMAIL PROTECTED]> To: <ADSM-L@VM.MARIST.EDU> Sent: Thursday, May 05, 2005 4:35 PM Subject: Re: Migration -> Primary and Copy Pool You can't migrate data in copy pools. ________________________________ From: ADSM: Dist Stor Manager on behalf of Bruno Melo - Suporte Informatica Sent: Thu 5/5/2005 3:24 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Migration -> Primary and Copy Pool 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] ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ -- 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