If you want to ensure your website will be able to cope with all potential issues going forward, then taking backs is simply a no-brainer. There are numerous situations where backups will be useful Here are just a few.

So it’s clear there are many situations where a backup would not only be useful, but would be critical for your website. Now, let’s look at a couple of the most popular options for taking and restoring backups.

UpraftPlus is a free WordPress plugin (there’s also a Premium version) for taking and restoring backups. It’s by far the most popular backup plugin around with over 3 million active installations.

To get started with Updraft Plus is basically a two-step process.

– Select how often you want your files and database to be backed up.

– Select Where you want them to be backed up.

You can make a manual backup, but the strength of UpdraftPlus is in the scheduling, so you’ll want to take advantage of that.

Step 1. To set up your backups using UpdraftPlus, go to Settings > UpdraftPlus Backups from your WordPress menu. This will open the UpdraftPlus settings page.

Step 2. Select the Settings tab at the top.

Step 3. Here you can schedule how often UpdraftPlus creates a new backup. You can pick whichever schedule suits you and your site. For example, if you regularly update your site with new pages and posts, then a more frequent backup may be more suitable. The backup is in two parts – the files, and the database. These should both be backed up at the same time.

Step 4. You can also adjust how many of these backups should be stored at one time. Any new backups will then override the older ones, so as not to use too much storage space.

Step 5. Next, select where you would like your backups to be stored. Scroll down the page and you can choose where you’d like your files to be stored. UpdraftPlus integrates with a number of remote storage options, so pick the one that suits you best.

Step 6. Once you have selected a backup location, specific instructions for that service will be displayed. Follow the prompts to finalize your location. You can also select what files are backed up and what files to exclude during backup.

Step 7. You will have to authenticate with the service so that UpdraftPlus can backup to that location.

There are also a number of other methods to take a WordPress backup. The first of these is to take a manual backup. This is not nearly as complicated as many people think, but it’s still a method reserved for those familiar with working with server software. This goes beyond the scope of this document, but here is a good tutorial if you want to know more.

You may also have backup options directly with your hosting company. Some hosts offer easy to create and restore backups as part of their hosting plans, and this is an option you should investigate with your host.

While these videos refer to website migration, the process is virtually the same as backup and restore, and might also fit your situation.

All-in-One WP Migration does not have any settings, and takes a very streamlined approach to the task of migrating your site. Any options are included in the export and import workflow. The reason for this, and why this process is quite different to the one outlined in How to Migrate Your Website With Duplicator, is that the All-In-One WP Migration plugin only exports your site’s contents and database, and not WordPress itself. As such, to import the site on the new location, WordPress must be already installed. Let’s see how it all works.

To begin with it, simply click on the All-in-One WP Migration link on the WordPress Dashboard menu. The first thing you see is a very streamlined page, with a large ‘Export To’ button at the bottom. It is in fact as simple as clicking on this button to proceed. There are additional options, and there is a Find and Replace function at the top if needed, but most users can simply click Export To, and continue the process.

The available options are exclusion options, and some are purely for troubleshooting purposes. Most users will not need, or want, to exclude any of their site’s content, but it’s worth having a look to see if any of the options apply to your site.

Once you have chosen any options, the next thing to do is to click the ‘Export To’ button. A dropdown appears with apparent choices of where to Export your file to. With the free version of All-In-One WP Migration, only the File option is available. All other options are individual extensions that you can purchase. For our example, we are just going to export to a file.

The plugin then prepares the Export file. This may take some time, depending on the size of your site. At the end of the process, you will see a ‘Download’ button. The file is also stored in the Backups section found at All-In-One WP Migrations > Backups. Click on the Download button to download the Export file to your local computer. Again, this may take some time, depending on the size of the file and your Internet speed.

Once you have your file, you are ready to move on to the Import Process. This takes place on your new server.

Now you have your Export file, it’s time to complete the migration of your site. Regardless of whether you are moving the site from a local production site to a new server, or from one host to another, the process is exactly the same.

