dsmisi4spp

Preface

This publication contains information about installation and configuration for General Storage dsmISI4spp software.

dsmISI4spp is the easiest and most effective way to address Dell EMC PowerScale (formerly known as Dell EMC Isilon® Scale-Out NAS) clusters, hereinafter referred to as Isilon as a target storage device from Spectrum Protect Plus vSnap servers, hereinafter referred to as SPP and vSnap.

Target Audience

The information included in this guide is targeted at a Linux and/or SPP administrator tasked with implementing vSnap storage pools on Isilon storage.

Components

dsmISI for SPP consists of a set of tools to configure all aspects of an NFS based access from SPP to Isilon storage clusters.

Prerequisites

dsmisi4spp has to be installed on each vSnap that should use Isilon storage as a storage pool. The following prerequisites have to be fulfilled:

• Installed IBM Spectrum Protect Plus vSnap OVA 10.1.3 or later.

• Working IPv4 connection between the vSnap and the Isilon cluster.

• Configured Isilon OneFS.

Planning

The following planning sheet describes the information needed to configure dsmisi4spp.

Information	Examples
Isilon IP Pool	subnet0:data1-pool, subnet0:data1-pool
Isilon Management IP	10.10.10.120
Isilon Management User	root, dsmisi
Isilon export directory	/ifs/spp
Isilon mount directory	/spp, /isilon
Isilon mount subdirectory	(/spp/isiclus/000X/)vSnap1Pool/
Number and size of .img-Files	1024 * 100 (equals 100 TB)

Installation

The installation of dsmisi4spp mostly takes place on the vSnap, so make sure to have the serveradmin credentials ready.

1. Copy the dsmisi4sppXXX.tar-File to your vSnap server:

   user@hostname dsmisi4spp320 % scp dsmisi4spp320.tar serveradmin@172.16.49.167:/home/serveradmin
   restricted access
   serveradmin@172.16.49.167's password:
   dsmisi4spp320.tar                                                                         100%  156kb   4.3mb/s   00:00
   

2. Unzip the package on the vSnap server:

   [serveradmin@localhost ~]$ tar -xvf dsmisi4spp320.tar
   ._dsmisi-3.2.0.15-0.x86_64.rpm
   dsmisi-3.2.0.15-0.x86_64.rpm
   dsmisi.service
   dsmisi4spp
   dsmisi4spp-setup
   startup
   

3. Become root user:

   [serveradmin@localhost ~]$ sudo -i
   

4. Execute the dsmisi4spp-setup-script and follow the instructions:

   [root@localhost serveradmin]# ./dsmisi4spp-setup
   
   dsmISI Setup for IBM Spectrum Protect Plus
   
   Determining environment...
   Searching for installed components...
   dsmISI is not installed on this machine.
   Searching for required rpm packages in /home/serveradmin...
           Package found: ./dsmisi-3.2.0.19-0.x86_64.rpm
           Installing now...
           Installation ended. Checking status...
   dsmISI was successfully installed (dsmisi-3.2.0.19-0.x86_64).
   
   Cheking for dsmISI configuration...
   Enter name of Isilon cluster to mount (this name can be generic, i.e. MYISILON). Enter Q to quit.:
   isiclus
   An IP address under which the Isilon can be reached is required (i.e. 10.0.20.130). Enter Q to quit.:
   Enter address:
   172.16.49.10
   Enter the subnet and ip pool you want to mount against separated by a colon (i.e. subnet0:pool0). Enter Q to quit.:
   subnet0:pool0
   Enter the export you want to mount (i.e. /ifs/spp). Enter Q to quit.:
   /ifs/spp
   Enter the local path you want to mount Isilon isiclus on (i.e. /spp). Enter Q to quit.:
   /spp
   Writing config file /etc/dsmisi/dsmisi.conf...
   FileLogLevel Warning
   SysLogLevel Warning
   MountArgs rw,hard,proto=tcp,timeo=600,retrans=2,intr,async,actimeo=5
   NfsRsize 1048576
   NfsWsize 1048576
   IsiName isiclus
   IsiMgmtIp               172.16.49.10
   IsiIpPool               subnet0:pool0
   IsiConnectionTimeout    60
   IsiUser                 dsmisi
   IsiMountRootDir         /spp
   IsiExport               /ifs/spp
   Config file /etc/dsmisi/dsmisi.conf written.
   

