A backup must be made by copying the source data image when it is in a consistent state
The word "backup" gets thrown around so much that folks tuned in to the world of enterprise storage can start getting surly. One of the best ways to annoy a backup administrator is to start talking about how well the backup will facilitate disaster recovery, e-discovery, and compliance! So what is a backup anyway? Is it different from an archive?
SNIA defines a backup as follows:
"A collection of data stored on (usually removable) non-volatile storage media for purposes of recovery in case the original copy of data is lost or becomes inaccessible; also called a backup copy.To be useful for recovery, a backup must be made by copying the source data image when it is in a consistent state."
This description does not strike me as all that useful, so I put this simple question to a number of folks on Twitter and through direct discussion.
I contacted W. Curtis Preston, "Mr. Backup", for his opinion. He pointed out that just about any copy of data can be used as a backup, but not all are equally effective. A simple file copy routine might suffice, but managing this might prove troublesome. Preston also warned about relying on backups for more than simple restore: "using a backup as an archive, for example, doesn't make it an archive!"
To Continue Reading: Click Here---------------------------------------------------
Source: dotnet.sys-con.com
By Stephen Foskett
0 comments:
Post a Comment