The starting point for importing the site is a fresh install of WordPress on your destination location. If it’s a brand new site, then all you need to do is organize the hosting and domain name, and install WordPress in your new account. If you are moving a site from one host to another, and you would like to avoid downtime, there are a few extra steps you need to take. There are many ways to do this, depending on your hosting, but basically, you want to be able to log in to your new account and import the site before changing nameservers. My favorite way of doing this is to get the IP address of the new account and use the hosts file on my computer to temporarily map the IP to the domain name, so we can complete the import and only then, when the site has been migrated, change nameservers.

OK, so when you have a fresh copy of WordPress installed on your destination location, you then need to install the All-In-One WP migration plugin again. Once you have done that, head over to Import. The dialog you see is as equally simple as the Export one. The only thing to note here is that you might have a low Maximum Upload File Size, as shown in the image below, depending on your hosting. There are good instructions on the Servmask website for how to fix this.

You can see in this second image, that we have increased the file upload size.

Once you are ready to upload simply click on the ‘Import From’ button and navigate to the file you downloaded earlier.

Once you have chose your file, the plugin gets to work preparing the upload. You will see a flurry of activity about Preparing the upload and checking extensions compatibility etc, and then you will be presented with a  screen that lets you know that by continuing on from this point, files and databases will be overwritten. Click Proceed to import your site, or Close to abort at this point. If you proceed, the import begins. This might take a while, depending on how big your site is, and the speed of your host.

When the upload is complete, you are presented with a  final screen, to let you know that your data has been successfully imported. The final thing to do, as the screen indicates, is to log in to the new site (with the old site’s credentials) and save the Permalinks twice. This completes the process, and your site has now been migrated.

The first step in the process is to ‘Create a Package’. This is the term Duplicator uses for making a full backup of your site. For this reason, Duplicator is also well known as a backup plugin. If you are not familiar with Duplicator, you may want to watch the Quick Overview Video below before continuing.

Creating a Package is a three step process of Setup, Scan & Build. Let’s step through that one at a time.

When you first click on Duplicator, you come to the screen below. Simply click on ‘Create New’ to being the package creation process.

Next, you come to the screen below. At this point, you can just click Next to continue, but there are options here for you to explore, if you wish. Let’s take a look at those.

The options in the Storage area can only be accessed with the Pro version. These allow you to control where the package is stored, and you can choose from a number of options, including Amazon, Dropbox, Google Drive, OneDrive and FTP/SFTP.

The options in the Archive area are split into two sections. The first section – Files, gives you a range of options to choose and filter the files you will backup. You can make a backup of the database only and you can also exclude certain files from the backup.

The second section – Database, allows you to exclude certain tables from the database backup. Use this with caution, as it might break your site if you exclude the wrong tables.

To understand these sections better, please refer to the Archive sub-section of the Packages >> New – Step 1: Setup section of the Duplicator docs.

Finally, the options in the Installer section are completely optional, and some are only available with the Pro Version. For more info on this section, please refer to the Installer sub-section of the Packages >> New – Step 1: Setup section of the Duplicator docs.

So, whether we have explored the options or not, the next step is the scanning process, in preparation for the build process. When you are finished with the Setup page, and you click Next, Duplicator immediately begins scanning the site for any potential issues. You will see the scanning window, and then you will get the scan results, both shown below. If the scan results are all good, you can continue to the Build stage. If there are warnings, you can address these and rescan, but many of these warnings will not interfere with the backup at all.

As they say in the Duplicator documentation; “It is OK to try and build a package even if you have a ‘Warn’ status. If you are able to build a package with a ‘Warn’ status then you can ignore the warning. However if you have issue during the build or install process you may want to work with your hosting provider to try and address the warning.”

When you are satisfied with the Scan results, click the blue ‘Build’ button under the Scan results to actually create the package. You will see a Build Screen for a time, while your package is being prepared, and when it is complete, you will see the second screen below. From this screen, you can download the Archive file, and the Installer separately, or together, from the ‘One Click Download’ button.

