Restore Time Machine Full Backup After Catastrophic Failure

I am new to the Mac and using Time Machine as my primary backup utility. My concern is the way it creates one full backup at the beginning and only incremental ones after that. If the full backup gets overwritten due to the program needing hard drive space, does it know to create another full backup, even if it needs to delete some older incremental backups?
I am concerned I will need to complete a full restore at some point, and will not be able to do so because there will not be a full backup present on the Time Machine disk.
Also, who has had to restore from a catastrophic disk failure using an external time machine disk? Is this easy? Does it work properly?

you concerns are unfounded. due to the way TM keeps data organized every backup is full and independent of any other backups.
when TM makes a backup it only backs up afresh new and changed files. everything else is _*hard linked*_ to existing backup copies.
deleting an earlier backup to save space as TM does sometimes has zero effect on the remaining backups. they remain full and complete. doing a full system restore from TM is very easy. you boot from the SL install DVD and select "restore system from backup" from Utilities menu.
However, it should be noted that TM is still very buggy and doing a full restore can not be tested until you actually do it. therefore, it's advisable to have a double backup using a different backup tool. bootable clones are the best for doing a full restore. CCCloner and Superduper are excellent cloning backup programs.

Similar Messages

Time machine full backup after disk and disk permissions repair

my macbook would not boot so i inserted the snow leopard DVD and did a disk repair and disk permissions repair, after that it booted perfectly but when it went to do a backup it did a full backup of 149GB , i am unsure why it has done this and would like to know how to stop it as i am trying to save space on my time capsule.
thank you in advance

Brycycle wrote:
i do not wish to let it do a full backup so as to save space on my time capsule but this is the log up till when it started transferring data.
I'm afraid you don't have much choice. You do have lot of space available, though.
Node requires deep traversal:/ reason:must scan subdirs|new event db|
No pre-backup thinning needed: 165.92 GB requested (including padding), 507.60 GB available
The "deep traversal" means TM compared everything on your system to the backups, and estimates that about 138 GB is new/changed (it adds 20% for workspace on the TM disk - the "padding" in the message).
If there's about 138 GB on your system, see #D3 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum), for some common reasons for TM to do a new full backup.
If there's more, #D4 there has some common reasons for large backups.
If all you did was repair disk and permissions, neither should have resulted.
the reason i did a permission repair and disk repair while running from the install disk was because my laptop would not boot from the internal disk so i did both just to be safe.
That's fine; just do the Permissions Repair again, while running normally.

Time Machine Full backup after disk move

I have followed the instructions for moving my Time Machine backup to a new disk as per instructions here. However, once I have completed the copy to the new disk, the first time that time machine runs, it seems to be do a full new backup and therefore there is not enough room on the new disk.
I get the following error: Time Machine could not complete the backup. This backup is too large for the backup disk.
Please help, this is driving me nuts.
Thanks,
Ian.

Peeps, I am so sorry, I am such an idiot, I have just realise what I have done wrong!!!
Whilst trying to build my new drive (part of which is to be my new Time Machine backup) I created a 500gb backup in my local Documents folder - this is why my initial Time Machine backup was so large, not because Time Machine was trying to do a full backup!!!
Thanks for looking,
Ian.

Time Machine loses backups after a full restore.

Greetings
(Possibly due to parallels, my Imac was running so slow or hanging. As a result,) I ran a full system restore from Time Machine. It worked well. Then I thought I would try a better restore date and used that. After this successful restore, I now notice that all earlier backups have been deleted/lost - or at least they are not available on the Time Machine,
The only event in between was to add to the time machine a windows based account file.
Imac seems to run OK now, but files from around July to now are missing.

After a full restore, Time Machine may start a new backup. You can ctrl-click the TM icon and +Browse Other Time Machine Disks+ to view your old backups. I can't be sure, but you could try to go to TM Preferences and Change Disks to see if you can continue to back up to your old TM folder/sparsebundle. Otherwise, you will have 2 backups now, the old one being dormant, but accessible.

Access Time Machine partial backup after system restore

