17.03.2015 Views

Storage Area Networks For Dummies®

Storage Area Networks For Dummies®

Storage Area Networks For Dummies®

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

296<br />

Part IV: SAN Management and Troubleshooting<br />

Managing database storage<br />

Another example — much more complicated but still completely<br />

autonomous — proves that people are completely useless after a SAN is<br />

put in operation. (HAL, did you say that, or did I?)<br />

Suppose that your database (XYZ) is getting larger and larger, and it begins<br />

to run out of space one night. At the 99 percent capacity level, automation<br />

can step in, allocate more disk space to your database server, and then tell<br />

the database software to expand to the new storage area. This function keeps<br />

your database administrators (DBAs) from getting paged at 3 a.m. and shows<br />

how flexible your new SAN environment really is. This example is a bit more<br />

involved than the backup example in the preceding section, requiring coordination<br />

with your DBAs to developing the scripts, but it can be done.<br />

Oh, by the way, the SAN framework also makes sure to send you an e-mail to<br />

tell you (when you get in at 10:30 the next morning) that the XYZ database<br />

grabbed a few more gigabytes of space last night . . . and you’re welcome.<br />

As you see, the possibilities can be relatively simple or get quite complicated,<br />

depending on what you need to anticipate and how you go about delivering<br />

the fix for the problem. Compare these two examples with what you’d have to<br />

do today without a SAN in place. Order a disk? Wait for your vendor to install<br />

it and configure it? With a SAN that’s automated, your problem is solved in<br />

about five minutes at 3 a.m. without waking anyone up.<br />

Providing a Service Level Agreement<br />

A Service Level Agreement (SLA) is a contract between your end users and<br />

you. It quantifies a level of performance, reliability, and support that you<br />

promise your users, in essence making them your customers.<br />

With an SLA, you define a set of parameters that you must meet to keep your<br />

customers from yelling at you. As long as the computing environment that<br />

you promised doesn’t go outside the bounds of the SLA that your customers<br />

agreed on, you won’t have to worry about getting a phone call that something<br />

is wrong.<br />

What happens if an SLA is breached? Usually, someone gets angry and starts<br />

calling people to find out what’s going on. Sometimes a monetary penalty is<br />

assessed. Usually, the customer doesn’t have to pay for service during the<br />

outage, just like when your cable television service goes out.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!