Using VNX FileMover - emclink.net · the VNX, the policy and archiving application, and the...

EMC®VNX® SeriesRelease 8.1

Using VNX® FileMoverP/N 300-015-119 Rev 01

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-91031-508-435-1000

www.EMC.com

Copyright © 2006 - 2013 EMC Corporation. All rights reserved.

Published August 2013

EMC believes the information in this publication is accurate as of its publication date. Theinformation is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATIONMAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TOTHE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIEDWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires anapplicable software license.

For the most up-to-date regulatory document for your product line, go to the TechnicalDocumentation and Advisories section on EMC Powerlink.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks onEMC.com.

All other trademarks used herein are the property of their respective owners.

Corporate Headquarters: Hopkinton, MA 01748-9103

2 Using VNX FileMover

Contents

Preface.....................................................................................................7

Chapter 1: Introduction...........................................................................9System requirements.............................................................................................10Limitations..............................................................................................................10Cautions and warnings.........................................................................................11User interface choices...........................................................................................13Related information..............................................................................................13

Chapter 2: Concepts.............................................................................15Connection types...................................................................................................17Archive operation..................................................................................................18Write operation......................................................................................................20Read operation.......................................................................................................21VNX FileMover configuration and management.............................................24Planning storage requirements...........................................................................25Planning orphan file management.....................................................................27Planning backup strategies..................................................................................27Planning file system usage...................................................................................29Planning network traffic.......................................................................................29Planning for read-only file systems....................................................................29Planning interactions between VNX FileMover and your

applications.......................................................................................................30Planning file system scanning performance......................................................30Planning secondary hostname resolution..........................................................30Planning application integration.........................................................................38

Using VNX FileMover 3

Chapter 3: Enabling VNX FileMover.....................................................43Enable VNX FileMover.........................................................................................44

Chapter 4: Creating a CIFS connection..............................................45CIFS connection considerations..........................................................................46Create a CIFS connection......................................................................................46

Chapter 5: Creating an NFS connection.............................................49Create an NFS connection....................................................................................50

Chapter 6: Creating an HTTP or HTTPS connection.............................51HTTP and HTTPS connection considerations...................................................52Create a non-CGI HTTP or HTTPS connection.................................................52Create a CGI HTTP or HTTPS connection.........................................................53Switch between HTTP and HTTPS connections...............................................54

Chapter 7: Configuring API security....................................................55Configuring certificate authentication...............................................................56

Configure access based on IP address......................................................56Stop the existing FileMover HTTP service..............................................57Configure HTTPS........................................................................................58Start the FileMover HTTPS service...........................................................58Verify certificate availability......................................................................59

Configuring digest or basic authentication.......................................................60Create a VNX FileMover user account.....................................................60Configure digest or basic access authentication.....................................61

Listing HTTP connection information................................................................61

Chapter 8: Managing............................................................................63Modify a connection.............................................................................................64List VNX FileMover connections........................................................................65List connection information.................................................................................65Delete a VNX FileMover connection..................................................................66

Chapter 9: Administering......................................................................69Change a CIFS password......................................................................................70Disable VNX FileMover log.................................................................................71Increase log file size..............................................................................................73


Contents

Scan applications...................................................................................................73Perform an NDMP backup...................................................................................74Perform a CIFS network backup.........................................................................75Perform an NFS network backup........................................................................76Enable pop-up notification (CIFS only).............................................................77Adjust offline attribute settings...........................................................................78Tune HTTP threads...............................................................................................79Tune threads to read data from secondary storage..........................................80Move VNX FileMover stub files..........................................................................81Disable FileMover functionality..........................................................................81

Chapter 10: Example procedure.........................................................83Example procedure...............................................................................................84

Chapter 11: Troubleshooting................................................................87EMC E-Lab Interoperability Navigator..............................................................88VNX user customized documentation...............................................................88Known problems...................................................................................................88Error messages.......................................................................................................89EMC Training and Professional Services...........................................................90

Appendix A: VNX FileMover log file example....................................91VNX FileMover log file example.........................................................................92

Appendix B: Storage space requirement example ..........................93Storage space requirement example...................................................................94

Appendix C: HTTP connections and Data Mover HTTP clients...........95VNX FileMover HTTP connection to secondary storage connection

counts................................................................................................................97Data Mover HTTP client secondary connection high availability.................97Forcing a Data Mover to stop using a secondary HTTP server......................98

Glossary..................................................................................................99

Index.....................................................................................................105


Contents


Contents

Preface

As part of an effort to improve and enhance the performance and capabilities of its product lines,EMC periodically releases revisions of its hardware and software. Therefore, some functions describedin this document may not be supported by all versions of the software or hardware currently in use.For the most up-to-date information on product features, refer to your product release notes.

If a product does not function properly or does not function as described in this document, pleasecontact your EMC representative.


Special notice conventions

EMC uses the following conventions for special notices:

Note: Emphasizes content that is of exceptional importance or interest but does not relate to personalinjury or business/data loss.

Identifies content that warns of potential business or data loss.

Indicates a hazardous situation which, if not avoided, could result in minor ormoderate injury.

Indicates a hazardous situation which, if not avoided, could result in death orserious injury.

Indicates a hazardous situation which, if not avoided, will result in death or seriousinjury.

Where to get help

EMC support, product, and licensing information can be obtained as follows:

Product information—For documentation, release notes, software updates, or forinformation about EMC products, licensing, and service, go to EMC Online Support(registration required) at http://Support.EMC.com.

Troubleshooting—Go to EMC Online Support at http://Support.EMC.com. Afterlogging in, locate the applicable Support by Product page.

Technical support—For technical support and service requests, go to EMC CustomerService on EMC Online Support at http://Support.EMC.com. After logging in, locatethe applicable Support by Product page, and choose either Live Chat or Create a servicerequest. To open a service request through EMC Online Support, you must have avalid support agreement. Contact your EMC sales representative for details aboutobtaining a valid support agreement or with questions about your account.

Note: Do not request a specific support representative unless one has already been assigned toyour particular system problem.

Your comments

Your suggestions will help us continue to improve the accuracy, organization, and overallquality of the user publications.

Please send your opinion of this document to:

[email protected]


Preface

http://Support.EMC.com



1

Introduction

EMC VNX FileMover is a VNX feature that delivers dynamic filemobility—the ability to automate the archiving of files in anetwork-attached storage (NAS) environment across a hierarchy of storageplatforms. When VNX FileMover is used with the external policy andarchiving application, it automatically archives infrequently used files, orfiles of a particular type, to slower, less-expensive storage devices.

VNX FileMover demonstrates the benefits of Information LifecycleManagement (ILM) by optimizing the placement of files within an existingtiered storage infrastructure. Enabling VNX FileMover on the VNX allowsadministrators to use storage devices economically to:

◆ Reduce storage management costs◆ Extend storage lifetime◆ Reduce the frequency of backups

This document discusses how to configure VNX FileMover, including:

◆ Configuring and managing VNX FileMover connections on the VNX◆ Configuring API security

This document is part of the VNX information set and is intended for useby the system administrators responsible for configuring VNX FileMoverto use with an external policy and archiving application.

Topics included are:◆ System requirements on page 10◆ Limitations on page 10◆ Cautions and warnings on page 11◆ User interface choices on page 13◆ Related information on page 13


System requirements

Table 1 on page 10 describes the EMC® VNX® Series software, hardware, network, andstorage configurations.

Table 1. System requirements

Search the EMC E-Lab™ Interoperability Navigator for policy and archiving applicationssupported when using VNX FileMover.

Software

VNX 514 Data Mover.

VNX series system.

Read your policy and archiving application documentation for requirements specific tothe policy and archiving application platform.

Hardware

For maximum performance and security, consider managing the network traffic betweenthe VNX, the policy and archiving application, and the secondary storage to travel by

Network

using a private, high-speed (Gigabit Ethernet) network. Read Planning network trafficon page 29.

Read your policy and archiving application documentation for detailed informationabout network requirements.

Read Planning storage requirements on page 25.Storage

Search the EMC E-Lab Interoperability Navigator for secondary file servers that aresupported when using VNX FileMover.

Limitations

The following are the limitations for VNX FileMover:

◆ VNX FileMover cannot be enabled on a read-only file system not previously enabled forthe FileMover functionality.

◆ A file-level retention (FLR) file system cannot be used as the primary storage in aFileMover environment. However, it is possible to use an FLR file system as a secondarystorage. Contact your software vendor to determine whether your policy and archivingapplication supports this configuration.

A file in the FLR state on secondary storage cannot be altered or deleted by VNX for Fileclients or users. A file in the FLR state can be deleted only after its retention date haspassed.Using VNXFile-Level Retention contains information about FLR storage technologyand file system behavior.

◆ VNX FileMover cannot be enabled on a Migration File System (MGFS).


Introduction

◆ VNX FileMover can manage a maximum path length of 1024 bytes. However, themaximum pathname length depends on the policy and archiving application.

◆ VNX FileMover does not support archiving of alternate data streams.◆ VNX FileMover does not support the NFSv4 protocol as a secondary server connection.◆ VNX FileMover does not support using DFS-based UNC paths to connect to CIFS-based

secondary storage. The VNX must connect to the real server and share name when usingCIFS connections to the secondary storage.

◆ To avoid issues when accessing files archived from the primary storage multiple times,ensure your chosen policy and archiving application supports maintaining multipleversions of files on the secondary storage.

◆ A multihop configuration allows you to move data from the primary storage to thesecondary storage, from the secondary storage to the tertiary storage, and back. AFileMover-enabled file system can be the secondary storage. In a multihop configuration,the secondary storage must be a VNX while tertiary storage can be a VNX NFS/CIFS orHTTP file server.

◆ Although VNX FileMover supports a multihop configuration up to two hops, your policyand archiving application vendor might not yet support this functionality. Contact yourpolicy and archiving application vendor directly for the most up-to-date informationabout multihop configurations.

◆ If you want to use a Windows Microsoft Cluster Service (MSWC) based file server as thesecondary storage in the FileMover environment, you need VNX version 5.3.23.0, 5.4.20.0,5.5, or later.

◆ NDMP Volume Backup (VBB) does not support the NDMP environment variableEMC_OFFLINE_DATA. In this case, the contents of archived files—the offline files—onthe secondary storage must be backed up independently.

◆ fs_dhsm does not support IPv6.

Cautions and warnings

If any of this information is unclear, contact an EMC Customer Support Representative forassistance.

◆ When the read policy value is set to the partial option, a partially recalled file remainsintact on the VNX until one of the following occurs:

• The recall operation is completed in response to a VNX for File client reading theremainder of the file.

• The policy and archiving application reissues a VNX FileMover API call to free thedata blocks associated with the recalled data.

◆ Only policy and archiving applications and backup applications should be allowed tomodify the archived data on secondary storage. Otherwise, archived data on the secondary

Cautions and warnings 11

Introduction

storage must not be modified. Any modification of archived files on the secondary storagecauses the files to be inaccessible through the stub file on VNX.

◆ VNX FileMover compares the modification time (mtime) kept by the stub file to themtime on the file on the secondary storage to ensure the two remain synchronous. If thestub files are restored from an EMC SnapSure™ checkpoint with an mtime different fromthe mtime of the secondary storage file, depending on the policy and archiving applicationin use, the data might be unavailable on the primary file system.

This caution also applies to tape backup, a BCV for either EMC TimeFinder®/FS orTimeFinder/FS NearCopy (which uses SRDF®/S), or an STD volume for TimeFinder/FSFarCopy (which uses SRDF adaptive copy write pending mode). Contact your softwarevendor to determine whether your policy and archiving application supports multiplefile archiving.

◆ Depending on the policy and archiving application in use, if a file is archived more thanonce and a backup occurs between archiving, such as SnapSure checkpoint refresh orTimeFinder/FS Snapshot refresh, the file on the secondary storage becomes inaccessiblethrough the stub file in the SnapSure checkpoint, TimeFinder/FS NearCopy, andTimeFinder/FS FarCopy.

You might experience the same behavior on the secondary file system of EMC VNXReplicator™ if a file is archived more than once and the file systems have not yetsynchronized.

If your policy and archiving application supports multiple file versions, which is theability to store multiple versions of a single file, it is likely the archived file content isaccessible through the stub file in the backup.

Contact your software vendor directly to determine whether your policy and archivingapplication supports multiple file archiving.

◆ When you are working with the VNX FileMover log files in the /.etc directory of the filesystem, be careful not to touch any other files in the same directory.

◆ EMC recommends you disable logging on the primary file system before removing anydhsm_log.* files in the /.etc directory of the primary file system.

◆ VNX FileMover can manage a maximum pathname length of 1,024 bytes (not characters).However, the actual maximum pathname length depends on the policy and archivingapplication, file system type and operating system of the policy and archiving applicationor the secondary server, the device format connected to the secondary server, and so on.The lowest maximum pathname length supported for any of these elements is the actualmaximum pathname length in the environment.

◆ The primary VNX, the secondary file server, and the policy and archiving applicationmust use the same locale. Planning application integration on page 38 contains moreinformation about international character set support.

◆ If you intend to use VNX FileMover with existing VNX features such as internationalcharacter sets, SnapSure, quotas, or the AntiVirus Agent, review Planning applicationintegration on page 38.


Introduction

User interface choices

This document describes how to set and manage the VNX for File side of VNX FileMoverby using the command line interface (CLI). You cannot use other VNX managementapplications to configure VNX FileMover.

Related information

Specific information related to the features and functionality described in this document isincluded in:

◆ EMC VNX Command Line Interface Reference for File

◆ Online VNX for File man pages

◆ Parameters Guide for VNX

◆ Security Configuration Guide for File

VNX FileMover information that is related, but is beyond the scope of this document, isincluded in VNX FileMover API Integration Guide.

EMC VNX documentation on EMC Online Support

The complete set of EMC VNX series customer publications is available on EMC OnlineSupport. To search for technical documentation, go to http://Support.EMC.com. Afterlogging in to the website, click Support by Product and type VNX series in the Find aProduct text box. Then search for the specific feature required.

VNX wizards

Unisphere software provides wizards for performing setup and configuration tasks. TheUnisphere online help provides more details on the wizards.

User interface choices 13

Introduction



Introduction

2

Concepts

VNX FileMover helps you to place the right data in the right location atthe right time when combined with policy and archiving application anda secondary storage infrastructure, enabling you to build an ILM solutionfor VNX data. In the VNX FileMover environment, the VNX is the primarydata storage while the secondary storage might be another VNX or anetwork file server supporting CIFS, NFS, HTTP, or HTTPS.

A combination of policies or rules helps VNX FileMover determine whetherfiles should be automatically archived from higher-speed, costly primarystorage to slower, less-expensive storage devices and back again. The VNXimplements the migration method options that determine whether a fileshould be recalled from secondary storage. Commonly used archivingpolicies are those that archive older, less frequently used files or files of aparticular type, such as MPG files. Files, not symbolic links or directories,are targeted for archiving.

The file archiving and retrieval process is automatic and completelytransparent. When you access a file on the server, the file is immediatelyaccessible and you can process data as though it were stored on primarystorage. However, archived files can take longer to access than files thathave not been archived.

Topics included are:◆ Connection types on page 17◆ Archive operation on page 18◆ Write operation on page 20◆ Read operation on page 21◆ VNX FileMover configuration and management on page 24◆ Planning storage requirements on page 25◆ Planning orphan file management on page 27◆ Planning backup strategies on page 27◆ Planning file system usage on page 29◆ Planning network traffic on page 29


◆ Planning for read-only file systems on page 29◆ Planning interactions between VNX FileMover and your applications

on page 30◆ Planning file system scanning performance on page 30◆ Planning secondary hostname resolution on page 30◆ Planning application integration on page 38


Concepts

Connection types

The connection to the secondary storage can be a CIFS, NFS, HTTP, or HTTPS connection.

CIFS connection

When defining a CIFS connection, you define the credentials of the user account thatVNX will use when reading files from the secondary storage CIFS server. Any CIFSserver should work, but check with the policy and archiving application vendor to seewhat that vendor supports. Also, VNX for File does not support archiving to a CIFSserver identified by a Windows DFS name; it must connect to the real server name.

NFS connection

When defining an NFS connection, you define the credentials that VNX will use whenreading files from the secondary storage NFS server. Any NFSv3 server should work,but check with the policy and archiving application vendor to see what that vendorsupports. VNX does not support using NFSv4 to connect to a secondary storage server.

