Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #96426 > unrolled thread

Why is Time Machine doing a full backup?

Started byPatty Winter <patty1@wintertime.com>
First post2016-11-03 19:39 +0000
Last post2016-11-08 18:22 +0000
Articles 5 on this page of 25 — 8 participants

Back to article view | Back to comp.sys.mac.system

Contents

  Why is Time Machine doing a full backup? Patty Winter <patty1@wintertime.com> - 2016-11-03 19:39 +0000
    Re: Why is Time Machine doing a full backup? Jolly Roger <jollyroger@pobox.com> - 2016-11-03 19:56 +0000
      Re: Why is Time Machine doing a full backup? Patty Winter <patty1@wintertime.com> - 2016-11-03 20:33 +0000
        Re: Why is Time Machine doing a full backup? Jolly Roger <jollyroger@pobox.com> - 2016-11-03 20:39 +0000
        Re: Why is Time Machine doing a full backup? Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-11-03 17:12 -0400
        Re: Why is Time Machine doing a full backup? me@home.spamsucks.ca (Király) - 2016-11-05 15:27 +0000
    Re: Why is Time Machine doing a full backup? Fred McKenzie <fmmck@aol.com> - 2016-11-04 12:47 -0400
      Re: Why is Time Machine doing a full backup? Jolly Roger <jollyroger@pobox.com> - 2016-11-04 19:26 +0000
        Re: Why is Time Machine doing a full backup? Fred McKenzie <fmmck@aol.com> - 2016-11-04 16:52 -0400
          Re: Why is Time Machine doing a full backup? Jolly Roger <jollyroger@pobox.com> - 2016-11-04 21:48 +0000
            Re: Why is Time Machine doing a full backup? Fred McKenzie <fmmck@aol.com> - 2016-11-05 13:08 -0400
              Re: Why is Time Machine doing a full backup? Jolly Roger <jollyroger@pobox.com> - 2016-11-05 20:08 +0000
                Re: Why is Time Machine doing a full backup? Fred McKenzie <fmmck@aol.com> - 2016-11-06 12:33 -0500
                  Re: Why is Time Machine doing a full backup? Jolly Roger <jollyroger@pobox.com> - 2016-11-07 03:54 +0000
          Re: Why is Time Machine doing a full backup? nj_kruse@me.com (Niels Jørgen Kruse) - 2016-11-05 08:16 +0100
            Re: Why is Time Machine doing a full backup? Jolly Roger <jollyroger@pobox.com> - 2016-11-05 19:05 +0000
              Re: Why is Time Machine doing a full backup? nj_kruse@me.com (Niels Jørgen Kruse) - 2016-11-05 21:59 +0100
                Re: Why is Time Machine doing a full backup? Jolly Roger <jollyroger@pobox.com> - 2016-11-05 22:11 +0000
                  Re: Why is Time Machine doing a full backup? nj_kruse@me.com (Niels Jørgen Kruse) - 2016-11-06 13:00 +0100
                    Re: Why is Time Machine doing a full backup? Jolly Roger <jollyroger@pobox.com> - 2016-11-06 16:08 +0000
              Re: Why is Time Machine doing a full backup? nj_kruse@me.com (Niels Jørgen Kruse) - 2016-11-08 07:04 +0100
                Re: Why is Time Machine doing a full backup? Johnson <null@example.com> - 2016-11-08 08:16 +0000
                  Re: Why is Time Machine doing a full backup? nj_kruse@me.com (Niels Jørgen Kruse) - 2016-11-08 11:44 +0100
                    Re: Why is Time Machine doing a full backup? nospam <nospam@nospam.invalid> - 2016-11-08 10:07 -0500
                  Re: Why is Time Machine doing a full backup? Jolly Roger <jollyroger@pobox.com> - 2016-11-08 18:22 +0000

Page 2 of 2 — ← Prev page 1 [2]

#96648

Fromnj_kruse@me.com (Niels Jørgen Kruse)
Date2016-11-08 07:04 +0100
Message-ID<1mwdubn.38hku81s1wygrN%nj_kruse@me.com>
In reply to#96516
Jolly Roger <jollyroger@pobox.com> wrote:

