Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrades.
Please accept our apologies in advance for any inconvenience this might cause.

INSTALLATION NBU 7 fails on vcs cluster 5

Created: 27 Dec 2012 • Updated: 04 Jan 2013 | 8 comments
This issue has been solved. See solution.

HI all,

I am trying to install netbackup & on solaris 10 10/10 on varitas cluster 5 (SF ) . I created a shared disk-group and volume that is mounting .

I deported the dg and tried to install NBU7 during installation this is happening ...............

==================== installer error ============================

 

If this machine will be using a different network interface than the
default (bmr-node1), the name of the preferred interface should be used
as the configured server name.  If this machine will be part of a
cluster, the virtual name should be used as the configured server name.

Would you like to use "bmr-node1" as the configured
name of the NetBackup server? [y,n] (y) n

Enter the name of the NetBackup server: bmr.testbmr.org

Is bmr.testbmr.org the master server? [y,n] (y)
VCS WARNING V-16-1-10357 System does not exist
No supported cluster package was detected.
Do you have any media servers? [y,n] (n) Hangup
Connection to 172.17.67.41 closed.
If this machine will be using a different network interface than the
default (bmr-node1), the name of the preferred interface should be used
as the configured server name.  If this machine will be part of a
cluster, the virtual name should be used as the configured server name.

Would you like to use "bmr-node1" as the configured
name of the NetBackup server? [y,n] (y) n

Enter the name of the NetBackup server: bmr.testbmr.org

Is bmr.testbmr.org the master server? [y,n] (y)
VCS WARNING V-16-1-10357 System does not exist
No supported cluster package was detected.
Do you have any media servers? [y,n] (n) Hangup
=====================================================

while the hastatus is showing this

============================
root@bmr-node1.testbmr.org # hastatus
attempting to connect....
attempting to connect....connected

group           resource             system               message
--------------- -------------------- -------------------- --------------------
                                     bmr-node1.testbmr.org  RUNNING
                                     bmr-node2.testbmr.org  RUNNING
VCShmg                               bmr-node1.testbmr.org  OFFLINE
VCShmg                               bmr-node2.testbmr.org  OFFLINE
-------------------------------------------------------------------------
                VCShm                bmr-node1.testbmr.org  ONLINE
                VCShm                bmr-node2.testbmr.org  ONLINE
^C
root@bmr-node1.testbmr.org # hagrp status
=====================================================

can you please find out my mistakes ..........

 

 

Comments 8 CommentsJump to latest comment

Nagalla's picture

hi Sumit,

Do you have any media servers? [y,n] (n) Hangup
Connection to 172.17.67.41 closed.

Hangup is your Media server name or installation is hanging up there...?

if that is your media server name.. and you are trying to add it .. just dont do that.. say n to that question and go ahead with the installation.

you can configure the media server once you install the master server..

 

SumitS's picture

 

 

my problem is here

==========================================

Is bmr.testbmr.org the master server? [y,n] (y)
VCS WARNING V-16-1-10357 System does not exist
No supported cluster package was detected.

==========================================

I am trying to install the netbackup in vcs cluster but during installation the cluster is not identified by the NBU istallation procedure ..

Is it there any configuration change is required ? Or solaris version any compatibilities is required .

 

 

Nagalla's picture

hi,

does this bmr.testbmr.org the Virtual Name of the cluster.?

below is from admin guide of clustered master server

Verify that VCS and NetBackup Enterprise Server 7.5 support your hardware.

