<?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: Druvaa inSync Roadmap</title>
	<atom:link href="http://blog.druva.com/2008/09/24/druvaa-insync-roadmap/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.druva.com/2008/09/24/druvaa-insync-roadmap/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=druvaa-insync-roadmap</link>
	<description>Enterprise Data Backup and Beyond</description>
	<lastBuildDate>Thu, 26 May 2011 12:12:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Jaspreet</title>
		<link>http://blog.druva.com/2008/09/24/druvaa-insync-roadmap/#comment-254</link>
		<dc:creator>Jaspreet</dc:creator>
		<pubDate>Wed, 15 Oct 2008 14:01:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.druvaa.com/?p=48#comment-254</guid>
		<description>Walton,

thanks for trying insync.

the v2.2 would be available on the website in a day or so</description>
		<content:encoded><![CDATA[<p>Walton,</p>
<p>thanks for trying insync.</p>
<p>the v2.2 would be available on the website in a day or so</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T Walton</title>
		<link>http://blog.druva.com/2008/09/24/druvaa-insync-roadmap/#comment-253</link>
		<dc:creator>T Walton</dc:creator>
		<pubDate>Wed, 15 Oct 2008 13:11:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.druvaa.com/?p=48#comment-253</guid>
		<description>Started testing v2.1.1 this week.

Have been using BackuExec DLO for some time.

New features in v2.2 seem to resolve issues I already have.  When are we likely to see this so we can test it?</description>
		<content:encoded><![CDATA[<p>Started testing v2.1.1 this week.</p>
<p>Have been using BackuExec DLO for some time.</p>
<p>New features in v2.2 seem to resolve issues I already have.  When are we likely to see this so we can test it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aciampoli</title>
		<link>http://blog.druva.com/2008/09/24/druvaa-insync-roadmap/#comment-252</link>
		<dc:creator>Aciampoli</dc:creator>
		<pubDate>Tue, 14 Oct 2008 15:48:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.druvaa.com/?p=48#comment-252</guid>
		<description>Just wondering if 2.2 has been released yet.</description>
		<content:encoded><![CDATA[<p>Just wondering if 2.2 has been released yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Faisal</title>
		<link>http://blog.druva.com/2008/09/24/druvaa-insync-roadmap/#comment-251</link>
		<dc:creator>Faisal</dc:creator>
		<pubDate>Tue, 30 Sep 2008 06:28:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.druvaa.com/?p=48#comment-251</guid>
		<description>Pete,

The new reporting mechanism is basically streamlining the current reporting process into something we can expand on fairly easily. For starters, we now have an idea of alerts and notifications. We have classified alerts into different levels of severity. This allows us to handle notifications and behavior with more fine-grained control. With subsequent releases, we hope to fine-tune this and allow more user control with the whole notification and reporting engine.

W.r.t Mac support, it&#039;s definitely in the pipeline. But I can&#039;t commit on a date for that. 

-Faisal</description>
		<content:encoded><![CDATA[<p>Pete,</p>
<p>The new reporting mechanism is basically streamlining the current reporting process into something we can expand on fairly easily. For starters, we now have an idea of alerts and notifications. We have classified alerts into different levels of severity. This allows us to handle notifications and behavior with more fine-grained control. With subsequent releases, we hope to fine-tune this and allow more user control with the whole notification and reporting engine.</p>
<p>W.r.t Mac support, it&#8217;s definitely in the pipeline. But I can&#8217;t commit on a date for that. </p>
<p>-Faisal</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete</title>
		<link>http://blog.druva.com/2008/09/24/druvaa-insync-roadmap/#comment-250</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Fri, 26 Sep 2008 17:13:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.druvaa.com/?p=48#comment-250</guid>
		<description>I have been testing this for a month, very smooth backup almost invisible.

Can you please elaborate on new reporting ?

Mac support ?

What is the max. scalability of v2.2 on single backup server  (4-core machine, 4 GB RAM) ? Can it take load for 500+ ?</description>
		<content:encoded><![CDATA[<p>I have been testing this for a month, very smooth backup almost invisible.</p>
<p>Can you please elaborate on new reporting ?</p>
<p>Mac support ?</p>
<p>What is the max. scalability of v2.2 on single backup server  (4-core machine, 4 GB RAM) ? Can it take load for 500+ ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jaspreet</title>
		<link>http://blog.druva.com/2008/09/24/druvaa-insync-roadmap/#comment-249</link>
		<dc:creator>Jaspreet</dc:creator>
		<pubDate>Fri, 26 Sep 2008 17:01:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.druvaa.com/?p=48#comment-249</guid>
		<description>@aciampoli

This happens even now, profile changes are automatically pushed/applied to the client when the client requests a new backup.

inSync is a client triggered backup architecture, where client always initiates all requests. So, before any new backup request, the client downloads and updates any new profile changes.

The client triggered architecture has various advantages - 
1. Backup over WAN/Internet (where client doesn&#039;t have visible IP)
2. Secure - server never initiates a out-bound request.
3. Scalable - backup intelligence is embedded into the client and hence load is distributed.

I hope this information helped.

- Jas</description>
		<content:encoded><![CDATA[<p>@aciampoli</p>
<p>This happens even now, profile changes are automatically pushed/applied to the client when the client requests a new backup.</p>
<p>inSync is a client triggered backup architecture, where client always initiates all requests. So, before any new backup request, the client downloads and updates any new profile changes.</p>
<p>The client triggered architecture has various advantages &#8211;<br />
1. Backup over WAN/Internet (where client doesn&#8217;t have visible IP)<br />
2. Secure &#8211; server never initiates a out-bound request.<br />
3. Scalable &#8211; backup intelligence is embedded into the client and hence load is distributed.</p>
<p>I hope this information helped.</p>
<p>- Jas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aciampoli</title>
		<link>http://blog.druva.com/2008/09/24/druvaa-insync-roadmap/#comment-248</link>
		<dc:creator>Aciampoli</dc:creator>
		<pubDate>Fri, 26 Sep 2008 16:23:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.druvaa.com/?p=48#comment-248</guid>
		<description>Automatic push to client when changes in the profile are detected.

If I need to add a new folder to the backup right away, I need to make the changes and then generate a new key for every user. Then update the key on every laptop.

This is ok for a small office but I have over 40 laptops in 5 different countries getting this done very quickly is almost impossible.

If the update could get propagated to the user automatically that would make management and deployment so much simpler.</description>
		<content:encoded><![CDATA[<p>Automatic push to client when changes in the profile are detected.</p>
<p>If I need to add a new folder to the backup right away, I need to make the changes and then generate a new key for every user. Then update the key on every laptop.</p>
<p>This is ok for a small office but I have over 40 laptops in 5 different countries getting this done very quickly is almost impossible.</p>
<p>If the update could get propagated to the user automatically that would make management and deployment so much simpler.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Milind</title>
		<link>http://blog.druva.com/2008/09/24/druvaa-insync-roadmap/#comment-247</link>
		<dc:creator>Milind</dc:creator>
		<pubDate>Fri, 26 Sep 2008 06:33:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.druvaa.com/?p=48#comment-247</guid>
		<description>Admin side folders is addressed in 2.2. It&#039;s the first item in the list.

We are planning a controlled beta for Linux, tentatively by Oct 15. Keep watching the blog space.

Beta is not planned for 2.2. We&#039;ll certainly have it for 3.0.</description>
		<content:encoded><![CDATA[<p>Admin side folders is addressed in 2.2. It&#8217;s the first item in the list.</p>
<p>We are planning a controlled beta for Linux, tentatively by Oct 15. Keep watching the blog space.</p>
<p>Beta is not planned for 2.2. We&#8217;ll certainly have it for 3.0.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TC</title>
		<link>http://blog.druva.com/2008/09/24/druvaa-insync-roadmap/#comment-246</link>
		<dc:creator>TC</dc:creator>
		<pubDate>Fri, 26 Sep 2008 05:14:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.druvaa.com/?p=48#comment-246</guid>
		<description>I was promised Linux port and admin side folders two months back. I hope you stick to this date now :)

Linux backup should have big market here in europe.

v2.2 seems like a big release. Is there a beta for 2.2 or 3.0 ?</description>
		<content:encoded><![CDATA[<p>I was promised Linux port and admin side folders two months back. I hope you stick to this date now <img src='http://blog.druva.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Linux backup should have big market here in europe.</p>
<p>v2.2 seems like a big release. Is there a beta for 2.2 or 3.0 ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

