![]() You can restore from a Time machine backup without or after installing an operating system. When the backup is completed, the hard drive will NOT be bootable, meaning that you can’t run macOS from your Time machine backup. The backup includes docker files, npm packages, your personal files etc. I’ve also noticed that when restoring from a backup you will need to sign in to App Store and iCloud again and Chrome extensions need to be re-installed. The rest of the exclusions are for system things like caches and databases that exist to index other files where the system can regenerate these databases after a restore. Some of the more obvious user file exclusions are Trash, Document revisions and MobileBackups from the local Time Machine store are all excluded. It excludes log files, Spotlight indexes, caches, temporary files and trash (have a look: On OS X, what files are excluded by rule from a Time Machine backup?). Time Machine by default backs up nearly everything in your macOS partition. Backing up your devices to NAS using Time Machine No performance penalty from the second redundant drive and you still have protection the trade-off is you get a big performance penalty when the hot spare is activated (while it rebuilds) and there’s still a risk of the array failing if a second drive fails while the array is rebuilding. You may consider setting it up with SHR1 and a hot spare. No penalty from simultaneous use as long as each use is on a different volume. ![]() One drive needs to fail before there is a risk of data loss.Slight performance penalty in situations where there is significant use from two sources.Two drives need to fail before there is a risk of data loss.The only advantage you would gain would be less loss of data if an array fails, but at the cost of a higher risk of array failure. Let’s take an example a NAS with 4 x 6TBb drives. The advantage to creating multiple volumes comes when you are using different size drives, want different levels of redundancy, or have significantly different uses. That being said, in this case you want to just make one, and then create shares to logically organize things. You can use the Synology RAID calculator to help determine how you want to set up volumes. It's from this computer you decide when to perform the backups (as long as the other Mac is power on of course!) and how it's done (which files to back up etc.).It’s important that before you start you understand the concept of volumes on Synology Diskstations, because that’s the first thing you will need to set up before you set up Time Machine backups. Then, on the Mac with the backup drive attached (in my case I have a USB-dock for removing/inserting standard 3.5" SATA drives) you have to have Chronosync installed. I don't think I messed around with the other options. As far as I remember I didn't do much apart from assigning a username/password (for allowing access). Using its System Preference you can configure various options. The ChronoAgent software is installed on the Mac which needs to be backed up. Here's a quick summary on how this all works: It looks to work very well now, and I think this has been a great investment.Īctually I bought a second ChronoAgent license after the first one as I want to back up another Mac the same way (one license covers one Mac, but if you have many you can buy a 5-license pack and save some money if you need that many, as far as I can remember). It's been working very well, but with some minor mistakes underway which I believe have now been fixed (no fault of Chronosync/ChronoAgent, but my experience with Chronosync is that it has so many options that you need to go through several backups and do adjustments to its settings). Thanks to your explanation I got a general understanding of how it all worked and was able to try it out even without reading the manual. A little update (after having used it for several weeks): ![]()
0 Comments
Leave a Reply. |