Setting Start Time for Time Machine Backups
in [Mac Systems]
|
From: TaliesinSoft on 14 Apr 2010 13:07 On 2010-04-14 11:33:15 -0500, Nick Naym said: [commenting on how I set TimeMachineEditor to backup "on the hour"] > >> forcing the Time Machine backups to always run on the >> hour, e.g. 1:00, 2:00, 3:00.... > > Huh? That's pretty much TM's default. What have you changed? My experience has been that although Time Machine's default is to backup hourly the times of the backups are not synchronized to the hour. That is, and I just opened Time Machine to check, and found a series of backups that ran at roughly 45 minutes after the hour. My gutsy is that the default is based upon when the Mac is started. And after having set the schedule with TimeMachineEditor the backups are now initiated according to the schedule I set, that is, 1:00, 2:00, 3:00.... -- James Leo Ryan --- Austin, Texas --- taliesinsoft(a)me.com
From: Jochem Huhmann on 14 Apr 2010 16:21 TaliesinSoft <taliesinsoft(a)me.com> writes: > On 2010-04-14 09:12:01 -0500, Nick Naym said: > > [in reference to TimeMachineEditor] > >> (BTW: Did you get the installer I sent you?) > > I did get the installer you sent (many thanks) but by the time I > received it I had already installed TimeMachineEditor and it seems to be > working fine, forcing the Time Machine backups to always run on the > hour, e.g. 1:00, 2:00, 3:00.... This allows me to schedule the > SuperDuper! backups at a time when Time Machine is certain to not be > running. This seems still to be a workaround. The proper way to do this would be to run either of both from a script that waits until the backup is done and then starts the other. Jochem -- "A designer knows he has arrived at perfection not when there is no longer anything to add, but when there is no longer anything to take away." - Antoine de Saint-Exupery
From: Jochem Huhmann on 14 Apr 2010 16:44 Michelle Steiner <michelle(a)michelle.org> writes: >> This seems still to be a workaround. The proper way to do this would be >> to run either of both from a script that waits until the backup is done >> and then starts the other. > > Why would that be the proper way? So long as TM can schedule itself, why > not just use a utility to tell it what time to start, and compute the > schedule from that point onward? Because this way you will have to guess when TM will be done with its backup and if it isn't you get a problem. As most workarounds it will work most of the time and may still bite you later on. Jochem -- "A designer knows he has arrived at perfection not when there is no longer anything to add, but when there is no longer anything to take away." - Antoine de Saint-Exupery
From: Nick Naym on 14 Apr 2010 17:02 In article michelle-7AE2F6.13485214042010(a)news.eternal-september.org, Michelle Steiner at michelle(a)michelle.org wrote on 4/14/10 4:48 PM: > In article <m239yxkblh.fsf(a)revier.com>, Jochem Huhmann <joh(a)gmx.net> > wrote: > >>>> This seems still to be a workaround. The proper way to do this would >>>> be to run either of both from a script that waits until the backup is >>>> done and then starts the other. >>> >>> Why would that be the proper way? So long as TM can schedule itself, >>> why not just use a utility to tell it what time to start, and compute >>> the schedule from that point onward? >> >> Because this way you will have to guess when TM will be done with its >> backup and if it isn't you get a problem. As most workarounds it will >> work most of the time and may still bite you later on. > > After the initial backups, neither will take more than a half hour, Maybe, maybe not. > so > schedule the other one at the half-hour mark. -- iMac (27", 3.06 GHz Intel Core 2 Duo, 4 GB RAM, 1 TB HDD) � OS X (10.6.3)
From: =?ISO-8859-1?Q?Kir=E1ly?= on 14 Apr 2010 17:54
Michelle Steiner <michelle(a)michelle.org> wrote: > After the initial backups, neither will take more than a half hour, so > schedule the other one at the half-hour mark. I have had both SuperDuper! and Time Machine backups take longer than 30 minutes. Not often, but it happens. Running 10.5.8 on a G4 with 120GB of used space on my boot drive. -- K. Lang may your lum reek. |