Decoupled Install - UNIX

Perform the Decoupled Installation

Decoupled install is performed without involving the CommServe until you are ready to add the Client and/or MediaAgent to the CommCell. Once all necessary physical connections are established, the computer can be added to the CommCell. This feature can be useful, for instance, if you want to pre-image computers with the software at a central location, then ship them to where they will be used in the enterprise.

Use the following procedure to install the components in decoupled mode.

  1. Logon to the client computer as root.
  2. Run the following command from the installation package that was created using the Download Manager.

    ./cvpkgadd

    If the installation package was copied to a DVD, run the following command to mount the DVD:

    mount -t iso9660,udf /dev/dvd /mnt/dvd

    You can also run the installation command as a SUDO user with root privileges:

    ./sudo cvpkgadd

    To add a SUDO user to /etc/sudoers, see Adding SUDO Users with Root Privileges to Log On to a UNIX Client.

  3. The product banner and other information is displayed.

    Press Enter.

  4. Read the license agreement. Type y and press Enter.
  5. Type 2 and press Enter.

    Selecting Unix Setup Task
    Please select a setup task you want to perform from the list below:
    Advanced options provide extra setup features such as creating custom package,recording/replaying user selections and installing External Data Connector software.
    1) Install data protection agents on this computer
    2) Advanced options
    3) Exit this menu
    Your Choice: [1] 2

  6. Type 2 and press Enter.

    Selecting Unix Setup Advanced Options
    Please select a setup task you want to perform from the list below:
    [Custom Package Creator]
    1) Create a custom install package
    [De-coupled Installer]
    2) Pre-install software Components (De-coupled Mode)
    [Done]
    3) Exit this menu
    Your Choice: [1] 2

  7. Type 3 and press Enter.

    Selecting Instance to Install
    There are several SnapProtect instances currently configured on this host. You can either install a new instance going to yet another CommServe, or make changes(configure a new cluster group, install a new SnapProtect subsystem) to an existing instance.

    1) Adding new agents to Instance001(CS=172.19.97.79)
    2) Adding new agents to Instance002(CS independent)
    3) Create a new instance of SnapProtect
    4) Exit this menu

    Your Choice: [1] 3

  8. The default network interface name of the client computer is displayed if the computer has only one network interface (NIC card), press Enter to accept.
    • If the computer has multiple network interfaces, enter the interface name that is preferred for communication with the CommServe, and then press Enter.

    The interface names and IP addresses depend on the computer in which the software is installed and may be different from the example shown.

    Setting Client/Physical Machine Host Name
    We found one network interface available on your machine. We will associate it with the client being installed, and it will also be used by the CommServe to connect to the client. Note that you will be able to additionally customize Datapipe Interface Pairs used for the backup data traffic later in the SnapProtect Java GUI.
    Please check the interface name below, and make corrections if necessary:
    Client/Physical Machine Host Name: [myclient.company.com]

  9. The local name of the client computer is displayed, press Enter to accept.

    • If necessary you can also enter a new (friendly) name for the client, and then press Enter. This name will be used in the CommCell and will also be displayed in the CommCell Console.
    • Do not use spaces when specifying a new name for the client.

    Setting Client Name
    Please specify the client name for this machine.
    It does not have to be the network host name: you can enter any word here without spaces. The only requirement is that it must be unique on the CommServe.
    Physical Machine Client name: [myclient]

  10. Type the number associated with File System and press Enter.

    Selecting Modules to Install.
    [ ] 1) File System Core [1002] [CVGxBase]
    [ ] 2) File System [1101] [CVGxIDA]
    [ ] 3) MediaAgent [1301] [CVGxMA]
    [ ] 4) Documentum iDataAgent [1126] [CVGxDctmIDA]
    [ ] 5) Oracle iDataAgent [1204] [CVGxOrIDA]
    [ ] 6) SAP for Oracle [1205] [CVGxOrSAP]
    [ ] 7) SAP for MaxDB [1206] [CVGxSAPMAXDB]
    [ ] 8) Informix iDataAgent [1201] [CVGxIfIDA]
    [ ] 9) Sybase iDataAgent [1202] [CVGxSybIDA]
    [ ] 10) DB2 iDataAgent [1207] [CVGxDB2]
    [ ] 11) MySQL iDataAgent [1208] [CVGxMySQL]
    [ ] 12) PostGres iDataAgent [1209] [CVGxPostGres]
    [ ] 13) Lotus Notes Database iDataAgent [1051] [CVGxLndbIDA]
    >) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>
    [a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]
    Enter number(s)/one of "a,n,r,q,d,>,<,?" here: 2

  11. Type d for Done, and press Enter.

    Selecting Modules to Install.
    [ ] 1) File System Core [1002] [CVGxBase]
    [X ] 2) File System [1101] [CVGxIDA]
    [ ] 3) MediaAgent [1301] [CVGxMA]
    [ ] 4) Documentum iDataAgent [1126] [CVGxDctmIDA]
    [ ] 5) Oracle iDataAgent [1204] [CVGxOrIDA]
    [ ] 6) SAP for Oracle [1205] [CVGxOrSAP]
    [ ] 7) SAP for MaxDB [1206] [CVGxSAPMAXDB]
    [ ] 8) Informix iDataAgent [1201] [CVGxIfIDA]
    [ ] 9) Sybase iDataAgent [1202] [CVGxSybIDA]
    [ ] 10) DB2 iDataAgent [1207] [CVGxDB2]
    [ ] 11) MySQL iDataAgent [1208] [CVGxMySQL]
    [ ] 12) PostGres iDataAgent [1209] [CVGxPostGres]
    [ ] 13) Lotus Notes Database iDataAgent [1051] [CVGxLndbIDA]
    >) >>>>>>>>>>>> NEXT PAGE >>>>>>>>>>>>
    [a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]
    Enter number(s)/one of "a,n,r,q,d,>,<,?" here: 2

  12. Press Enter.

  13. Deciding if to Config for Laptop or Desktop Backups
    Do you want to configure the iDataAgent for laptop or desktop backups?
    Config for Laptop or Desktop Backups? [no]

  14. Press Enter.

    Deciding if to Install Agents for Restore Only
    Do you want to install the agents for restore only without consuming licenses?
    Install Agents for Restore Only? [no]

  15. Verify the default path for software installation.

    Press Enter.

    If necessary, enter a path to modify the default path and press Enter.

    • Do not install the software to a mapped network drive
    • Do not use the following characters when specifying the path:

      !@#$%^&*():/?\

    • It is recommended that you use alphanumeric characters only

    Preparing Installation Directory
    Please specify where you want us to install SnapProtect binaries.
    It must be a local directory or NFS and there should be at least 281MB of free space available. All files will be installed in a "snapprotect" subdirectory, so if you enter "/opt", the files will actually be placed into "/opt/snapprotect".
    Installation Directory: [/opt]

  16. Verify the default path for log files.

    Press Enter.

    If necessary, enter a path to modify the default path and press Enter.

    • Do not use the following characters when specifying the path:

      !@#$%^&*():/?\

    • It is recommended that you use alphanumeric characters only
    • All the modules installed on the computer will store the log files in this directory.

    Preparing Log Directory
    Please specify where you want to keep SnapProtect log files.
    It must be a local directory or NFS share and there should be at least 100MB of free space available. All log files will be created in a "snapprotect/Log_Files" subdirectory, so if you enter "/var/log", the logs will actually be placed into "/var/log/snapprotect/Log_Files".
    Log Directory: [/var/log]

  17. Press Enter.

    Deciding If to Use a Unix Group
    Most of SnapProtect processes run with root privileges, but some are launched by databases and inherit database access rights. To make sure that registry and log files can be written to by both kinds of processes we can either make such files world-writeable or we can grant write access only to processes belonging to a particular group, e.g. a "snapprotect" or a "dba" group.
    We highly recommend now that you create a new user group and enter its name in the next setup screen. If you choose not to assign a dedicated group to SnapProtect processes, you will need to specify the access permissions later.
    If you're planning to backup Oracle DB you should use "dba" group.
    Would you like to assign a specific group to Software? [yes]

  18. Type the Group name and press Enter.

    Press Enter again.

    Setting Unix Group
    Please enter the name of the group which will be assigned to all SnapProtect files and on behalf of which all SnapProtect processes will run.
    In most of the cases it's a good idea to create a dedicated "snapprotect" group.
    However, if you're planning to use Oracle iDataAgent or SAP Agent, you should enter Oracle's "dba" group here.
    Group name: testgrp1
    REMINDER
    If you are planning to install SnapProtect Informix, DB2, Sybase or Lotus Notes iDataAgent, please make sure to include Informix, DB2, etc. users into group "testgrp1"..
    Press <ENTER> to continue...

  19. Type d for done with the selection and press Enter.

    Setting Access Permissions for Group and Other Users
    Installer will assign full access rights to root user for all installed SnapProtect files and its processes.
    For group and any other users, you can specify the access permissions now.
    If you did not assign a dedicated group in previous step, make sure you specify sufficient access rights for other users if you are also planning to install SnapProtect agents involving third party software protection.
    [X] 1) Allow read permission to group users
    [X] 2) Allow write permission to group users
    [X] 3) Allow execute permission to group users
    [X] 4) Allow read permission to other users
    [ ] 5) Allow write permission to other users
    [X] 6) Allow execute permission to other users
    [a=all n=none r=reverse q=quit d=done >=next <=previous ?=help]
    Enter number(s)/one of "a,n,r,q,d,>,<,?" here: d

  20. The default port numbers used for CommCell communication is displayed. If necessary, you can modify the port numbers.

    Press Enter.

    Setting Instance Port Number of cvd
    Every instance of SnapProtect should use a unique set of network ports to avoid interfering with other instances running on the same machine.
    The port numbers selected must be from the reserved port number range and have not been registered by another application on this machine.
    Please enter the port numbers.
    Port Number for CVD : [8400]

  21. Press Enter.

    Setting Instance Port Number of EvMgrC
    Every instance of SnapProtect should use a unique set of network ports to avoid interfering with other instances running on the same machine.
    The port numbers selected must be from the reserved port number range and have not been registered by another application on this machine.
    Please enter the port numbers.
    Port Number for CVD: 8400
    Port Number for EvMgrC: [8402]

  22. Do one of the following:
    • If firewall configuration is not required, press Enter.
    • If this computer and the CommServe is separated by a firewall, type Yes and then press Enter.

    For firewall options and configuration instructions, see Firewall Configuration.

    Deciding If to Configure Firewall

    You need to configure firewall settings if there is a firewall between this client and the CommServe.
    Is there a firewall between this client and the CommServe? [no]

  23. Press Enter.

    CommServe name can be specified later on.

    Setting CommServe Host Name
    Please specify hostname of the CommServe below. Make sure the hostname is fully qualified, resolvable by the name services configured on this machine.
    CommServe Host Name:

  24. Press Enter.

    Deciding if to Install Decoupled
    If you do not enter a CommServe name, the installer will treat it as a decoupled install. Please confirm this is really what you want.
    Do you want to treat the install as a decoupled install? [yes]

  25. If you have enabled per-client certificate on CommServe, type y and press Enter.

    Else, press Enter.

    Specifying If CommServe Per-Client Certificate is Enabled
    If you have checked "Force per-client certificate authentication on CommServe" on the CommServe or Proxy, you need to provide installer with a Temp Certificate.
    This Temp Certificate can be obtained by opening "Certificate Administration Applet" from the Java GUI's Control Panel, clicking "Temp Certificate" button, selecting newly created client in the popped up window and copying/pasting generated certificate to a local file accessible from this installer.
    Have you enabled per-client certificate authentication on CommServe? [no]

  26. To review the setup, you may find the following logs useful if available:

    Thank you for choosing  NetApp, Inc. Systems, Inc. SnapProtect.
    [LOG INFO] To review the setup, you may find the following logs useful if available:
    (1) logs under /tmp/.gxsetup
    (2) install.log|env and UpdateInfo.log|env under Log Directory
    (3) logs under /var/log/.gxsetup/10-116

