Answer

How image-level backup differs from traditional backup

What is an image-level backup and how is it different from traditional backup?

    Requires Free Membership to View

Image-level backup is a snapshot. There are three different kinds of snapshots: Copy-on-write (COW), Redirect-on-write (ROW), and clones. COW and ROW really are taking only a copy of the pointers of what the data looked like at that point in time. There is no real copy of the data although COW will create one over time as changes to that original data occur. Clones are complete copies of the data.

Traditional backup refers to creating a full copy of data. Today, backup software typically backs up all of the files on a server including the hidden files one time, then backs up any changes since the previous backup.

The differences between the two technologies show up in restores. A snapshot has to be mounted to recover any of the data. For single file recoveries, which are more than 90% of the restores per Symantec's recent research, traditional backup (also known as file-level backup), is a better data protection solution because only that single file needs to be restored.

For system-level restores, image backups or snapshots are much faster and easier to restore. It's not an either or and they are not mutually exclusive. Many backup software products provide both image and file backup as well as file and image restores.

This was first published in December 2013

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: