<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Vss on BAFM</title><link>https://christian.blog.pakiheim.de/tags/vss/</link><description>Recent content in Vss on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Thu, 26 Jan 2012 21:02:09 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/vss/index.xml" rel="self" type="application/rss+xml"/><item><title>Doing TSM's job on Windows Server 2008</title><link>https://christian.blog.pakiheim.de/posts/2012-01-26_doing-tsm-s-job-on-windows-server-2008/</link><pubDate>Thu, 26 Jan 2012 21:02:09 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=4064</guid><description>&lt;p&gt;Ran into another weird problem the other day &amp;hellip; Had a few Windows boxens running out of space. Why ? Well, because TSM includes a System-State backup when creating the daily incremental. Now, apparently (as stated by the IBM support) it isn&amp;rsquo;t TSM&amp;rsquo;s job to keep track of the VSS snapshots but rather Windows&amp;rsquo;. Now by default, if you don&amp;rsquo;t click on the VSS properties of a Windows drive, there is no limit on the volume. Thus, VSS is slowly eating up all your space.&lt;/p&gt;</description></item></channel></rss>