Comments on: TimeMachine Backups to NFS http://www.micromux.com/2010/04/28/timemachine-backups-to-nfs/ Commentary on the state of my microcosm. Sun, 29 Jan 2012 03:48:47 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Eric http://www.micromux.com/2010/04/28/timemachine-backups-to-nfs/comment-page-1/#comment-627 Eric Sun, 29 Jan 2012 03:48:47 +0000 http://www.micromux.com/?p=348#comment-627 You will definitely need more than 128GB for your backup, I would estimate 250GB as a starting point. However, it really depends what your plans are for the larger drive - if you do end up using much of that then you'll need significantly more space. I would just allocate 1TB to your sparse bundle and make sure it doesn't outgrow the physical storage space. You will definitely need more than 128GB for your backup, I would estimate 250GB as a starting point. However, it really depends what your plans are for the larger drive – if you do end up using much of that then you’ll need significantly more space.

I would just allocate 1TB to your sparse bundle and make sure it doesn’t outgrow the physical storage space.

]]> By: forrie http://www.micromux.com/2010/04/28/timemachine-backups-to-nfs/comment-page-1/#comment-626 forrie Fri, 27 Jan 2012 21:59:42 +0000 http://www.micromux.com/?p=348#comment-626 How do we determine the fair initial size of the sparsebundle? For example, my current HD config consumes: /dev/disk0s2 232Gi 154Gi 78Gi 67% / /dev/disk1s2 931Gi 39Gi 892Gi 5% /Volumes/Macintosh HD 2 I don't think 128gb would be sufficient...? Thank you :-) How do we determine the fair initial size of the sparsebundle? For example, my current HD config consumes:

/dev/disk0s2 232Gi 154Gi 78Gi 67% /
/dev/disk1s2 931Gi 39Gi 892Gi 5% /Volumes/Macintosh HD 2

I don’t think 128gb would be sufficient…?

Thank you :-)

]]> By: Eric http://www.micromux.com/2010/04/28/timemachine-backups-to-nfs/comment-page-1/#comment-612 Eric Thu, 07 Oct 2010 12:59:17 +0000 http://www.micromux.com/?p=348#comment-612 It's a fixed size, but it won't actually consume all of that space when created. So, in this case, 128GB is the largest size of the sparsebundle but if your initial backup is 40GB then that's all the space you will consume. These can be resized as well using the hdiutil package, so if you start with 128GB and need more later it's possible. It’s a fixed size, but it won’t actually consume all of that space when created. So, in this case, 128GB is the largest size of the sparsebundle but if your initial backup is 40GB then that’s all the space you will consume.

These can be resized as well using the hdiutil package, so if you start with 128GB and need more later it’s possible.

]]> By: forrie http://www.micromux.com/2010/04/28/timemachine-backups-to-nfs/comment-page-1/#comment-611 forrie Wed, 06 Oct 2010 20:27:32 +0000 http://www.micromux.com/?p=348#comment-611 Regarding the arg to hdiutil "-size 128g", is this a fixed size or is it dynamic (ie: to determine the correct amount of space to use for Time Machine's backup). Regarding the arg to hdiutil “-size 128g”, is this a fixed size or is it dynamic (ie: to determine the correct amount of space to use for Time Machine’s backup).

]]>