Container became unhealthy and is marked for lazy cleanup
When running opdupe, it is possible that backup jobs could fail due to a disconnect. The disconnect could come from a network problem or an application error from the client or DR side.
Part of the troubleshooting steps for disconnects is to run the dellDRdiags bundle from the client that experienced the failure.
One of the logs included in the bundle is DellDRLog.log.
It is not uncommon to see the following error message when some form of disconnect occurs:
2014-09-30 06:44:31 [0]: [5892] ERROR: [Test_REMOTE] [OCA_OFS Test-test-dr4100::17]Container became unhealthy and is marked for lazy cleanup
2014-09-23 07:48:07 [0]: [696] ERROR: [Test_REMOTE] [OCA_OFS 10.0.0.1::2]Container became unhealthy and is marked for lazy cleanup
This error does not represent any type of cleaner or corruption issue.
This message only appears when Test remote client lost connection to Test server. The client side then would mark this container as "CONTAINER_LAZY_STOPPED". So "lazy" means we don't clean it now until the connection recovers. When a connection is down, any further read/write operations on the container would trigger an error message to the caller (customer application). The customer application would then decide the next action. Usually this would be to delete it or re-ingest the data.
So from Test point of view, it would take no action (not removing or migrating files, no cleaning) but just an error message to customer. For the most part all this error message can confirm is that a disconnect occurred during a backup job.
Workaround:
To lessen the likelihood of a peer disconnect create the following registry key if one is not already present. The default value is 5. Try using a value of 15 and rerun your tests. 15 is the standard setting and that matches the Linux default behavior even though Windows has a default of 5.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
Value Name: TcpMaxDataRetransmissions
Data Type: REG_DWORD - Number
Valid Range: 0 - 0xFFFFFFFF
Default: 5
Disclaimer: Quest Software 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.
