Voltar
-
Título
Retention Job Times out in Archive Manager 5.x -
Descrição
Retention jobs do not complete and the RPS.wlog shows a timeout error similar to the following:
2015-02-28 02:00:04,318 [349] INFO BL.RRun - Retention Run 32: applying policy 4 'Legal Hold'2015-02-28 02:40:05,033 [349] ERROR Configuration.AfterMailServiceBase - {{3169ef67-d24e-47be-a0b8-7de7394220da}} Error performing service dutiesSystem.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()at System.Data.SqlClient.SqlDataReader.get_MetaData()at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)at System.Data.SqlClient.SqlCommand.ExecuteScalar()at Dell.AM.BusinessLayer.RetentionPolicy2.Apply(Int32 retentionRunPolicyID, IRetentionPolicySupport support, RRPolicyStats stats)at Dell.AM.BusinessLayer.RetentionRun.ApplyPolicy(RetentionRunPolicy policy, IRetentionPolicySupport support, RRPolicyStats stats)at Dell.AM.BusinessLayer.RetentionRun.ApplyPolicies(IRetentionPolicySupport support, RRPolicyStats stats, Int32 maxCount)at Dell.AM.BusinessLayer.RetentionRun.Advance(Int32 maxCount, Int32 threadCount, Boolean& done, IRetentionPolicySupport support)at Dell.AM.Service.RetentionPolicyService.MessageRetentionPolicyService.PerformProcessing()at Dell.AM.Configuration.AfterMailServiceBase.OnProcessTimer(Object state)2015-02-28 02:40:16,000 [349] INFO BL.RRun - Retention Run 32: applying policy 4 'Legal Hold' -
Causa
The default SQL timeout for retention in v5.x is 10 minutes and is not enough time for some retention policies. The same policy will be retried and, normally, will timeout again creating a loop.
Adding CommandTimeout and RetentionTimeoutSec values do not have an affect in the new retention system.
-
Resolução
Open the Configuration Console and add the following item in the Advanced section:
RetentionEngineSQLQueryTimeoutMsec
Give it a value of "2400000" (without the quotes). Click Apply and restart the Retention Service. If you still get a time out we will need to try a larger value.
If this does not resolve the issue, adjust your policy so that fewer messages are being processed in one policy.
For example, set the policy to delete the messages in 1 year steps, starting with the oldest messages then increase this range until you reach the desired time frame.
This will reduce the workload of the Retention Service, reducing the likelihood of time-outs when searching.
Once the policy has time to process all the items, then check how much space is used.
After the solution was successfully implemented, similar messages could be seen in the RPS.wlog:
2015-04-30 06:00:00,029 [13] INFO BL.RRun - Starting new Retention Run with CommitMode Auto
2015-04-30 06:00:00,965 [13] INFO BL.RRun - Retention Run 152: started
2015-04-30 06:00:01,043 [13] INFO BL.RRun - Retention Run 152: applying policy 3 'Keep mails for 10 years'
2015-04-30 06:02:34,814 [13] INFO BL.RRun - Retention Run 152: finished applying policy 3 'Keep mails for 10 years': 4915800 message(s) (0 occluded), 8246754 link(s) (0 occluded) in 153760 msec
2015-04-30 06:02:34,829 [13] INFO BL.RRun - Retention Run 152: applying policy 5 'Delete Mails after 11 years'
2015-04-30 06:03:15,499 [13] INFO BL.RRun - Retention Run 152: finished applying policy 5 'Delete Mails after 11 years': 28862 message(s) (0 occluded), 36182 link(s) (0 occluded) in 40659 msec -
Informações adicionais
SQL Server also has a default remote query timeout of 600 seconds (10 minutes).
If the above resolution does not, work check the timeout value in SQL Management Studio, right click the SQL Server and choose Properties.
Click Connections then adjust the remote query timeout value.
If the SQL timeout is increased then the following setting will need to be added the the archive manager configuration console to match (default is 10 minutes):
RetentionEngineSQLQueryTimeoutMsec
The value is in milliseconds, e.g. 3600000 = 1 hour.