Backups are copies of website, database or hosting data that can be used to recover information after accidental deletion, corruption, failed updates, malware, configuration errors or other service issues. For Apexhost customers, backups are an important part of managing web hosting safely because many hosting services are self-managed, which means customers are responsible for the changes they make within their hosting environment.

This article explains what backups are, why they matter in a web hosting environment, the main types of backups relevant to Apexhost services, and how hosting space and SQL Server database backups generally work. It also outlines important limitations and best practices so you can better protect your website and related data.

In web hosting, a backup is a separate copy of important service data stored so it can be restored later if needed. Depending on the service, this may include website files, databases, DNS settings, FTP accounts, mail-related settings, or other hosting resources.

Backups are commonly used before major website updates, control panel changes, migrations, application upgrades or database work. They are also useful after unexpected issues such as broken websites, missing files, damaged databases or failed configuration changes.

A backup is most useful when it is created before a problem occurs, stored somewhere accessible, and tested or verified so you know it can be used when needed.

Without a usable backup, recovering lost website or database data can be difficult or impossible. Even a small mistake, such as deleting the wrong file or changing the wrong database table, can cause major disruption to a website or business service.

Backups help reduce risk by giving you a recovery point you can return to if something goes wrong.

* Common reasons to create backups include:

* Before updating a website, plugin, theme or custom code.

* Before changing DNS, database or hosting settings.

* Before migrating a website to a new hosting environment.

* Before importing or editing large amounts of data.

* As part of regular website maintenance and business continuity planning.

Backups are not only for emergencies. They are also a normal part of safe change management.

Different services may use different backup methods. In a typical hosting environment, the most relevant backup categories are hosting space backups and database backups.

* Hosting space backups usually include a broader set of hosting resources, such as website files, DNS zones, websites, FTP accounts, databases, database users and other hosting-space-level items.

* Database backups usually capture the contents of a database so that application data can be restored separately from the rest of the hosting account.

* File-level backups focus on website content such as HTML, PHP, images, documents, scripts or application files.

* Local backups are stored on your own computer or local network.

* Hosting-space backups may also be stored within a hosting space if that option is available in the control panel.

Which method is most appropriate depends on what you are trying to protect and how quickly you may need to restore it.

A hosting space backup is designed to copy a broader set of hosting resources in one operation. Based on the available Apexhost hosting space backup guidance, the control panel may allow you to back up items such as domains and DNS zones, websites, FTP and mail accounts, databases, database users, files and other hosting space resources.

This type of backup is useful when you want a wider snapshot of a hosting environment rather than only a single website file set or database.

The general process is:

1. Open the Hosting Space home page in the relevant control panel.

2. Select the Backup option from the tools area.

3. Enter a backup name.

4. Choose the backup destination.

5. If available, choose the target hosting space and folder where the backup file will be saved.

6. Start the backup process.

If more than one hosting space is available under the account, it may be possible to save the backup into a different hosting space, such as a separate backup space if one has been provided.

To restore a hosting space backup, the documented process is generally:

1. Open the Hosting Space home page.

2. Select the Restore option from the tools area.

3. Choose the hosting space where the backup file is stored.

4. Select the backup file.

5. Start the restore process.

One important limitation is that a hosting space backup restores the whole space rather than selected individual items. However, the restore process may skip items that already exist in the destination space.

[Screenshot: Hosting Space home page showing Backup and Restore options]

For customers using SQL Server in a Windows hosting environment, SQL Server database backups provide a way to copy database contents so they can be restored later if needed.

According to the Apexhost SQL Server backup guidance, the backup process generally works from the database properties screen.

1. Open the SQL Server database properties screen.

2. Select Backup.

3. Enter a backup name.

4. Choose whether to download the backup immediately or copy it to a folder within your hosting space.

5. If available and appropriate, enable ZIP Backup to compress the backup file.

6. Start the backup.

SQL Server backups are created in BAK format. These files can be large depending on the size of the database and its transaction log. ZIP compression may help reduce the final file size for storage or download.

To restore a SQL Server database, the general documented process is:

1. Open the SQL Server database properties screen.

2. Select Restore.

3. Choose the backup file from your local computer, or select a file stored in the hosting space if that option is available.

4. Start the restore process.

The SQL Server database properties screen may also include a Truncate Files option, which is used to reduce the size of database data and log files. This is a separate action from a backup and restore process, but it may be relevant when managing large databases.

[Screenshot: SQL Server database properties screen showing Backup, Restore and Truncate Files options]

Backups are helpful, but they are not a substitute for planning, verification and safe change management.

* A backup created after data loss may not help recover the missing data.

* A single backup copy may not be enough for important business data.

* Large backup files may take time to generate, download, upload or restore.

* A database backup does not always include website files, and a file backup does not always include database contents.

* Restoring a backup may overwrite current data or settings depending on the tool and restore method used.

* Hosting space restore operations may apply to the whole space rather than an individual item.

* Compressed backups may be easier to store, but they still need to be retained securely and accessibly.

If your website or application is business-critical, it is good practice to maintain more than one backup copy and keep at least one copy outside the live hosting environment.

* Create a backup before making major website, application, database or DNS changes.

* Keep backup filenames clear and meaningful so they are easier to identify later.

* Store important backups in a safe location separate from the live production environment where possible.

* Verify that the backup completed successfully before relying on it.

* Keep both website files and databases backed up if your site uses a database-driven application.

* Be especially careful before restoring a backup, as current data may be replaced.

* Limit access to backup files because they may contain sensitive website or database information.

* Review backup size regularly if you manage large websites or SQL Server databases.

Regular backups are one of the simplest ways to reduce the impact of hosting issues, user error and failed changes.

This can happen when a website has large files, when a database has grown significantly, or when SQL Server transaction logs increase the size of the backup. If available, use ZIP compression for SQL Server backups and review whether old files, logs or unused data should be cleaned up before future backups.

The exact location depends on the hosting control panel and service type. Check that you are managing the correct hosting service and that you are in the relevant hosting space or database properties area.

If you need protection for the full hosting environment, a hosting space backup is usually more suitable. If you only need a copy of the application data stored in SQL Server, a database backup may be sufficient. Many websites require both files and databases to be recoverable.

This may happen if the backup did not include that item, if the wrong backup file was selected, or if the restore method works at a whole-space level rather than at an individual item level. Review what the backup actually contains before starting another restore.

Do backups include everything in my hosting service?

Not always. The contents depend on the backup type and the control panel feature being used. A hosting space backup is broader than a single database backup, but you should still confirm what is included.

What format is used for SQL Server backups?

SQL Server backups are generally created in BAK format. They may also be compressed into a ZIP file if that option is selected.

Should I back up my website before making changes?

Yes. Creating a backup before major changes is strongly recommended.

Can I restore only one item from a hosting space backup?

Based on the documented guidance, hosting space backups restore the whole space rather than selected individual items.

Shared Hosting (Web Hosting)

Linux Hosting (Web Hosting)

Website Migration (Web Hosting)

Choosing the Right Hosting (Getting Started)

Welcome to Apexhost (Getting Started)

Viewing Emails (Apexhost - Client Area)

If you require further assistance, please contact Apexhost Support at support@apexhost.com.au.