Now I know where to get working.How to setup a Synology NAS Part 12: Connecting to a Shared Folder via MacOS Time Machine Backups with a Synology Diskstation Map a Network Drive in OS X (Mac) Permanently How to setup a Synology NAS Part 27: Installing and Configuring Media Server Getting Started With Synology Synology NAS Setup Guide Part 2 - Users, Groups and App Installation ★ Inbetriebnahme Synology ▷ Installation & Einrichtung der Synology DS218+ (DSM 6.2x) Map a network drive on Mac (OSX) How to setup a Synology NAS Part 17: Reviewing Storage Manager Back to the Mac 009: Synology NAS Time Machine backups! Installing Synology Drive Client on a Mac Synology DS220J NAS - The Best Way to Store & Backup your Data - I'm Switching! Mapping a network drive for MacOS Connect Finder Mac to Synology using SMB | 4K TUTORIAL NAS 101 | The Ultimate Guide to Network Attached Storage How to Sync a Synology NAS with DropBox, Google Drive and OneDrive with Hyper Backup Creating a Windows 10 Virtual Machine on Synology DS918+ How to setup a Synology NAS Part 13: Connecting to a Shared Folder From Windows 10 Synology NAS im Apple Umfeld - Webinar DSM 6. This means something has screwed up in my normal account - it must be something within the Time Machine configuration or database. The process started normally and got stuck at 107,000 documents or so. So when I got my new MBPRO 16 I thopught it would be safe to use Target Disk Mode and Migration Assistant to transfer my data.
So I did make a new admin account and tried to run Time Machine to the same Synology volume as my failed regular account. I have 3 TimeMachine NAS backups of my MacBook Pro, each one in a different location, two on a Synology NAS and one on a Time Capsule. Maybe a database got corrupted or something. I didn't want to do this but I guess I'll have to poke around using the command line TM utility "tmutili". On the new Parallels backup that SID was updated to the proper machine name once the TM backup got started. It's funny but when I look at the volume rather than the sparsebundle having the name of my machine as would be normal it has a long SID looking value. I'm guessing maybe TM itself has screwed up someplace. So obviously there's something wrong on my MBP Sierra setup causing it to fail. Same domain account I used for my main TM backup to the exact same volume. It was suggested to me that High Sierra may have killed my ability to use AFP because the plan is to depreciate AFP shortly. One day, for no apparent reason, it quit working. I've had TM backing up to a Synology shared folder for about a year. I run High Sierra 10.3.2 beta 2 on Parallels so just for fun I thought I'd see how it would backup via Time Machine to the same Synology server Time Machine service as I was using above that wasn't working. Time Machine backups broke with no apparent cause and will not resume. This leads me to think there's something going on in my installation but I can't figure it out. It's only me.Īnother clue is that when I try to connect to my regular shared folders from my MBP it takes about 5 or 6 seconds to make the connection whereas my colleague connects almost instantaneously. I've noticed also that periodically (perhaps after updates and rebooting) that the Time Machine checkbox for the volume in File Services becomes unchecked.Įven stranger is that my colleague (who I set up for Time Machine) is going merrily along with their TM Backup in the same volume so I know the Synology services are working properly. Then Time Machine backups would spend around 24 hours 'preparing backup' with the backupd taking around 98 CPU. Both we working without problem prior to the upgrade. Mid 2010 iMac 27' and a 2015 MacBook Pro. Time Machine itself is working because I have dual location backup and my local backups are working. MacOS Sierra breaks Time Machine on ReadyNAS So just updated two systems to MacOS Sierra. I'm on Sierra also and was always using SMB. I have not yet had any resolution to the problem.
0 kommentar(er)
