Andy,
BACKUP STGP does not check headers inside an 'object' on a tape, so if your
file is damaged somewhere in the middle, but both start and end of the file
good, then backup stgpool
will not complain and you will never know that both primary and copy
versions are bad until you do audit volume.
The best way is to export data on the source server and then import on the
target. You can export to tape, disk or, starting with 5.1.5.0, directly to
the target server. If both servers
are on the same 100/GB LAN, then direct export would be the fastest way to
do this.
-Original Message-
David,
Here is the list of the things to check:
(1) make sure hardware compression is enabled on your tape drives
(2) make sure TSM does NOT compress data
(3) Oracle server should have enough CPU power to push data, especially if
MTU size is set to 1500 - monitor CPU usage during backups
(4) as
No, it does not work. Per IBM, if you have COPYSTGPOOL defined for a primary
Stg Pool and you attempt to perform LAN free backup to this primary Stg
Pool, it _should_ queitly revert to LAN path and then
write to both primary and copy pools.
In reality, this appears to be behaving like this only
Thomas,
There is no existing [SQL] table you can run SELECT from to get this data.
BUT you can map one of the hidden
tables to create new SQL table and then run your SELECT against this new
table. I'd recommend you to search ADSM-L archive
for the command to do the mapping; this is 'undocumented'
