 




<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The musings of an IT Consultant &#187; Veeam Backup and Replication</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/it-consultant/tag/veeam-backup-and-replication/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/it-consultant</link>
	<description></description>
	<lastBuildDate>Wed, 01 May 2013 01:19:15 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>VM redundancy in a SMB environment</title>
		<link>http://itknowledgeexchange.techtarget.com/it-consultant/vm-redundancy-in-a-smb-environment/</link>
		<comments>http://itknowledgeexchange.techtarget.com/it-consultant/vm-redundancy-in-a-smb-environment/#comments</comments>
		<pubDate>Sun, 28 Feb 2010 20:18:36 +0000</pubDate>
		<dc:creator>Raj Perumal</dc:creator>
				<category><![CDATA[DL380]]></category>
		<category><![CDATA[HP]]></category>
		<category><![CDATA[iSCSI]]></category>
		<category><![CDATA[ML350]]></category>
		<category><![CDATA[QNAP]]></category>
		<category><![CDATA[SMB]]></category>
		<category><![CDATA[Veeam Backup and Replication]]></category>
		<category><![CDATA[virtual SMB solution]]></category>
		<category><![CDATA[VMWare]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/it-consultant/vm-redundancy-in-a-smb-environment/</guid>
		<description><![CDATA[Hi folks, so you&#8217;ve decided to pull the trigger on virtualization in your SMB business and want go virtual. Now what do you do about backups? Well you know I&#8217;ve mentioned Veeam before and SANs, but exactly how can you implement this in your environment in a cost effective manner? Well, there are a few [...]]]></description>
				<content:encoded><![CDATA[<p>Hi folks, so you&#8217;ve decided to pull the trigger on virtualization in your SMB business and want go virtual. Now what do you do about backups? Well you know I&#8217;ve mentioned Veeam before and SANs, but exactly how can you implement this in your environment in a cost effective manner?</p>
<p>Well, there are a few pieces to the puzzle you&#8217;ll need, but here is a nice little solution you can put together for not a lot of money. For the purposes of my example I&#8217;ll use HP servers, but you can fill in the blanks with your own vendor of choice. Everything mentioned here is on the VMware HCL(hardware compatibility list).</p>
<p>First of all, here are the ingredients you&#8217;ll need:</p>
<ul>
<li><a href="http://www.vmware.com/products/vsphere/small-business/buy.html">vSphere 4 Essentials</a></li>
<li><a href="http://www.veeam.com/vmware-esx-backup.html">Veeam Backup and Replication</a></li>
<li><a href="http://www.qnap.com/pro_detail_feature.asp?p_id=144">QNAP 459 Pro network attached storage device with some fast 1 TB hard drives</a></li>
<li>Two <a href="http://h10010.www1.hp.com/wwpc/us/en/sm/WF25a/15351-15351-241434-241646-241477-3884315.html#model-diff">HP ML350 tower servers</a> or two <a href="http://h10010.www1.hp.com/wwpc/us/en/sm/WF25a/15351-15351-3328412-241644-241475-3884082.html#model-diff">DL380 rack mount servers</a> with maxed out local SAS storage, redundant fans and power supplies, and upgraded battery backed cache with advanced iLO for remote management.</li>
<li><a href="http://www.procurve.com/products/switches/HP_ProCurve_1810G_Switch_Series/overview.htm#J9450A">HP 1810 series 24 port gigabit switch</a></li>
</ul>
<p>So what I would do is setup the two servers of your choice with VMware installed on them, and use the tons of local storage as the storage place for your virtual machines. For the purposes of this example we&#8217;ll call the first server &#8220;server1&#8243; and the second server &#8220;server2&#8243;.</p>
<p>Then create a vCenter server that is virtualized. This server can also act as your management box. Install Veeam Backup and Replication on this management server. Configure the QNAP device on your network using iSCSI and mount it so the management VM can mount the storage as a drive letter.</p>
<p>Setup Veeam to run backup jobs to the QNAP device and then setup Veeam to run replication jobs from server1 to server2 and vice versa.</p>
<p>Voila! You end up with external backups to the QNAP device, and you end up with virtual machine replicas of each virtual machine on the opposite vSphere server. If you need offsite backup, you can add some usb drives and connect them to your QNAP device to offload the backups to them to take them off site or you can buy another QNAP device for remote replication.</p>
<p>All in all a quick and dirty SMB solution that actually works!</p>
<p>-RP</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/it-consultant/vm-redundancy-in-a-smb-environment/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
