question

Hi Experts, In our production Servers, Few databases in Primary server failover to Secondary database. ex:10 databases in primary, 5 will be principal synchronized status,remaining 5 will be mirror synchronized state We failback manually in from Secondary server. in that server we are installing another instance for Witness also. We want to know how to avoid this situation in future? Anyother method for resolving issues permanently Mirroring timeout setting we changed to 60. sql server Version: Microsoft SQL Server 2005 - 9.00.5057.00 (X64) Mar 25 2011 13:33:31 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.0 (Build 6002: Service Pack 2) error logs: Message Database mirroring connection error 2 'Connection attempt failed with error: '10060(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)'.' for 'TCP://HZNTPMPDBME002.xxx:5090'. Message Database mirroring connection error 4 'An error occurred while receiving data: '64(The specified network name is no longer available.)'.' for 'TCP://HZNTPMPDBME002.xxxx:5090'. The mirroring connection to "TCP://HZNTPMPDBE002xxx:5089" has timed out for database "WSS_Search" after 60 seconds without a response. Check the service and network connections.