HTTP connection

There are two types of HTTP connections: CGI and non-CGI. Use the -cgi option tospecify the type of HTTP connection that you want to create. By default, VNX FileMoverassumes an HTTP server hosted on the secondary storage is using CGI connections toaccess archived file data through a CGI application. The default port to which the DataMover sends its requests over HTTP is port 80. When the -cgi option is set to yes, youmust configure the application to send an HTTP response describing the health statusof the secondary storage. CGI connections require that the -secondary option be used toidentify the CGI application residing on the HTTP server.

HTTPS connection

HTTPS connections are very similar to HTTP connections, except that HTTP traffic issent over SSL when HTTPS connections are used. Like HTTP connection, HTTPSconnection can also be of two types: cgi and non-cgi. HTTPS uses basic authentication,and encryption done by SSL. The default port to which the Data Mover sends its requestsover HTTPS is 443. HTTPS connections to a secondary server require the secondaryserver's CA certificate to be installed on the Data Mover by using the server_certificatecommand. This enables the Data Mover's HTTPS client to validate the secondary server'sSSL certificate.

Connection types 17

Concepts

Archive operation

A file is usually targeted for archiving based on its attributes, such as file size, file type, orperiod of inactivity.

As shown in Figure 1 on page 18, the policy and archiving application periodically searchesthe system for files that match policies preset by customers. When the policy and archivingapplication finds a match, it archives or reads the file from the system, and then writes it tothe secondary file server by using HTTP, HTTPS, NFS, or CIFS. Finally, the policy andarchiving application issues a command through the VNX FileMover API to convert the fileto a stub file. This action frees the storage associated with the file and completes the archivingoperation.

When a file is archived, its data is moved to a file on the secondary storage, and the originalfile is replaced with a stub file. The stub file contains all the metadata associated with theoriginal file—permissions, timestamps, size, attributes, and alternate data streams. The stubfile also contains additional data associated with the FileMover functionality, including thelocation of the file content on the secondary storage, the identity of the policy and archivingapplication that archived the file's content, and an information field in which the policy andarchiving application can store any additional information it deems necessary. In the primaryfile system on the system, a stub file consumes one inode and one 8 KB data block, plus thesize of any alternate data streams associated with the file.

PS0 PS1 PS2 PS3 PS4 SMB0 SMB1

SB

0

SB

1

SB

2

SB

3

SB

4

SB

5

SB

6

SB

7

SB

8

SB

9

SB

10

SB

11

SB

12

SB

13

SB

14

SB

15

2. Read file

Policy /archiving

application

VNX

NAS clients

3.W

ritefile

conte

nts

4. Create stub file

1. Search

NFS / CIFS

NFS / CIFS / HTTP

FileMover API

VNX-000016

Centera ATA Tape

Secondary storage file server

Figure 1. VNX FileMover archiving operation

To estimate archiving time, you might consider the time it takes for the policy and archivingapplication to search for and archive data from the system to the secondary storage throughthe network. The size of the directory tree, network speed, and policy and archivingapplication resources help determine the amount of time it takes for the policy and archivingapplication to search and archive the data. The time it takes to replace an original file witha stub file after it has archived the data to the secondary storage is a relatively small overhead.System requirements on page 10 contains information about network requirements.


Concepts

The search operation scans all directories on the primary file system for files specified bythe policy and archiving application even if there is no file match for archiving. Becausesearching uses the Data Mover and network resources, EMC strongly recommends that youschedule archiving and search operations to occur at a time when the Data Mover is lessused. FileMover supports an option that allows the system to perform file system scans onbehalf of the policy and archiving application.This can significantly reduce the time requiredto discover candidates for archiving. This also optimizes the load on the network and thepolicy and archiving application host. Contact the policy and archiving application vendorto determine if it supports the FileMover Bulk Attribute Retrieval (BAR) functionality.

Note: The policy and archiving application server can be a secondary server. Review your policy andarchiving application documentation for more information about policy and archiving applicationperformance.

Protecting the user’s view of archived files

In some cases, the secondary storage may provide the option to ensure that the archiveddata cannot be modified or removed for a specified period of time. The user's view ofarchived files can be protected for the same period of time that the archived data isprotected by the secondary storage system, delivering a more robust and transparentfile archiving solution.

When the policy and archiving application archives files to the secondary storage, it mayapply retention date-based protection to the archived data. When it instructs the systemto convert the original file in the primary file system on the system with a stub file thatreferences the archived data on the secondary storage, it can instruct the system to protectthe stub file until a specified date. Typically, the policy and archiving application willcoordinate the retention dates applied to both the archived data and the stub file so thatthe user's view of the stub file is protected for the same length of time as the archiveddata.

Protection of VNX FileMover stub files is managed by using the policy and archivingapplication, which in turn uses the VNX FileMover API to instruct the system to protectstub files. This architecture gives customers the freedom to choose from numerousindustry-leading applications, deploying the one that best suits their specific operationalneeds.

File systems described in this solution are not required to be FLR-enabled. The file systemof the primary storage device cannot be an FLR-enabled file system. The file system (orequivalent) of the secondary storage device may be FLR-enabled, but it is not arequirement for this feature to work.

Contact the policy and archiving application vendor to see if it supports this functionality.

Archive operation 19

Concepts

Write operation

VNX clients write file data to the VNX system through NFS, CIFS, or FTP as illustrated inFigure 2 on page 20. Until the policy and archiving application archives a file, the filephysically resides on the system and write operations proceed normally.

When a file is archived from the system to the secondary storage, the policy and archivingapplication copies all the file’s data to a file on the secondary storage and converts the originalfile to a stub file. The stub file contains all the file’s metadata, including the file's actuallocation on the secondary storage.


SB

0

SB

1

SB

2

SB

3

SB

4

SB

5

SB

6

SB

7

SB

8

SB

9

SB

10

SB

11

SB

12

SB

13

SB

14

SB

15

Centera ATA Tape


2. Modify file

1. Recall file

VNX

NAS clients

NFS / CIFS

NFS / CIFS / HTTP

VNX-000017

Figure 2. VNX FileMover write operation

Writing to archived files

When a write operation occurs, the system uses the information in the stub file to locatethe file on the secondary storage. It then compares the modification time (mtime) andsize it has stored with the current mtime and size of the file on the secondary storage.This comparison ensures that the stub file and archived file remain synchronous. Whenthese attributes match, the file data is returned to the system and the write operationproceeds. If the attributes differ, an error message appears. The system will not returnpotentially corrupt file data.

Note: For HTTP and HTTPS connections, comparisons of mtime and the entity tag are done toensure that the file on the secondary storage has not been changed.

There are two ways in which client applications can write to archived files on a file server.The client can either modify a portion of a file or replace the entire file.


Concepts

If the write operation is modifying a portion of an archived file, the system recalls theentire file to the primary storage. The file replaces the stub file to allow the client toproceed with the write operation. If the client is truncating the file, the system only recallsthe data up to the truncation point before replacing the stub file. The file remains on thesystem until the policy and archiving application determines that it should be movedback to the secondary storage. At that time, the file's full pathname is once again in thestub file and its data is stored on a secondary file server. Stub files with retention dateprotection settings cannot be modified or truncated by write operations.

Note: If there is not enough space on the file system, or the user, group, or tree quota limits havebeen exceeded, file data cannot be recalled and the client write request fails. The original file andthe stub file are unchanged.

If the write request is an attempt to rewrite an entire file, the client application truncatesthe file to zero, thus causing the file server to discard the existing contents of the file.After a file is truncated, whatever the application writes to the file becomes the file’s newcontent. When the system detects a truncated file, it marks the file as one that belongson the primary storage. There is no need to recall any data from the secondary storage.

Note: If there is inadequate space on the file system or quota limits are exceeded during a rewriterequest, there will be partially written files on the primary file system.

Read operation

Until the policy and archiving application archives a file, the file physically resides on theVNX system and client read operations proceed normally. When a file is archived onsecondary storage, the file contents are copied to a file on secondary storage and the originalfile is converted to a stub file. The stub file contains all the file’s metadata including its actuallocation on secondary storage, mtime, size, and its archiving method, which is set for eachindividual file when the file is archived.

When a client attempts to read an archived file, the VNX system accesses the informationin the stub to locate the file on the secondary storage server as illustrated in . When the VNXsystem reads the contents of an archived file, it compares the mtime and size it has storedfor the file with the current mtime and size of the file on secondary storage. This comparisonensures that the stub file and the archived file remain synchronous.

Note: For HTTP and HTTPS connections, comparisons of mtime and the entity tag are done to ensurethat the file on secondary storage has not been changed.

The amount of file data recalled during a read operation depends on the archiving methodspecified on the file and the amount of data the application actually reads during access.Depending on the type of client I/O (read or write operation) and the archiving methodspecified in the stub file, connection, or file system level, VNX might replace the stub fileon primary storage with the recalled data or leave the file in an archived state.

Read operation 21

Concepts

With the exception of CIFS backup, all NFS and CIFS applications cause file data to berecalled during read operations.

Note: Archiving method options are sometimes referred to as read policies and read methods.


SB

0

SB

1

SB

2

SB

3

SB

4

SB

5

SB

6

SB

7

SB

8

SB

9

SB

10

SB

11

SB

12

SB

13

SB

14

SB

15

Centera ATA Tape


1. Read file contents

VNX

NAS clients

NFS / CIFS

NFS / CIFS / HTTP

VNX-000018

2. Read file

The read operation may, or may not,replace the stub file on theVNX Network Server.

Figure 3. VNX FileMover VNX for File client read of an archived file

Note: A customer-defined archiving method specified on an individual file, connection, or primaryfile system determines whether the file’s content is recalled from secondary storage to VNX in responseto the client request. The read operation might or might not replace the stub file on VNX.

VNX FileMover is designed such that the policy and archiving application is not part of thefile data recall process. Data archiving and data recall are automatic and completelytransparent to VNX for File clients and have no effect on the availability or integrity of data.

For example, if the archiving method is set to full, VNX recalls all the file data to primarystorage in response to the read request. However, if the method is set to the defaultpassthrough, the file data is retrieved and returned to the client, but the original file is notrecalled to the VNX system.

Reading archived file data

The archiving method for read operations is set to passthrough by default. If an archivingmethod is not specified in the file, and the connection or file system overrides are set tonone, the passthrough option is used. Files that have retention date protection settingsare read through the passthrough method regardless of the file system connection or filepolicy.

When a client attempts to read an archived file, the VNX system recalls file data basedon one of the three archiving method options set by the policy and archiving application:


Concepts

◆ Passthrough

VNX reads the requested data from secondary storage and returns it to the clientimmediately. None of the file’s data is recalled to primary storage; the file remainson the secondary storage.

The passthrough option (default) ensures that archived files remain archived regardlessof how often the files are read. This option is also applicable as an override settingon a connection (secondary storage) or primary file system. For example, you mightuse the passthrough option when you want to prevent an operation, such as a searchfor specific content in all files, from prompting a massive unintended recall of archivedfiles to primary storage.

◆ Partial

VNX recalls only as much of the file’s contents—in part or whole—as it needs tosatisfy the client read request. The data is retrieved and returned to the client whenVNX receives it from the secondary storage. In addition, if a VNX for File client readsthe same data again, VNX retrieves the data from the partially recalled file; the datadoes not need to be recalled from the secondary storage.

Use of the partial option is applicable in the same situations where you might use thefull option. You might use partial for files that are read frequently and thus shouldhave the performance benefit of being on primary storage. The additional benefit isthat client read requests of large files complete more quickly because the VNX systemrecalls only the data requested before responding to the client request.

◆ Full

VNX recalls all file data to primary storage when the file is first accessed for read,which maximizes the performance of subsequent read or write operations. It isimportant to realize that when VNX recalls large files to satisfy a read request, theread operation might take time to complete.

This behavior emulates that of traditional hierarchical storage management (HSM),where the entire file must be recalled from secondary to primary storage before clientaccess is possible.

Note: In some cases, the primary Data Mover might not need to retrieve data from secondarystorage because the data already resides in the cache of the primary Data Mover.

Archiving method selection

The archiving method associated with each stub file can be overridden at the connectionor primary file system level by using the -read_policy_override option of the fs_dhsmcommand.

The archiving method for a read operation is determined as follows:

Read operation 23

Concepts

◆ If the file system is read-only, or if the stub file has had retention date protectionapplied to it, the passthrough option is used.

◆ If the file is currently being backed up by an NDMP or CIFS backup application byusing options to read archived data, or is being scanned by CAVA, the passthroughoption is used.

◆ The file system archiving method, when specified, takes precedence over theconnection and stub file settings.

◆ The connection archiving method, when specified, takes precedence over the optionset in the stub file.

◆ The stub file archiving method, when specified, is used. Otherwise, the policy defaultsto the passthrough option.

◆ If attempts to recall data produce an error related to insufficient space or quotas,FileMover attempts to reread the data by using the passthrough option.

VNX FileMover configuration and management

After a file system and an associated Data Mover are enabled and configured for VNXFileMover on the VNX system, the day-to-day management of VNX FileMover is performedby using the policy and archiving application. This document does not discuss the installation,configuration, and management of the policy and archiving application. Contact yoursoftware vendor or read your policy and archiving application documentation for moreinformation.

Systems with version 5.6 of the software support a management API, which the policy andarchiving application can use to perform management operations such as modifyingFileMover API users and hosts, and creating, modifying, and deleting FileMover secondarystorage connections from the software’s user interface. Contact the policy and archivingapplication vendor to see if it supports this feature. Otherwise, you must perform thesemanagement operations from the Control Station CLI.

VNX FileMover can be used in multiprotocol environments.This means NFS, CIFS, HTTP,and HTTPS file servers can be used as secondary storage regardless of the protocol clientsuse to access archived files. This is because the metadata associated with an archived file isin a stub file; only the content of the file is archived to secondary storage. Managing aMultiprotocol Environment on VNX contains detailed information about how to configure theVNX system for use in a multiprotocol environment.

Note: If the policy and archiving application does not perform these management operations, the VNXfor File administrator must do them. The policy and archiving application documentation providesmore information to enable you to perform the FileMover configuration. You can also perform theoperations by using EMC Unisphere® software.


Concepts

Creating the connection to the secondary storage

Enable VNX FileMover on the file system, and then create a connection to a secondaryfile server. You can archive files to or recall files from the secondary storage only if thesecondary file server connection is established. The policy and archiving applicationmust have read or write access to the secondary file server; VNX requires read accessonly. The connection to the secondary storage can be a CIFS, NFS, HTTP, or HTTPSconnection.

Note: VNX for File clients must not be allowed to modify the archived data on secondary storage.Any modification of archived files on the secondary storage causes the files to be inaccessiblethrough the stub file on VNX.

Managing the VNX FileMover file system

After enabling VNX FileMover on a file system and establishing a connection to thesecondary storage device, you can perform several management tasks. By using theoptions in the fs_dhsm command, you can list VNX FileMover attributes, modify theVNX FileMover connection, set or query file system parameters, and disconnect theconnection.

Configuring API security

The Data Mover must be configured to work with the policy and archiving application.The VNX FileMover API service is started on the Data Mover port 5080. It uses the HTTPor HTTPS protocol to allow the policy and archiving application to archive files andquery the VNX system for file attributes.

The process of configuring security options might involve the following:

◆ Configuring the Data Mover’s HTTP or HTTPS server by using the server_httpcommand

◆ Using the server_user command to add users to the Data Mover’s local password file

Note: This HTTP and HTTPS server in the VNX Data Movers is intended for use by the VNXFileMover API and Management APIs only. It is not for use by any other HTTP clients.

Planning storage requirements

When you design an ILM solution based on VNX FileMover, you need to consider therelative space requirements for primary and secondary storage.

Planning storage requirements 25

Concepts

Setting primary and secondary storage size

Primary storage must be large enough to store all the files you do not plan to archive tothe secondary storage and the stub files representing all archived files. Stub files typicallyoccupy 8 KB of space on primary storage.

The secondary storage device must be a CIFS, NFS, HTTP, or HTTPS server. Secondarystorage must be large enough to store all the files that you intend to archive. It is alsoimportant to consider the amount of file data, as well as the number of objects such asfiles, directories, and symbolic links that the secondary storage device needs to manage.You can associate up to 1,024 secondary storage locations with a single primary filesystem; storage space can be spread over a number of devices. Contact your softwarevendor directly for advice on dimensioning your secondary storage.

