I use Inline Entropy Scott. Jobs do take a while to finish first run after enabling, similar to first non-CBT run after creating a Job. What you could do if you have a lot of Job overlap is disable some and do manual runs, either running 1 at a time if you don’t have too awful many, or run a couple at a time if they use different Proxy/Repo resources, until all of them have completed the first run post-enabling Scanning.

My overall Jobs data size isn’t too awful large...15-20TB maybe. It’s hard to say how long it takes because, as you know, it just depends on many factors. But what I shared above is about what it’s like. 

Hope that helps.

Additionally, I didn’t really monitor my Proxy resources because of a few reasons → 1. I ran my jobs manually and sporadically; 2. I have different Proxies for a couple ‘subsets’ of Jobs I have so there isn’t much of a resource overload; and 3. My Proxies are Linux. All that to say is I can’t give more concrete details on resource utilization during Job runs post-enabling Scanning.

Thanks for the replies. I am not worried about CPU. I got lots of horsepower. I just worry it’s going to take days for my next backup if I enable this. Disabling jobs isn’t ideal either. 

I’m in the middle of a big storage migration.. Perhaps when I’m at the 50% mark, and i have double the repo’s and proxies I’ll turn it on and manually kick off a bunch of jobs to get it in place.

Yeah...well, it’d just be like if CBT somehow got disabled, or like the Jobs were all new. That’s what it’ll be like time-wise. It takes a while.

I agree...staggering your Jobs isn’t ideal. It’s just something I decided to do and was ok doing. Sorry I couldn’t give more definitive stats to help you out Scott.