|
Scenario I
To either expand or move away from the traditional tape backup environment which is traditionally complex, costly, and slow to restore. This environment would be a good candidate for a consolidated backup solution. Such an implementation would incorporate the usage of a storage sub-system (traditionally known as D2D or Disk-to-Disk).
Another implementation would be to replace a main tape backup system with a disk storage subsystem as a VTL (Virtual Tape Library). A VTL is a functionality provided by the backup software in that it virtualizes the block level storage into virtual tapes (just like the original tapes of the tape backup system). This achieves a very high performance environment in which daily and weekly backups are done and at the end of the week, or month, are then archived to tape for external storage. Such an implementation significantly cuts backup and restore time while maintaining a solid backup strategy.
Scenario II
Another traditional requirement for archiving is to offload older data from an online storage system to a near-line storage system.
This protects the online-storage system and doesn’t require the added expenditure of adding more disks of the same class. Instead, one moves older data onto another storage system which can be near-line (meaning using Serial-AtA drives a.k.a. SATA).
Such an implementation is usually known as ILM or Information Lifecycle Management.
Requirements
Since performance is usually not the driving force behind archiving (or backup solutions) using a very solid and reliable disk technology, such as Serial-ATA (SATA), would be more than sufficient.
SATA storage is also known as near-line storage. Additionally, high availability is also not required on the majority of the implementations so getting a dual raid controller storage sub-system would generally be over-kill. To have redundant components such as redundant power supplies and fans would be adequate but the RAID controller can be single.
Here you would not require high performance disks so SATA backplane solutions would be sufficient.
DAS or NAS
Well, Direct Attached Storage or Network Attached Storage, would both do the trick. The main difference is which implementation exists in the environment.
Case 1
If your environment has an existing tape backup solution then the most likely scenario is to consider a DAS solution. In this scenario one would incorporate a storage solution directly connected to the backup server (where the backup application resides) and this can be any technology such as SCSI, FC, or even iSCSI.
Since there is only going to be one connection to the backup server the most likely (and cost effective) choice is SCSI. This will provide a fast, reliable, and cost effective pipe. The next function will be from the backup software and it will involve creating a VTL (Virtual Tape Library). For specifics on how to achieve this please consult your backup software vendor.
Case 2
If your environment does not have a current backup solution in place then the most likely scenario is to consider a NAS (Network Attached Storage).
This is the best solution as it allows many connections to the storage without needing a CAL (Client Access License). Every host which needs to be backed up (whether it’s an application server or a client machine) would simply connect with the company network (i.e. Ethernet). The speed achieved would be more than satisfactory (especially when compared to traditional tape backup!). The storage can easily be configured, managed, and scaled to match the backup needs.
Potential Solutions
NetStor WSS NAS
SecurStor Astra SA DAS
|
