When performing any replication setting changes (i.e. changing bandwidth) on a Volume Replicator (VVR) Replicated Data Set (RDS), the Secondary may stop responding with a bug check.
BSOD, Bluescreen, STOP.
Windows Server 2008 R2: STOP 0x0000012E (0x12E) -INVALID_MDL_RANGE
Windows Server 2003/2008: STOP 0x00000050 (0x50) - PAGE_FAULT_IN_NONPAGED_AREA
fffffa60`07df79d0 fffffa60`00c1cbb0 nt!IoBuildPartialMdl+0xb3
fffffa60`07df7a00 fffffa60`00c1d0eb vxio!tdi_get_next_tcp_block+0x16c
fffffa60`07df7a70 fffffa60`00c1d1c1 vxio!nmcom_get_next_msg+0x367
fffffa60`07df7aa0 fffffa60`00c2a0c2 vxio!nmcom_wait_msg_tcp+0xa9
fffffa60`07df7ad0 fffffa60`00c2aed4 vxio!nmcom_server_proc_tcp+0x12a
fffffa60`07df7b50 fffff800`01c68f77 vxio!nmcom_server_main_tcp+0xc7c
fffffa60`07df7d50 fffff800`01a9b636 nt!PspSystemThreadStartup+0x57
fffffa60`07df7d80 00000000`00000000 nt!KiStartSystemThread+0x16
Certain error conditions in building Partial MDL structures were not handled correctly causing Memory corruption.
This issue has been identified and a private fix is available from Symantec Enterprise Technical Support. To obtain the private fix, contact Symantec Enterprise Technical Support and reference this article during the call. A support representative will be available to assist in troubleshooting this issue. If it is determined that the private fix addresses the problem the support representative will further assist in obtaining the private fix.
Note: This fix specifically addresses the problem identified above. It has not been fully tested and should be applied in a test environment before placing into production. If the systems are not critically impaired, it is recommended to delay the installation of this private fix until the next scheduled maintenance release. Before applying this private fix, systems may be required to be upgraded to the latest code base. The support representative will help in determining the best course of action.
Storage Foundation for Windows with VVR option.
TCP mode replication.