![]() Time Machine backups are now even slower than usual. You don't notice it at first but as the drive fills up you soon realize that APFS is much slower than HFS on HDDs. Time Machine is now slow as molasses because it requires APFS on HDDs, which negates the speed advantage of running SoftRAID 5 entirely. TIME MACHINE REQUIRES APFS on HDDs - SLOW I don't need backups to be bootable for emergencies because Apple no longer allows booting from SoftRAID anymore, and I already have the CCC clone I mentioned. But now I might need to use CCC or ChronoSync or something else you recommend to replace the functionality of Time Machine entirely, as closely as possible, faster. I'm using Time Machine to backup my first SoftRAID unit holding my Work and Media volumes on my SoftRAID HDDs, as well backup my my internal SSD (data only, for more reliable versioning over CCC). I use it to make a bootable clone (with SafetyNet) of my startup SSD, on an external USB 3 SSD. I've owned and loved Carbon Copy Cloner forever. The SoftRAID developer has helped me a ton with this but there is no known fix so he recommended giving up on TM, so here we are. Those downloads and Plex files are on my Media volume and when TM tries to back them up while they're being used it causes restarts with no real evidence of crashes in Console - it's driving me nuts. I keep experiencing restarts when TM backs up while I'm concurrently downloading torrents with qBittorrent and/or viewing movies via Plex on my living room TV connected through wired ethernet. Time Machine has worked well for me since day 1 but over the last couple years it's not reliable and I need a better solution. I have a late 2015 27" iMac with an internal SSD, two ThunderBay 4 running SoftRAID 5 populated with 4 - 3TB HDDs (HFS format for Media and Work volumes) and 4 - 4TB HDDs (APFS format for Time Machine), respectively. I'm just curious if anyone has ever found a way to recover other than simply trashing the smartbundle and starting a fresh backup.TLDR: I can no longer trust Time Machine and need a recommendation for a replacement that does the exact same thing scheduled incremental backups of multiple volumes that keep as many older daily, weekly and monthly versions as the volume can hold, with automatic pruning, simple browsing of older versions, and easy restoring of single files or entire volumes. I know there have numerous cases where users have found Time Machine backups over a network can fail. I've been using Time Machine for backups for many years, formerly to a Time Capsule that I retired two and a half years ago repalced by my Synology NAS which Ialso use as a media streamer. I am now starting a brand new full backup from scratch, luckily I don't have much on the Air's SSD so the progress bar shows it will take another three hours. I restarted the Air, restarted the NAS and still nothing. I manually mounted the folder to the desktpop, this often clears such errors. Time Machine continued to claim it could not connect to the disk. I also checked the NAS system log and it noted a "system event" five days ago which would be after the last successful backup to the NAS. The other machines show recent backups completed. I noticed in the folder on my NAS where all three of the Macs in the house (my Air, my wife's Air and my iMac) store the sparsebundles that there was a sprasebundle dated for my Air and a second one dated in the folder's recycle subfolder. Backups to an external drive over USB have been working fine. ![]() On my new MB Air (bought just before Christmas) I got a message saying that it had been unable to backup to my NAS for over 10 days because it could not connect to the disk. Please allow us to turn on or off autosave.Ĭorrupted Time machine smartbundles I've run into this problem a few times in the past and it just happened again. So now I have to duplicate to local drive then copy back to server. "ask to keep changes when closing documents" is not a fix. (I seriously detest auto save in specific instances like when quickly raiding a file for content). Open the duplicate copy of that file in this location from the NAS on the M1 mini – boom errors.Ĭan't even turn off auto save to fix the error. Opened a pages file yesterday on older iMac machine running os from 3 or 4 versions back on another synchronised NAS, no problem. Saving it onto a local drive (M1 mini Big Sur) the file works fine. The numbers file was opened from a template file and saved onto the Nas. ![]() Im working at three in the morning alone. The file has been changed by another application. The document “insert document name.pages” could not be autosaved. Apple Pages and Numbers both throwing these persistent errors. Document could not be autosaved (Synology NAS / SMB Mounted Volume) Driving me bats. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |