Dell EMC VNX / Celerra Filer Configuration

After the agent has been installed, perform the following tasks from the command prompt on the Dell EMC VNX / Celerra file server.

Procedure

  1. Set permissions to archive and recover data.

    On the Dell EMC VNX / Celerra file server, make sure that the CIFS path with required read/write permissions is configured.

  2. In the Access-Checking Policy area, select the NATIVE option.

  3. To recall stubs successfully, ensure that the Dell EMC VNX / Celerra file system is configured for CWORM=off.

    To verify if CWORM=off, run the following command:

    Syntax:

    nas_fs –info FileSystemName

    Example:

    [root@cs0vnx5300 nasadmin]# nas_fs -info FS_Automation

    Sample Output:

    id = 20

    name = FS_Automation

    acl = 0

    in_use = True

    type = uxfs

    worm = off

    volume = v126

    pool = clarsas_archive

    member_of = root_avm_fs_group_32

    rw_servers= server_2

    ro_servers=

    rw_vdms =

    ro_vdms =

    auto_ext = hwm=90%,thin=no

    fast_clone_level = 1

  4. Enable DHSM services on the File System share.

    Syntax:fs_dhsm –modify <file_system_name_where_share_resides> -state enabled

    Example:
    fs_dhsm –modify FS6 –state enabled

    For a Virtual Data Mover, <file_system_name_where_share_resides> refers to the name of the file system that is created on the Virtual Data Mover.

  5. Enable the DHSM services on the Dell EMC VNX / Celerra file server:

    Syntax:server_http<server_name_where_file_system_resides>-service dhsm -start

    Example:server_http server_4 -service dhsm -start

    For a Virtual Data Mover, <server_name_where_file_system_resides> refers to the physical data mover that the Virtual Data Mover points to.

  6. Disable the digest authentication on the Dell EMC VNX / Celerra file server:

    Syntax:server_http<server_name_where_file_system_resides>-modify dhsm -authentication none

    Example:server_http server_4 -modify dhsm -authentication none

    For a Virtual Data Mover, <server_name_where_file_system_resides> refers to the physical data mover that the Virtual Data Mover points to.

  7. Verify that the dhsm services have been enabled and the digest authentication has been disabled by running the following command on the file server:

    Syntax:server_http<server_name_where_file_system_resides> -info

    The correct values should be returned as follows:

    Active: True

    Authentication: none, Realm: DHSM_Authorization

    For a Virtual Data Mover, <server_name_where_file_system_resides> refers to the physical data mover that the Virtual Data Mover points to.

  8. Obtain the name and the IP address of the proxy computer and the computer on which the Web Console is installed.

    Type the following command to add the IP address of the proxy server and the computer on which the webconsole is installed to the list of valid target hosts:

    Syntax:server_http<server_name_where_file_system_resides>-append dhsm -hosts<IP_address_of_web_console_machine_>

    Example:server_http server_4 -append dhsm -hosts 172.19.97.208

    Where "server_4" is the name of the server where the file system resides, and where "172.19.97.208" is the IP address of the proxy server (in this example).

    For a Virtual Data Mover, <server_name_where_file_system_resides> refers to the name of the file system that is created on the Virtual Data Mover.

    Note

    If the proxy and the Web Console are installed on different computers, then their IP addresses should be registered to the Dell EMC VNX / Celerra file server. Also, the two machines must be in the same domain as that of the Dell EMC VNX / Celerra file server.

    [root@celerra_cs nasadmin]# server_http server_4 -append dhsm -hosts 172.19.97.208
    server_4 : done
    
  9. Navigate to the command prompt and define a connection between the Dell EMC VNX / Celerra file server and the computer on which the Web Console is installed. The Dell EMC VNX / Celerra file server will use this connection to recall files. When you perform a Preview operation on a file, the file is recalled and the stub is replaced with the file on the file server.

    Important: Replace -read_policy_override with -read_policy_override passthrough,if you do not want the stubs to be replaced with the file when you perform a Preview operation on the file server.

    HTTP Syntax:

    • fs_dhsm -connection <file_system_name_where_share_resides> -create -type http -secondary <http://machine_name> -read_policy_override full -cgi n -user <domain\\username>-password <user_password>

    • fs_dhsm -connection <file_system_name_where_share_resides> -create -type http -secondary <http://machine_name> -read_policy_override passthrough full -cgi n -user <domain\\username>-password <user_password>

    HTTP Example:fs_dhsm -connection FS6 -create -type http -secondary http://machine_name -read_policy_override full -cgi n -user <domain\\username>-password <user_password>

    Where "FS6" is the name of the file system where the share resides, and where "http://machine_name" is the URL of the webconsole computer (in this example).

    Note

    The Web Console URL must include the fully qualified domain name of the Web Console computer.

    For a Virtual Data Mover, <server_name_where_file_system_resides> refers to the name of the file system that is created on the Virtual Data Mover.

    [root@scylla bin]# fs_dhsm -connection FS6 -create -type http -secondary http://machine_name -read_policy_override full -cgi n
    FS6:
    state                = enabled
    offline attr:        = on
    popup timeout        = 0
    backup:              = passthrough
    read policy override = none
    log file:            = on
    max log size:        = 10MB
     cid                 = 1
       type                 = HTTP
       secondary            = http://machine_name
       state                = enabled
       read policy override = full
       write policy         =        full
       user                 =
       options              = cgi=n Done
    
×

Loading...