You should also consider the amount of data that will be written to primary storagebefore the policy and archiving application is able to archive the data to secondarystorage. Be mindful about keeping an amount of space available on primary storage forany new files being created. Space is also needed to recall archived files if they are writtento, or recalled, in response to a client request. Storage space requirement example onpage 94 provides additional information about space requirements.

In the Microsoft Windows Explorer Properties dialog box, the Size on disk property forthe stub file displays the logical size of the file or its true size on disk, if file size quotapolicy was selected. The size shown is dependent on the quota policy on VNX. Quotason page 38 contains more information about quota policy settings. When viewing a stubfile with Windows Explorer from an XP client, stub files might appear to have a logicalsize and disk size of 0 bytes. This happens because that version of Windows Explorersets the backup intent flag, and all the following conditions must be true to encounterthis anomaly:

◆ Windows XP client is used (Windows 2000 can be used).

◆ The XP client (or Windows 2000) has mapped the share by using an account withAdministrative or backup privileges on the Data Mover.

◆ The FileMover-enabled file system is using an offline attribute backup instead of apassthrough backup for CIFS.

A multiple hop configuration (multihop) allows you to move data from primary tosecondary storage, from secondary to tertiary storage, and back. A FileMover-enabledfile system can be secondary storage. In a multihop configuration, secondary storagemust be a VNX while tertiary storage can be either a VNX or an NFS, HTTP, HTTPS, orCIFS file server. Although FileMover supports a multihop configuration of up to twohops, a better way of implementing this is for the policy and archiving application tomove the archived content to its new location and update the stub file on the VNXaccordingly. Contact your policy and archiving application vendor for the most up-to-dateinformation about multihop configurations.


Concepts

Archiving small files

Each stub file occupies a minimum of 8 KB and a maximum of 64 KB of space on primarystorage. If you intend to archive files to release space on primary storage, it is importantto realize there is no advantage in archiving any file less than 8 KB. However, if you needto archive files for compliance purposes, you might choose to archive files regardless oftheir size.

Note: EMC recommends that you do not archive zero-length or empty files to secondary storageas CIFS and NFS protocols never issue a read request against a zero-byte file. VNX FileMoverrecalls a zero-byte file only when the file is written to; it does not recall the file if it is read.

Planning orphan file management

When a file is archived from the VNX system to the secondary storage, the original filephysically resides on the secondary file server and a stub file replaces the original file onthe VNX system. If the stub file on VNX is deleted, the file data on the secondary storagebecomes orphaned with respect to VNX. If this happens, the VNX system does not deletethe file content on the secondary storage.

Note: There might be a copy of that stub file in a SnapSure checkpoint of the primary file system, aTimeFinder/FS or VNX Replicator copy of the primary file system, or on a backup tape, which mightneed to reference the content on the secondary storage. For this reason, it is important that the secondarystorage file content remain intact until all copies of a stub file that reference the archived content havebeen deleted.

VNX FileMover does not automatically delete orphan files on the secondary storage. Youdetermine how long you want to retain access to the content on secondary storage throughalternative copies of a deleted stub file.

Contact your software vendor or read your policy and archiving application documentationfor information about orphan file management and multiversioning of files on the secondarystorage.

Planning backup strategies

Table 2 on page 28 lists backup behaviors of FileMover-enabled file systems.

Planning orphan file management 27

Concepts

Table 2. Backup behaviors

Back up the contents of archivedfiles on secondary storage withoutrecalling the files to primary storage

Back up the stub files and online filecontent on primary storage

Backup type

Set the NDMP variable to:

EMC_OFFLINE_DATA=y

DefaultPerform an NDMP backup on page 74

By default, the -backup option is set topassthrough

Set the primary FileMover file system -backup option to offline

Perform a CIFS network backup onpage 75

Set the FileMover file system -read_policy_override option topassthrough

N/APerform an NDMP backup on page 74

N/ADefaultserver_archive

There are two ways to back up FileMover-enabled file systems: from primary only, or fromprimary and secondary.

Backing up from primary only

When backing up from primary only, the online file content on primary storage and thearchived file content on secondary storage, the offline files, are backed up.

For NDMP backups, set the NDMP environment variable in your backup software toback up file contents of archived files on secondary storage. Archived file content isbacked up without recalling the files to primary storage. Perform an NDMP backup onpage 74 provides instructions for setting the NDMP environment variable.

For CIFS network backups, the -backup option is set to passthrough by default. Files arebacked up to the backup application without being recalled to primary storage.

For NFS backups, set the -read_policy_override option to passthrough to back up archivedfile contents, also called offline files, without recalling the files to primary storage. Youcannot back up the stub files in the primary file system by using NFS backup. Performan NFS network backup on page 76 contains procedural information.

Note: If the network between the servers hosting the primary and secondary storage is slow, orthe secondary server’s response is slow, backup performance might be impacted as the dataassociated with the file from secondary storage is put into the backup stream. Some applicationsmight experience errors such as time-out.


Concepts

Backing up from primary and secondary

By default, NDMP backs up and restores stub files and files that have not been archivedfrom primary storage—also called online files. The contents of archived files—or offlinefiles—on secondary storage must be backed up independently.

For CIFS network backups, set the -backup option to offline to back up stub files andonline files—the files that have not been archived from primary storage. The contentsof archived files—or offline files—on the secondary file server must be backed upindependently. Perform a CIFS network backup on page 75 contains proceduralinformation.

For NFS, it is not possible to back up only the stub files.

Planning file system usage

Use the server_df command to obtain the actual usage of a VNX FileMover file system. If afile is partially recalled from secondary storage, another inode is allocated for this partialfile. This command counts all the inodes on the VNX system, including the inodes associatedwith partially recalled files. Planning application integration on page 38 contains moreinformation about quotas.

Planning network traffic

For maximum performance and security, consider managing the network traffic betweenthe VNX system, the policy and archiving application, and the secondary storage to travelthrough a private, high-speed (Gigabit Ethernet) network. In this case, you can use thestandard VNX network traffic monitoring capabilities to monitor the FileMover traffic levelsin the environment.

You can use trunking, Fail-Safe Network, and LACP to maintain a high-availability networkbetween the VNX system and the secondary storage. There is no automatic network failoverfunctionality in VNX FileMover. Configuring andManaging Network High Availability on VNXprovides additional information.

Note: If the network between the servers hosting the primary and secondary storage is slow, or thesecondary server’s response is slow based on access time to the connected device, some applicationsmight experience errors such as time-out.

Planning for read-only file systems

Changes to FileMover parameters at the connection and file system level on a read-onlyVNX FileMover-enabled file system are not persistent; they are in memory only. Rebootsor remounts cause the settings to revert to their former state.

Planning file system usage 29

Concepts

Planning interactions between VNX FileMover and your applications

It is important to understand file system usage as well as the behavior of the applicationsassociated with the VNX FileMover file system. For example, some applications causearchived files to be recalled unexpectedly.

When you perform a content search, VNX FileMover reads the content of archived files fromsecondary storage in the same manner as all other read request operations. However, in anenvironment where content searching is performed, EMC strongly recommends that youset the archiving method to passthrough to avoid data from being mistakenly recalled toprimary storage.

Planning file system scanning performance

EMC has enhanced VNX FileMover to improve file system scanning performance for thepolicy and archiving application. The Bulk Attributes Retrieval (BAR) operation allows aFileMover policy and archiving application to request the VNX Data Mover to scan a filesystem and locate files matching criteria defined by the policy and archiving application. Avariety of search criteria can be specified in the scan request, such as timestamp, file size,and file type.

When matching files are found, the metadata—or file attributes—associated with those filesare written to an output file located on a VNX file system. Because the content of outputfiles might be sensitive in nature, EMC strongly recommends creating a file system specificallyto hold output files and to be accessible only to the policy and archiving application thatinitiated the metadata retrieval request.

Under normal circumstances, the policy and archiving application deletes output files nolonger required. Occasionally, the administrator might have to clean up output files if thepolicy and archiving application fails to do this.

Planning secondary hostname resolution

The Data Mover can use CIFS, NFS, or HTTP to recall archived data from the secondarystorage. For the purposes of a FileMover deployment, this section provides some generalrecommendations and discusses NFS and CIFS together, and then discusses HTTP separately.

You can set up secondary servers for:

◆ Single site deployment◆ Dual site deployment

VNX FileMover secondary server hostname resolution recommendations

EMC recommends always using hostnames in HTTP or NFS/CIFS secondary connections.


Concepts

Note: VNX will accept IPv4 addresses in both NFS/CIFS and HTTP secondary connections. However,EMC does not recommend using IPv4 addresses because it makes reconfiguring the environmentharder and it is not allowed by RFC 2616.

◆ For single site deployments:

• Use DNS if you have only one secondary server or if you have more than oneserver, but do not want to specify which server to use for recall traffic.

• Use local hosts files on Data Movers if you will be using multiple HTTP secondaryservers and want to prioritize which server each Data Mover will use for recalltraffic.

◆ For dual site Disaster Recovery deployments:

• EMC recommends using local hosts files on Data Movers for FileMover secondaryserver hostname resolution in dual-site DR deployments. DNS hostname resolutionfor dual site Disaster Recovery deployments on page 37 contains recommendationsif you must use DNS.

• You can use local hosts files to allow for the direction of traffic to local secondaryservers. This requires no change on file system failover to the remote site.

• Add the IP addresses of the secondary servers at the remote site to each DataMover’s hosts file to have it use the remote secondary servers automatically in theevent that the local servers are unavailable.

• Ensure that the hosts files are not accidentally copied between Data Movers atdifferent sites, thereby undoing the local site customization.

HTTP hostname resolution for single site deployment

VNX recalls files from HTTP secondary servers, which in turn read data from thesecondary storage. An EMC Centera® is shown in Figure 4 on page 32. The HTTP serverprovides an HTTP gateway to the secondary storage such as an EMC Rainfinity® FMA.

Planning secondary hostname resolution 31

Concepts

While it is possible to deploy a single HTTP server to provide access to the secondarystorage, EMC recommends deploying two to provide high availability as shown in Figure6 on page 34.


SB

0

SB

1

SB

2

SB

3

SB

4

SB

5

SB

6

SB

7

SB

8

SB

9

SB

10

SB

11

SB

12

SB

13

SB

14

SB

15

VNX Data Mover

HTTP

10.0.0.100 10.0.0.101

HTTP

Centera VNX-000019

HTTP Server 1 HTTP Server 2

Figure 4. HTTP server single site deployment

You can place the IP addresses of the secondary HTTP servers into DNS and allow theData Movers to use DNS to resolve the hostnames to IP addresses. However, most DNSservers will return the IP addresses associated with a hostname in a different order eachtime. This means that you have no control over which HTTP secondary server the DataMovers will use.

To prioritize the HTTP servers to use for recalling archived data, add IP address entriesto the local hosts file on each (physical) Data Mover that is hosting a primary file system.This directs the Data Mover to use the HTTP servers in the order specified in the localhosts file.

If multiple Data Movers host primary file systems, you can change the IP address orderingfor each Data Mover to distribute the recall traffic load among the secondary storageservers.

Add one line for each HTTP server. For example, if using two HTTP servers, the hostsfile might contain the following:

# <IP address> <hostname>10.0.0.100 secstore # HTTP server 110.0.0.101 secstore # HTTP server 2


Concepts

Note: IP addresses do not have to be on the same subnet.

When there is only one HTTP server, the hosts file would contain only one entry. In thiscase, there is no difference between using a local hosts file and DNS.

NFS/CIFS hostname resolution for single site deployment

The system recalls files from the NFS/CIFS secondary servers directly. An NFS/CIFSserver can be a Data Mover or other NFS or CIFS server. Figure 5 on page 33 shows anNFS/CIFS server.


SB

0

SB

1

SB

2

SB

3

SB

4

SB

5

SB

6

SB

7

SB

8

SB

9

SB

10

SB

11

SB

12

SB

13

SB

14

SB

15

VNX-000021

VNX Data Mover

10.0.0.100

NFS/CIFS

NFS/CIFS Server

Figure 5. NFS/CIFS server single site deployment

To recall archived data from an NFS/CIFS server, add an entry for the secondary serverto DNS or to the local hosts file on each (physical) Data Mover that is hosting a primaryfile system.

For example, the hosts file might contain the following:

# <IP address> <hostname>10.0.0.100 secstore # NFS/CIFS server


HTTP hostname resolution for dual site deployment

Figure 6 on page 34 shows two secondary sites. The Data Movers on both Site A andSite B connect through two HTTP servers to the EMC Centera.


Concepts

For high availability, you can have two HTTP servers at each site, but it is possible touse just one HTTP server at either site if desired.


SB

0

SB

1

SB

2

SB

3

SB

4

SB

5

SB

6

SB

7

SB

8

SB

9

SB

10

SB

11

SB

12

SB

13

SB

14

SB

15


SB

0

SB

1

SB

2

SB

3

SB

4

SB

5

SB

6

SB

7

SB

8

SB

9

SB

10

SB

11

SB

12

SB

13

SB

14

SB

15

Asynchronousreplication

VNX-000020

VNX Data Mover

HTTP

10.0.0.200 10.0.0.201

HTTP

Centera


VNX Data Mover

Site BSite A

Synchronous orasynchronous replication

HTTP

10.0.0.100 10.0.0.101

HTTP

Centera


Figure 6. HTTP server dual site deployment

HTTP hostname resolution for dual site Disaster Recovery deployment

To recall archived data from HTTP servers on a local site, add IP address entries to thelocal hosts file on each (physical) Data Mover that is hosting either a primary file systemor a replica of one. This directs the Data Mover to use the HTTP servers, and hencesecondary storage (EMC Centera in this example), at the local site when reading datafrom the archive.

If multiple Data Movers host primary file systems, you can change the IP address orderingin the local hosts file of each Data Mover to distribute the recall traffic load among thesecondary storage servers.

Add one line for each HTTP server to each local hosts file on the multiple sites. Eachhosts file must contain the HTTP server information for that specific site.

For example, if Site A is using two HTTP servers, the hosts file might contain thefollowing:

# <IP address> <hostname>10.0.0.100 secstore # HTTP server 1 at Site A10.0.0.101 secstore # HTTP server 2 at Site A

Also, if Site B is using two HTTP servers, the hosts file might contain the following:


Concepts

# <IP address> <hostname>10.0.0.200 secstore # HTTP server 1 at Site B10.0.0.201 secstore # HTTP server 2 at Site B


When there is only one HTTP server at a site, the hosts file would contain only one entryfor that site.

You do not need to make any changes to name resolution on a VNX file system failover.If the local HTTP servers fail, the Data Mover will not use those at the remote site.

If you want the Data Movers to use the HTTP servers at the remote site in the event thatnone of those at the local site are functional, you can either modify the hosts file for eachData Mover at failure time to include the HTTP servers at the remote site, or you canadd the IP addresses of the HTTP servers at the remote site to each Data Mover's localhosts file ahead of time; it will use them automatically if it cannot contact the local HTTPservers. HTTP hostname resolution with cross-site traffic on secondary failure on page35 contains details.

HTTP hostname resolution with cross-site traffic on secondary failure

To recall archived data from either HTTP servers on a local site or HTTP servers on aremote site if the local HTTP servers are unavailable, add entries to the local hosts fileon each (physical) Data Mover that is hosting a primary file system, or a replica of one.This directs the Data Mover to use the HTTP servers at the local site first, and only usethose at the remote site if the local ones are unavailable.

If it is available, use the "delayed stubbing" functionality of the policy and archivingapplication to ensure that archived data is replicated to the remote site before any stubfile references it.

Configuring the local hosts files ahead of time means that you do not need to make anychanges to name resolution on a VNX file system failover. However, be aware that oncea Data Mover HTTP client starts using an HTTP server at a remote site, the Data Movercontinues to do so until the HTTP server on the remote site stops responding or youforce it to change HTTP server. Forcing a Data Mover to stop using a secondary HTTPserver on page 98 contains more details.

Add one line for each HTTP server to each local hosts file on the multiple sites.

For example, the Site A Data Mover local hosts file might contain the following whenusing two HTTP servers at both Site A and Site B:

# <IP address> <hostname>10.0.0.100 secstore # HTTP server 1 at Site A10.0.0.101 secstore # HTTP server 2 at Site A10.0.0.200 secstore # HTTP server 1 at Site B10.0.0.201 secstore # HTTP server 2 at Site B

