WHM 11 management series

How to restore existing backups to your WHM server

Now that you should have the backup system enabled and configured, you should know how to powered by ausweb backups in case you ever need to do so.

There are three tools in the Backup section that we’ll be going over.

1) Find that section in the menu.

2) First, go to Restore Backups.

In order to use this tool, you must have properly configured backups as shown in the previous tutorial. You must also have some sort of backup currently available in the backup folder.

3) Select which type of backup to restore.

4) Choose a username from the list to restore.

5) If the account no longer exists on this server, check the box next to Recreate Account. Then, choose whether you want to Give the account an IP Address.

6) Alter any of the other options you want, then click Start Restore.

With any luck, after a moment the account restoration should be complete.

Now, let’s see how to restore multiple backups.

This tool will automatically open up a new tab or window. If you’ve ever transferred multiple accounts, this should look familiar.

7) Again, start by choosing which type of backup to restore.

8) Select at least one user from the table to restore.

9) Then, hit the Deselect Column button for the Recreate Account column. These two accounts already exist, so we don’t need to recreate them.

10) When ready, click Start Restore.

Note the warning — you shouldn’t close this window or press the back button during the restore process if you want it to succeed.

You should receive a status update in the left frame when the first account has finished.

11) When the second account finishes, the multi restore is complete. Return to WHM. Remember not to press the back button here; just close the tab or window.

On to the final restore method.

This restore tool works a bit differently; it’s designed to work with Full Backups, as generated from a cPanel account. The backup must be in one of the directories listed on the screen. Any detected backups will be displayed at the bottom of this page.

12) Enter the username of the account you wish to restore.

13) Then, click Restore.

As you can see, we received an error because the user already exists on this system. In other circumstances, this page should look exactly like the individual account restoration we performed first in this tutorial.

With the final method described to you, this tutorial is now at an end. You now know all three ways to restore existing backups in WHM.

WHM 11 management series

How to reboot your server using WHM

There are two tools you can use to reboot your server from within WHM.

They have their own category, called System Reboot.

1) Let’s go to Graceful Server Reboot first.

This tool is the preferred way to reboot your system. You should use this method whenever possible; it allows the server to close any processes your users may be running before restarting, storing data as it does so. This reboot method should not result in data loss.

2) To reboot, simply press Proceed.

3) Next, Forceful Server Reboot.

A Forceful Reboot will shut down the computer regardless of what’s running. It can cause data loss. You should avoid using this method whenever possible; only use it in the event the Graceful Reboot function is not working.

This method is generally preferrable to physically rebooting the server with the power switch, however.

This completes the tutorial. You now know both ways to reboot your server in WHM.

WHM 11 management series

How to use the background process killer in WHM

With the Background Process Killer, you can tell WHM to search every day for processes your users should have no reason to run in a standard web hosting environment.

If a process is found, the scanner will automatically kill the process and send you an e-mail telling you who was running it.

1) Locate the System Health category.

2) Click Background Process Killer.

WHM recommends that you check all of the programs in this list. Most of these relate to IRC, or Internet Relay Chat. IRC brings with it the stigma of causing lots of Denial of Service attacks, so most hosts explicitly disallow their users to run IRC servers on their networks.

This scanner will find these processes even if the user tries to hide them by renaming them.

3) We’ll do as they suggest and check off all the programs.

4) Using this textarea, you may enter a list of users that you want the process killer to ignore, one per line.

5) Press Save to finish.

Your selection has been saved. All the processes you chose will be killed every night, if detected.

Also, any users you entered have been marked as trusted.

This completes the tutorial. You now know how to use the Background Process Killer in WHM.

WHM 11 management series

How to run security scans in WHM

WHM allows you to run two security-related ausweb that may be of use to you.

1) Go to Security.

2) Start with Quick Security Scan.

This tool will check for and disable any unnecessary services that may have been installed by your operating system. If they aren’t being used, there’s no point in keeping them running.

3) Click Proceed to begin the scan.

Any [FAILED] results from the scan indicate that the service wasn’t running, so there was nothing to shut down.

4) Next, let’s Scan for Trojan Horses.

A Trojan Horse is a type of malicious software that may appear harmless but actually can allow a hacker to gain access your system.

This function will check for system files that have recently been modified by something other than cPanel or the operating system.

Generally, this tool only finds false positives and not trojan horses. There are better alternatives, but none that come with WHM. Still, you might want to look into any files that this scan points out, to ensure that they have not been compromised.

5) Proceed with the scan.

As you can see, the scan detected 16 possible trojans — that doesn’t mean that they definitely are trojans. In fact, it’s more likely that they aren’t.

This tutorial is now complete. You now know how to run security scans in WHM.