<?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>nScaled, Inc.</title>
	<atom:link href="http://nscaled.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://nscaled.com</link>
	<description>Recover Fast, Rest Easy</description>
	<lastBuildDate>Thu, 23 May 2013 19:45:18 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5</generator>
		<item>
		<title>For Law Firms: Online Backup and Disaster Recovery Made Simple</title>
		<link>http://nscaled.com/for-law-firms-online-backup-and-disaster-recovery-made-simple/</link>
		<comments>http://nscaled.com/for-law-firms-online-backup-and-disaster-recovery-made-simple/#comments</comments>
		<pubDate>Wed, 20 Mar 2013 18:27:23 +0000</pubDate>
		<dc:creator>Jay Kozie</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://nscaled.com/?p=3289</guid>
		<description><![CDATA[<p>Thanks to Hybrid Cloud Solutions Hurricanes in Vermont. Earthquakes in Washington, D.C. Tornados in Missouri. Natural disasters seem to be all over the news lately. Would your firm be able to recover in a reasonable amount of time and resume operations? Many risks exist &#8211; even for firms far away from earthquake fault lines, tornado alleys and hurricane zones. Consider the risk of water damage. Every law firm is at risk from broken pipes, too much rain or even a sink overflowing on the floor above you. There’s nothing to stop a flood. As some experts point out, “Water always wins.” Most law firms understand the importance of such a plan, but actually implementing one can be extremely challenging. Cost and logistics have been major barriers for many firms. Firms need to rent space at an off-site data center to secure data. They must purchase servers for the off-site location and pay someone to manage them. They need to develop procedures and policies to ensure that data is backed up regularly and securely transmitted to the DR site. In some cases, law firms with multiple offices use a secondary office as a makeshift DR data center. This can work, but satellite offices typically aren’t designed to serve as data centers and can’t handle the amount of data traffic that’s generated when you are replicating all your servers to that satellite office. When firms adopt either of these approaches, they are essentially rolling the dice that their internal DR solution will be ready and capable to support them in a disaster situation. The good news is you don’t need to spend a lot of money or roll the dice anymore. There are cost-effective and reliable online [...]</p><p>The post <a href="http://nscaled.com/for-law-firms-online-backup-and-disaster-recovery-made-simple/">For Law Firms: Online Backup and Disaster Recovery Made Simple</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></description>
				<content:encoded><![CDATA[<p><H3>Thanks to Hybrid Cloud Solutions</h3>
<p>Hurricanes in Vermont. Earthquakes in Washington, D.C. Tornados in Missouri. Natural disasters seem to be all over the news lately. Would your firm be able to recover in a reasonable amount of time and resume operations?</p>
<p>Many risks exist &#8211; even for firms far away from earthquake fault lines, tornado alleys and hurricane zones. Consider the risk of water damage. Every law firm is at risk from broken pipes, too much rain or even a sink overflowing on the floor above you. There’s nothing to stop a flood. As some experts point out, “Water always wins.”</p>
<p>Most law firms understand the importance of such a plan, but actually implementing one can be extremely challenging. Cost and logistics have been major barriers for many firms. Firms need to rent space at an off-site data center to secure data. They must purchase servers for the off-site location and pay someone to manage them. They need to develop procedures and policies to ensure that data is backed up regularly and securely transmitted to the DR site.</p>
<p>In some cases, law firms with multiple offices use a secondary office as a makeshift DR data center. This can work, but satellite offices typically aren’t designed to serve as data centers and can’t handle the amount of data traffic that’s generated when you are replicating all your servers to that satellite office.</p>
<p>When firms adopt either of these approaches, they are essentially rolling the dice that their internal DR solution will be ready and capable to support them in a disaster situation. The good news is you don’t need to spend a lot of money or roll the dice anymore. There are cost-effective and reliable online backup and DR solutions, thanks to new hybrid cloud approaches.</p>
<p>These solutions provide:</p>
<ul>
<li>Affordability</li>
<li>Remote data backup &#8211; without tapes</li>
<li>A local hardware appliance, which is essential for fast recovery of a folder or documents or a failed server</li>
<li>Secure, controlled data transfers to the cloud</li>
</ul>
<p>Every good plan should include both DR and online backup. This ensures your clients’ data is safe and your lawyers can continue to service your clients, no matter what happens.</p>
<p>While online backup and DR solutions have a lot in common, you should think about what your firm needs in each area.</p>
<p><strong>Disaster Recovery Considerations</strong></p>
<p>DR has always been a daunting task. The headaches and expense of internally built DR sites made that an unappealing option,. At the same time, many firms are leery of the security and accessibility of cloud solutions.</p>
<p>Hybrid solutions, such as <a href="http://nscaled.com/solutions/online-backup/">nScaled</a>, address many of these issues. As a cloud environment, all the purchase, installation and maintenance of DR hardware/software are offloaded. Ongoing, the cloud expands automatically as your firm grows.</p>
<p>These new hybrid cloud DR solutions have resulted in a dramatic cost decrease, to about one-third of a traditional data center-based DR solution. How? You avoid paying for disk storage that may remain empty for years. You also only pay for the DR servers (admittedly at a premium) when you need them in a DR incident. Meanwhile, your data stays safely tucked away in a secure cloud data center until needed.</p>
<p>This type of solution addresses more than major disasters. It can also be used as your backup solution, providing significant advantages over traditional backup tapes. If you need to recover files spanning multiple days or weeks, the data is all in one online location. Your IT team doesn’t need to dig through and restore multiple tapes.</p>
<p>A cloud solution can also back up once an hour throughout the day, rather than end of day like most tape systems do. Consider this familiar scenario — you begin a brief at 8:00 am and work on it all day. Near the end of the day, your file becomes corrupted. With this solution, you can retrieve the copy that was last backed up an hour ago. Better yet &#8211; it will only take about 15 minutes for your IT department to recover. Instead of losing an entire day’s work, you lose an hour.</p>
<p><strong>Online Backup Solutions</strong> </p>
<p>There are also cost effective cloud based online backup solutions such as Barracuda Networks. Like the DR options mentioned above, they provide both a remote backup as well as a local copy of data on an appliance in your office. With the local copy, you can quickly restore one document, one folder, or an entire server. This helps ensure you can be up and running within hours of a disaster, instead of days.</p>
<p>In the cloud, Barracuda and similar systems use de-duplication and compression to minimize the amount and cost of data stored in the cloud. That data is also encrypted for your protection.</p>
<p>Just like a hybrid cloud DR solution, you only pay for the data as you use it. You don’t need to purchase a large amount of storage space that you may or may not use sometime in the future.</p>
<p>No one is immune from disasters. Fortunately, we can help you recover fast if one strikes. If you are interested in finding out more about Disaster Recovery or Online Backup solutions, contact me at jkozie@kenokozie.com.</p>
<p>Jay Kozie is a Principal with <a href="http://www.kenokozie.com">Keno Kozie Associates</a>, an IT consulting firm and a member of <a href="http://www.lawfirmconsultantsnetwork.com">Law Firm Consultants Network of Chicago (LFCN)</a>. LCFN is a diverse group of senior-level professionals with expertise serving the legal community. The group’s sole focus is to be a resource to law firms and the professionals servicing law firms by providing the highest level of professional service and coordinating these services when it is of benefit to our clients. Contact Jay at jkozie@kenokozie.com</p>
<p>The post <a href="http://nscaled.com/for-law-firms-online-backup-and-disaster-recovery-made-simple/">For Law Firms: Online Backup and Disaster Recovery Made Simple</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://nscaled.com/for-law-firms-online-backup-and-disaster-recovery-made-simple/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Make the Most of Your IT Budget in Q4</title>
		<link>http://nscaled.com/make-the-most-of-your-it-budget-in-q4/</link>
		<comments>http://nscaled.com/make-the-most-of-your-it-budget-in-q4/#comments</comments>
		<pubDate>Thu, 11 Oct 2012 19:29:57 +0000</pubDate>
		<dc:creator>Sarah Grant</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[budget]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[disaster recovery]]></category>
		<category><![CDATA[downtime]]></category>
		<category><![CDATA[draas]]></category>
		<category><![CDATA[raas]]></category>
		<category><![CDATA[recovery]]></category>
		<category><![CDATA[regulation]]></category>
		<category><![CDATA[ROI]]></category>
		<category><![CDATA[technology]]></category>

		<guid isPermaLink="false">http://blog.nscaled.com/blog/?p=415</guid>
		<description><![CDATA[<p>Welcome to the fourth quarter, the time when most IT departments are working hard to tie up loose ends and complete projects before the end of the fiscal year. Economic conditions have caused organizations to do more with less. They are tasked with protecting a growing amount of mission-critical data, often with a shrinking budget. Now is the time to review and adjust your current technology budget, to make room for investing in new services and new technology. It’s also the time of year when you’ll want to spend any remaining 2012 budget. Failing to do so may result in your budget getting reallocated in 2013. The clock is ticking, so make the most of your 2012 budget in the last quarter. Learn some best practices for technology budgeting: Download the Q4 Budget Flush Solution Brief</p><p>The post <a href="http://nscaled.com/make-the-most-of-your-it-budget-in-q4/">Make the Most of Your IT Budget in Q4</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>Welcome to the fourth quarter, the time when most IT departments are working hard to tie up loose ends and complete projects before the end of the fiscal year. Economic conditions have caused organizations to do more with less. They are tasked with protecting a growing amount of mission-critical data, often with a shrinking budget.</p>
<p>Now is the time to review and adjust your current technology budget, to make room for investing in new services and new technology. It’s also the time of year when you’ll want to spend any remaining 2012 budget. Failing to do so may result in your budget getting reallocated in 2013. The clock is ticking, so make the most of your 2012 budget in the last quarter. Learn some best practices for technology budgeting: </p>
<p><a title="Budget Flush Solution Brief" href="http://pages.nscaled.com/budget-flush.html" target="_blank">Download the Q4 Budget Flush Solution Brief</a></p>
<p>The post <a href="http://nscaled.com/make-the-most-of-your-it-budget-in-q4/">Make the Most of Your IT Budget in Q4</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://nscaled.com/make-the-most-of-your-it-budget-in-q4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Never Underestimate Your Resource &amp; Skillset Requirements</title>
		<link>http://nscaled.com/never-underestimate-your-resource-skillset-requirements/</link>
		<comments>http://nscaled.com/never-underestimate-your-resource-skillset-requirements/#comments</comments>
		<pubDate>Thu, 09 Aug 2012 23:04:32 +0000</pubDate>
		<dc:creator>Sarah Grant</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[disaster recovery]]></category>
		<category><![CDATA[dr]]></category>

		<guid isPermaLink="false">http://blog.nscaled.com/blog/?p=400</guid>
		<description><![CDATA[<p>The final post in this series of five hidden DR hazards involves underestimating your resource and skillset requirements. When creating a do-it-yourself disaster recovery solution, you must consider your team’s personal priorities and also their ability to access your remote site. One of the biggest mistakes that you can make is to assume that your staff will be available during a disaster. Because of the interdependence on skillsets that DIY disaster recovery demands, it is virtually impossible to guarantee that your entire team will be available to work during a medium to large scale incident. In a massive geographic disaster, the priorities of your top IT employees will be on personal needs, like the safety and well-being of their families. If you work for a large enough organization, you can mitigate this risk by leveraging skillsets across a variety of offices. If you don’t have this luxury, you should reduce your risk by keeping a consultant or team of consultants on retainer (you’ll need to keep these consultants up to speed as your environment evolves). This is just another example of the unplanned expense of DIY disaster recovery. Making sure users and remote offices can and will be able to reach the disaster recovery site can be challenging. Even if the process is documented thoroughly, it can be difficult to make sure that a workable plan is in place for the event. Careful documentation and frequent meetings will help ensure that all relevant users have access to your DR site. Download the White Paper: &#8220;5 Things That Can Go Wrong with DIY DR&#8221;</p><p>The post <a href="http://nscaled.com/never-underestimate-your-resource-skillset-requirements/">Never Underestimate Your Resource &#038; Skillset Requirements</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>The final post in this series of five hidden DR hazards involves underestimating your resource and skillset requirements. When creating a do-it-yourself disaster recovery solution, you must consider your team’s personal priorities and also their ability to access your remote site.</p>
<p>One of the biggest mistakes that you can make is to assume that your staff will be available during a disaster. Because of the interdependence on skillsets that DIY disaster recovery demands, it is virtually impossible to guarantee that your entire team will be available to work during a medium to large scale incident. In a massive geographic disaster, the priorities of your top IT employees will be on personal needs, like the safety and well-being of their families.</p>
<p>If you work for a large enough organization, you can mitigate this risk by leveraging skillsets across a variety of offices. If you don’t have this luxury, you should reduce your risk by keeping a consultant or team of consultants on retainer (you’ll need to keep these consultants up to speed as your environment evolves). This is just another example of the unplanned expense of DIY disaster recovery.</p>
<p>Making sure users and remote offices can and will be able to reach the disaster recovery site can be challenging. Even if the process is documented thoroughly, it can be difficult to make sure that a workable plan is in place for the event. Careful documentation and frequent meetings will help ensure that all relevant users have access to your DR site. </p>
<p><a title="The 5 Things That Can Go Wrong With DIY DR" href="/5-things-that-can-go-wrong-with-diy-dr/?form=34">Download the White Paper: &#8220;5 Things That Can Go Wrong with DIY DR&#8221;</a></p>
<p>The post <a href="http://nscaled.com/never-underestimate-your-resource-skillset-requirements/">Never Underestimate Your Resource &#038; Skillset Requirements</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://nscaled.com/never-underestimate-your-resource-skillset-requirements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Failed Testing: Another Hidden Hazard of DIY DR</title>
		<link>http://nscaled.com/failed-testing-another-hidden-hazard-of-diy-dr/</link>
		<comments>http://nscaled.com/failed-testing-another-hidden-hazard-of-diy-dr/#comments</comments>
		<pubDate>Mon, 30 Jul 2012 18:15:31 +0000</pubDate>
		<dc:creator>Sarah Grant</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[disaster recovery]]></category>
		<category><![CDATA[remote colocation]]></category>

		<guid isPermaLink="false">http://blog.nscaled.com/blog/?p=397</guid>
		<description><![CDATA[<p>Building a disaster recovery site can be an exciting project for ambitious IT teams. It involves a great deal of planning and results in a high degree of satisfaction once the environment is complete, the budget is justified and the equipment is procured and configured. Overall it is a gratifying experience&#8211; until it’s time to test the solution. Designing a DR testing scenario can be a project in itself. Significant capital expense has to be justified for building the DR site and the return on investment cannot be realized until a test has been developed. Most companies will plan scheduled downtime, take production systems offline, and test the DR site with production offline. This typically involves many hours of late night and weekend work for the IT staff and for the application owners. If the testing is unsuccessful, these complications and costs are multiplied. Get tips for a successful DR test in the nScaled white paper The 5 Things That Can Go Wrong With DIY Disaster Recovery: 5 Things That Can Go Wrong With DIY DR</p><p>The post <a href="http://nscaled.com/failed-testing-another-hidden-hazard-of-diy-dr/">Failed Testing: Another Hidden Hazard of DIY DR</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>Building a disaster recovery site can be an exciting project for ambitious IT teams. It involves a great deal of planning and results in a high degree of satisfaction once the environment is complete, the budget is justified and the equipment is procured and configured. Overall it is a gratifying experience&#8211; until it’s time to test the solution.</p>
<p>Designing a DR testing scenario can be a project in itself. Significant capital expense has to be justified for building the DR site and the return on investment cannot be realized until a test has been developed. Most companies will plan scheduled downtime, take production systems offline, and test the DR site with production offline. This typically involves many hours of late night and weekend work for the IT staff and for the application owners.</p>
<p>If the testing is unsuccessful, these complications and costs are multiplied. Get tips for a successful DR test in the nScaled white paper <em>The 5 Things That Can Go Wrong With DIY Disaster Recovery</em>: <a title="The 5 Things That Can Go Wrong With DIY DR" href="/5-things-that-can-go-wrong-with-diy-dr/?form=34">5 Things That Can Go Wrong With DIY DR</a></p>
<p>The post <a href="http://nscaled.com/failed-testing-another-hidden-hazard-of-diy-dr/">Failed Testing: Another Hidden Hazard of DIY DR</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://nscaled.com/failed-testing-another-hidden-hazard-of-diy-dr/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Avoid Hardware/ Software Drift</title>
		<link>http://nscaled.com/how-to-avoid-hardware-software-drift/</link>
		<comments>http://nscaled.com/how-to-avoid-hardware-software-drift/#comments</comments>
		<pubDate>Tue, 10 Jul 2012 18:38:12 +0000</pubDate>
		<dc:creator>Sarah Grant</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[Cloud Computing]]></category>
		<category><![CDATA[costs]]></category>
		<category><![CDATA[data centres]]></category>
		<category><![CDATA[disaster recovery]]></category>
		<category><![CDATA[diy]]></category>
		<category><![CDATA[dr]]></category>
		<category><![CDATA[dr plan]]></category>
		<category><![CDATA[hardware]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[raas]]></category>
		<category><![CDATA[remote activation power grid failure]]></category>
		<category><![CDATA[software]]></category>

		<guid isPermaLink="false">http://blog.nscaled.com/blog/?p=393</guid>
		<description><![CDATA[<p>I’ve been writing about the hidden hazards of do-it-yourself disaster recovery. One of these hazards is hardware/software drift. Since your disaster recovery site represents a working replica of the production environment, it will need to be maintained on an ongoing basis. There are several strategies for how hardware and software are provisioned for your DR site. The strategies you choose will determine the how much maintenance will be needed to keep your DR site running at an optimal level. There are two main techniques for acquiring hardware for a disaster recovery site, although you may want to use a combination of both. One technique is to replace hardware (i.e. a server) that is no longer covered by warranty with new hardware and use the old hardware for disaster recovery. Another strategy is to buy or lease new equipment to use at the DR site. Most organizations going the DIY route choose to use old equipment because of the low upfront costs. But the challenge with using old equipment is that the hardware is not exactly like the production hardware. This can cause problems with drivers, CPU capabilities and general hardware maintenance. However, buying or leasing new hardware for the disaster recovery site is expensive and can be difficult to justify. When deciding whether or not to buy new equipment, remember to calculate the extra maintenance costs required to keep the DR site up to date in parallel with the production site. Depending on the strategy you choose, you will need to keep software licenses, patch levels, and upgrades in sync. This is also true for applications, operating systems, infrastructure (firmware), and hypervisors. Syncing your applications can significantly increase the amount of work required to maintain [...]</p><p>The post <a href="http://nscaled.com/how-to-avoid-hardware-software-drift/">How to Avoid Hardware/ Software Drift</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>I’ve been writing about the hidden hazards of do-it-yourself disaster recovery. One of these hazards is hardware/software drift. Since your disaster recovery site represents a working replica of the production environment, it will need to be maintained on an ongoing basis. There are several strategies for how hardware and software are provisioned for your DR site. The strategies you choose will determine the how much maintenance will be needed to keep your DR site running at an optimal level.</p>
<p>There are two main techniques for acquiring hardware for a disaster recovery site, although you may want to use a combination of both. One technique is to replace hardware (i.e. a server) that is no longer covered by warranty with new hardware and use the old hardware for disaster recovery. Another strategy is to buy or lease new equipment to use at the DR site.</p>
<p>Most organizations going the DIY route choose to use old equipment because of the low upfront costs. But the challenge with using old equipment is that the hardware is not exactly like the production hardware. This can cause problems with drivers, CPU capabilities and general hardware maintenance. However, buying or leasing new hardware for the disaster recovery site is expensive and can be difficult to justify. When deciding whether or not to buy new equipment, remember to calculate the extra maintenance costs required to keep the DR site up to date in parallel with the production site.</p>
<p>Depending on the strategy you choose, you will need to keep software licenses, patch levels, and upgrades in sync. This is also true for applications, operating systems, infrastructure (firmware), and hypervisors. Syncing your applications can significantly increase the amount of work required to maintain a disaster recovery site. Learn more about syncing your primary and colocation sites in the nScaled white paper <em>The 5 Things That Can Go Wrong With DIY Disaster Recovery</em>: <a title="The 5 Things That Can Go Wrong With DIY DR" href="/5-things-that-can-go-wrong-with-diy-dr/?form=34">5 Things That Can Go Wrong With DIY DR</a></p>
<p>The post <a href="http://nscaled.com/how-to-avoid-hardware-software-drift/">How to Avoid Hardware/ Software Drift</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://nscaled.com/how-to-avoid-hardware-software-drift/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Choose a Remote Colocation Site</title>
		<link>http://nscaled.com/how-to-choose-a-remote-colocation-site/</link>
		<comments>http://nscaled.com/how-to-choose-a-remote-colocation-site/#comments</comments>
		<pubDate>Tue, 03 Jul 2012 16:11:19 +0000</pubDate>
		<dc:creator>Sarah Grant</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[disaster recovery]]></category>
		<category><![CDATA[remote activation power grid failure]]></category>
		<category><![CDATA[remote colocation]]></category>

		<guid isPermaLink="false">http://blog.nscaled.com/blog/?p=387</guid>
		<description><![CDATA[<p>Choosing a disaster recovery location is critical to the success of any DR project. One of the biggest mistakes that you can make is to choose a colocation site that is too close to your production site. It’s way too easy for a power grid failure to knock out both your primary and your colocation site if both sites are located in the same metropolitan area. (It happens!) But the challenge of in-house DR is that the technical team responsible for bringing your DR site online will need access to that site. This means that the approach and technology used to deliver a disaster recovery solution must be capable of remote activation. Learn more about remote activation in the nScaled white paper The 5 Things That Can Go Wrong With DIY Disaster Recovery: 5 Things That Can Go Wrong With DIY DR</p><p>The post <a href="http://nscaled.com/how-to-choose-a-remote-colocation-site/">How to Choose a Remote Colocation Site</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>Choosing a disaster recovery location is critical to the success of any DR project. One of the biggest mistakes that you can make is to choose a colocation site that is too close to your production site. It’s way too easy for a power grid failure to knock out both your primary and your colocation site if both sites are located in the same metropolitan area. (It happens!) But the challenge of in-house DR is that the technical team responsible for bringing your DR site online will need access to that site. This means that the approach and technology used to deliver a disaster recovery solution must be capable of remote activation. Learn more about remote activation in the nScaled white paper <em>The 5 Things That Can Go Wrong With DIY Disaster Recovery</em>: <a title="The 5 Things That Can Go Wrong With DIY DR" href="/5-things-that-can-go-wrong-with-diy-dr/?form=34">5 Things That Can Go Wrong With DIY DR</a></p>
<p>The post <a href="http://nscaled.com/how-to-choose-a-remote-colocation-site/">How to Choose a Remote Colocation Site</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://nscaled.com/how-to-choose-a-remote-colocation-site/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Hidden Hazards of SAN-to-SAN Replication</title>
		<link>http://nscaled.com/the-hidden-hazards-of-san-to-san-replication/</link>
		<comments>http://nscaled.com/the-hidden-hazards-of-san-to-san-replication/#comments</comments>
		<pubDate>Thu, 28 Jun 2012 17:16:16 +0000</pubDate>
		<dc:creator>Sarah Grant</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[disaster recovery]]></category>
		<category><![CDATA[diy]]></category>
		<category><![CDATA[dr]]></category>
		<category><![CDATA[san to san replication]]></category>
		<category><![CDATA[snapshot storage requirements]]></category>
		<category><![CDATA[virtualization]]></category>

		<guid isPermaLink="false">http://blog.nscaled.com/blog/?p=383</guid>
		<description><![CDATA[<p>It might be tempting to create a “do-it-yourself” disaster recovery solution by purchasing additional hardware and installing it in a branch office or colocation facility. But creating an effective disaster recovery solution is a complex project and there are several unplanned costs and other hidden hazards associated with it. I’ll identify some of these hidden hazards over the next few weeks. I’ll begin with SAN to SAN replication. Any SAN manufacturer with a clear understanding of storage space has some kind of SAN to SAN replication offer, but not all SAN to SAN replication is alike. When creating an effective DR solution, you have to make several architectural considerations for replicating data between production and DR, including virtualization, application specific agents and snapshot storage requirements. Once all of these architectural considerations have been addressed, you must bring the copies of each server online. There are several approaches that you can take, depending on the complexity of your servers. This means that thorough documentation must be developed and refined throughout the life and evolution of your DR site. This is an ongoing process and you must also remember to include plenty of time for testing. Learn more about SAN to SAN replication in nScaled’s white paper The 5 Things That Can Go Wrong With DIY Disaster Recovery: 5 Things That Can Go Wrong With DIY DR</p><p>The post <a href="http://nscaled.com/the-hidden-hazards-of-san-to-san-replication/">The Hidden Hazards of SAN-to-SAN Replication</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>It might be tempting to create a “do-it-yourself” disaster recovery solution by purchasing additional hardware and installing it in a branch office or colocation facility. But creating an effective disaster recovery solution is a complex project and there are several unplanned costs and other hidden hazards associated with it. I’ll identify some of these hidden hazards over the next few weeks.</p>
<p>I’ll begin with SAN to SAN replication. Any SAN manufacturer with a clear understanding of storage space has some kind of SAN to SAN replication offer, but not all SAN to SAN replication is alike. When creating an effective DR solution, you have to make several architectural considerations for replicating data between production and DR, including virtualization, application specific agents and snapshot storage requirements.</p>
<p>Once all of these architectural considerations have been addressed, you must bring the copies of each server online. There are several approaches that you can take, depending on the complexity of your servers. This means that thorough documentation must be developed and refined throughout the life and evolution of your DR site. This is an ongoing process and you must also remember to include plenty of time for testing.</p>
<p>Learn more about SAN to SAN replication in nScaled’s white paper The 5 Things That Can Go Wrong With DIY Disaster Recovery: <a title="The 5 Things That Can Go Wrong With DIY DR" href="/5-things-that-can-go-wrong-with-diy-dr/?form=34">5 Things That Can Go Wrong With DIY DR</a></p>
<p>The post <a href="http://nscaled.com/the-hidden-hazards-of-san-to-san-replication/">The Hidden Hazards of SAN-to-SAN Replication</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://nscaled.com/the-hidden-hazards-of-san-to-san-replication/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Recovery-in-a-Cave</title>
		<link>http://nscaled.com/recovery-in-a-cave/</link>
		<comments>http://nscaled.com/recovery-in-a-cave/#comments</comments>
		<pubDate>Fri, 04 May 2012 16:02:50 +0000</pubDate>
		<dc:creator>Andrew Lochart</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.nscaled.com/blog/?p=375</guid>
		<description><![CDATA[<p>Just got done reading the funniest white paper ever, from our friends at Iron Mountain. It asks the question, “…what happens when the devastation is so fierce that it hits the backups too? Don’t panic.” Don’t panic? Really? I think you damn well better panic – about your career. You stashed your backup tapes so close to your primary data center that they got clobbered by the same natural disaster? C’mon man! Better update that resume. And while we’re at it, why on earth are you still using tape? Iron Mountain, whose business is storing tape, points out just how fragile tape is: “…if tapes suffer major temperature fluctuations every night, they will weaken and become more likely to snap. When your staff fails to maintain drive heads’ cleanliness, or cleans equipment incorrectly, tapes may be more prone to breaking. To avoid such problems, know the cleaning cycle and storage conditions recommended by your vendor.” Snapping tapes? Drive head cleaning cycles? Fred Flintstone had to put up with this nonsense, but you do not. The punch line comes at the end of this litany of All The Things That Can Go Wrong With Tape when IM reminds us that they have a nice, safe cave where you can stash your tapes. A cave? What is this, the Al Qaeda approach to disaster recovery? Do they use mules to get the tapes into the cave? Look, disk-to-disk backup is mature; backup-to-the-cloud is mature; snapshotting, de-duplication, and virtualization are mature; and recovery-as-a-service (RaaS) is now mature. There is no excuse for backup to tape, and no excuse for sticking your tapes – and your company’s chances of recovery – in a cave.</p><p>The post <a href="http://nscaled.com/recovery-in-a-cave/">Recovery-in-a-Cave</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>Just got done reading the funniest white paper ever, from our friends at Iron Mountain. It asks the question, “…what happens when the devastation is so fierce that it hits the backups too? Don’t panic.”</p>
<p>Don’t panic? Really? I think you damn well better panic – about your career. You stashed your backup tapes so close to your primary data center that they got clobbered by the same natural disaster? C’mon man! Better update that resume.</p>
<p>And while we’re at it, why on earth are you still using tape? Iron Mountain, whose business is storing tape, points out just how fragile tape is:</p>
<p style="padding-left: 30px;">“…if tapes suffer major temperature fluctuations every night, they will weaken and become more likely to snap. When your staff fails to maintain drive heads’ cleanliness, or cleans equipment incorrectly, tapes may be more prone to breaking. To avoid such problems, know the cleaning cycle and storage conditions recommended by your vendor.”</p>
<p>Snapping tapes? Drive head cleaning cycles? Fred Flintstone had to put up with this nonsense, but you do not.</p>
<p>The punch line comes at the end of this litany of All The Things That Can Go Wrong With Tape when IM reminds us that they have a nice, safe cave where you can stash your tapes. A cave? What is this, the Al Qaeda approach to disaster recovery? Do they use mules to get the tapes into the cave?</p>
<p>Look, disk-to-disk backup is mature; backup-to-the-cloud is mature; snapshotting, de-duplication, and virtualization are mature; and recovery-as-a-service (RaaS) is now mature. There is no excuse for backup to tape, and no excuse for sticking your tapes – and your company’s chances of recovery – in a cave.</p>
<p>The post <a href="http://nscaled.com/recovery-in-a-cave/">Recovery-in-a-Cave</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://nscaled.com/recovery-in-a-cave/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Really?</title>
		<link>http://nscaled.com/really/</link>
		<comments>http://nscaled.com/really/#comments</comments>
		<pubDate>Wed, 04 Apr 2012 14:49:51 +0000</pubDate>
		<dc:creator>BrunchWeb</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://199.193.156.119/?p=360</guid>
		<description><![CDATA[<p>Disco Stu has moved from Springfield to the world of backup and DR. Earlier this week, eVault announced 4-hour recovery times for their mid-size business customers. This is one of those mind boggling announcements that gets a lot of us in the business saying, “Really?” Because the thing is, in 2012, a 4-hour recovery time is terrible. They never explain if the 4-hour guarantee applies to any single system or an entire data center. In either case, eVault’s claim is just plain archaic. For the sake of comparison, nScaled offers customers a 15-minute RTO for any single system, and a 2-hour RTO for an entire data center. And, it turns out, the 4-hour SLA is available for a very limited selection of OSs and applications. I don’t think a single one of our customers has an IT environment simplistic enough to qualify for their 4-hour guarantee, and would be forced to choose the 24- and 48-hour options that eVault offers. As Disco Stu once said, “Did you know that disco record sales were up 400% for the year ending 1976? If these trends continues&#8230; AAY!” Really?</p><p>The post <a href="http://nscaled.com/really/">Really?</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></description>
				<content:encoded><![CDATA[<p><a href="http://simpsons.wikia.com/wiki/Disco_Stu" target="_blank">Disco Stu</a> has moved from Springfield to the world of backup and DR.</p>
<p>Earlier this week, eVault announced 4-hour recovery times for their mid-size business customers. This is one of those mind boggling announcements that gets a lot of us in the business saying, “Really?”</p>
<p><a href="http://blog.nscaled.com/blog/?attachment_id=361" rel="attachment wp-att-361"><img class="aligncenter size-full wp-image-361" title="disco_stu" src="http://199.193.156.119/wp-content/uploads/2012/04/disco_stu.png" alt="" width="565" height="677" /></a></p>
<p>Because the thing is, in 2012, a 4-hour recovery time is terrible. They never explain if the 4-hour guarantee applies to any single system or an entire data center. In either case, eVault’s claim is just plain archaic.</p>
<p>For the sake of comparison, nScaled offers customers a 15-minute RTO for any single system, and a 2-hour RTO for an entire data center.</p>
<p>And, it turns out, the 4-hour SLA is available for a very limited selection of OSs and applications. I don’t think a single one of our customers has an IT environment simplistic enough to qualify for their 4-hour guarantee, and would be forced to choose the 24- and 48-hour options that eVault offers.</p>
<p>As Disco Stu once said,</p>
<p>“Did you know that disco record sales were up 400% for the year ending 1976? If these trends continues&#8230; AAY!”</p>
<p>Really?</p>
<p>The post <a href="http://nscaled.com/really/">Really?</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://nscaled.com/really/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Boston Fire leads to customer failover</title>
		<link>http://nscaled.com/boston-fire-leads-to-customer-failover/</link>
		<comments>http://nscaled.com/boston-fire-leads-to-customer-failover/#comments</comments>
		<pubDate>Wed, 14 Mar 2012 15:25:56 +0000</pubDate>
		<dc:creator>Andrew Lochart</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.nscaled.com/?p=354</guid>
		<description><![CDATA[<p>You may have read about the fire in Boston yesterday that took out power for a section of the city. The power outage affected the Boston office one of our large disaster recovery customers. We protect 70 servers in 11 offices around the US for this customer. Our support guys were up late last night, getting the customer failed over so they could keep working through the interruption, so I haven’t had a chance to get the detailed story from them. I’ll post again when I have more news.</p><p>The post <a href="http://nscaled.com/boston-fire-leads-to-customer-failover/">Boston Fire leads to customer failover</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></description>
				<content:encoded><![CDATA[<p>You may have read about the fire in Boston yesterday that took out power for a section of the city.</p>
<p>The power outage affected the Boston office one of our large disaster recovery customers. We protect 70 servers in 11 offices around the US for this customer.</p>
<p>Our support guys were up late last night, getting the customer failed over so they could keep working through the interruption, so I haven’t had a chance to get the detailed story from them. I’ll post again when I have more news.</p>
<p>The post <a href="http://nscaled.com/boston-fire-leads-to-customer-failover/">Boston Fire leads to customer failover</a> appeared first on <a href="http://nscaled.com">nScaled, Inc.</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://nscaled.com/boston-fire-leads-to-customer-failover/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
