Thanks for the quick response.

I found the documentation on FLRTool kit (Tech notes). I am having issues when tyring to run flrquery/flrapply.

I am getting DHSM server user error:

“DHSM user authentication failed.

ERROR:Error on socket connect"

I had my storage team setup the DHSM server and included the IP address where I am runnint the Toolkit from but still getting above error.

I am not logged on to the server as the user setup in DHSM server.  This is the part confusing me since my application will deployed on a server where FLRTool kit is installed but the DHSM service will be on differen server (or it has to be on the same server that FLRToolkit is running from?).

I am looking for the documentation /picture which tells me what are the steps involved to FLR CLI to work.

Thank you.

FLR CLI

There is a detailed document ' File-Level Retention toolkit, technical notes' this shows the different CLI switches and provides examples. You can also get the same examples from the cli. In the DOS prompt type just the cli command e.g. flrquery or flrapply

I have used the CLI extensively, let me know what you are trying to do.

Vasa,

I am assuming you already created the user on the datamover using /nas/sbin/server_user server_X command e.g. /nas/sbin/server_user server_2 -add -md5 -passwd flruser

I suspect you may need to modify your configuration, make sure you have the allowed IPs, authentication and allowed portions configured. See an example below. Also make sure the service is running

server_http server_X -info dhsm (replace the server_X with the datamover you are using)
server_2 : done
DHSM FACILITY CONFIGURATION
  Service name       : EMC File Mover service
  Comment            : Service facility for getting DHSM attributes
Active             : True (This shows the service is running)
  Port               : 5080
  Threads            : 16
  Max requests       : 300
  Timeout            : 60 seconds
  ACCESS CONTROL
   Allowed IPs        : 10.0.0.x (This is the IP address to the host running the flr toolkit)
    Authentication     : digest ,Realm : DHSM_Authorization
    Allowed user       : valid
  SSL CONFIGURATION
    Mode               : OFF
    Persona            : default
    Protocol           : default
    Cipher             : default

The username and password will be what you setup on the datamover. This 'authentication' function was added as of FLR toolkit 4.0. Yes authentication will be required the first time for every host/server running the toolkit.

Yes, the configuration matches with what you suggested.  I just came to know that our storage team has used the GUI first time which asked for the user id and password and then he is able to use CLI without any issues.  I am going to try this think, it will solve the problem.

Does this mean, we need to login using GUI first time for every client we are going to use for FLRTool kit?

Correct, in my experience I have only been prompted for the username and password information once. Rebooting the server was not an issue. Keep in mind this is once per datamover i.e. each datamover will require you to authenticate once.

Okay, so it will save the information on the client permenently (bouncing the server will not loose the information) is this correct?

The monitor service requires a domain user with specific privileges. EMC docs states

• The service account used for the FLR Monitor Service should be a domain administrator account and should be added to the local admin group on the client where the service is intended to run.
• The service account should be granted the "Logon as Service" privilege on the client where the service is intended to run.

I however did not grant that account domain admin rights for various reasons, security being one of them.

Do I need to install all components of FLRTool kit (FLR Explorer, FLR Monitor Serivce, Shell Extensions along with FLR Query and FLR Apply) on the client where I am going to use these CLIs?

If I need to install FLR Monitor Service, it is asking for Domain\User name and passowrd, I believe this user name is not same as DHSM service user.

Thanks for the answers Mosesn.

BTW, how did you run these CLIs in programs (hope you did some).  Have you used Java for your programming? Did you run FLRTool kit CLI as executables or did you use winAPI calls?

No problem.

I haven't used the API. I used batch scripts to call the executables, I mostly used Linux for my heavy lifting.

Thanks for all the help.  Will get back to you if I need further assistance on any of this.

If you don't need the functionality of the component then you don't need to install it

Rainer,

All I need CLI to run from Java, So you are saying I do not need to install other componenets in the toolkit (FLRExplorer, Shell and Monitor)?  Is DHSM service has to run on the same location where my FLRTool kit is installed or I should login into the system as DHSM user?  If I install just  CLI on the system and DHSM is not running on this same system, I am getting a "DHSM user authentication failed.  ERROR:Error on socket connect".