backup usually involves the ability to share a SAN connected tape library between all the nodes connected in the SAN. The backup server simply coordinates access to the tape resources. Each server in the SAN actually runs a copy of the backup engine and moves its own data to tape. This is sometimes called the "SSO" or shared storage option from some backup vendors. The
server becomes the traffic cop for the SAN connected tape resources and allows each server in the
to back up its own data. This removes the need to "PULL" data over the
via backup agents to a backup server connected tape resource.
is accomplished by the backup server having the ability to connect to storage on behalf of other hosts connected to the SAN and back up that host's storage on its behalf. This usually involves the use of
or image copies of the production LUNs in the SAN. The snapshot is used as the source media for backup so that the production application can continue during backup. The snapshot is given access through
security in the SAN for access by the backup server, and the backup server sends the data to tape. Another method is to use the SCSI extended copy command called E-Copy which allows even the backup server to get out of the backup path. E-copy allows data to move directly from disk to tape via a "data router" that provides the E-copy intelligence.
Dig Deeper on Tape backup and tape libraries
SAN expert Chris Poelker discusses how to change the size of a LUN in a Microsoft cluster server environment.
SAN expert Chris Poelker compares connecting a SAN with wavelength cabling and dark fiber and discusses the pros and cons of each.
Storage expert Chris Poelker outlines WWN basics in order to answer the question: "Why do HBAs in a SAN have same base?"
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.