Uploading a WP MyBackup/custom backup and restoring its content is just one drag & drop away

Quickly backup and restore your website with one click

The CLI interface has an exhaustive list of switches/options. This is very useful when you write a script that schedules the backup at OS level.

The CLI interface allows you to run the backup from terminal like any other command. The CLI interface has about 100 different switches/options.

The backup profiles can be run at demand or scheduled to run later as a background task

The backup profile can be created with ease thanks to a step-by-step user-friendly Wizard interface

This option allows you to create many fine-grainer backup profiles

An upload threshold helps in balancing the network usage

Configure the application's proxy and SSL settings

Whether you want to rename, delete a file or directory, or just to download a remote file it is easy like a walk in the park.

The file explorer looks and works like any other file explorer. It allows you to navigate through the directory structure with just a single click, it allows you to create/rename/remove directories and download remote files.

With the addon there are no limits. You may include into your backup whatever folder your system can access.

The WordPress version limits the access to the blog files only. At the same time it groups all files by their scope which is a nice feature 🙂

mysqldump is a powerfull tool that allows you to create natively the MySQL database script

The payed version allows to backup any remote MySQL database

The free version is limited comparing with the payed version

By setting a threshold for the CPU usage you make sure your website visitors still have a good browsing experience while your system is backing up your files

Sometimes the native OS compression toolchain proves to be faster and more efficient than the PHP internal compression implementation. For instance the PBZIP2 uses all available CPUs cores.

The benchmark result will print-out few benchmark metrics that allow you to choose the right toolchain for the job

The benchmark test provides a progress feedback each second. You can abort the test whenever you want.

Benchmark either your files or a utterly random file

Benchmark different settings scenarios to find out which toolchain is better to use

Very fast compression speeds, rivaling a straight copy loop. Mediocre compression ratios - you can usually expect about 40-50% compression for typical binary data

It will not compress your files like TAR.BZ2 but it's super fast and you don't need to install any extra software. Great for Windows and Mac users.

The encryption key and initialization vector (iv) are automatically generated to ensure the strongest encryption.

OpenSSL offers AES encryption with an incredible speed. When available the OpenSSL implementation is preferred (30x faster than Mcrypt).

The encryption key and initialization vector (iv) are automatically generated to ensure the strongest encryption.

MCrypt offers AES encryption with a reasonable speed. When available the OpenSSL implementation is preferred (30x faster).

One nice feature is that you can always check the original log that could provide even some more details about the job.

You can always check what was transfered or why it wasn't transfered.

The job history detail tells you, among all small details about the job itself, what was the system status at backup/restore time.

The job history list can be filtered out using various predefined criterias.

The log can be viewed in any text editor as it is just a plain text file.

The full log files can be downloaded locally

With cURL we capture all you need to know about what is sent/received from to/from any remote server.

The cURL log files can be downloaded locally

When mail is not delivered successfully, the first order of business is to look for errors that prevent mail library from working properly.

This option will check if you system fulfils the minimal criteria for this application to work like the installed hardware/software.

The messages are well organized and are bound directly to the job history.

You don't have to read the whole log to know that you have errors or warning.

Forecasts the media usage trend by analyzing the historical data

Shows the current system resources usage: CPU, memory, network, disk.

Shows the backup state (complete|partial|failed) grouped by destination (target)

Shows the free/used space by media type (eg. disk, Dropbox, Google)

Shows the backup state (complete|partial|failed) within last month (1-31)

Shows the backup status (running|aborted|completed) within a date interval grouped hourly (0-24)

Shows the CPU usage (max|avg) within a date interval grouped hourly (0-24)

Shows the compression rate within a date interval grouped hourly (0-24)

Uploading a WP MyBackup/custom backup and restoring its content is just one drag & drop away

Quickly backup and restore your website with one click

We keep this information in history and use it later on restore

Two restore methods are available: manual|assisted. The preferred method is "assisted by Wizard".

The progress of the restore process is synced every one second. You may even abort the restore process if that's what you want.

Before launching the restore job you can review and refine your selections.

Some files may already exist at the restore destination. You may opt to overwrite or rename them.

The backup can be restored at its original location or at a custom location specified by you.

Select which components to restore: files and/or database.

Thanks to the job history the available restore points can be easily located no matter where the backup was transfered. You may however search an alternative custom location (like disk, cloud, etc) and restore a backup from there.

The whole restore process is guided via a user-friendly Wizard interface

We can always see the full log even of the background jobs run by WP-Cron.

Sometimes is useful to see what WP-Cron job does in background. It is even more awesome if you can abort it.

You can always tweak the schedule running date/time (see also the Next Run field).

The WP-Cron entry is created and removed when the scheduler is enabled respectively disabled.

The OS scheduler command is generated automatically based on your changes