Skip to main content

Restore Time Machine backup from Synology

If you find yourself in a situation where you need to restore your Mac from a Synology NAS, you will find out pretty soon after you enter the recovery mode, that backup disk is not visible in recovery window. Steps need to be executed in order Recovery process to find NAS.

Best practise is to name Time Machine shared folder on Synology without spaces. Second, if you are using a password with spaces, which I strongly suggest from security point of view, always put it between ' ' example: 'This is my password'.

  1. Enter the OS X recovery mode by holding Command +R (when Mac restarts and display is grey)
  2. When window with options is presented, select Utilities from the bar and select Terminal
  3. In Terminal use following commands:
  • Cd /Volumes
  • ls /la
  • Create a folder to mount Synology to by typing mkdir synology
  • Now mount your NAS by entering following command
mount -t afp afp://admin:password@10.10.10.11/TimeMachine synology
Where admin is your username with administrative rights, password is password for that account (use ' ' if you are using spaces) and TimeMachine is the name of your TimeMachine share on your NAS.

After it mounts, check if it is really there

- cd synology
- ls -la

Now you need to mount sparsebundle by using hdid (hard drive image driver)

- hdid nameOfThebundle.sparsebundle

Enter the password if needed (if your drive or backup was encrypted)
Now quit the Terminal and select Restore from Time Machine. Your backup on NAS should be visible now. Just follow the instructions on screen.


Popular posts from this blog

Error "<#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP#" when you send attachment in your mail

Some users were receiving error <#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP# when they sent message with attachment. The problem is when attached document name is longer than 50 characters. Some Firewalls have header size restriction and that limit blocks this messages to be sent. To correct this, change header limit on affected Firewall or shorten the name of the document you are sending (which is probably not good permanent solution).******
Update #1: Default header size limit in Exchange 2007 is 64K.Update #2: It might be the SMTP version problem. Mail is rejected with CONTENT-DISPOSITION error (overly long message header field for CONTENT-DISPOSITION) but not for all SMTP servers (same mail sent through different SMTP servers). If you send mail with attachment that has name longer than 50 characters from Exchange 2007 directly through DNS you may encounter this error, but if you send same mail from Exchange 2007 through smart host (other than Exchange) mail is d…

Change SMTP port 25 in Exchange 2007, 2010

For some reason you might want to change default SMTP port number 25 Exchange 2007 is using. Exchange 2007 uses RECEIVE AND SEND connectors, one for receiving mails and other for sending mails (obviously ;)
So you need to change ports on those connectors. I will not say those two, because you might be using more than two.
You change Receive connector port by opening the connector properties in Exchange Management Console --> Hub Transport --> RECEIVECONNECTORNAME --> Properties --> Network --> Local IP Addresses (Edit Receive Connector Binding)
Just to clarify what "Local IP Addresses" and "Remote Servers" are (from Exchange 2007 help), because I find it little bit confusing: Use these local IP Addresses to receive mail Use this list to specify the IP addresses and port numbers on which this Receive connector listens for incoming mail. Receive mail from remote servers which have these IP addresses Use this list to specify the remote IP address range fr…

The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange setup

You get this error "The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange setup" when you try to install Exchange 2016 on Windows 2016 server. Exchange 2016 pre CU3 does not support Windows 2016, therefore you need to download Exchange 2016 CU3, which is in fact full copy of Exchange 2016 server in order to install it on Windows 2016 machine.