Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
Apple Computing Products:
macOS - Apps and Programs
Getting inside Time Machine's head
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="tewatson" data-source="post: 1046848" data-attributes="member: 68855"><p>My remedial understanding of TM is that it backs up everything but the core OS files (i.e., you have to reinstall OSX and then run TM, but it will also restore your OS preferences/settings). It seems that TM can take quite a bit of time for the initial backup (which makes sense), then subsequent sessions run very quickly, as it's only backing up changed files...in other words, an incremental backup of sorts. I say "of sorts" because one can choose any day in TM's inventory and it will restore your system to the exact overall state of that day. To do so, it must be effectively assembling a "full" backup every time, hence my questions:</p><p></p><p>In my limited knowledge, I would guess that TM takes the last backup set and "brings it forward", overlaying changed files on top. This is why the incremental backups run quickly - most of the data is already there - and also seems the practical way to allow the option of a complete restore to any point in the dataset, without running a full backup routine every time. Correct?</p><p></p><p>I want to start backing up two Macs to a single external drive using TM, and swap the drive out with another regularly to always have one off-site (rotating the two monthly or so). The drive is currently full, and I assume (perhaps incorrectly) that TM for Machine B will not delete old backups for Machine A if the disk is already full. So, can I choose a range of dates for Machine A on my backup disk and delete them, without destroying TM's ability to restore subsequent dates? I suspect so, since it automatically deletes old backups when space is required. That intuitively tells me that TM is effectively creating a "full" backup with every run, as an algorithm to selectively delete only the data it would not need to assemble a full backup set on demand would be exceedingly complex.</p><p></p><p>Will TM automatically create separate ID'd datasets on the drive, using a single partition? I also assume each machine's TM runs will manage their respective datasets for disk space requirements?</p><p></p><p>Thanks in advance for any insights.</p><p></p><p>Tom</p></blockquote><p></p>
[QUOTE="tewatson, post: 1046848, member: 68855"] My remedial understanding of TM is that it backs up everything but the core OS files (i.e., you have to reinstall OSX and then run TM, but it will also restore your OS preferences/settings). It seems that TM can take quite a bit of time for the initial backup (which makes sense), then subsequent sessions run very quickly, as it's only backing up changed files...in other words, an incremental backup of sorts. I say "of sorts" because one can choose any day in TM's inventory and it will restore your system to the exact overall state of that day. To do so, it must be effectively assembling a "full" backup every time, hence my questions: In my limited knowledge, I would guess that TM takes the last backup set and "brings it forward", overlaying changed files on top. This is why the incremental backups run quickly - most of the data is already there - and also seems the practical way to allow the option of a complete restore to any point in the dataset, without running a full backup routine every time. Correct? I want to start backing up two Macs to a single external drive using TM, and swap the drive out with another regularly to always have one off-site (rotating the two monthly or so). The drive is currently full, and I assume (perhaps incorrectly) that TM for Machine B will not delete old backups for Machine A if the disk is already full. So, can I choose a range of dates for Machine A on my backup disk and delete them, without destroying TM's ability to restore subsequent dates? I suspect so, since it automatically deletes old backups when space is required. That intuitively tells me that TM is effectively creating a "full" backup with every run, as an algorithm to selectively delete only the data it would not need to assemble a full backup set on demand would be exceedingly complex. Will TM automatically create separate ID'd datasets on the drive, using a single partition? I also assume each machine's TM runs will manage their respective datasets for disk space requirements? Thanks in advance for any insights. Tom [/QUOTE]
Verification
Post reply
Forums
Apple Computing Products:
macOS - Apps and Programs
Getting inside Time Machine's head
Top