This is the second time after upgrading to High Sierra, that my current time machine backup was no longer recognised. The first time I just started a new time machine backup and deleted the old files on my Air Port Time Capsule, as I thought that over the years it had grown too much any way.
But this time, everything was started under High Sierra without legacy stuff. Nevertheless, after the last upgrade to 10.13.3 I was informed that the Air Port had changed its identity (or something like this), and if I want to use it anyway. I confirmed with "Yes", but noted that no previous time machine backup was available. The same symptoms as the first time this happened.
I again deleted the old files and started a new time machine backup that finished hours later. I guess its time to move on to another system such as CCC. Am I the only one with this problem? It never happened before and was using time machine for years.
This is on a MacBook Pro 15" 2015 without dGPU. I started with El Capitan, upgraded to Sierra last year and recently to High Sierra, but without conversion to the APFS file system (using a command line command for the upgrade), because I still want to have access to HFS+ from Windows.
But this time, everything was started under High Sierra without legacy stuff. Nevertheless, after the last upgrade to 10.13.3 I was informed that the Air Port had changed its identity (or something like this), and if I want to use it anyway. I confirmed with "Yes", but noted that no previous time machine backup was available. The same symptoms as the first time this happened.
I again deleted the old files and started a new time machine backup that finished hours later. I guess its time to move on to another system such as CCC. Am I the only one with this problem? It never happened before and was using time machine for years.
This is on a MacBook Pro 15" 2015 without dGPU. I started with El Capitan, upgraded to Sierra last year and recently to High Sierra, but without conversion to the APFS file system (using a command line command for the upgrade), because I still want to have access to HFS+ from Windows.
