Chat now with support
Chat with Support

Metalogix Archive Manager for Files 8.1.1 - Administration Guide

About the documentation Enterprise Manager – Common Part
How to manage more Archive Manager servers Restrictions tab Settings tab Scheduler tab Archive tab Post Processing tab Statistics tab System context menu
Other functionality Addendum

How to include a NetApp device

 

To include one or more NetApp device(s), you need to add it on the Storage tab. Before adding it you have to give rights to the desired user for the Storage tab. However, after a standard installation, this tab is visible for the administrator without a need to specify the rights.

To include a NetApp device, follow these steps:

1.Click on the Settings tab.

2.Click on the User management tab.

3.In the left pane select the user for which you want to enable Storage tab. Make sure to select the Storage management check box.

b-include net1

4.After allowing Storage management on the User management tab, you may include a NetApp device on the Storage tab. So, click on the Storage tab.

b-include net2

5.Click on the Add button and then click NetApp Filer.

b-include net3

6.Now you need to specify the name of the machine and the policy. Click the Machine name text box and specify the machine name.

b-include net4

 

7.The Show hidden shares option can be set to True or False. It makes hidden shares accessible and archivable for Archive Manager. By default is this option off (False).

 

8.In the Command Option text box it is possible to set the operations for which the NetApp fPolicy server will be registered. Possible values are: open, offline, rename, close, delete, lookup, getattr, setattr, read, write, all70, all65, all64 and their combinations separated by commas. The default settings in the handler service are: “open, offline”. If you experience problems with auto-retrieving files or property changes, please, try to set this value to: “read,write,offline”. Please note that no empty spaces can be contained in the command option.

 

NOTE: When this property is modified, it is necessary to restart Archive Manager for Files (MAM) services so that the changes are applied.

 

9.In the Policy text box, enter the desired policy.

In the Protocol text box it is possible to configure the fPolicy registration for CIFS, NFS or both protocols. Click on the Protocol text box. Then click the down arrow at the end of the text box. Check CIFS or NFS or both options.

 

NOTE: When this property is modified, it is necessary to restart Archive Manager for Files services so that the changes are applied.

 

b-include net5

10.Click Apply.

After including a NetApp device, you may proceed with file archiving (see the section “Archive tab” as well as “Scheduler tab” to learn how to archive either manually or by applying scheduled jobs).

 

Using the NetApp Cluster Mode

Metalogix Archive Manager can leverage the advantages of a NetApp Cluster Mode environment.

A cluster consists of one or more nodes grouped together to form a scalable cluster. Creating a cluster enables the nodes to pool their resources and distribute work across the cluster, while presenting administrators with a single entity to manage. Clustering also enables continuous service to end users if individual nodes go offline. Depending on the controller model, node storage consists of flash disks, capacity drives, or both. Nodes communicate with each other over a private, dedicated cluster interconnect.

To use Metalogix Archive Manager with a NetApp cluster node environment it is necessary to create, configure and enable FPolicy. NetApp® FPolicy® is a file access notification framework that allows an administrator to monitor file access over NFS or CIFS protocol. When configured for Metalogix Archive Manager, FPolicy monitors events in the NetApp environment and sends notifications to the Metalogix Archive Manager (MAM FSA FPolicy Server) every time a user opens a stub file. Metalogix Archive Manager listens to these events and restores a file every time an 'open' request is received.

There are several steps you must perform to create an FPolicy configuration:

1.Plan your configuration.

2.Create an FPolicy external engine, an FPolicy event, and an FPolicy policy.

3.Create an FPolicy scope and attach it to the FPolicy policy.

4.Enable the FPolicy policy.

Prerequisites

1.Configured and running NetApp (Cluster mode) environment with CIFS servers.

2.Installed Metalogix Archive Manager .

NetApp Fpolicy configuration

1.Log into NetApp Admin node console.

2.Create an FPolicy external engine.

The cluster uses the external engine to hold configuration information that it needs in order to send notification information to the FPolicy servers. It specifies the primary servers and secondary servers to which the cluster will send notifications. It also specifies FPolicy server related configuration information.

Metalogix Archive Manager requires FPolicy external engine sending notifications to MAM FSA FPolicy Server. This service is part of Metalogix Archive Manager for Files installation. Default port used by MAM FSA FPolicy Server is 7790.