Next Steps

Try to log in to the isilon as root user by issuing:

ssh dsmisi@172.16.49.10 isi version

If you are prompted for a password, generate a public key by entering ssh-keygen, copy that key to the end of /ifs/home/dsmisi/.ssh/authorized_keys and retry to log in. If logging in to the Isilon as user dsmisi works without being prompted, continue with dsmisi4spp, while the values highlighted in yellow have to be your actual values determined in the planning.

Configuration

1. Establish a key-based ssh-connection from your vSnap to the Isilon as the service user:

   ssh dsmisi@172.16.49.10 isi version
   ECDSA key fingerprint is SHA256:tVQmJkb9/DfMFH0wDN+HxAPG61AVP7XPL/f5D/V3Pps.
   ECDSA key fingerprint is MD5:86:2f:7f:ee:9c:f9:aa:83:f1:60:55:85:b6:a2:e4:13.
   Are you sure you want to continue connecting (yes/no)? yes
   Warning: Permanently added '172.16.49.10' (ECDSA) to the list of known hosts.
   Password:
   
   ...Cancel the password prompt and generate a ssh-key::
   
   [root@localhost serveradmin]# ssh-keygen
   Generating public/private rsa key pair.
   Enter file in which to save the key (/root/.ssh/id_rsa):
   Enter passphrase (empty for no passphrase):
   Enter same passphrase again:
   Your identification has been saved in /root/.ssh/id_rsa.
   Your public key has been saved in /root/.ssh/id_rsa.pub.
   The key fingerprint is:
   SHA256:iL105RBZE7ttkM6hHqH1n84hLbs08gTju8TvN0gMZpY root@localhost.localdomain
   The key's randomart image is:
   +---[RSA 2048]----+
   …
   +----[SHA256]-----+
   

2. View and copy your newly generated ssh-key:

   [root@localhost serveradmin]# cat /root/.ssh/id_rsa.pub
   ssh-rsa <LOTSOFTEXT> root@localhost.localdomain
   

3. Log on to your ISILON-Cluster as root user and switch to dsmisi-User:

   [serveradmin@localhost ~]$ ssh root@172.16.49.10
   The authenticity of host '172.16.49.10 (172.16.49.10)' can't be established.
   ECDSA key fingerprint is SHA256:tVQmJkb9/DfMFH0wDN+HxAPG61AVP7XPL/f5D/V3Pps.
   ECDSA key fingerprint is MD5:86:2f:7f:ee:9c:f9:aa:83:f1:60:55:85:b6:a2:e4:13.
   Are you sure you want to continue connecting (yes/no)? yes
   Warning: Permanently added '172.16.49.10' (ECDSA) to the list of known hosts.
   Password:
   Last login: Thu Jul  9 20:02:08 2020 from 172.16.49.1
   Copyright (c) 2001-2019 Dell Inc. or its subsidiaries. All Rights Reserved.
   Copyright (c) 1992-2018 The FreeBSD Project.
   Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
           The Regents of the University of California. All rights reserved.
   
   Isilon OneFS v8.2.0.0
   isiclus-1# su – dsmisi
   

4. Append your copied key to the /ifs/home/dsmisi/.ssh/authorized_keys – File and save it:

   isiclus-1% vi /ifs/home/dsmisi/.ssh/authorized_keys -> Append to last line, Save the file.
   

5. Test the ssh-login as dsmisi again:

   [root@localhost serveradmin]# ssh dsmisi@172.16.49.10 isi version
   Isilon OneFS v8.2.0.0 B_8_2_0_0_007(RELEASE): 0x802005000000007:Thu Apr  4 11:44:04 PDT 2019    root@sea-build11-04:/b/mnt/obj/b/mnt/src/amd64.amd64/sys/IQ.amd64.release   FreeBSD clang version 3.9.1 (tags/RELEASE_391/final 289601) (based on LLVM 3.9.1)
   

