A Best Practice to Schedule Cron Jobs on a Shared RedHat Linux Server
JockVSJock
Member Posts: 1,118
in Off-Topic
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?
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?
***Freedom of Speech, Just Watch What You Say*** Example, Beware of CompTIA Certs (Deleted From Google Cached)
"Its easier to deceive the masses then to convince the masses that they have been deceived."
-unknown
"Its easier to deceive the masses then to convince the masses that they have been deceived."
-unknown
Comments
-
darkerosxx
Banned Posts: 1,343
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. -
JockVSJock
Member Posts: 1,118
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Resource_Management_Guide/ch01.html
Didn't know these existed in RedHat Linux. Time to do some research, thanks!***Freedom of Speech, Just Watch What You Say*** Example, Beware of CompTIA Certs (Deleted From Google Cached)
"Its easier to deceive the masses then to convince the masses that they have been deceived."
-unknown