Error=1053 reported for Netbackup Services when Netbackup is Clustered using VCS.
Article ID: 100030019
Updated On:
Description
Error Message
VCS ERROR V-16-20025-4 NetBackup:NBU-FS02:online:Failed to start the service 'NetBackup Enterprise Media Manager'. Error = 1053.VCS ERROR V-16-20025-4 NetBackup:NBU-FS02:online:Failed to start the service 'NetBackup Resource Broker'. Error = 1053.
Cause
In the SFW/HA GCO configuration that includes a NetBackupservice group to control NetBackup server services, two service groups are configured to manage NetBackup; one service group at the production site and one service group at the DR site.
Each service group has the same Virtual ServerName attribute for the Lanman resource, however, each service group has a different TCP/IP address for the IP Address resource.
When attempting to start the service group on a node at the DR site, the following NetBackup services fail to start causing the NetBackup resource to fault which can cause the service group to fail back to the primary site:
NetBackup Enterprise MediaManager
NetBackup ResourceBroker
NetBackup Job Manager
NetBackup Policy ExecutionManager
Review of the "%VCS_HOME%\log\NetBackup_A.txt" log file to determine why the NetBackup resource faulted It will show the below VCS errors:
VCS ERROR V-16-20025-4NetBackup:NBU-FS02:online:Failed to start the service 'NetBackup EnterpriseMedia Manager'. Error = 1053.VCS ERROR V-16-20025-4NetBackup:NBU-FS02:online:Failed to start the service 'NetBackup ResourceBroker'. Error = 1053VCS ERROR V-16-20025-4NetBackup:NBU-FS02:online:Failed to start the service 'NetBackup Job Manager'.Error = 1053.VCS ERROR V-16-20025-4NetBackup:NBU-FS02:online:Failed to start the service 'NetBackup PolicyExecution Manager'. Error = 1053.VCS ERROR V-16-2-13066Thread(4840) Agent is calling clean for resource(NBU-PRODBKP01) because theresource is not up even after online completed.The above NetBackup services must be able to resolve the server by name and IP address.
When the PING command is issued to test connectivity with the Virtual Server name that NetBackup uses, the IP address that is returned might possibly be the IP address from the primary site.
This could be caused as during failover, the DNS is not updated with the correct IP address for the VirtualServer name on the DR site.
Resolution
To resolve the issue, follow the below procedure on the cluster at the DR site:
1. In the Veritas Cluster Manager, offline the NetBackup service group so it is not running on a node in the DR site
2. Edit the Lanman resource attribute DNSUpdateRequired from the default of
false to true in the NetBackup service group3. Save and Close Configuration
4. Bring the service group online on the node at the DR site
When the Lanman resource is online, it will now update DNS with the IP address for the virtual server name that needs to be used at the DR site and the NetBackup services will now start successfully.
Issue/Introduction
The NetBackup resource faults because the Enterprise Media Manager service fails to start in a Veritas Storage Foundation HA for Windows (SFW/HA) cluster using the Global Cluster Option (GCO) for a Disaster Recovery (DR) site.
Was this article helpful?
Yes
No
Powered by
