<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Kommentare zu: Time Machine backups on network shares 2: possible problems</title>
	<link>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/</link>
	<description>Belanglosigkeiten aus meinem Leben</description>
	<pubDate>Fri, 21 Nov 2008 18:06:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>Von: michi</title>
		<link>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-8684</link>
		<dc:creator>michi</dc:creator>
		<pubDate>Thu, 28 Aug 2008 10:14:38 +0000</pubDate>
		<guid>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-8684</guid>
		<description>sorry, hab gleich gesehen das das problem im update gelöst ist...nevermind.</description>
		<content:encoded><![CDATA[<p>sorry, hab gleich gesehen das das problem im update gelöst ist&#8230;nevermind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: michi</title>
		<link>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-8683</link>
		<dc:creator>michi</dc:creator>
		<pubDate>Thu, 28 Aug 2008 10:12:20 +0000</pubDate>
		<guid>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-8683</guid>
		<description>hi

you mention that 

"There is a possibility to reclaim unoccupied space via hdiutil. However, as Time Machine does not utilize it I will ignore this possibility here." and "Regularly delete old backups in Time Machine manually and reclaim freed space via hdiutil. Most complicated but also the most flexible solution."

would you have a hint as to how this is done? i.e. what is the terminal command to use to free that space? thanks a lot, as i am not very versed in terminal...</description>
		<content:encoded><![CDATA[<p>hi</p>
<p>you mention that </p>
<p>&#8220;There is a possibility to reclaim unoccupied space via hdiutil. However, as Time Machine does not utilize it I will ignore this possibility here.&#8221; and &#8220;Regularly delete old backups in Time Machine manually and reclaim freed space via hdiutil. Most complicated but also the most flexible solution.&#8221;</p>
<p>would you have a hint as to how this is done? i.e. what is the terminal command to use to free that space? thanks a lot, as i am not very versed in terminal&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: William K</title>
		<link>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-7105</link>
		<dc:creator>William K</dc:creator>
		<pubDate>Tue, 29 Apr 2008 16:19:41 +0000</pubDate>
		<guid>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-7105</guid>
		<description>I'm finding the wording in the original post a bit unclear.  Let me try to restate:

  It sounds like the formula for calculating free space in a mounted
  sparse image is flawed in Leopard.  Instead of adding the free
  space from the containing volume to the free space inside the
  image, Leopard uses the _minimum_ of free space in the Volume
  and the mounted image.  I can imagine that the erroneous free
  space calculation results in certain processes running out of
  space when there is really enough space.  Perhaps higher level software is using a correct free space calculation and then gets stopped while trying to write a file for which there is really enough free space. Maybe the lower level image management/driver code likely throws an error thinking there isn't enough space?

Does this make sense?

My problems has to do with trying to maintain backups from two different desktop macs on the same hard drive which is network mounted via an Airport Extreme.  Perhaps the free space showing in Finder is leading me to believe there is room for all backups while Time Machine thinks it's out of space due to this free space calculation error?</description>
		<content:encoded><![CDATA[<p>I&#8217;m finding the wording in the original post a bit unclear.  Let me try to restate:</p>
<p>  It sounds like the formula for calculating free space in a mounted<br />
  sparse image is flawed in Leopard.  Instead of adding the free<br />
  space from the containing volume to the free space inside the<br />
  image, Leopard uses the _minimum_ of free space in the Volume<br />
  and the mounted image.  I can imagine that the erroneous free<br />
  space calculation results in certain processes running out of<br />
  space when there is really enough space.  Perhaps higher level software is using a correct free space calculation and then gets stopped while trying to write a file for which there is really enough free space. Maybe the lower level image management/driver code likely throws an error thinking there isn&#8217;t enough space?</p>
<p>Does this make sense?</p>
<p>My problems has to do with trying to maintain backups from two different desktop macs on the same hard drive which is network mounted via an Airport Extreme.  Perhaps the free space showing in Finder is leading me to believe there is room for all backups while Time Machine thinks it&#8217;s out of space due to this free space calculation error?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: jct888</title>
		<link>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-7037</link>
		<dc:creator>jct888</dc:creator>
		<pubDate>Wed, 23 Apr 2008 04:23:38 +0000</pubDate>
		<guid>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-7037</guid>
		<description>PS Of course after posting "there's no easy way...", I found this on Mac OS X Hints (http://www.macosxhints.com/article.php?story=20071101005330768)

10.5: How to delete objects from Time Machine backups
Wed, Nov 14 '07 at 7:30AM PST • Submitted by iGrouch	
This is a something that Apple has hidden away, leaving some Mac users out there to go through all sorts of lengths to remove items from their Time Machine backups. 

The solution is really easy, though. 

Open time Machine. Go to the top level -- the first window; the one with your hard drive. Navigate to the backup you want to delete and use the Actions menu (gear icon) in the Finder's toolbar. It has an option to delete the backup. Also, when using the Actions menu, with a file or folder selected, there is an option to delete all instances of the file/folder from all backups.</description>
		<content:encoded><![CDATA[<p>PS Of course after posting &#8220;there&#8217;s no easy way&#8230;&#8221;, I found this on Mac OS X Hints (http://www.macosxhints.com/article.php?story=20071101005330768)</p>
<p>10.5: How to delete objects from Time Machine backups<br />
Wed, Nov 14 &#8216;07 at 7:30AM PST • Submitted by iGrouch<br />
This is a something that Apple has hidden away, leaving some Mac users out there to go through all sorts of lengths to remove items from their Time Machine backups. </p>
<p>The solution is really easy, though. </p>
<p>Open time Machine. Go to the top level &#8212; the first window; the one with your hard drive. Navigate to the backup you want to delete and use the Actions menu (gear icon) in the Finder&#8217;s toolbar. It has an option to delete the backup. Also, when using the Actions menu, with a file or folder selected, there is an option to delete all instances of the file/folder from all backups.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: jct888</title>
		<link>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-7035</link>
		<dc:creator>jct888</dc:creator>
		<pubDate>Wed, 23 Apr 2008 04:06:38 +0000</pubDate>
		<guid>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-7035</guid>
		<description>Not obsolete if you have this problem (which I ran into and still don't have a fix for it.  The free space on the Time Machine drive didn't give back its free space after deleting the backup data my moving it to the trash and emptying it.  Normally I would simply reformat the drive, but it has some data on it that I need. 

While I'm glad the "new" software from Apple fixes the from the problem from this point forward, it's not clear or likely that it will go box and update the free space to agree with the Capacity - Used = Free.  In other words, despite deleting Time Machine bakcup files (/Backups.backupb//{folder1,...,folderN), when free space was down to 40 GB (on a 600 GB drive), with 200 GB of other files, the free space is still only 40 GB!  This suggests not using a drive for Time Machine to keep any other data, at the least. 

So I'll find another drive on which to move the data I need (200 GB), reformat, and then think about using Time Machine again. While the visual part of Time Machine is a nice way to understand the timeframe backups, there's no easy way to reclaim the free space or need to understand why, without some technical background.  

Thanks very much for posting the findings, information, and fixes, and good news for those who want to continue using Time Machine. I'm now going to use a Time Capsule and not put anything else on it.  If Apple had spent just a little more time testing these boundary conditions, instead of leaving it to the customer, we all may not have had to suffer the discovery and lost of time and data.  Pushing out a complex feature like this without fully flushing out such a major problem is just silly.</description>
		<content:encoded><![CDATA[<p>Not obsolete if you have this problem (which I ran into and still don&#8217;t have a fix for it.  The free space on the Time Machine drive didn&#8217;t give back its free space after deleting the backup data my moving it to the trash and emptying it.  Normally I would simply reformat the drive, but it has some data on it that I need. </p>
<p>While I&#8217;m glad the &#8220;new&#8221; software from Apple fixes the from the problem from this point forward, it&#8217;s not clear or likely that it will go box and update the free space to agree with the Capacity - Used = Free.  In other words, despite deleting Time Machine bakcup files (/Backups.backupb//{folder1,&#8230;,folderN), when free space was down to 40 GB (on a 600 GB drive), with 200 GB of other files, the free space is still only 40 GB!  This suggests not using a drive for Time Machine to keep any other data, at the least. </p>
<p>So I&#8217;ll find another drive on which to move the data I need (200 GB), reformat, and then think about using Time Machine again. While the visual part of Time Machine is a nice way to understand the timeframe backups, there&#8217;s no easy way to reclaim the free space or need to understand why, without some technical background.  </p>
<p>Thanks very much for posting the findings, information, and fixes, and good news for those who want to continue using Time Machine. I&#8217;m now going to use a Time Capsule and not put anything else on it.  If Apple had spent just a little more time testing these boundary conditions, instead of leaving it to the customer, we all may not have had to suffer the discovery and lost of time and data.  Pushing out a complex feature like this without fully flushing out such a major problem is just silly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: flokru</title>
		<link>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-6898</link>
		<dc:creator>flokru</dc:creator>
		<pubDate>Sun, 06 Apr 2008 18:24:20 +0000</pubDate>
		<guid>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-6898</guid>
		<description>@Adam: That’s indeed good news. Made my article somewhat obsolete though. ;-)</description>
		<content:encoded><![CDATA[<p>@Adam: That’s indeed good news. Made my article somewhat obsolete though. <img src='http://www.flokru.org/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Adam Cohen-Rose</title>
		<link>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-6896</link>
		<dc:creator>Adam Cohen-Rose</dc:creator>
		<pubDate>Sun, 06 Apr 2008 17:25:19 +0000</pubDate>
		<guid>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-6896</guid>
		<description>Hi there,

Thanks for the clear explanation of how the sparse images make Time Machine delete all the old backups.

I've been running Time Machine against an SMB share for a while now (since the beginning of January) and this was my last outstanding issue. However, I was pleasantly surprised to find out that &lt;a href="http://adamcohenrose.blogspot.com/2008/04/time-machine-update-fixes-sparse-bundle.html" rel="nofollow"&gt;the latest Time Machine and AirPort Updates v1.0 fixes the problem&lt;/a&gt;. Apple have changed Time Machine so it now compacts the sparse bundle after it deletes each old backup.

Cheers,

Adam</description>
		<content:encoded><![CDATA[<p>Hi there,</p>
<p>Thanks for the clear explanation of how the sparse images make Time Machine delete all the old backups.</p>
<p>I&#8217;ve been running Time Machine against an SMB share for a while now (since the beginning of January) and this was my last outstanding issue. However, I was pleasantly surprised to find out that <a href="http://adamcohenrose.blogspot.com/2008/04/time-machine-update-fixes-sparse-bundle.html" rel="nofollow">the latest Time Machine and AirPort Updates v1.0 fixes the problem</a>. Apple have changed Time Machine so it now compacts the sparse bundle after it deletes each old backup.</p>
<p>Cheers,</p>
<p>Adam</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Time-Machine-Backups auf Netzwerkfreigaben 2: Mögliche Probleme auf flokrus Blog</title>
		<link>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-6780</link>
		<dc:creator>Time-Machine-Backups auf Netzwerkfreigaben 2: Mögliche Probleme auf flokrus Blog</dc:creator>
		<pubDate>Thu, 27 Mar 2008 23:32:33 +0000</pubDate>
		<guid>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-6780</guid>
		<description>[...]           &#171; Drogendealermörderterroristenpiraten Time Machine backups on network shares 2: possible problems [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;]           &laquo; Drogendealermörderterroristenpiraten Time Machine backups on network shares 2: possible problems [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Mike</title>
		<link>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-6762</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 26 Mar 2008 18:10:10 +0000</pubDate>
		<guid>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-6762</guid>
		<description>Hallo Flo,

Du solltest vor dem Artikel noch einen Hinweis auf die deutsche Übersetzung einfügen. Habe mich soeben durch das Englisch gekämpft und hernach erst den deutschen Artikel entdeckt.

Danke für die Infos!</description>
		<content:encoded><![CDATA[<p>Hallo Flo,</p>
<p>Du solltest vor dem Artikel noch einen Hinweis auf die deutsche Übersetzung einfügen. Habe mich soeben durch das Englisch gekämpft und hernach erst den deutschen Artikel entdeckt.</p>
<p>Danke für die Infos!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: flokru</title>
		<link>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-6743</link>
		<dc:creator>flokru</dc:creator>
		<pubDate>Mon, 24 Mar 2008 22:55:03 +0000</pubDate>
		<guid>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-6743</guid>
		<description>@Dana: Your assumption is right.</description>
		<content:encoded><![CDATA[<p>@Dana: Your assumption is right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Dana Sutton</title>
		<link>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-6734</link>
		<dc:creator>Dana Sutton</dc:creator>
		<pubDate>Mon, 24 Mar 2008 11:06:03 +0000</pubDate>
		<guid>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-6734</guid>
		<description>In this very interesting article you say "The image capacity must not exceed the free space of the container." Now consider the situation of two or more Macs using Time Machine to back up to images on a shared server. In this case should the rule be "The total image capacity of all images should not exceed the free space of the container"?</description>
		<content:encoded><![CDATA[<p>In this very interesting article you say &#8220;The image capacity must not exceed the free space of the container.&#8221; Now consider the situation of two or more Macs using Time Machine to back up to images on a shared server. In this case should the rule be &#8220;The total image capacity of all images should not exceed the free space of the container&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Time Machine backups on network shares in Leopard auf flokrus Blog</title>
		<link>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-6664</link>
		<dc:creator>Time Machine backups on network shares in Leopard auf flokrus Blog</dc:creator>
		<pubDate>Sat, 15 Mar 2008 17:58:01 +0000</pubDate>
		<guid>http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possible-problems/#comment-6664</guid>
		<description>[...] Update 2: Things you should know about the maximum size of the image and the free space on the network share. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Update 2: Things you should know about the maximum size of the image and the free space on the network share. [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
