Skip to main content

MacOS Sierra Time Machine - Preparing backup... forever to Synology

I am using Synology NAS to backup my Mac using Time Machine. After upgrade to MacOS Sierra (10.12.1) Time Machine backup sort of backed up my Mac. By sort of I mean it was showing Preparing backup...  forever but if I entered Time Machine backup all backups even new ones were there.

To resolve the issue with "Preparing backup...":

Time Machine disk selection
  1. I removed backup disk in Time Machine preferences
  2. Removed all Synology Diskstation passwords from KeyChain Access (not only Time Machine ones) 
  3. Deselected Time Machine shared folder from Synology file services menu
  4. Disabled Mac file service (AFP) from Synology Control panel
  5. Dismounted all Synology mounted drives
  6. Enabled SMB 3.0 in Synology File services (Control panel)
  7. Enabled back Mac file service in Synology
  8. Selected Time Machine shared folder under Mac file services in Synology
  9. Opened Time Machine settings and Selected Time Machine disk from the list
  10. Selected Encrypt backup
  11. Entered username and password for Time Machine backup
  12. Entered password for encrypted backup
  13. Selected to Delete old backup (move .sparseBundle to other disk if you want to preserve it)
  14. Started backup

I was checking if Time Machine mounts the folder in Finder and everything was OK. Backup finished "first" backup in around 5 hrs. Now it's working without any problems.


Comments

  1. I followed this exactly and it sadly didn't work for me. My error is:

    The network backup disk could not be accessed because there was a problem with the network username or password. You may need to re-select the backup disk and enter the correct username and password.

    Username and password are confirmed working via Finder. Any suggestions are appreciated.

    ReplyDelete
    Replies
    1. It is crucial that you don't open/mount anything from Diskstation in Finder after you delete credentials in keychain. Time Machine should be the first instance asking you to enter username/password for Diskstation.

      Delete

Post a Comment

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.