CloudBerry Backup supports a broad range of data protection scenarios, including system state and image-based backup and recovery plans. By using these tools, you can solve several system-wide issues. In this article, we are going to evaluate their possibilities and strengths in depth, and look at how to create image-based and system state backups.
System State Backup
System state backup is a data backup type that only includes crucial OS data. CloudBerry Backup extends this function with the ability to store the data on a cloud storage of your choice.
Typical Windows system state backup contains the following data:
- Windows System Registry.
- Performance Counter Configuration information.
- Component Services Class registration database.
- Boot and system files, including those protected by Windows File Protection (WFP).
- Configuration of system-dependent Microsoft applications, such as Certificate Services, Active Directory, IIS, etc.
This backup type can help you solve issues such as: configuration-dependent system faults (for example, BSOD errors) and crucial file or system registry corruption of any kind. The main point here is that you cannot manually select data to restore since system state is only backing up or restoring as a solid object. Since it contains only necessary data, the backup is small in size and can be completed quite quickly.
You can create a System State backup job using the Image-Based button on the main window’s ribbon:
- Press Image Based button in the top left-hand corner of the main window.
- Proceed to Select Backup Storage step and point to the necessary storage account.
- Then select backup storage and backup plan name, and choose System State.
- In the next step you should select drive partition for storing temporary backup data:
You will then be able to enable the Block level backup option that allows you to make a copy of data blocks only changed since the last backup session.
Image-based backup creates a system image that includes the exact copy of all system drive partitions with corresponding metadata and boot records, OS and apps files. It is similar to having a separate copy of your hard drive’s data.
Image copy created with CloudBerry Backup is stored in one file, which you can keep locally or upload to a cloud storage. Unlike system state backup, image-based data copy can be used granularly – you can select either the whole system’s image or only a few user files.
This backup type is helpful in most disaster or failure cases, including loss of user or system files, corrupting the system’s configuration, moving OS to the new hardware, hard drive crash etc. For example, you can restore your server in a few hours, even if most of the hardware is physically broken – simply get hardware with enough resources and restore the previous server images on it.
There is however, one major drawback of using this backup type in any case – its data file size. Since you need to have the entire system’s data, backup tool will spend a lot of time carefully copying all system drives and corresponding partitions. If this backup started on a high-loaded system in business hours, the backup window would significantly expand and the system’s performance may deteriorate.
You can configure Image-based backup similarly to previous procedures, yet with small differences:
- Repeat steps 1 and 2 from the previous chapter and select Image-Based Backup as a backup type.
- Next, you need to select the backup scope. In most cases you need to select Backup only system required partitions, that include system and boot volumes.
At this time, you have the choice of selecting the Use block level backup option. You can also use the Synthetic Full Backup feature for image-based backups in CloudBerry Backup. This enhancement decreases the amount of data uploaded to the cloud and accelerates the overall process – you can learn more in the Synthetic Full Backup with CloudBerry Backup article.
Configure the rest of backup wizard steps as with any other backup plan.
System State and System Image. The Comparison
You can obviously, use Image Based Backup for data and server protection of any kind. Keep in mind though, that it is one of the slowest backups that will use a lot of space in your backup repository. Using System State backup allows you to quickly “snapshot” the system prior to, for example, configuration changes – you can revert the system to the previous state relatively fast. You cannot, however, use System State backup for user data protection or in cases of significant OS malfunctions.
You can note other considerations in the quick comparison table below:
|System State Backup||Image-Based Backup|
|Allows system configuration and crucial system file(s) restoration.||Yes||Yes|
|Enables roll back from the improper system configuration.||Yes||Yes|
|Allows recovery of the server in any case of disaster.||No||Yes|
|Suitable for server OS cloning or relocation.||No||Yes|
|Allows restoration of certain user files, granularly.||No||Yes|
|Suitable for fast “snapshot” backup.||Yes||No|
|Suitable for regular backup of the heavy-loaded server.||Yes||No|
It is not important which backup type you prefer since CloudBerry Backup supports both with ease, as well as many other backup and restoration features. Download the new CloudBerry Backup tool and check out its advantages using the FREE 15-day trial. If you have any questions left – contact us in the comments.