Avamar: El informe de back-end (DD) falla después de la actualización del SO de Data Domain

Summary: El informe de back-end (DD) de Avamar falla después de la actualización del SO de Data Domain.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

El informe de back-end (DD) de Avamar falla después de la actualización del SO de Data Domain.

El error que se observa en el mcserver.log es:
com.avamar.mc.rpt.job.BackendCapacityDDReportJob.publishStatus
WARNING: I/O error: Fatal Alert received: Handshake Failure.; nested exception is javax.net.ssl.SSLException: Fatal Alert received: Handshake Failure.
org.springframework.web.client.ResourceAccessException: I/O error: Fatal Alert received: Handshake Failure.; nested exception is javax.net.ssl.SSLException: Fatal Alert received: Handshake Failure.
        at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:453)
        at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:415)
        at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:391)
        at com.avamar.mc.rpt.bcrdd.AuthSession.authenticate(AuthSession.java:87)
        at com.avamar.mc.rpt.job.BackendCapacityDDReportJob.authenticate(BackendCapacityDDReportJob.java:634)
        at com.avamar.mc.rpt.job.BackendCapacityDDReportJob.submit(BackendCapacityDDReportJob.java:244)
        at com.avamar.mc.rpt.job.BackendCapacityDDReportJob.run(BackendCapacityDDReportJob.java:130)
        at com.avamar.mc.rpt.job.ReportManager$1.run(ReportManager.java:88)
        at java.lang.Thread.run(Unknown Source)
Caused by: javax.net.ssl.SSLException: Fatal Alert received: Handshake Failure.
        at com.rsa.sslj.x.aH.a(Unknown Source)
        at com.rsa.sslj.x.aH.a(Unknown Source)
        at com.rsa.sslj.x.aH.a(Unknown Source)
        at com.rsa.sslj.x.ap.c(Unknown Source)
        at com.rsa.sslj.x.ap.a(Unknown Source)
        at com.rsa.sslj.x.ap.j(Unknown Source)
        at com.rsa.sslj.x.ap.i(Unknown Source)
        at com.rsa.sslj.x.ap.h(Unknown Source)
        at com.rsa.sslj.x.aS.startHandshake(Unknown Source)
        at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:394)
        at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:353)
        at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134)
        at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
        at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
        at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
        at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
        at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
        at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
        at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
        at org.springframework.http.client.HttpComponentsClientHttpRequest.executeInternal(HttpComponentsClientHttpRequest.java:88)
        at org.springframework.http.client.AbstractBufferingClientHttpRequest.executeInternal(AbstractBufferingClientHttpRequest.java:46)
        at org.springframework.http.client.AbstractClientHttpRequest.execute(AbstractClientHttpRequest.java:49)
        at org.springframework.http.client.InterceptingClientHttpRequest$RequestExecution.execute(InterceptingClientHttpRequest.java:91)
        at com.avamar.mc.datadomain.DdrRestClient$1.intercept(DdrRestClient.java:92)
        at org.springframework.http.client.InterceptingClientHttpRequest$RequestExecution.execute(InterceptingClientHttpRequest.java:81)
        at org.springframework.http.client.InterceptingClientHttpRequest.executeInternal(InterceptingClientHttpRequest.java:67)
        at org.springframework.http.client.AbstractBufferingClientHttpRequest.executeInternal(AbstractBufferingClientHttpRequest.java:46)
        at org.springframework.http.client.AbstractClientHttpRequest.execute(AbstractClientHttpRequest.java:49)
        at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:438)
        ... 8 more

Cause

Data Domain OS utiliza nuevos cifrados que no se especifican en el mcserver.xml en Avamar.

Resolution

No debe haber respaldos, restauraciones ni replicaciones en ejecución en Avamar Server.

Haga una copia de /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml.

Detenga el servicio MCS.

Actualice las siguientes entradas en el mcserver.xml:
<entry key="ddr_rest_supported_cipher_suites"
and
<entry key="ssl_ciphers"
Asegúrese de que los siguientes cifrados estén en ambas entradas:
TLS_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

Inicie el servicio

MCS El informe de back-end (DD) de Avamar ahora debería funcionar.

Affected Products

Avamar Server
Article Properties
Article Number: 000220880
Article Type: Solution
Last Modified: 16 Feb 2024
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.