Understanding Backup For Restoration

Anthony Parsons

• August 12, 2016 23:00

I understand backups, but I don't quite understand the system files restore component. So... if my server totally crashed, I would reload Centos, then reinstall WHM and then I could restore the system file backup which would put my system file settings back to what I have them... is that right? After that I could then just restore each account backup to get them all working again. Is that the gist of this? I also have all my backups going to S3 in case of total SSD failure. Question on the S3 -- can you restore if needed direct from S3? Will the auto delete feature work on external accounts, i.e. as it auto deletes older backups on the server, will it auto delete the same at S3 or is S3 self managed? Sorry about the newb questions... just trying to understand in the event of catastrophic failure.

• 

  cPanelMichael

  • August 16, 2016 20:35

  Hello, It's generally not recommended to restore all system configuration files on a new server. These files are mostly intended for restoration locally (e.g. an administrator accidentally deletes /etc/passwd and needs to restore it). In most cases, the cPanel backups contain most of the necessary configuration data associated with the accounts. You would reinstall the OS and cPanel, configure your EasyApache profile, and update your configuration settings in WHM before restoring the accounts. You may find documents like this helpful for restoring some of the configuration files: EasyApache 4 - Create a profile - EasyApache 4 - cPanel Documentation More information on system backups is available at: You can also vote and add feedback to the following feature request:

  0
• 

  Anthony Parsons

  • August 17, 2016 08:55

  Thanks @cPanelMichael, appreciated for your time to help me understand WHM backup more completely.

  0

Please sign in to leave a comment.