Member You
#1 in Business Subscribe Email Print

You are here: Home > Computers and Technology > Computers and Technology > SANRAD Application Note: Exchange Disaster Recovery with SANRAD V-Switch Planning Guide

Tags

  • different
  • their
  • domain
  • exchange volumes
  • links allow
  • synchronizationsanrad replication

  • Links

  • Moroccan Rugs - Unique Ways to Enliven Your Home Decor
  • Prepaid Master Card
  • Network Marketing Business - What's Your Color?
  • Member You - SANRAD Application Note: Exchange Disaster Recovery with SANRAD V-Switch Planning Guide

    Microsoft Word 2003 – Create a Colorful Venn Diagram Easily
    I love Venn Diagrams because nothing comes to close to expressing the logical relationships between different sets of elements that well.With Microsoft Word 2003 you can create fantastic looking and colorful Venn Diagrams on the fly, with as many elements and colors as you need.It helps to launch your DRAW toolbar first before you do anything else.Then follow these steps:1) Click the 3-balls icon (the tooltip text should read “Insert Diagram or Organization Chart”) to display the Diagram Gallery dialog box.2) Click and select the Venn Diagram icon on the lower-center to insert a default Venn diagram and also to display the Diagram mini tool-bar.3) To add a new set of elements (represented by each CIRCLE in the diagram), click the Insert Shape button on the mini tool-bar.4) To move the circl
    b) since both acknowledgements are local (from the primary volume and the journal volume) and thus the replication is fast by default.
    • For Asynchronous replication, you must decide the data replication frequency. There are three factors that must be considered:
    1. The size of the network bandwidth between the sites.
    2. The amount of data changes that need to replicate each time. For example, large amounts of data changes take longer to replicate using T1 links.
    3. The RPO requirements.


    Initial Volume Synchronization

    SANRAD replication solution can be used to protect existing production Exchange data. SANRAD Disaster Recovery solution supports both online and offline synchronization. When using SANRAD replication with existing Exchange data, an Initial synchronization of the Exchange volumes on th

    Discover How To Blog Your Way To Free Traffic
    Blogging for your Internet business is a great way to boost the visibility of your products and services. Here are a few ways to boost your internet advertising with the help of a blogger.com:1. Share your thoughts and ideas about your product or service. Make your customers aware of new developments you make to your website. You can also share websites that pertain to your industry.2. Your blog content can be easily stored through archiving3. It is easy to share your opinions, advice or reviews on specific services or products.4. You can include links that will support back links and improve your ranking on search engines. This could be better executed through putting well-written articles in your website. Affiliate links can also be included in your blog to earn more extra income.5. Collect response
    Introduction

    Designing a disaster recovery system requires planning and consideration of the available options that will best fit your company’s needs, SLA and budget. This guide will help you design an Exchange Disaster Recovery plan in conjunction with SANRAD Replication. The guide assumes that you have basic knowledge of SANRAD V-Switch and Exchange Administration.

    Note: It is recommended to read Microsoft’s Exchange Server 2003 Disaster Recovery Planning Guide available from http://www.microsoft.com/downloads/details.aspx?FamilyId=784BBE A2-28DD-409A-8368-F9914E993B28&displaylang=en.

    Exchange Disaster Recovery Planning

    This section discusses both general and Exchange specific considerations that need to be addressed when designing a disaster recovery solution combining SANRAD replication and Microsoft Exchange Server.

    General Considerations

    SANRAD replication solution allows for flexibility with Exchange Disaster Recovery design.
    The most influential factors affecting design consideration are:
    • Budget limitations
    • Recovery Time Objective (RTO) requirements (the time until the data is back online)
    • Recovery Point Objective (RPO) requirements (the amount of data that can be lost)
    • Network bandwidth between the local site and remote site
    • Replication method: Synchronous versus Asynchronous
    • Replication frequency (only for Asynchronous replication)
    • Initial volume synchronization


    RTO (Recovery Time Objective)

    • With high level RTO, duplicate hardware is required to allow quick recovery making the solution more costly.


    RPO (Recovery Point Objective)

    RPO requirements are best defined by the amount of data that the company is willing to lose.
    • High level RPO requires more bandwidth for both Synchronous and Asynchronous replication.
    • Low level RPO requires less frequent replication and increases the risk of losing more data.

    Network Bandwidth between the Local and Remote sites

    Bandwidth between the sites is generally the most crucial factor affecting the replication component of a Disaster Recovery solution.
    • T1 (1.5Mb) links impose less frequent data replication and the use of asynchronous replication methods.
    • T3 (45Mb) links or a 1Gb links allow frequent replication and the flexibility to choose between synchronous replication or asynchronous replication methods.

    Replication method

    When considering which replication method to choose it is important to remember:
    • In Synchronous Replication the I/O commands are written to the local disk and to the remote volume at the same time. Every IO command requires an acknowledgment from both the local and remote sites before the next command. Consequently, synchronous replication is best deployed with a high bandwidth connection in order to allow the remote acknowledgment to arrive back to the local site as fast as possible and the replication can run faster.
    • In Asynchronous Replication the I/O commands are written to the local volume and local journal volume which in turn is replicated periodically to the remote volume as periodically defined by the user. Consequently asynchronous replication can work well with lower bandwidth (minimum recommended for Exchange replication is 1.5 Mb) since both acknowledgements are local (from the primary volume and the journal volume) and thus the replication is fast by default.
    • For Asynchronous replication, you must decide the data replication frequency. There are three factors that must be considered:
    1. The size of the network bandwidth between the sites.
    2. The amount of data changes that need to replicate each time. For example, large amounts of data changes take longer to replicate using T1 links.
    3. The RPO requirements.


    Initial Volume Synchronization

    SANRAD replication solution can be used to protect existing production Exchange data. SANRAD Disaster Recovery solution supports both online and offline synchronization. When using SANRAD replication with existing Exchange data, an Initial synchronization of the Exchange volumes on the

    List Building: Creating A Flood Of Affluent People Ready To Buy Your Products
    No matter what kind of website you have or business you want to run, you need to always capture the names and email addresses of the people visiting your sites. If you don't do this, you're leaving money on the table. Let me explain why.An interesting trend is developing in the business sector that makes it more important than ever to capture information from your web visitors. According to the Washington Post, business people are more influenced by the web than by any other type of advertising medium.What this means to you is that there is a captive affluent audience of "credit card in hand buyers" waiting to hear from you and to purchase your products. Sixty per cent of the decision makers remarked in a poll that the Internet was the best way for advertisers to reach them.These buyers are not only affluent and decis
    nge Server.

    General Considerations

    SANRAD replication solution allows for flexibility with Exchange Disaster Recovery design.
    The most influential factors affecting design consideration are:
    • Budget limitations
    • Recovery Time Objective (RTO) requirements (the time until the data is back online)
    • Recovery Point Objective (RPO) requirements (the amount of data that can be lost)
    • Network bandwidth between the local site and remote site
    • Replication method: Synchronous versus Asynchronous
    • Replication frequency (only for Asynchronous replication)
    • Initial volume synchronization


    RTO (Recovery Time Objective)

    • With high level RTO, duplicate hardware is required to allow quick recovery making the solution more costly.


    RPO (Recovery Point Objective)

    RPO requirements are best defined by the amount of data that the company is willing to lose.
    • High level RPO requires more bandwidth for both Synchronous and Asynchronous replication.
    • Low level RPO requires less frequent replication and increases the risk of losing more data.

    Network Bandwidth between the Local and Remote sites

    Bandwidth between the sites is generally the most crucial factor affecting the replication component of a Disaster Recovery solution.
    • T1 (1.5Mb) links impose less frequent data replication and the use of asynchronous replication methods.
    • T3 (45Mb) links or a 1Gb links allow frequent replication and the flexibility to choose between synchronous replication or asynchronous replication methods.

    Replication method

    When considering which replication method to choose it is important to remember:
    • In Synchronous Replication the I/O commands are written to the local disk and to the remote volume at the same time. Every IO command requires an acknowledgment from both the local and remote sites before the next command. Consequently, synchronous replication is best deployed with a high bandwidth connection in order to allow the remote acknowledgment to arrive back to the local site as fast as possible and the replication can run faster.
    • In Asynchronous Replication the I/O commands are written to the local volume and local journal volume which in turn is replicated periodically to the remote volume as periodically defined by the user. Consequently asynchronous replication can work well with lower bandwidth (minimum recommended for Exchange replication is 1.5 Mb) since both acknowledgements are local (from the primary volume and the journal volume) and thus the replication is fast by default.
    • For Asynchronous replication, you must decide the data replication frequency. There are three factors that must be considered:
    1. The size of the network bandwidth between the sites.
    2. The amount of data changes that need to replicate each time. For example, large amounts of data changes take longer to replicate using T1 links.
    3. The RPO requirements.


    Initial Volume Synchronization

    SANRAD replication solution can be used to protect existing production Exchange data. SANRAD Disaster Recovery solution supports both online and offline synchronization. When using SANRAD replication with existing Exchange data, an Initial synchronization of the Exchange volumes on th

    Five Creative Ways To Find Creative Work Today
    Working for yourself as a writer, designer, or other creative professional is extremely satisfying. It's also lucrative, if you can face the reality that you're responsible for how much work you do. Your aim as a freelancer is to be happy, constantly employed, but not overwhelmed, so that you're making more money than you would be making if you were working for someone else.You can avoid under-employment as a freelance creative professional if you compartmentalize the creation of products, and the selling of your services. These two activities demand different mindsets. Schedule both activities, and do them at different times of the day or week.Set aside a couple of hours each day, or each week if you're moonlighting in your own business, to promote yourself and your services so you can build up work-orders. Over time, you'l

    RPO requirements are best defined by the amount of data that the company is willing to lose.
    • High level RPO requires more bandwidth for both Synchronous and Asynchronous replication.
    • Low level RPO requires less frequent replication and increases the risk of losing more data.

    Network Bandwidth between the Local and Remote sites

    Bandwidth between the sites is generally the most crucial factor affecting the replication component of a Disaster Recovery solution.
    • T1 (1.5Mb) links impose less frequent data replication and the use of asynchronous replication methods.
    • T3 (45Mb) links or a 1Gb links allow frequent replication and the flexibility to choose between synchronous replication or asynchronous replication methods.

    Replication method

    When considering which replication method to choose it is important to remember:
    • In Synchronous Replication the I/O commands are written to the local disk and to the remote volume at the same time. Every IO command requires an acknowledgment from both the local and remote sites before the next command. Consequently, synchronous replication is best deployed with a high bandwidth connection in order to allow the remote acknowledgment to arrive back to the local site as fast as possible and the replication can run faster.
    • In Asynchronous Replication the I/O commands are written to the local volume and local journal volume which in turn is replicated periodically to the remote volume as periodically defined by the user. Consequently asynchronous replication can work well with lower bandwidth (minimum recommended for Exchange replication is 1.5 Mb) since both acknowledgements are local (from the primary volume and the journal volume) and thus the replication is fast by default.
    • For Asynchronous replication, you must decide the data replication frequency. There are three factors that must be considered:
    1. The size of the network bandwidth between the sites.
    2. The amount of data changes that need to replicate each time. For example, large amounts of data changes take longer to replicate using T1 links.
    3. The RPO requirements.


    Initial Volume Synchronization

    SANRAD replication solution can be used to protect existing production Exchange data. SANRAD Disaster Recovery solution supports both online and offline synchronization. When using SANRAD replication with existing Exchange data, an Initial synchronization of the Exchange volumes on th

    Accident Lawyers – Help For You
    It makes no difference how alert you try to be, you are assured that an accident can happen when you least expect it to. You can be driving along carefully and be smashed from behind. The car comes from out of the blue and side swipes your car. You could be walking across the street and a car hits you. It may be any number of reasons they did not stop. None of them matter now that you are injured.If you are one of the less fortunate ones to have this occur or know someone who has, it is best for all to find a lawyer that has a good reputation for helping those in accident cases. You might try searching the internet. Many lawyers, especially accident specialists, are providing information about their services. You may find some lawyers with toll free numbers and email for easy contact. Websites have forms allowing you to give them a
    replication method to choose it is important to remember:
    • In Synchronous Replication the I/O commands are written to the local disk and to the remote volume at the same time. Every IO command requires an acknowledgment from both the local and remote sites before the next command. Consequently, synchronous replication is best deployed with a high bandwidth connection in order to allow the remote acknowledgment to arrive back to the local site as fast as possible and the replication can run faster.
    • In Asynchronous Replication the I/O commands are written to the local volume and local journal volume which in turn is replicated periodically to the remote volume as periodically defined by the user. Consequently asynchronous replication can work well with lower bandwidth (minimum recommended for Exchange replication is 1.5 Mb) since both acknowledgements are local (from the primary volume and the journal volume) and thus the replication is fast by default.
    • For Asynchronous replication, you must decide the data replication frequency. There are three factors that must be considered:
    1. The size of the network bandwidth between the sites.
    2. The amount of data changes that need to replicate each time. For example, large amounts of data changes take longer to replicate using T1 links.
    3. The RPO requirements.


    Initial Volume Synchronization

    SANRAD replication solution can be used to protect existing production Exchange data. SANRAD Disaster Recovery solution supports both online and offline synchronization. When using SANRAD replication with existing Exchange data, an Initial synchronization of the Exchange volumes on th

    Options for Lawsuit Settlement Winners Receiving Periodic Payments
    On January 22,2002, President George W. Bush signed into law a bill that protects individuals who must sell their structured settlement payments to meet unplanned financial needs. H.R.2884Victims of Terrorism Tax Relief Act of 2001 (Signed by the President January 22,2002)) Under a structured settlement, a lawsuit plaintiff will not receive compensation in one lump sum but will receives a periodic stream of
    b) since both acknowledgements are local (from the primary volume and the journal volume) and thus the replication is fast by default.
    • For Asynchronous replication, you must decide the data replication frequency. There are three factors that must be considered:
    1. The size of the network bandwidth between the sites.
    2. The amount of data changes that need to replicate each time. For example, large amounts of data changes take longer to replicate using T1 links.
    3. The RPO requirements.


    Initial Volume Synchronization

    SANRAD replication solution can be used to protect existing production Exchange data. SANRAD Disaster Recovery solution supports both online and offline synchronization. When using SANRAD replication with existing Exchange data, an Initial synchronization of the Exchange volumes on the local site to the remote site must be performed. The initial volume sync method depends on:
    • The size of the volumes needed to be synchronized.
    • The network bandwidth between the sites. For example, the bigger the volume size, the longer it will take to synchronize over a T1 link.
    Online synchronization starts immediately when replication is started and uses the same network link that will be used during the replication.
    Offline synchronization is a manual process where SANRAD replication prepares the volumes on the primary site and the user must copy the data to the remote site. It is the user’s responsibility to make sure the volumes on the remote site are synchronized.

    Exchange Considerations

    Any Exchange Disaster Recovery planning should (at the very least) consider the following requirements:
    • Quick access to the most recent copy of the Exchange database and the transaction logs. In a disaster situation SANRAD replication provides fast access to the replicated data on the remote site.
    • The Exchange database and its related transaction logs must be replicated together to the remote site. SANRAD replication uses consistency groups to ensure simultaneous replication of all volumes assigned to a consistency group.
    • Exchange is integrated into Active Directory. An Active Directory domain controller (running Global Catalog) which is part of the same Active Directory domain that exists in the primary site, must exist in the remote site as well (or at least the capability to rebuild one and reconnect it to the existing Active Directory Domain).
    • The most up to date replicated copy of the Windows backup set (which includes system state) to expedite Exchange Server recovery.

    Note: for detailed information about Exchange 2003 disaster recovery considerations please read Microsoft’s article, “Exchange Server 2003 Disaster Recovery Planning Guide (http://go.microsoft.com/fwlink/?LinkId=21277)”.

    This guide deals with designing a disaster recovery system while planning and considering the available options. It further discusses about suggested Disaster Recovery Designs, fully Mirrored Remote Site, partially Mirrored Remote Site, small Remote Site, combining SANRAD Disaster Recovery Designs with Exchange Disaster, restore Models, restore Exchange with a Standby Server and restore by Rebuilding Exchange Server.

    HTTP = HTML link (for blogs, profiles,phorums):
    <a href="http://www.memberyou.net/article/169048/memberyou-SANRAD-Application-Note-Exchange-Disaster-Recovery-with-SANRAD-VSwitch-Planning-Guide.html">SANRAD Application Note: Exchange Disaster Recovery with SANRAD V-Switch Planning Guide</a>

    BB link (for phorums):
    [url=http://www.memberyou.net/article/169048/memberyou-SANRAD-Application-Note-Exchange-Disaster-Recovery-with-SANRAD-VSwitch-Planning-Guide.html]SANRAD Application Note: Exchange Disaster Recovery with SANRAD V-Switch Planning Guide[/url]

    Related Articles:

    Proper Submission Of Rebates In 10 Steps

    Hurricanes and Wealth Building

    Refinancing Mortgage Loans

    Bookmark it: del.icio.us digg.com reddit.com netvouz.com google.com yahoo.com technorati.com furl.net bloglines.com socialdust.com ma.gnolia.com newsvine.com slashdot.org simpy.com shadows.com blinklist.com