6. Initialize your vSnap system:

   [root@localhost ~]# vsnap system init
   Installing kernel modules. This may take several minutes...
   Loading kernel modules...
   Creating primary storage pool with default options...
   vSnap system initialized successfully.
   
   ID: 02245023347e462382c7a0980326168e
   INIT STATUS: Ready
   MULTIPOOL SUPPORT: No
   LOCAL REPL SUPPORT: No
   HOSTNAME: localhost.localdomain
   FQDN: localhost
   OS NAME: CentOS Linux
   OS VERSION: 7.6.1810
   API VERSION: 1.0
   VSNAP VERSION: 10.1.5-2056
   NGINX VERSION: 1.12.2-3.el7
   UWSGI VERSION: 2.0.17.1-2.el7
   NFS VERSION: 1.3.0-0.61.el7
   SAMBA VERSION: 4.8.3-4.el7
   ZFS VERSION: 0.8.1-20190813.el7
   CRYPTSETUP VERSION: 2.0.3-5.el7
   ADS DOMAIN: N/A
   ADS SERVER: N/A
   ADS WORKGROUP: N/A
   MAINTENANCE MODE: No
   

7. Mount the Isilon cluster via dsmisi:

   [root@localhost serveradmin]# /opt/generalstorage/dsmisi/bin/dsmisi mount
   Mount processing isiclus.
   [root@localhost serveradmin]# /opt/generalstorage/dsmisi/bin/dsmisi status
   
   dsmisi, version 3.2.0.15 x86_64 (123151920872)
   Copyright (C) 2020 General Storage Software GmbH
   
   Cluster isiclus (v8.2.0.0):
           0001: /spp/isiclus/0001 mounted.
           0002: /spp/isiclus/0002 mounted.
           0003: /spp/isiclus/0003 mounted.
   
   dsmisi status: no I/O server configured.
   

8. Create a path on the Isilon for the vSnap data:

   [root@localhost serveradmin]# mkdir -p /spp/isiclus/0001/sppVsnap/pool
   

9. Use the dsmisi4spp-script to create the .img-files and replace the storage pool. Please use the tool without any parameters first to see how to use it:

   [root@localhost serveradmin]# ./dsmisi4spp
   Usage: dsmisi4spp ISILON-Name SubPath GB-per-vDev Number-of-vDevs do/preview
                   - ISILON-Name: (name of Isilon as set in /etc/dsmisi/dsmisi.conf) - see below
                   - SubPath: Path underneath the Isilon Mountpoint - see below.
                   - GB-per-vDev: Size of individual vDevs in GB (can be between 128 and 2048)
                   - Number-of-vDevs: Number of vDevs overall.
                           This number multiplied with DB-per-vDev will determine the maximum size of this vpool.
                   - do or preview: With do dsmisi4spp will create the vDev structure and destroy/create the
                           vpool in question. With preview it will check the environment and not actually do anything.
   
           Example: dsmisi4spp CLUSTER-01 spp/vsnap20 1024 100 do
                                   This command will create a vpool of 100 TB in the directory spp/vsnap20 underneath
                                   the mountpoint(s) used for CLUSTER-01
   
                                   dsmisi4spp CLUSTER-02 myspp/testpool 512 10 preview
                                   This command will list all commands it would perform if it created a 5 TB pool with 10
                                   vDevs at 512 GB each underneath the mountoint of Isilon CLUSTER-02 in path myspp/testpool
   
   Usage for applying services: dsmisi service-install
                   This will place a startup stanza and script in /etc/systemd/system/multi-user.target.wants/dsmisi.service
                   and /opt/generalstorage/dsmisi/bin/startup
   
   Reading Isilon Cluster Inforamtion from /etc/dsmisi/dsmisi.conf...
   Cluster name: isiclus
   Cluster mount root: /spp
   Cluster Paths: /spp/isiclus/0001|/spp/isiclus/0003|/spp/isiclus/0002
   

Examples:

[root@localhost serveradmin]# ./dsmisi4spp isiclus sppVsnap/pool 512 10 do
Checking Environment....
Cluster name: isiclus
Cluster mount root: /spp
Cluster Paths: /spp/isiclus/0001|/spp/isiclus/0002|/spp/isiclus/0003

