![]() Run first aid, sometimes on all disks registered within Disk Utility. Now after every upgrade to Catalina or, if I have unplug my iMac say, to move it as, have decorators in I have to go through this process: I have done this many, many times over many years without problems. In the past I could remove the USB cable from my external drive to utilise the USB on my iMac for something else without un-mounting the external drive and then simply plug it in again and it would carry on from where it left off. I have found, since Catalina, that my TimeMachine back-ups on an external drive have become problematic. I am not sure if what I am going to say is relevant necessarily to yourself, but may be to others. Apple needs to enhance Time Machine to use the most common, efficient, and secure network protocol to backup to a NAS whether that NAS be on a local network or using a VPN connection. With the majority of MacOS products being portable, Apple's Time Machine solution is just not realistically practical. For MacOS we are expected to use Time Machine for backup either to an attached storage device or one connected to a networked Apple product, most of which are out of production. Part of the marketing strategy for Apple is to talk about how secure their products are and how iCloud is used as a backup strategy well except for MacOS products. The MacOS Time Machine app was only designed for an Apple to Apple NAS solution, nothing else, even if the NAS is using AFP. When the NAS is non-Apple the only error recovery is to retry. When an Apple NAS is used as the endpoint the MacOS Time Machine app has a functioning error recovery process. Using Finder on my MacBook, I was able to view the directory structure of the backup for every solution except AirPort Extreme which showed as a "Sparse Disk Image Bundle".Resurrected AirPort Extreme experienced a failure but MacOS app recovered.Raspberry Pi using Netatalk would eventually experience a failure from which MacOS app could not recover.Using Merlin firmware would eventually experience a failure from which MacOS app could not recover.Using ASUS firmware would eventually experience a failure from which MacOS app could not recover. ![]() We all agree that the Time Machine app on MacOS is flawed. In all Mac OS Versions since Mountain Lion. Other Issue with with Macbooks in a WLAN: There is always the case I need to disable and enable the WLAN to get access to the internet. But Mac OS is not a reliable Network Service OS. there was always a network service which didn't worked properly anymore after a Mac OS upgrade. An other option could be, move the Mac Mini Server to the trash and buy a reliable network device:Īnd after an upgrade of the Mac Mini Server to a new Mac OS version, it was always the same story. The Mac Mini Time Machine Server is not working as before. ![]() And now if I map the File Share by AFP, there is no content anymore and the Time Machine on the client does not recognize the mapped AFP drive.I can use the File Share in SMB with the same user credentials Somehow a Network User Password Issue with SMB.Recovered a Macbook Pro and another Mac Mini as a Client from a Backup.Setup Mac Mini Server from Scratch (NOT BACKUP).SMB works as file share system only, but not for the Mac Mini Time Machine Server. ![]() And now not even AFP is working in 10.15.2. And that is the Problem, because in earlier Mac OS versions SMB for Time Machine never worked, only AFP. It never worked with SMB, but always with AFP. Now I cannot anymore use this server as a time Machine Server since the Upgrade to Catalina 10.15.2. I have an old Mac Mini (2012) as a Time Machine and File Server with external USB HDD's in a Docking Station. ![]()
0 Comments
Leave a Reply. |