> Niels Jørgen Kruse <nj_kruse@me.com> wrote:
> > Fred McKenzie <fmmck@aol.com> wrote:
> > 
> >> I am worried that there may be a bad spot on the Time Capsule's drive.
> >> After all, it has been running continuously for several years.  Maybe
> >> getting a new Time Capsule would be worthwhile.
> > 
> > I am also having problems with time machine backups being started over.
> > This happens every 3 days or so on a 10.12.1 iMac. An older 10.11.6 iMac
> > has no problems backing up to the same Time Capsule. I have wiped the
> > drive of the Time Capsule without effect. The problems started after the
> > upgrade from 10.12.0 to 10.12.1.
> 
> When it happens you should see a message. It would be helpful to know what
> that message says (verbatim).
> 
> Also, if you make note of the time the message appears, there should be
> messages with time stamps on or near that time in the /var/log/system.log
> file giving more detail about the cause of the issue.
> 
> Post both here for diagnosis.

Well it happened again.

The alert is at http://tinypic.com/r/mcgcy1/9

The last backup to the Time Capsule was at 02.55, so the alert would
have come within the next 2 hours. The system log has only this:

-----------------
Nov  8 01:51:31 Tiroth com.apple.xpc.launchd[1]
(com.apple.quicklook[4443]): Endpoint has been activated through legacy
launch(3) APIs. Please switch to XPC or bootstrap_check_in():
com.apple.quicklook
Nov  8 02:52:18 Tiroth syslogd[50]: ASL Sender Statistics
Nov  8 02:54:10 Tiroth logd[67]:
_handle_cache_delete_with_urgency(0x7fa372d273d0, 3, 0)
Nov  8 02:54:10 Tiroth com.apple.xpc.launchd[1]
(com.apple.imfoundation.IMRemoteURLConnectionAgent): Unknown key for
integer: _DirtyJetsamMemoryLimit
Nov  8 02:54:10 Tiroth logd[67]:
_handle_cache_delete_with_urgency(0x7fa372d418b0, 3, 0)
Nov  8 02:55:16 Tiroth com.apple.xpc.launchd[1]
(com.apple.quicklook[4503]): Endpoint has been activated through legacy
launch(3) APIs. Please switch to XPC or bootstrap_check_in():
com.apple.quicklook
Nov  8 02:55:19 Tiroth com.apple.xpc.launchd[1]
(com.apple.quicklook[4506]): Endpoint has been activated through legacy
launch(3) APIs. Please switch to XPC or bootstrap_check_in():
com.apple.quicklook
Nov  8 02:55:20 Tiroth com.apple.xpc.launchd[1] (com.apple.quicklook):
Service only ran for 0 seconds. Pushing respawn out by 1 seconds.
Nov  8 02:55:21 Tiroth com.apple.xpc.launchd[1]
(com.apple.quicklook[4510]): Endpoint has been activated through legacy
launch(3) APIs. Please switch to XPC or bootstrap_check_in():
com.apple.quicklook
Nov  8 03:55:19 Tiroth syslogd[50]: ASL Sender Statistics
Nov  8 03:55:19 Tiroth com.apple.xpc.launchd[1]
(com.apple.bsd.dirhelper[4511]): Endpoint has been activated through
legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in():
com.apple.bsd.dirhelper
Nov  8 04:56:13 Tiroth syslogd[50]: ASL Sender Statistics
Nov  8 04:59:16 Tiroth com.apple.xpc.launchd[1]
(com.apple.quicklook[4597]): Endpoint has been activated through legacy
launch(3) APIs. Please switch to XPC or bootstrap_check_in():
com.apple.quicklook
Nov  8 05:03:27 Tiroth com.apple.xpc.launchd[1]
(com.apple.quicklook[4598]): Endpoint has been activated through legacy
launch(3) APIs. Please switch to XPC or bootstrap_check_in():
com.apple.quicklook
Nov  8 05:07:00 Tiroth syslogd[50]: ASL Sender Statistics
Nov  8 05:07:37 Tiroth com.apple.xpc.launchd[1]
(com.apple.quicklook[4599]): Endpoint has been activated through legacy
launch(3) APIs. Please switch to XPC or bootstrap_check_in():
com.apple.quicklook
Nov  8 05:11:48 Tiroth com.apple.xpc.launchd[1]
(com.apple.quicklook[4600]): Endpoint has been activated through legacy
launch(3) APIs. Please switch to XPC or bootstrap_check_in():
com.apple.quicklook
Nov  8 05:17:00 Tiroth syslogd[50]: ASL Sender Statistics
Nov  8 05:19:59 Tiroth com.apple.xpc.launchd[1]
(com.apple.quicklook[4601]): Endpoint has been activated through legacy
launch(3) APIs. Please switch to XPC or bootstrap_check_in():
com.apple.quicklook
Nov  8 05:24:10 Tiroth com.apple.xpc.launchd[1]
(com.apple.quicklook[4603]): Endpoint has been activated through legacy
launch(3) APIs. Please switch to XPC or bootstrap_check_in():
com.apple.quicklook
Nov  8 05:27:00 Tiroth syslogd[50]: ASL Sender Statistics
Nov  8 05:28:21 Tiroth com.apple.xpc.launchd[1]
(com.apple.quicklook[4604]): Endpoint has been activated through legacy
launch(3) APIs. Please switch to XPC or bootstrap_check_in():
com.apple.quicklook
Nov  8 05:32:32 Tiroth com.apple.xpc.launchd[1]
(com.apple.quicklook[4606]): Endpoint has been activated through legacy
launch(3) APIs. Please switch to XPC or bootstrap_check_in():
com.apple.quicklook
Nov  8 05:36:43 Tiroth com.apple.xpc.launchd[1]
(com.apple.quicklook[4608]): Endpoint has been activated through legacy
launch(3) APIs. Please switch to XPC or bootstrap_check_in():
com.apple.quicklook
Nov  8 05:37:00 Tiroth syslogd[50]: ASL Sender Statistics
Nov  8 05:40:54 Tiroth com.apple.xpc.launchd[1]
(com.apple.quicklook[4609]): Endpoint has been activated through legacy
launch(3) APIs. Please switch to XPC or bootstrap_check_in():
com.apple.quicklook

