Commentary

George Crump
 

Replications On A Theme - Host-Based Replication

Disaster recovery is certainly more than getting the data out of your data center and having it land in a remote facility, but that isn't a bad pace to start. Problem is, there are now 800 different ways to replicate data.

Disaster recovery is certainly more than getting the data out of your data center and having it land in a remote facility, but that isn't a bad pace to start. Problem is, there are now 800 different ways to replicate data.I typically break these down into three areas; host-based replication, appliance-based replication, and storage controller-based replication. I'll dive into all of these over the next few blogs, but suffice to say, you have options.

First up is host-based replication. I'm not sure whom to give credit to for this space, but the guys that come to mind most often lately are DoubleTake Software and SteelEye Technology. Host-based replication installs an agent on each server that you want to protect, all managed by a central console.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Sometimes I think that host-based replication has been forgotten in the rush to networked storage, but it continues to be very viable in certain situations. For example, in smaller accounts that simply don't yet need a SAN but have mission-critical information, these are very cost-effective solutions to getting that done.

Second, staying with the small-business theme, if the business is also using server virtualization, then these solutions also give you some capabilities as it relates to virtual server migration. Virtual machine migration normally requires shared storage. This is the ability to move a virtual machine from one physical host to another physical host. With some of the host-based replication solutions, you can pull this off without networked storage -- just replicate from one internal hard disk to another.

A viable solution is to have a two-server environment with two internal drives each. Each primary drive could replicate to the secondary drive in real time. This covers you from a basic drive loss situation and sets the stage for virtual migration. When the need arises to move a virtual machine, you could stop the replication and move your virtual machines over to the alternate server. The reasoning behind this could be a simple need to load balance or to perform maintenance on the first server.

A final situation applies to even large environments. Large environments have two situations that make using host-based replication a nice complement to storage-based replication. First, most larger data centers don't have only one SAN. Replicating from brand A to brand B isn't always supported with SAN Storage, but it is almost always supported with host-based replication.

Finally, all your data may not be on the SAN yet, if ever. There may be several important servers that for one reason or another never land on the SAN. Yet you want something more than a backup of these systems and host-based replication could be ideal.

Next, appliance-based replication.

Track us on Twitter: http://twitter.com/storageswiss.

Subscribe to our RSS feed.

George Crump is founder of Storage Switzerland, an analyst firm focused on the virtualization and storage marketplaces. It provides strategic consulting and analysis to storage users, suppliers, and integrators. An industry veteran of more than 25 years, Crump has held engineering and sales positions at various IT industry manufacturers and integrators. Prior to Storage Switzerland, he was CTO at one of the nation's largest integrators.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links