<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Automated Windows Server Backups on AWS EC2</title>
	<atom:link href="http://www.noahlh.com/blog/2014/07/automated-windows-server-backups-on-aws-ec2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.noahlh.com/blog/2014/07/automated-windows-server-backups-on-aws-ec2/</link>
	<description>Figuring out the world, one day at a time.</description>
	<lastBuildDate>Wed, 30 Jul 2014 19:08:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4</generator>
	<item>
		<title>By: noahlh</title>
		<link>http://www.noahlh.com/blog/2014/07/automated-windows-server-backups-on-aws-ec2/comment-page-1/#comment-386</link>
		<dc:creator>noahlh</dc:creator>
		<pubDate>Wed, 30 Jul 2014 19:08:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.noahlh.com/blog/?p=23#comment-386</guid>
		<description>Hi Gavin -- no, no verification of consistency -- it&#039;s just a raw snapshot output.  I haven&#039;t had any issues so far -- have restored once and had zero problems.  But I imagine that putting some consistency-checking in there would be a good thing (a bit beyond my know-how right now though).

The restore process for me is pretty straightforward -- you use the same instance and create a new EBS volume from the snapshot(s), then assign the correct device path on AWS (i.e. /dev/sda1, xvdb, etc.) and attach the new volumes that were built from the snapshots.  All seems to work fine for me.  See here:

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-restoring-volume.html</description>
		<content:encoded><![CDATA[<p>Hi Gavin &#8212; no, no verification of consistency &#8212; it&#8217;s just a raw snapshot output.  I haven&#8217;t had any issues so far &#8212; have restored once and had zero problems.  But I imagine that putting some consistency-checking in there would be a good thing (a bit beyond my know-how right now though).</p>
<p>The restore process for me is pretty straightforward &#8212; you use the same instance and create a new EBS volume from the snapshot(s), then assign the correct device path on AWS (i.e. /dev/sda1, xvdb, etc.) and attach the new volumes that were built from the snapshots.  All seems to work fine for me.  See here:</p>
<p><a href="http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-restoring-volume.html" rel="nofollow">http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-restoring-volume.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gavin Hamill</title>
		<link>http://www.noahlh.com/blog/2014/07/automated-windows-server-backups-on-aws-ec2/comment-page-1/#comment-381</link>
		<dc:creator>Gavin Hamill</dc:creator>
		<pubDate>Tue, 08 Jul 2014 20:55:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.noahlh.com/blog/?p=23#comment-381</guid>
		<description>What a wonderful piece of work! Thank you not only for doing it and making it public, but also putting it on Github!

Do the scripts do anything to ensure a consistent snapshot e.g. any kind of VSS? If not. have you had any problems with backup integrity?

What would be the restore process? EC2 is a pain that you can&#039;t just create a &#039;blank&#039; Windows instance and attach an EBS volume as its root in the way you can with Linux instances. How have you solved that?

Cheers,
Gavin.

Before now I&#039;ve just had to launch a new Windows EC2 instance, and &#039;stop&#039; it as soon as it moves to</description>
		<content:encoded><![CDATA[<p>What a wonderful piece of work! Thank you not only for doing it and making it public, but also putting it on Github!</p>
<p>Do the scripts do anything to ensure a consistent snapshot e.g. any kind of VSS? If not. have you had any problems with backup integrity?</p>
<p>What would be the restore process? EC2 is a pain that you can&#8217;t just create a &#8216;blank&#8217; Windows instance and attach an EBS volume as its root in the way you can with Linux instances. How have you solved that?</p>
<p>Cheers,<br />
Gavin.</p>
<p>Before now I&#8217;ve just had to launch a new Windows EC2 instance, and &#8216;stop&#8217; it as soon as it moves to</p>
]]></content:encoded>
	</item>
</channel>
</rss>
