![Synology nas time machine](https://kumkoniak.com/60.jpg)
The migration assistant found my NAS, I was able to connect to it and see the backups but at the same time I got the following message: “No volumes found in backup”.
![synology nas time machine synology nas time machine](https://sflanders.net/wp-content/uploads/2015/10/synology-user-tm2.png)
As I make use of Time Machine for making encrypted backups on my Synology NAS I thought it would be a great opportunity to actually test my backups as a non tested backup is no backup at all ( Schrodinger’s backup).ĭuring the initial setup of my new Macbook however, I ran into a problem.
![synology nas time machine synology nas time machine](https://www.ceskymac.cz/wp-content/uploads/2020/11/synology_nastaveni_time_machine_005-600x527@2x.jpg)
I don't think there's any particular "right" and "wrong" way to go about it, it's a value judgement more than anything.I recently replaced my Macbook Pro (early 2015) with a newer model. Again, "in busniness" when we use quotas, it tends to be on a user by user basis (not least because some need more than others) and often it's set at the volume rather than the folder level, but the basic idea is the same. Setting quota by user means "others" could write to the target folder unimpeded. Setting quota at the folder level means anyone can use anything to write to the target folder and it all "counts" towards folder quota and once it's gone it's gone. Since most SOHO users run completely open unsecure systems without using credentials, the point is moot. We might also configure them so we can restrict those accounts to (for example) only access certain machines, can only be used certain times of day, never have any Internet access, and so on.
![synology nas time machine synology nas time machine](https://community.synology.com/images/picture/1280x1280/282/1562575231_MeYG2.png)
![synology nas time machine synology nas time machine](https://sflanders.net/wp-content/uploads/2015/11/synology.png)
If you were using an infrastructure where you used credentials, ie everyone has their own loginid and password - using a dedicated account for backup means that you are not using the identity of a flesh and blood "person" to perform service tasks - and if you change the password of that person, you don't have to "remember" to go update the backup process to reflect the changes (otherwise your backup stops working and you wouldn't know if you aren't checking the logs.) In business, we use "service" accounts all the time.
![Synology nas time machine](https://kumkoniak.com/60.jpg)