My iMac crashed. I ran Disk Utility Repair Disk on the hard drive and received this message: "Disk Utility can't repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files".
I had had Time Machine backing up regularly wirelessly, and previously hadn't noticed any problem with it. So I thought everything had been backed-up properly.
I reformatted the hard drive and chose to restore the system from Time Machine back-up. It turned out that you can only restore from full system back-ups and my Time Machine hadn't made a full back-up for half a year! Previously it had made full back-ups every 2 or 3 days then it stopped doing full back-ups half a year ago without any warning.
I went ahead with the system restore from the half-year-old full backup thinking that I would be able to access the partial back-ups once the system is restored. But I can't! If I access Time Machine, the most recent back-up I can see is the half-year-old full backup from which I restored the system. There are documents, music and hundreds of photos, originally saved to the hard drive since the last full back-up, that I cannot access, even though Time Machine had been backing up every day until the iMac crashed.
How can I retrieve these files from Time Machine?

tmutil listbackups
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2009-11-10-210145
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2009-11-17-053753
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2009-12-02-005634
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2009-12-09-073939
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2009-12-16-000359
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-01-07-164941
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-01-18-194339
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-01-25-073833
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-02-01-071544
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-02-08-192553
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-02-23-011615
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-03-02-073425
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-03-11-001704
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-03-18-134858
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-03-31-004614
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-04-09-084554
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-04-16-142610
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-04-25-210514
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-05-03-040744
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-05-10-080207
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-05-17-020416
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-05-28-002711
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-06-04-010034
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-06-16-000448
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-06-25-213759
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-07-08-002557
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-08-19-222633
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-08-26-193609
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-09-02-203645
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-09-10-075001
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-09-24-000147
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-10-11-071420
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-10-18-071136
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-10-25-192005
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-11-08-105951
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-11-16-082710
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-11-28-000529
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-12-05-094613
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2010-12-12-010050
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-01-09-224521
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-01-16-002322
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-01-23-005302
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-01-30-123816
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-02-06-084024
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-02-13-152616
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-02-21-172006
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-02-28-073952
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-03-07-064607
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-03-14-072117
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-03-21-002338
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-03-28-191153
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-04-05-034614
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-04-12-073716
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-05-01-231606
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-05-08-145446
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-05-15-102229
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-05-22-144213
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-05-29-201711
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-06-05-005053
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-06-13-160254
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-06-25-224356
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-07-02-112247
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-07-11-003808
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-08-21-195918
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-08-28-104051
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-09-04-001125
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-09-10-001317
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-09-15-194157
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-09-16-210303
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-09-17-112311
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-09-18-120910
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-09-19-194243
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-09-20-073831
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-09-21-073034
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-09-22-075050
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-09-23-230449
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-09-24-092757
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-09-25-001748
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-09-26-215704
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-09-27-182748
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-09-28-192528
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-09-29-182816
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-09-30-201924
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-10-01-004110
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-10-02-003106
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-10-03-221651
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-10-04-211443
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-10-05-213335
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-10-06-183753
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-10-07-212855
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-10-08-204219
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-10-09-162419
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-10-11-165739
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-10-12-225835
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-10-13-090625
/Volumes/Backup of T’s iMac/Backups.backupdb/T’s iMac/2011-10-13-191539
Oct 13, 2011 was the last full backup, the one used to restore the system.

Force Time Machine Full Backup

