Q
Problem solve Get help with specific problems with your technologies, process and projects.

# Configuring your first SAN: Usable versus raw storage

For a company with 12 servers (no failover server), I want to create a mirror/snapshot of the system drive (OS...

+ database + application server settings). The reason is that after a server and an OS go down, reinstallation of an OS +application server + database server takes twice as long (four hours) as restoring database from database backup files (two hours). Will a SAN help in this case? We have 14 internal disks (73 GB, 10K rpm) per server for a total of 164 disks. Is \$150K a reasonable target for moving all the disks into a SAN with tape library support? We currently have seven DAS tape drives -- one tape drive per two servers -- for a total of five TB data full backup in the weekend and 0.3 TB incremental every weeknight.

A 5 TB SAN solution using modular storage should not cost an arm and a leg. Make sure the vendor you choose gives you 5 TB of usable storage, and not raw storage. The number of drives you'll need for usable storage will depend on how you configure your RAID sets in the storage array. (RAID-1 or 1+0 will cost the most, since you need twice as many physical disks). You say you have 12 servers, each with 14 x 73 GB 10K rpm disks. If you buy a modular SAN array, you can configure your RAID to be RAID-5 13+1, which should net you a bit over 900 GB per server using 73 GB disks, or around 1.8 TB if you use 146 GB disks. This gives you a total of either: 73 GB drives: (13 x 73= 949) x 12 servers = 11.388TB usable storage; 146 GB drives: (13 x 146 = 1898) x 12 servers = 22.776TB usable storage. Take a close look at those numbers. Since you're backing up only 5 TB for full backup, that means you're underutilizing your current storage investment by about 60%.

``` (73 x 14 = 1022) x 12 servers = 12.264TB RAW 12264 - 5120 = 7144
```

This shows me you're wasting over 7 TB worth of storage since you cannot share it between servers. This is why a SAN makes so much sense for many companies. You'ill also need at least two more disks per server in your SAN to act as your mirrored boot disk. This means 24 more drives. Create 12 RAID-1 mirror sets in the array and dedicate one for each server. Do not share these disks with other servers, or install any other applications on them. Use LUN security in the array to make sure the server's host bus adapters (HBAs) have a dedicated mirror set as its boot LUN. Use LUN number 0 (zero) for each boot LUN, if your array supports it. You should use at least two HBAs per server but three would be better. I would dedicate one HBA per server as the backup path through the SAN fabric, which is either zoned out to a Fibre Channel-based tape library connected to the fabric, or to a third SAN switch dedicated for backup. You'll need at least two 16-port switches for the fabrics with each switch as its own fabric, and each server connected to each switch. It should end up looking something like this, which is from my book that shows you how to hook up server-free backup.

If you do use a third HBA in each server for backup, then you'd use another SAN switch and the dedicated backup HBAs and the tape library would connect to that switch. You'll need "path management" software on your servers so your data path can failover in case of the HBA, switch or storage controller fails. If this is a Unix solution, then something like Veritas DMP or Solaris MPXIO can be used. If it's Windows, you can use the MPIO driver, or you can buy software from your storage vendor that supports their array (Hitachi HDLM, EMC Powerpath, HP Securepath, etc.)

This was last published in June 2004

## Content

Find more PRO+ content and other member only offers, here.

#### Have a question for an expert?

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

#### Start the conversation

Send me notifications when other members comment.

## SearchDisasterRecovery

• ### Don't let your BC/DR plan get lost in the shuffle

How can you maintain consistency in your BC/DR strategy in a world of constantly evolving technology? If it's a reactive part of ...

• ### Zerto Virtual Replication reduces marketing firm's RPO

Maritz needed a short RPO and flexible cloud provider options for its recovery process. Zerto replication protects applications ...

• ### Nakivo Backup & Replication software gets automated

Nakivo updates its software for quick and automated recovery. While the vendor has a focus on virtual data protection, it has ...

## SearchDataBackup

• ### Modern data backup technologies afford merging opportunities

Through technologies such as copy data management, vendors are merging primary and secondary storage. There's more convergence ...

• ### Criteria for vetting appliance-based data backup systems

Knowing the right questions to ask when vetting data backup appliance vendors can help ensure you select the product that will ...

• ### Spanning Backup for Salesforce enhances metadata restore

Spanning Backup makes it easier for Salesforce administrators who deal with metadata. Direct restore improves self-service of ...

## SearchConvergedInfrastructure

• ### Ten hyper-converged infrastructure architecture buying mistakes

Buying hyper-converged infrastructure systems can be less stressful if you learn about and avoid these 10 common mistakes that ...