What mechanism is used for making scheduled backups happen in SuperDuper?

[mantronix]

Hi. What mechanism is used for making scheduled backups happen in SuperDuper?

I recently set SuperDuper to do a scheduled backup every Sunday at 1am. I then entered my admin account name and password. Because I like to know what's going on, I began searching for exactly what changed on my system to make scheduled runs of SuperDuper possible.

I looked in the admin account's crontab. Nope, no changes there.
I looked in root's crontab. Nope.
I looked in /Library/LaunchDaemons. Nope.
I looked in /Library/LaunchAgents. Nope.
I looked in /System/Library/LaunchDaemons. Nope.
I looked in /System/Library/LaunchAgents. Nope.
I looked in ~/Library/LaunchDaemons. Nope.
I looked in ~/Library/LaunchAgents. Nope.

So, having looked in all these places, where does SuperDuper store its launch info? Thanks.

(I am a paid user of SuperDuper.)

[dnanian]

It's in the crontab. Try

crontab -l

in Terminal.

[mantronix]

Thanks, Dave. I looked in every crontab except my own.

Now, how does SuperDuper handle the password part? Where is it storing my admin credentials so that it doesn't have to ask me for them at 1am on Sunday? I did not see anything related to SuperDuper when I looked in the Keychain app.

Thanks.

(I am a paid user of SuperDuper.)

[dnanian]

It authorizes an agent in our application bundle. We never see or store the password.

[mantronix]

Thanks again, Dave. Interesting. So the authorization step in SuperDuper changes a system setting to allow an agent in the app bundle to proceed with the backup.

What files in my system are changed as a result of the authorization?

Thanks.

(I am a paid user of SuperDuper.)

[dnanian]

As I said, it's inside our application bundle. No "system files" are changed at all.