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.


Labels:

Comments

  1. KevMNovember 12, 2016 at 9:57 PM

    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. DuĊĦan SoraviaNovember 12, 2016 at 10:16 PM

      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

Netscaler vs Exchange 2019 "time out during ssl handshake stage

If you are using Citrix Netscaler as load balancer in front of Exchange 2019 server you must know this: Microsoft Exchange 2019 is secured by default and allows only TLS 1.2. Therefore default schannel settings are as follows (using IISCrypto tool from Nartac Software): While Citrix Netscaler offers following Cipher Suites: TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_RSA_WITH_DES_CBC_SHA TLS_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 TLS_DHE_DSS_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_RSA_WITH_DES_CBC_SHA TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT1024_WITH_RC2_CBC_56_MD5 TLS_DH_anon_WITH_DES_CBC_SHA TLS_DH_anon_WITH_AES_128_CBC_SHA TLS_DH_anon_WITH_AES_256_CBC_SHA TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA Now, you will fi
1 comment
Read more

Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}]

 If you got this error checking the mail flow for a distribution group, it means the distribution group is closed and only internal senders can send e-mail to this group. When outside user sends e-mail to this group you get  Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}] Set Delivery for this group to internal and external users and your problem will be solved. 
Read more

Ports that need to be open on Firewall for Edge Transport servers

Ports that need to be open on firewall for Edge Server subscription with Hub Server to function properly: For Inbound traffic: SMTP - TCP port 25 (from Internet) SMTP - TCP port 25 (from Edge server to Hub server on internal network) For Outbound traffic: SMTP - TCP/UDP port 25 (from Edge to Internet) SMTP - TCP/UDP port 25 (from Hub to Edge server) LDAP for EdgeSync - TCP port 50389 (from Hub to Edge server) Secure LDAP for EdgeSync - TCP port 50636 (from Hub to Edge server) Since Edge server needs to communicate with Hub server it is important that it can resolve Hub transport servers by FQDN and Hub transport servers must be able to resolve Edge servers by its FQDNs. To accomplish this you need to either open 53 (DNS) port and configure internal network adapter to use internal DNS but as a security precaution I would suggest to enter DNS records for Edge servers on local DNS manually and to fill hosts file on Edge servers with FQDNs for Hub transport servers.
2 comments
Read more