How to backup your WordPress database with one click

How to backup your WordPress database with one click

How to backup your WordPress database with one click
Our plugin offers you a lot of settings for your backups. But it is also possible to get things done the easy way. If you just want to create a WordPress backup of your database, you can use the BackWPup One Click Backup option. You can find this in the WordPress admin area:

Login to WordPress.
Go to BackWPup → Dashboard.
Click on the big blue button Download database backup under One click backup. Your database will be stored as .sql file on your computer.
Click on the big blue button Download database backup under One click backup

Note: The WordPress database backup is not a full backup of your WordPress website. For a full WordPress backup you need to save the files of the WordPress installation as well. Create a recurring backup job to save all files. This will prevent you from not being able to restore your website if needed.

Starting a backup job – immediately or scheduled

Starting a backup job – immediately or scheduled

Starting a backup job – immediately or scheduled
Backup jobs can be started either immediately or scheduled. You can choose between five different ways a job can be executed.

Table of Contents

Immediate (manual) Execution of a Backup JobExecute a Scheduled Backup Job
1. Immediate (manual) Execution of a Backup Job
In your WordPress admin area, you can find a list of all created backup jobs under BackWPup → Jobs. The table has the following columns: Job Name, Type, Destinations, Next Run, Last Run. Here you can not only see when your backups are going to start, but also start them manually if needed.

Hover your mouse over a job name. Under the name, a new line of links will appear.
Click on Run now to start the backup job immediately.

Immediate (manual) Execution of a Backup Job
2. Execute a Scheduled Backup Job
The scheduling of backup jobs can be set while creating a new job or by editing an existing job (see screenshot above, link Edit). The settings for scheduling are under the Schedule tab.
Execute a Scheduled Backup Job
Here can you find five ways to get a scheduled job started:

Manually only – Choosing this option, the backup job will not be scheduled. Instead, you have to start it yourself manually as described above under 「Immediate (manual) Execution of a Backup Job」. At BackWPup  → Jobs the Next Run column will be set to Inactive.
With WordPress Cron – The WordPress Cron offers processes to be run automatically and scheduled. With BackWPup you can use the WordPress Cron to schedule the backup jobs. If you choose this option, more settings will be shown on the page where you can set the desired time of execution: monthly, weekly, daily, hourly or individually under advanced. At BackWPup  → Jobs the Next Run column will be set to the date and time you chose.

WordPress Cron to schedule the backup jobs

With EasyCron.com – This is an external Cron server. If you encounter problems with the WordPress Cron, you can choose this as a replacement. You need an API key of EasyCron.com, which you can enter under BackWPup → Settings, in the API Keys tab.
With a link – Copy the link that is displayed under this option, paste it into the address bar of a new browser window and hit enter. You will only see a blank page but BackWPup is working in the background and executes the backup job. This way can be also used for starting a job from another application.
Use WP-CLI from the commandline – WP-CLI is a command line tool for WordPress, which is popular among developers. Backup jobs can be started with the command wp backwpup start .

For beginners we usually recommend the option 「with WordPress Cron」. A manual execution can be used after the creation to test if everything is working. All other options are more for advanced users.
In rare cases, jobs which are running with WordPress Cron may not work correctly. If you encounter this, please have a look at 「My backup jobs don』t seem to run as scheduled「.

How to restore a WordPress backup?

How to restore a WordPress backup?

How to restore a WordPress backup?
In this guide, we will introduce you to various ways how to restore your WordPress website in an emergency with a previously created WordPress backup.

Table of Contents

