Getting Started With WordPress Optimized Template
- This article applies specifically to Liquid Web’s WordPress Optimized Template servers.
- Restoring a site from backup will completely overwrite all of its existing content (both the files and the database). If you are not completely certain that the existing files will no longer be needed, you may wish to back up the database and download the database backup and site files locally using SFTP with a client such as FileZilla.
WordPress Optimized Template sites installed via the Sites tab in Manage automatically are backed up each day, with the server retaining the 10 most recent backups. You can easily restore any site from an available backup in the Sites dashboard in Manage.
Step #1: Open the site in the Sites dashboard
Click on the [+] next to the domain name to expand the window, then select the desired restore point from the Automatic Backups section.
Step #2: Restore the Site
- After clicking on the radio button next to the desired restore point, click the Restore button to restore the site. A confirmation window will pop up to remind you that you will be overwriting the existing site with the contents of the backup. Any changes made to the site since the chosen backup was made (comments, posts, etc.) will be completely overwritten and can not be recovered. If you wish to proceed with restoring the site, click the Restore WordPress Domain button.
- The restoration process will begin, and you will see a banner at the top of the page alerting you that the process is under way. The time it will take to complete depends entirely on the size of the site directory and database.
Now that you have an image of a storm server, you can create new servers from that image. Here’s how to do just that:
Continue reading “Restoring a Storm Server from an Image”
We have written previously about regularly backing up Storm Servers, but that only covers automated image backups. With the Storm platform, it is possible to take image snapshots of your server whenever you wish.
Continue reading “Creating Storm Server Images”
While it is always important create a backup of your server’s data, some backup solutions can be costly and unwieldy. Creating a backup of a Storm server is neither of those things. Instead, it’s cost efficient and easy!
Continue reading “How to Create a Backup of a Liquid Web Storm Server”
MySQL via Command Line 101: Basic Database Interaction
While automated backups are important, sometimes you just want to take a quick and dirty snapshot before making a change to your data. When changing files in Linux, you can simply cp a file to another name, and cp it back if your change does not workout. With MySQL, it is not quite that simple, but it is by no means difficult.
Continue reading “How to Back Up MySQL Databases From The Command Line”
While it is a good and useful thing to have entire server backups, sometimes you only need to restore one or two domains. In these situations, cPanel backups make it easy for one to restore just a single site from the Web Host Manager (WHM) interface, or from the command line.
Continue reading “How To: Restore a Domain From cPanel Backups”
Individual accounts within cPanel have the ability to create backups for their site via the cPanel interface. The backup that is created via this method will backup the user’s home directory, any sql databases owned by the user, and any cPanel configuration settings for that user.
Continue reading “Creating a Backup for a Site in cPanel”
Most of us have had a time (or two) when we’ve accidentally deleted something or have had a disk crash that led to data loss. This can be a painful, harsh lesson in maintaining backups – don’t let it happen to you (or happen again!)
Continue reading “Levels of Backup Data Integrity”
- This article applies specifically to configuring backups in Plesk 12.5.30.
- We’ll be working from a Liquid Web server running Microsoft Windows Server 2012 R2, but these steps apply to any server running Plesk 12.5, regardless of operating system.
- You can use the links below to quickly jump to a specific section:
Configuring Backup Settings
- From Plesk’s Tools & Settings panel, locate the Tools & Resources menu and click on Backup Manager.
- Click the Settings tab to configure backup settings:
When configuring your backup settings, there are several items to which you will want to pay particular attention:
- Maximum number of scheduled backups to store: It is critically important that you consider both the total size of subscriptions and the server’s available disk space when determining how many backups to store. If you do not set a reasonable limit, you could cause the server to run out of disk space, affecting both server stability and service availability. Moreover, Plesk will continue to attempt to create backups even if there is no disk space available; in that event, any newly-created “backups” will be zero-k (empty) files, overwriting the oldest existing backup in turn until no viable backup files remain. As Plesk backups are not managed by Liquid Web, you will want to take care when configuring this setting.
Note: Please note that you can manually download backups from Plesk at any time. If you find that your available disk space is insufficient to retain the number of backups you wish to store, and you do not wish to download them for local storage, you always have the option to purchase additional storage (an additional drive or a Storm® Block Storage device, depending on your server type).
- Do not compress backup files: If you select this option, compression will be disabled and each backup file will take up the same amount of space on the server as the full account.
- Allow setting up personal FTP backup storage on the local server: This option allows users to configure backups for their Plesk accounts in their own FTP directories on the server. If enabled, this option will double the amount of disk space used upon creation of each backup, potentially causing the server out of free disk space. If you elect to activate this option, please adjust your backup retention accordingly.
- Password type: If you choose to encrypt the backups with Plesk’s encryption key (which is unique to each Plesk installation), you will not be able to restore the backups to any other server. Instead, it is recommended that you use the Specified password option to set a password; password-encrypted backups can be restored on any server.
Manually Backing up the Entire Server
By clicking the Back Up button in Backup Manager, you can manually take a full or incremental backup of the server configuration or server configuration and content:
From Backup Manager, click the Schedule button to set up automatic full or incremental backups of the domain configuration, mail configuration and content, and/or user files (including databases):
Note: Incremental backups take up less space and are less resource-intensive because only files which have changed since the last backup are copied over. They also allow you to more quickly restore individual files. However, you only ever will have a single restore point. In the event that backups ran after a file was deleted or damaged, the original would be overwritten.
Restoring a Backup
- From Backup Manager, click the date of an available backup to begin the process of restoring from the backup. If the backup is not stored on the server, you can click the Upload button to upload it to the list.
- On the backup restoration page, use the Type of object to restore select menu to choose whether you want to restore the entire subscription or only a part, such as the mail account, database, or sites.
- The restoration will begin once you click the Restore button.