{"id":17730,"date":"2018-02-20T01:00:24","date_gmt":"2018-02-20T00:00:24","guid":{"rendered":"https:\/\/eltallerdelbit.com\/?p=17730"},"modified":"2020-09-03T13:57:58","modified_gmt":"2020-09-03T11:57:58","slug":"shared-memory-connection-was-closed","status":"publish","type":"post","link":"https:\/\/eltallerdelbit.com\/shared-memory-connection-was-closed\/","title":{"rendered":"Veeam Error: Shared memory connection was closed"},"content":{"rendered":"<h2>Vamos a ver a qu\u00e9 se debe el error\u00a0<em><strong>Shared memory connection was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}<\/strong><\/em> en Veeam, y c\u00f3mo solucionarlo.<\/h2>\n<p>&nbsp;<\/p>\n<h3><a href=\"https:\/\/forums.veeam.com\/veeam-agent-for-windows-f33\/error-shared-memory-connection-was-closed-t27473.html\" target=\"_blank\" rel=\"noopener noreferrer\">Error: <em><span style=\"color: #3366ff;\">Shared memory connection was closed<\/span><\/em><\/a><\/h3>\n<p>&nbsp;<\/p>\n<ul>\n<li>1. El error:\u00a0<a href=\"#error_shared_memory_connection\">Shared memory connection was closed. Failed to upload disk<\/a><\/li>\n<p>&nbsp;<\/p>\n<li>2. Posibles <a href=\"#causas_error\">Causas del Error<\/a>.<br \/>\n&nbsp;<\/p>\n<ul>\n<li>2.1 <a href=\"#perdida_paquetes_red\">P\u00e9rdida de paquetes en alg\u00fan lugar de la red entre los dos servidores<\/a>\n<ul>\n<li>2.1.1 <a href=\"#log_errores_red_vcenter\">Buscando mensajes de error en el Vcenter Server<\/a>\n<ul>\n<li><a href=\"#log_errores_red_vcenter\" target=\"_blank\" rel=\"noopener noreferrer\">Delayed Write Failed<\/a><\/li>\n<li><a href=\"#id_event_50\" target=\"_blank\" rel=\"noopener noreferrer\">mensaje de error de los eventos con IEventD 50<\/a><\/li>\n<\/ul>\n<\/li>\n<p>&nbsp;<\/p>\n<li>2.1.2 <em><a href=\"#synattackprotect\">The\u00a0<strong style=\"text-align: center;\">SynAttackProtect<\/strong><span style=\"text-align: center;\">\u00a0setting may be dropping connections<\/a><\/em> (Conexiones rechazadas debido a la configuraci\u00f3n de la directiva\u00a0<\/span><strong style=\"text-align: center;\">SynAttackProtect<\/strong><span style=\"text-align: center;\">)<\/span>\n<ul>\n<li>2.1.2 a) <a href=\"#solucion_error_synattackprotect\">Soluci\u00f3n para el error relativo a\u00a0la directiva\u00a0<strong>SynAttackProtect<\/a><\/strong><\/li>\n<\/ul>\n<\/li>\n<p>&nbsp;<\/p>\n<li>2.2 Podr\u00eda ser por un <a href=\"#error_pila_tcpip\">error relacionado con la pila tcp \/ ip de Microsoft<\/a>\n<ul>\n<li>2.2.a) <a href=\"#solucion_error_relacionado_vmware\">Soluci\u00f3n si el error est\u00e1 relacionado con VMWare y no con Veeam<\/a><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<p>&nbsp;<\/p>\n<li>3. <a href=\"#herramientas_diagnostico_red\">Herramientas de Diagn\u00f3stico<\/a><\/li>\n<p>&nbsp;<\/p>\n<li>4. <a href=\"#conclusiones\">CONCLUSIONES<\/a><\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h3 id=\"error_shared_memory_connection\" style=\"text-align: center;\"><span style=\"text-decoration: underline;\">1. El error:\u00a0<em><strong>Shared memory connection was closed<\/strong>. Failed to upload disk<\/em><\/span><\/h3>\n<p>&nbsp;<br \/>\nAqu\u00ed vemos el error cuando es mostrado por <em>Veeam Backup<\/em>:<\/p>\n<pre lang=\"javascript\">\r\n02\/11\/**** 16:20:47 :: Processing <em>HOST<\/em> Error: The specified network name is no longer available.\r\nFailed to write data to the file [\\\\192.168.***.***\\Copia_Seguridad\\\\Backup_*****-02T162034.vbk].\r\nFailed to download disk.\r\nShared memory connection was closed.\r\nFailed to upload disk.\r\nAgent failed to process method {DataTransfer.SyncDisk}.\r\n<\/pre>\n<p>&nbsp;<\/p>\n<p><img decoding=\"async\" loading=\"lazy\" class=\"aligncenter size-full wp-image-17817\" src=\"https:\/\/eltallerdelbit.com\/wp-content\/uploads\/2017\/11\/shared-memory-connection-was-closed.jpg\" alt=\"Shared memory connection was closed\" width=\"800\" height=\"444\" srcset=\"https:\/\/eltallerdelbit.com\/wp-content\/uploads\/2017\/11\/shared-memory-connection-was-closed.jpg 800w, https:\/\/eltallerdelbit.com\/wp-content\/uploads\/2017\/11\/shared-memory-connection-was-closed-300x167.jpg 300w, https:\/\/eltallerdelbit.com\/wp-content\/uploads\/2017\/11\/shared-memory-connection-was-closed-768x426.jpg 768w, https:\/\/eltallerdelbit.com\/wp-content\/uploads\/2017\/11\/shared-memory-connection-was-closed-600x333.jpg 600w, https:\/\/eltallerdelbit.com\/wp-content\/uploads\/2017\/11\/shared-memory-connection-was-closed-610x339.jpg 610w\" sizes=\"(max-width: 800px) 100vw, 800px\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h3 id=\"causas_error\" style=\"text-align: center;\"><span style=\"text-decoration: underline;\">2. Posibles causas del error\u00a0<em><strong>Shared memory connection was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk<\/strong><\/em><\/span><\/h3>\n<p>&nbsp;<\/p>\n<h4 id=\"perdida_paquetes_red\" style=\"text-align: center;\"><span style=\"text-decoration: underline;\">2.1 P\u00e9rdida de paquetes en alg\u00fan lugar de la red entre los dos servidores<\/span><\/h4>\n<p>&nbsp;<\/p>\n<p>Normalmente, este problema est\u00e1 relacionado con la p\u00e9rdida de paquetes en alg\u00fan lugar de la red entre los dos servidores. Aunque las razones pueden ser muy diversas.<br \/>\n<\/br><\/br>&nbsp;<br \/>\nEl error se refiere al mecanismo utilizado para que los componentes &#8220;<em>hablen<\/em>&#8221; entre ellos. Podr\u00eda ser tambi\u00e9n un error de memoria o un error f\u00edsico en los discos (un error I\/O). Fuente: <a href=\"https:\/\/forums.veeam.com\/veeam-agent-for-windows-f33\/error-shared-memory-connection-was-closed-t27473.html\" target=\"_blank\" rel=\"noopener noreferrer\">Veeam Forum<\/a>.<\/p>\n<p>&nbsp;<\/p>\n<p>En detalle: una m\u00e1s que posible causa de este error es que alg\u00fan dispositivo de la red est\u00e1 generando <a href=\"https:\/\/statusexcessu.wordpress.com\/2012\/02\/28\/spanning-tree-protocol-y-broadcast-storm-control\/\" target=\"_blank\" rel=\"noopener noreferrer\">tormentas de Broadcast<\/a>, y eso crea problemas de inestabilidad y latencia en la red, que provocan que la backup no pueda realizarse correctamente, ya que la conexi\u00f3n entre el host del cual se intenta hacer una copia de seguridad, y el dispositivo de copias de seguridad en el que se almacenar\u00e1 dicha backup, se corta o resulta intermitente.<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h5 id=\"log_errores_red_vcenter\" style=\"text-align: center;\"><span style=\"text-decoration: underline;\">2.1.1 Buscando mensajes de error sobre p\u00e9rdida de paquetes\/problemas de red en el <em>Vcenter Server<\/em><\/span><\/h5>\n<p>&nbsp;<br \/>\nB\u00fascamos errores en el Vcenter Server. Y analizando los errores relativos a las horas de funcionamiento de la tarea de Backup de Veeam que falla, encontramos el error:\u00a0<a href=\"https:\/\/aidanfinn.com\/?p=15657\" target=\"_blank\" rel=\"nofollow noopener noreferrer\"><em><strong>Delayed Write Failed<\/strong><\/em><\/a><\/p>\n<p>&nbsp;<\/p>\n<p>Descripci\u00f3n:<\/p>\n<p><em>{<strong>Delayed Write Failed<\/strong>} Windows was unable to save all the data for the file<\/em> ******* . <em>The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere<\/em>.<br \/>\n&nbsp;<br \/>\n<img decoding=\"async\" loading=\"lazy\" class=\"aligncenter size-full wp-image-17815\" src=\"https:\/\/eltallerdelbit.com\/wp-content\/uploads\/2017\/11\/event-50-mup-windows-server.jpg\" alt=\"event 50 mup windows server\" width=\"1024\" height=\"298\" srcset=\"https:\/\/eltallerdelbit.com\/wp-content\/uploads\/2017\/11\/event-50-mup-windows-server.jpg 1024w, https:\/\/eltallerdelbit.com\/wp-content\/uploads\/2017\/11\/event-50-mup-windows-server-300x87.jpg 300w, https:\/\/eltallerdelbit.com\/wp-content\/uploads\/2017\/11\/event-50-mup-windows-server-768x224.jpg 768w, https:\/\/eltallerdelbit.com\/wp-content\/uploads\/2017\/11\/event-50-mup-windows-server-600x175.jpg 600w, https:\/\/eltallerdelbit.com\/wp-content\/uploads\/2017\/11\/event-50-mup-windows-server-610x178.jpg 610w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>Se trata de un evento con ID: 50<\/p>\n<p><a href=\"https:\/\/docs.microsoft.com\/en-us\/windows-server\/storage\/file-server\/troubleshoot\/troubleshoot-event-id-50-error\" target=\"_blank\" rel=\"noopener noreferrer\">Descripci\u00f3n del mensaje de error de los eventos con IDEvent 50<\/a>:<\/p>\n<p>&nbsp;<\/p>\n<p>Traducci\u00f3n: <\/p>\n<p id=\"id_event_50\">Windows &#8211; Error en la escritura demorada: Windows no pudo guardar todos los datos del archivo ***** .<br \/>\n<\/br><\/br>&nbsp;<br \/>\nLa informaci\u00f3n se ha perdido.\u00a0Este error puede deberse a una falla en el hardware de su computadora o <strong>en la conexi\u00f3n de red<\/strong>.<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h5 id=\"SynAttackProtect\" style=\"text-align: center;\"><span style=\"text-decoration: underline;\">2.1.2 <em>The\u00a0<strong>SynAttackProtect<\/strong>\u00a0setting may be dropping connections<\/em> (Conexiones rechazadas debido a la configuraci\u00f3n de la directiva\u00a0<strong>SynAttackProtect<\/strong>)<\/span><\/h5>\n<p>&nbsp;<br \/>\nSeguimos investigando, y relativo al mensaje de error de <em>DataTransfer.SyncDisk<\/em>, encontramos informaci\u00f3n de que puede deberse a que en el Vcenter Server est\u00e1 activada la protecci\u00f3n contra Ataques Syn .\u00a0<a href=\"https:\/\/www.itprotoday.com\/security\/what-syn-attack\" target=\"_blank\" rel=\"noopener noreferrer\">El ataque SYN (solicitud de conexi\u00f3n TCP) es una t\u00e9cnica de denegaci\u00f3n de servicio (DoS)<\/a><br \/>\n&nbsp;<br \/>\nEn este caso pod\u00eda ser que el Vcenter Server est\u00e9 tirando abajo las conexiones con el Host (<em>The\u00a0<strong>SynAttackProtect<\/strong>\u00a0setting may be dropping connections<\/em>) debido a que esta directiva est\u00e1 activada.<br \/>\n&nbsp;<br \/>\nSe podr\u00eda resolver corrigiendo una clave del registro de Windows, lo vemos en el siguiente punto.<br \/>\n&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h5 id=\"solucion_error_synattackprotect\" style=\"text-align: center;\"><span style=\"text-decoration: underline;\">2.1.2 a) Soluci\u00f3n para el error relativo a\u00a0la directiva\u00a0<strong>SynAttackProtect<\/strong><\/span><\/h5>\n<p>&nbsp;<br \/>\nAbrimos <em>regedit<\/em> y navegamos hasta la siguiente localizaci\u00f3n:<br \/>\n&nbsp;<\/p>\n<pre lang=\"javascript\">HKLM\\SYSTEM\\CurrentControlSet\\Services\\Tcpip\\Parameters<\/pre>\n<p>Creamos un valor DWORD (32 bits) con el nombre: <strong><em>SynAttackProtect<\/em><\/strong><\/p>\n<p>con el valor:\u00a000000000<\/p>\n<p>Al poner el valor a 0, habremos deshabilitado esta caracter\u00edstica.<br \/>\n&nbsp;<br \/>\n<img decoding=\"async\" loading=\"lazy\" class=\"aligncenter size-full wp-image-18552\" src=\"https:\/\/eltallerdelbit.com\/wp-content\/uploads\/2018\/02\/synattackprotect-windows-server.jpg\" alt=\"SynAttackProtect Windows Server\" width=\"640\" height=\"554\" srcset=\"https:\/\/eltallerdelbit.com\/wp-content\/uploads\/2018\/02\/synattackprotect-windows-server.jpg 640w, https:\/\/eltallerdelbit.com\/wp-content\/uploads\/2018\/02\/synattackprotect-windows-server-300x260.jpg 300w, https:\/\/eltallerdelbit.com\/wp-content\/uploads\/2018\/02\/synattackprotect-windows-server-600x519.jpg 600w, https:\/\/eltallerdelbit.com\/wp-content\/uploads\/2018\/02\/synattackprotect-windows-server-610x528.jpg 610w\" sizes=\"(max-width: 640px) 100vw, 640px\" \/><\/p>\n<p>Fuente de este error y su soluci\u00f3n: <a href=\"https:\/\/www.veeam.com\/kb1781\" target=\"_blank\" rel=\"noopener noreferrer\">Veeam Backup Forum |\u00a0Connection forcibly closed by remote host<\/a><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h4 id=\"error_pila_tcpip\" style=\"text-align: center;\"><span style=\"text-decoration: underline;\">2.2 Otra posible causa (aunque no muy com\u00fan) ser\u00eda un <a href=\"https:\/\/www.reddit.com\/r\/vmware\/comments\/47d1ee\/veeam_br_backups_failing_xpost_from_rveeam\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">error en la pila de TCP\/IP<\/a><\/span><\/h4>\n<p>&nbsp;<br \/>\nOtro posible problema podr\u00eda estar relacionado con la pila tcp \/ ip de Microsoft.<br \/>\n&nbsp;<br \/>\nY <a href=\"https:\/\/www.reddit.com\/r\/vmware\/comments\/47d1ee\/veeam_br_backups_failing_xpost_from_rveeam\/?st=jd8tbpef&#038;sh=0f47cd2b\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">esta info<\/a>\u00a0 sobre problemas con VMware y no con Veeam, nos lleva a la siguiente soluci\u00f3n:<br \/>\n&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h5 id=\"solucion_error_relacionado_vmware\" style=\"text-align: center;\"><span style=\"text-decoration: underline;\">2.2 a)\u00a0 Soluci\u00f3n si el error est\u00e1 relacionado con VMWare y no con Veeam<\/span><\/h5>\n<ul>\n<li>Reiniciar el Host<\/li>\n<li>Realizar una tarea de Backup de Veeam con una m\u00e1quina. Si funciona, es que el problema no es Veeam sino Vmware.<\/li>\n<li>Reiniciar ESXI<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h3 id=\"herramientas_diagnostico_red\" style=\"text-align: center;\"><span style=\"text-decoration: underline;\">3. Herramientas de Diagn\u00f3stico<\/span><\/h3>\n<p>Unas herramienta com\u00fan que suele recomendarse para las pruebas es <a href=\"\/filtrar-dhcp-wireshark\/\" title=\"Filtrar DHCP con Wireshark\" rel=\"noopener noreferrer\" target=\"_blank\"><em>Wireshark<\/em><\/a>, ya que pueden proporcionar bastante informaci\u00f3n sobre la conexi\u00f3n de red.<br \/>\n&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h3 id=\"conclusiones\" style=\"text-align: center;\"><span style=\"text-decoration: underline;\">4. CONCLUSIONES<\/span><\/h3>\n<p>&nbsp;<br \/>\nEst\u00e1 bastante claro que el error\u00a0 <strong><em>Shared memory connection was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}<\/em><\/strong> se debe a un problema de comunicaci\u00f3n entre los dos dispositivos afectados en la Backup de las VM\u00b4s de Veeam.<br \/>\n<\/br><\/br>&nbsp;<br \/>\nPero las razones pueden ser muy diversas como hemos visto en este art\u00edculo, y debemos explorar todas las opciones hasta encontrar la raz\u00f3n concreta en cada escenario particular.<\/p>\n<p>&nbsp;<\/p>\n\n<div style=\"font-size: 0px; height: 0px; line-height: 0px; margin: 0; padding: 0; clear: both;\"><\/div>","protected":false},"excerpt":{"rendered":"<p>El error  &#8220;Shared memory connection was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}&#8221; se debe a un problema de comunicaci\u00f3n entre los dos dispositivos afectados en la Backup de las VM\u00b4s de Veeam<\/p>\n","protected":false},"author":1,"featured_media":17817,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false},"categories":[1276],"tags":[1116,1125,1123,1124],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/eltallerdelbit.com\/wp-json\/wp\/v2\/posts\/17730"}],"collection":[{"href":"https:\/\/eltallerdelbit.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/eltallerdelbit.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/eltallerdelbit.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/eltallerdelbit.com\/wp-json\/wp\/v2\/comments?post=17730"}],"version-history":[{"count":0,"href":"https:\/\/eltallerdelbit.com\/wp-json\/wp\/v2\/posts\/17730\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/eltallerdelbit.com\/wp-json\/wp\/v2\/media\/17817"}],"wp:attachment":[{"href":"https:\/\/eltallerdelbit.com\/wp-json\/wp\/v2\/media?parent=17730"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/eltallerdelbit.com\/wp-json\/wp\/v2\/categories?post=17730"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/eltallerdelbit.com\/wp-json\/wp\/v2\/tags?post=17730"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}