Register the Client Computer

Use one of the following methods to register your client computer:

Method 1: Register a Client Using the CommCell Console

Method 2: Register a Client from the Command Line

Register a Client Using the CommCell Console

Choose the procedure that is applicable to your CommCell environment configuration:

On a Non-Firewall Environment

  1. From the CommCell Browser, right-click the Client Computers node, and then click New Client > File System > Unix.

  2. In the Host Name box, type the host name of the client computer.

    Select the Fetch the configuration information from the client that is already installed in decoupled mode check box and then click the Connect to a client and get its configuration button. In the CVD port on client box, specify the CVD port number that was entered during the decoupled installation on the client computer.

    Click Next

  3. Click Next.

    If you want to override the client name, select the Overrides the Client name checkbox and then specify the client name in the Client name box. This name will be displayed in the CommCell Console.

  4. Click Finish.

Once the client registration is complete, the client computer will be listed under the Client Computers in the CommCell Console.

On a Firewall Environment

  1. Add the client to the CommCell Console by using the following steps:

    Note: You can repeat this operation to add more clients.

    1. From the CommCell Browser, right-click the Client Computers node, and then click New Client > File System > Unix.

      The New Unix Client dialog box is displayed.

    2. On the Configure Client page, enter a Client Name and Host Name of the computer where you installed the SnapProtect software and click Next.
    3. On the Optional Data page, click Next.
    4. On the Summary page, click Finish.
  2. Configure the appropriate SnapProtect firewall settings on the client (or clients) that you added to the CommCell Console.

    For instructions, see Configuring Firewall Using Proxy for Laptop Backup. For more information on firewall configurations, see Firewall: Overview.

  3. Configure the nDisable_CVFWD registry key on the client and set it to 0.

    This key enables the client to establish communications with the CommServe computer.

    Tip: If you have multiple clients, use a script or a third-party application to push the additional setting to all the clients.

  4. On the CommServe computer, run the command to register the clients.
    1. On the command line, go to the Software_Installation_Directory/Base folder and run the qlogin command to access the CommServe database.
    2. Run the registration command for each of the clients that you configured.

      qoperation register -hn clientName -dock yes -roaming yes

    Tip: If you need to register multiple clients, use a script or a third-party application to run the registration command on all the clients.