Example:

vserver fpolicy policy external-engine create -vserver svm1  -engine-name policy_engine -primary-servers 10.16.1.1 -port 7790 -extern-engine-type synchronous –ssl-option no-auth

 

info

NOTE:

vserver svm1: svm1 - is the name of the Storage Virtual Machine with the CIFS share archived by Metalogix Archive Manager.

primary-servers: 10.16.1.1 - 10.16.1.1 is the IP address of the server with Metalogix Archive Manager FSA FPolicy Server installed.

port 7790 - 7790 is the port under which Metalogix Archive Manager FSA FPolicy Server listens.

To verify the FPolicy external engine has been created you can use vserver fpolicy policy external-engine show command.

netapp-cluster-01

3.Create an FPolicy event.

An event describes what to monitor. An event can contain protocol, file operations, filters, and volume operation event types. In the FPolicy configuration, an event is attached to an FPolicy policy. You can attach the same event to one or more policies.

Metalogix Archive Manager requires monitoring of open file operations over offline files.  

Example:

vserver fpolicy policy event create -vserver svm1 -event-name cifs_event -protocol cifs -file-operations open -filters offline-bit  -volume-operation true

 

info

NOTE: vserver svm1: svm1 is the name of the Storage Virtual Machine (Data VServer) with the CIFS share archived by Metalogix Archive Manager

To verify the FPolicy event has been created you can use vserver fpolicy policy event show command.

netapp-cluster-02

4.Create an FPolicy policy.

Fpolicy policy associates an external engine from step 2 and one or more events from step 3 to the policy.

You must create an FPolicy event name before creating an FPolicy policy. If you are using an external FPolicy server, you must also create an FPolicy engine before creating a policy.

Example:

vserver fpolicy policy create -vserver svm1  -policy-name mam_policy -events cifs_event -engine policy_engine -is-mandatory false -allow-privileged-access yes -privileged-user-name demodomain\mam -is-passthrough-read-enabled false

 

 

info

NOTE:

vserver svm1: svm1 is the name of the Storage Virtual Machine (Data VServer) with the CIFS share archived by Metalogix Archive Manager.

events cifs_event: cifs_event is the name of the Fpolicy event that was created in the Step 3.

engine policy_engine: policy_engine is the name of the Fpolicy engine that was created in the Step 2.

privileged-user-name: demoadmin\mam is the name of the superuser under which Metalogix Archive Manager’s services run.

To verify the FPolicy policy has been created you can use vserver fpolicy policy show -instance command.

netapp-cluster-03

5.Create an FPolicy scope for an FPolicy policy.

A scope defines the boundaries on which the FPolicy policy will apply. The Vserver is the basic scope boundary. When you create a scope for an FPolicy policy, you must define the FPolicy policy to which it will apply and you must designate to which Vserver you want to apply the scope. There are a number of parameters that further restrict the scope within the specified Vserver. You can restrict the scope by specifying what to include in the scope. Or you can restrict the scope by specifying what to exclude from the scope.

Example:

vserver fpolicy policy scope create -vserver svm1 -policy-name mam_policy -volumes-to-include * -export-policies-to-include * -file-extensions-to-include *

 

info

NOTE:

vserver svm1: svm1 is the name of the Storage Virtual Machine (Data VServer) with the CIFS share archived by Metalogix Archive Manager.

policy-name mam_policy: mam_policy is the name of the FPolicy policy that was created in the Step 4.

To verify the FPolicy scope has been created you can use  the vserver fpolicy scope show -instance command.

netapp-cluster-04

6.Enable FPolicy policy for the specified Vserver and set its sequence (priority).

The sequence is used when multiple policies have subscribed to the same file access event. To modify the sequence number of a policy, the administrator must disable the policy (if it is enabled) and then use this command to enable it with the new sequence number. Policies that use the native engine configuration have a higher priority than policies for any other engine, regardless of the sequence number assigned to them.

Example:

vserver fpolicy enable -vserver svm1 -policy-name mam_policy -sequence-number 1

 

info

NOTE:

vserver svm1: svm1 is the name of the Storage Virtual Machine (Data VServer) with the CIFS share archived by Metalogix Archive Manager.

policy-name mam_policy: mam_policy is the name of the FPolicy policy that was created in the Step 4.

