<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://dotnet.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Articles by Bruce Backa</title>
 <link>http://dotnet.sys-con.com/</link>
 <description>Latest articles from Bruce Backa</description>
 <language>en</language>
 <copyright>Copyright 2008 SYS-CON Media</copyright>
 <generator>SYS-CON Media</generator>
 <lastBuildDate>Sun, 07 Sep 2008 03:27:01 EDT</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>10</ttl>
<item>
 <title>Storage &amp; Security Journal: &quot;Striking the Right Balance&quot;</title>
 <link>http://dotnet.sys-con.com/node/187526</link>
 <description>Storage is still one of the most costly and fastest-growing aspects of everyone&#039;s network and is likely to remain so for some time. Every network user is a storage user. We&#039;re all part of a community that shares the costs and the benefits of this expensive resource. Storage management can be a challenging task. There&#039;s so much hardware, so many alternatives, and so many issues that it&#039;s easy to get lost in the details and fail to see the forest for the trees.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/187526&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 27 Feb 2006 15:45:00 EST</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/187526</guid>
</item>
<item>
 <title>Where&#039;s the money?</title>
 <link>http://dotnet.sys-con.com/node/163688</link>
 <description>Remarkably, as we work with clients we discover that they rarely analyze the component costs of their operations. So let me make this easy: the bulk of the money is in whatever you do for data protection. But even if you know this, have you looked at the details of what you&#039;re protecting and how it flows through you systems? What components make up the bits you write? How often do you write them and why?&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/163688&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 14 Dec 2005 11:45:00 EST</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/163688</guid>
</item>
<item>
 <title>What&#039;s In Store For 2006?</title>
 <link>http://dotnet.sys-con.com/node/159547</link>
 <description>Okay, 2005 is over. Let&#039;s get back to work...But first, let&#039;s look at what&#039;s new. Microsoft has taken WinFS, its new file system, out of the first release of its next operating system. The story is that WinFS will follow soon after the OS releases. For most of us, this is something we don&#039;t need to worry about for a couple of years, at least.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/159547&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 02 Dec 2005 11:00:00 EST</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/159547</guid>
</item>
<item>
 <title>Bruce Backa&#039;s Storage Blog: The New Economics</title>
 <link>http://dotnet.sys-con.com/node/158980</link>
 <description>Tape used to be much cheaper than on-line storage. Not any more. While it is still neither infinite nor free (and it&#039;s certainly not free to manage), on-line storage is pretty inexpensive these days. A smaller company needs tapes for disaster recovery (although on-line vendor-based alternatives exist), but daily backups should be on-line.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/158980&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 01 Dec 2005 06:00:00 EST</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/158980</guid>
</item>
<item>
 <title>Information Security - No Longer the Perennial Afterthought</title>
 <link>http://dotnet.sys-con.com/node/130103</link>
 <description>Storage always seems to come first in technical discussions and security seems to be the perennial afterthought. This can be considered reasonable given how we shop for things in general, namely finding the thing that meets our expectations and then ensure it has all the bells and whistles. The good news is that this seems to be changing bit by bit as our industry realizes that security is no longer a nice-to-have feature, but is actually a core requirement.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/130103&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 14 Sep 2005 13:30:00 EDT</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/130103</guid>
</item>
<item>
 <title>A Quick Look at the Coming Year in Storage...</title>
 <link>http://dotnet.sys-con.com/node/101580</link>
 <description>We (Patrick and Bruce) are new to ISSJ. In a future article, you&#039;ll learn more about who we are and why we are here. In this issue, we thought we would take a minute to frame some of the discussions that will go on throughout the year.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/101580&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 17 Jun 2005 13:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/101580</guid>
</item>
<item>
 <title>How to Avoid Creating a Network Security Hole with Your Windows Server-Based App</title>
 <link>http://dotnet.sys-con.com/node/86221</link>
 <description>Nowadays it&#039;s quite common for us to write server-based applications. These apps differ from desktop applications in many ways - one of the most important of which is how they handle security. For a desktop application, security is easy. The application runs in the security context of the user who loaded it. Whatever the user has rights to, the desktop app has rights to, and nothing more. Server-based applications, on the other hand, run all the time and have their own security context, in addition to others they may impersonate.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/86221&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 20 May 2005 11:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/86221</guid>
</item>
<item>
 <title>BizTalk Server 2004 Technical Drilldown</title>
 <link>http://dotnet.sys-con.com/node/37963</link>
 <description>Come and join us for a technical drilldown on BizTalk Server 2004 - including the new features and toolsets available to help you solve Enterprise Application Integration (EAI), Business Process Automation (BPA) and Information Worker Integration.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/37963&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 26 Feb 2004 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/37963</guid>
</item>
<item>
 <title>End-to-End Application Security</title>
 <link>http://dotnet.sys-con.com/node/39064</link>
 <description>Last month (.NETDJ, Vol. 1, issue 12) we demonstrated a simple technique that allows you to avoid storing passwords in clear text, making your .NET applications more secure and safer should they somehow be compromised. In this article, we want to step back a bit and look at the big picture: application security from end to end.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/39064&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 12 Jan 2004 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/39064</guid>
</item>
<item>
 <title>Advanced BizTalk Server 2004</title>
 <link>http://dotnet.sys-con.com/node/38098</link>
 <description>x&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/38098&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 04 Dec 2003 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/38098</guid>
</item>
</channel>
</rss>
