Time Machine completed a verification of your backups. To improve reliability, Time Machine must create a new backup for you.

I have not consulted said website. Thank you for the info. As for your confusions, I may be able to clear a bit of them up.

1) Yes it is definitely a typo of the sort, I have always updated my system when the golden master is released. I am definitely running macOS Sierra.

2) The configurator issue is resolved now, I had previously downloaded configurator in anticipation to assist my wife as she was waiting on approval for new iPads for her classroom. She finally got the funds and Apple had apparently released configurator 2 sometime in between. Those errors were produced as I was trying to use the first edition. It produced the errors and told me to use the new updated version. Since then I have used Configurator 2 to push all of the settings, apps, and restrictions to the laptops for my wife's classroom.

3) Thank you for that information as I was wondering why those crashes were occurring. I am still slightly concerned as I do not have any google software on this machine. I will dig around to see what I find. The only thing I previously recall having on this machine (all has been removed) was google drive and google sketch-up.

TheNgbaka wrote:

I was wondering why those crashes were occurring. I am still slightly concerned as I do not have any google software on this machine.

Safari (and several other browsers) use the Google Safe Browsing database to "Warn when visiting a fraudulent website" when you have that option enabled in Safari Security Preferences.

I encountered this error on my main iMac last month and again today. Never had any problems before. Total Apple products. No 3rd party. Have AirPort Extreme with 2TB storage (Model A1409) that I purchased May 2012. I followed the instructions and did a new backup the first time. Didn't document when I first saw the error but when I look at the TM backups I see November 29, 2016 as probably the first day of new backup. However, going backwards, the backups are missing until August 29, 2016. None from then until November 29. There are additional backups going back to Jan. 2016 but only about one a month. Could this be due to doing the new backup in November?

Something else that is puzzling me. When I open TM and click on a particular day's backup it will say "Waiting" and everything on the left is grayed out and no files are listed. The last backup was 3:30AM today. Why does it say "Waiting"?

By the way, backups on my other iMac are working fine and they weren't affected last month either so it is confined to just this machine. Why?

Really need some insight on this whole issue. I am fairly computer literate but this is a little overwhelming. Any help would be greatly appreciated. If I was having problems backing up my other machine I would lean towards there is a problem with the backup drive and it is probably going to fail soon.

The way Apple handles this is kinda sad.

On http://www.garth.org/archives/2010,07,16,124,fixing-time-machine-sparsebundle-ne twork-backup-errors.html

there is a good article on how to repair the backup package file. It is a article from more than 6 years ago, but it worked for me (Sierra Server Time Machine service). I already lost my 4 year old backup archive once, and now it happened again just 2 weeks later.

Offering that Time Machine must create a new backup, is the easy way out for Apple, and it doesn't show much respect for the value of the data of their customers.

The backup package is getting corrupted.

More these days than before. There is nothing more to it.

The Time Machine program code does not handle disconnects well, or crashes more then before, leading to incomplete disk writes and therefore corrupted archives.

If Apple thinks that their customer are not technically savvy enough to fix things themselves, they should try to automatically fix the corrupted archive first (in essence just an fschk command), and not give this "improve reliability - make new backup?" misleading message, which actually destroys the complete backup archive without the user realising that he or she is giving the order.

I'm considering switching to backup software that works more reliably.

I'm 100% behind the idea of a simple user interface for backup software, but that doesn't mean that the software shouldn't be sofisticated, something I am not used to from Apple. The times they are a changing…

Until today when its doing exactly the same thing. Bit annoyed now as I probably didn't need to purchase the new time capsule.

I received this error from 1 month ago (DEC16) to today in 5 times.

Apple, is there any solution?

I solved my problem and went to a 3rd party external drive and using it with Time Machine. Working great now. Took me a while to get the new drive to work but persevered and figured it out.

Seriously, Apple will not solve this problem with an update? Very bad Apple. Very sad.

cisco111 wrote:

Seriously, Apple will not solve this problem with an update? Very bad Apple. Very sad.

Is that a question?

It is a question for Apple or for the world.

I upgraded to Sierra some time ago, turned Time Machine on at the same time. It worked (and still works) correctly. You have a local issue to deal with.

Then settle for leaving it as it is.

I have the same problem, it's the third time it happens to me, there is another mac in the network that doesn't have this problem... I don't understand what's going on...

I've been trying it but the system won't allow the sudo command to work. I get "sudo: unable to stat /etc/sudoers: Permission denied".

What a pain.

I continue to have no problems after a clean re-install of the OS, leaving off Clam-X