To verify the FPolicy has been enabled you can use the vserver fpolicy show-enabled command.

netapp-cluster-05

7.Configure Metalogix Archive Manager

To archive and access date in the NetApp environment it is necessary to create, and configure connection to NetApp in Metalogix Archive Manager.

Steps to configure Metalogix Archive Manager to use the NetApp Cluster Mode.

1.Open Enterprise Manager Console for Metalogix Archive Manager (Settings > Storage > Add > NetApp Filer)

netapp-cluster-MAM-config

2.Enter the parameters for the properties as described below:

Field

Description

Machine name

CIFS server name to be archived

Admin Vsever

IP adress of admin vserver

Admin Vserver login name

User name to log into admin server

Admin Vserver password

Password to log into admin server

Data Vserver

Name of Data Vserver (Storage Virtual Machine) with CIFS server

Node Vserver

Name of Node Vserver in the NetApp cluster

Policy

Name of the Fpolicy policy configured in step 6.

 

info

NOTES: NetApp cluster consists of three types of Vservers, which help in managing the cluster and its resources, and the data access to the clients and applications. A cluster contains the following types of Vservers:

·Admin Vserver

·Node Vserver

·Data (cluster) Vserver

An Admin Vserver is created automatically by the cluster setup process.

A Node Vserver is created when the node joins the cluster. The Admin Vserver represents the cluster, and Node Vservers represents the individual nodes of the cluster.

A Data (Cluster) Vserver represents the data serving Vservers. After the cluster setup, a cluster administrator must create Data (Cluster) Vservers and add volumes to these Vservers to facilitate data access from the cluster. A cluster must have at least one Data (Cluster) Vserver to serve data to its clients.

Cluster Vservers are also referred to as Data Vservers because they are used to read and write data to and from the cluster. Also, unless otherwise specified the term Vserver refers to cluster (data-serving) Vserver, which applies to both Vserver with FlexVol volumes and Vserver with Infinite Volume.

The user account that runs the Metalogix Archive Manager services must be part of the BUILT-IN\Administrators group on the Storage Virtual Machine with the CIFS share that is to be archived.

Celerra & VNX FileMovers

Configuring Celerra & VNX FileMovers for use with Archive Manager for Files

 

The archiving of files on the Celerra & VNX FileMovers is achieved by putting them offline using HTTP commands sent to the FileMover API. Be default, only the Control Station can access the Celerra & VNX FileMovers API. Therefore the server_http command must be used to allow other IP addresses to access it. It is necessary to enable HTTP commands sending from the Archive Manager server to the Celerra & VNX FileMovers using the following server_http command:

 

server_http <data mover> -append dhsm -hosts <Archive Manager_server_IP>

 

Respond should look as follows…

<data mover> :

DHSM FACILITY CONFIGURATION

…

 ACCESS CONTROL

   Allowed IPs        : <Archive Manager_server_IP>

…

 

 

[This configures CELERRA & VNX FILEMOVERS API security and then restarts the API service so that the changes take effect.]

 

Further you need to specify the authentication and a user. There are three types of authentication (none, basic, digest), but supported types for Archive Manager are these:

·none

·digest

In case you choose a “digest” type of authentication, you have to assign a user for DHSM commands. The user must exist or it should be created and assigned to the DHSM feature.

 

Specifying authentication:

server_http <data mover> -modify dhsm -authentication <authentication type>

 

Creating a user:

/nas/sbin/server_user <data mover> –add –md5 –passwd <User name>

 

Assigning the user to the DHSM feature:

server_http <data mover> -modify dhsm –users <User name>

 

Respond should look as follows…

   Authentication     : digest ,Realm : DHSM_Authorization

   Allowed user       : user1    (or valid)

 

[<User_name> is the name of the account (A Celerra or VNX account) that Archive Manager for Files needs to use for authentication. This user is a Data Mover user, not a domain user. A prompt for a "User ID" and "Group ID" may also occur.  A suitable number is 1000 for both, unless this is in use elsewhere. The number must be unique and does not need to have "root" privileges.   If  prompted for a "Home Directory" just press Enter to continue and leave the entry blank.]

 

DHSM command must be allowed on the selected file system. This is done in the following way:

 

fs_dhsm -modify <file_system> -state enabled

 

Respond should look as follows…

