Code: Select all
20-01-2015 01:27:32:649 24492ms [ 7] ERROR Log - Module : Accounts Operation : Provider :: FetchTransactionTypeTemplateForMobil Sys. Gen. Message : The connection was not closed. The connection's current state is connecting. at System.Data.ProviderBase.DbConnectionBusy.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at vendor.DataComponentsProvider.MSSQL.DataComponentsProvider.get_Conn() at vendor.DataComponentsProvider.MSSQL.DataComponentsProvider.AccountsTransactionTypesForMobile() App. Gen. Message : Exception raised while trying to Fetch Accounts Transaction Type Template for Mobile 20-01-2015 01:28:43:255 95097ms [ 16] ERROR Log - Sys. Gen. Message : The request channel timed out while waiting for a reply after 00:00:59.9844000. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
Short of buying enterprise SQL and clustering them and using two front ends behind a load balanancer, and backing up each pair in different jobs/times... is there any way to mitigate the intense performance hit when snapshots are consolidated?
The environment is EMC VNX5200 storage array, NFS, 10gbe 9000 mtu, brocade turbo iron 24x switches and QLogic adapters. Each filesystem is on its own subnet with its own vmkernel. 6 hosts each. The backup is on 1gig ethernet, but the vmdk's are on the 10gig (isolated) VNX5200. ESXi 5.0.0, 2312428, Veeam 22.214.171.1247 on a Server 2012 R2 virtual machine in the same environment as production virtual machines.