What is the Difference Between File Backup and Image Backup?
by Nathan.Fouarge, on Jul 14, 2014 7:42:25 PM
The whole backup and data protection space is filled with a lot of nomenclature that if you do not already know the abbreviations, the specific words and phrases that are used, or concepts that you can become lost very easily. In this article I am going to go over two concepts that seem to come up all the time in NovaBACKUP’s Technical Support discussion with customers or prospective customers. These two are the difference between file level and disk image backup.
What is a Disk Image Backup?
Starting out with the concept of disk image backup which in itself can be called a number of different names such as: bare metal backup / recovery (BMR), disaster recovery backup, ghost backup, image level backup, block level backup, system image recovery or a clone of your machine. This is a very simple to configure type of backup where you normally have to just select an entire drive, partition, or entire machine which typically backs up the entire selection you have selected.
Some software such as NovaBACKUP for example, allow you to backup changes since the last full disaster recovery backup. Where disk image backups really shine is in a complete disaster type of situation. For instance when your hard drive dies, your Windows will not boot or is corrupt, your machine is stolen, an upgrades goes horribly wrong, or other major disaster that requires a complete rollback of the entire machine and do a system image recovery. While most disk image backup products, NovaBACKUP included, can access single files from the disk image backup in case of the need to restore a single file, file level backups are more suited to file level restores.
What is a File-Level Backup?
File level backups are the most common type of backup out there and for good reason. They are very simple to understand and very simple to make sure they are good. File level backups basically come down to you selecting some files and folders that you want to back up and then where you want those file level backups to go. File level type of backups typically allow for more granular options for backup and restore of things such as Exchange, SQL, System State (Registry, Active Directory, and other things), along with the ability to exclude a lot of other things that you probably do not want to backup unlike most disk image backups. File level backups also typically give you a more flexible way of doing backups, scheduling, and normally smaller backups than disk image backups.
What Type of Backup is Recommended?
Now that you a rough idea of the difference between file backup and image backup, you may be wondering which backup type should you use? I would suggest you use both types. A good typical backup setup would include a disk image backup (disaster recovery) once a month, a full file level backup once a week, and a differential file level backup (backup that backs up all files since the last full file level backup) every day other than the full backup day. This type of schedule will give you an easy quick way to get files and folders back, which is where a majority of the restores we see happen, along with giving you a good disk image base while being backup space conscious.
I would also suggest that before any major change to the machine that you are backing up to do a manual disk image backup. This can include service packs to production type software such as Exchange, SQL, or other software that is critical to your business, new hardware, or installation of new software. That way if something goes wrong with that change you can bring the machine back to where it was before the change very quickly. These are obviously just my opinions as what we see as something very easy to setup within NovaBACKUP along with giving great protection to your machine. If you happen to be utilizing another type of backup software that does not include both disk image and file level backup capabilities in it, it might be worth reevaluating the software you are using and to look at the downtime you are willing to accept when something happens and how much that will cost you.