![]() ![]() |
After the agent has been installed, perform the following tasks from the command prompt on the Celerra File Server using this procedure:
5. | Ensure that the Celerra file system is configured for CWORM=off. | |
6. | Obtain the name and the IP address of the computer on which the Celerra File Archiver Agent is installed. | |
7. |
Enable the DHSM services on the Celerra Data Mover: Syntax: Example:
|
|
8. |
Disable the digest authentication on the Celerra Data Mover: Syntax: Example: |
|
9. |
Verify that the dhsm services have been enabled and the digest authentication
has been disabled by running the following command on the Data Mover: Syntax: The correct values should be returned as follows: Active: True Authentication: none, Realm: DHSM_Authorization |
|
10. |
On the command prompt type the following to set archive and recover
permissions for Unix data: Syntax: Example: Where "server_4" is the name of the server where the share resides. |
[root@celerra_cs
~] $ su root Password: [root@celerra_cs nasadmin]# server_param server_4 -f cifs -modify acl.extac1 -value 28 server_4 : done |
11. |
Type the following to enable EMC Celerra File Mover on the File
System where the CIFS share resides: Syntax: Example: Where "FS3" is the name of the File System where the share resides. |
[rootcelerra_cs
nasadmin]# fs_dhsm -modify FS3 -state enabled FS3: state = enabled offline attr: = on popup timeout = 0 backup: = passthrough read policy override = none log file: = on max log size: = 10MB Done |
12. |
Type the following to add the proxy server to the list of
valid target hosts: Syntax: Example: 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). |
[root@celerra_cs
nasadmin]# server_http server_4 -append dhsm
-hosts 172.19.97.208 server_4 : done |
13. |
Type the following to connect the EMC Celerra Data Mover with the proxy
computer:
CIFS Syntax: It is recommended to use the fully qualified domain name for domain name resolution in some environment settings.
CIFS Example: Where "FS3" is the name of the file system where the share resides, and where "\\pavo3.testlab.<company>.com\pavo3_celerra" is the UNC path of the virtual directory on the proxy server (in this example). CIFS Example for Virtual data Mover (VDM)
fs_dhsm -connection vdm_fs
-create -type cifs -admin testlab\\administrator -secondary
'\\pavo3.testlab.<company>.com\pavo3_celerra' -local_server
celerra_vdm2.<company>.com -password -read_policy_override full where "vdm_fs" is the name of the file system set up on the VDM, "\\pavo3.testlab.<company>.com\pavo3_celerra" is the UNC path of the proxy stub folder, and "celerra_dm2.<company>.com" is the virtual data mover. |
[root@celerra_cs
nasadmin]# fs_dhsm -connection FS3 -create -type cifs -admin
testlab \\ administrator -secondary
'\\pavo3.testlab.<company>.com\pavo3_celerra' -local_server
celerra_dm4.<company>.com -password -read_policy_override
full FS3: state = enabled offline attr: = on popup timeout = 0 backup: = passthrough read policy override = none log file: = on max log size: = 10MB cid = 1 type = CIFS secondary = \\ids35vm3.testlab.<company>.com\ida35vm3_celerra\ state = enabled read policy override = full write policy = full user = options = cgi=n Done |
![]() ![]() |