Time Machine crashes during backup

Similar Questions

• Time machine crashes during the attempt to remove backup

  Hello people,

  Recently trying to remove a TM backup my machine freezes completely upwards. This seems to happen after doing a delete in the morning, it after trying to delete another back up and my machine freezes.

  I can get it to unlock by slightly pressing the power switch on the back of my Imac, then the screen goes black for a moment, then turns on and I can make the choice to delete or remove the back upward.

  Can I delete a backup by day with questions, as soon as I try and do it again, it freezes.

  It was after my system boots every day.

  I'm on the latest version of OSX Yosemite.

  Suggestions for troubleshooting this problem would be appreciated.

  Removal of TM backups seem to be a very intense process for the machine and takes a long time. It is probably just processing information and take a lot of computer resources. And it should only be done for TM, or you will corrupt your backup.

  Why you try to manually delete the backups? This isn't a good idea.

• Time Machine crashes after leaving

  My Time Machine crashes after I open and then 'Cancel' to return to the desktop, even without the restoration of a file. The console displays a lot of mistakes for different files like this:

  14/01/16 9:49:27.114 AM Finder [325]: layout error: error Domain = NSCocoaErrorDomain Code = 257 "the file '944773V7K4.com.musicnotes.ipad.free' could not be opened because you do not have permission to see." UserInfo = 0x60800326cf80 {NSFilePath = / Volumes/iMac Time Machine 2TB/Backups.backupdb/David's iMac/2016-01-01-005253/Macintosh HD / Users / myuser / Library / Application Support/CloudDocs/session/containers/944773V7K4.com.musicnotes.ipad.free, NSUnderlyingError = 0x608002641ef0 "the operation could not be completed.} Permission denied"}

  Any ideas how to solve this problem?

  Start with A4 in the 1st article linked.

  Troubleshooting of Time Machine

  Solving the problems of Time Machine

• Using Time Machine for subsequent backups

  I would like to know how can I use Time Machine for frequent backups after the initial. Specifically, I want to know how I can assure you that Time Machine DO backup files that have changed since the initial AND only the new backup files that have been added to the hard drive since the last backup?  In other words, Time Machine will do it automatically or it will save all the entire hard drive again?

  Time Machine which will automatically

  Yes.

• Time Machine is not backup as I loaded Sierra

  My time Machine says that it has not saved for 890days? Since I loaded Sierra now its in "preparing backup" permanent mode

  Reboot, try again.

• Time Machine blocked preparation backup

  Hi community

  Time Machine, I get the iMac to backup, Time Capsule 371 GB of the preparation phase of backup available 998 GB for one eternity, as others have reported.

  My system is an iMac (27-inch, late 2009), processor 2.8 GHz Intel Core i7, 12 GB 1067 MHz DDR3 Memory with an ATI Radeon HD 4850 512 MB video card and a physical disk internal 1 TB ST31000528AS Sata media.

  My last backup was September 16, 2016 @ 1257 GMT and my software was the last version of El Capitan.  (I backup to another external HARD drive, using Carbon Copy Cloner and backup guru Mac unfortunately I don't have a big enough other ext HDD to run a time Machine backup to as well).

  When the TC is connected I can see the iMac and iMac.sparsebundle backup folder and when I enter the time Machine I can see the chronology running back from 16 Sep and it allows me to access the files in the folders.  So, I guess that the disk HARD of TC is OK.

  Software changes have been: 1 MS a copy of CCleaner Free 1.14.451, 2 Ms Security Update 2016-001, 13 Sep Adobe Flash, 14 Sep 12.5.1, 16 Sep Digital Camera RAW compatibility update iTunes.  Never had a problem before with these downloads.  Safari updated September 20, then to Sierra 22 Sep having saved first using the CCC and MBG.

  Through the various pages of help through Google.  Follow-up advice given to reset the SMC and the PRAM, deleted Sophos home and com.apple.TimeMachine.plist and com.apple.TimeMachine.plist.lockfile.

  Rebooted and restarted the iMac and Time Capsule several times, done many backups check the reset even the time Capsule disk, but all without success.

  I'm still stuck in preparation of backup when I reselect the backup drive.

  Can someone help please?

  Finally, I had a problem in 2014 when Apple recalled the iMac to a HARD drive replacement program.  This was successful, but a few days later the Time Machine and time Capsule would not save.  This is due to the component change when the UUID was different.  The advice I would have given were to know how inherit backup and controls disk associated within the Terminal. Stupidly, I started again when the TC asked me to and then discovered the Terminal commands a few days later.  The loss of backups of 4 years was no big problem, so I suppose that if I have to, I won't again unless a member of the smart community can better advise me please?

  Good community

  I forgot to tell you that I save on a Capsule of 1 GB bought in 2010 with the iMac.

  Don't know how, but not before I finished posting my above query Time Machine kicked back in action and performed a backup pick up all the changes, about 50 GB since Sept. 16.

  He did once again this morning, so I'm sorry I can't post what Time Machine and my Time Capsule due action to act properly.

  Concerning

• MacOS Sierra - time machine stuck preparation backup on network devices

  Since I've upgraded to Mac OS Sierra, cannot use my local backup USB. Time Machine is stuck with the message "preparing backup" - more than 12 hours - for network devices, an Apple FileVault and another NAS device. Works very well with the local USB drive.

  Something funny underway with network devices such that she works for the drives the.

  Hope Apple take note and fix.

  I have the same problem. I found this,

  macOS, problems of the Sierra: Time Machine backup Mac

  Time Machine problems prevented the Mac owners of their devices to backup since the upgrade to Mac OS Sierra, and the problem is widespread enough that Apple has published a guide on what to do if you can't back up:

  Discount for the iMac SMC

  1. turn off the device

  2. unplug the power cord from the monitor

  3. wait 60 seconds

  4 reconnect the power cord

  5. DON'T TURN ON DEVICE

  Reset the PRAM

  1. the computer must always be switched off.

  2. Locate the following keys on the keyboard: command, Option, P, and r. you need to hold these keys down simultaneously in step 4.

  3. press and release the power button to turn on the computer.

  4. press and hold the Command-Option-P-R keys. You have to press these keys before the gray screen appears. Continue to hold the keys down until the computer is restarted, and you hear the tone of starting for the 3rd time.

  5. release the keys.

  You can then try to save again. If this does not work, try to disable indexing on the drive you want to back up.

  but I'm not sure it's the same question. I'll try it and report.

• Time Machine crashes

  Looking in my journal I find this:
  com Apple.backupd: waiting for index or loan (100)

  After consultation with google I find that the problem is probably related to a disconnection from the backup disk that happened earlier today, when I accidentally stumbled upon the USB when fixing my iPhone.

  I barely touched, but it was enough to cause a disconnect.

  I ' t may be something else though because it seems a little far fetched that a simple disconnect/connect must

  cause such a catastrophic failure like that.

  This post describes how Time Machine can lead to corrupted data when they are exposed to accidents:

  Re: Time Machine 'Waiting for the index to be ready': what it really means?

  If this is the case, then it tells me that Time Machine is not capable of handling disconnects and auto resume.

  I'm guessing that disconnects happen every day to thousands of users of the time Machine.

  So I'm expecting Time Machine to use a fault-tolerant Protocol.

  Maybe it's not.

  Now, I get multiple instances of "com.apple.backupd: waiting for index be ready (100)" in my log file.

  Even if the projector is not indexing.

  It took about an hour to save 3 KB of data.

  Wow
  I'm NOT surprised!

  I should also mention that I added all external drives including the backup drive to the exclusion of Spotlight list.
  So they must not interfere with the backup.
  However, when you add the backup drive, I received the message:

  "My Passport for Mac ' is a Time Machine backup drive.

  Spotlight will continue to search for Time Machine backups but seek no other items on the disk.

  But why must it seek the backups at all.
  Why would I want an index of my backup files?

  Tip: I don't want

• First Time Machine to NAS backup freezes at the same point, Console polluted by the same mistakes.

  I just configured my LaCie 5big Network2 act as a time Machine, but it is not back up correctly. When I run it always freezes at 14.70GB/237.71GB, even after deleting the backup and starting up again. I don't know if it of related or not, but the Console is littered with the same error messages (even if Time Machine is not running):

  

  If I stop the backup and restart it, it will get stuck after 7KB. If I delete the backup and starting a new one, it will get stuck at 14,70 Go again. This could be the cause? The NAS is configured correctly and firmware is up to date, disks are operational and functioning perfectly.

  My system is a 2015 retina MBP 15 "16GB / 500GB.

  Time Machine is a LaCie 5big Network2.

  LaCie can support this, but isn't Apple. the NAS can have its own propreitary features or a network can introduce the software is not designed for questions.

  If you want to use a NAS for backup, you can consider Carbon Copy Cloner as alternative

  For more information on the use of a 3rd party with network drive time machine see these article

  http://pondini.org/TM/2.html

  https://www.Google.com/?client=Safari#q=time+machine+over+network+drive

• Time machine sees the backup, but not connecting to new machine

  Just did a transfer from MAC to MAC using Thunderbolt cable - everything is good!  Then, I wanted to make sure that the new Mac can access Time Machine backup file on the network file server.

  Old MAC - running El Capitan 10.11.3 - TM full backup to the network Central of Seagate drive is successful.

  New Mounting successful MAC - running El Capitan 10.11.4 - Time machine disk Seagate file

  . Name of the new Mac is slightly different because of the collision of network host names

  Various attempts to select the reader appear to succeed but the backup information (Date of last backup) are not displayed.

  Entering Time Machine will display the finders stacked, but it will timeout to 30 seconds, saying: he cannot connect to the backup file.

  UNIX command 'mount' shows the machinery once mounted via afp: in /Volumes

  (From old Mac - should be present)

  Rich@SeagateHomeDisk._afpovertcp._tcp.local./SeagateHomeDisk%20TM%20Backup on the Volumes/SeagateHomeDisk TM Backup (afpfs, nobrowse)

  (But on the new Mac - mounts like this)

  [email protected]/SeagateHomeDisk%20TM%20Backup on the Volumes/SeagateHomeDisk TM Backup (afpfs, nodev, nosuid, ridden by rickenne)

  To verify access to the backup file, I started the old Mac and accessed fine.

  Note that I try to not to have the two machine upwards at the same time.

  Should I clean server Seagate Keychain Access permissions for the file mounted correctly?

  How is the drive connected to the network?

• time machine remove the backup target drive

  Running El Capitan - I have set up three units for Time Machine backup: a RAID and a dock that is used for a pair of alternation of readers of archive. One of two archives training to life in a safe Bank and I have Exchange it with the current drive once a week.

  Before I upgraded my OS, Time Machine would simply be two backups between some readers were available and do so without comment. Now, after the upgrade, Time Machine sees that one of the pair is missing and he complains. This means that one time every three hours Time Machine issues a warning that one of the players is not available.

  I have not found a way to disable this warning.

  Be resigning myself to this, I decided that I simply change the names of readers Archives are identical, and then remove the 'third' drive in the list. With this version of Time Machine, I don't see a button "select disk" or any other way for the list of target readers and remove one of them. The options button allows you to control the volume of the source, not the target volumes.

  Either I have to stop the needless alert or remove a drive in the list.

  Any suggestions?

  Re: community - the only results of a search of a community of Time Machine is under Mountain Lion. Sorry if this is too broad

  After losing all kinds of weather (including a right click on the list of drives for backup and the research in all directions - including multiple searches on google), I discovered that you have right click on the drive icon in the list to use or remove the drive. This follows a different set of rules than the Finder user interface.

• Is time Machine a safe backup

  I use Time Machine to back up files on my iMac.

  Some of these files (credit card info, etc) can be found in a special Folder.dmg that I created with the disk utility application.

  This Folder.dmg is a disk image that is password protected, so whenever I want to access the files in Folder.dmg I have to enter the password that I attributed to him.

  My question is: the Time Machine backup, I create also require this password to access the files in Folder.dmg?

  (In other if someone steals my back upwards, would words, know the Folder.dmg password to access its content?)

  Thank you very much.

  That is right.

• Time Machine backup failure

  I get the message:

  Time Machine could not complete the backup "Backups Time Machine". Full backup impossible. An error occurred during the creation of the backup folder.

  I reboot the system and am able to do the backup.

  Three questions:

  1 is my default backup drive and must be replaced?

  2. If I get a new drive, do I need to do any formatting when connecting it to my system?

  3. is there anything else that would work not to mention that the system restarts?

  Thank you!

  I should add that failures occur about once or twice a week.

• Backups Time Machine very slow on 2015 MacBook Air

  Associated with a topic of discussion between a few days ago (two MacBooks, 10.11.4, a fast Time Machine backup and a very slow), I start a new topic with new information that seem to show it is a problem more general and not related to Time Machine networks.

  Here's the situation:

  • A 2015 MacBook Air, 10.11.4, 8 GB / 512 GB, has extremely slow performance of backup Time Machine, taking 40 hours for the first 300 GB backup and incremental backups for a long time as well
  • TM performance is essentially the same whether on the network (wired Ethernet) or a USB3 external disk
  • When you back up to disk USB3, I confirmed that the information system shows that the port is configured as USB3, not USB2 (nothing else is plugged into the USB port)
  • Tests of bandwidth I/O gross (using dd and iperf) show no problem; the network reached 110 MB/s bandwidth, written network managed at 50 Mbps, external USB3 HD written work at 40-50 MB/s (write hard drive speed limit)
  • 3 other Macs of various ages from 2009-2014 on the same network have no problem at all do backups Time Machine Network; a backup complete first on a 2011 MacBook Pro 500 GB takes 5 hours or more than 10 x faster than the MBA problem
  • Time machine network uses a Linux server running the latest Debian and Netatalk 3.1.8 and the connection is via a USB3/Gigabit adapter, no WiFi, and iperf tests with this arrangement shows 900 MB/s of throughput of the server.  In all cases, the Time Machine and external time Machine Network USB HD have the same symptoms.
  • The problem with MacBook Air is configured the same as the MacBook Pro 2011, which she replaced "daily driver", possible
  • This problem was shown by the MBA since his unboxing conversion, taking 20 hours for his first backup once Setup initially.  Incremental backups now take several hours, leading to interrupted incremental backups and, I believe, databases corrupted backup triggers new full backups that take today the 40 hours.

  Using Terminal Server and iostat, Console, etc, I see that there is significant activity e/s for the backup drive on the order of 20 to 40 MB/s for long periods on the MBA during the TM backup, but during that time the average declared backup size as shown in the window in the console and TM is growing by only 5 GB/hour.  This occur even if the backup will the external drive or a network drive. This seems to mean that the I/O bandwidth to and from the disk hard external, only 1/600 contributes to the progress of the backup.  I am sure that there is overload of certain checks and other tasks, but not to a 600-to-1 ratio.

  I tried to disable the limitation of the I/O of low priority as shown here: http://apple.stackexchange.com/questions/212537/time-machine-ridiculously-slow-a close-el-capitan-upgrade, that helps a bit (maybe 20-30%), but not by a factor of 10 for others.

  I have gone through a number of the Time Machine of Pondini troubleshooting steps, but he found nothing corresponding to these symptoms.

  The only thing I can conclude is that Time Machine, the application or configuration, on this specific MBA, is down. (A single thought that I wrote this to the top that I have not tried: the MBA and the time MBP running VMware Fusion and have a file of 50 + GB VM; on the MBA that is not excluded from TM backups while on the MBP is)

  Does anyone have advice on what to watch next?  In all cases, only one key would be why it seems that only 0.16% of all the bandwidth I/O to the backup drive seems to be actual data backup.

  Once again, three other Macs, all running the same 10.11.4, back to the Time Machine Server perfectly and have for years.  Only this new MBA glue as broken out, either to a network drive or an external hard drive USB3.

  (A single thought that I wrote this to the top that I have not tried: the MBA and the time MBP running VMware Fusion and have a file of 50 + GB VM; on the MBA that is not excluded from TM backups while on the MBP is)

  What happens when you exclude it as the MBP?

• Clone of Time machine backup to a new drive?

  I'm trying to help out a new Mac. Before, I had two back ups of all my data: on the hard drive of my old iMac and my external time machine backup disk. Long story, but during the process of troubleshooting using AppleCare support, my iMac has been cleared. Now, I have only the Time Machine external backup.

  I bought a new drive for Time Machine external backup on my new Mac. I am very very afraid of something bad happens to my old Time Machine backup during the troubleshooting process. My question is, is there a way to clone back to the top of my old drive time machine to the new, so I once more two copies?  If something happens to my old time machine up during this process of troubleshooting, I won't lose all my files.

  I'm not familiar with the Time Machine backups, and even if they need to be cloned since that they are not bootable backups.  The following link is dated but maybe having the relevant documents:

  The restore function of disk utility included in directions of OS X. alarm - http://discussions.apple.com/message/8799711#8799711