Forum Discussion

NavGee's avatar
NavGee
Level 5
11 years ago

Netbackup installation steps for linux vcs cluster

Hi Can anybody help me validate steps to install Netbackup 7.6 server, client  and the latest patch on a newly build linux VCS cluster. I have read the HA guide and Netbackup clustered Admin Guide however I need clarification on the progresses involved. Please confirm what is correct below and if any of the steps are incorrect then please correct them  for me.

 

Install Netbackup 7.6 on the Primary node with virtual IP and virtual name.

During the install stage will the install request the physical name, IP and NIC name.

Once the install is complete do I go ahead and install the client binaries and maintance patch without freezing the cluster etc.

Start and complete the Netbackup 7.6 server install at completion Do I need to freeze the cluster, put it in read and write then take it offline to install the client binaries and Maintance Patch.

 

After Installing Netbackup ,  maintance patch and client on the primary active node  create the required symbolic links.

/usr/openv/netbackup/db  ->  /opt/VRTSnbu/netbackup/db

/usr/openv/db/staging    ->  /opt/VRTSnbu/db/staging

 

  • You need to download and read through the relevant sections of these 2 manuals:

    NetBackup Installation Guide 

    NetBackup Clustered Master Server Administrator's Guide 

    Basic Cluster installation and configuration should be done. 
    gabconfig -a 
    should show both nodes port a and h configured.

    Read through the preparation checklist and requirements in the Clustered master server guide, 
    such as having the virtual IP and hostname in /etc/hosts on both nodes, catalog volume, rsh/ssh comms without password, etc... etc...

    No need to create symbolic links - the installation process will do everything for you.
    Installation on 1st node will create service group with this node only. Do not install NBU patch at this point.

    Client software is installed along with Server software. If you want to install additional Client software for other Unixes, you can do so at this point in time. You can freeze the service group before installing client software. Just remember to unfreeze before installing node 2.
    Installation on 2nd node will join this service group and add node to EMM.
    Do same for additional Client software.

    EMM entries will only show up correctly once you have successfully switched to node 2.

    Patch installation steps are listed in the patch download page (Find download for your Linux server version here: http://www.symantec.com/docs/TECH217819 . Ensure you have Server and Client patch extracted in same folder.
    Offline NBU resource (NOT the Service Group) and freeze the SG.
    Start patch installation on the inactive node as per the installation instructions.
    (Detailed, step-by-step instructions in the download link).

     

     

     

  • Hi Marianne, I'm not sure if it is duplicate as such just broke down my questions differently, seem to getting weird responses in return no real answers to my questions that's why I rewrote the post.   Would be great if you could answer my questions that would be splendid?????

     

     

    Regards

     

  • You need to download and read through the relevant sections of these 2 manuals:

    NetBackup Installation Guide 

    NetBackup Clustered Master Server Administrator's Guide 

    Basic Cluster installation and configuration should be done. 
    gabconfig -a 
    should show both nodes port a and h configured.

    Read through the preparation checklist and requirements in the Clustered master server guide, 
    such as having the virtual IP and hostname in /etc/hosts on both nodes, catalog volume, rsh/ssh comms without password, etc... etc...

    No need to create symbolic links - the installation process will do everything for you.
    Installation on 1st node will create service group with this node only. Do not install NBU patch at this point.

    Client software is installed along with Server software. If you want to install additional Client software for other Unixes, you can do so at this point in time. You can freeze the service group before installing client software. Just remember to unfreeze before installing node 2.
    Installation on 2nd node will join this service group and add node to EMM.
    Do same for additional Client software.

    EMM entries will only show up correctly once you have successfully switched to node 2.

    Patch installation steps are listed in the patch download page (Find download for your Linux server version here: http://www.symantec.com/docs/TECH217819 . Ensure you have Server and Client patch extracted in same folder.
    Offline NBU resource (NOT the Service Group) and freeze the SG.
    Start patch installation on the inactive node as per the installation instructions.
    (Detailed, step-by-step instructions in the download link).

     

     

     

  • Hi Marianne

    Many thanks for the clarification, fully understood, however I'm dealing with a quite a difficult customer this morning he has informed me that they have a global cluster, firstly he had given me that it was HA cluster. The configuration is site A has 1 master server and site B has the second master server. I assuming that HA has shared disk amongst the cluster where as the global cluster has its own local install and VVR that replicates the catalog information how does this change the Netbackup install? Please advise?

     

     

    Regards

      

  • Hi Marianne

    once again many thanks for pointing me into the right direction, ok I understand the different requirements for global cluster with catalog replication.  I need to create a document with all the steps involved I'm assuming that I need to carry out a normal Netbackup VC cluster in on the primary node first instead then move on to the secondary node.  I found a normal VCS cluster install step by step guide on the forums which I need to adapt to include the VVR steps.  The customer has VCS team which can turn once I created the steps involved is it possible you could go through the step and qualify any changes for VVR catalog replication?

     

     

    Regards

     

     

  • Considerations for Netbackup Global VCS cluster taken from HA guide:

     

    Specify following while installing NetBackup master server cluster on primary

    node:

    Replicated storage as the mount point for the cluster common storage.

    All servers that are part of the domain.

    Servers that form the secondary site cluster.

    2 After the NetBackup cluster group is created, reconfigure the storage resources

    to include the replication control components.

    3 For some replications layers, for example for Veritas Volume Replicator (VVR),

    the replication agent must be in a separate service group. You must link the

    agent with the NetBackup application service group.

     

    Installing and configuring secondary NetBackup master server

    cluster

    To install and configure the secondary NetBackup master server cluster, it is not

    necessary to have the same number of nodes as the primary NetBackup master

    server cluster. The secondary NetBackup master server cluster can be a single

    node cluster but should be clustered. Refer follwoing guidelines to install the

    secondary NetBackup master server cluster with catalog replication.

    Installing the secondary NetBackup master server cluster with catalog replication

    1 Before starting the installation determine the mount point that would be used

    to mount the replicated volume from the primary site.

    Do not mount the replicated volume at this time. Instead mount another

    formatted volume against this mount point. During the installation an empty

    catalog will be created on this volume, which can later be discarded.

    2 Install NetBackup on the secondary master server cluster using the same virtual

    host name as the primary master server cluster. During the installation make

    sure to specify all media servers configured on the primary master server

    cluster as additional servers. This ensures that the server list is consistent for

    both clusters.

    Deploying NetBackup master servers with full catalog replication 62

    About globally clustered NetBackup master servers with catalog replication

    3 Once the installation is complete, shutdown NetBackup and take the cluster

    common catalog volume off line.

    4 Update the cluster configuration to mount the replicated volume from the primary

    site as the cluster common volume. This step may require adding the replication

    agent or enabling replication within the disk resource. Do not bring this resource

    online until you are instructed to do so in the next phase of the setup (Populating

    the server tables in EMM) The volume used during the installation is no longer

    required and can be re-used for another purpose.

     

     

  • Found this old post on the subject

    https://www-secure.symantec.com/connect/forums/netbackup-and-vvr

     

  • Not sure why you copy & pasted from the manual...

    Is anything unclear?

    If you are not confident about VCS and VVR installation and config, please find a Symantec reseller with installation consulting services.

  • I copied and pasted from the manual to share the differences between HA and global cluster differences. The client has a VCS team my role is to help with the netbackup install. I used the installation steps from the forum can you review for me and advice what changes need to be during the install.  I have attached the doc to this post and highlighted anything of concerns in bold for you to review.   Please review and advice, we will have a meeting with VCS team so everybody has a better understanding off what is going on. The decision is made by the client's to bring in a reseller or not.   I was informed at it was a standalone install prior to visiting the site.

    primary node

    root@srv-vrts-n1 NetBackup_7.1_LinuxR_x86_64]# ./install

    Symantec Installation Script
    Copyright 1993 - 2011 Symantec Corporation, All Rights Reserved.

            Installing NetBackup Server Software

    Do you wish to continue? [y,n] (y) y

    The NetBackup and Media Manager software is built for use on LINUX_RH_X86 hardware.
    Do you want to install NetBackup and Media Manager files? [y,n] (y)

    NetBackup and Media Manager are normally installed in /usr/openv.
    Is it OK to install in /usr/openv? [y,n] (y) y

    Reading NetBackup files from /home/nbu/NetBackup_7.1_LinuxR_x86_64/linuxR_x86/anb

    usr/openv/db/
    ...
    ...
    Product NB is installed and will be registered.

    Updating LiveUpdate registration now...this may take some time.

    A NetBackup Server or Enterprise Server license key is needed
    for installation to continue.

    Enter license key:xxxxx

    All additional keys should be added at this time.
    Do you want to add additional license keys now? [y,n] (y) n

    Use /usr/openv/netbackup/bin/admincmd/get_license_key
    to add, delete or list license keys at a later time.

    Installing NetBackup Enterprise Server version: 7.1

    If this machine will be using a different network interface than the
    default (srv-vrts-n1), 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 "srv-vrts-n1" as the configured
    NetBackup server name of this machine? [y,n] (y) n

    Enter the name of this NetBackup server: srv-vrts-nb

    Is srv-vrts-nb the master server? [y,n] (y) y
    Do you want to create a NetBackup cluster? [y,n] (y) y

    *******************************************************************************
    This script will only handle global configuration options.
    If you need Local configuration, enter values for the node
    you are currently on. Then after the script is completed
    use the web GUI or ha commands to enter local
    *******************************************************************************

    Enter the VCS group name for the NetBackup group (nbu_group):
    Enter the VCS resource name for NetBackup (nbu_server):

    ******************************************************************************

    VCS group name for the NetBackup group is :nbu_group
    VCS resource name for NetBackup is : nbu_server

    Is this correct? [y,n]: y

    ******************************************************************************

    Enter the VCS resource name for the NetBackup server IP (nbu_ip):
    Enter the netmask for the NetBackup service (255.255.255.0):

    ******************************************************************************

    You entered the following for Virtual IP configuration
    NetBackup IP Resource name = nbu_ip
    NetBackup virtual name = srv-vrts-nb
    The IP address to use with NetBackup = 192.168.200.43
    The IP address type( IPv4 or IPv6 ) = IPv4
    The netmask to use with NetBackup = 255.255.255.0
    Is this correct? [y/n]: y

    ******************************************************************************

    NetBackup will run on the following nodes: srv-vrts-n1  

    IP address of the node srv-vrts-n1  = 192.168.200.39
    Is this correct? [y,n]: y

    ******************************************************************************

    Enter the VCS resource name for the NIC (nbu_nic):
    Enter the network device for NetBackup: eth0   

    ******************************************************************************

    You entered the following for Network configuration
    NetBackup NIC VCS resource name = nbu_nic
    The NIC to use with NetBackup on srv-vrts-n1 = eth0
    Is this correct? [y/n]: y

    ******************************************************************************

            Initial Cluster Configuration for NetBackup Server takes only
            one shared disk.

            Multiple disks, if needed,  can be configured after the inital
            cluster configuration completes. After the installation is
            complete, Run /usr/openv/netbackup/bin/cluster/cluster_mvnbdb
            to configure multiple disks.

    (I’m assuming that we need to make changes here for the global VCS config with VVr catalog VVR replication)

     Select your VCS disk configuration.
            1. Disk Group
            2. None (We will just configure a mount for NetBackup)

    Enter the disk configuration: 2
    Enter the VCS resource name for the NetBackup shared disk mount point
            (nbu_mount):
    Enter the mount point for the NetBackup disk (/opt/VRTSnbu): /nbu
    Enter the Block Device for the NetBackup disk: /dev/vx/dsk/nbu_shared/vxNBUvol
    Enter the FS Type for the NetBackup file system: vxfs
    Enter any mount options you would like passed to the NetBackup disk
            (Enter for none): rw
    Enter any fsck options you would like passed to the NetBackup disk
            (Default is -y. This must be included if options are added):

    ******************************************************************************

    VCS NetBackup Mount Point resource name = nbu_mount
    NetBackup Mount Point = /nbu
    Block Device = /dev/vx/dsk/nbu_shared/vxNBUvol
    File System type = vxfs
    Mount options = rw
    fsck options = -y
    Is this correct? [y,n]: y

    ******************************************************************************

    Creating NetBackup Group....
    Setting up NetBackup limitations on srv-vrts-n1
    Adding NetBackup type to VCS...
    Adding nbu_group
    Adding nbu_nic to nbu_group
    Adding nbu_ip to nbu_group
    Adding nbu_mount to nbu_group
    Linking nbu_ip to nbu_nic
    Linking nbu_server to nbu_ip
    Linking nbu_server to nbu_mount
    Probing resources on srv-vrts-n1.
    Waiting for NIC resource to finish probing
           Probe completed for  nbu_nic resource on node srv-vrts-n1.
                    The resource is ONLINE
    Waiting for IP resource to finish probing
           Probe completed for  nbu_ip resource on node srv-vrts-n1.
                    The resource is ONLINE
    Waiting for Disk Group and Volume resources to finish probing
    Waiting for MOUNT resources to finish probing
           Probe completed for  nbu_mount resource on node srv-vrts-n1.
                    The resource is OFFLINE
    Waiting for resources to come online
    The NetBackup VCS configuration was successful!
    Waiting for virtual name to come online...

    Media servers can be added during this installation or
    to a NetBackup environment after installation completes.
    Refer to the NetBackup Administrator's Guide, Volume I for
    more information.

    Do you want to add any media servers now? [y,n] (n) n

    Checking network connections.
    bp.conf: IP_ADDRESS_FAMILY = AF_INET: default value, no update needed

    Sending SIGHUP to xinetd process.

    Reloading configuration:                                   [  OK  ]

    NetBackup maintains a centralized catalog (separate from the image
    catalog) for data related to media and device configuration, device
    management, storage units, hosts and host aliases, media server status,
    NDMP credentials, and other information.  This is managed by the
    Enterprise Media Manager server.

    Enter the Enterprise Media Manager server (default: srv-vrts-nb):
    Converting STREAMS files.  This may take a few minutes.

    STREAMS files conversion is complete.

    Successfully updated the session cache parameters.
    Starting the NetBackup network daemon.
    Starting the NetBackup client daemon.
    Starting the NetBackup SAN Client Fibre Transport daemon.
    Creating /usr/openv/tmp/sqlany

    Installed SQL Anywhere Version 11.0.1.2475
    Installation completed successfully

    set_value: Key "AZDBPasswordFilePath" successfully updated
    AZ database setup complete.

    Database server is NB_srv-vrts-nb
    Creating the NetBackup database.
    Creating NetBackup staging directory in: /nbu/db/staging
    Creating /nbu/db/staging
    Starting the NetBackup database.
    Authenticating the NetBackup database.
    VXDBMS_NB_DATA entry in bp.conf updated successfully.
    Setting of database authentication for NBDB successful.
    Change of dba password for NBDB successful.
    Creating the NetBackup database files.
    Creating the NetBackup EMM schema.
    Verifying the running version of NBDB ...
    NBDB version 7.1.0.0 verified.
    Nothing to upgrade. Version unchanged.
    Database [NBDB] validation successful.
    Database [NBDB] is alive and well on server [NB_srv-vrts-nb].
    Creating the NetBackup Authorization database.

    Starting the NetBackup Event Manager.

    Starting the NetBackup Audit Manager.

    Starting the NetBackup Deduplication Manager.
    Starting the NetBackup Deduplication Engine.

    Starting the NetBackup database manager process (bpdbm).

    Creating Directive Set for LotusNotes
    Creating Directive Set for MS_Exchange_Mailbox
    Creating Directive Set for MS_Exchange_Database
    Creating Directive Set for MS_Exchange_Public_Folders
    Creating Directive Set for MS_Exchange_Database_Availability_Groups
    Creating Directive Set for MS_SharePoint_Portal_Server
    Creating Template Set for Oracle_RMAN
    Creating Template Set for Oracle_XML_Export
    Creating Template Set for DB2
    Creating Directive Set for Windows2003
    Creating Directive Set for Windows2008
    Creating Directive Set for Enterprise_Vault_7.5
    Creating Directive Set for Enterprise_Vault_8.0
    Creating Directive Set for Enterprise_Vault_9.0
    Creating Directive Set for Enterprise_Vault_10.0

    Converting snapshot policies:

    Policy conversion summary:
            Number of original policies:                    0
            Number of non-snapshot policies skipped:        0
            Number of policies not needing conversion:      0
            Number of policies converted to
              'auto' snapshot method:                       0
            Number of policies converted:                   0

    Updating client hardware definitions:

    Hardware update conversion summary:
            Number of policies processed:                         0
            Number of policies with affected clients:             0
            Number of clients processed:                          0
            Number of clients converted:                          0
            Number of Disaster Recovery flags cleared:            0

    Starting the NetBackup compatibility daemon.
    Starting the NetBackup Enterprise Media Manager.
    Starting the NetBackup Resource Broker.

    Populating the database tables.  This will take some time.

    Starting the Media Manager device daemon processes.

    Do you want to start the NetBackup bprd process so
    backups and restores can be initiated? [y,n] (y) y
    Starting the NetBackup request daemon process (bprd).
    Starting the NetBackup Job Manager.
    Starting the NetBackup Policy Execution Manager.
    Starting the NetBackup Storage Lifecycle Manager.
    Starting the NetBackup Remote Monitoring Management System.
    Starting the NetBackup Key Management daemon.
    Starting the NetBackup Service Layer.
    Starting the NetBackup Agent Request Server.
    Starting the NetBackup Bare Metal Restore daemon.
    Starting the NetBackup Vault daemon.
    Starting the NetBackup Service Monitor.
    Starting the NetBackup Bare Metal Restore Boot Server daemon.

    OpsCenter is the next-generation monitoring, reporting and
    administrative solution designed to centrally manage one or
    more NetBackup installations from a web browser.  Existing
    NetBackup Operations Manager or Veritas Backup Reporter
    installations can be upgraded to OpsCenter.

    If an OpsCenter server already exists in your environment
    or you plan to install one, enter the real hostname of that
    OpsCenter server here.  Do not use a virtual name.  If you
    do not want this local machine to be an OpsCenter server,
    enter NONE.

    Enter the OpsCenter server (default: NONE):

    NetBackup daemons will be shut down to complete the
    NetBackup cluster configuration.

    Updating /usr/openv/volmgr/vm.conf
    We have detected that this is an EMM server.
    Adding nbemm, nbrb & NB_dbsrv to the list of monitored daemons...
    Starting the NetBackup agent on srv-vrts-n1
    Waiting 240 seconds for nbu_group to come online...
    NetBackup is online...

    NetBackup server installation complete.

    File /usr/openv/tmp/install_trace.11467 contains a trace of this install.
    That file can be deleted after you are sure the install was successful.
     

    secondary node

    [root@srv-vrts-n2 NetBackup_7.1_LinuxR_x86_64]# ./install

    Symantec Installation Script
    Copyright 1993 - 2011 Symantec Corporation, All Rights Reserved.

            Installing NetBackup Server Software

    Do you wish to continue? [y,n] (y) y

    NetBackup Deduplication software is incorrectly installed.
    /etc/pdregistry.cfg was unexpectedly found.
    Moving to /etc/pdregistry.cfg.2012-04-28_18:11 in order to continue.

    The NetBackup and Media Manager software is built for use on LINUX_RH_X86 hardware.
    Do you want to install NetBackup and Media Manager files? [y,n] (y) y

    NetBackup and Media Manager are normally installed in /usr/openv.
    Is it OK to install in /usr/openv? [y,n] (y) y

    Reading NetBackup files from /home/nbu/NetBackup_7.1_LinuxR_x86_64/linuxR_x86/anb

    usr/openv/db/
    ...
    ...

    Product NB is installed and will be registered.

    Updating LiveUpdate registration now...this may take some time.

    A NetBackup Server or Enterprise Server license key is needed
    for installation to continue.

    Enter license key:xxx

    All additional keys should be added at this time.
    Do you want to add additional license keys now? [y,n] (y) n

    Use /usr/openv/netbackup/bin/admincmd/get_license_key
    to add, delete or list license keys at a later time.

    Installing NetBackup Enterprise Server version: 7.1

    If this machine will be using a different network interface than the
    default (srv-vrts-n2), 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 "srv-vrts-n2" as the configured
    NetBackup server name of this machine? [y,n] (y) n

    Enter the name of this NetBackup server: srv-vrts-nb

    Is srv-vrts-nb the master server? [y,n] (y) y

    This is the list of existing NetBackup cluster groups:
    nbu_group

    Do you wish to join this existing NetBackup cluster group? [y,n] (y) y
    Adding node srv-vrts-n2 to NetBackup Group nbu_group
    VCS
    Enter the network device for NetBackup on srv-vrts-n2: eth0

    You entered the following for Network configuration
    The NIC to use with NetBackup on srv-vrts-n2 = eth0
    The IP address for srv-vrts-n2 is : 192.168.200.23

    Is this correct? [y/n]: y

    Media servers can be added during this installation or
    to a NetBackup environment after installation completes.
    Refer to the NetBackup Administrator's Guide, Volume I for
    more information.

    Do you want to add any media servers now? [y,n] (n) n
    Sending SIGHUP to xinetd process.

    Reloading configuration:                                   [  OK  ]

    Successfully updated the session cache parameters.
    Starting the NetBackup network daemon.
    Starting the NetBackup client daemon.
    Creating /usr/openv/tmp/sqlany

    Installed SQL Anywhere Version 11.0.1.2475
    Installation completed successfully

    set_value: Key "AZDBPasswordFilePath" successfully updated
    AZ database setup complete.

    OpsCenter is the next-generation monitoring, reporting and
    administrative solution designed to centrally manage one or
    more NetBackup installations from a web browser.  Existing
    NetBackup Operations Manager or Veritas Backup Reporter
    installations can be upgraded to OpsCenter.

    If an OpsCenter server already exists in your environment
    or you plan to install one, enter the real hostname of that
    OpsCenter server here.  Do not use a virtual name.  If you
    do not want this local machine to be an OpsCenter server,
    enter NONE.

    Enter the OpsCenter server (default: NONE):

    NetBackup server installation complete.

    File /usr/openv/tmp/install_trace.21363 contains a trace of this install.
    That file can be deleted after you are sure the install was successful.
    [root@srv-vrts-n2 NetBackup_7.1_LinuxR_x86_64]#

     

     

    Regards