![]() ![]() On the developers website, they mention that this program doesn't run in place of TimeMachine, rather, it just changes the interval that the system backs up. You can change it to once a day, week, or month and control the times it backs up at. TimeMachineEditor allows you to change the times that TimeMachine backs your system up. It does this until your Time Machine disk is completely full, then it erases the oldest backups and carries on. As many of you already know, Time Machine does a complete system backup at first, then hourly backups of system changes. Thanks to all for the suggestions, and I promise to provide a more timely update with the results of this new experiment.If you have been putting off using Time Machine to back up your Mac because of the lack of being able to time backups you have no excuse now. ![]() That will be my experiment for later this week. I think the solution will be to create a new APFS volume on the external drive, and designate that as the TM backup for the Mac mini. There is one rub, however: The Mac mini itself cannot back up to that attached drive, Any attempt to use it comes with a warning that it will wipe out the contents of the drive (thereby killing the ability to use it as a remote TM backup for the other computers). That step (manually mounting the volume) is something I think Apple should include in their instructions. The new/old (refurbished) Mac mini is working like a champ. To get the process started, I had to manually mount the share via SMB, and then got Time Machine going, After successfully inheriting the previous TM backup, it was no longer necessary to have the remote drive mounted in the Finder. I have been remiss in following up with this thread. Per either me thinking about it or maybe advice from Bombich…shifted the destination to the Remote Macintosh option with Safety Net enabled…and it just works. Set up rotating CCC clones which are finder readable…they mostly worked when I mounted the destination once, set up the job, and told the job to mount and I mount the destinations as needed. ![]() One of the reasons I eliminated TM over the network…with 2 different destination machines selected for alternating laptop backups…they random and inextricably fail despite all userids, numbers, shares, permissions, and passwords being the same…then the one that broke fixes itself with no action on my part and the other fails a few days later. If anyone has any idea what I am doing wrong here, I would be most grateful.Ĭarefully following Apple’s simple directions for configuring the mini as a TM destination, I find that it does not accept the access credentials for any of the user accounts that work perfectly when logging into the mini directly. But when the same credentials are used within System Settings / General / Time Machine, they are rejected. In other words, when I manually mount the external (TM destination) drive from the Finder (after putting in login credentials), it mounts correctly. My AirPort Extreme 802.11ac (which hosts the TM backups for my household on a 6TB external drive) has gone unreliable, and since my “just in case of emergency” 2014 Mac mini is not only obsolete but is also flakey, I picked up a refurbished 2018 Mac mini to replace both devices (for a little over $400, which, given the dual-purpose of this replacement, addresses the cost-effectiveness issue that Ivan cited).īut I am running into a problem: After carefully following Apple’s simple directions for configuring the mini as a TM destination, I find that it does not accept the access credentials for any of the user accounts that work perfectly when logging into the mini directly. I know this article is a year old, but it is very relevant to me right now. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |