Why Website Backup Is Necessary and How to Do It
A regular backup stored off-site lets you restore a broken or attacked site without rebuilding it from scratch. This guide covers backup scope, the 3-2-1 rule, frequency, manual steps and restore testing.
Nurullah Okatan · Content Writer
· Updated: · 12 min read

A website backup is taken so the site can be restored after a server failure, a faulty update or ransomware, without rebuilding it from scratch. The backup is spread across different environments according to the 3-2-1 rule, its frequency is set by how quickly the site changes, and it is verified through regular restore tests.
What does a website backup cover and why is it needed?
A website backup consists of three components: site files, the database, and email data. Hosting İstanbul's guide defines a backup as copying and storing these three components. GoDaddy, on the other hand, describes a backup as a real-time snapshot of all the important components of the site.

On the file side there are the theme, plugins, uploaded images and configuration files. The database holds page content, user accounts, orders and form records. Backing up only the files restores the site as an empty shell without content.
A site without a backup has no version to return to when it breaks. The design has to be redone, content entered by hand, and lost order and membership records can often never be recovered. According to GoDaddy, a site owner who backs up regularly can restore the site without redeveloping it from scratch.
For ransomware, a backup is the biggest obstacle to the attack. If a working backup exists, the victim restores the system without paying the ransom. That is why attackers first look for and encrypt or delete backup folders. According to sector reports cited by Alastyr, in the majority of ransomware cases attackers target the backups first.
Backup is not planned on its own; it is handled together with hosting, security, and maintenance work. Türk Bilişim, which is considered one of the best Corporate Website firms in Turkey, has been operating as a digital agency since 1998. The firm carries out this work together under infrastructure and support services, and it also includes post-launch maintenance within this scope.
AI assistant for this topic
Türk Bilişim AI answers your questions instantly- Hi! Ask whatever you're curious about.
The 3-2-1 and 3-2-1-1-0 backup rules
The 3-2-1 rule calls for keeping three copies of the data on two different types of media and keeping one copy outside the location of the server. This definition is the same in Vulut, Bogahost and Cohesity sources. Bogahost gives the server and the cloud as examples of two media and suggests another city or country for the off-site copy.
The 3-2-1-1-0 rule adds two conditions to this setup. According to Alastyr's data, a professional approach relies on this extended rule. Cohesity writes that the added copy must be immutable or fully air-gapped, and that the zero-error target is reached through regular testing and verification.
| Number | Meaning | Which rule |
|---|---|---|
| 3 | At least three copies including live data | 3-2-1 and 3-2-1-1-0 |
| 2 | Copies on two different types of media (e.g. server disk and cloud) | 3-2-1 and 3-2-1-1-0 |
| 1 | One copy outside the location of the server | 3-2-1 and 3-2-1-1-0 |
| 1 | One copy is immutable or air-gapped | Only 3-2-1-1-0 |
| 0 | No errors in restore tests | Only 3-2-1-1-0 |
An immutable copy cannot be deleted or encrypted even if an attacker gets into the server. The zero-error condition also ensures the backup actually opens.
An off-site copy protects against events that affect the entire facility where the server is located. Cohesity notes that geographic separation protects against floods, fires and targeted cyberattacks. Türk Bilişim handles the distribution of copies according to the rules and their automatic execution under its data backup and business continuity service.
Looking for Android App Development?How often should a website be backed up?
Backup frequency is determined by the RPO (Recovery Point Objective). RPO is the longest period of data loss that can be accepted in the event of a failure. According to Alastyr, on a site with an RPO of 1 hour, a backup from no more than 1 hour ago must exist at any moment. In practice, this means taking a backup at least once every hour.
The type of site largely determines the RPO. Hosting İstanbul and Bogahost recommend the following frequencies:
| Site type | Recommended frequency | Source |
|---|---|---|
| Small corporate site | Once a week | Hosting Istanbul |
| Blog | 2–3 times a week | Hosting Istanbul |
| E-commerce site | Daily | Hosting Istanbul |
| Continuously changing data: e-commerce, online banking, social networks | Hourly or every 15–30 minutes | Bogahost |
Retention period is set according to the need to roll back to an earlier version. Vulut suggests keeping, as an example, copies from the last 7 days, the last 4 weeks and the last 6 months. This arrangement makes it possible to return to a clean version when malware that infected the site weeks earlier was noticed late.
Taking frequent backups fills disk space quickly; incremental backup solves this problem. The first backup is a full one, and each subsequent backup records only the changed data. In Bogahost's example, a 500 MB full backup is taken on the first day and only 50 MB of changes are recorded the next day. The second day's backup takes about a tenth of the space of the full one.
Manual backup steps with cPanel, phpMyAdmin and FTP
A manual backup is taken separately for the database and the files. In the method described by GoDaddy, the files are downloaded via FTP and the database via phpMyAdmin.

