If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.
Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.
This is backup to disk - not tape.They managed to back it up at 1.6TB per hour.
I know this TDP and that is why in a classic setup: node --> disk --> tape, restores will be a lot slower except when you are running LAN Free, or cache data on disk. Restore will likewise be slow from copy tapes (DR scenario).Remember also that this is TDP not the BA client so it will behave a little different.
My experience with the TDP is with DB2 so the config may be different for Oracle.
Backom is the command used with the DB2 TDP.What is backom?
On your side, which bandwidth do you get, per tape drive, when you backup and restore?
It is my understanding that the order for DB backups is maintained correctly by TSM when it writes to tape. Data tags are provided with each backup stored on disk such that when writing to tape, the sequential Data tags are observed and ordered correctly.What may cause your performance problem while using a disk cache (staging area) is the data is migrated from disk to tape in the "wrong" order. Rman (Oracle/SAP) is requesting files in the same order as they were written to the backup system. The use of a staging disk in this case may affect the restore.