Register a Client from the Command Line

Use the following steps to register client computers with the CommServe after a decoupled install.

  1. Log onto a client computer.
  2. Run the following command from the Installation_Directory/snapprotect/Base directory after substituting the parameter values.

    If you installed the laptop package as a non-root user, you must run the galaxy_vm command before running the SIMCallWrapper command. The galaxy_vm command is located in the Installation_Directory/snapprotect directory.

    ./SIMCallWrapper -OpType 1000 -CSHost <CS Host Name> -clientname <Client Name> -output <Location for XML File>

    Usage of the command is:

    SIMCallWrapper -OpType 1000 [-instance <instance name>] [-user <User Name>] [-password <User password>] [-passwordEncrypted]] [-CSName <CS Name>] [-CSHost <CS Host Name>] [-ClientName <Client Name>] [-ClientHostName <Client Host Name>] [-ClientGroup <Client Group>] [-subclientPolicy <Subclient Policy>] [-StoragePolicy <Storage Policy>] [-overwriteClientInfo] [-resetNetworkPassword] [-regPath <alternative registry path>] [-instanceFor1Touch <instance>] -output <xmlFileName> [-Instance <Instance Name>] [-skipCertificateRevoke] [-registerme]

  3. Available Parameters

    The following table displays all the parameters you can use with the commands mentioned above:

    Parameter Description of Parameter Values
    -opType 1000 * Name of the operation type to register the client to the CommServe.
    -clientName * Name of the client computer
    -output * Location for xml file
    -instance Instance of the CommServe on which the command is run.
    -user Name of a CommCell user account with sufficient permissions to install clients. This parameter is required if user authentication is enabled in the CommCell.

    Note: If the user is part of a domain, specify the user name as 'domain\user'.

    -password Password for the user account provided.
    -CSName Name of the CommServe
    -CSHost * Host name of the CommServe
    -clientHostName Host name of the client computer
    -clientGroup Name of the client group
    -subclientPolicy Nam of the subclient policy
    -storagePolicy Name of the storage policy
    -overwriteClientInfo It overwrites client name or host name if there is a mismatch between the two. It's either ON or OFF.
    -regPath Name of the alternative registry path
    -instanceFor1Touch Name of the instance for 1-Touch
    -Instance Name of the instance

    * marked parameters are mandatory to run the command. Other parameters are optional.