dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1061
share rss forum feed

ke4pym
Premium
join:2004-07-24
Charlotte, NC
Reviews:
·VOIPO
·ooma
·Verizon Broadban..
·Northland Cable ..
·Time Warner Cable

Time Machine craps out in 10.8.2

Gang,

I just upgraded my early 2008 Mac Pro from 10.7.3 to 10.8.2. Every single version of Mac OS that I've had on my Mac has had a perfectly working install of Time Machine.

TM just worked (tm). I didn't have to futz with it. It saved my from the crappy Mac RAID card, and helped me transition back and forth to various RAID levels.

But on 10.8.2, it just breaks (tm). It fills up the target TM disk and says it is full. How can it be full? It is bigger than the volumes I'm backing up?

So, I erase the TM disk, set everything back up and less than a day later, it craps out again. Telling me the TM disk is full and that it will try to clear out old copies on its next run. Except, it doesn't.

Any ideas? I'm backing up to a 1.5TB drive attached via FW. The volume size on the Mac is 1TB.

And for the record, SMB still sucks. Can't they go back to Samba? That just worked (tm) too.



kerriskandie

join:2001-10-09
Coram, NY

Can't help, but I've NEVER felt confident using TM..

CCC or similar for me everytime..........


kitsune

join:2001-11-26
Sacramento, CA
reply to ke4pym

Couple different possibilities. First and most likely, you have an app that changes a large file on a regular basis. Database apps commonly do this, Virtual Machines (VMWare/Parallels) are likely culprits as well. Second, Time Machine mistakenly thinks everything needs to be backed up. If you want to find more info, I would open console and search for "backupd" in the system.log.


ke4pym
Premium
join:2004-07-24
Charlotte, NC
Reviews:
·VOIPO
·ooma
·Verizon Broadban..
·Northland Cable ..
·Time Warner Cable
reply to ke4pym

Kerriskandie-->TM has *never* failed me. I used it to migrate from RAID 1 -> RAID 5 and back again. Full system restores. I've used it to restore files. It has worked perfectly.

Until now.

Yes, I do have a VM running under Fusion 5.0. However, this has never been a problem prior to 10.8.2.


kitsune

join:2001-11-26
Sacramento, CA
reply to ke4pym

Is the VM on a separate partition? If not have you excluded it from your backup? If it's not on a separate partition or excluded then every time you open the VM it will trigger TM to backup all of it.

As a side note, if you just got 10.8 you have 90 days of support from Apple. So if all else fails you can call in to have them take a look at it.


ke4pym
Premium
join:2004-07-24
Charlotte, NC
Reviews:
·VOIPO
·ooma
·Verizon Broadban..
·Northland Cable ..
·Time Warner Cable

said by kitsune:

Is the VM on a separate partition? If not have you excluded it from your backup? If it's not on a separate partition or excluded then every time you open the VM it will trigger TM to backup all of it.

As a side note, if you just got 10.8 you have 90 days of support from Apple. So if all else fails you can call in to have them take a look at it.

No, the VM is on the same partition. I've not excluded it from my backup. But why should I have too? This wasn't an issue in 10.7.3. And it saved my hide a couple of times when I'd been lax in doing updates and got drive-by downloads. Just ask TM to put the VM back from 2 days ago.

kitsune

join:2001-11-26
Sacramento, CA
reply to ke4pym

The way time machine works did not change in 10.8. It will automatically backup any file that has been changed since the last backup. VM's usually cause the backup to fill quickly because they store the entire VM in a single file. So any time you open the VM that file is changed and triggers time machine to back it up.

Now I'm not saying that this is definitely your problem, just that it could be contributing to it.

I would open console and search system.log for backupd to find more information.

PS as an FYI your backup should be larger than the amount of data you are backing up. The first backup is for the entire contents and then every hour it will backup whatever has changed. Eventually it will fill any size drive you decide to use. Normally, it will consolidate backups to make them take up less space and once it gets close to full erase older backups. However, yours is filling so quickly those processes are not being triggered.


rmmoody

join:2001-02-15
Leawood, KS
reply to ke4pym

For what it's worth, I also have an early 2008 Mac Pro with 10.8.2 and Time Machine running to a network drive and it's working just fine. I also have my boot partition set up as a software raid (two mirrored drives), never had a problem with it.

--
Mark



kerriskandie

join:2001-10-09
Coram, NY
reply to ke4pym

Never got it to work consistently, with NAS/Networked drives, even desktop....in the early TM days...kind of gave up,
CCC, less eye candy, but does a solid job!!!!!!!


ke4pym
Premium
join:2004-07-24
Charlotte, NC
Reviews:
·VOIPO
·ooma
·Verizon Broadban..
·Northland Cable ..
·Time Warner Cable
reply to kitsune

said by kitsune:

The way time machine works did not change in 10.8. It will automatically backup any file that has been changed since the last backup. VM's usually cause the backup to fill quickly because they store the entire VM in a single file. So any time you open the VM that file is changed and triggers time machine to back it up.

Now I'm not saying that this is definitely your problem, just that it could be contributing to it.

I would open console and search system.log for backupd to find more information.

PS as an FYI your backup should be larger than the amount of data you are backing up. The first backup is for the entire contents and then every hour it will backup whatever has changed. Eventually it will fill any size drive you decide to use. Normally, it will consolidate backups to make them take up less space and once it gets close to full erase older backups. However, yours is filling so quickly those processes are not being triggered.

My VM (W7 in Fusion) is open all the time.

The TM disk is 1.5TB in a FW enclosure and is connected via FW800.

The disks in the Mac are a RAID 1 at 1TB with 300GB free. So, the TM disk should have plenty of capacity.

The thing is TM will start up and say it has 35MB to backup. Then it starts counting up the data it has backed up. Before you know it TM is saying it has to back up a gig. Then 2, then 3, then 4, then 30, then 35 and then it yells because the disk is full.

I'll look into the logs.


kerriskandie

join:2001-10-09
Coram, NY

See what I mean, more trouble than it worth.....CCC/ mere minutes, have your whole 500 Gig HD cloned/backed up!!!!!!!


ke4pym
Premium
join:2004-07-24
Charlotte, NC
Reviews:
·VOIPO
·ooma
·Verizon Broadban..
·Northland Cable ..
·Time Warner Cable

said by kerriskandie:

See what I mean, more trouble than it worth.....CCC/ mere minutes, have your whole 500 Gig HD cloned/backed up!!!!!!!

I'm really happy you like CCC. But TM has worked well for 5 years now for me. I'd like to get it fixed.


kerriskandie

join:2001-10-09
Coram, NY
reply to ke4pym

CCC has worked perfectly for..........well certainly more than 10 years!!!!!!

hope you get it sorted!!!!


ke4pym
Premium
join:2004-07-24
Charlotte, NC
reply to ke4pym

Deleting /Library/Preferences/com.apple.TimeMachine.plist for the win!

All fixed.