SQL attachability check fails due to the timeout period elapsed prior to completion of the operation or the server is not responding error.
ERROR 2016-07-18T05:17:24  - Replay.Core.Implementation.Sql.AgentAttachabilityJob ()
Job 'Performing the attachability check on Maul' failed
...Microsoft.SqlServer.Management.Common.ExecutionFailureException depth 3: An exception occurred while executing a Transact-SQL statement or batch. (0x80131501) ---> System.Data.SqlClient.SqlException depth 4: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (0x80131904) ---> System.ComponentModel.Win32Exception depth 5: The wait operation timed out
Heavy load on the core machine during nightly jobs, result attachability is failing by timeouts.
Windows Registry Disclaimer:
Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.
Extend the Attachability check Execution and Connection timeout values as below;
If issue have not resolved, kindly log a case with AppAssure/Rapid Recovery support.