Creating 10 vDevs (512 GB each) in /spp/isiclus/0001/sppVsnap/pool/...
# Pool to replace/create will be vpool1 with ID 1
# History for 'vpool1':
# 2020-11-11.13:39:16 zpool create -f -o autotrim=on -o autoexpand=on -o altroot=/vsnap -o cachefile=/etc/vsnap/zpool.cache/1 vpool1 /dev/sdd
# 2020-11-11.13:39:22 zfs set atime=off primarycache=metadata compress=lz4 dedup=off sync=always vpool1
# 2020-11-11.13:39:32 zfs create -o sync=always vpool1/fs1
# 2020-11-11.13:39:47 zfs set compress=off vpool1/fs1
# 2020-11-11.13:39:52 zfs set dedup=off vpool1/fs1
# 2020-11-11.13:40:02 zfs set sync=disabled vpool1/fs1
#
=========================================================================================
If you are expanding a current pool, use the follwing vdev list via copy/paste wth:
zpool add -o ashift=12 vpool1 /spp/isiclus/0002/sppVsnap/pool/1/1.img /spp/isiclus/0003/sppVsnap/pool/2/2.img /spp/isiclus/0001/sppVsnap/pool/3/3.img /spp/isiclus/0002/sppVsnap/pool/4/4.img /spp/isiclus/0003/sppVsnap/pool/5/5.img /spp/isiclus/0001/sppVsnap/pool/6/6.img /spp/isiclus/0002/sppVsnap/pool/7/7.img /spp/isiclus/0003/sppVsnap/pool/8/8.img /spp/isiclus/0001/sppVsnap/pool/9/9.img /spp/isiclus/0002/sppVsnap/pool/10/10.img
after having created directories and files listed above.
=========================================================================================

zpool create -f -o autoexpand=on -o altroot=/vsnap -o ashift=12 -o cachefile=/etc/vsnap/zpool.cache/1 vpool1 /spp/isiclus/0002/sppVsnap/pool/1/1.img /spp/isiclus/0003/sppVsnap/pool/2/2.img /spp/isiclus/0001/sppVsnap/pool/3/3.img /spp/isiclus/0002/sppVsnap/pool/4/4.img /spp/isiclus/0003/sppVsnap/pool/5/5.img /spp/isiclus/0001/sppVsnap/pool/6/6.img /spp/isiclus/0002/sppVsnap/pool/7/7.img /spp/isiclus/0003/sppVsnap/pool/8/8.img /spp/isiclus/0001/sppVsnap/pool/9/9.img /spp/isiclus/0002/sppVsnap/pool/10/10.img  ... Successful
zfs set checksum=sha256 atime=off compress=lz4 dedup=off sync=disabled vpool1 ... Successful
zfs create -o sync=disabled vpool1/fs1 ... Successful
zfs set compress=off vpool1/fs1 ... Successful
zfs set dedup=off vpool1/fs1 ... Successful
zfs set sync=disabled vpool1/fs1 ... Successful
zpool set cachefile=/etc/vsnap/zpool.cache/1 vpool1 ... Successful
chown -R vsnap:vsnap /vsnap ... Successful

10. Use dsmisi4spp service-install to automatically mount the Isilon on each startup of the vSnap:

    [root@localhost serveradmin]# ./dsmisi4spp service-install
    Enabling startup services...
    Copied dsmisi.service to /etc/systemd/system/multi-user.target.wants
    Copied startup to /opt/generalstorage/dsmisi/bin
    

11. Reboot the vSnap.