Also, the Site B Data Mover local hosts file might contain the following when using twoHTTP servers at both Site B and Site A:


Concepts

# <IP address> <hostname>10.0.0.200 secstore # HTTP server 1 at Site B10.0.0.201 secstore # HTTP server 2 at Site B10.0.0.100 secstore # HTTP server 1 at Site A10.0.0.101 secstore # HTTP server 2 at Site A


NFS/CIFS hostname resolution for dual site deployment

Figure 7 on page 36 shows two secondary sites. The VNX recalls files from the NFS/CIFSsecondary servers directly. An NFS/CIFS server can be a VNX Data Mover or other NFSor CIFS server.


SB

0

SB

1

SB

2

SB

3

SB

4

SB

5

SB

6

SB

7

SB

8

SB

9

SB

10

SB

11

SB

12

SB

13

SB

14

SB

15


SB

0

SB

1

SB

2

SB

3

SB

4

SB

5

SB

6

SB

7

SB

8

SB

9

SB

10

SB

11

SB

12

SB

13

SB

14

SB

15



VNX Data Mover

10.0.0.100

NFS/CIFS

NFS/CIFS Server

VNX-000022

VNX Data Mover

Site A Site B

10.0.0.200

NFS/CIFS

NFS/CIFS Server

Figure 7. NFS/CIFS server dual site deployment

NFS/CIFS hostname resolution for dual site Disaster Recovery deployment

To recall archived data from an NFS/CIFS server on a local site, add IP address entriesto the local hosts file on each (physical) Data Mover that is hosting a primary file system,or a replica of one. This directs the Data Mover to use the NFS/CIFS server at its localsite.

Add a line for the NFS/CIFS server to each local hosts file on the multiple sites.

For example, the Site A hosts file might contain the following:

# <IP address> <hostname>10.0.0.100 secstore # NFS/CIFS server 1 at Site A

Also, the Site B hosts file might contain the following:


Concepts

# <IP address> <hostname>10.0.0.200 secstore # NFS/CIFS server 1 at Site B


You do not need to make any changes to name resolution on a VNX file system failover.If the local secondary NFS/CIFS server fails, the Data Mover will not use the server atthe remote site.

If you want to use the NFS/CIFS server at the remote site for failover, you can eithermodify the Data Mover hosts file at failure time to include the IP address of the NFS/CIFSserver at the remote site, or you can add the IP address of the NFS/CIFS server at theremote site to each Data Mover's local hosts file ahead of time so that the Data Moverwill use it automatically if it cannot contact the local NFS/CIFS server.

NFS/CIFS hostname resolution with cross-site traffic on secondary failure

To recall archived data from either NFS/CIFS servers on a local site or NFS/CIFS serverson a remote site if the local NFS/CIFS servers are unavailable, add entries to the localhosts file on each (physical) Data Mover that is hosting a primary file system, or a replicaof one. This directs the Data Mover to use the NFS/CIFS servers at the local site first, andonly use those at the remote site if the local ones are unavailable.

If it is available, use the "delayed stubbing" functionality of the policy and archivingapplication to ensure that archived data is replicated to the remote site before any stubfile references it.

Configuring the local hosts files ahead of time means that you do not need to make anychanges to name resolution on a VNX file system failover.

For example, the Site A Data Mover local hosts file might contain the following whenconfigured to use the NFS/CIFS at the remote site if the local one is unavailable:

# <IP address> <hostname>10.0.0.100 secstore # NFS/CIFS server 1 at Site A10.0.0.200 secstore # NFS/CIFS server 1 at Site B

Also, the Site B Data Mover local hosts file might contain the following when configuredto use the NFS/CIFS at the remote site if the local one is unavailable:

# <IP address> <hostname>10.0.0.200 secstore # NFS/CIFS server 1 at Site B10.0.0.100 secstore # NFS/CIFS server 1 at Site A


DNS hostname resolution for dual site Disaster Recovery deployments

If you set up multiple IP addresses with a single hostname in DNS, most DNS serverswill return all of the addresses, but rotate the order of them each time it is queried. Thismeans you cannot predict which secondary server a Data Mover will recall data from.


Concepts

For this reason, EMC recommends using local hosts files on Data Movers for FileMoversecondary server hostname resolution rather than DNS.

Do not put the IP addresses for secondary servers on both sites into DNS. Only IPaddresses for the secondary servers at the production site should be associated with thesecondary server hostname in DNS:

◆ Any recall activity at the Disaster Recovery site will recall from the secondary serversat the production site (across the WAN).

◆ On a VNX file system or secondary server failover, you must update the DNS entryfor the secondary servers to reference the IP addresses of the secondary servers at theDisaster Recovery site.

◆ You must flush the DNS cache on the Data Mover if the DNS entry for the secondaryserver hostname has a Time to Live (TTL) of more than a few minutes.

Planning application integration

The applications used to ensure a successful integration with VNX FileMover are:

◆ Quotas on page 38◆ AntiVirus scan on page 39◆ SnapSure on page 40◆ Replicator, TimeFinder/FS, TimeFinder NearCopy, and FarCopy on page 40◆ Virtual Data Mover on page 41◆ International character sets on page 41◆ FS link on page 42◆ Nested mount file system on page 42◆ File-level retention on page 42◆ CDMS on page 42

Quotas

When you set file system quotas on a VNX system, those quotas monitor and control theusage of only the primary file systems on that VNX system. The quotas on the VNXsystem do not monitor or control the usage of the secondary storage file systems. Thus,quotas set on the VNX system do not affect or reflect usage on the secondary storagesystems.

The VNX system can track quotas by using either of two quota policies: blocks or filesize.By default, the quota policy is set to blocks. When configured to use the blocks quotapolicy, the VNX system calculates disk usage by counting the number of file systemblocks each file occupies on disk. For example, a 1 KB file counts as 8 KB in the quotabecause the file consumes one 8 KB block on disk. As the content of files archives to


Concepts

secondary storage, the VNX system quota usage decreases because the number of blocksoccupied in the primary file system on the VNX is reduced. Likewise, VNX quota usageincreases as files are recalled from secondary storage and begin to occupy blocks in theprimary file system on the VNX system again.

If quota policy is set to filesize, disk usage is calculated in logical file size, which meansa 1 KB file counts as 1 KB in the quota. When using the filesize quota policy, VNX quotausage is unaffected by file archiving and recall operations because these operations donot impact the logical size of files. In this case, the reported size on disk of each file isapproximately the same as the reported logical size of the file.

When calculating the storage required in the primary file system on theVNX systemremember that each archived file consumes one inode, regardless of the quota policysetting. Each archived file will also consume one 8 KB data block in the primary filesystem.

In addition, the VNX system will allocate an additional inode in the primary file systemwhile it converts an unarchived file in the primary file system into a stub file, and whileit recalls the content of an archived file from secondary storage to the primary file system.These temporary inodes count toward any inode-based quotas in use. EMC stronglyrecommends that you avoid letting the system reach hard inode quota limits to avoiddisrupting FileMover-related activity.

The server_df command always displays the inodes and blocks in use in the primaryfile system on the VNX system.

Using Quotas on VNX provides additional information about setting quotas.

Note: If the file system is out of space, is mounted read-only, or a quota limit is encountered, theread recall policy specified in the stub file or connection database is overridden and the passthroughread method is used. In this case, any files partially recalled to the primary file system will continueto occupy space in the primary file system until they are cleaned up by the policy and archivingapplication. The presence of such partially recalled files does not affect access to the data.

AntiVirus scan

Using the AntiVirus Agent (CAVA), the write operation proceeds as usual. Regardingscan-on-read operation, the scan operation does not cause data to be recalled; data isread by using the passthrough archiving method from the AntiVirus (AV) server.

Using CAVA, -fsscan options scan all the files on the file system. By default, stub filesare skipped. Using the -fsscan -create offline option, stub files are scanned. The scanoperation does not cause data to be recalled; data is read by using the passthrough optionfrom the secondary storage.

For network drive scan from the AV server without CAVA, the read operation does notfall back to the passthrough method as it does with CAVA. Instead, it follows the readpolicy setting in the VNX FileMover configuration. In addition, AV applications mightscan stub files depending on whether they recognize the Server Message Block (SMB)offline file attribute set on all archived files by default.

Planning application integration 39

Concepts

The -offline_attr off option of the fs_dhsm command might change the behavior of theAV server as it disables the offline bit in the SMB protocol file attribute.

EMC recommends the use of CAVA for AV scanning of VNX file systems rather thannetwork drive scanning. Contact your AV software vendor for information about howthe AV application handles stub files.

Note: For safety when performing a full file system scan by using an external AV server, set the-read_policy_override command to the passthrough option while files are being scanned. Scanapplications on page 73 contains procedural information.

SnapSure

You can create a checkpoint of a VNX FileMover-enabled file system. The FileMoverconfiguration and connections for the checkpoint are inherited from the production filesystem and cannot be changed. Because a checkpoint is read-only, any attempt to accessa stub file contained within the checkpoint causes the file data to be read from secondarystorage by using the passthrough option. The file content is not recalled from secondarystorage in response to the client request.

VNX FileMover configuration information is stored in a VNX FileMover file system.Restoring from a checkpoint restores the configuration prior to any subsequentmodification occurring after the checkpoint.

For writable checkpoints, FileMover works as described above, except that the DataMover always uses the passthrough option to read data from secondary storage. Toarchive files out of a writable checkpoint, you must first configure FileMover on theproduction file system, create the baseline read-only checkpoint, and then create thewritable checkpoint.

If stub files are restored from a SnapSure checkpoint with an mtime different from themtime of the original file, depending on the policy and archiving application in use,the data might be unavailable on the primary file system. This caution also applies totape backup, a BCV for either TimeFinder/FS or TimeFinder/FS NearCopy (which usesSRDF/S), or an STD volume for TimeFinder/FS FarCopy (which uses SRDF adaptivecopy write pending mode). Contact your software vendor to determine whether yourpolicy and archiving application supports multiple file archiving.

Replicator, TimeFinder/FS, TimeFinder NearCopy, and FarCopy

You can create replicated copies of a VNX FileMover-enabled file system. Because thesecondary file system of Replicator is read-only, any attempt to access a stub file on thesecondary file system causes the file to be read in the passthrough method. The filecontent can be read, but is not recalled from secondary storage in response to the clientrequest.

If you are using CIFS connections on the primary storage, the CIFS server on the secondaryside of Replicator must be in the same domain as the CIFS server on the primary Data


Concepts

Mover. Otherwise, the CIFS connections on the replicated file system do not work, andattempts to access stub files on the replicated file system result in I/O errors.

When you access files on the primary file system of Replicator, the behavior is the sameas in a typical VNX FileMover-enabled file system.

If NFS is used to make a connection to the secondary storage, VNX FileMover uses anyavailable network interface to make the connection because the network interface isdifferent on the secondary side of Replicator.

This behavior applies to a BCV for either TimeFinder/FS or TimeFinder/FS NearCopy(which uses SRDF/S), or an STD volume for TimeFinder FarCopy (which uses SRDFadaptive copy write pending mode).

FileMover configuration is replicated as a part of the file system and users do not needto create FileMover connections on a secondary file system. After setting up FileMoveron the source, the FileMover configuration might not show up on the secondary filesystem until Replicator copies those file system changes. Copying might take severalminutes (or hours) depending on the Replication configuration and environment. Usersneed to configure FileMover API security and user account on the secondary file system.Without configuration, FileMover policy engine will not be able to manage files on thesecondary file system during DR Failover.

Note: In each of the previously mentioned cases, the Data Mover that mounts the copy of theprimary file system must have network connectivity to the secondary storage. Otherwise, it cannotretrieve archived content from secondary storage when clients access stub files in the copy of theprimary file system.

Virtual Data Mover

Virtual Data Mover (VDM) file systems can be used as primary and secondary datastores. However, VNX FileMover API security, managed by using the server_httpcommand, is implemented at the physical Data Mover level. This means that when usingthe server_http command to configure VNX FileMover API security you must specifythe physical Data Mover hosting the VDM as the target of the command, not the VDMitself. It also means if the VDM is moved to another Data Mover, in the same or a differentVNX, you must ensure that you have configured the API security on the new Data Moverappropriately. You can also alter the API security on the Data Mover that the VDM hasmoved from.

International character sets

Unicode must be enabled on the Data Mover that mounts a VNX FileMover-enabled filesystem.

Even if Unicode is enabled, any non-ASCII filename not converted to UTF-8 cannot bearchived by using the policy and archiving application. You must convert the non-ASCIIfilenames before using VNX FileMover. This applies to non-ASCII filenames created

Planning application integration 41

Concepts

from an NFS client with a locale that does not match the VNX encoding informationfrom the client.

The primary VNX system, secondary file server, and policy and archiving applicationall must use the same locale.

Note: Contact your software vendor directly or read your policy and archiving applicationdocumentation for information about international character sets.

FS link

VNX FileMover must be enabled at each file system level. Each file system must have aconnection to secondary storage.

Nested mount file system

VNX FileMover cannot be enabled on the nested mount root file system.

If you are using nested mount file systems (NMFS) to access stub files, you must enableVNX FileMover and create connections on all the individual component file systemscontaining stub files.

File-level retention

You cannot use an FLR file system as the primary storage in a FileMover environment.However, it is possible to use an FLR file system as a secondary storage. Contact yoursoftware vendor to determine whether your policy and archiving application supportsthis configuration.

Note that a file in the FLR state on secondary storage cannot be altered or deleted byNAS clients or users. An FLR file can be deleted only after its retention date has passed.Using VNX File-Level Retention provides additional information about file-level retentionstorage technology and FLR file system behavior.

CDMS

FileMover cannot be used with VNX File System Migration (also known as CDMS).

You cannot enable the FileMover functionality on an MGFS file system. FileMover cannotbe used to archive data out of a file system while you are using CDMS to archive datainto it. You can enable FileMover on a file system only after you have finished usingCDMS and converted the file system to UxFS.


Concepts

3

Enabling VNX FileMover

You enable VNX FileMover functionality on a mounted file system. Thesesettings remain persistent across remounts unless the file system ismounted read-only. The file system must be enabled on a UxFS file systemthat is mounted read or write.

The topic included is:◆ Enable VNX FileMover on page 44


Enable VNX FileMover

Action

To enable VNX FileMover functionality on a Data Mover, use this command syntax:

$ fs_dhsm -modify <fs_name> -state enabled

where:

<fs_name> = name of the file system on which you want to enable VNX FileMover

Example:

To enable VNX FileMover on file system pri_ufs1, type:

$ fs_dhsm –modify pri_ufs1 –state enabled

Output

pri_ufs1:state = enabledoffline attr = onpopup timeout = 0backup = passthroughread policy override = nonelog file = onmax log size = 10MBDone


Enabling VNX FileMover

4

Creating a CIFS connection

You can create a connection by using the CIFS protocol between thespecified file system and a secondary file system. To create a CIFSconnection, you must specify the username and password that matchesthe username and password stored on the domain controller or in theActive Directory in the CIFS environment. The username and passwordare reused each time a CIFS connection is established.

If you do not explicitly set the fully qualified domain name of the CIFSfile server acting as primary storage for the connection, the Control Stationappends the domain name. You cannot use an IP address to specify thesecondary server in a CIFS connection. EMC strongly recommends thatyou use fully qualified domain names where domain names are required.

A connection ID—or <cid>—is automatically created when a connectionis established. Use the fs_dhsm -list option to display connectioninformation.

If you create a general connection path, do not create a connection for aspecialized storage within the shared connection path. For example, if youhave already created cifs://acme.com/share, you cannot create a connectionwith cifs://acme.com/share/workspace1. You will get a DuplicateEntryerror because this is a duplicate of /share. This restriction is applicable toCIFS, NFS, HTTP, and HTTPS connections.

Note: When creating a CIFS connection, do not use a share that references aDistributed File System (DFS) link.

Topics included are:◆ CIFS connection considerations on page 46◆ Create a CIFS connection on page 46


CIFS connection considerations

Considerations for CIFS connections are:

◆ The user does not have to be a domain administrator but must have backup privilegeson the secondary storage CIFS server to access the archived files on secondary storage.That is, the user must be a member of the local "Backup Operators" group on the secondarystorage CIFS server.