Restore a WordPress Backup with BackWPup Pro – NEWManually restore a WordPress BackupThe content of the backup archiveRestore the WordPress database from a backupRestore the WordPress files with FileZilla from a backup
1. Restore a WordPress Backup with BackWPup Pro – NEW
Since version 3.5, BackWPup PRO helps you to restore the website backups you made with our backup plugin. The restore feature is integrated in BackWPup PRO which means you can start the restore process in your WordPress backend directly. To do this, you simply need a backup which was created with BackWPup. In case your website is destroyed completely and you don』t have access to your backend anymore, you can use the restore standalone app which you get as PRO user.
In our BackWPup restore documentation you can read how the restore with BackWPup works in detail.
2. Manually restore a WordPress Backup
Besides that, there are some tools to restore your WordPress website from a backup.
Here we explain how to restore the database with phpMyAdmin and Adminer and how to restore the files with the FTP program Filezilla.
Please note: For this tutorial we use a complete WordPress backup created with BackWPup, as all needed files are contained. This is the preferred method for beginners.
Advanced users can also use partial backups. For example, not backing up plugins or themes as they are available in the WordPress.org repositories or stored locally on your computer. You can save some space with this method. This means it can be that you don』t have all the files we are mentioning here.
Under BackWPup Pro → Add new job, tab General, we check all job tasks and choose Backup to folder as job destination. The WordPress backup will be stored on the server in your WordPress installation.
Check all job tasks
2.1. The content of the backup archive
Before you start, get the backup archive that you created with BackWPup. Unzip the
archive and take a look at the contents. You will see:

the database of your WordPress as .sql file. The file may be zipped, depending on the settings of the backup job.
the file SiteName.pluginlist..txt – the list of all installed plugins. This is helpful if you don』t backup the plugin files, so you can easily add the plugins to your WordPress again and don』t forget any.
the file SiteName.wordpress..xml – the backup of the WordPress contents (blog posts, pages, products, etc.) in the XML format. Via the WordPress Importer you can restore the contents. In the admin area, this is located under Tools → Import.
the file manifest.json – in the future, this file will be used for the automatic restore. You can ignore this file for now.
the file backwpup_readme.txt – this file contains important information. You should read it before doing a restore.
the files of your backed up WordPress installation – these need to be copied into the folder of your WordPress installation. See the part Restore the files with FileZilla. All other files mentioned above should not be copied to your server.

2.2. Restore the WordPress database from a backup
with phpMyAdmin
phpMyAdmin is a web application which you can use to administrate MySQL databases via a browser. It is offered by many web hosts. You don』t need any MySQL skills to work with it, as the tool has a WYSIWYG interface. If you want to restore a database, follow these steps:

Log in to phpMyAdmin.
In the sidebar you can see all current databases. Choose the one you wish to restore. You can find the name of the database of your WordPress in the wp-config.php file, which is located in the main directory of WordPress. Search for the line define('DB_NAME', 'your_database_name_here');
If there are any tables in the database that are also in the database backup, they will be overwritten.
Log in to phpMyAdmin
Go to Import.
Go to Import.
Select the database .sql file of the BackWPup backup from your computer. It may be a zipped file if it is not a .sql file. phpMyAdmin should automatically set the encoding and database format settings (see screenshot above). The format should match the ending of the database file, it should be SQL. You can check the encoding by opening the unzipped database file in a text editor. Find the line /*!40101 SET NAMES ... */;
Click the OK button and wait until you get the message that the import was successful.

Some providers only allow importing databases up to a specific size. You』ll get an error message if you try to import a bigger file. Please contact your host or try to import the database with the plugin Adminer, which is described in the following section.
with Adminer
Adminer is similar to phpMyAdmin, it is a free tool you can download here. Upload it to the main folder of your WordPress installation. Adminer comes with just one php file, feel free to rename it to adminer.php for easier use.

Open the uploaded Adminer file, for example yourdomain.com/adminer.php in your browser. You』ll see a form where you need to fill in the database credentials. You can find these in the wp-config.php file of your WordPress or you can get them from your host.
Log in with the credentials. You』ll now get a screen similar to phpMyAdmin. The workflow is also similar to phpMyAdmin.
If there are any tables in the database which are also in the database backup file, these will be overwritten by the import.
Go to Import.
Go to Import Adminer
Select the database .sql file of the BackWPup backup from your computer. It may be a zipped file if it is not a .sql file. Once you selected the file, click on Execute. Instead of uploading the file via Adminer, you can upload it via FTP in the same folder of the adminer.php file. Rename the database backup file to adminer.sql.gz. With a click on Run file the import of this file is started.
Run file the import
Wait until you get the message that the import was successful.