Once you have the package contents, you need to then upload them to the server you wish to migrate the website to. In the local production to web server scenario, it’s likely you have a brand new hosting account, or perhaps just a new folder on an existing server if you already have hosting. If you are moving your website from one server to another, you will be uploading the files to the new server.

The next section will show you how the second part of the migration takes place.

Once you have downloaded the two package files, you need to place them in a directory where you would like to install/migrate the WordPress site.

To do this, use FTP or cPanel to upload both the archive.zip and installer.php to your hosting provider. Place the files in a new empty directory under your host’s webroot, where they are accessible from a valid url such as http://your-domain/installer.php or http://your-domain/your-wp-directory/installer.php. On many hosts the root directory will be a something like public_html  -or- www. If you’re not sure what your root directory is, then contact your hosting provider.

Once you have the files uploaded to the directory you wish to migrate the site to, you can then navigate to the installer. Simply type the full path into a browser. For example, http(s)://your-domain/installer.php or http(s)://your-domain/your-wp-directory/installer.php

This will bring up the Install / Migrate screen seen below. As you can see, it is a 4 step process. Let’s walk through it.

In the image below, you will see that there are three sections on the page – Archive, Validation, and Options. You should note that Archive and Validation have both got a green Pass mark next to them. Also take note of the link to the extensive Help docs at the top right if you need them. Note, as well, that if it says Unlocked next to the Help link, this is because you haven’t set a password in the initial Create a Package steps. Click the unlocked link for more details, but it’s not a problem if you will be doing the install straight away and not leaving it at this stage for a considerable amount of time.

Finally at the bottom, you must tick the checkbox next to the Terms and notices section, before the Next button will appear in the bottom right.

If you expand the individual sections, you will see the detailed results of the Archive and Validation steps, and under Options, there are some advanced options. 95% of users won’t need these, but if you run into issues, there is extensive documentation in the help menu linked at the top right of the dialog.

Upon clicking Next, the final part of Step 1 takes place, which is the deployment of the files. This will take some time, depending on the size of your package. When this is finished, we move to Step 2.

Step 2 is all about installing a MySQL database on the target server. Unless you use the Pro version, this is a manual task, but it’s not very difficult. As you can see in the Basic panel, the default Action is Connect and Remove All Data. The remove part won’t be an issue, as we will be connecting to a brand new, empty database.

Before we can click on Test Database, or Next, we have to switch over to our cPanel to create a new database.

Once you have logged in to your cPanel, you need to create a database. What options you have and how it looks will depend on your cPanel version, and indeed, whether you are running cPanel at all. Plesk is another popular hosting administration package, but the concepts will be the same. For this example we are using cPanel.

To create a new database you need to choose either MySQLD Databases, or MySQL Database Wizard. Either will help you quickly create a database for your incoming site.

Either way you do it, there are 3 basic steps (the 4th is just confirmation). See the images below for each step.

1. Create a new database. Take note of the full name of the database.
2. Create a new user. Again, take note of the full name of the user, and the password used.
3. Add the user to the database, assigning full privileges.

Once you have created your database, we can go back to the website and finish Step 2.

Here, you need to enter the details of the database you have just created. Once you enter the details, you can click on Test Database to be sure it’s all connecting, and then click on Next.

One final confirmation screen, and we are on to Step 3!

Step 3 and 4 are quite fast, as the job is nearly done.

Step 3 is simply to update the new paths to the new website. Review and click next.

The final step, Step 4, is to log in to the new website and to check everything is good, and then delete the installation files. Click on the Admin Login button as seen below. To log in, you have to use the credentials of the original site you migrated.

The next screen shows that you have successfully migrated your site, and provides a link to delete the installation files. Once you have clicked on the link, the final screen shows you what has been deleted, and includes a link to Which files need to be removed after an install, in case there are any issues with the automatic deletion.

If all the files have been removed, you’re done!  You have successfully migrated your website from either a local production site or another server, using Duplicator.

Some hosting companies offer a 1 Click Staging Service. This is typically an automated process, where you click a button to duplicate the site, and click another button once you have worked on the site, to push the changes live. There is a lot of variance in how hosting companies implement this feature, and on some hosts, it’s a manual process usually only available on the higher level hosting plans. Check with your hosting company to see if they offer this feature. It’s not that common yet, but this is a high demand feature that many hosting companies are rolling out.

