Setting Start Time for Time Machine Backups [Mac Systems]

Prev: damaged iPod classic
Next: Is the MacBook Pro due for an update? (17-inch)

From: Nick Naym on 14 Apr 2010 21:57

From: TaliesinSoft on 14 Apr 2010 22:12

On 2010-04-14 20:57:30 -0500, Nick Naym said:

[commenting on the two SuperDuper! logs previously posted in this
thread, one where SuperDuper! fails and one where SuperDuper! succeeds,
both backups being made to a sparse bundle on a Time Capsule, the
difference being that Time Machine was running at the time the failed
backup initiated and was not running at the time the successful backup
initiated]

> This stuff is all "Geek to me." ;) But, just looking at where the two logs
> appear to diverge, it sort of seems like the Mac has "lost its way" back to
> your Time Capsule...or at least to /Volumes/Data/SuperDuper
> Backup.sparsebundle on your Time Capsule. If so, it comes back to the
> original question: Why? If it only happens when backing up to Time Capsule,
> and if then only when SD! and TM are running simultaneously, it seems to
> suggest that the link to Time Capsule is somehow broken/breaking when the
> two backups are running together.
>
> But that doesn't really tell us much more than we knew before. Since the
> "bug" that causes Time Capsule's link to break only appears when the two
> apps come together, whose bug is it? Shirt-Pocket's or Apple's?

As I've mentioned, this problem only started after the release of OS X
10.6.3. The details have been reported to both Shirt-Pocket and Apple,
and hopefully between the two of them the issue can be addressed. And,
as I've also mentioned, I have a 'workaround" that appears to prevent
the backup failure from occurring by insuring that Time Machine is not
running at the time SuperDuper! initiates a backup.

--
James Leo Ryan --- Austin, Texas --- taliesinsoft(a)me.com

From: Paul Sture on 15 Apr 2010 06:34

In article <82k818Fsa5U1(a)mid.individual.net>,
TaliesinSoft <taliesinsoft(a)me.com> wrote:

> What I would like is to be able to set the exact time at which the
> hourly Time Machine backups take place. For example, 1:00, 2:00,
> 3:00.....
>
> 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.
>
> So what I want to do is to make sure that Time Machine is not running
> at the time a SuperDuper! backup initiates.
>
> Many thanks in advance for suggestions and such!

I'm on Leopard here, if that makes any difference.

What I do is set my system to start at 05:59* every morning.

Time Machine won't actually do anything until I log in for the first
time after a restart, so my first backup of the day is a bit later.

However, until I restart the system, Time Machine kicks in every hour at
59 minutes (plus 30 seconds or so) past the hour.

If I reboot during the day (I've just done that after applying Security
Update 2010-003), then Time Machine will kick in an hour after the
reboot time.

*Why 05:59 and not on the hour you might ask? There's a clock tower
nearby and setting Time Machine off at 59 minutes past the hour through
the day means that the hourly rattling of the disks coincides with the
chiming of the bells :-)

Back-in-Time is a useful utility for seeing when your Time Machine
backups have been performed and how much was backed up in each run:

<http://www.tri-edre.com/download/download/backintime.html>

Tri-Edre also do TechTool Pro and other system level products.

--
Paul Sture

From: Paul Sture on 15 Apr 2010 09:19

In article <1Qqxn.1796$Z6.1685(a)edtnps82>, me(a)home.spamsucks.ca (Kir�ly)
wrote:

> 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.

I've only seen it happen once*, but if Time Machine goes into a deep
traversal it can take hours to complete.

* The one time it did happen, the system log complained about some
change in the disk UID (?), and saying it didn't trust things. I think
this was after a power cut.

--
Paul Sture

From: Paul Sture on 15 Apr 2010 09:21

In article <82mb2mFd4rU1(a)mid.individual.net>,
TaliesinSoft <taliesinsoft(a)me.com> wrote:

> My gutsy is that the default is based upon when the Mac is
> started.

I have hard evidence to say that is true (on Leopard, and I'm not
using TimeMachineEditor or any similar utilities which do the same thing).

--
Paul Sture

First | Prev | Next | Last
Pages: 1 2 3 4 5 6
Prev: damaged iPod classic
Next: Is the MacBook Pro due for an update? (17-inch)