If your host does not allow the use of Adminer, you can give the plugin Adminer for WordPress a try. You can install it via the WordPress admin area and access it via the menü Ari Adminer.
2.3. Restore the WordPress files with FileZilla from a backup
Please note: For restoring the WordPress files with FileZilla, it is not relevant where you have saved your backup to. It can be Amazon, Google Drive, on a FTP server or any other destination: get the backup archive from there and unzip it to get the WordPress files (see section Contents of the backup archive) before you continue with the tutorial.
Restoring the WordPress files is simply copying the files from your backup to the folder of your WordPress installation via a FTP client like FileZilla. Follow these steps:

Install the FTP client FileZilla on your computer if you don』t have such a program. You can find the download here. You don』t need to download the FileZilla Server, only the client.
Get the credentials for your FTP access. If you don』t know them, please contact your host.
In FileZilla, go to File → Site Manager, add a New Site and add your credentials.
To open a connection to your web server, click on Connect.
After the successful connection, you can see the files on your computer on the left and the files on your web server on the right.
On the left side, navigate to the folder of your BackWPup backup. On the right side, navigate to the folder of your WordPress installation.
Select all files on the left side that you want to upload.
Please note: Only upload the WordPress files, NOT: the database, the file SiteName.pluginlist..txt, the file SiteName.wordpress..xml, the file manifest.json and the file backwpup_readme.txt.

With a right click on the selection a context menu opens, where you can start the upload. It can take up to a few minutes, depending on how big the files are. You can see the progress and possible errors in the bottom area of the FileZilla window.

Please note: Files, which are not backed up by BackWPup (depending on your settings), need to be uploaded additionally. Missing plugins and themes can be re-added via the WordPress backend afterwards. If you chose the option for excluding thumbnails in backups, you need to regenerate them again. For this, you can use the plugin Regenerate Thumbnails.

What is the difference between BackWPup Free and BackWPup Pro?

What is the difference between BackWPup Free and BackWPup Pro?

What is the difference between BackWPup Free and BackWPup Pro?
BackWPup Free offers you some features for automated backups of your website. The Pro version offers you a lot more. The following feature table shows the important features as well as the differences between BackWPup Pro and the free version.

Feature
BackWPup FREE

BackWPup PRO

10 Mio. downloads

Complete database backup

Complete file backup

Multisite Support

Database check

WordPress XML export

List of installed plugins

Backup archives management

Log file management

Start jobs per WP-Cron, URL, system, backend or WP-CLI

Log report via email

Backup to Microsoft Azure

Backup as email

Backup to S3 services (Amazon, Google Storage, Hosteurope and more)

Backup to Dropbox

Backup to Rackspace Cloud Files

Backup to FTP server

Backup to your web space

Backup to SugarSync

Backup to Amazon Glacier

Backup to Google Drive

Backup to OneDrive


New!

Backup to HiDrive


New!

Restore manually uploaded Backup Archives

Restore BackUp Archives from local server folder

Restore BackUp Archives from FTP Server

Restore BackUp Archives from DropBox

Restore BackUp Archives from Google Drive

Restore BackUp Archives from S3 Services

Encrypt Backup Archives

Restore Encrypted Backups

Custom API keys for DropBox and SugarSync

XML database backup as PHPMyAdmin schema

Database backup as mysqldump per command line

Database backup for additional MySQL databases

Import and export job settings as XML

Wizard for system tests

Wizard for scheduled backup jobs

Wizard to import settings and backup jobs

Differential backup of changed directories to Dropbox

