![]() Apart from Time machine I didn't have any need for that anyway. On the plus side: I can get rid of all the AFP stuff on my FreeNAS now. I do have other means of backup including cloned drives which the Macs allow to boot from and get back up and running in seconds. ![]() I'm using it because it's there and it is a convenient way to get older versions of files back. So losing a backup history is not a real threat to me. Time machine is not a real backup for me. I guess I will be switching back to using this one. I still have a Time Capsule here which is more convenient than using an external drive IMO. Is this a problem for anyone else here and is there a known solution or workaround? (I can deal with the problem however it is definitely not production ready for migrating my wife's time machine backup to the FreeNAS server. However restarting the afp service as well as increasing the maximum number of connections (as mentioned in the bug description) do not solve the problem. In the bug database I came across this issue: Needless to say that I didn't change any configuration neither on the Mac nor on FreeNAS, for example in regard to user names or passwords.Īfter a retry most of the time the backup can be completed without problems. In this case I can see this in the Konsole:Ģ0151228 14:13:09,307 : NAConnectToServerSync failed with error: 80 for url: afp:// 14:13:09,307 : Authentication error (80) - the correct user or password info may not exist in the System.keychain or the server may no longer allow access for this user. ![]() Is this a common problem? When my Mac starts a time machine backup from time to time this just fails.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |