#1
|
|||
|
|||
Disable Time Machine before cloning
I've had it happen that booting from a clone with the Time Machine drive still attached would start a backup, after which the system on the internal drive refused to do incremental backups. Since this wastes time & space it'd be great if SD could disable TM before cloning, or just disable it on the clone. I suppose a script can do this?
|
#2
|
||||
|
||||
Since Time Machine is a black box, doing this would require using undocumented (and thus subject to change) interfaces, something I'm loathe to do.
On top of that, disabling Time Machine on destinations would both make any restored backup also not back up with Time Machine, which would be quite bad. I'd suggest simply disconnecting the Time Machine volume, should this prove an issue for you...
__________________
--Dave Nanian |
#3
|
|||
|
|||
Quote:
I assume before/after copy scripts run as root? It's not in the manual. Quote:
|
#4
|
||||
|
||||
tmutil disable turns backups off for now, as opposed to on a specific drive.
__________________
--Dave Nanian |
#5
|
|||
|
|||
That's fine, an after copy script can enable them again. The re-scan will take a while, but no space will be wasted.
|
#6
|
||||
|
||||
Feel free to do this with some shell scripts if you want... it's not something I'd want to put in the app.
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Time Machine Issue with Restored Clone | sdsl | General | 3 | 10-14-2012 08:18 PM |
Time Machine Copy | jerrykrinock | General | 1 | 04-02-2010 01:36 PM |
Needed: Time Machine and SuperDuper guidance | kapalama | General | 7 | 08-13-2009 07:55 AM |
"Unable to create hard link" error when cloning Time Machine drive | Moussaka | General | 5 | 07-15-2009 03:53 PM |
Cloning from a backup and Time Machine Weirdness | isaac | General | 3 | 03-27-2008 01:09 PM |