Differential backup of changed directories to Google Drive

Differential backup of changed directories to Rackspace Cloud Files

Differential backup of changed directories to S3

Differential backup of changed directories to MS Azure

Premium support

Automatic updates

BackWPup License Update

BackWPup License Update

BackWPup License Update
Starting from version 3.7.1 the licensing system of BackWPup has been updated, and the info needed to activate the license are now different, depending on the plugin version you currently use.

Table of Contents

Version minor or equal to 3.7.0 requires an Api Key and an Email AddressVersion above 3.7.0 requires a Master Api Key and a Product Id code
Version minor or equal to 3.7.0 requires an Api Key and an Email Address

The Api Key is available in your My Account page, in the Dashboard or Api Key section and it is now named as Deprecated.

The purchase Email is available in your My Account page, in the Account Details section.

You can use these information to activate your license, inserting them in your plugins settings license tab.

Version above 3.7.0 requires a Master Api Key and a Product Id code

The Master Api Key is available in your My Account page, in the Dashboard or Api Key section. This key can be used to activate any of the products you purchased.

 

The Product Id identifies the product purchased and it is available in the My Account page, in the Dashboard or Api Key section.

You can use these information to activate your license, inserting them in your plugins settings license tab.

How to backup WordPress to HiDrive

How to backup WordPress to HiDrive

How to backup WordPress to HiDrive
In this post we explain how to connect your HiDrive cloud storage with BackWPup, and we also provide an example about how to perform a back up in HiDrive.
Let』s dig deep into the topic.

Table of Contents

Connect BackWPup with HiDriveRun HiDrive Job
1. Connect BackWPup with HiDrive
In order to save a WordPress backups to HiDrive you need first to activate an HiDrive storage cloud plan. If you don』t have one account yet, you can create one here.
After installing and activating BackWPup Pro version 3.8 or above in your site, proceed as follow in order to back up your WordPress site to HiDrive destination.

Create a new job going to BackWPup → Add new Job or edit an existing job going to BackWPup → Jobs
In the tab General go to the section Job Destinations and select the Backup to HiDrive checkbox.
Select the Backup to HiDrive checkbox
A new tab appears called To: HiDrive, where you can configure the settings for HiDrive. If the connection is not active yet, in the Authentication field a red highlighted Not authenticated! message will appear.
In the App Access to HiDrive text field click 「Get HiDrive Authorization Code」 button.
HiDrive tab configuration settings
The link redirects you to the login page in HiDrive: provide now the credentials in the login form
Authenticate in HiDrive Login Form
Allow permission to access the HiDrive storage
Allow access to storage
As a result you get an Authorization code, copy the code
HiDrive Authorization code generation
Head back to BackWPup To:HiDrive settings page and paste the Authorization Code into the 「App Access to HiDrive」 field and click on the 「Save changes」 button
Paste the Authentication Code into the 「App Access to HiDrive」 text field and save the changes
After that action a new green message informs the user that the plugin is now Authenticated
BackWPup is now authenticated in HiDrive

2. Run HiDrive Job
Now that the HiDrive storage is properly configured and enabled in BackWPup let』s proceed showing how you can create a back up archive of your site and store it in HiDrive.

Go to BackWPup → Jobs and on the link of the job created in the previous section click on Run now link, this way the job starts processing your sites, creates the BackUp and then upload it on the HiDrive destination
Run the Job to create a back up in HiDrive
After the process is complete head to your HiDrive account and check that the back up archive is correctly uploaded and visible
The back up archive created is available in the HiDrive server

Backup Type Synchronize File by File to Destination

Backup Type Synchronize File by File to Destination

