• dgw

    (@voyagerfan5761)


    DreamHost runs a procwatch script on shared servers that kills any process that uses more than a certain (unspecified) amount of server resources. I just watched in top -c as the php53.cgi process running my backup job suddenly became <defunct> in the middle of the job.

    This has been causing incomplete backup archives to be created.

    I think BackWPup could use a “nice” mode that, when enabled, splits the backup job into small pieces that can be done separately and in under 10 seconds each (or some other safe threshold).

    https://www.ads-software.com/extend/plugins/backwpup/

Viewing 2 replies - 1 through 2 (of 2 total)
  • To overcome a similar issue, I split the entire backup into multiple parts (such as database, plugin files, theme files, other files, etc) and put them to back up at different times of the day. Hope this helps someone.

    I agree with Pothi that I broke mine up similar to stated above. Also, try using tar and gzip as it uses less resources. In some cases, especially if you are doing a blog directory with lots of images, videos etc that are already compressed, it isn’t even worth compressing again so just use tar which will use much less resources.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘[Plugin: BackWPup] Gets killed on DreamHost shared hosting’ is closed to new replies.