![]() How could you when it would take days for them to back to you? The tech support guy clearly said his goal was to show me that the problem was my hardware. You could NEVER use this utility for any kind of production, no matter how small. Fine, but via email support was far worse and slow. When I tried to talk with tech support, that was impossible, and they used Covid as an excuse. Then when SoftRaid 6 came out, which is required for Big Sur, they charged me $50 for an upgrade.Įven worse, when I got it, configured my Raid, my performance was in the 300 Mb range (Read and Write) for three SSDs. I had not received the shipment and I had not opened it. They had shipped, but I asked them to return the product. I purchased with SoftRaid 5.8.4 and SoftRaid 6 was in beta. I would just like to know why Big Sur was spitting out 2 sets of user credentials for each attempted logon to the NAS.The product is slow. That is what seemed to do the trick for me. So, in short, have only a single dedicated user in DSM with privileges to your TimeMachine folder, unselect the drive in Time Machine and then reselect it using that dedicated user's credentials. I think I may have figured out what is going on here, although I can't understand the why. After sending Synology the debug.dat in response to the Support Ticket I started I began examining the Connections log in DSM. I noted that each time one of my Big Sur systems tried to access the NAS from TimeMachine there were 2 user connection entries nearly simultaneously - the user I had designated in Time Machine, and another user I had previously designated - both with privileges for that backup shared folder. I went back into DSM and eliminated all those user privileges to that shared folder except the general admin user. I then went back into the Big Sur Time Machine and deselected and reselected the appropriate NAS, entered the general admin user credentials and then initiated a Time Machine backup. I'm just not going to risk that machine to some fatal bug that totally borks a 24tb array. I have a Mac I use as an Apple Music/TV/Plex server that relies on a 24tb SoftRAID RAID5 array that I cannot transition to Big Sur until SoftRAID is able to release an update (they claim their updated driver is built into the Big Sur release, but users are reporting issues and the client is beta and will be for some time). Everyone knows the 11.0.1 release was rushed to coincide with the M1 Macs show, and may not still be ready for primetime. It won't surprise me in the least if this is addressed in an 11.1 release. ![]() I suspect there is a bug lurking in Big Sur regarding Apple's choice of APFS Time Machine backups that causes it to not play well with NAS devices, or in particular Synology NAS devices. I have no explanation or even speculation as to why that was happening. For example, I noted that when my backups failed I would have two (2) users that had privileges to that shared folder attempt to connect nearly simultaneously from the same Mac even though I had only supplied one user credentials when selecting the share in Time Machine setup. ![]() Check if when a Time Machine backup initiates whether you have more than one user attempting the connection. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |