Managing Celerra Data

Configure the EMC Celerra File Server for Celerra Proxy Stub Subclient Support

Configure the IIS Server for Proxy Stub Subclient Support

Configure a Celerra Proxy Stub Subclient

Configure File Server/Proxy Authentication Credentials

Configure the EMC Celerra File Server for Celerra Proxy Stub Subclient Support

The following procedure describes the steps involved in configuring the EMC Celerra File Server for Celerra Proxy Stub Subclient support.

Before You Begin
Review Configuring File Archiver for Windows to Archive and Recover Celerra Data. The user ID must have administrator-level privileges on the EMC Celerra File Server in order to perform these tasks. Ensure that the Celerra file system is configured for CWORM=off, since dhsm cannot be enabled on a CWORM file system type. Data is always archived on a CIFS share. For recalls from CIFS clients, the volume does not need to be a mixed mode type on the file server. For recalls from NFS clients, the volume must be a mixed mode type on the file server. Refer to vendor documentation for instructions on configuring mixed mode. Note that examples provided in this procedure use DART 5.6 command syntax, with variables noted in <italics> that will be specific to your environment. For more information on EMC Celerra FileMover commands, refer to EMC Celerra documentation.
Configure the EMC Celerra File Server to Archive and Recover the UNIX Permission Mode
1.	From the command prompt of the Celerra File Server, set the following option to archive and recover the UNIX permission mode: Syntax: server_param <server_name_where_share_resides> -f cifs -modify acl.extacl -value 28 Example: server_param server_4 -f cifs -modify acl.extacl -value 28 Where "server_4" is the name of the server where the share resides (in this example).	[root@celerra_cs ~] $ su root Password: [root@celerra_cs nasadmin]# server_param server_4 -f cifs -modify acl.extac1 -value 28 server_4 : done
Enable EMC Celerra FileMover on the File System where the CIFS Share Resides
2.	At the command prompt, enable EMC Celerra FileMover on the File System where the CIFS share resides: Syntax: fs_dhsm -modify <file_system_name_where_share_resides> -state enabled Example: fs_dhsm -modify FS3 -state enabled Where "FS3" is the name of the File System where the share resides (in this example).	[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
Add the Proxy Server to the Valid List of Target Hosts
3.	At the command prompt, add the proxy server to the valid list of target hosts: Syntax: server_http <server_name_where_file_system_resides> -append dhsm -hosts <IP_address_of_proxy_server> 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).	[root@celerra_cs nasadmin]# server_http server_4 -append dhsm -hosts 172.19.97.208 server_4 : done
Define a Connection between the EMC Celerra Data Mover and the Proxy Host
4.	At the command prompt, define a connection between the EMC Celerra Data Mover and the proxy host where the File Archiver for Windows Agent is installed. The EMC Celerra File Server will use this connection to recall files, and can be configured to use either CIFS or HTTP access. CIFS connection is highly recommended: CIFS Syntax: fs_dhsm -connection <file_system_name_where_share_resides> -create -type cifs -admin <domain\\administrator> -secondary '<\\xyz.company.com\shared_dir_where_stubs_reside>' -local_server <fully_qualified_celerra_server_name> -password -read_policy_override full CIFS Example: fs_dhsm -connection FS3 -create -type cifs -admin galaxylab\\administrator -secondary '\\pavo3.galaxylab.commvault.com\pavo3_celerra' -local_server celerra_dm4.commvault.com -password -read_policy_override full Where "FS3" is the name of the file system where the share resides, and where "\\pavo3.galaxylab.commvault.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 galaxylab\\administrator -secondary '\\pavo3.galaxylab.commvault.com\pavo3_celerra' -local_server celerra_vdm2.commvault.com -password -read_policy_override full where "vdm_fs" is the name of the file system set up on the VDM, "\\pavo3.galaxylab.commvault.com\pavo3_celerra" is the UNC path of the proxy stub folder, and "celerra_dm2.commvault.com" is the virtual data mover.	[root@celerra_cs nasadmin]# fs_dhsm -connection FS3 -create -type cifs -admin galaxylab \\ administrator -secondary '\\pavo3.galaxylab.commvault.com\pavo3_celerra' -local_server celerra_dm4.commvault.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.galaxylab.commvault.com\ida35vm3_celerra\ state = enabled read policy override = full write policy = full user = options = cgi=n Done

Configure the IIS Server for Proxy Stub Subclient Support

For details on configuring IIS Server for Proxy Stub Subclient Support see Configure the IIS Server for Celerra Proxy Stub Subclient Support

