When running InfiniGuard Code version 3.3.x and above, the NetBoost devices’ service monitoring includes the ability for Backup Admins to use the CLI based “iguard_ls” tool to list and sort NetBoost Share contents.

This feature allows Backup Admins to monitor the data stored on the shares for capacity consumption. This includes the long list of content review reports, content owner, age, size of the data on the NetBoost Shares, and so on.

Your TA can assist you in obtaining these tools before they are officially available from the Infinidat Support site. Once you have obtained it, it can then be installed (as an RPM) on any AIX 7.1, AIX 7.2, Redhat or Centos Linux server.

Once installed, the script-based tools allow authenticated access to any 3.3.x or above InfiniGuard to list and sort contents of any or all Deduplication Engine NetBoost Shares. The tool requires read-only account on the InfiniGuard UI (as a minimum).

  1. Install the InfiniGuard_LS RPM on the system you wish to use as a cli tool server to list data on the Shares.
  2. Obtain the RPM appropriate for your host operating system (LINUX/AIX) from Infinidat Support or your TA.
  3. Install the RPM using “rpm –ivh INFINIDAT_InfiniGuard_ls.rpm

Once installed, you can list and sort data on DDEs and Application Specific (NetBoost) shares.

If the stored data exceeds your client SLA, you can simply point the path data and backups and/or logs that they need to delete with their applications, to maintain Share SLA integrity. Some examples follow.

[root@io-wt-11 ~]# iguard_ls --help

Help shows the syntax of using the command:
iguard_ls --hostname=<hostname> [--username=<username>] [--password=<password>] --dde=<dde_id> 
iguard_ls --hostname=<hostname> [--username=<username>] [--password=<password>] --dde=<dde_id> --list
iguard_ls --hostname=<hostname> --username=<username> --password=<password> --save
iguard_ls --delete
iguard_ls --help
 iguard_ls --version

: - sort by DDE, Share, Size, and find files older than a specified Age (in days)
   -H hostname --hostname=<hostname>   DNS name/IP  of InfiniGuard
   -u username --username=<username>   Administrator's username
   -p password --password=<password>   Administrator's password
   -d dde_id, --dde=<dde_id>           DDE ID (1/2)
   -s share, --share=<share>           Display only share name <share>
   -a age, --age=<age>                 Only display files older than <age> days
   -D, --delete                        Delete all stored credentials
   -S, --save                          Save credentials for hostname
   -L, --list                          List all share names
   -l, --long                          Use long display format
   -t, --time                          Sort by time
   --size                              Sort by size
   -r, --reverse                       Sort in reverse order
   -h, --human-readable                Display size in human readable format
   --help                              Show this screen
   -V, --version                       Show iguard_ls version

The iguard_ls command will use the –H (or - –hostname) and point to the InfiniGuard DNS-hostname or IP address.  User and Password can be saved to avoid having to authenticate each task.

This requires “http” access to the ibox floating IP (the System Management IP), and at least a Read-Only user on the iGuard UI.

The following example shows a listing of all shares and files (with Human readable capacity).

  • By default, capacities are listed in bytes.
[root@io-wt-11 ~]# iguard_ls --hostname= -d 1 –lth
Permissions   UID/GID   Date/Time    Share/File

-rw------- 0    0    Tue Aug  4 20:48:49 2020   23.8M 1593dde1-ora1/c-1629726080-20200804-00
-rw------- 0    0    Tue Aug  4 20:48:48 2020   23.8M 1593dde1-ora1/9qv7266v_1_1
-rw------- 0    0    Tue Aug  4 20:48:36 2020    4.9G 1593dde1-ora1/9ov7264s_1_1
-rw------- 0    0    Tue Aug  4 20:47:46 2020  468.8M 1593dde1-ora1/9pv7264s_1_1
-rw------- 0    0    Tue Aug  4 20:47:32 2020  256.0K 1593dde1-ora1/1ov7223g_256_1_256
-rw------- 0    0    Tue Aug  4 20:47:09 2020   67.0M 1593dde1-ora1/1ov7223g_254_1_254
-rw------- 0    0    Tue Aug  4 20:47:09 2020  256.0K 1593dde1-ora1/1ov7223g_255_1_255
-rw------- 0    0    Tue Aug  4 20:47:02 2020  256.0K 1593dde1-ora1/1ov7223g_253_1_253
-rw------- 0    0    Tue Aug  4 20:46:56 2020   67.0M 1593dde1-ora1/1ov7223g_252_1_252
-rw------- 0    0    Tue Aug  4 20:46:54 2020  256.0K 1593dde1-ora1/1ov7223g_251_1_251
-rw------- 0    0    Tue Aug  4 20:46:54 2020  256.0K 1593dde1-ora1/1ov7223g_250_1_250
-rw------- 0    0    Tue Aug  4 20:46:39 2020   67.0M 1593dde1-ora1/1ov7223g_249_1_249

The Following example shows a listing of files older than 180 days.

[root@io-wt-11 ~]# iguard_ls --hostname= -d 1 -a 180 -lth 
-rw-r--r-- 0    0    Thu Aug 15 14:27:16 2019      92 Xu_BoostFS_Sybase/boost_fs_file4
-rw-r--r-- 0    0    Thu Aug 15 14:27:15 2019      92 Xu_BoostFS_Sybase/boost_fs_file2
-rw-r--r-- 0    0    Thu Aug 15 14:27:15 2019      92 Xu_BoostFS_Sybase/boost_fs_file
-rw-r--r-- 0    0    Thu Aug 15 14:27:15 2019      92 Xu_BoostFS_Sybase/boost_fs_file3

Was this article helpful?
0 out of 0 found this helpful

0 out of 0 found this helpful

Last edited: 2022-08-06 08:20:45 UTC