A Best Practice to Schedule Cron Jobs on a Shared RedHat Linux Server

JockVSJock

So where I work, we have a number of IT departments that share a RedHat Linux Enterprise server. We are all competing with our back up jobs for precious cpu and memory, along with anti-virus and other tasks that are needed.

Because of this, a backup job that would typically run a few hours takes at least 4 to 6 hours.

I'm familiar with mainframe environments where they schedule jobs or job scheduling because of limited resources.

Can anyone offer a best practice on how to manage this better?

darkerosxx

Define priority levels of groups based on business requirements, then define priorities within group, and schedule jobs accordingly. If necessary, place processes in cgroups based on priority level and restrict resources accordingly.