Good morning. Are you referring to the fact that you can only run one job for a subclient at a time?
I believe so. For example we have staggered cron jobs that kick off RMAN backups, only the first starts and the others go into ‘waiting on stream’ status. With this many databases, it doesn’t make sense to do them all sequentially, rather we’d like to kick off a subset at X time, another subset at Y time if that makes sense.
What we’re seeing is jobs waiting multiple hours for a stream. Thanks!
Thank you very much Gowri, we will give both of those settings a look.
Thanks! - Chris
Hi,
I just wanted to close the loop on this. Our storage folks had the server throttled. We had them check the ‘exclude’ for immediate jobs, and set an appropriate number for default and archival subclients. We can now run multiple rman jobs with multiple channels each from the server without issue. Thanks for pointing us in the right direction.