SAN School: Lesson 6

"SANs for disaster recovery"

Join Christopher Poelker, co-author, Storage Area Networks for Dummies for a webcast on how you can use your SAN for disaster recovery purposes. This webcast explores the most important things you need to consider when backing up and recovering data using a SAN.

More about "Lesson 6: SANs for disaster recovery"
One of the main selling points for implementing a Storage area network (SAN) are all of the disaster recovery features one provides. In this lesson, Christopher Poelker delineates considerations for building a basic disaster recovery plan. This lesson answers the questions: How much data do I need to copy? What can I afford to lose? How do latency and bandwidth play into faster backups and restores? Some other topics covered...recovery time vs. recovery point objectives...choosing a remote site and its components and creating the final plan, according to budget.

What you'll walk away with:
** In-depth knowledge of how to create an effective SAN DR plan
** Synchronous and Asynchronous data replication
** The importance of bandwidth, distance, and latency
** Designing a DR architecture
** The ability to ask Chris your specific SAN questions
 

Also, follow along with class with this

    Requires Free Membership to View

    Login

worksheet.

Take the first SAN School quiz.

***TEST YOUR KNOWLEDGE OF PART 2 -- TAKE OUR QUIZ***
Once you've viewed lessons 5-7, test your skills by taking the SAN School Quiz

About Christopher Poelker:

Christopher Poelker is a storage architect at Hitachi Data Systems. Prior to Hitachi, Chris was a lead storage architect/senior systems architect for Compaq Computer, Inc., in New York. While at Compaq, Chris built the sales/service engagement model for Compaq StorageWorks, and trained most of the company's VAR's, Channel's and Compaq ES/PS contacts on StorageWorks. Chris' certifications include: MCSE, MCT (Microsoft Trainer), MASE (Compaq Master ASE Storage Architect), and A+ certified (PC Technician).

Back to the SAN School table of contents.


This was first published in May 2005

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.
    Back to top