Prev: damaged iPod classic
Next: Is the MacBook Pro due for an update? (17-inch)
From: TaliesinSoft on 13 Apr 2010 18:03
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!

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

From: TaliesinSoft on 13 Apr 2010 18:53
On 2010-04-13 17:03:20 -0500, TaliesinSoft said:

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

After making my post I discovered what looks like it will do the job in
TimeMachineEditor. We shall see!


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

From: Nick Naym on 13 Apr 2010 19:24
In article 82kav3FccoU1(a)mid.individual.net, TaliesinSoft at
taliesinsoft(a)me.com wrote on 4/13/10 6:53 PM:

> On 2010-04-13 17:03:20 -0500, TaliesinSoft said:
>
>> 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.....
>
> After making my post I discovered what looks like it will do the job in
> TimeMachineEditor. We shall see!
>


Been using it for quite some time. In fact, I'm still using v.2.2 -- I
didn't upgrade to v. 2.5, as I didn't like the idea of having a daemon
intrude into my system (which, as I understand, is how 2.5.x operates -- a
change that was made when SL was released).

--
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 13 Apr 2010 23:41
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?

--
K.

Lang may your lum reek.
From: TaliesinSoft on 14 Apr 2010 00:06
On 2010-04-13 22:41:23 -0500, Kir�ly said:

> 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've had several discussions with Dave Nanian of Shirt Pocket regarding
this, and am trying to narrow down the exact circumstances of the
failure.

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

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