This is a great service for beginners, as it doesn’t require you to understand how to move sites manually, and is generally a much quicker and easier option. Below are a few links to hosting companies offering staging services in some form or other.

Staging sites can also be created through the use of plugins. There are dedicated premium staging plugins, free staging plugins, and migration and transfer plugins that can also easily create a duplicate site. Please read our How to Migrate your Site with Duplicator and How to Migrate your Site with All-In-One WP Migration docs for more information on that process, or see the links below to some of the more popular staging plugins.

As mentioned at the start, you can also easily create a local staging environment. To do this you need some sort of local WordPress installation (see How to Set Up a Local WordPress Installation on Your PC or How to Set Up a Local WordPress Installation on Your Mac for more info on that.) There are many different tools for this, so do your research, and see the links below.

Once you have a local install, you can use a migration / backup plugin like Duplicator or All-In-One WP Migration to transfer your live site to your computer, and then move it back again, once you have made your changes. This is a bit more of a manual process than using a staging service, but this should not cause any issues for an experienced WordPress user.

As mentioned at the start, you can also easily create a local staging environment. To do this you need some sort of local WordPress installation. There are many different tools for this, so do your research, and see the links below.

Once you have a local install, you can use a migration / backup plugin like Duplicator or All-In-One WP Migration to transfer your live site to your computer, and then move it back again, once you have made your changes. This is a bit more of a manual process than using a staging service, but this should not cause any issues for an experienced WordPress user.

The WP Memory Limit is the maximum amount of memory (RAM) that your site can use at one time. When you reach your Memory Limit, you’ll encounter a fatal error. Several things consume memory, such as WordPress itself, the theme you’re using, and the plugins installed on your site. Basically, the more content and features you add to your site, the higher your memory limit has to be.

There are a number of factors that may affect how much memory your website will need such as content, themes, plugins, etc. The default memory limit for WordPress is 32MB. If you’re only running a small site with basic functions, this default value is more than enough. However, once you start encountering ‘Fatal Error: Memory Size Exhausted…, it may be time to adjust your memory limit.

To increase your memory limit, you’ll need to access and modify certain files such as the php.ini, wp-config.php, and .htaccess files. Most hosts won’t grant you full access to modify the PHP.ini file because it affects the whole server and all the websites hosted on it. Please contact your host first to find out if they can adjust it for you.

For advanced users who have their own server setups and full access to the php.ini file, please go ahead and try Method 1 first before the other methods. For standard users, we encourage you to try Method 2 and Method 3 instead.

Step 1 – Locate your PHP.ini file. If you can’t find it, then you can create your own PHP.ini file in the root folder of your WordPress installation.

Step 2 – If you find your existing PHP.ini, open the file and locate the following line of code (xx represents a number):

Then change xxM to your desired limit. For example, 256M.

Step 3 – If you created your own PHP.ini file, then add the same code inside it:

Simply change the value to the recommended value. For example, 256M.

Step 4 – Save your changes, and reboot your local host or server.

Step 1 – Locate your wp-config.php file in the root folder of your WordPress installation.

Step 2 – Open the wp-config.php with a text editor program (Notepad or TextEdit) and add the following line of code above /* That’s all, stop editing! Happy publishing. */

Simply change the value to the recommended value. For example, 256M.

Step 3 – Save the file and refresh your System Status tab. If the WP Memory Limit turns green, then you have successfully increased your WP Memory Limit.

Step 1 – Locate your .htaccess file which is usually in the root folder of your WordPress installation. If you can’t find it, it may be because it’s hidden. Here’s a tutorial for Windows and a tutorial for Mac on how to reveal hidden files.

Step 2 – Open the .htaccess file with a text editor program (Notepad or TextEdit) and add the following line of code:

Simply change the value to the recommended value. For example, 256M.

Step 3 – Save the file and refresh your website.

