Re: Time Machine CORRECTION.

From	Lloyd E Parsons <lloydp21@live.com>
Newsgroups	comp.sys.mac.system
Subject	Re: Time Machine CORRECTION.
Date	2013-11-10 10:48 -0600
Organization	A noiseless patient Spider
Message-ID	<l5odc4$rt7$1@dont-email.me> (permalink)
References	<l5o9vc$7vp$1@dont-email.me> <l5od5s$ov0$3@dont-email.me>

Show all headers | View raw

On 2013-11-10 16:44:45 +0000, Wes Groleau said:

> On 11-10-2013 11:42, Wes Groleau wrote:
>> On 11-10-2013 11:33, Lloyd E Parsons wrote:
>>> On 2013-11-10 15:50:03 +0000, Wes Groleau said:
>>> 
>>>> Opinions/comments on this?
>>>> 
>>>> I have two external backup disks.  One is a whole disk, 500 GB
>>>> (WD500).   Other is an 800 GB partition (WD800) in a 2 TB disk.
>>>> 
>>>> Today, I got a pop-up that Time Machine (TM) could not complete the
>>>> backup on WD800.
>>>> 
>>>> Opened TM preferences, and it was "preparing to backup" on WD500.
>>>> 
>>>> Opened Finder to check size (with GetInfo) and saw the symbol that
>>>> backup is in progress on WD800 !  Checked the size--lots of free space.
>>>> 
>>>> After a long time, TM was still "preparing" on WD500
>>>> 
>>>> So, pop-up says backup on "eight" failed; Finder says it is still
>>>> happening on "eight" and TM says it is working on "five"
>>>> 
>>>> ??
>>> 
>>> Wes, are you on Mavericks?  I noticed some oddities along the way with
>>> TimeMachine and since I didn't actually need the backup that was there,
>>> I just killed it and started anew.  Now things are as they are supposed
>>> to be.
>>> 
>>> Of course, I haven't come close to filling the 2Tb TimeCapsule with new
>>> TM backups from a 128Gb MBP!  :)
>> 
>> Yes.  I have had other weird things on TM before, but never this one.
>> Most of the others seem to be due to some obscure bug in disk
>> management.  External drives suddenly become read-only, fixed by unmount
>> and re-mount.  And then I have to (sometimes) re-add the drive to TM.
> 
> OOPS, backup.  I do have 10.9, but today I booted 10.8 to look for a 
> prefs file that was trashed by the 10.9 installer.  So the 
> above-described weirdness happened on 10.8

Odd.  I've had good luck with TM over the years.  But there have been a 
very few times when things got hinky and the only solution offered from 
Applecare was wipe and redo.  In my case that isn't an issue since I've 
never had to go to a TM backup to get anything other than as a test to 
see if it worked.

but it does put the backup in question doesn't it?

-- 
Lloyd

Back to comp.sys.mac.system | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Time Machine oddity. Wes Groleau <Groleau+news@FreeShell.org> - 2013-11-10 10:50 -0500
  Re: Time Machine oddity. Lloyd  E Parsons <lloydp21@live.com> - 2013-11-10 10:33 -0600
    Re: Time Machine oddity. Wes Groleau <Groleau+news@FreeShell.org> - 2013-11-10 11:42 -0500
      Re: Time Machine CORRECTION. Wes Groleau <Groleau+news@FreeShell.org> - 2013-11-10 11:44 -0500
        Re: Time Machine CORRECTION. Lloyd  E Parsons <lloydp21@live.com> - 2013-11-10 10:48 -0600

csiph-web