12. After reboot, verify that the vsnap pool is configured correctly. This may take a while, if you get the ERROR: PoolInfoError: Failed to collect pool details for 1, try again after a minute:

    [serveradmin@localhost ~]$ vsnap pool show
    ERROR: PoolInfoError: Failed to collect pool details for 1
    [serveradmin@localhost ~]$ vsnap pool show
    TOTAL: 1
    
    ID: 1
    NAME: primary
    POOL TYPE: raid0
    STATUS: ONLINE
    HEALTH: 100
    COMPRESSION: Yes
    COMPRESSION RATIO: 1.00
    DEDUPLICATION: No
    DEDUPLICATION RATIO: 1.00
    ENCRYPTION:
            ENABLED: No
    
    TOTAL SPACE: 99.99GB
    FREE SPACE: 4.81TB
    USED SPACE: -5055455720.00KB
    DATA SIZE BEFORE DEDUPLICATION: 936.00KB
    DATA SIZE BEFORE COMPRESSION: 311.00KB
    CREATED: 2020-11-11 13:39:11 UTC
    UPDATED: 2020-11-11 13:39:11 UTC
    DISKS PER RAID GROUP: 1
    DISKS IN POOL:
            RAID0:
                    /spp/isiclus/0002/sppVsnap/pool/1/1.img
                    /spp/isiclus/0003/sppVsnap/pool/2/2.img
                    /spp/isiclus/0001/sppVsnap/pool/3/3.img
                    /spp/isiclus/0002/sppVsnap/pool/4/4.img
                    /spp/isiclus/0003/sppVsnap/pool/5/5.img
                    /spp/isiclus/0001/sppVsnap/pool/6/6.img
                    /spp/isiclus/0002/sppVsnap/pool/7/7.img
                    /spp/isiclus/0003/sppVsnap/pool/8/8.img
                    /spp/isiclus/0001/sppVsnap/pool/9/9.img
                    /spp/isiclus/0002/sppVsnap/pool/10/10.img
    

Expand a vSnap Storage Pool

Warning

Do not use these steps if you are not 100% sure what to do! If misused, you can destroy your vsnap storage pool!