<file_system>:

state                = enabled

 

[This command enables DHSM for the file system. If the DHSM in not enabled, the next command will not establish he connection between Archive Manager and the Celerra & VNX FileMovers and the Celerra & VNX FileMovers will not be accepted in the Enterprise Manager.]

 

As mentioned above the archiving of files on Celerra & VNX FileMovers is based on putting them offline. Then an URL pointing to the file in the archive is specified for each file. When VNX or Celerra is used with Archive Manager for Files this URL is the address of a .NET ASPX web page. The page ensures retrieving of the original file from the archive. That’s why a non-CGI HTTP connection must be configured to the web page. It could be done in Celerra & VNX FileMovers administration console as follows:

fs_dhsm -connection <file_system> -create -type http -secondary http://<Archive Manager_server>/HsmDownload -read_policy_override full -cgi n

 

Respond should look as follows…

<file_system>:

…

cid                 = 0

  type                 = HTTP

  secondary            = http://<Archive Manager_server>/HsmDownload

  read policy override = full

  options              = cgi=n

…

[This command creates a Celerra & VNX FileMovers connection on the file system. This uses a Web server “<Archive Manager_server>” and specifies that files offlined via this connection could be retrieved from the virtual directory /HsmDownload  in the hierarchical name space published by the web server. This command only has to be done once; it remains persistent across Data Mover boots.]

 

If the web page is configured to require authentication, the above command line must be enhanced by –user and –password parameters, e.g.:

 

fs_dhsm -connection <file_system> -create -type http -secondary http://<Archive Manager _server>/HsmDownload -read_policy_override full -cgi n -user <user_name>

-password <password>

 

As a last step of the configuration, it is necessary to activate DHSM feature:

server_http <data mover> -service DHSM –start

Respond should look as follows…

DHSM FACILITY CONFIGURATION

Service Name        : EMC File Mover service

Active                    : True

 

After completing the above steps, the Celerra & VNX FileMovers can be added to Archive Manager for Files using the Enterprise Manager (see the next section “How to include a VNX or Celerra file server”). The meaning of the properties of the FileMover (see the figure below) is the following:

 

Machine name

-

The network name of the Celerra or VNX FileMover machine.

Show hidden shares

-

It makes hidden shares accessible and archivable for Archive Manager. By default is this option off (False).

Offline URL format

-

The format of offline URLs of archived files. The URL format must contain string %ID%, which will be replaced by ID of the archived file. The URL must point to connection set up in above steps.

Protocol

-

The type of the Celerra or VNX FileMover file system.

Authentication

-

If the Celerra or VNX FileMover requires authenticated requests (depends on your Celerra or VNX configuration), specify the name and password of the user.

 

c-celera1

 

 

How to include a VNX or Celerra file server

 

To include a VNX or Celerra file server, you need to include it on the Storage tab. Before including it you have to give rights to the desired user for the Storage tab. However, after a standard installation, this tab is visible for the administrator without a need to specify the rights.

 

To include VNX or Celerra file server, follow these steps:

1.Click on the Settings tab.

2.Click on the User management tab.

3.In the left pane select the user for which you want to enable Storage tab. Make sure to select the Storage management check box.

d-generic1

4.After allowing Storage management on the User management tab you may include a Celerra file-server on the Storage tab. So, click on the Storage tab.

5.Click on the Add button and then click VNX FileMover.

c-celera3

6.If the Celerra or VNX FileMover requires authenticated requests (depends on your VNX or Celerra configuration), specify the name and password of the user. Click on the Authentication box. Then click on the down arrow. In the respective text boxes enter the name of the appropriate use (User name) and password (Password and Confirm password text boxes).

c-celera4

7.Click on the Offline URL format to specify the format of offline URLs of archived files. The URL format must contain string %ID% which will be replaced by the ID of the archived file. The URL must point to the connection set up at VNX or Celerra configuration (see “Configuring Celerra & VNX FileMovers for use with Archive Manager for Files”).

c-celera5

8.Click on the Protocol box. Then click on the down arrow to choose the desired protocol, i.e. the type of the Celerra or VNX FileMover file system.

c-celera6

9.Click on the Machine name box and enter the network name of the Celerra or VNX FileMover machine.

Finally click Apply.

c-celera7

 

Related Documents