I wanted to update my Macbook Pro with a new Hard Disk, after preparing & installing the new HD and then chossing to restore from the Time Machine, i was surpised that the Time Machine showed me only some Backups(Full Backups), and the last full backup was 6 Months old, although i did a TM Backup just before installing the new HD, but apprently it is an incremntal backup, therfore it was not shown in the list.
So my question is how to force a TM Full Backup so that i can just restore it on the new HD. I know i can do it if i deleted all the old Backups, but i want to keep them, is it possible?

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
          <key>sourcePaths</key>
          <array>
                    <string>/</string>
          </array>
          <key>standardExclusionPaths</key>
          <array>
                    <string>/.MobileBackups</string>
                    <string>/MobileBackups.trash</string>
                    <string>/.MobileBackups.trash</string>
                    <string>/.Spotlight-V100</string>
                    <string>/.TemporaryItems</string>
                    <string>/.Trashes</string>
                    <string>/.com.apple.backupd.mvlist.plist</string>
                    <string>/.fseventsd</string>
                    <string>/.hotfiles.btree</string>
                    <string>/Backups.backupdb</string>
                    <string>/Desktop DB</string>
                    <string>/Desktop DF</string>
                    <string>/Network/Servers</string>
                    <string>/Library/Updates</string>
                    <string>/Previous Systems</string>
                    <string>/Users/Shared/SC Info</string>
                    <string>/Users/Guest</string>
                    <string>/dev</string>
                    <string>/home</string>
                    <string>/net</string>
                    <string>/private/var/db/com.apple.backupd.backupVerification</string>
                    <string>/private/var/db/efw_cache</string>
                    <string>/private/var/db/Spotlight</string>
                    <string>/private/var/db/Spotlight-V100</string>
                    <string>/private/var/lib/postfix/greylist.db</string>
                    <string>/Volumes</string>
                    <string>/Network</string>
                    <string>/automount</string>
                    <string>/.vol</string>
                    <string>/tmp</string>
                    <string>/cores</string>
                    <string>/private/tmp</string>
                    <string>/private/Network</string>
                    <string>/private/tftpboot</string>
                    <string>/private/var/automount</string>
                    <string>/private/var/folders</string>
                    <string>/private/var/run</string>
                    <string>/private/var/tmp</string>
                    <string>/private/var/vm</string>
                    <string>/private/var/db/dhcpclient</string>
                    <string>/private/var/db/fseventsd</string>
                    <string>/Library/Caches</string>
                    <string>/Library/Logs</string>
                    <string>/System/Library/Caches</string>
                    <string>/System/Library/Extensions/Caches</string>
                    <string>/private/var/log</string>
                    <string>/private/var/spool/cups</string>
                    <string>/private/var/spool/fax</string>
                    <string>/private/var/spool/uucp</string>
          </array>
          <key>systemFilesExcluded</key>
          <false/>
          <key>userExclusionPaths</key>
          <array/>
</dict>
</plist>

Post-restore Time Machine/bundle backup problem

Earlier this week the HD in my iMac died. I had the drive replaced and performed a full restore from my Time Machine backup. The four hour restore went fine.
The next day I turned Time Machine back on. I expected it would want to perform a complete backup of the restored machine. It appeared to start okay, calculating changes and deleting old backups. But then it started doing that in a loop: checking changes, deleting backups, cleaning up, checking changes, deleting backups, etc. After about five cycles I just left work and let it do its thing. Twelve hours later when I got home it still hadn't done a backup, and appeared to be stuck in 'deleting old backups.' So I went ahead and stopped Time Machine.
Now, if I turn TM on or initiate a manual backup, it checks for changes, spends a long time at 99% during that process, then eventually unmounts the bundle, goes to cleaning up, and then hangs there until I manually stop it.
I've tried disk utility, but anytime the backup bundle is mounted, Disk Utility locks up with the spinning beach ball before I ever get to drag the bundle into the window and try to verify/repair.
Any suggestions? At this point I'd be fine erasing the entire bundle and starting new backups from scratch, but I'm not sure how to properly "reset" Time Machine, and of course I can't the bundle to appear in Disk Utility.

