Max Camber
January 19th, 2010, 07:27 PM
I have a fully working setup using Amanda 2.5.0p2 on my Red Hat 5 servers. What I am looking to do is use the ionice command to reduce the I/O impact when backing up servers that are in 24 x 7 production. It seems like this should be possible but I can't quite figure out where to stick ionice in the whole process.
The ionice command is much like regular nice, except that it deals specifically with disk I/O rather than CPU scheduling. It's settings are also is inherited by child processes so as long as I can get it in ahead of the tar and gzip portion of the backup it should work. I was hoping to use the script functionality but I'm not able to upgrade to version 2.6 due to business rules. Is there some other way I can easily sneak this into my backup process?
Just for testing purposes I manually set the ionice level of xinetd and it was automatically applied to amandad, tar, gzip, etc. but obviously that is not a long term solution as it affects all processes spawned by xinetd.
The ionice command is much like regular nice, except that it deals specifically with disk I/O rather than CPU scheduling. It's settings are also is inherited by child processes so as long as I can get it in ahead of the tar and gzip portion of the backup it should work. I was hoping to use the script functionality but I'm not able to upgrade to version 2.6 due to business rules. Is there some other way I can easily sneak this into my backup process?
Just for testing purposes I manually set the ionice level of xinetd and it was automatically applied to amandad, tar, gzip, etc. but obviously that is not a long term solution as it affects all processes spawned by xinetd.