◆ To establish a VNX FileMover connection between Windows domains, specify the targetdomain\name by using -admin option of the fs_dhsm command when creating aconnection to secondary storage. For example, when the secondary file server belongsto xyz.com, include:

-admin 'xyz.com\Administrator'

◆ You can associate up to 1,024 secondary storage connections with a single primary filesystem; storage space can be spread over a number of devices.

◆ You must use single quotes when you include backward slashes in the command line.

Create a CIFS connection

Action

To create a CIFS connection on the file system, use this command syntax:

$ fs_dhsm -connection <fs_name> -create -type cifs -admin [<fqdn>\]<admin_name>

-secondary \\<fqdn>\<share>[\<path>] -local_server <host_name>

where:

<fs_name> = name of the VNX FileMover-enabled file system from which files are archived to secondary storage acces-sible through this connection

<fqdn> = fully qualified domain name of secondary CIFS server

<admin_name> = username used to make the CIFS connection

<share> = fully qualified domain name of the secondary server and its sharename

<path> = (optional) base path within the share on the secondary server under which all archived files reside

<host_name> = computer name or NetBIOS name of the local CIFS file server acting as primary storage on the DataMover

Example:

To create a CIFS connection from ufs1 to wichita.nasdocs.emc.com\dhsm2, type:

$ fs_dhsm -connection ufs1 -create -type cifs -admin 'nasdocs.emc.com\Administrator'-secondary '\\wichita.nasdocs.emc.com\dhsm2' -local_server dm112-cge0



Output

Enter Password:*******ufs1:state = enabledoffline attr = onpopup timeout = 0backup = passthroughread policy override = nonelog file = onmax log size = 10MBcid = 1type = CIFSsource = \\wichita.nasdocs.emc.com\dhsm2\state = enabledread policy override = nonewrite policy = fulllocal_server = DM112-CGE0.NASDOCS.EMC.COMadmin = nasdocs.emc.com\Administratorwins =

Done

Create a CIFS connection 47


5

Creating an NFSconnection

You can create a connection by using the NFS protocol between thespecified file system and a secondary file system. The secondary file systemstores the archived files. EMC recommends that you use the -useRootCredoption to specify the user credentials the Data Mover uses when requestingdata from the secondary VNX. When set to true, the Data Mover requestsdata as the root user (UID 0); the secondary storage NFS server must grantthe Data Mover root privilege for NFS traffic. When set to false (default),the Data Mover requests data as the owner of the file as specified in thestub file.

Although you can specify an IP address for <host>, EMC recommends thatyou use the hostname of the server.

Contact your policy and archiving application vendor for the mostup-to-date information about NFS connections to a secondary server.



The topic included is:◆ Create an NFS connection on page 50


Create an NFS connection

Action

To create an NFS connection on the file system, use this command syntax:

$ fs_dhsm -connection <fs_name> -create -type {nfsv3|nfsv2} -secondary<nfs_server>:/<path> -useRootCred true

where:


<nfs_server> = name or IP address of the NFS server

<path> = location of the remote file system

Example:

To create an NFSv3 connection for ufs1 to nasdocs.emc.com:/dest with -useRootCred set to true, type:

$ fs_dhsm –connection ufs1 –create -type nfsv3 -secondary nasdocs.emc.com:/dest-useRootCred true

Output

source:state = enabledoffline attr = onpopup timeout = 0backup = passthroughread policy override = nonelog file = onmax log size = 10MBcid = 0type = NFSV3source = nasdocs.emc.com:/deststate = enabledread policy override = nonewrite policy = fulloptions = useRootCred=true

Done


Creating an NFS connection

6

Creating an HTTP or HTTPSconnection

A FileMover HTTP or HTTPS connection is a virtual circuit between twoendpoints: a VNX file system and a portion of the namespace publishedby an HTTP or HTTPS server. You can create an HTTP or HTTPSconnection between a primary and secondary file system to access archivedfiles on secondary storage. An HTTP or HTTPS connection allows you tointegrate the VNX with an HTTP or HTTPS server.



Topics included are:◆ HTTP and HTTPS connection considerations on page 52◆ Create a non-CGI HTTP or HTTPS connection on page 52◆ Create a CGI HTTP or HTTPS connection on page 53◆ Switch between HTTP and HTTPS connections on page 54


HTTP and HTTPS connection considerations

Considerations for HTTP and HTTPS connections are:

◆ Although you can specify an IP address for <host>, EMC strongly suggests that you usethe hostname of the server, which allows you to take advantage of DNS failover capability.

◆ For non-CGI connections, FileMover assumes that the HTTP server has direct access tosecondary storage content. In this case, providing a URL path in the -secondary optionis optional.

◆ If you attempt to create multiple connections that have identical endpoints with differentattributes, such as -cgi, -user, -password, -localPort, and -httpPort, the connection willfail.

Create a non-CGI HTTP or HTTPS connection

Action

To create a non-CGI HTTP or HTTPS connection, use this command syntax:

$ fs_dhsm -connection <fs_name> -create -type {http|https} -secondary<protocol>://<host>/<url_path> -cgi n

where:


<protocol> = HTTP or HTTPS depending on the value specified for type

<host> = name of the server running the secondary storage HTTP or HTTPS server

<url_path> = location of the application used to access secondary storage

Example:

To create a non-CGI HTTP connection from pri_ufs1 to http://nasdocs.emc.com/dir1, type:

$ fs_dhsm –connection pri_ufs1 –create -type http -secondaryhttp://nasdocs.emc.com/dir1 -cgi n


Creating an HTTP or HTTPS connection

Output

pri_ufs1:state = enabledoffline attr = onpopup timeout = 0backup = passthroughread policy override = nonelog file = onmax log size = 10MBcid = 0type = HTTPsecondary = http://nasdocs.emc.com/dir1state = enabledread policy override = nonewrite policy = fulluser =options = timeout=30 cgi=n

Done

Create a CGI HTTP or HTTPS connection

Action

To create a CGI HTTP or HTTPS connection, use this command syntax:

$ fs_dhsm -connection <fs_name> -create -type {http|https} -secondary<protocol>://<host>/<url_path> -cgi y

where:


<protocol> = HTTP or HTTPS depending on the value specified for type

<host> = name of the server running the secondary storage HTTP or HTTPS server

<url_path> = location of the application used to access secondary storage

Example:

To create a CGI HTTPS connection from pri_ufs1 to https://nasdocs.emc.com/bin/access.sh, type:

$ fs_dhsm –connection pri_ufs1 -create -type https -secondaryhttps://nasdocs.emc.com/bin/access.sh -cgi y

Create a CGI HTTP or HTTPS connection 53


Output

pri_ufs1:state = enabledoffline attr = onpopup timeout = 0backup = passthroughread policy override = nonelog file = onmax log size = 10MBcid = 0type = HTTPSsecondary = https://nasdocs.emc.com/bin/access.shstate = enabledread policy override = nonewrite policy = fulluser =options = timeout=30 cgi=y

Done

Switch between HTTP and HTTPS connections

Perform the following tasks to switch between HTTP and HTTPS connections.

1. Delete the HTTP connection.

2. Configure the secondary server to support HTTPS.

3. Create the HTTPS connection.

4. Roll back to HTTP from HTTPS connections.



7


FileMover API security administration is done on the Control Station orVNX Management API.

Optionally, the HTTP or HTTPS protocol can use digest or basicauthentication to permit only specified users access to the VNX FileMoverAPI.

The HTTP or HTTPS server release 5.6 supports IPv6. The server_httpcommand allows configuring a list of IPv6 nodes and netmasks.

Policy and archiving application must be run on a separate external server,not the VNX .

The tasks to configure security options to modify the HTTP and HTTPSserver on the Data Mover to restrict access to the VNX FileMover APIservice based on different authentication methods and the IP address are:◆ Configuring certificate authentication on page 56◆ Configuring digest or basic authentication on page 60◆ Listing HTTP connection information on page 61


Configuring certificate authentication

SSL provides encryption and authentication. It encrypts data over the network and providesmessage and server authentication. SSL uses digital certificates, whose authenticity is verifiedby a certificate authority. SSL can be combined with basic and digest authentication.

Note: The tasks Stop the existing FileMover HTTP service on page 57, Configure HTTPS on page 58,Start the FileMover HTTPS service on page 58, and Verify certificate availability on page 59 areperformed only when an HTTPS connection is required.

Perform the following tasks to configure certificate authentication.

1. Configure access based on IP address on page 56.

2. Stop the existing FileMover HTTP service on page 57.

3. Configure HTTPS on page 58.

4. Start the FileMover HTTPS service on page 58.

5. Verify certificate availability on page 59.

Configure access based on IP address

Action

To configure access based on the IP address of the policy and archiving application server, use this command syntax:

$ server_http <movername> -append dhsm -hosts <ipaddress>

where:

<movername> = name of the specified Data Mover

<ipaddress> = IP address of the policy and archiving application host

Example:

To allow the policy and archiving application running on a host with IP address 172.24.102.236 to access the VNX FileMoverAPI on server_2, type:

$ server_http server_2 -append dhsm -hosts 172.24.102.236

Output

server_2: done



Stop the existing FileMover HTTP service

The tasks to generate, sign, and import certificates are:

◆ Generate a certificate on page 57◆ Sign a certificate on page 57◆ Import a certificate on page 58

Generate a certificate

Action

To generate a certificate, use this command syntax:

$ server_certificate <movername> -persona -generate -key_size <bits>

-cs_sign_duration <no of months> -common_name <common_name>

where:


<bits> = key size, which can be either 2048 or 4096 bits

<no of months> = specifies the number of months the certificate is valid

<common_name> = hostname that describes the Data Mover with which the persona is associated

Example:

To generate a key set and certificate request that is automatically received by the Control Station for the persona identifiedby the persona name default, type:

$ server_certificate server_2 -persona -generate default -key_size 2048-cs_sign_duration 12 -comon_name division.xyz.com

Output

server_2 :Starting key generation. This could take a long time ...done

Sign a certificate

The steps for signing the default certificate depend on your certificate authority. A localcertificate authority can be used because Windows and Linux hosts are capable of servingas certificate authorities. A commercial certificate authority can also be used.

Configuring certificate authentication 57


Import a certificate

Action

To import a certificate, use this command syntax:

$ server_certificate <movername> -persona -import default

where:


Example:

To import a signed certificate and paste the certificate text, type:

$ server_certificate server_2 -persona -import default

Output

server_2: Please paste certificate data. Enter a carriagereturn and on the new line type ‘end of file’ or ‘eof’ followedby another carriage return.

Configure HTTPS

Action

To configure an HTTPS server, use this command syntax:

$ server_http <movername> -modify dhsm -ssl required

where:


Example:

To configure HTTPS on server_2, type:

$ server_http server_2 -modify dhsm -ssl required

Output

server_2: done

Start the FileMover HTTPS service

By default, this procedure will start the DHSM API service on port 5080. Without thiscommand, the DHSM API service will not run and the customer cannot use the DHSM API.



Action

To start a FileMover HTTPS server, use this command syntax:

$ server_http <movername> -service dhsm -start

where:


Example:

To start FileMover HTTPS on server_2, type:

$ server_http server_2 -modify dhsm -start

Output

server_2 :DHSM FACILITY CONFIGURATIONService name : EMC File Mover serviceComment : Service facility for getting DHSM attributesActive : True

Verify certificate availability

Action

To verify the certificate, use this command syntax:

$ server_certificate <movername> -persona -list

where:


Example:

To check the certificate, type:

$ server_certificate server_2 -persona -list

Output

server_2 : id=1name=defaultnext state=Not AvailableCURRENT CERTIFICATE:id=1subject=O=acme;CN=io2expire=20081003212234Zissuer=C=US;ST=NJ;L=SouthPlainfield;O=NAS;CN=io;emailAddress=DHSM_Partne

Configuring certificate authentication 59


Configuring digest or basic authentication

If digest or basic authentication is required, the policy and archiving application must usea username and password to issue VNX FileMover API requests to the Data Mover HTTPserver. Basic authentication transmits the password in clear text where as digest transmitsin encrypted text. Because the Data Mover HTTP server supports SSL, basic authenticationcan be combined with SSL for a secure transport.

The tasks to manage a user account are:

◆ Create a VNX FileMover user account on page 60◆ Configure digest or basic access authentication on page 61

Create a VNX FileMover user account

Use the server_user command as root on the VNX Control Station to create a user accounton the Data Mover that hosts the VNX FileMover-enabled file system. You can create asmany user accounts as you need. VNX FileMover user accounts require that you use the-md5 option for password encryption.

The username and password are important for the policy and archiving application. EMCrecommends that you avoid using a user or group identifier (UID or GID) that might be inuse. Configuring VNX User Mapping contains additional information about user and groupidentifiers.

Action

To create a VNX FileMover user account to support VNX FileMover access, use this command syntax:

# /nas/sbin/server_user <movername> -add -md5 -passwd <name>

where:


<name> = name of VNX FileMover user account

Example:

To create a new user for md5 on server_3, type:

# /nas/sbin/server_user server_3 -add -md5 -passwd user1

Output

Creating new user user1User ID: 1000Group ID: 1000Home Directory:Changing password for user user1New password:Retype new passwd:



Configure digest or basic access authentication

The HTTP server can also be configured to permit only specified users to access the VNXFileMover API. Upon completion, every attempt to access the FileMover API is challengedand requires digest authentication to proceed.

If the valid users are defined, all users in the Data Mover's local password file can authenticatefor access to the VNX FileMover API. Use a comma-separated list to specify multiple users.If users are not set, digest authentication is not required and all users have access.

Action

To specify users allowed to digest authenticate to the HTTP server, use this command syntax:

$ server_http <movername> -modify dhsm -authentication digest -users {valid}-hosts <ipaddress>

where:


<ipaddress> = IP address of the secondary storage host

Example:

To configure server_2 to allow all users to digest authenticate from 172.24.102.236, type:

$ server_http server_2 -modify dhsm -authentication digest -users valid -hosts172.24.102.236

Output

server_2: done

Listing HTTP connection information

Action

To display HTTP connection information, use this command syntax:

$ server_http <movername> -info dhsm

where:


Example:

To display connection information for server_2, type:

$ server_http server_2 -info dhsm

Configuring digest or basic authentication 61


Output

server_2 : doneDHSM FACILITY CONFIGURATIONService name : EMC File Mover serviceComment : Service facility for getting DHSM attributesActive : FalsePort : 5080Threads : 40Max requests : 300Timeout : 60 secondsACCESS CONTROLAllowed IPs : anyAuthentication : digest ,Realm : DHSM_AuthorizationAllowed user : nobody

SSL CONFIGURATIONMode : OFFPersona : defaultProtocol : defaultCipher : default

Note

The default output is <no user authentication>.



8

Managing

The tasks to manage CIFS, NFS, HTTP, and HTTPS connections are:◆ Modify a connection on page 64◆ List VNX FileMover connections on page 65◆ List connection information on page 65◆ Delete a VNX FileMover connection on page 66


Modify a connection

When you modify a CIFS, NFS, HTTP, or HTTPS connection, the change is effectiveimmediately. Although you might experience a slight delay, there is no impact on the client.

Although the http_server option can be used to modify the hostname of the secondarystorage, files once converted into a stub by using an HTTPS connection can only be broughtback online through HTTPS. It is not possible to recall the data through NFS, CIFS, or evenHTTP.

Action

To modify the connection attributes on the file system, use this command syntax:

$ fs_dhsm -connection <fs_name> -modify <cid> -read_policy_override partial

where:

<fs_name> = name of the file system

<cid> = connection ID

Example:

To modify the read policy override setting for connection 0 for the file system ufs1, type:

$ fs_dhsm -connection ufs1 -modify 0 -read_policy_override partial

Output

ufs1:state = enabledoffline attr = onpopup timeout = 0backup = passthroughread policy override = nonelog file = onmax log size = 10MBcid = 0type = CIFSsecondary = \\wichita.nasdocs.emc.com\dhsm1\state = enabledread policy override = partialwrite policy = fulllocal_server = DM112-CGE0.NASDOCS.EMC.COMadmin = nasdocs.emc.com\Administratorwins = 172.24.102.25

cid = 1type = CIFSsecondary = \\wichita.nasdocs.emc.com\dhsm2\state = enabledread policy override = fullwrite policy = fulllocal_server = DM112-CGE0.NASDOCS.EMC.COMadmin = nasdocs.emc.com\Administratorwins = 172.24.102.26

