No. It will actually copy the files in the pool specified not the higher pool in the hierarchy.
Normally what you do with a traditional pool hierarchy is as follows: backup stg diskpool copypool backup stg tapepool copypool update stg diskpool highmig=0 lowmig=0 (thus forcing the migration) This ensures that all newly arrived data is backed up to the copypool. After these three steps all newly arrived data is in both the tapepool and the copypool. If cache=yes, then newly arrived data (and perhaps data from past days) is still in the diskpool as well. Clients needing data will fulfill that need from the most easily accessible pool. Ideally, the diskpool, but if the data has been migrated and flushed, then tapepool. If destroyed in the tapepool then from the copypool. Remember, the backup stg operation is incremental. So only data that is not already in the copypool is copied from disk and tapepool. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs, CO 80949 [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com or www.storserver.com (719)531-5926 Fax: (240)539-7175 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Ran Harel Sent: Thursday, May 23, 2002 12:19 AM To: [EMAIL PROTECTED] Subject: Backup Migrated Chached files Hi TSMers Does Anyone have a clue: You have a primary storage pool with cached option enabled. You perform a migration to your secondary storage pool. Then you perform a backup storage pool from the secondary storage pool to your copy pool. Could it be true that TSM uses the cached files for the operation in the way it does with restore ? It is documented that when you backup the primary storage pool, tsm will not copy cached files - which means you have to copy the secondary storage pool either - that is clear. Any ideas ? Tnx. Ran
