KB Logo

TOLIS Group Knowledge Base

Browse KB by category:
Go to KB #:
Glossary
Email   Bookmark



Image based backups versus file-by-file backups. Competitive or Complimentary Technologies?

Views: 10296
Votes: 1
Posted: 02 Oct, 2007

Image-based Backup Versus File by File Backup

Competitive or Complimentary Technologies?

Methods of System Backup

When backing up data from a computer system, there are many different methods available. Some more reliable than others. The most popular method is to copy the files on your system, one by one, to your archive device. A file-by-file backup. There are many variations on this method which are referred to by different names: incremental , differential , full, grandfather - father - child, and many others. Another method, less often used, is based on the process of copying the entire contents of a given disk drive. Instead of backing up just one file - for example: C:\DOS\FORMAT.COM - you would backup each sector on the disk as raw data, creating an Image of the entire disk contents. This last method is referred to as image-based backup.

When should I use image-based backup?

Image-based backup provides a mechanism that allows you to more completely recover a crashed system without having to spend time dealing with partitions, disk geometries, drive letter assignments or drive formatting. Whatever partitions or formats were defined on the original disk will be restored when the image is rewritten onto the new disk drive.

This way, you have rescued everything that was on the drive in both the user accessible data areas as well as the system areas, including the master boot record (MBR), partition table and any partition-based boot records. This last, but important step, is almost always overlooked in a file-by-file backup scheme unless special steps are taken to ensure that they are backed up, such as special boot recovery disks or a method that copies these system areas into files on the user accessible areas.

What special situations does image-based backup create?

Since image-based backup only copies raw data, backups made using this method have no concept of the files involved or mechanism for dealing with the restoration of a single file. This means that restoring a system based on an image-based backup is an all or nothing operation - there is no way for you to recover a single file from within the image-based backup.

Also, when using this type of backup, you need to be sure that the tool used to create the backup provides a mechanism for adjusting certain disk parameters in the event that the disk that was backed up has different geometries than the replacement disk. These differences could include a difference in the size, number of heads, number of tracks per cylinder or even the numbers or size of the sectors in a given track.

Finally, image-based backup almost always requires that your system is booted into a maintenance mode to ensure that the disk contents don't change during the backup operation. Since this requires that you shut your server down to perform the backup operation, it is not the best option for daily backups when your servers are running in a 7x24 environment.

When is file-by-file backup better than image-based backup?

Any time that you may need to recover subsets of data from a backup (a single file, a user's directory, a system configuration file), file-by-file backup offers the best mechanism for recovery. You should not have to restore an entire image just to recover a few files.

And, as mentioned above, when you are concerned with backing up server or high availability systems, file-by-file backup allows you to backup the system without interfering with its normal operation.

So which should I use?

This is not an either/or situation. Each method has its strengths and weaknesses. However, a combination of both daily file-by-file backup for your simple recovery needs ("Hey Don, I deleted the '97 payroll files by mistake. Can we recover them?") and weekly or monthly image-based backup for serious system disasters ("Hey Don, why is the system making that screeching noise? And what's that smell?") will provide you with the peace of mind that a complete system backup and disaster recovery solution can deliver.

How do I know which tools are right for me?

Select your image-based tool based on a few simple rules:

  • Does the product provide data verification to ensure that the data really did get written to your backup device properly?
  • Does it work with the backup device you use or do you need to add new hardware to support the way it works?
  • Does it get all necessary information to successfully recover your system in the event of a fatal system crash?
  • Is the backup and recovery process easy enough for a non-technical user to operate?
  • Does it take into account any geometry differences in the event that the replacement drive is not of the same size / geometry / manufacture as the original drive?

Select your file-by-file backup tool based on similar simple rules:

  • Does the product provide data verification to ensure that the data really did get written to your backup device properly?
  • Is the product easy to use?
  • Does it provide the ability to perform backups based on file dates (incremental/differential)?
  • Does it allow you to run your backups in a scheduled mode?

Summary

As you can see, image-based backup and file-by-file backup are not competitive technologies. Together they help create a backup and recovery strategy that will make your recovery from a simple file deletion or a full system crash a non-event.

Others in this Category
document What are the proper settings for my tape drive or library and how does the BRU I/O buffer work?
document How to get OS X to mount drives on boot rather than login and leave them mounted when you logout
document I think I found, or have found, a bug. How do I report this?
document Tape Drive Performance Figures
document Big Endian vs. Little Endian. What does this mean?
» More Articles



RSS
Powered by KnowledgebasePublisher
Page Load Time: 0.03604 seconds / 36.04 milliseconds.
Page File Size: 27363 bytes.