Skip to main content

How to dimension a server for successful backups

Comments

3 comments

  • cPRex Jurassic Moderator
    Hey there! The backups have to get created and compressed on the local system before they are moved over to the remote destination, so that does take up some space, but in general, we like to see 2 times the space of the largest account, plus 1G for some breathing room. So, if your largest account is50G, we'd want to see 101G of space to ensure there is room for that to compress and copy.
    0
  • Duplika
    Just to confirm, does cPanel create, compress, transfer and remove 1 backup at a time right? We plan to use remote Wasabi compressed backups. In your example. even if we have hundreds of accounts to backup, if "Retain Backups in the Default Backup Directory" is disabled, we would only need 101 GB of space on the local server for all backups to be successfully transfered to remote destination right?
    0
  • cPRex Jurassic Moderator
    Yes - if you watch one of the backup logs in /usr/local/cpanel/logs/cpbackup, you'll see something similar to this, which is taken from the most recent log on my personal server: [2022-08-24 02:00:28 -0400] info [backup] Calling pkgacct under cpuwatch to backup user "cptest2" [2022-08-24 02:00:29 -0400] pkgacct started. [...several lines later...] [2022-08-24 02:04:06 -0400] info [backup] Calling pkgacct under cpuwatch to backup user "domaintest"
    so we can see they are sequential. Your disk space thought is also correct - we always tell people "two times the space of the largest account, plug 1G for some breathing room" for the tool to actually function.
    0

Please sign in to leave a comment.