Done


Managing

List VNX FileMover connections

Action

To list one or all of the VNX FileMover-enabled connections on the file system, use this command syntax:

$ fs_dhsm -connection <fs_name> -list

where:

<fs_name> = name of the FileMover-enabled file system

Example:

To list VNX FileMover connections for ufs1, type:

$ fs_dhsm -connection ufs1 -list

Output

id name cid22 ufs1 022 ufs1 1

Note

Column definitions:

id — file system ID

name — name of the file system

cid — connection ID

List connection information

Action

To list all the information about a given connection, use this command syntax:

$ fs_dhsm -connection <fs_name> -info

where:


Example:

To list ufs1 connection information, type:

$ fs_dhsm -connection ufs1 -info

List VNX FileMover connections 65

Managing

Output

ufs1:state = enabledoffline attr = onpopup timeout = 0backup = passthroughread policy override = nonelog file = onmax log size = 1MBcid = 0type = CIFSsource = \\wichita.nasdocs.emc.com\dhsm1\state = enabledread policy override = nonewrite policy = fulllocal_server = DM112-CGE0.NASDOCS.EMC.COMadmin = nasdocs.emc.com\Administratorwins = 172.24.102.25

cid = 1type = NFSV3source = nasdocs.emc.com:/home/dhsm2state = enabledread policy override = nonewrite policy = fulloptions =

Delete a VNX FileMover connection

When you delete an NFS, CIFS, HTTP, or HTTPS connection, use the -recall_policy optionto specify whether the VNX should recall all archived files relying on the connection toprimary storage before deleting the connection. The -recall_policy option default is yes.The file system checks for stub files and causes the delete operation to fail at the first stubfile found. Set the -recall_policy option to no only when you are certain the stub files are nolonger needed to recall file data. When the FileMover connection no longer exists, a readrequest to the stub file causes an I/O error to appear. To regain access to archived file data,reestablish the FileMover connection by using exactly the same secondary path initiallyspecified.

Action

To delete a VNX FileMover connection from the file system, use this command syntax:

$ fs_dhsm -connection <fs_name> -delete <cid> -recall_policy {yes}

where:



Example:

To delete the VNX FileMover connection from ufs1 and recall the files back to the VNX, type:

$ fs_dhsm –connection usf1 –delete 1 –recall_policy yes


Managing

Action

If the -recall_policy option is set to yes:

◆ Archived files are recalled to the VNX before the connection is removed.

◆ The delete operation can take some time to complete depending on the size of the file system. During this time, youcan continue to access all the files regardless of whether the file is archived.

Output

ufs1:state = enabledoffline attr = onpopup timeout = 10backup = offlineread policy override = fulllog file = onmax log size = 10MB

cid = 0type = CIFSsource = \\wichita.nasdocs.emc.com\dhsm1\state = recallonlyread policy override = nonewrite policy = fulllocal_server = DM112-CGE0.NASDOCS.EMC.COMadmin = nasdocs.emc.com\Administratorwins = 172.24.102.25

cid = 1type = NFSV3source = emcdocs.emc.com:/home/dhsm2state = enabledread policy override = nonewrite policy = fulloptions =

Done

Delete a VNX FileMover connection 67

Managing


Managing

9

Administering

The tasks to perform administrative actions on VNX FileMover-enabledCIFS, HTTP, HTTPS, and NFS file systems are:◆ Change a CIFS password on page 70◆ Disable VNX FileMover log on page 71◆ Increase log file size on page 73◆ Scan applications on page 73◆ Perform an NDMP backup on page 74◆ Perform a CIFS network backup on page 75◆ Perform an NFS network backup on page 76◆ Enable pop-up notification (CIFS only) on page 77◆ Adjust offline attribute settings on page 78◆ Tune HTTP threads on page 79◆ Tune threads to read data from secondary storage on page 80◆ Move VNX FileMover stub files on page 81◆ Disable FileMover functionality on page 81


Change a CIFS password

To ensure security, your organization might require you to change user passwords on aregular basis. The administrator password on the VNX FileMover connection must matchthe administrator password in the CIFS environment. Be aware that the username andpassword for a CIFS connection are different from the username and password used tomanage VNX FileMover API security.

Perform the following steps:

1. List all VNX FileMover-enabled file systems by using this command syntax:

$ fs_dhsm -connection <fs_name> -list

2. List connection information for each VNX FileMover-enabled file system to confirm thesessions for VNX FileMover by using this command syntax:

$ fs_dhsm -connection <fs_name> -info

This action queries whether a session exists. If one does not, a session is established. CIFSsessions are triggered under the following conditions:

• Stub files have been accessed.• A new connection was created.• The fs_dhsm command was used to list connection information.

However, if a session does exist, the actions listed do not trigger a connection. The DataMover always keeps the session until the connection is disconnected, CIFS stops, or thefile system is unmounted.

3. Disable the VNX FileMover connection by using this command syntax:

$ fs_dhsm -connection <fs_name> -modify {-all|<cid>[,<cid>...]} -statedisabled

where:



Example:

To disable all VNX FileMover connections on ufs1, type:

$ fs_dhsm -connection ufs1 -modify -all -state disabled

To disable VNX FileMover connections 1 and 3 on ufs1, type:

$ fs_dhsm -connection ufs1 -modify 1,3 -state disabled

4. Change the user password on the Windows server or domain controller.

5. Change the CIFS administrator password on a VNX FileMover connection by using thiscommand syntax:


Administering

$ fs_dhsm -connection <fs_name> -modify {-all|<cid>[,<cid>...]} –password<password>

where:



<password> = the specified administrator password

Note: If the -password option is given but a password is not specified, the user is promptedinteractively.

Example:

To change the administrator password on all VNX FileMover connections on ufs1, type:

$ fs_dhsm –connection ufs1 –modify -all –password

Enter Password: ******

To change the administrator password for VNX FileMover connection IDs 1 and 3 onufs1, type:

$ fs_dhsm -connection ufs1 -modify 1,3 -password

Enter Password: ******

6. Enable the disabled FileMover connection by using this command syntax:

$ fs_dhsm -connection <fs_name> -modify {-all|<cid>[,<cid>...]} -stateenabled

where:



Example:

To enable all VNX FileMover connections on ufs1, type:

$ fs_dhsm -connection ufs1 -modify -all -state enabled

To enable VNX FileMover connections 1 and 3 on ufs1, type:

$ fs_dhsm -connection ufs1 -modify 1,3 -state enabled

Disable VNX FileMover log

By default, the VNX logs all stub file activity, which includes all events associated withcreating, modifying, and deleting stub files. The default log filename is dhsm.log; it residesin the /.etc directory on the VNX FileMover-enabled file system and is accessible by thepolicy and archiving application. Appendix A contains additional information about VNXFileMover log files. Stub file event activity is written to read or write file systems only; there

Disable VNX FileMover log 71

Administering

is no logging of stub file events on read-only file systems. You cannot modify loggingparameters on a read-only file system.

When logging events exceed the size of the log file, a new log file is created. A maximumof five log files are kept at any given time; the oldest log file is replaced in sequential order.If the primary file system is running low on space, you can delete the old dhsm.log files inthe /.etc directory to free the space they occupy. EMC recommends you disable logging onthe primary file system before removing any dhsm_log.* files.

When you are working with VNX FileMover log files in the /.etc directory of the primaryfile system, be careful not to touch any other files in the same directory.

Action

To disable VNX FileMover logging, use this command syntax:

$ fs_dhsm -modify <fs_name> -log off

where:


Example:

To disable VNX FileMover logging, type:

$ fs_dhsm -modify ufs1 -log off

Output

ufs1:state = enabledoffline attr = onpopup timeout = 0backup = passthroughread policy override = nonelog file = offmax log size = 10MBcid = 0type = CIFSsource = \\wichita.nasdocs.emc.com\dhsm1\state = enabledread policy override = nonewrite policy = fulllocal_server = DM112_CGE0.NASDOCS.EMC.COMadmin = nasdocs.emc.com\Administratorwins = 172.24.102.25

Done


Administering

Increase log file size

The default VNX FileMover log file size is 10 MB; this is also the minimum log size. Althoughyou cannot decrease the size below the minimum, you can increase the log file size.

Action

To increase the log file size, use this command syntax:

$ fs_dhsm -modify <fs_name> -max_log_size <mb>

where:


<mb> = log file size in megabytes

Example:

To increase the log file size to 20 MB on ufs1, type:

$ fs_dhsm -modify ufs1 -max_log_size 20

Output

ufs1:state = enabledoffline attr = onpopup timeout = 0backup = passthroughread policy override = nonelog file = onmax log size = 20MBcid = 0type = CIFSsource = \\wichita.nasdocs.emc.com\dhsm1\state = enabledread policy override = nonewrite policy = fulllocal_server = DM112_CGE0.NASDOCS.EMC.COMadmin = nasdocs.emc.com\Administratorwins = 172.24.102.25

Scan applications

If you employed an application that uses CIFS or NFS to scan a VNX FileMover-enabledfile system, consider setting the -read_policy_override option to passthrough for the durationof the file system scan to avoid recalling files from secondary to primary storage. Examplesof such applications are NFS backups, antivirus software, and Windows Explorer file contentsearches.

To use the Windows offline folder synchronization feature on a VNX FileMover-enabledfile system, the -read_policy_override option must be set to passthrough for any filessynchronized with users’ machines. If passthrough is not specified, the archived files are

Increase log file size 73

Administering

recalled to the VNX every time a user synchronizes their local machine with the shared filesbecause the operation prompts a read of the archived files.

Note: Zip files might be recalled when Windows Explorer reads them during a file or folder namesearch.

Action

To enable passthrough reads while scanning applications, use this command syntax:

$ fs_dhsm -modify <fs_name> -read_policy_override passthrough

where:


Example:

To enable a passthrough read while scanning file system ufs1, type:

$ fs_dhsm -modify ufs1 -read_policy_override passthrough

Output

ufs1:state = enabledoffline attr = onpopup timeout = 0backup = passthroughread policy override = passthroughlog file = onmax log size = 10MBcid = 0type = CIFSsource = \\wichita.nasdocs.emc.com\dhsm1\state = enabledread policy override = nonewrite policy = fulllocal_server = DM112_CGE0.NASDOCS.EMC.COM

Done

Perform an NDMP backup

By default, NDMP backup operations back up the stub files. The backup option of thefs_dhsm command has no impact on an NDMP backup.

When an NDMP backup is performed with the environment variableEMC_OFFLINE_DATA=n, which is the default configuration, only the primary storagecontent is backed up. When you restore such a file system, the stub files are restored andcontinue to serve as pointers to access the file content on secondary storage. The file contentremains on secondary storage as long as its associated policy dictates. In this case, the contentsof all archived files on the secondary file server must be backed up independently.


Administering

You can also choose to set the NDMP environment variable to read the contents of eacharchived file from secondary storage—without recalling the files to primary storage—andback up the file contents to a tape drive if this is the action you want.

Action

To set the NDMP environment variable on the backup application server, include the following text in the backup job defi-nition:

EMC_OFFLINE_DATA=y

Perform a CIFS network backup

By default, a backup that uses CIFS causes the file content on secondary storage to be readby using passthrough. The files are backed up to the backup application and not recalledto primary storage. The data is read from secondary storage to the backup stream throughthe local area network (LAN).

Set the -backup option to offline to back up stub files and files that have not been archivedfrom primary storage.

This command applies only to CIFS network backup. It does not apply to NDMP, NFS, orserver_archive backups.

Action

To back up only the stub files to the CIFS backup application, use this command syntax:

$ fs_dhsm -modify <fs_name> -backup offline

where:


Example:

To back up stub files on ufs1 by using the offline method, type:

$ fs_dhsm -modify ufs1 -backup offline

Perform a CIFS network backup 75

Administering

Output

ufs1:state = enabledoffline attr = onpopup timeout = 0backup = offlineread policy override = nonelog file = onmax log size = 10MBcid = 0type = CIFSsource = \\wichita.nasdocs.emc.com\dhsm1\state = enabledread policy override = nonewrite policy = fulllocal_server = DM112_CGE0.NASDOCS.EMC.COMadmin = nasdocs.emc.com\Administratorwins = 172.24.102.25

Done

Perform an NFS network backup

Set the -read_policy_override option to passthrough to perform an NFS backup operationthat does not recall archived file content to primary storage.

There is no option to back up only the stub files when you back up through the NFS network.

Action

To perform an NFS backup, use this command syntax:

$ fs_dhsm -modify <fs_name> -read_policy_override passthrough

where:


Example:

To back up all the file data on ufs1 by using passthrough, type:

$ fs_dhsm -modify ufs1 -read_policy_override passthrough


Administering

Output

ufs1:state = enabledoffline attr = onpopup timeout = 0backup = passthroughread policy override = passthroughlog file = onmax log size = 10MBcid = 0type = CIFSsource = \\wichita.nasdocs.emc.com\dhsm1\state = enabledread policy override = nonewrite policy = fulllocal_server = DM112_CGE0.NASDOCS.EMC.COMadmin = nasdocs.emc.com\Administratorwins = 172.24.102.25

Done

Enable pop-up notification (CIFS only)

Use the -popup_timeout option to specify a pop-up time-out value, which permits the VNXto send pop-up notifications to CIFS clients. When a CIFS I/O request cannot be processedwithin the time specified, a notification of the delay appears to the CIFS client in a Windowspop-up message.

The default value for -popup_timeout <sec> is zero, which disables pop-up notification.

Action

To enable pop-up notification, use this command syntax:

$ fs_dhsm -modify <fs_name> -popup_timeout <sec>

where:


<sec> = the pop-up time-out value, in seconds

Example:

To enable pop-up notification on ufs1, type:

$ fs_dhsm -modify ufs1 -popup_timeout 10

Enable pop-up notification (CIFS only) 77

Administering

Output

ufs1:state = enabledoffline attr = onpopup timeout = 10backup = passthroughread policy override = passthroughlog file = onmax log size = 10MBcid = 0type = CIFSsource = \\wichita.nasdocs.emc.com\dhsm1\state = enabledread policy override = nonewrite policy = fulllocal_server = DM112_CGE0.NASDOCS.EMC.COMadmin = nasdocs.emc.com\Administratorwins = 172.24.102.25

Done

Note

The default Windows pop-up notification message is: Accessing offline data, please wait while retrieving data.To customizethis message, change the parameter line in the cifsmsg.txt file to $warning.remote=<the customized message>. UsingQuotas on VNX contains more information about customizing Windows pop-up warning and error messages.

The Windows Messenger service must be running on the CIFS client for it to be able to display Windows pop-up messages.This service does not run by default in Windows Server 2003 or Windows XP.

Adjust offline attribute settings

EMC strongly recommends you accept the default for the -offline_attr option. The defaultenables theVNX to notify CIFS clients that a file is archived. A small marker appears at thebottom-left corner of the file icon when the file appears in Windows Explorer. If the optionis disabled, archived files can be recalled to primary storage unnecessarily as applications,like Windows Explorer, read parts of files even when just viewing the enclosing directory.

Note: CIFS Notify Change is not supported by the VNX FileMover. To obtain up-to-date stub file statusinformation, refresh Windows Explorer as needed.

Action

To disable offline attribute settings, use this command syntax:

$ fs_dhsm -modify <fs_name> -offline_attr off

where:



Administering

Action

Example:

To disable offline attributes on ufs1, type:

$ fs_dhsm -modify ufs1 -offline_attr off

Output

ufs1:state = enabledoffline attr = offpopup timeout = 0backup = offlineoverride = fulllog = onmax log size = 20MBcid = 2type = NFSV3source = emcdocs.emc.com:/dhsm1state = enabledread policy override = nonewrite policy = fulloptions =

Done

Tune HTTP threads

By default, 20 threads are available on the Data Mover to service all HTTP requests; of thatnumber, 15 threads—75 percent of the thread pool—are available for VNX FileMover. Thismeans the Data Mover, unless otherwise configured, can process a maximum of 15simultaneous VNX FileMover API requests from the policy and archiving application. Inmost environments, the default number of threads should be sufficient. If the policy andarchiving application that you are using can simultaneously issue more API requests thanthere are HTTP threads, or you have multiple policy and archiving applications that mightsimultaneously issue VNX FileMover API requests to the Data Mover, consider increasingthis thread count.

