Snapshot Replication on Synology delivers fast, reliable data protection by creating schedulable, near-instantaneous backups of your critical business data. It safeguards shared folders and virtual machines stored on LUNs. This ensures your data remains secure, consistent, and readily available in the event of hardware failure, accidental deletion, ransomware, or disaster. In this article, we shall discuss “Inbound connection Error: Failed to Perform Scheduled Replication”. Please, see how to license Veeam Enterprise Manager and Add VBR Servers, and how to fix Failed to create scheduled task due to Windows Server.
With Snapshot Replication, you create point-in-time copies of shared folders and LUNs and replicate them to another Synology NAS. This process preserves data integrity while minimizing downtime, allowing you to restore individual files, entire folders, or full LUNs quickly and efficiently.
By automating snapshots and replication schedules, you maintain continuous protection without interrupting daily operations.
Also, see How to Create a Snapshot on vSphere Web Client, how to uninstall Veeam Backup and Replication from your server, and “how to create Synology Snapshot Replication”
Why was the error “The Replication Task Failed to Perform Scheduled Replication”?
In the past, we had a different issue and here is how we solved it how to fix Task failed to perform Scheduled Snapshot Replication [Part 1]. For this specific error below, it was due to Synology credential change. As such, the replication could not succeed.
More specifically, when the password on the target NAS changes. The source NAS continues to authenticate using the previously stored credentials configured in DSM’s Snapshot Replication task.
Because the stored password no longer matches the updated credentials on the target DSM, authentication fails immediately when the scheduled replication job initiates. As a result, the replication task cannot establish a secure connection and terminates with an authentication error as shown in the email notifcation below and from the snapshot replication job..
As you can see also from the Replication tab of Synology Snapshot Replication. We can see “Permission error for inbound connection”.
Please, see “Mitigating ‘PrintNightmare’ Vulnerability: Print Spooler Solutions, How to create and configure a Shared Folder on Windows Server, and Unable to Ping an EC2 Instance.
Fix Permission error for inbound connection
To fix this issues, please navigate to the Snapshot Replication console and click on Replication. Select the Task and click on Edit under Actions as shown below.
Click on Authenticate
You will be requested to enter your new password via any of the options below. I will choose the “Password login” in this case.
I will enter the new password and click on Submit.
When prompted, enter the 6 digit code and will click on Submit again.
As you can see, we have correctly entered our new credential for this specific replication task. I will click ok Ok to complete it.
As you can see, the replication is in progress and will completed successfully very shortly.
Please, see How to upgrade Windows Admin Center from v2411 to v2511, how to Deploy Veeam Recovery Orchestrator and Agents to VBR and VEM, and How to link an iPhone with Windows PC with Phone Link App.
Using the browser login for New Credential
This process is similar to the password login. But in this method, you will be redirected our of the Snapshot Replication console t a new browser window. You will be prompted to authenticate by entering your new password.
Upon completing the login via the browser login, you can start the replication as shown below. As you can see already, the first replication job we initiated has completed successfully.
The image below confirms the credential fix worked and the replication is now running successfully. “Replication in Progress” with the progress dialog open, showing real-time transfer from Source Server to the destination source server.
Below is the Topology tab of the replication task. It confirms everything is configured correctly and operational post-credential fix
As you can see now, the notifications are no longer failing as well.
I hope you found this article on “Inbound connection Error: Failed to Perform Scheduled Replication” very useful. Please, feel free to leave a comment below.