the PHP Time Limit is the amount of time (in seconds) that your site will spend on a single operation before timing out. This is also to avoid server lockups. The default value for the PHP Time Limit is 30 seconds. When an operation reaches the time limit set, then it will return a fatal error that looks like this

Because the default value is only 30 seconds, you will most likely receive a fatal error when running longer operations. We recommend changing your PHP Time Limit to at least 180 seconds, or to 300 seconds depending on what your host allows.

To increase your PHP time limit, you’ll need to access and modify certain files such as the php.ini, wp-config.php, and .htaccess files. Most hosts won’t grant you full access to modify the PHP.ini file because it affects the whole server and all the websites hosted on it. Please contact your host first to find out if they can adjust it for you.

For advanced users who have their own server setups and full access to the php.ini file, please go ahead and try Method 1 first before the other methods. For standard users, we encourage you to try Method 2 or Method 3 instead.

Step 1 – Locate your PHP.ini file. If you can’t find it, then you can create your own PHP.ini file in the root folder of your WordPress installation.

Step 2 – If you find your existing PHP.ini, open the file and locate the following line of code (xx represents a number):

Then change xx to your desired limit. For example, 300.

Step 3 – If you created your own PHP.ini file, then add the same code inside it:

Simply change the value to the recommended value. For example, 300.

Step 4 – Save your changes, and reboot your local host or your server.

Step 1 – Locate your wp-config.php file in the root folder of your WordPress installation.

Step 2 – Open the wp-config.php with a text editor program (Notepad or TextEdit) and add the following line of code after ‘define(‘WP_DEBUG’, false);:

Simply change the value to the recommended value. For example, 300.

Step 3 – Save the file and refresh your System Status tab. If the PHP Time Limit turns green, then you have successfully increased your PHP Time Limit.

Step 1 – Locate your .htaccess file which is usually in the root folder of your WordPress installation. If you can’t find it, it may be because it’s hidden. Here’s a tutorial for Windows and a tutorial for Mac on how to reveal hidden files on your computer.

Step 2 – Open the .htaccess file with a text editor program (Notepad or TextEdit) and add the following line of code:

Then just put in the recommended value. For example, 300.

Step 3 – Save the file and refresh your website.

The PHP Max Input Vars is the maximum number of variables your server can use for a single function to avoid overloads. The default value of the PHP Max Input Vars is 1000, while the recommended value is 1540. This limitation will truncate some post data such as your menu items which causes issues like your menu items aren’t saving or being left off.

You may need to increase your PHP Max Input Vars if you’re running into issues with your menu. If your menu items aren’t saving properly, or if the last few menu items are being left off, this is most likely because your PHP Max Input Vars value is too low. We recommend your PHP Max Input Vars to be 1540 in order to load all the Classic Demo’s menu items.

Like the other values above, you’ll need to access and modify either the php.ini or the .htaccess files. Most hosts won’t grant you full access to modify the PHP.ini file because it affects the whole server and all the websites hosted on it. Please contact your host first to find out if they can adjust it for you.

For advanced users who have their own server setups and full access to the php.ini file, please go ahead and try Method 1 first before the other method. For standard users, we encourage you to try Method 2 instead.

Step 1 – Locate your PHP.ini file. If you can’t find it, then you can create your own PHP.ini file in the root folder of your WordPress installation.

Step 2 – If you find your existing PHP.ini, open the file and locate the following line of code (xx represents a number):

And set it to your desired limit. For example, 1540.

Step 3 – If you created your own PHP.ini file, then add the same code inside it:

Simply change the value to the recommended value. For example, 1540.

Step 4 – Save your changes, and reboot your local host or your server.

Step 1 – Locate your .htaccess file which is usually in the root folder of your WordPress installation. If you can’t find it, it may be because it’s hidden. Here’s a tutorial for Windows and a tutorial for Mac on how to reveal hidden files on your computer.

Step 2 – Open the .htaccess file with a text editor program (Notepad or TextEdit) and add the following line of code:

Simply change the value to the recommended value. For example, 1540.

Step 3 – Save the file and refresh your website.