You can use the -threads option to specify the number of threads to make available for anexternal policy and archiving application (server) that requires more than the default. Thisvalue takes effect immediately without rebooting the Data Mover.

Action

To specify the number of threads available on a Data Mover, use this command syntax:

$ server_http <movername> -modify dhsm -threads <threads>

where:


<threads> = number of threads, from 4 through 99, for incoming service requests; default is 20

Tune HTTP threads 79

Administering

Action

Example:

To increase the number of threads to 30 on server_2, type:

$ server_http server_2 -modify dhsm -threads 30

Output

server_2 :DHSM FACILITY CONFIGURATIONService name : EMC File Mover serviceComment : Service facility for getting DHSM attributesActive : TruePort : 5080Threads : 30Max requests : 300Timeout : 60 secondsACCESS CONTROLAllowed IPs : 172.24.252.41,45.252.1.40,45.252.1.45,172.24.252.40Authentication : digest ,Realm : DHSM_AuthorizationAllowed user : valid

SSL CONFIGURATIONMode : OFFPersona : defaultProtocol : defaultCipher : default

Note

◆ 25% of the thread pool is reserved for non-VNX FileMover operations, which means a value of 40 provides 30 threadson the Data Mover to service the VNX FileMover API.

◆ The recommended maximum number of threads is 30. If more VNX FileMover API requests are sent to the DataMover than there are HTTP threads to process them, the extra requests are rejected.

Tune threads to read data from secondary storage

The Data Mover usually reads data from secondary storage in response to a client requestto read from or write to the stub files, but also recalls data when a VNX FileMover connectionis deleted by using the -recall_policy yes flag.

By default, for NFS and CIFS, 256 threads run on the 510 Data Mover or later. The numberof simultaneous reads allowed to the stub files is half of the lesser number of CIFS threadsand NFS threads. This means there can be a maximum of 128 simultaneous reads to the stubfiles.

Note: The default number of threads depends on the memory size of the Data Mover. If the memorysize is less than 1 GB, the default is 32 threads.

Several applications can read from stub files: CIFS and NFS clients, NDMP backup, CIFS orNFS network backup, recall operations with VNX FileMover connection deletion, AV servers,


Administering

FTP clients, and so on. If the limit on simultaneous reads is reached, NFS and CIFS clientsmight experience slow response time. CIFS clients might receive an error and need to attemptthe operation again.

To increase the number of CIFS threads, readConfiguring andManaging CIFS on VNX. Contactthe EMC Customer Support Center to increase the number of NFS threads.

Move VNX FileMover stub files

You can copy or move the stub files between VNX file systems. There are two ways to copyor move VNX FileMover stub files from one file system to another without recalling filedata from secondary storage.

The simplest way to copy or move FileMover stub files between VNX file systems is to usea policy engine that supports the copying or moving of stub files. Contact your softwarevendor to determine whether your policy and archiving application supports thisfunctionality.

You can also use EMcopy to copy VNX FileMover stub files between VNX file systems. Inthis case, you need to set the CIFS backup option to offline on the source file system; it isunnecessary to set this option on the destination file system.

Note: EMC strongly recommends that the Data Movers hosting both source and destination file systemsrun software version 5.3.16 or later. The destination file system must exist and be enabled with theFileMover functionality. In addition, the connections to secondary storage must match the connectionsdefined on the source file system.

Disable FileMover functionality

If you disable the FileMover functionality on a VNX file system, any files archived tosecondary storage are inaccessible. Subsequent attempts to read or write to an archived filecause I/O errors.

When specifying the -modify option on a disabled file system, the state is automaticallychanged to enabled. In this instance, to maintain the disabled state specify -state disabled.

Disabling the FileMover functionality on a VNX file system does not delete VNX FileMoverconnections, including the options set on the file system. You can also choose to disable orenable a single FileMover connection.

Action

To disable FileMover functionality on a VNX file system, use this command syntax:

$ fs_dhsm -modify <fs_name> -state disabled

where:


Move VNX FileMover stub files 81

Administering

Action

Example:

To disable ufs1, type:

$ fs_dhsm -modify ufs1 -state disabled

Output

ufs1:state = disabledoffline attr = onpopup timeout = 10backup = offlineread policy override = fulllog file = offmax log size = 20MBDone

Note

You cannot specify any additional options to the modify command when changing the state to disabled. If you do specifyadditional options, the command will be rejected.


Administering

10

Example procedure

The following example procedure shows you how to enable VNXFileMover on the file system, and then create a connection to a secondaryfile server:◆ Example procedure on page 84


Example procedure

1. Create a file system on the VNX.

2. Enable the file system for VNX FileMover by using this command syntax:

$ fs_dhsm -modify <fs_name> -state enabled

Note: Perform this command only once. It remains persistent across Data Mover reboots and mustbe explicitly disabled.

3. Create a connection for either NFS, CIFS, non-CGI HTTP, or CGI HTTPS.

• Create an NFS connection by typing:

$ fs_dhsm -connection dm7fs1 -create -type nfsv3 -secondary

nasdocs.emc.com:/nfsv3_fs

This command creates a VNX FileMover connection on the file system dm7fs1. Thiscommand remains persistent across Data Mover boots. nasdocs.emc.com is thehostname of the secondary NFS file server with an export path of /nfsv3_fs. Be certainthat the NFS file server allows root access from this Data Mover. Use/usr/sbin/showmount -e nasdocs.emc.com to verify the export path.

• Create a CIFS connection by typing:

$ fs_dhsm -connection dm7fs1 -create -type cifs -admin

‘nasdocs.emc.com\Administrator’ -secondary

‘\\wichita.nasdocs.emc.com\test_share’ -local_server DMNJ-2-7

This command creates a second VNX FileMover connection on the file system dm7fs1.This uses a secondary CIFS file server, wichita, which exports the share test_share.You are prompted for a password for the administrator account. This commandremains persistent across Data Mover boots.

• Create a non-CGI HTTP connection by typing:

$ fs_dhsm –connection pri_ufs1 –create -type http -secondary

http://nasdocs.emc.com/dir1 -cgi n

This command creates a VNX FileMover non-CGI HTTP connection on the file systempri_ufs1. This command remains persistent across Data Mover boots. nasdocs.emc.comis the hostname of the secondary HTTP file server with an export path of /dir1.

• Create a CGI HTTPS connection by typing:

$ fs_dhsm –connection pri_ufs1 –create -type https -secondary

https://nasdocs.emc.com/dir1 -cgi y

This command creates a VNX FileMover CGI HTTPS connection on the file systempri_ufs1. This command remains persistent across Data Mover boots. nasdocs.emc.comis the hostname of the secondary HTTPS file server with an export path of /dir1.


Example procedure

4. Configure the HTTP server on the Data Mover to accept VNX FileMover API connectionsfrom the user or host by using this command syntax:

$ server_http <server_x> -append dhsm -users <user_name> -hosts <ip_address_policy_engine>

5. Use your policy and archiving application to archive files from the VNX to secondarystorage and access the file.

Example procedure 85

Example procedure


Example procedure

11

Troubleshooting

As part of an effort to continuously improve and enhance the performanceand capabilities of its product lines, EMC periodically releases new versionsof its hardware and software. Therefore, some functions described in thisdocument may not be supported by all versions of the software orhardware currently in use. For the most up-to-date information on productfeatures, refer to your product release notes.

If a product does not function properly or does not function as describedin this document, contact your EMC Customer Support Representative.

ProblemResolution Roadmap for VNX contains additional information aboutusing EMC Online Support and resolving problems.

Topics included in this chapter are:◆ EMC E-Lab Interoperability Navigator on page 88◆ VNX user customized documentation on page 88◆ Known problems on page 88◆ Error messages on page 89◆ EMC Training and Professional Services on page 90


EMC E-Lab Interoperability Navigator

The EMC E-Lab™ Interoperability Navigator is a searchable, web-based application thatprovides access to EMC interoperability support matrices. It is available on EMC OnlineSupport at http://Support.EMC.com. After logging in, in the right pane under Product andSupport Tools, click E-Lab Navigator.

VNX user customized documentation

EMC provides the ability to create step-by-step planning, installation, and maintenanceinstructions tailored to your environment. To create VNX user customized documentation,go to: https://mydocs.emc.com/VNX.

Known problems

Table 3 on page 88 describes known problems that might occur when using VNX FileMoverand presents workarounds. File attributes are set using the policy and archiving application.

Table 3. Known problems and workarounds

WorkaroundSymptomKnown problem

N/APop-up notifications appear after 10seconds have passed.

If the pop-up time-out value is less than10 seconds, pop-up notifications onCIFS clients do not appear until at least10 seconds have passed.

Use the policy and archiving applicationto rearchive the recalled files and setthe read recall policy to passthrough, ifneeded. EMC is investigating the behav-ior between FileMover and WindowsExplorer.

Files might be recalled to primary stor-age when some Windows clients checkthe property of the stub files.

Viewing the stub file properties by usingsome Windows Server 2003 or Win-dows XP clients might cause a readoperation to occur.

EMC is investigating the behavior be-tween FileMover and Windows Explorer.

Viewing the stub file properties of exe-cutable and Zip files by using Windows2000 might recall all data from sec-ondary storage.

Conversion to UTF-8 must be done be-fore the file is archived.

Filenames not in UTF-8 format that arecreated from wrong locale NFS or CIFSclients cannot be archived by usingFileMover.


Troubleshooting


https://mydocs.emc.com/VNX

Table 3. Known problems and workarounds (continued)

WorkaroundSymptomKnown problem

Try to create the CIFS connectionagain.Warning: RecvStream

failed Protocol notavailable on serverlnsga176 with client170dm2test

fs_dhsm -connection-create -type cifs:failed to completecommand

Search results do not return filesmatching the search criteria.

Windows Explorer search functionalitycannot locate archived files or folderson Windows Server 2003 or WindowsXP.

1. Click Start and then Search ➤ For

Files or Folders.

2. Click All files and folders.

3. In the All or part of the file name

field, type the file name you wantto find.

4. Click Search tape backup.

5. Click Search.

Note: When the Search tape backupoption is enabled, do not search for anarchived file by using a specific word orphrase. Doing so recalls all the files toprimary storage as they are searched.

Error messages

All event, alert, and status messages provide detailed information and recommended actionsto help you troubleshoot the situation.

To view message details, use any of these methods:

◆ Unisphere software:

• Right-click an event, alert, or status message and select to view Event Details, AlertDetails, or Status Details.

◆ CLI:

• Type nas_message -info <MessageID>, where <MessageID> is the messageidentification number.

◆ Celerra Error Messages Guide:

Error messages 89

Troubleshooting

Use this guide to locate information about messages that are in the earlier-releasemessage format.

•

◆ EMC Online Support:

• Use the text from the error message's brief description or the message's ID to searchthe Knowledgebase on EMC Online Support. After logging in to EMC Online Support,locate the applicable Support by Product page, and search for the error message.

EMC Training and Professional Services

EMC Customer Education courses help you learn how EMC storage products work togetherwithin your environment to maximize your entire infrastructure investment. EMC CustomerEducation features online and hands-on training in state-of-the-art labs conveniently locatedthroughout the world. EMC customer training courses are developed and delivered by EMCexperts. Go to EMC Online Support at http://Support.EMC.com for course and registrationinformation.

EMC Professional Services can help you implement your system efficiently. Consultantsevaluate your business, IT processes, and technology, and recommend ways that you canleverage your information for the most benefit. From business plan to implementation, youget the experience and expertise that you need without straining your IT staff or hiring andtraining new personnel. Contact your EMC Customer Support Representative for moreinformation.


Troubleshooting



Appendix A

VNX FileMover log fileexample

By default, the VNX logs all activity associated with creating, modifying,and deleting stub files in a VNX FileMover-enabled file system. Theseevents are logged to a file named dhsm.log in the /.etc directory of the filesystem.

The following example illustrates this:◆ VNX FileMover log file example on page 92


VNX FileMover log file example

You can use a UNIX client to locate stub files mentioned in the server_log output. The stubfile inode is identified as node <inode number> is offline, abort. To locate stub files in theserver_log file, use find /<directory> -inum <inode number> or ls -lRia. Events can be issuedwhen the delete operation is complete. Use facility number 75 and event ID 0. ConfiguringEvents and Notifications on VNX for File contains more information about events.

The example entries from a dhsm.log file are as follows:

1*: debug dhsmlog: initialize dhsm log ... Wed May 12 10:14:09 20042*: SET_OFFLINE: 1.12.b52.40a2408c, pe_id: Enigma Celerra Hostid:795c65be983eee130171bc3fd025e6d1, offline_path:\\cfs6dm2a.w2003.celerra.co.uk\fs4\SMDEST\_SHARE_cfs2dm2a\source1\PROJECT\test.txt ... Wed May 12 17:13:35 20041003*: REMOVE: 1.12.b52.40a2408c, pe_id: Enigma Celerra Hostid:795c65be983eee130171bc3fd025e6d1, offline_path:\\cfs6dm2a.w2003.celerra.co.uk\fs4\SMDEST\_SHARE_cfs2dm2a\source1\PROJECT\test.txt ... Wed May 12 18:25:03 20042707*: GET_ONLINE: 1.12.edf.40a27a69, pe_id: Enigma Celerra Hostid:795c65be983eee130171bc3fd025e6d1, offline_path:\\cfs6dm2a.w2003.celerra.co.uk\fs4\SMDEST\_SHARE_cfs2dm2a\source1\BVT-P10x100\P1\file-1.txt ... Wed May 12 19:50:522004

Table 4 on page 92 describes the entries.

Table 4. VNX FileMover log file example entry

Brief descriptionExample log entry

The event type that occurred:

◆ SET_OFFLINE indicates an archived file was replaced by a stub.

◆ REMOVE indicates a stub file was deleted.

◆ GET_ONLINE indicates the file represented by the stub file onprimary storage was recalled from secondary to primary storage.

SET_OFFLINE

Log event number.1.12.b52.40a2408c

Policy and archiving application that archived the file.pe_id

Number identifier for the policy and archiving application.host id

Location the file was archived to on secondary storage.offline_path

The date or time stamp when this event occurred.Wed May 12 17:13:35 2004


VNX FileMover log file example

Appendix B

Storage space requirementexample

To determine how big the primary and secondary file systems should be,consider the following example:◆ Storage space requirement example on page 94


Storage space requirement example

For the purpose of this storage space requirement example, assume you have a requirementto store 1 TB of data, of which 80 percent of the files are considered stale. The stale files areeligible for archiving to secondary storage in a VNX FileMover-enabled environment. Also,assume the average file size is 110 KB and you want to use primary and secondary storageat approximately 80 percent. To keep things simple, all the archived files will reside in asingle secondary storage location.

With an average file size of 110 KB per file, 1 TB of data represents approximately 9,761,289files. The files eligible for archiving to secondary storage are 7,809,031 (80 percent), whichleaves the same number of stub files plus 1,952,258 unarchived files—the remaining 20percent of the 1 TB total—on primary storage. Each stub file usually occupies 8 KB of spacein the primary file system.

In addition, consider the space needed to keep recalled files on primary storage. The readrecall method can have significant impact. Assume 1 percent of the stale data (78,090 filesx 110 KB) is recalled with read access.

Write operations must also be considered. A write operation causes full recall of the data.When a file is fully recalled by using a write or read operation, the file stays active until itis once again archived by the policy and archiving application. Assume 1 percent stale data(78,090 files x 110 KB) is recalled with write access.

Subsequently, the total space used in the primary file system will be ((20 percent *1 TB) +(7,809,031 - 78,090 - 78,090) * 8 KB + (78,090 x 110 KB) + (78,090 x 110 KB)) = 301 GB (roundedto the nearest GB). With a targeted file system utilization of 80 percent, the primary filesystem needs to be 376 GB in size. The amount of data stored in the secondary file systemis approximately 800 GB, which is 80 percent of the 1 TB that is stale. With the targeted filesystem usage of 80 percent, the secondary file system needs to be 1 TB.

The E-Lab Interoperability Navigator, which is available on EMC Online Support , providesmore information on sizing a VNX FileMover file system.


Storage space requirement example


Appendix C

HTTP connections and DataMover HTTP clients

When a FileMover connection is configured to an HTTP secondary storageserver, the Data Mover creates up to 32 HTTP clients. Each HTTP clientin the Data Mover tries to establish an HTTP connection to the secondaryserver that the FileMover connection refers to by resolving its hostnameto one or more IP addresses.

