Okay, this is weird problem, so bear with me.
Back when I first updated to Leopard and decided to give Time Machine a try, I didn't like that TM did it's backups every hour. For me, it was overkill so I went about trying to find a solution. When TM first came out there wasn't a lot of options to control it, but I did find a couple of solutions. One was to create a script in automater then control it with an iCal event. The one I wound up using was to create a crontab (I think I used Lingon) to change the backup times for Time Machine. I set it up to backup at noon, 6PM and midnight, then let it go. Over the year or so it has been doing it's job faithfully with only a couple of errors (but those are unrelated to this post).
Last week, I bought a new hard drive to update my computer to Snow Leopard and do a fresh install of all of my programs. I zeroed out the drive and did a total fresh install of Snow Leopard. The only thing I brought over from my old drive was my files, a copy of keychain, and an exported iCal. Pretty much everything is fresh and it took me a couple of days to tweak it. Here's where the problem comes in. I'm getting time machine errors saying the backup drive can't be found. I haven't even setup Time Machine yet!! Seems that something on the root system is firing off that old cron job that I setup way back when. I checked to see if I could find where it was coming from but no luck. I even reinstalled Lingon thinking the job would show up there and I could delete or change it, but nothing shows up in the panel. Of course, Lingon has been discontinued and might not be compatible with SL, so that might be part of the problem. Anyway, I also checked Launchd plist and it shows the default of 3600 for Time Machine. The TM error shows up on my old backup times so I know it's from my old script. The error happens at noon, 6 and midnight.
I don't understand how the script is controlling Time Machine when I did a reformat of the drive. How did an old sub-routine make it over to a newly reformated drive? That tells me that the job must be embedded somewhere or it managed to get on to the reformatted drive when I copied my files over.
How can find this script or cron job or whatever is causing Time Machine backup to run? I could try reformatting again but I don't want to spend the time doing that, and I'm not sure it will fix it. Surely there is a command or something I can do in terminal or other piece of software that will track this down? Resetting Time Machine (it's currently turned off) is not going to make a difference. Nor is looking at the backupd.plist file because that is also at the default. I need to find the agent that is telling TM to run at those special times so that I can turn it off. My hope it to create a new launchd control with Time Machine editor and have a different backup solution.
Thanks for reading!
Back when I first updated to Leopard and decided to give Time Machine a try, I didn't like that TM did it's backups every hour. For me, it was overkill so I went about trying to find a solution. When TM first came out there wasn't a lot of options to control it, but I did find a couple of solutions. One was to create a script in automater then control it with an iCal event. The one I wound up using was to create a crontab (I think I used Lingon) to change the backup times for Time Machine. I set it up to backup at noon, 6PM and midnight, then let it go. Over the year or so it has been doing it's job faithfully with only a couple of errors (but those are unrelated to this post).
Last week, I bought a new hard drive to update my computer to Snow Leopard and do a fresh install of all of my programs. I zeroed out the drive and did a total fresh install of Snow Leopard. The only thing I brought over from my old drive was my files, a copy of keychain, and an exported iCal. Pretty much everything is fresh and it took me a couple of days to tweak it. Here's where the problem comes in. I'm getting time machine errors saying the backup drive can't be found. I haven't even setup Time Machine yet!! Seems that something on the root system is firing off that old cron job that I setup way back when. I checked to see if I could find where it was coming from but no luck. I even reinstalled Lingon thinking the job would show up there and I could delete or change it, but nothing shows up in the panel. Of course, Lingon has been discontinued and might not be compatible with SL, so that might be part of the problem. Anyway, I also checked Launchd plist and it shows the default of 3600 for Time Machine. The TM error shows up on my old backup times so I know it's from my old script. The error happens at noon, 6 and midnight.
I don't understand how the script is controlling Time Machine when I did a reformat of the drive. How did an old sub-routine make it over to a newly reformated drive? That tells me that the job must be embedded somewhere or it managed to get on to the reformatted drive when I copied my files over.
How can find this script or cron job or whatever is causing Time Machine backup to run? I could try reformatting again but I don't want to spend the time doing that, and I'm not sure it will fix it. Surely there is a command or something I can do in terminal or other piece of software that will track this down? Resetting Time Machine (it's currently turned off) is not going to make a difference. Nor is looking at the backupd.plist file because that is also at the default. I need to find the agent that is telling TM to run at those special times so that I can turn it off. My hope it to create a new launchd control with Time Machine editor and have a different backup solution.
Thanks for reading!