For a list of supported storage devices, visit the following Web site:
http://entsupport.symantec.com
■ Verify that the supported version of VCS is correctly installed and configured
on Solaris, HP-UX, AIX, or Linux. Follow the steps in the Veritas Cluster Server
Installation Guide.
■ Verify that no VCS resource group and resource exist with the same name as
the one you intend to use for NetBackup.
■ Make sure that the shared disk is configured and accessible to all cluster nodes
where you want to install NetBackup. Also, verify that you can mount the disk.
■ Verify that you have an IP address (virtual IP) and a host name (virtual name)
to assign to the NetBackup resource in VCS. Use these only for the NetBackup
resource.
Also, ping the IP address and verify that the IP address is not plumbed.
For VCS-UNIX, IP address of the Nodes and Virtual Name must be of same type
(IPv6 or IPv4).
With this release IPv6 is supported with NetBackup.
See “About NetBackup's IPv6 support” on page 97.
■ Make sure that each node in the cluster, where you want to install NetBackup,
is RSH equivalent (On HP Service Guard the command is remsh). As the root
user you must be able to perform a remote logon to each node in the cluster
without entering a password. This configuration is only necessary for
installation, upgrades, and configuration of the NetBackup server and any
NetBackup database agents and options. After installation and configuration
are complete RSH can be disabled.
 
 
Note: Node IP type must be same as virtual IP type.
■ For a clustered NetBackup master server, if the master server is the robotic
control host, physically connect the robotic devices and tape devices to each
node where you want to install NetBackup. Connect devices by SCSI or Fibre
Channel. Use OS commands to verify that all the devices are connected
properly. Refer to the Symantec NetBackup Device Configuration Guide.
■ Verify that you have the NetBackup
 
Note: NetBackup automatically detects supported clustering technology and
prompts questions based on it. If you are not prompted for these questions on a
clustered setup, please exit from the script and verify that cluster is configured
correctly. Refer to the cluster guide for details on how to verify the cluster setup.

 

hope this helps.

Marianne's picture

Can we start at the beginning, please: 

Before you install NBU - it what state is the cluster?
Was SF/HA installed (Storage Foundation plus Veritas Cluster) or just SF?
Was initial cluster config done?

Please post output of 'gabconfig -a'.

When you see output like this:

Port a gen a3640003 membership 01
Port h gen fd570002 membership 01

NBU can be installed and configured in the cluster.

Carefully go through all pre-req's in NBU 7.0 High Availability Guide   
or NBU 7.1 Clustered Master Server Admin Guide  
or NBU 7.5 Clustered Master Server Admin Guide.

The basics for all of these versions are the same - like rsh enabled between nodes, virtual hostname an IP in /etc/hosts on both nodes, volume that can be mounted on both nodes, etc... etc....

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Yasuhisa Ishikawa's picture

Reviewing configuration scripts under /usr/openv/netbackup/bin/cluster, I found that VCS nodename must be same with short name (first part of  'hostname' command splitted by '.').
Now, you have been configured your VCS nodenames in FQDN form. Please reconfigure your VCS nodes with shot name like bmr-node1.

BTW, please ensure following points before you retry:

  • IP address for bmr.testbmr.org is not configured on any host includnig cluster nodes.
  • Unmount and deport shared disk(s) for NetBackup cluster.
  • create mount point for shared disk for NetBackup cluster(/opt/VRTSnbu by default)
  • Remove /usr/openv/netbackup/bin/cluster/NBU_RSP and /usr/openv/netbackup/bp.conf

You can retry configuring NetBackup by running /usr/openv/netbackup/bin/install_bp.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

SOLUTION
Yasuhisa Ishikawa's picture

Additional information: "VCS WARNING V-16-1-10357 System does not exist" is displayed when configuration script fires "hasys -state ${systemName}" as below.

        systemName=`getLocalHostName`
        if [ -d /var/VRTSvcs ]; then
                status=`/opt/VRTSvcs/bin/hasys -state ${systemName}`
                TRACE 1 "VCS system state (hasys -state): $status"
                if [ "${status}" = "RUNNING" ] ; then
                        CLUTYPE=VCS
                fi
        fi

systemName is exstraced from hostname command as below. getLocalHostName() picks up first part of 'hostname' command.

getLocalHostName(){
        ${ECHO} `hostname |sed 's/\..*$//'`
}

If VCS nodes are configured in FQDN, "hasys -state <short_name>" returns V-16-1-10357 error.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

SumitS's picture

Thank you all for your commants.

As you all guided me we  find out the issue . There was a ip confilict in our network ...

 

 

 

 

 

Marianne's picture

So, Yasuhisa was right:

 

BTW, please ensure following points before you retry:

  • IP address for bmr.testbmr.org is not configured on any host including cluster nodes.

 

Please mark his post as Solution.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links