If a Data Mover HTTP client cannot establish a TCP connection with thefirst IP address associated with the secondary HTTP server, it tries thenext and so on until it succeeds or runs out of IP addresses to try. Planningsecondary hostname resolution on page 30 contains details on how tomanage the order in which secondary servers will be used.

Note: This means that it is possible for a single Data Mover to end up withconnections to multiple secondary HTTP servers if the secondary HTTP serversthat are first in the IP address list cannot support the number of HTTPclients/connections that the Data Mover tried to establish.

As long as at least one HTTP client succeeds in making a connection witha secondary HTTP server, the FileMover connection establishmentsucceeds. If none of the HTTP clients are able to make a connection, theFileMover connection establishment fails.

Once the FileMover HTTP connection is established, where at least oneHTTP client was able to connect to a secondary HTTP server, the connectionmay be idle for some time and the secondary HTTP server is free to dropthe connection.

When the Data Mover needs to recall data, it chooses an idle HTTP clientand, if the connection was dropped, it attempts to reestablish the HTTPconnection.

Note: This may also cause the HTTP client to use a different IP address if it cannotre-establish its connection to the IP address that it was using.


If no HTTP connections can be established in response to NFS and CIFSuser client activity:

◆ NFS clients receive an NFS I/O error◆ CIFS clients receive a CIFS STATUS_INTERNAL_ERROR

Topics included are:◆ VNX FileMover HTTP connection to secondary storage connection

counts on page 97◆ Data Mover HTTP client secondary connection high availability on

page 97◆ Forcing a Data Mover to stop using a secondary HTTP server on page

98


HTTP connections and Data Mover HTTP clients

VNX FileMover HTTP connection to secondary storage connectioncounts

The number of HTTP clients, and therefore HTTP connections, established must be consideredwhen designing solutions with many primary file systems to avoid overwhelming thesecondary storage HTTP servers.

The following four examples describe different scenarios.

Example 1: 1 primary file system with 1 FileMover HTTP secondary connection

A Data Mover runs up to 32 HTTP clients and the one or more secondary storage HTTPservers referenced by the FileMover HTTP secondary connection get up to 32 HTTPconnections.

Example 2: 1 primary file system with 10 HTTP secondary connections that referencedifferent HTTP servers

The secondary storage HTTP servers targeted by the secondary connections each get 32connections for a total of 320 in the environment.

Example 3: 1,000 primary file systems on the same Data Mover, with each primaryfile system having 1 FileMover HTTP secondary connection and all referencing thesame HTTP server hostname

The secondary storage HTTP server hostname targeted by the secondary connections getsa total of 32,000 connections.

If the secondary HTTP server hostname refers to multiple HTTP servers, the connectionsmay be distributed among the HTTP servers depending on the order in which the DataMover gets the IP addresses for the HTTP secondary servers, and whether a secondaryHTTP server is able to handle all of the connection requests it receives. Planning secondaryhostname resolution on page 30 contains details on how to manage the order in whichsecondary servers will be used.

Example 4: 1,000 primary file systems on the same Data Mover, with each primaryfile system having 1 FileMover HTTP secondary connection and all referencing differentHTTP servers

The secondary storage HTTP servers targeted by the secondary connections each get 32connections for a total of 32,000 connections in the environment.

Data Mover HTTP client secondary connection high availability

Data Mover HTTP clients direct all requests to the first resolved secondary server hostnameIP address until that server stops responding to requests. An HTTP server is consideredunavailable if a TCP connection cannot be established within the specified timeout (thedefault is 15 seconds) or if the TCP connection is refused.

If a Data Mover HTTP client cannot establish a connection with a secondary server IP address,the client tries the next IP address it has in the hostname list.

VNX FileMover HTTP connection to secondary storage connection counts 97


The IP address of the failed HTTP server is added back to the list of IP addresses that maybe tried after 60 seconds. This means that the IP addresses are always tried in the order thatthe hostname resolution service returns them. Planning secondary hostname resolution onpage 30 contains details on how to manage the order in which the secondary servers willbe used.

A Data Mover HTTP client does not refresh the list of hostname IP addresses until it hastried all of them (for example, it fails to connect to all of the IP addresses within a single60-second period).

If you are using DNS for hostname resolution and the DNS’s TTL value for the hostnamehas not expired, the Data Mover uses its DNS cache to resolve the hostname rather thanquerying DNS again. You must flush the Data Mover DNS cache to get it to notice changesin DNS prior to the DNS entry TTL expiring. Use the VNX Control Station CLI command"server_dns <mover> -o flush" to flush a Data Mover's DNS cache.

Forcing a Data Mover to stop using a secondary HTTP server

This section explains how you make a Data Mover that is using a secondary HTTP serverstart using a different server.

An HTTP client on a Data Mover may use a different HTTP secondary server if you either:

◆ Shut down the secondary HTTP server.

or

◆ Stop and restart the secondary HTTP server, or block its IP address with a fictitious routeon the Data Mover.

However, these measures will work only if all HTTP clients/connections are exercised duringthe period that the secondary HTTP server is down or blocked. If an HTTP client is idleduring that time and resumes operation when the secondary HTTP server is back online orunblocked, then the HTTP client starts using the server again.

The above scenarios do not take into consideration when a secondary HTTP server is up(because other Data Movers are using it), but is not used by the particular Data Mover inquestion, or the fact that stopping and restarting a server or blocking its IP address cannotguarantee that all HTTP clients/connections are shifted to the correct Data Mover.

To actually force a Data Mover to stop using a secondary HTTP server, you need to deletethe FileMover secondary connection from the primary file system and then re-create it. Youmust ensure that, while deleting the FileMover connection, the stub files that reference thatconnection are not recalled by specifying the "-recall_policy no" when issuing the fs_dhsmcommand to delete the FileMover connection.

Also, be aware that the primary file system remains online during this process. It is onlyaccess to archived files that is disrupted and that can be minimized by scripting the deletionand re-creation of the FileMover secondary connection on the Data Mover.



Glossary

A

AV engineThird-party antivirus software running on a Windows Server that works with the CommonAntiVirus Agent (CAVA).

See also AV server, CAVA, VC client, and virus definition file.

AV serverWindows Server configured with the CAVA and a third-party antivirus engine.

See also AV engine, CAVA, and VC client.

C

Common AntiVirus Agent (CAVA)Application developed by EMC that runs on a Windows Server and communicates with astandard antivirus engine to scan CIFS files stored on VNX for file.

See also AV engine, AV server, and VC client.

Common Gateway Interface (CGI)Standard for interfacing an external application with an information server, such as HTTPS.

Common Internet File System (CIFS)File-sharing protocol based on the Microsoft Server Message Block (SMB). It allows users toshare file systems over the Internet and intranets.

component file systemFile system mounted on the nested mount root file system that is part of the nested mount filesystem.

connection databaseDatabase of secondary storage connection information that includes the server name, share,and credentials, which are stored on the file and maintained across system reboots.


D

Digest Access AuthenticationMeans of verifying that the client and server possess a shared secret (a password).

E

extended ACLContainer used to store extended attributes. In VNX FileMover system, extended ACLs areused to back up and restore stub files through a CIFS network backup.

F

Fail-Safe Network (FSN)High-availability feature that extends link failover out into the network by providing switch-levelredundancy. A FSN appears as a single link with a single MAC address and potentially multipleIP addresses.

File Mapping Protocol (FMP)File system protocol used to exchange file layout information between an application serverand VNX for file.

fully qualified domain name (FQDN)Full name of a system, which contains the domain name of the organization and its highestsubdomain.

H

Hypertext Transfer Protocol (HTTP)Communications protocol used to connect to servers on the World Wide Web.

Hypertext Transfer Protocol Secured (HTTPS)HTTP over SSL. All network traffic between the client and server system is encrypted. Inaddition, there is the option to verify server and client identities. Server identities are typicallyverified and client identities are not.

L

link aggregationHigh-availability feature based on the IEEE 802.3ad Link Aggregation Control Protocol (LACP)standard which allows Ethernet ports with characteristics similar to the same switch to combineinto a single virtual device, or link with a single MAC address and potentially multiple IPaddresses.

N

nested mount file system rootFile system on which the component file systems are mounted read-only, except for mountpoints of the component file systems.


Glossary

Network Data Management Protocol (NDMP)Open standard network protocol designed for enterprise-wide backup and recovery ofheterogeneous network-attached storage.

network file system (NFS)Network file system (NFS) is a network file system protocol that allows a user on a clientcomputer to access files over a network as easily as if the network devices were attached to itslocal disks.

O

orphan fileFile that exists on secondary storage, but is no longer referenced by a stub file on VNX for file.An orphan file is kept intact on secondary storage. It can be managed by the systemadministrator.

P

passthroughArchiving method option that instructs VNX for file to read the requested data from secondarystorage. The data is returned to the client, but is not recalled to primary storage; thus the stubfile remains intact.

policy and archiving softwarePolicy and software used to archive data from VNX for file to secondary storage according tocustomer-defined policies and schedules.

policy engineExternal server on which the policy and archiving software runs.

primary storageVNX for file that provides clients access to normal files and archived files through the stub filesthat represent them. The VNX for file contains all the stub files.

public key infrastructure (PKI)Means of managing private keys and associated public key certificates for use in public keycryptography. It is a framework which allows the creation of a certificate which is used by SSL.

Q

quotaLimit on the amount of allocated disk space and the number of files (inodes) that a user or groupof users can create in a Production File System. Quotas control the amount of disk space or thenumber of files that a user or group of users can consume or both.

R

recall policyAttribute that is set per individual file and is in the stub file when a file is archived to secondarystorage. VNX for file uses the recall policy to determine the amount of data that is recalled toprimary storage to satisfy the client read request.


Glossary

S

secondary storageStorage device that contains original files associated with stub files on the primary storage. Thisdevice must be either a CIFS, HTTP, HTTPS, or NFS server. VNX for file can also be secondarystorage.

Secure Sockets Layer (SSL)Security protocol that provides encryption and authentication. It encrypts data and providesmessage and server authentication. It also supports client authentication if required by theserver.

SnapSureOn the VNX for file, a feature that provides read-only, point-in-time copies, also known ascheckpoints, of a file system.

stub fileFile that replaces the original file on VNX for file when the file is archived to secondary storage.The stub file contains all the metadata associated with the archived file and the informationrequired by VNX for file to allow it to access the archived data on secondary storage whenrequired.

Symmetrix Remote Data Facility (SRDF)EMC technology that allows two or more Symmetrix systems to maintain a remote mirror ofdata in more than one location. The systems can be located within the same facility, in a campus,or hundreds of miles apart using fibre or dedicated high-speed circuits. The SRDF family ofreplication software offers various levels of high-availability configurations, such asSRDF/Synchronous (SRDF/S) and SRDF/Asynchronous (SRDF/A).

T

TimeFinder/FSBusiness continuance configuration allowing customers to use Symmetrix business continuancevolumes (BCVs) to provide a local or remote point-in-time copy of VNX for file.

trunkSet of physical network devices bundled together for high availability. Ethernet channels andlink aggregations are trunks.

V

Virtual Data Mover (VDM)VNX for file software feature that enables users to administratively separate CIFS servers,replicate CIFS environments, and move CIFS servers from one Data Mover to another.

virus definition fileFile containing information for a virus protection program that protects a computer from thenewest, most destructive viruses. This file is sometimes referred to as a virus signature updatefile, a virus pattern update file, or a virus identity (IDE) file.

See also AV engine, AV server, CAVA, and VC client.


Glossary

virus-checking client (VC client)Virus-checking agent component of VNX for file software that runs on the Data Mover.

See also AV engine, AV server, and CAVA.

VNX FileMoverPolicy-based system used to determine where files should be physically stored. In most cases,policies are based on file size or last access time (LAT) or both and are used to identify datathat can be moved to slower, less-expensive storage.

VNX FileMover APIAPI that enables integration between VNX for file and policy and archiving software applicationsto automatically monitor and manage the movement of files between primary and secondaryimage.


Glossary


Glossary

Index

Aadjusting offline attributes 78AntiVirus server

planning considerations 39scanning applications 74

archive operation 18archive policy, FileMover concepts 15archiving method

full 23partial 23passthrough 23read operation 23

Bbacking up

CIFS 75NDMP 74NFS 76

backup strategies 28

CCAVA

integration considerations 39CDMS integration considerations 42

configuringaccess based on IP address 58

CIFSadjusting offline attributes 78backup strategies 28, 29client backups 28enabling pop-up notification 77performing a backup 75

configuringaccess based on IP address 56, 58, 59digest access authentication 61

configuring (continued)security options 25, 55

connection 49, 51, 61, 64, 65, 66deleting 66HTTP 51listing information 61, 65modifying 64NFS 49

customizing Windows pop-up messages 78

DData Mover

configuringaccess based on IP address 56, 58, 59security options 55

configuring security options 25configuring:access based on IP address 56, 58, 59enabling VNX FileMover 43tuning HTTP threads to read data fromsecondary storage 80

deleting a VNX FileMover connection 66DFS root 11digest access authentication

configuring 61disabling

VNX FileMover log files 72DNS hostname resolution

dual site disaster recovery deployment 36

EEMC E-Lab Navigator 88enabling

offline attributes 78pop-up notification 77VNX FileMover 43


error messages 89

Ffile system

creatingHTTP 51

creating connectionNFS 49

deleting a VNX FileMover connection 66enabling pop-up notification 77listing connection information 65listing VNX FileMover connections 65modifying a connection 64monitoring usage 29scanning applications 74

File-Level Retention (FLR) integrationconsiderations 42FQDN

creating a CIFS connection 45FS linking integration considerations 42

HHTTP

authentication 55listing connection information 61tuning HTTP threads 79

HTTP hostname resolutiondual site deployment 33single site deployment 31

Iincrease log file size 73Information Lifecycle Management 15integration considerations

CAVA 39CDMS 42File-Level Retention (FLR) 42FS linking 42international character sets 41quotas 38Replicator 40SnapSure 40TimeFinder/FS 40Virtual Data Mover (VDM) 41

international character setsintegration considerations 41

Llimitations 10

listingFileMover connection information 65FileMover connections 65HTTP connection information 61

log filesdisabling 72increase size 73VNX FileMover log file example 91

Mmessages, error 89metadata, retrieving from VNX file system 30modifying a VNX FileMover connection 64multihop configuration 26

NNDMP

backing up 74backup strategies 28, 29

NFSbackup strategies 28, 29creating a VNX FileMover connection 49performing an NFS backup 76

NFS/CIFS hostname resolutiondual site deployment 36single site deployment 33

NMFS integration considerations 42, 43

Ooffline attributes 78orphan file

handling limitations 27

Ppassthrough

archiving method 23backup strategies 28scanning applications 74

Qquotas

file system usage 29limitations 21


Index

quotas (continued)planning considerations 38

Rread operation 21, 23

archiving method 23Replicator integration considerations 40

Sscanning

applications 74CAVA 39

secondary hostname resolution 30recommendations 30

secondary storagearchiving small files 27backing up 29multi-hop configuration 26multiprotocol environments 24storage considerations 25

server_df command 29server_http command 61SnapSure integration considerations 40storage considerations

archiving small files 26stub file 15, 18, 20, 26, 74

archive operation 18performing an NDMP backup 74storage considerations 26write operation 20

stub file;storage considerationsarchiving small files 27deleting 27

Tthreads

tuning HTTP threads to read data fromsecondary storage 80

TimeFinder NearCopy/FarCopy 40TimeFinder/FS

integration considerations 40

troubleshooting 87tuning HTTP threads 79

UUnicode 12, 41

integration considerations 41UTF-8 12, 41

VVirtual Data Mover (VDM)

integration considerations 41VNX FileMover

concepts 15creating

NFS connection 49creating connection

HTTP 51deleting a connection 66enabling 43how it works 15listing connection information 65listing connections 65modifying a connection 64tuning HTTP threads 79

VNX FileMover APIarchive operation 18CIFS Notify Change 78configuring

access based on IP address 56, 58, 59API security 55

VNX FileMover log filesdisabling 72increase size 73

WWindows Explorer

scanning applications 73size on disk 26zip files 74

write operation 20write recall policy 21


Index


Index

Using VNX FileMover - emclink.net · the VNX, the policy and archiving application, and the...

Documents

Transcript of Using VNX FileMover - emclink.net · the VNX, the policy and archiving application, and the...