Backup Type Synchronize File by File to Destination
During the first backup with the BackWPup setting synchronize file by file to destination, BackWPup copies all the files that shall be backed up uncompressed into a folder of your backup destination, for example Google Drive. When backing up data the next time, BackWPup backs up only those files into the folder which changed since the last backup. In case you back up the database too, BackWPup always transfers the database completely.
In comparison to the backup type backup archive, this setting causes that only the changed files are backed up. This speeds up the backup process. Moreover, the backup is uncompressed.
This feature behaves like incremental or differential backups.
Synchronize files to Google Drive with BackWPup
Synchronize file by file to destination
When you create a new backup job, choose the backup type synchronize file by file to destination on the general settings site.Imagine you made the first backup with BackWPup Pro on Monday. Then, the tuesday backup will only back up the data which changed since Monday (synchronize file by file to backup destination).
Job 「Synchronize file by file to destination」 started.
The Wednesday data backup will only overwrite the data which changed since Tuesday and so on. There is no file compression as zip achive, tar archive or other archive types.
BackWPup files synchronized to Google Drive folder
The benefit of this synchronisation is quite obvious: Less data need to be backed up. Therefore the backup process is faster.
This feature is not compatible with encryption. So you can speed the back up process, but your data in the chosen destination will be in plaintext, not encoded.

WARNING: Link not following

WARNING: Link not following

WARNING: Link not following
When the following message is displayed while you are creating a backup
WARNING: Link /folder_1/folder_2/…/folder_n not following,

then BackWPup has found a so-called 「symlink」 and will exclude it from the backup to prevent problems. The inclusion of symlinks in your backup could result in an endless loop.
Symlinks are not real directories; they are merely references to a directory located elsewhere. Find out more about symlinks here.
There are two things you can do to prevent this warning:
a) manually exclude the directory indicated in the warning from the backup if a backup of this directory is not mandatory (which would be the case for e.g. the log directory).
Go to BackWPup → Jobs via the backend, select the relevant Job and click the tab Files. There you will find various options for excluding files.

Important: The tab 「Files」 will only be visible if you have previously indicated a backup of the files in the tab 「General」.

b) include the actual folder in the backup if you need to back up the directory. The relevant settings are available in the tab Files → Extra folders to backup, where you specify the absolute path of the directory for backup. Determining the actual folder is an advanced topic. Please contact your hosting provider if you don』t know how to do that.

Warning: File name too long to be saved

Warning: File name too long to be saved

Warning: File name too long to be saved
In case you save files with the archive format Tar or TarGZ, it may happen that BackWPup reports the warning 「file name too long」.
The reason is that the formats Tar or TarGZ only allow 100 characters as file name lengths. Nonetheless, BackWPup saves files with longer names, but the archive format shortens the names. This may lead to problems during the restoring process.
Example:
WARNING: File name 「wp-content/plugins/bwp-minify/cache/minify_tagdiv_theme,commentreply.min,wpembed.min,js_composer_front._998cbd8e7258ea432e75c51c3cabf110.gz」 is too long to be saved correctly in TarGz archive!
In case you get the warning 「file name too long」, you should consider to do these steps:

Exclude folders like e.g. cache, temp, logs and backups from saving.

Choose zip as archive format

Settings for Log Files

Settings for Log Files

Settings for Log Files
Every time a BackWPup job is running, a log file is created. You can configure the log files under BackWPup → Settings → Logs.
Log Settings

Log file folder – here you can set the folder, where all logs are saved to. It can be an absolute path or a relative path to the wp-content folder. If you』re new to BackWPup, you can leave this setting as it is. It will be automatically generated.
Maximum log files – the maximum number of log files, which will be stored in the folder set above. Old files will be deleted.
Compression – usually log files will be saved uncompressed. If you wish, you can select the checkbox and the log files will be compressed with Gzip.
Logging Level – with this setting you can choose which kind of log file is generated. Usually the log logging level Normal will work for you. If you need support, it』s best to change it to Debug (not translated). For more information about this, read our article Sending in log files for the support. Log files can be translated, which means they will have the language you use in your WordPress installation. Choosing not translated, the log files will be saved in English.

If you click on the button Reset all settings to default, all settings will be restored to our recommended settings.