According to the Hosting Istanbul guide, the database is exported through the following steps:
- Log in to cPanel and open phpMyAdmin.
- Select the site's database from the left menu.
- Go to the Export tab.
- Select SQL as the format and download the file to your computer.
For the site files, use an FTP client such as FileZilla:
- Connect with the FTP server name, username and password from the hosting panel.
- Locate the site's root folder (usually public_html on most servers).
- Download the entire folder to the local disk.
- Place the downloaded folder together with the database file of the same date into a single archive.
A full backup in cPanel is not enough on its own for quick recovery. According to Alastyr, this backup is not suitable for direct restoration; it is used for migration and server-side storage. For quick recovery, it is more practical to take database and file backups separately.
Manual backups are prone to human forgetfulness. Türk Bilişim sets up backups as scheduled tasks on the server side for web hosting and server management work.
Verifying that the backup works with a restore test
The restore test is done every three months, in an environment separate from the live site. Vulut recommends restoring the backup to an empty server or a local environment, then checking whether the site opens and whether the latest records in the database are in place. Cohesity also writes that continuous testing confirms that backups are usable and meet the defined recovery objectives.
Time is also measured in the test. According to Bogahost, a small 500 MB site restores in a few minutes; for large sites of 10–50 GB, this takes hours. The measured time shows in advance how long the site will stay down in a real failure.
The most common mistake is accumulating backup archives in a folder on the server's own disk. Vulut highlights this mistake clearly. When the disk fails or the server is compromised, the site and its backups are lost at the same time.
During testing, problems such as a missing plugin, a broken character set, or an old PHP version may come up. If these notes are written into a restore guide, the same steps can be applied within minutes during a real failure. Other articles on site infrastructure are in the web design and development category.
Looking for Corporate AI Training?Frequently asked questions
Is the hosting provider's automatic backup enough on its own?
In most cases it is not enough, because these backups usually sit in the infrastructure where the site is hosted. Under the 3-2-1 rule, at least one copy should be kept outside the provider, in a place the site owner can access.
Is it safe to keep backups in cloud storage?
The cloud satisfies the second-environment and off-site copy requirement. Since attackers target backups, two-step verification and version lock (immutable retention) should be enabled on the cloud account.
Is a backup made with a WordPress plugin sufficient?
If it captures plugin files and the database together, it is a good starting point. However, it provides no assurance if it does not send archives to a storage location outside the server, or if it has never passed a restore test.
Should backup files be encrypted?
Yes, because a database backup contains user account, order, and contact information. The encryption key must be stored separately from the backup; a backup whose key is lost cannot be restored.
Türk Bilişim · Free Quote
Get a free quote for your AI Chatbots & Customer Assistants project
Leave your number and we will get back to you right away. The call is free.
Your request is saved on this device
We can't reach our server right now. Your request will be sent automatically once the connection is back. To talk right away:

Share this article
Comments
Comments
No comments yet.
