-- 
Mvh./Regards,    Niels Jørgen Kruse,    Vanløse, Denmark

[toc] | [prev] | [next] | [standalone]

#96649

FromJohnson <null@example.com>
Date2016-11-08 08:16 +0000
Message-ID<582189cb$0$3964$c3e8da3$de690749@news.astraweb.com>
In reply to#96648
On 2016-11-08, Niels Jørgen Kruse <nj_kruse@me.com> wrote:
> Jolly Roger <jollyroger@pobox.com> wrote:
>
>> Niels Jørgen Kruse <nj_kruse@me.com> wrote:
>> > Fred McKenzie <fmmck@aol.com> wrote:
>> > 
>> >> I am worried that there may be a bad spot on the Time Capsule's drive.
>> >> After all, it has been running continuously for several years.  Maybe
>> >> getting a new Time Capsule would be worthwhile.
>> > 
>> > I am also having problems with time machine backups being started over.
>> > This happens every 3 days or so on a 10.12.1 iMac. An older 10.11.6 iMac
>> > has no problems backing up to the same Time Capsule. I have wiped the
>> > drive of the Time Capsule without effect. The problems started after the
>> > upgrade from 10.12.0 to 10.12.1.
>> 
>> When it happens you should see a message. It would be helpful to know what
>> that message says (verbatim).
>> 
>> Also, if you make note of the time the message appears, there should be
>> messages with time stamps on or near that time in the /var/log/system.log
>> file giving more detail about the cause of the issue.
>> 
>> Post both here for diagnosis.
>
> Well it happened again.
>
> The alert is at http://tinypic.com/r/mcgcy1/9
>
> The last backup to the Time Capsule was at 02.55, so the alert would
> have come within the next 2 hours. The system log has only this:

[...]

