O backup do vProxy apresenta falha com o erro: ddp_connect_with_config() failed, Hostname: DD_name, Erro: 5075-DDBOOST Erro 1 para pesquisa /backup/ost no DD_Name

ddp_connect_with_config() failed, Hostname: DD_name, Err: 5075-DDBOOST Error 1 for lookup /backup/ost on DD_Name (nfs: Operation not permitted)

Verificação inicial:

• O DDBoost está em execução no DD
• O NFSv3 está habilitado no Data Domain
• As portas do firewall estão abertas entre o DD e o vProxy: NVP vProxy: Solução de problemas de conectividade de rede para operações de backup e restauração
• A senha do DDBoost usada está correta
• A configuração do client DDBoost permite este client específico:

• 1) Example:  
  
  Below example shows both "*" and a client name.  If "*" is missing then only clients in the list are permitted to connect to the DD.
  
  # ddboost clients show config
  Client               Encryption Strength   Authentication Mode
  ------------------- -------------------   -------------------
  *                    none                  none
  MyClient.mycomp.com  none                  none
  MyOtherClient        none                  none
  -------------------  -------------------   -------------------
  (**) The global security settings take precedence over these client(s) specific settings.
  
  2) Example from ddfs.info:
  07/03 14:59:25.659490 [7ff122a44170] WARNING: Client <MyOtherClient.mycomp.com> did not match access list entries
  07/03 14:59:25.659521 [7ff122a44170] nfsproc3_ost_mnt_3_svc: client access denied for <Client IP> version 7.0
  
  3) In some cases you will see that the error log lists the FQDN or the short name, but the client config is using the other form of the name. The configuration and the client name must match exactly. The DDBoost Plugin on the client will determine the name for the client. This will check the local hosts file on the client for a match for the source side IP for the client. If there is a match, it will use it. (Selecting the FQDN name if one is available, then short name) If there is no match, then the plugin will do a DNS query for the IP and use the response returned.
  
  4) If there is a discrepancy between the clients local host entry verses the DDBoost client config, ask the customer to choose which configuration that they would like to change.
  
  a) add "*" to the DD clients list will allow any client with proper credentials to authenticate to the DD.
  # ddboost clients add *
  
  b) add the corresponding name (from the error log, or client side local hosts file) to the DD:
  # ddboost clients add <hostname>
  
  c) modify the local hosts file or DNS for the IP address being used by the client to make it reflect the client name that was added to DD clients list.
  Example for Linux:
  file: /etc/hosts
  10.11.12.13 MyOtherClient.mycomp.com MyOtherClient
    changed to 
  10.11.12.13 MyOtherClient
  
  
  
  

Se todos os itens acima forem confirmados acima, verifique o comprimento da senha do DDBoost para o MTREE que está sendo usado para o vProxy. A senha máxima permitida para uso com o vProxy é de 30 caracteres.

Se o comprimento da senha não for excessivo, recomenda-se uma verificação de conectividade entre o vProxy e o DD usando o utilitário 'ddpconnchk'. Mais detalhes sobre o uso de 'ddpconnchk': NetWorker: Como usar a ferramenta DDPCONNCHK para testar a conectividade do DD ddboost dos hosts do NetWorker