Setting Start Time for Time Machine Backups
in [Mac Systems]
|
From: Nick Naym on 14 Apr 2010 00:34 In article DPaxn.1746$Z6.1357(a)edtnps82, Kir�ly at me(a)home.spamsucks.ca wrote on 4/13/10 11:41 PM: > TaliesinSoft <taliesinsoft(a)me.com> wrote: >> The reason for this is that there is a conflict between SuperDuper! and >> Time Machine if Time Machine is running when a scheduled SuperDuper! >> backup initiates, the result being a failure of the SuperDuper! backup. >> This happens if borth the Time Machine and SuperDuper! backups are to a >> Time Capsule. > > That sounds like a bug with SD!. Have you checked with Shirt Pocket > support? I don't think it's a SuperDuper!/Time Machine conflict/bug, per se (see, for example, http://www.shirt-pocket.com/forums/showthread.php?t=5006). I'd be inclined to suspect it's somehow related to Time Capsule. -- iMac (27", 3.06 GHz Intel Core 2 Duo, 4 GB RAM, 1 TB HDD) � OS X (10.6.3)
From: TaliesinSoft on 14 Apr 2010 08:17 On 2010-04-13 23:34:44 -0500, Nick Naym said: > In article DPaxn.1746$Z6.1357(a)edtnps82, Kir�ly at me(a)home.spamsucks.ca wrote > on 4/13/10 11:41 PM: > >> TaliesinSoft <taliesinsoft(a)me.com> wrote: >>> The reason for this is that there is a conflict between SuperDuper! and >>> Time Machine if Time Machine is running when a scheduled SuperDuper! >>> backup initiates, the result being a failure of the SuperDuper! backup. >>> This happens if borth the Time Machine and SuperDuper! backups are to a >>> Time Capsule. >> >> That sounds like a bug with SD!. Have you checked with Shirt Pocket >> support? > > I don't think it's a SuperDuper!/Time Machine conflict/bug, per se (see, for > example, http://www.shirt-pocket.com/forums/showthread.php?t=5006). I'd be > inclined to suspect it's somehow related to Time Capsule. I purchased my Time Capsule in early January of this year and in addition to the Time Machine hourly backups there have also been two nightly scheduled SuperDuper! backups to the Time Capsule. Thee are also Everything ran without any apparent problems until I upgraded to OS X 10.6.3 and then I started having frequent failures of one of the SuperDuper! scheduled backups, the one which backed up my computer. The other SuperDuper! backup which didn't fail was that of an external drive. With a bit of experimenting I established that the failures apparently occurred if Time Machine was running when the backup of the computer itself was initiated. I've installed TimeMachineEditor and have programmed it to have my hourly Time Machine backups occur on the hour, and have set my nightly SuperDuper! backups to initiate at 15 minutes past the hour so that there is essentially no chance that there would be an overlap between Time Machine and the backups, and this seems to be eliminating the problem, time will tell. I will be keeping Dave Nanian of Shirt Pocket, the implementors of SuperDuper!, updated as to whether my workaround eliminates the problem. I'd be interested if there are others who have experienced the same problem. -- James Leo Ryan --- Austin, Texas --- taliesinsoft(a)me.com
From: Nick Naym on 14 Apr 2010 10:12 In article 82lq36F3o4U1(a)mid.individual.net, TaliesinSoft at taliesinsoft(a)me.com wrote on 4/14/10 8:17 AM: > On 2010-04-13 23:34:44 -0500, Nick Naym said: > >> In article DPaxn.1746$Z6.1357(a)edtnps82, Kir�ly at me(a)home.spamsucks.ca wrote >> on 4/13/10 11:41 PM: >> >>> TaliesinSoft <taliesinsoft(a)me.com> wrote: >>>> The reason for this is that there is a conflict between SuperDuper! and >>>> Time Machine if Time Machine is running when a scheduled SuperDuper! >>>> backup initiates, the result being a failure of the SuperDuper! backup. >>>> This happens if borth the Time Machine and SuperDuper! backups are to a >>>> Time Capsule. >>> >>> That sounds like a bug with SD!. Have you checked with Shirt Pocket >>> support? >> >> I don't think it's a SuperDuper!/Time Machine conflict/bug, per se (see, for >> example, http://www.shirt-pocket.com/forums/showthread.php?t=5006). I'd be >> inclined to suspect it's somehow related to Time Capsule. > > I purchased my Time Capsule in early January of this year and in > addition to the Time Machine hourly backups there have also been two > nightly scheduled SuperDuper! backups to the Time Capsule. Thee are > also Everything ran without any apparent problems until I upgraded to > OS X 10.6.3 and then I started having frequent failures of one of the > SuperDuper! scheduled backups, the one which backed up my computer. The > other SuperDuper! backup which didn't fail was that of an external > drive. With a bit of experimenting I established that the failures > apparently occurred if Time Machine was running when the backup of the > computer itself was initiated. I've installed TimeMachineEditor and > have programmed it to have my hourly Time Machine backups occur on the > hour, and have set my nightly SuperDuper! backups to initiate at 15 > minutes past the hour so that there is essentially no chance that there > would be an overlap between Time Machine and the backups, and this > seems to be eliminating the problem, time will tell. I will be keeping > Dave Nanian of Shirt Pocket, the implementors of SuperDuper!, updated > as to whether my workaround eliminates the problem. I'd be interested > if there are others who have experienced the same problem. I assumed that it was somehow related to Time Capsule, as I don't have Time Capsule and have never experienced a conflict between SD! and TM. Though, admittedly, they rarely run at the same time, on those occasions when they happen to be running simultaneously -- say, when TM is going through a deep traversal and it's still backing up when SD! kicks in -- they never conflict. I'm currently on SL 10.6.3 (see sig), SD! 2.6.2, and TME 2.2. (BTW: Did you get the installer I sent you?) The only times SD! has failed on me has been when the target volume (external drive) was too full (i.e., nearing capacity) and a large file on the source volume (internal drive) was being modified while the backup was occurring. But that's to be expected. (FWIW, open MS Office apps -- even if they're not being actively used -- have a habit of making db changes in the middle of backups!) But, as I said above, I've not had any apparent SD! problems due to overlapping backups with TM. -- iMac (27", 3.06 GHz Intel Core 2 Duo, 4 GB RAM, 1 TB HDD) � OS X (10.6.3)
From: TaliesinSoft on 14 Apr 2010 11:11 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. -- James Leo Ryan --- Austin, Texas --- taliesinsoft(a)me.com
From: Nick Naym on 14 Apr 2010 12:33
In article 82m490F2f0U1(a)mid.individual.net, TaliesinSoft at taliesinsoft(a)me.com wrote on 4/14/10 11:11 AM: > 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, Of course it works...the thing I don't like about the Snow Leopard version is that unlike previous versions, it no longer sets a system parameter to tell TM when to back up, but instead installs a daemon that runs in the background and requires you to manually shut off TM. All the advantages of the Leopard version are now gone. Why be forced to rely on a (by definition, intrusive) background daemon, not be able to see TM active, and not have a reliable and visible indicator of when the last and next backup occurred? That's why I stayed with the last Leopard version (2.2). > 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? I find that hourly backups are unnecessarily too often. I've set TME to schedule Calendar Intervals every 2 hours during normal working hours, every 3 hours at night until midnight, and none after that. > This allows me to schedule the > SuperDuper! backups at a time when Time Machine is certain to not be > running. TME 2.2 will do/does that very nicely. -- iMac (27", 3.06 GHz Intel Core 2 Duo, 4 GB RAM, 1 TB HDD) � OS X (10.6.3) |