How do I completely disable WHM backups?

[alexisb]

Hi, I put disable in Backup configuration from WHM but I am still getting the "tar" commands with 99% cpu usage in my top listings, also getting the cpuwatch message, that so many threads mention.

How can I effectively disable these backups?, I am getting huge loads.

Thank you.

 

[kris1351]

Click on the Backup Configuration link in WHM and select disable.

 

[alexisb]

Already did that

Hi, thanks for your kind reply but that was the first thing that I did, I have checked many times and Backup Configuration is disabled in WHM, but I can still see the "tar" processes in top.

Do I have to restart any service in order for this change to take effect?

I also noticed that the tar commands are pointing to a non existant backup directory, should I manually create this? how should I chown?

Thanks.

 

[PWSowner]

Maybe a user is doing a manual backup.

 

[alexisb]

Nop

Hi, nop, the server is new, very few domains, most of them are mine.

Any other idea?

Regards!

 

[haze]

killall -9 cpbackup should do it. You'll have to see if any processes such as pkgacct gzip tar etc are still active.. they may just die off though.

 

[alexisb]

Disable backup not a good idea

Hi, this is getting me nuts.

I realize disabling backup is not the best idea.

I have re-enabled it, even if it never was disabled, and selected "weekly" and incremental.

However, I still have a load average around 2.0.

From time to time I see this line in top using 99% CPU:

tar cfzp /backup/cpbackup/daily/dirs/_etc_vfilters.tar.gz .... (just the part of the command I can see)

My question is: Why do I see this line that apparently is for a "daily" backup operation if I have only activated "weekly"?

My other question: Why do I see /backup/cpbackup directory, I don't see that directory in my file system. Could that be the problem? Should I have to create that directory? How do I chown it?

So sorry for asking so many questions but this is a new server, very few customers, no manual backups running, and the WHM Backup is "eating" it.

Thank you.