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

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

Exchange Admin Center language

Depending on your computer language settings, Exchange Admin Center can take those and open in a language you actually don't want to use. You'll Google that this can be changed if administrator/ admin user has mailbox by openening OWA settings and changing Regional parameters. But usually Admin user does not have mailbox or you don't want her/him to have it. You will search again and find that you can add mkt=en-US (as an example) to the URL of the Exchange Admin Center (https://yourexchangehostname/ecp?ExchClientVer=15&mkt=en-US) Third option you have is opening Internet Explorer settings (I am using Windows 2016) Click languages Click Set Language Preferences Add language you want to use by clicking Add language Use Move up or Move Down options to put desired language on top Close Internet Explorer Open it again and login again to Exchange Admin Center

Free/Busy missing - Cloud to On-Premises

We had a problem where M365 users could not retreive Free/Busy information from on-premise Exchange server. Hybrid setup was run and everything was working fine except this. After research I found out that TargetSharingEpr is the way to look at. There are many sites out there that are pointing to the same setting but only Set-OrganizationRelationship is used to change the value. The problem is, this value is available for two commands: Set-IntraOrganizationConnector Set-OrganizationRelationship While we changed the value in  Set-OrganizationRelationship it didn't work until we changed the value in  Set-IntraOrganizationConnector too. By default it should work with just  TargetAutodiscoverEpr but for us it didn't. Finally we ran this command on Intra Organization Connector which is used from Cloud to On-prem:  Set-IntraOrganizationConnector -TargetSharingEpr   https://mail.domain.com/ews/exchange.asmx And it worked.