Normal file backup and SQL backup works fine to the deduplication folder. It's only GRT that throws these errors (Active Directory and Exchange 2007 SP2). Got my Backup Exec 2010 with all availble patches running on a Windows Server 2008 SP2 x64 with 8 GBs of RAM and about 2,5 TB deduplication data (ISCSI). And yes, you do want to back up system files necessary for a full reinstall. If you try those directions and get a “We can’t create a recovery drive” error, try these solutions.
Why I Don’t Rely on Time Machine In I say quite a lot about Time Machine, the backup app built into OS X. On the plus side, Time Machine is incredibly easy to use—and it’s officially supported by Apple. (It’s also the best way to restore individual contacts and email messages in Contacts and Mail, respectively.) Lots of people use Time Machine because it requires essentially no thought or preparation. You can plug in a properly formatted external drive, click one button, and get a full backup of your Mac, updated automatically every hour. I used to be a big Time Machine fan, because anything that makes backups easier greatly increases the likelihood that people will use it. But not so much anymore. In fact, I still use Time Machine, but not exclusively.
I don’t depend on it anymore, and I’d like to give just two recent examples to illustrate why. A couple of weeks ago, not long before my new book was published, Time Machine displayed the following helpful error message on my Mac: “Time Machine couldn’t complete the backup to ‘Backup Drive’.
Unable to compete backup. An error occurred while creating the backup folder.” Huh. The Time Machine preference pane suggested that I try again later, and I did, with the same result. Since there was an error creating a folder, I guessed that the disk might have some errors, so I ran Disk Utility. Sure enough, there were errors, but Disk Utility couldn’t fix them. Neither could DiskWarrior. Or TechTool Pro.
So I was left with no choice but to reformat the disk and start over from scratch. I still don’t know what caused the problem, but neither Time Machine nor any disk utility I tried could fix it—and the hardware itself was, as far as I could tell, just fine. When my backups become suddenly inaccessible for unknown reasons and I’m offered no solution but starting over, that sort of diminishes my faith in the software. Then yesterday, Morgen’s laptop, which backs up to a completely different destination (a Time Capsule), displayed yet another error message: “Time Machine completed a verification of your backups on ‘Zora’.
To improve reliability, Time Machine must create a new backup for you. Click Start New Backup to create a new backup. This will remove your existing backup history. This could take several hours. Click Back Up Later to be reminded tomorrow. Time Machine won’t perform backups during this time.” Huh.
So, different message, but the same end result. Time Machine was informing her that, effective right now, her Mac would stop backing up and if she wanted it to continue, her only choice was to start over from scratch. Now, for us, all of this was a minor irritation, because Time Machine isn’t the only software we use for backups. We also use CrashPlan (see ) and Carbon Copy Cloner, not to mention not-quite-backup cloud services such as Dropbox. So we could wipe and restart our Time Machine backups without worrying that we’d lose any crucial data—there are plenty of other copies.
But if Time Machine had been our only backup solution, we would have been in a pickle. So, word to the wise: use Time Machine if you like, but if you do, make sure you have other backups too. Until Apple makes some serious progress on Time Machine reliability and transparency, it’s not worthy of your trust. Joe Kissell. June 9, 2015.
I bought a Western Digital Passport external hard drive and I'm using Time Machine to back up my computer. After one successful backup, I keep getting the following message: Unable to complete backup. An error occurred while creating the backup folder.
If I eject the backup disk, unplug it and plug it back in, then I can back up without this error. I'm also using TimeMachine Editor to schedule the backup at midnight every night. That's when the error occurs.
Any manual attempt to run a backup after this fails. I have a MacOS running High Sierra version 10.13.6. I suggest that you try to narrow down the possibilities to try to isolate the real cause of the problem. If you want to try this.disable Time Machine Editor.
It used to be that you had to uninstall the application to fully disable it, but I'm not sure about the current or more recent versions. I do notice that there was an update in July, which may or may not be a factor here as well. If you are running High Sierra (10.13.x) on your Mac.that may be a factor as well.because of increased security. Once Time Machine Editor is disabled, go ahead and let Time Machine operate normally for a day or two. Do things operate normally that way? If they do, then try enabling Time Machine Editor again. If things are still messing up.you know that you have a Time Machine Editor issue with the TME software.
Best to post on the Time Machine Editor support forum in that case. I'm having this same error message, also with a WD external drive connected to my 2018 MacBook Pro via a CalDigit Thunderbolt 3 hub, MacOS 10.13.6.
First 5 backups went fine, then got the error message about not being able to create a backup folder. After that, I was not able to manually start the backup either. I am not using Time Machine Editor, though - just letting backups occur at the default interval.
I just ejected and remounted the drive, and now Time Machine is running. Hope I don't need to do this every day! Any suggestions welcome! If I eject the backup disk, unplug it and plug it back in, then I can back up without this error.
I just ejected and remounted the drive, and now Time Machine is running. Hope I don't need to do this every day! Any suggestions welcome! It sounds like you both have the same or at least similar issue. Is your USB drive plugged directly into your Mac or is it in a hub of some sort?
What happens is the drive spins down and does not get a spin up again. When you eject the drive and plug it back in the drive goes through its start up sequence and will become active again.
Some drives seem prone to this. WD passport does seem to be one of those. Put your hand on the drive and feel if it is spinning. Or some drives you can hear them.
Very softly when they are spinning. Well, the problem came back again yesterday. I poked around the WD support forums and found this post: tl;dr: Several people seeing this exact problem with various WD drives and Time Machine, in a variety of configurations.
A user claims to have tracked this down to the WD driver / helper utility not being compatible with Sierra and High Sierra. Removing this driver fixed the problem for more than one user.
Run the Uninstall utility in Applications. Remove /Library/LaunchDaemons/com.wdc.WDPrivilegedHelper.plist. In System Preferences Users and Groups Login Items, remove WDDriveUtilityHelper I've tried this just now and restarted my laptop. Will try to remember to report back in a few days if it fixed the problem! Interesting that it's been since Lion:-( When I initially plugged in the WD drive, I couldn't mount it, erase it using Disk Utility or set it as a Time Machine backup, though the drive showed up in on the USB chain in system information and was visible in Disk Utility. So I installed the WD utility and used it to check the drive was ok and to erase it and format it as HFS-J.
Once I did that, I could mount the drive and use it for Time Machine. So I did need the WD utility initially to get going, though it appears it messes things up in the long run. After deleting WD utility, I no longer get the Time Machine errors. Apple Footer. This site contains user submitted content, comments and opinions and is for informational purposes only.
Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the.