Create/Modify a Celerra Instance

Before You Begin

Required Capability: See Capabilities and Required Actions

To create/modify a Celerra Instance:

To create a Celerra instance, from the CommCell Browser, locate the correct client computer node, and right-click the File Archiver agent node for which you want the new instance created, click All Tasks, click Create Instance from the shortcut menu, and then click Celerra.
To modify an existing instance, from the CommCell Browser, right-click the instance you want to modify, and then click Properties from the shortcut menu.
From the General tab, enter the name (up to 32 characters) for the instance.

When modifying an existing instance, you cannot change the name of the instance. However, you can change the file server name and credentials.
Enter a name for the Celerra file server - see Add/Change file server Name.
Enter the credentials for the proxy computer - see Configure file server/Proxy Authentication Credentials.
Enter Celera Proxy settings if you wish to change the defaults - see Configure Celerra Proxy Settings.
Click OK to save the instance.

After creating a File Archiver instance, a default Archive Set is created for the instance type. You cannot create additional Archive Sets. Default subclients are not created for the default Archive Set. You must create a user-defined subclient for the default archive set. See Subclients - File Archiver for Windows for more information.

Configure a Celerra Proxy Stub Subclient

Before You Begin

This feature requires a Feature License to be available in the CommServe. Review general license requirements included in License Administration. For step-by-step instructions on how to view the license information, see View All Licenses.

Required Capability: See Capabilities and Permitted Actions

To configure a Proxy Stub Subclient:

From the CommCell Browser, expand the Client node containing the File Archiver for Windows Agent being used as the proxy computer, expand the Agent node and perform one of the following tasks:
- If a new subclient is being configured as the Proxy Stub Subclient, right-click the Archive Set, select All Tasks and then click New Subclient.
- If an existing subclient is being configured as the Proxy Stub Subclient, right-click the existing subclient and then click Properties.
From the Subclient Properties (General) tab, specify the Subclient name (if applicable).
Type in or Browse to the Proxy Stub Path. Note that this path must match exactly the Local Path that was entered during the IIS Server configuration task. Also when creating a proxy path , the Proxy Stub Path field should not be set to the root of a drive.
Type in the HTTP/CIFS Address of the Virtual Directory that was configured on the IIS Server. For example:
http://proxy_server_name/virtual_directory_name
OR
cifs://proxy_server_name/virtual_directory_name
If a new subclient is being configured, then enter the required information as desired on the other tabs in the Subclient Properties dialog. Ensure that the Content is configured as a UNC Path which points to the CIFS share where the data to be archived resides, that the Archiving Rules have been enabled and configured, and that a Storage Policy association has been established.
Click OK to save the changes.
Follow the procedure to Configure Filer Authentication Credentials and Proxy File Settings.

Configure File Server/Proxy Authentication Credentials

Before You Begin

Required Capability: See Capabilities and Permitted Actions

To configure filer/proxy authentication credentials:

From the CommCell Browser, right-click the instance icon for the File Archiver Agent for Windows that you want to configure and then click Properties.
Click Configure Password.
Enter the User Name for the domain in which the network storage file server/proxy resides. Include the domain name with the user name. For example, domainA \administrator.
Enter the Password for the User Name entered above.

After all configuration tasks have been completed, reboot the IIS Server and for Celerra instances, the proxy computer where the File Archiver for Windows Agent is installed. This will ensure that the recall service recognizes all the configuration changes necessary to recall archived data.

The user account must have read and write permissions on the CIFS share and exported to the network storage file server/proxy. The user account must also have admin access to filer and read/write access to the Windows registry on the proxy computer.

Configure Celerra Proxy Settings

Before You Begin

Required Capability: See Capabilities and Permitted Actions

To configure proxy file settings:

From the CommCell Browser, right-click the Celerra instance icon for the File Archiver Agent for Windows that you want to configure and then click Properties.
Optionally, you can change the default settings for the Proxy File Expiration and Proxy Prune Interval by typing new values in the corresponding fields.
- Proxy File Expiration - Specify the number of minutes that a proxy file will remain fully recalled on the agent, before the file is re-stubbed or deleted.
- Proxy Prune Interval - Specify the frequency in which checks are performed on the proxy folder to determine whether there are files that have expired.
Click OK.

After all configuration tasks have been completed, reboot the IIS Server and the proxy computer where the File Archiver for Windows Agent is installed. This will ensure that the recall service recognizes all the configuration changes necessary to recall archived data.