zoukankan      html  css  js  c++  java
  • NBU客户端备份失败,报错error 48 client hostname could not be found

    今天在做备份时发现了这个报错。经过ping, nslookup, bpclntcmd命令检查没有发现连接或域名解析存在问题。

    参考文档http://www.symantec.com/docs/TECH59927,在检查时发现/use/openv/netbackup/db/client/<client_name>目录下存在一个名为fi_info.<client_backup_policy>.class的文件,而并不存在名为host_info的文件或目录。为了安全起见,我没有直接删除<client_name>这个目录,而是做了重命名。

    mv /use/openv/netbackup/db/client/<client_name> /use/openv/netbackup/db/client/<client_name_bk>

    然后重新执行备份,备份成功完成。

    附参考文档:http://www.symantec.com/docs/TECH59927

    Problem

    STATUS CODE 48: Backups of a UNIX client fail with a NetBackup Status Code 48 (client hostname could not be found), but hostname lookup and DNS issues are not the problem

    Error

    client hostname could not be found

    Solution

    Overview:
    A NetBackup client backup fails with NetBackup Status Code 48 (client hostname could not be found), even when no hostname lookup issues exist.  Traditional troubleshooting techniques using bpclntcmd, bptestbpcd, telnet, ping, nslookup, all show good connectivity and name resolution.  Other clients are backing up correctly.
    Troubleshooting:
    Review the contents of the /usr/openv/netbackup/db/client/<client_name> directory on the master server.  
    This directory should contain client attribute information, and by default is not present under the db/clientdirectory.   Client attributes may be added under the master server host properties in the NetBackup Administration Console, or by command line using the bpclient command.  When client attributes are set correctly, the <client_name> directory should contain the client attributes in a subdirectory called host_info.
    Log files:  
    The bpbrm log file shows the following:
    18:02:08.516 [21626] <2> verify_client: bpbrm.c.32914: Could not find a host name for DHCP client: <client_name>
    18:02:08.516 [21626] <2> bpbrm process_start_backup_msg: bpbrm.c.11705: verify_client failed: 48 48 0x00000030
    Resolution:
    The above symptoms and error messages are seen if the/usr/openv/netbackup/db/client/<client_name> directory on the master server does not contain any client attribute information, or contains otherwise corrupt information.  
    If the client directory is empty, the directory may be removed manually in one of three ways:

    1. Using the rm -r command. 

    2. Using the NetBackup Administration Console to remove the client from the client attributes in the master server host properties.

    3. By running bpclient -client <client_name> -delete.   If the client directory is not empty, the directory may be renamed to eliminate any data corruption as the cause of the issue.

  • 相关阅读:
    谈谈我对服务熔断、服务降级的理解
    PS-AXI-GPIO-流水灯设计
    立创EDA的使用
    multisim的操作回顾
    verilog的文件流和项目流
    AXI4的主从机的收发机制
    AXI4协议的物理模型
    verilog中的数据类型
    matlab的基本操作
    ARM之AXI总线协议初试
  • 原文地址:https://www.cnblogs.com/cqubityj/p/3262612.html
Copyright © 2011-2022 走看看