logging has changed with Sierra.

to see TM logs for the last four hours try
$ log show --predicate 'subsystem == "com.apple.TimeMachine"' --info --last 4h

[toc] | [prev] | [next] | [standalone]

#96651

Fromnj_kruse@me.com (Niels Jørgen Kruse)
Date2016-11-08 11:44 +0100
Message-ID<1mwe8lg.1fgh3eebwe53nN%nj_kruse@me.com>
In reply to#96649
Johnson <null@example.com> wrote:

> On 2016-11-08, Niels Jørgen Kruse <nj_kruse@me.com> wrote:
> > Jolly Roger <jollyroger@pobox.com> wrote:
> >
> >> Niels Jørgen Kruse <nj_kruse@me.com> wrote:
> >> > Fred McKenzie <fmmck@aol.com> wrote:
> >> > 
> >> >> I am worried that there may be a bad spot on the Time Capsule's drive.
> >> >> After all, it has been running continuously for several years.  Maybe
> >> >> getting a new Time Capsule would be worthwhile.
> >> > 
> >> > I am also having problems with time machine backups being started over.
> >> > This happens every 3 days or so on a 10.12.1 iMac. An older 10.11.6 iMac
> >> > has no problems backing up to the same Time Capsule. I have wiped the
> >> > drive of the Time Capsule without effect. The problems started after the
> >> > upgrade from 10.12.0 to 10.12.1.
> >> 
> >> When it happens you should see a message. It would be helpful to know what
> >> that message says (verbatim).
> >> 
> >> Also, if you make note of the time the message appears, there should be
> >> messages with time stamps on or near that time in the /var/log/system.log
> >> file giving more detail about the cause of the issue.
> >> 
> >> Post both here for diagnosis.
> >
> > Well it happened again.
> >
> > The alert is at http://tinypic.com/r/mcgcy1/9
> >
> > The last backup to the Time Capsule was at 02.55, so the alert would
> > have come within the next 2 hours. The system log has only this:
> 
> [...]
> 
> logging has changed with Sierra.
> 
> to see TM logs for the last four hours try
> $ log show --predicate 'subsystem == "com.apple.TimeMachine"' --info --last 4h

2016-11-08 04:57:57.999414+0100 0x139e39   Info        0x0
4312   backupd: (TimeMachine) [com.apple.TimeMachine.TMLogInfo] Checking
for runtime corruption on /dev/disk7s2
2016-11-08 04:57:58.665878+0100 0x139e39   Error       0x0
4312   backupd: (TimeMachine) [com.apple.TimeMachine.TMLogError] Runtime
corruption detected on /Volumes/nj_kruses Time
Capsule/Tiroth.sparsebundle (fsck_hfs -q termination status: 3)

-- 
Mvh./Regards,    Niels Jørgen Kruse,    Vanløse, Denmark

[toc] | [prev] | [next] | [standalone]

#96653

Fromnospam <nospam@nospam.invalid>
Date2016-11-08 10:07 -0500
Message-ID<081120161007221376%nospam@nospam.invalid>
In reply to#96651
In article <1mwe8lg.1fgh3eebwe53nN%nj_kruse@me.com>, Niels Jørgen Kruse
<nj_kruse@me.com> wrote:

> 2016-11-08 04:57:58.665878+0100 0x139e39   Error       0x0
> 4312   backupd: (TimeMachine) [com.apple.TimeMachine.TMLogError] Runtime
> corruption detected on /Volumes/nj_kruses Time

there's your answer.

[toc] | [prev] | [next] | [standalone]

#96662

FromJolly Roger <jollyroger@pobox.com>
Date2016-11-08 18:22 +0000
Message-ID<e8ejerFns3lU4@mid.individual.net>
In reply to#96649
On 2016-11-08, Johnson <null@example.com> wrote:
>
> logging has changed with Sierra.
>
> to see TM logs for the last four hours try
> $ log show --predicate 'subsystem == "com.apple.TimeMachine"' --info --last 4h

Thanks. I forgot about that. Still blissfully running El Capitan here. : )

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.sys.mac.system

csiph-web