Best practices for preparing, creating, and restoring the full server using the new backup feature

[maestroc]

I am fairly familiar now with restoring individual accounts through WHM and the new backup system. My backups get off loaded to Amazon S3 but if I need them I can get them back fairly quickly and restore them with no problems.

My question though is how to proactively backup the system in case I need to eventually restore the entire server. In other words, if I accidentally screw something up while digging around in SSH how do I go about rolling back the system settings and restoring WHM, cPanel, etc.? I understand how WHM and cpanel are an operating system installed on top of my CentOS server, but how do I reinstall cpanel if the need arises? Once cpanel is reinstalled would I then have to go in and manually install any software like Amazon's s3cmd in order to allow me to reconnect to my backup drive to grab the accounts and other info?

What is the easiest and fastest way to prepare for a catastrophic crash where everything get's damaged and needs to be replaced? Is there a checklist for server owners to fill out/prepare with?

 

[cPanelMichael]

Re: Best practices for preparing, creating, and restoring the full server using the new backup featu

Hello

In the event of a drive failure, the recommended solution is to reinstall cPanel on a fresh Operating System, and then restore the accounts from backup. Some third-party providers such as R1Soft do offer commercial solutions that include a full backup image of the entire system. The following thread also provides information you may find helpful:

Moving Full cPanel/WHM Server

Thank you.