blevenstein wrote:
Earlier this week the HD in my iMac died. I had the drive replaced and performed a full restore from my Time Machine backup. The four hour restore went fine.
The next day I turned Time Machine back on. I expected it would want to perform a complete backup of the restored machine. It appeared to start okay, calculating changes and deleting old backups. But then it started doing that in a loop: checking changes, deleting backups, cleaning up, checking changes, deleting backups, etc.
Yes, that cycle could go on for a very long time. Assuming the TC's disk was near full, TM would have to delete a whole lot of backups to make room for a new full backup. Unfortunately, it has to mount the sparse bundle, delete a single backup, dismount the sparse bundle, compact it, then mount it again to see if it's made enough room. The word "excruciating" isn't enough!
Now, if I turn TM on or initiate a manual backup, it checks for changes, spends a long time at 99% during that process, then eventually unmounts the bundle, goes to cleaning up, and then hangs there until I manually stop it.
It's probably still deleting old backups, although it's possible there's one that it can't delete, and is stuck on it.
I've tried disk utility, but anytime the backup bundle is mounted, Disk Utility locks up with the spinning beach ball before I ever get to drag the bundle into the window and try to verify/repair.
That does sound like the sparse bundle is now hopelessly corrupted.
Any suggestions? At this point I'd be fine erasing the entire bundle and starting new backups from scratch, but I'm not sure how to properly "reset" Time Machine, and of course I can't the bundle to appear in Disk Utility.
First, of course, turn TM "off" via TM Preferences.
If there's nothing else on the TC's disk, erase it. Use the +*Airport Utility+* app, in your Applications/Utilities folder. Select +*Base Station > Manual Set-Up+* from the Menubar, then Disks in the tool Bar, then Erase.
If there's other stuff there that you want to keep, and can't copy elsewhere temporarily, just delete the sparse bundle via the Finder.
Then you should be able to turn TM back on and have it start fresh (I'd strongly recommend connecting your Mac to the TC via an Ethernet cable to speed up the initial backup, if at all possible). If there's a problem, you can try the "reset" procedure in #A4 in the Time Machine - Troubleshooting *User Tip,* also at the top of the +Time Machine+ forum.

Time Machine full backup started... why!?

Installed Mavericks, played around a bit, time machine was behaving normally until today.
I thought the usual backup was starting, not so many changes since last one, maybe a couple of giga of new photos to add but Time Machine decided instead to delete the whole content and start from scratch.
My time machine disk is 1.5TB my full backup will be under 1.20TB, and again Mavericks was already backing up normally since I installed that... so what caused this absurd behaviour?
If this is not a bug, what else? Because of this at the moment I have no backup, time machine is working and if I am lucky it'll take one full day or two to have a backup again.

troyboy65 wrote:
I dont understand why when the total of the 2 machines only totals 500gb
Time Machine keeps copies of everything currently on your Mac, plus copies of things you've changed or deleted. It varies widely depending on how you use your Mac, but Time Machine generally needs 2-3 times the space of the data it's backing-up, to be able to keep a reasonable "depth" of backups for you.
Is there some settings i need to change or is something wrong?
Probably neither.
If both Macs are running Snow Leopard, you may be getting notices like the one in the blue box in #C4 of Time Machine - Troubleshooting. You can stop those notices if you want.
If either is on Leopard, it's a different story. When Time Machine on a Mac running Leopard runs out of room, and the +Warn when old backups are deleted+ option is checked, it fails with a message like the one in the tan box in #C4. Remove the check from the box, and it will start deleting old backups.
But if you're getting the message in the pink box, something is likely wrong. See the suggestions and explanations there.

Restore time machine from backup, stuck on Apple screen

A Macbook Pro I've restored from a TM backup is stuck in a spinning marker in the Apple bootup screen. Any suggestions to get it booting? Thanks

champ2153 wrote:
I am having the same issue. When I attempt to restore my information from time machine, the restore seems to go well. But..right around the moment of 70% or so on the progress bar, (with about 20 minutes remaining) the "restore was successful" box pops up and prompts me to restart the machine. Upon restart I can not get past the white apple screen. I've tried just installing OSX
When you do that, has all your data been restored? If so, just download and install the "combo" update to get back to 10.6.6.
and then using migration assistant, but migration assistant does not recognize my time machine external. Any thoughts?
Try repairing your backups, per #A5 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum).

Time Machine First Backup After Upgrade Stuck @ Deleting Old Backups

This has been going on for the past 4 hours. Should I quit and start over. I think I may have messed it up when I clicked the "Encypt Disk" during the first update... Thanks...

InAfrica wrote:
I think I may have messed it up when I clicked the "Encypt Disk" during the first update...
Quite possibly.
I don't know how long it takes to encrypt about 480 GBs, but it will clearly take quite a while.
See #31 in Time Machine - Frequently Asked Questions for some info on encrypting your backups.
Use the widget in #A1 of Time Machine - Troubleshooting to display the backup messages from your logs. Locate the backup in question, then copy and post all the messages here.

Time machine full backup

Why does my computer start a new backup series every week / 10 days now? Never used to with Lion.

It backs up every hour which is OK but the frequency of starting a new backup has increased dramatically since I switched to Mountain Lion.
It now wants to start a new backup every week to 10 days and it takes forever to do a new full backup.

FYI: No Sleep during Time Machine initial backup

Just an FYI - I noticed that during the first Time Machine full backup, the computer does not go to sleep.
I would also assume that if you computer is asleep, it will not wake for each hourly backup.

Hi, and welcome to the forums.
You need to know that backing-up that way is "iffy" and +*not supported by Apple.+* See Using Time Machine with an Airport Extreme Air Disk (or use the link in *User Tips* at the top of this forum).
Kernel panics are usually caused by hardware problems, but can be software.
Disconnect all peripherals, except keyboard and mouse. Reconnect one at a time to see if you can find the culprit.
If that's no help, run the Apple Hardware Test: http://support.apple.com/kb/HT1509
And perhaps a heavy-duty memory test, such as the free Rember: http://www.kelleycomputing.com/
More kernel panic info:
Apple Support - About kernel panic messages
Mac OS X Kernel Panic FAQ
The X Lab - Resolving Kernel Panics
Apple Developer - Technical Note TN2063: Understanding and Debugging Kernel Panics
Tutorial: Avoiding and eliminating Kernel panics
|
If you still want to back up via the Airport, the first backup will be much faster if you connect via Ethernet.

HT201250 When restoring Time Machine after a failure, does it also restore the files to the same order, for example - within iPhoto I have pics/ videos in folders and sub folders organised as family/events etc - will it go back to this exact order after a

When restoring Time Machine after a failure, does it also restore the files to the same order, for example - within iPhoto I have pics/ videos in folders and sub folders organised as family/events etc - will it go back to this exact order after a restore?

Hi Stavros0203,
When restoring your entire system from a Time Machine backup, it is restored to the state it was when that backup was made. See this article for reference -
OS X Yosemite: Recover your entire system
Thanks for using Apple Support Communities.
Best,
Brett L

Unable to boot after Time Machine full system restore!!

I was having some serious slowdowns with my computer. I did multiple RAM and HD hardware tests, everything seemed to be working fine. I had recently deleted a bunch of files in order to free up some HD space, so I thought that may be the culprit. So I did a Time Machine backup and restored the Powerbook to it's original 10.3 software. All was fine. Then I upgraded back to 10.5 and all was fine. Then I did a Time Machine full system restore overnight and got the message "Your restore was successful, you must now restart your computer" (or something to that effect). Now I get the start-up chime and startup screen (apple logo) but then the computer shuts itself down. I have reset the PMU and PRAM to no effect. I have tried booting up in safe made, also no dice. I have tried starting it up with the time machine HD attached - doesn't help. I guess I'll need to hit the genius bar but wanted to ask the friendly discussion forum folks first. thanks in advance.

Hi coldengray
Did you try to start from your System-CD? Hold down C-key during startup, start DiskUtility from the menu and verify/repair disk and permissions there.
If the CD is not available you can also connect your TimeMachine-Disk, select it as startup volume in System Preferences/StartupDisk, restart and then run DiskUtility from folder Applications/Utilities
Good luck P

Time machine started over after a complete restore, how to get to older?

Yesterday, photoshop and parrallels started crashing and I could not get them working, So I decided to do a complete system restore from install disk time machine from the day before when everything was working fine.
so it restored the system to its previous state. parrallels was still not working correctly so I restored the folder from a week or so ago. That didn't get it back either, so I thought of maybe reloading the application from an earlier time period might help.
But, time machine has started itself over. there is only backup data from this morning in the time machine internal backup drive. How do i get to my older backups? Do they just go away after a system restore?

Sam,
No, you need to Ctrl-Click the Time Machine DOCK icon. Then choose "Browse Other Time Machine Disks...".
Here is a thought. When you did the restore, what Mac OS version did you restore. Your states say 10.5.5 but might your Mac have been restored to 10.5.4 or earlier with your restore?
I have found in my own testing, that since the 10.5.5 update, "Archive & Installs", "Erase & Installs", and "Restore System From Backup..." no longer trigger a new full backup. That is they continue to use the same backup set as before. (Note though, you will likely see a very large incremental backup, but not necessarily a new Full Backup set.) See my comments here:
[http://discussions.apple.com/thread.jspa?threadID=1771493&tstart=0]
If, however, you restored to a Mac OS version previous to 10.5.5, and then allowed Time Machine to perform a backup, then a new Full Backup would be preformed. Likely, you might be able to avoid this if you do the restore (prevent Time Machine from backing up), update to 10.5.5, then allow Time Machine to backup.
Cheers!

Restore Time Machine Full Backup After Catastrophic Failure

Similar Messages

Maybe you are looking for