Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
I/O Slave
- Thread starter AliHassan
- Start date
Based on reading some documentation on Metalink, the answers to your questions are
1. RMAN doesn't require a large pool allocation, unless you have i/o slave processes enabled by question 2. Of course you may still need a large pool allocation for other reasons.
2. The i/o slave processes that are relevant to RMAN are backup_disk_io_slaves and backup_tape_io_slaves. One reason for using these parameters is if you are running on an O/S that either doesn't support asynchronous i/o, or implements it inefficiently. The goal would be to improve throughput of your backup jobs.
1. RMAN doesn't require a large pool allocation, unless you have i/o slave processes enabled by question 2. Of course you may still need a large pool allocation for other reasons.
2. The i/o slave processes that are relevant to RMAN are backup_disk_io_slaves and backup_tape_io_slaves. One reason for using these parameters is if you are running on an O/S that either doesn't support asynchronous i/o, or implements it inefficiently. The goal would be to improve throughput of your backup jobs.
- Status
Similar threads