1. Execute the dsmisi4spp script with preview and the final number (existing+new) of wanted .img-Files:

   [root@localhost serveradmin]# ./dsmisi4spp isiclus sppVsnap/pool 512 12 preview
   Checking Environment....
   Cluster name: isiclus
   Cluster mount root: /spp
   Cluster Paths: /spp/isiclus/0001|/spp/isiclus/0003|/spp/isiclus/0002
   
   Creating 12 vDevs (512 GB each) in /spp/isiclus/0001/sppVsnap/pool/...
   mkdir /spp/isiclus/0003/sppVsnap/pool/1
   File /spp/isiclus/0003/sppVsnap/pool/1/1.img already exists. Assuming extension.
   mkdir /spp/isiclus/0002/sppVsnap/pool/2
   File /spp/isiclus/0002/sppVsnap/pool/2/2.img already exists. Assuming extension.
   mkdir /spp/isiclus/0001/sppVsnap/pool/3
   File /spp/isiclus/0001/sppVsnap/pool/3/3.img already exists. Assuming extension.
   mkdir /spp/isiclus/0003/sppVsnap/pool/4
   File /spp/isiclus/0003/sppVsnap/pool/4/4.img already exists. Assuming extension.
   mkdir /spp/isiclus/0002/sppVsnap/pool/5
   File /spp/isiclus/0002/sppVsnap/pool/5/5.img already exists. Assuming extension.
   mkdir /spp/isiclus/0001/sppVsnap/pool/6
   File /spp/isiclus/0001/sppVsnap/pool/6/6.img already exists. Assuming extension.
   mkdir /spp/isiclus/0003/sppVsnap/pool/7
   File /spp/isiclus/0003/sppVsnap/pool/7/7.img already exists. Assuming extension.
   mkdir /spp/isiclus/0002/sppVsnap/pool/8
   File /spp/isiclus/0002/sppVsnap/pool/8/8.img already exists. Assuming extension.
   mkdir /spp/isiclus/0001/sppVsnap/pool/9
   File /spp/isiclus/0001/sppVsnap/pool/9/9.img already exists. Assuming extension.
   mkdir /spp/isiclus/0003/sppVsnap/pool/10
   File /spp/isiclus/0003/sppVsnap/pool/10/10.img already exists. Assuming extension.
   mkdir /spp/isiclus/0002/sppVsnap/pool/11
   truncate -s 512g /spp/isiclus/0002/sppVsnap/pool/11/11.img
   mkdir /spp/isiclus/0001/sppVsnap/pool/12
   truncate -s 512g /spp/isiclus/0001/sppVsnap/pool/12/12.img
   # Pool to replace/create will be vpool1 with ID 1
   # History for 'vpool1':
   # 2020-11-11.14:00:42 zpool create -f -o autoexpand=on -o altroot=/vsnap -o ashift=12 -o cachefile=/etc/vsnap/zpool.cache/1 vpool1 /spp/isiclus/0003/sppVsnap/pool/1/1.img /spp/isiclus/0002/sppVsnap/pool/2/2.img /spp/isiclus/0001/sppVsnap/pool/3/3.img /spp/isiclus/0003/sppVsnap/pool/4/4.img /spp/isiclus/0002/sppVsnap/pool/5/5.img /spp/isiclus/0001/sppVsnap/pool/6/6.img /spp/isiclus/0003/sppVsnap/pool/7/7.img /spp/isiclus/0002/sppVsnap/pool/8/8.img /spp/isiclus/0001/sppVsnap/pool/9/9.img /spp/isiclus/0003/sppVsnap/pool/10/10.img
   # 2020-11-11.14:00:42 zfs set checksum=sha256 atime=off compress=lz4 dedup=off sync=disabled vpool1
   # 2020-11-11.14:00:53 zfs create -o sync=disabled vpool1/fs1
   # 2020-11-11.14:00:58 zfs set compress=off vpool1/fs1
   # 2020-11-11.14:01:03 zfs set dedup=off vpool1/fs1
   # 2020-11-11.14:01:13 zfs set sync=disabled vpool1/fs1
   # 2020-11-11.14:01:13 zpool set cachefile=/etc/vsnap/zpool.cache/1 vpool1
   #
   =========================================================================================
   If you are expanding a current pool, use the follwing vdev list via copy/paste wth:
   zpool add -o ashift=12 vpool1 /spp/isiclus/0002/sppVsnap/pool/11/11.img /spp/isiclus/0001/sppVsnap/pool/12/12.img
   after having created directories and files listed above.
   =========================================================================================
   
   =========================================================================================
   If you are replacing a current pool, proceed as follows:
   1) Make sure no data resides in the current pool
   2) Copy the output of zpool history as shown above to a safe place
   3) Destroy the current pool vpool1 by entering: zpool destroy vpool1
   4) Execute the commands listed below
   =========================================================================================
   zpool create -f -o autoexpand=on -o altroot=/vsnap -o ashift=12 -o cachefile=/etc/vsnap/zpool.cache/1 vpool1 /spp/isiclus/0002/sppVsnap/pool/11/11.img /spp/isiclus/0001/sppVsnap/pool/12/12.img
   zfs set checksum=sha256 atime=off compress=lz4 dedup=off sync=disabled vpool1
   zfs create -o sync=disabled vpool1/fs1
   zfs set compress=off vpool1/fs1
   zfs set dedup=off vpool1/fs1
   zfs set sync=disabled vpool1/fs1
   zpool set cachefile=/etc/vsnap/zpool.cache/1 vpool1
   chown -R vsnap:vsnap /vsnap
   

2. Use the highlighted commands from above to create the new directories, .img-files and add them to the vpool:

   [root@localhost serveradmin]# mkdir /spp/isiclus/0002/sppVsnap/pool/11
   [root@localhost serveradmin]# truncate -s 512g /spp/isiclus/0002/sppVsnap/pool/11/11.img
   [root@localhost serveradmin]# mkdir /spp/isiclus/0001/sppVsnap/pool/12
   [root@localhost serveradmin]# truncate -s 512g /spp/isiclus/0001/sppVsnap/pool/12/12.img
   [root@localhost serveradmin]#  zpool add -o ashift=12 vpool1 /spp/isiclus/0002/sppVsnap/pool/11/11.img /spp/isiclus/0001/sppVsnap/pool/12/12.img
   

