Introduction
Laptop Battery 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.
Disaster recovery planning is not just available for the big boys. sized businesses (SMBs) in need quite affordably today.
Thinkpad 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.
"Computer industry analysts estimate that some 60 percent of all corporate data exists only on desktop and laptop computers, " said Walter Scott, CEO of Acronis. "Incorporating Acronis True Image with New Mexico Software backup server is the ideal solution to capture that corporate data and ensure that it is not lost. While traditional server backups are effective for protecting server data, every company should have a combination of server and workstation backup plans."
Microsoft
Exchange Disaster Recovery Planning
One way to significantly reduce TCO of your storage investment is to optimize your applications so that one action can accomplish multiple tasks. Such is the case with disaster recovery and data backup. A devised disaster recovery plan will not only secure your system, but also protect and back up your data. There are two popular backup disk imaging and based that take very different approaches to disaster recovery. We'll look at these options of mapping your disaster recovery plan later. For now, however, let' how a company implements its disaster recovery plan.
Laptop Computers 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.
A key component to Hudson Valley FCU's disaster recovery plan is disk imaging. Having a tape backup of a system is important for backing up individual files, but it is the disk image that keeps a record of the state of the whole system. We 3 regularly create backup images of each critical server using Acronis True Image Server. We can also schedule incremental backups on a daily basis, so maintaining a current image of each server is fast and easy to create.
Laptop Computer
General Considerations
"Recent events along the Gulf Coast and power outages in Los Angeles have brought to the fore the need for companies large and small to have disaster recovery strategies, " he continued. "As virtual servers are introduced into more networks, IT managers need a disaster recovery plan that addresses both physical and virtual systems."
Desktop Computer SANRAD replication solution allows for flexibility with Exchange Disaster Recovery design.
Notebooks The most influential factors affecting design consideration are:
Lenovo . Budget limitations
Hard Drive . Recovery Time Objective (RTO) requirements (the time until the data is back online)
Travelstar . Recovery Point Objective (RPO) requirements (the amount of data that can be lost)
Gateway . Network bandwidth between the local site and remote site
Laptop Parts . Replication method: Synchronous versus Asynchronous
Software . Replication frequency (only for Asynchronous replication)
Hard Drives . Initial volume synchronization
Electronics RTO (Recovery Time Objective)
Canon
. With high level RTO, duplicate hardware is required to allow quick recovery making
the solution more costly.
Desktop Pc RPO (Recovery Point Objective)
Desktop Computers
RPO requirements are best defined by the amount of data that the company is willing to
lose.
Think Pad . High level RPO requires more bandwidth for both Synchronous and Asynchronous
replication.
Repair . Low level RPO requires less frequent replication and increases the risk of losing
more data.
Data Recovery Network Bandwidth between the Local and Remote sites
Cisco
Bandwidth between the sites is generally the most crucial factor affecting the replication
component of a Disaster Recovery solution.
Keyboard . T1 (1.5Mb) links impose less frequent data replication and the use of asynchronous
replication methods.
Monitor . T3 (45Mb) links or a 1Gb links allow frequent replication and the flexibility to choose
between synchronous replication or asynchronous replication methods.
Desktop Replication method
Infosys
When considering which replication method to choose it is important to remember:
Refurbished Laptops . 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.
Wipro . 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.
Lap Top . For Asynchronous replication, you must decide the data replication frequency. There
are three factors that must be considered:
Refurbished 1. The size of the network bandwidth between the sites.
Memory 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.
Intel 3. The RPO requirements.
As400 Initial Volume Synchronization
Averatec
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:
Hardware . The size of the volumes needed to be synchronized.
Dual Xeon . The network bandwidth between the sites. For example, the bigger the volume size,
the longer it will take to synchronize over a T1 link.
Storage Online synchronization starts immediately when replication is started and uses the
same network link that will be used during the replication.
Seagate 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.
Computer Sales
Exchange Considerations
Any
Exchange Disaster Recovery planning should (at the very least) consider the following
requirements:
Computer Hardware . 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.
Printers . 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.
Technology . 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).
Mainframe . The most up to date replicated copy of the Windows backup set (which includes
system state) to expedite Exchange Server recovery.
Samsung
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)".
Computer Repair 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.
For further reading click here
