Paul, Assuming that "SQLDB_COPYPOOL" can be tape... The only implication that I can think of is that if you have to resort to using the copy storage pools, there are some DP/SQL queries (such as querying the TSM Server for SQL database backup file information)
that will require tape mounts, possibly causing some delays in your GUI or CLI extended queries. Operationally, things should work, it's just that you might see some delays on the extended queries. Thanks, Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <[email protected]> wrote on 08/08/2006 10:30:09 PM: > We currently have our primary and copy storage pools for SQL backups as > follows: > > Primary Copy > SQLDB_DISKPOOL SQLDB_COPYPOOL > SQLDB_TAPEPOOL SQLDB_COPYPOOL > SQLMETA_DISKPOOL SQLMETA_COPYPOOL > > Is there any problem if I change the SQLMETA_DISKPOOL so that it's copy > storage pool is also SQLDB_COPYPOOL?
