SnapProtect Pre-Deployment Test - UNIX

Table of Contents

Installation

  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.

    This screen will appear only on AIX and Solaris platform.

    Selecting 32bit or 64bit Base
    This machine supports both 32 bit and 64 bit binaries. By default, we will
    install 32 bit binary set that has full support for all the modules included in
    this package. Please note that 64 bit binary set currently only support limited
    modules
    1) All platforms(32 bit)
    2) FS and MA only(64 bit)
    Your Choice: [2]

  7. 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

  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 MediaAgent and then 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 3

  11. Type d for Done, and press Enter.

    Selecting Modules to Install.
    [ ] 1) File System Core [1002] [CVGxBase]
    [X] 2) File System [1101] [CVGxIDA]
    [X] 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: d

  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.

    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.

    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

Perform Test

The following procedure provides step-by-step instructions to configure and test your snap environment.

  1. Create a Lun on the array and map it to the client computer.

    Ensure that the Lun is visible on the client computer as a device node.

  2. Use the mapped device node to create a Volume Group.

    For example, use the following command:

    On AIX

    mkvg –y vg_name hdisk12

    On Linux:

    pvcreate /dev/sdd
    vgcreate vg_name /dev/sdd
    vgchange –a y vg_name

  3. Create a Logical Volume in the Volume Group.

    For example, use the following command:

    On AIX:

    mklv -y lv_name -t jfs2 vg_name 2G hdisk29

    On Linux:

    lvcreate –n lv_name –L 2G vg_name

  4. Create a File System on the Logical Volume.

    For example, use the following command:

    On AIX:

    crfs -v jfs2 -a logname=INLINE -d lv_name -m /snaptest

    On Linux:

    mkfs -t ext3 /dev/vg_name/lv_name

  5. Use the following commands to run the Snaptest tool:
    • Locate /opt/Simpana folder by running the below command.

      [root@ntr Simpana]# cd /opt/Simpana/Base

    • [root@ntr Simpana]# ./SnapTest

    If you have multiple instance installed, run the following command for SnapTest tool:

    [root@ntr Simpana]# ./SnapTest -vm Instance<XXX>

  6. Press Enter.

    This tool helps to perform operations such as...
    -> Automatic Snap Tests
    -> Individual Snap Tests
    -> Hardware Snapshot Engine Detection
    -> SCSI Inquiry
    -> Scan HBA/IQN Adapters
    NOTE: Please make sure that the mount points used for this test are not being used by any other application. If they are in use, it may cause data corruption or data loss. Please refer to our online documentation for list of supported Operating systems, Hardware Snapshot engines and File systems.
    Press <ENTER> to continue...

  7. Press Enter.

    SnapTest Version Main Menu
    --------------------------------------
    Perform automatic snap tests or launch Advanced Operations such as Array Configuration, Snapshot Engine Detection etc. Automatic snap tests take one or more source mounts to snap and performs series of Snap related operations on them. In order to perform these snap operations, array configuration such as array id, control host and user credentials is required. If no array configuration is found, Automatic Snaptests takes you to Array Configuration screen.
    1. Automatic Snap Tests
    2. Advanced Operations
    0. Exit
    Choose your option [1]:

  8. Type Y and press Enter.

    SnapTest Automatic Snap Operations
    -----------------------------------------------------
    We will perform the following operations on the given mount point[s].
    - Create snapshots
    - Mount snapshots
    - Unmount snapshots
    - Revert original volumes to snapshots
    - Delete snapshots
    WARNING:
    Revert is inherently risky and can cause data loss.
    Do you want to perform revert operation as part of this test? [Y/N] [N] : Y

    For NetApp, it is recommended that the revert operation is not tested using the automatic test. Revert should be tested using manual operations.

  9. Specify the path of mount directory and press Enter.

    Enter all the mount points that you want to test.

    Enter source mount paths to snap (separate by commas, if more than one) : /snap1

  10. Press Enter to add the detected array.

    SnapTest Automatic Snap Operations
    -----------------------------------------------------------
    Source Mount Point : /snap1
    Detecting underlying devices... /dev/sdh
    Detecting snapshot engine... <Array Name> SNAP
    No [<Array Name> SNAP] arrays found in database. Array configuration is required to do snap operations.
    Do you want to add <Array Name> Array? [Y/N] [Y] :

  11. Specify the following information for the detected array:
    • Array ID
    • Control host name/ip
    • User name
    • Password
    • Reenter password
    • Device group
    • Use only devices belonging to the above device group [y/n]

    SnapTest Add Array
    -----------------------------------
    Vendor : <Array Name>
    Enter array ID :
    Enter control host name/ip :
    Enter user name :
    Enter password :
    Enter password again :
    Enter device group :

  12. The setup is tested for snapshot operations (create, mount, unmount, revert, and delete).

    The snap test is now complete. You can now use this environment for performing SnapProtect operations.

    SnapTest Automatic Snap Operations
    ------------------------------------------------------------
    Mount points to be snapped : /snap1
    Engine for /snap1 : <Array Name> SNAP
    Creating snapshot... SUCCESS
    Snapshot name : SP_805326_805326_-1
    Mounting snapshot...SUCCESS
    Unmounting snapshot... SUCCESS
    Reverting to snapshot... SUCCESS
    Deleting snapshot... SUCCESS
    Congratulations!!! Automatic Snap test completed successfully.
    Press <ENTER> to continue...

  13. Type 0 and press Enter.

    SnapTest Version Main Menu
    --------------------------------------
    Perform automatic snap tests or launch Advanced Operations such as Array Configuration, Snapshot Engine Detection etc. Automatic snap tests take one or more source mounts to snap and performs series of Snap related operations on them. In order to perform these snap operations, array configuration such as array id, control host and user credentials is required. If no array configuration is found, Automatic Snaptests takes you to Array Configuration screen.
    1. Automatic Snap Tests
    2. Advanced Operations
    0. Exit
    Choose your option [1]:

Initial deployment and successful run of SnapProtect backup may take around 4 weeks due to the various environment dependencies. The following parameters are known to affect the deployment and initial run and hence need a thorough evaluation:

  • Firmware versions on the array
  • Device types
  • Mode of access
  • Security configuration
  • Operating Systems interacting with the storage array
  • Application layout on the storage array LUNs