3. Verify the new vpool size with vsnap pool show:

   [root@localhost serveradmin]# vsnap pool show
   TOTAL: 1
   
   ID: 1
   NAME: primary
   POOL TYPE: raid0
   STATUS: ONLINE
   HEALTH: 100
   COMPRESSION: Yes
   COMPRESSION RATIO: 1.00
   DEDUPLICATION: No
   DEDUPLICATION RATIO: 1.00
   ENCRYPTION:
           ENABLED: No
   
   TOTAL SPACE: 5.00TB
   FREE SPACE: 5.77TB
   USED SPACE: -823655056.00KB
   DATA SIZE BEFORE DEDUPLICATION: 948.00KB
   DATA SIZE BEFORE COMPRESSION: 315.50KB
   CREATED: 2020-11-11 13:39:11 UTC
   UPDATED: 2020-11-11 13:39:11 UTC
   DISKS PER RAID GROUP: 1
   DISKS IN POOL:
           RAID0:
                   /spp/isiclus/0003/sppVsnap/pool/1/1.img
                   /spp/isiclus/0002/sppVsnap/pool/2/2.img
                   /spp/isiclus/0001/sppVsnap/pool/3/3.img
                   /spp/isiclus/0003/sppVsnap/pool/4/4.img
                   /spp/isiclus/0002/sppVsnap/pool/5/5.img
                   /spp/isiclus/0001/sppVsnap/pool/6/6.img
                   /spp/isiclus/0003/sppVsnap/pool/7/7.img
                   /spp/isiclus/0002/sppVsnap/pool/8/8.img
                   /spp/isiclus/0001/sppVsnap/pool/9/9.img
                   /spp/isiclus/0003/sppVsnap/pool/10/10.img
                   /spp/isiclus/0002/sppVsnap/pool/11/11.img
                   /spp/isiclus/0001/sppVsnap/pool/12/12.img
   

Automatic deployment

If you are about to deploy lots of vSnap systems, going through the installation and configuration steps every time can take some time. If you want to deploy dsmisi4spp fast and automatically, consider using the dsmisi4sppautogen-script.

In order to use it, you have to supply two input files in the directory in which you extracted dsmisi4spp.

• config.in

• dsmisi.conf

There are 2 sample files dsmisi.conf.smp and config.in.smp which you can adapt to your needs.

dsmisi.conf is your standard dsmisi configuration file to connect to the ISILON.

dsmisi.conf.smp Content:

# General Storage dsmisi4spp 3.2.1
# Copyright: General Storage Software GmbH 2021
# Sample dsmisi.conf file for dsmISI4spp

FileLogLevel Warning
SysLogLevel Warning

MountArgs rw,hard,proto=tcp,timeo=600,retrans=2,intr,async,actimeo=5
NfsRsize 1048576
NfsWsize 1048576

IsiName <ISINAME>
IsiMgmtIp <ISIMGMTIP>
IsiIpPool <ISIIPPOOL>
IsiConnectionTimeout 60
IsiUser dsmisi
IsiMountRootDir <MOUNTPOINT>
IsiExport <EXPORT>

config.in is an input file containing information about what you want to automatically do.

config.in.smp Content:

# General Storage dsmisi4spp 3.2.1
# Distributed as part of dsmisi.3.x.rpm on 64bit Linux OVA courtesy by IBM
# Copyright: General Storage Software GmbH 2021
# Sample config input file for dsmisi4sppautogen-script

#Variables:
#["RUN"] the automatic installation or ["PREVIEW"] the commands to execute.
action="RUN"
#Take steps to install and configure dsmisi components
initDsmISI4spp="YES"
#Take steps to initialize and configure the vsnap pool
initPool="YES"
#Input dsmisi.conf-File
inputDsmISIFile="dsmisi.conf"
#clusterName for dsmISI4spp
clusterName="isi9000"
#SubPath for dsmISI4spp
subPath="sppvsnap"
#GB per vDev for dsmISI4spp
gbPerVdev="2048"
#Number of vDevs for dsmISIspp
numberofVdevs="6"

When the files dsmisi.conf and config.in are available in the dsmisi4spp-directory, you can execute dsmisiautogen.sh to set up dsmisi4spp accordingly to your configuration input files. At one point the script needs user input when trying to copy the ssh-key to the ISILON:

Please enter the password for root@XXX.XXX.XXX.XXX to copy your ssh-key to the ISILON cluster.

This is neccessary to establish a passwordless connection once done.