+ All Categories
Transcript
Page 1: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Administrator’s Guide

StorageX 8.0

March 2018

Page 2: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Copyright © 2018 Data Dynamics, Inc. All Rights Reserved.

The trademark Data Dynamics is the property of Data Dynamics, Inc. StorageX is a registered trademark of Data Dynamics Inc. All other brands, products, or service names are or may be trademarks or service marks of, and are used to identify, products or services of their respective owners.

Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any software, software feature, or service offered or to be offered by Data Dynamics, Inc. Data Dynamics, Inc. reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be currently available. Contact a Data Dynamics sales office for information on feature and product availability. Export of technical data contained in this document may require an export license from the United States government.

The authors and Data Dynamics, Inc. shall have no liability or responsibility to any person or entity with respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that accompany it.

Data Dynamics, Inc.

Corporate Headquarters

Data Dynamics, Inc.101 Cedar Lane, Suite 102Teaneck, NJ 07666Tel: 1-713-491-4298 Fax: 713-491-4882Email: [email protected]

2 StorageX Administrator’s Guide

Page 3: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

About This Document

This document is a procedural guide written to help storage administrators install, configure, and use Data Dynamics StorageX (StorageX). This preface contains the following sections:

•Documentation conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i

•Documentation feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii

•Contacting Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii

Documentation conventions

This section describes text formatting conventions and important notices formats.

Text formattingThe narrative-text formatting conventions that are used in this document are as follows:

For readability, command names in the narrative portions of this guide are presented in mixed lettercase: for example, switchShow. In actual examples, command lettercase is often all lowercase. Otherwise, this manual specifically notes those cases in which a command is case sensitive.

Note and attention statements The following note and attention statements are used in this documentation. They are listed below in order of increasing severity of potential hazards.

NOTEA Note provides a tip, guidance or advice, emphasizes important information, or provides a reference to related information.

bold text Identifies command namesIdentifies the names of user-manipulated GUI elementsIdentifies keywords and operandsIdentifies text to enter at the GUI or CLI

italic text Provides emphasisIdentifies variablesIdentifies paths and Internet addressesIdentifies document titles

code text Identifies CLI outputIdentifies syntax examples

StorageX Administrator’s Guide i

Page 4: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

ATTENTIONAn Attention indicates potential damage to hardware or data.

Documentation feedback

Because quality is our first concern at Data Dynamics, we have made every effort to ensure the accuracy and completeness of this document. However, if you find an error or an omission, or you think that a topic needs further development, we want to hear from you. Forward your feedback to:

[email protected]

Provide the title and version number of the document and as much detail as possible about your comment, including the topic heading and page number and your suggestions for improvement.

Contacting Support

If you encounter technical problems, send an email to [email protected] or go to the Data Dynamics, Inc. Support site at www.datdynsupport.com.

Include the following information in your email or support request:

• Product name, version, and build number

NOTETo obtain your product name, version, build number, and license serial number, log on to a computer where you installed the StorageX Console. On the Help menu, click About Data Dynamics StorageX. StorageX displays the product name, version, and build number. Click Edit License Keys and Notifications to view license key information.

• Operating system on which the StorageX server and StorageX Console are installed

• Your company name

• Your name and a phone number where we can reach you

• Your question or issue

ii StorageX Administrator’s Guide

Page 5: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

About This Document

Documentation conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i

Documentation feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii

Contacting Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii

Chapter 1 Planning and Installing StorageX

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Checklist: Planning and installing StorageX . . . . . . . . . . . . . . . . . . . . 2

Understanding the StorageX architecture and components . . . . . . . 3Understanding the StorageX server . . . . . . . . . . . . . . . . . . . . . . . 8Understanding the StorageX database . . . . . . . . . . . . . . . . . . . . 8Understanding the StorageX Console. . . . . . . . . . . . . . . . . . . . . . 8Understanding StorageX universal data engines . . . . . . . . . . . . 9

StorageX requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14StorageX server computer requirements . . . . . . . . . . . . . . . . . .14StorageX server service account requirements. . . . . . . . . . . . .16StorageX Console computer requirements . . . . . . . . . . . . . . . .17StorageX database computer requirements . . . . . . . . . . . . . . .19Universal data engine computer requirements . . . . . . . . . . . . .20Universal data engine service account requirements. . . . . . . .22File storage resource requirements . . . . . . . . . . . . . . . . . . . . . .24Feature-specific requirements . . . . . . . . . . . . . . . . . . . . . . . . . .24Network port requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

StorageX network connectivity and policy processing considerations27

StorageX installation and configuration worksheet . . . . . . . . . . . . .28

Installing StorageX components . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Installation account requirements . . . . . . . . . . . . . . . . . . . . . . .29Installing the StorageX server and StorageX Console . . . . . . . .29Installing Windows data engines . . . . . . . . . . . . . . . . . . . . . . . .34Installing and configuring Linux data engines . . . . . . . . . . . . . .35

Opening the StorageX Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Working with license keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Understanding StorageX licensing . . . . . . . . . . . . . . . . . . . . . . .38Adding license keys and specifying license notifications . . . . .39Viewing product version and license information . . . . . . . . . . .40Obtaining license keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Updating license keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41Verifying license keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Configuring StorageX access control . . . . . . . . . . . . . . . . . . . . . . . . .44Understanding role-based access control . . . . . . . . . . . . . . . . .44Understanding StorageX roles . . . . . . . . . . . . . . . . . . . . . . . . . .45Configuring role-based access control . . . . . . . . . . . . . . . . . . . .46Viewing assigned roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

StorageX Administrator’s Guide iii

Page 6: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring StorageX auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47Understanding StorageX auditing . . . . . . . . . . . . . . . . . . . . . . . .47Understanding StorageX audit events . . . . . . . . . . . . . . . . . . . .47Configuring auditing settings . . . . . . . . . . . . . . . . . . . . . . . . . . .48Viewing StorageX audit events . . . . . . . . . . . . . . . . . . . . . . . . . .49

Configuring StorageX to use a custom certificate . . . . . . . . . . . . . .50

Backing up the StorageX database . . . . . . . . . . . . . . . . . . . . . . . . . .51

Stopping and restarting the StorageX server . . . . . . . . . . . . . . . . . .51

Upgrading StorageX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52Upgrading StorageX servers and databases . . . . . . . . . . . . . . .53Upgrading StorageX Console computers . . . . . . . . . . . . . . . . . .54Upgrading StorageX universal data engines . . . . . . . . . . . . . . .55

Uninstalling StorageX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Checklist: Uninstalling StorageX components . . . . . . . . . . . . . .56Uninstalling universal data engines . . . . . . . . . . . . . . . . . . . . . .56Removing universal data engines from the StorageX database58Uninstalling the StorageX server and StorageX Consoles. . . . .59Deleting the StorageX database . . . . . . . . . . . . . . . . . . . . . . . . .60Deleting StorageX log files, cache files, and remaining program folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Chapter 2 Configuring and Viewing Storage Resources

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Checklist: Configuring storage resources and StorageX . . . . . . . . .64

Understanding the Storage Resources view . . . . . . . . . . . . . . . . . . .67Understanding the My Resources folder . . . . . . . . . . . . . . . . . .67Understanding custom folders in the Storage Resources view 69Creating custom folders in the Storage Resources view . . . . .70Deleting custom folders in the Storage Resources view. . . . . .70

Understanding storage resource validation checks . . . . . . . . . . . . .70

Verifying file storage resource DNS configuration . . . . . . . . . . . . . .71

Adding the StorageX server service account to file storage resources71

Configuring platform API access for file storage resources . . . . . . .72Enabling platform API access on Data ONTAP file storage resources72Enabling platform API access on VNX OE for File file storage resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75Enabling platform API access on OneFS file storage resources75

Configuring default credentials for file storage resources. . . . . . . .76Configuring default Data ONTAP credentials . . . . . . . . . . . . . . .76Configuring default VNX OE for File credentials. . . . . . . . . . . . .78Configuring default OneFS credentials. . . . . . . . . . . . . . . . . . . .78Configuring default SSH shell credentials . . . . . . . . . . . . . . . . .79

iv StorageX Administrator’s Guide

Page 7: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80Adding and configuring file storage resources individually. . . .82Creating file storage resource import lists . . . . . . . . . . . . . . . . .88Importing lists of file storage resources. . . . . . . . . . . . . . . . . . .95Adding and configuring object storage resources individually .96Creating object storage resource import lists . . . . . . . . . . . . . .98Importing lists of object storage resources . . . . . . . . . . . . . . . .99

Configuring storage resources in My Resources . . . . . . . . . . . . . .100

Configuring credentials for specific storage resources . . . . . . . . .103Configuring credentials for specific Data ONTAP file storage resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104Configuring credentials for specific VNX OE for File file storage resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105Configuring credentials for specific OneFS file storage resources106Configuring SSH shell credentials for specific file storage resources107Configuring credentials for specific object storage resources109

Configuring virtual file storage resources . . . . . . . . . . . . . . . . . . . .110Specifying hosting properties for Data ONTAP vFilers, Vservers, and SVMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110Specifying hosting properties for VNX OE for File Data Movers111Specifying hosting properties for EMC Isilon access zones . .112

Configuring the SNMP community name for file storage resources113

Configuring NFS credentials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

Configuring default administrative shares . . . . . . . . . . . . . . . . . . .114

Configuring replication options for clustered file storage resources115

Configuring intercluster interfaces for NetApp Cluster Mode file storage resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

Verifying storage resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117

Specifying universal data engine settings on file storage resources118Specifying universal data engine proxy computers for file storage resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119Specifying universal data engine data transfer rate limits . . .120

Viewing storage resource information. . . . . . . . . . . . . . . . . . . . . . .121Viewing storage resource properties . . . . . . . . . . . . . . . . . . . .121Refreshing displayed storage resource information . . . . . . . .121Specifying file storage resource platform type . . . . . . . . . . . .122

Removing storage resources from My Resources . . . . . . . . . . . . .122

Exporting storage resource import lists. . . . . . . . . . . . . . . . . . . . . .123

StorageX Administrator’s Guide v

Page 8: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing universal data engines . . . . . . . . . . . . . . . . . . . . . . . . . .123Specifying default service account credentials for Windows data engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124Manually deploying Windows data engines . . . . . . . . . . . . . . .124Enabling deployment of Windows data engines on Windows file storage resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126Specifying default universal data engine proxy computers . .127Viewing universal data engine status. . . . . . . . . . . . . . . . . . . .127Stopping, starting, pausing, and resuming Windows data engines128Changing deployed Windows data engine service account credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128Creating and managing universal data engine groups . . . . . .130

Changing StorageX server service account credentials . . . . . . . . .131

Working with StorageX events . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131Viewing StorageX events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131Filtering events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132

Configuring email notification profiles. . . . . . . . . . . . . . . . . . . . . . .133

Working with scheduled tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133Viewing scheduled tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134Modifying scheduled tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . .135Deleting scheduled tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136

Chapter 3 Provisioning Storage Resources

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137

Understanding provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138

Provisioning operating system requirements . . . . . . . . . . . . . . . . .138

Creating and managing CIFS shared folders . . . . . . . . . . . . . . . . .139Understanding the CIFS protocol . . . . . . . . . . . . . . . . . . . . . . .139Creating CIFS shared folders . . . . . . . . . . . . . . . . . . . . . . . . . .140Viewing CIFS shared folder properties . . . . . . . . . . . . . . . . . . .142Viewing CIFS shared folder contents . . . . . . . . . . . . . . . . . . . .142Cloning CIFS shared folders . . . . . . . . . . . . . . . . . . . . . . . . . . .143

Creating and managing NFS exports . . . . . . . . . . . . . . . . . . . . . . . .145Understanding the NFS protocol. . . . . . . . . . . . . . . . . . . . . . . .145Creating NFS exports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145Viewing NFS export properties . . . . . . . . . . . . . . . . . . . . . . . . .147Cloning NFS exports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147

Creating and managing Data ONTAP volumes and qtrees. . . . . . .149Creating volumes on Data ONTAP file storage resources . . . .149Creating qtrees on Data ONTAP file storage resources . . . . .150Viewing qtree properties on Data ONTAP file storage resources151Sharing qtrees on Data ONTAP file storage resources . . . . . .151Deleting qtrees on Data ONTAP file storage resources. . . . . .152

vi StorageX Administrator’s Guide

Page 9: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing Data ONTAP SnapMirrors . . . . . . . . . . . . .152Understanding SnapMirrors . . . . . . . . . . . . . . . . . . . . . . . . . . .153Creating SnapMirrors on Data ONTAP file storage resources 153Initializing SnapMirrors on Data ONTAP file storage resources154Quiescing and resuming SnapMirrors on Data ONTAP file storage resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154Updating SnapMirrors on Data ONTAP file storage resources155Interrupting SnapMirror data transfers on Data ONTAP file storage resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155Breaking SnapMirror relationships on Data ONTAP file storage resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156Resyncing SnapMirrors on Data ONTAP file storage resources156Deleting SnapMirrors from StorageX for Data ONTAP file storage resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157

Creating and managing object storage resource buckets . . . . . . .157Creating object storage resource buckets . . . . . . . . . . . . . . . .157Viewing object storage resource bucket properties . . . . . . . .158

Chapter 4 Creating and Managing DFS Namespaces

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

Checklist: DFS namespace planning and implementation . . . . . .160

Understanding DFS namespaces . . . . . . . . . . . . . . . . . . . . . . . . . .161DFS Namespace components . . . . . . . . . . . . . . . . . . . . . . . . .161How DFS namespaces work . . . . . . . . . . . . . . . . . . . . . . . . . . .162Understanding DFS namespace size limits and recommendations163Understanding DFS namespace types . . . . . . . . . . . . . . . . . . .164

DFS namespace operating system requirements . . . . . . . . . . . . .166DFS namespace server operating system requirements . . . .167DFS namespace client computer operating system requirements168

Understanding DFS namespace validation checks . . . . . . . . . . . .169

Creating and configuring DFS namespaces . . . . . . . . . . . . . . . . . .169Domain-based DFS namespace configuration requirements.169Creating domain-based DFS namespaces. . . . . . . . . . . . . . . .171Stand-alone DFS namespace configuration requirements. . .172Creating stand-alone DFS namespaces . . . . . . . . . . . . . . . . . .173Understanding consolidation DFS namespaces . . . . . . . . . . .175Consolidation DFS namespace configuration requirements .175Creating consolidation DFS namespaces . . . . . . . . . . . . . . . .176Configuring consolidation DFS namespaces . . . . . . . . . . . . . .177

StorageX Administrator’s Guide vii

Page 10: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS namespaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180Viewing DFS namespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180Viewing DFS namespace properties. . . . . . . . . . . . . . . . . . . . .181Modifying DFS namespace properties . . . . . . . . . . . . . . . . . . .181Enabling access-based enumeration for DFS namespaces . .182Delegating management for DFS namespaces. . . . . . . . . . . .183Specifying referral settings for DFS namespaces . . . . . . . . . .183Refreshing DFS namespaces . . . . . . . . . . . . . . . . . . . . . . . . . .184Upgrading DFS namespaces to Windows Server 2008 mode184Adding DFS namespaces to My Resources . . . . . . . . . . . . . . .186Verifying DFS namespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . .186Removing DFS namespaces from My Resources . . . . . . . . . .187Deleting DFS namespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . .188

Creating domain-based DFS namespace servers. . . . . . . . . . . . . .189

Managing domain-based DFS namespace servers . . . . . . . . . . . .190Viewing and modifying domain-based DFS namespace servers190Enabling and disabling referrals for domain-based DFS namespace servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191Overriding referral ordering for domain-based DFS namespace servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192Removing domain-based DFS namespace servers. . . . . . . . .193

Adding DFS links to DFS namespaces. . . . . . . . . . . . . . . . . . . . . . .193

Managing DFS links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195Viewing DFS link properties. . . . . . . . . . . . . . . . . . . . . . . . . . . .195Modifying DFS link properties . . . . . . . . . . . . . . . . . . . . . . . . . .196Specifying referral settings for DFS links . . . . . . . . . . . . . . . . .197Refreshing DFS links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198Creating folders in DFS namespaces . . . . . . . . . . . . . . . . . . . .198Deleting folders in DFS namespaces . . . . . . . . . . . . . . . . . . . .199Renaming DFS links and DFS namespace folders . . . . . . . . .201Converting DFS links to folders. . . . . . . . . . . . . . . . . . . . . . . . .201Deleting DFS links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202Viewing DFS link targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205Adding additional DFS link targets to DFS links . . . . . . . . . . .205Changing the status of DFS link targets. . . . . . . . . . . . . . . . . .206Specifying which users and groups can view specific DFS link targets207Enabling or disabling referrals for DFS link targets. . . . . . . . .208Overriding referral ordering for DFS link targets . . . . . . . . . . .209Deleting DFS link targets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210

Searching for DFS objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213

Converting stand-alone namespaces to domain-based namespaces214

Synchronizing DFS namespaces . . . . . . . . . . . . . . . . . . . . . . . . . . .216Creating Namespace Availability policies. . . . . . . . . . . . . . . . .217Running Namespace Availability policies immediately . . . . . .218Adding or Removing Namespaces in a Namespace Availability policy219Scheduling Namespace Availability policies . . . . . . . . . . . . . .219

viii StorageX Administrator’s Guide

Page 11: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Backing up and restoring DFS namespaces . . . . . . . . . . . . . . . . . .220Creating Namespace Backup policies . . . . . . . . . . . . . . . . . . .220Manually backing up namespaces . . . . . . . . . . . . . . . . . . . . . .222Browsing namespace backups . . . . . . . . . . . . . . . . . . . . . . . . .222Restoring namespace backups . . . . . . . . . . . . . . . . . . . . . . . .223

Configuring email notification options for Namespace policies . .224

Chapter 5 Creating and Managing Data Movement Policies

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227

Checklist: Creating and managing Data Movement policies . . . . .228

Understanding Data Movement templates and policies . . . . . . . .228Understanding Phased Migration and Archival Migration templates229Understanding Phased Migration policies . . . . . . . . . . . . . . . .230Understanding Archival Migration policies. . . . . . . . . . . . . . . .233Understanding unsupported file and folder types for migration236

Data Movement policy operating system requirements . . . . . . . .237

Data Movement policy protocol requirements . . . . . . . . . . . . . . . .237

Data Movement policy planning considerations. . . . . . . . . . . . . . .239General data transfer planning considerations. . . . . . . . . . . .239CIFS-specific data transfer planning considerations. . . . . . . .241How StorageX manages data access in CIFS environments with DFS namespaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242NFS-specific data transfer planning considerations . . . . . . . .243How StorageX manages data access in NFS environments with automount map files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245NDMP-specific data transfer requirements and configuration246Distributing file data transfer workloads using universal data engine groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248Distributing file data transfer workloads using specific cluster nodes or groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248

Creating and managing templates. . . . . . . . . . . . . . . . . . . . . . . . . .248Creating new templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248Copying an existing template . . . . . . . . . . . . . . . . . . . . . . . . . .249Viewing and modifying template properties. . . . . . . . . . . . . . .249Renaming templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250Deleting templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250

Creating Phased Migration policies . . . . . . . . . . . . . . . . . . . . . . . . .250Creating new Phased Migration policies . . . . . . . . . . . . . . . . .251Copying existing Phased Migration policies . . . . . . . . . . . . . . .257Creating Phased Migration policy import files . . . . . . . . . . . . .258Configuring Phased Migration policies to use native replication258

Validating Phased Migration policy settings . . . . . . . . . . . . . . . . . .260

Running Phased Migration policies immediately . . . . . . . . . . . . . .262

Scheduling Phased Migration policies. . . . . . . . . . . . . . . . . . . . . . .263

StorageX Administrator’s Guide ix

Page 12: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Planning for storage resource cutover . . . . . . . . . . . . . . . . . . . . . .265Creating a cutover plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266Reviewing and modifying a cutover plan . . . . . . . . . . . . . . . . .267

Canceling Phased Migration policies. . . . . . . . . . . . . . . . . . . . . . . .269

Restarting Phased Migration policies . . . . . . . . . . . . . . . . . . . . . . .269

Verifying Phased Migration policies completed successfully. . . . .271

Managing Phased Migration policies. . . . . . . . . . . . . . . . . . . . . . . .278Modifying Phased Migration policy properties. . . . . . . . . . . . .279Configuring replication options for Phased Migration policies279Specifying migration options for Phased Migration policies. .280Working with policy file and folder inclusion and exclusion filters280Running batch files with Phased Migration policies . . . . . . . .286Assigning universal data engines or universal data engine groups to Phased Migration policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288Processing security identifiers (SIDs) in a Phased Migration policy289Changing the template specified for a Phased Migration policy290Viewing and managing default settings for Phased Migration policies291Renaming Phased Migration policies . . . . . . . . . . . . . . . . . . . .291Creating custom folders for Data Movement Phased Migration policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292Viewing Phased Migration policies scheduled to run in the future292Deleting Phased Migration policies . . . . . . . . . . . . . . . . . . . . .293

Creating Archival Migration policies. . . . . . . . . . . . . . . . . . . . . . . . .294Creating new Archival Migration policies . . . . . . . . . . . . . . . . .294Copying an existing Archival Migration policy . . . . . . . . . . . . .296

Running Archival Migration policies immediately . . . . . . . . . . . . . .296

Scheduling Archival Migration policies . . . . . . . . . . . . . . . . . . . . . .297

Canceling Archival Migration policies . . . . . . . . . . . . . . . . . . . . . . .298

Restarting Archival Migration policies . . . . . . . . . . . . . . . . . . . . . . .298

Verifying Archival Migration policies completed successfully . . . .299

x StorageX Administrator’s Guide

Page 13: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Archival Migration policies . . . . . . . . . . . . . . . . . . . . . . .301Modifying Archival Migration policy properties . . . . . . . . . . . .302Immediately scanning for folders to migrate . . . . . . . . . . . . . .302Scheduling scanning for folders to migrate . . . . . . . . . . . . . . .302Viewing and managing migration candidates . . . . . . . . . . . . .303Specifying migration criteria for Archival Migration policies . .304Specifying folder exclusion and inclusion filters for Archival Migration policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305Creating batch files for Archival Migration policies . . . . . . . . .306Running batch files with Archival Migration policies . . . . . . . .308Specifying post-scanning options for Archival Migration policies310Managing Archival Migration template inheritance. . . . . . . . .311Managing default settings in Archival Migration policies . . . .311Renaming Archival Migration policies . . . . . . . . . . . . . . . . . . .312Organizing Archival Migration policies . . . . . . . . . . . . . . . . . . .312Viewing Archival Migration policies scheduled to run in the future312Deleting Archival Migration policies . . . . . . . . . . . . . . . . . . . . .313

Configuring email notification options for Data Movement policies and templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313

Bypassing path validation for Data Movement policies . . . . . . . . .314

Using batch files with Data Movement policies . . . . . . . . . . . . . . .315Using batch files with Phased Migration policies . . . . . . . . . .315Using batch files with Archival Migration policies . . . . . . . . . .316Phased Migration and Archival Migration batch file requirements317

Chapter 6 Creating and Managing Migration Projects

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .319

Checklist: Migrating data using Migration Projects . . . . . . . . . . . .320

Understanding Migration Projects . . . . . . . . . . . . . . . . . . . . . . . . . .321Understanding Migration Project sources and destinations. .323Understanding Migration Project designs . . . . . . . . . . . . . . . .326Understanding Migration Project Phased Migration templates328Understanding Migration Project Phased Migration policies .328Understanding using SnapMirror replication for Migration Projects330

Migration Project operating system requirements . . . . . . . . . . . . .332

Identifying Migration Project sources, destinations, and credentials332

Creating Migration Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333

Adding sources and destinations to Migration Projects. . . . . . . . .334

Understanding Migration Project views. . . . . . . . . . . . . . . . . . . . . .335Using Migration Project Summary views . . . . . . . . . . . . . . . . .335Using Migration Project Source and Destination Summary views336Using Migration Project Source and Destination Detail views337

Generating Data ONTAP SnapMirror reports. . . . . . . . . . . . . . . . . .338

StorageX Administrator’s Guide xi

Page 14: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Migration Project designs . . . . . . . . . . . . . . . . . . . . . . . . .339Migration Project design planning considerations . . . . . . . . .340Creating Like-to-Like Migration Project designs . . . . . . . . . . .342Creating Advanced Migration Project designs . . . . . . . . . . . . .349

Editing and specifying advanced options for Migration Project designs353

Exporting Migration Project designs . . . . . . . . . . . . . . . . . . . . . . . .354

Validating Migration Project designs . . . . . . . . . . . . . . . . . . . . . . . .354

Understanding Migration Project design validation rules . . . . . . .356

Deploying universal data engines for migrations using the NFS protocol361

Modifying Migration Project Phased Migration template properties362

Creating custom folders for Migration Project Phased Migration policies362

Executing Migration Project designs . . . . . . . . . . . . . . . . . . . . . . . .363

Viewing and modifying Migration Project Phased Migration policies365

Rolling back when a Migration Project design execution fails. . . .366

Managing Migration Projects and Migration Project designs . . . .369Modifying Migration Project properties . . . . . . . . . . . . . . . . . .369Renaming Migration Projects . . . . . . . . . . . . . . . . . . . . . . . . . .370Deleting Migration Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . .370Deleting Migration Project designs. . . . . . . . . . . . . . . . . . . . . .371

Chapter 7 Creating and Managing Disaster Recovery and Replication Policies

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .373

Checklist: Creating and managing Disaster Recovery and Replication policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374

Understanding Disaster Recovery policies . . . . . . . . . . . . . . . . . . .374Understanding Disaster Recovery policy functionality . . . . . .375CIFS-based resource monitoring. . . . . . . . . . . . . . . . . . . . . . . .375NetApp-based resource monitoring . . . . . . . . . . . . . . . . . . . . .376DFS namespace link monitoring. . . . . . . . . . . . . . . . . . . . . . . .376

Understanding replication and replication topology. . . . . . . . . . . .376

Understanding Disaster Recovery policy failover . . . . . . . . . . . . . .377Disaster Recovery failover options . . . . . . . . . . . . . . . . . . . . . .378Understanding failover topology . . . . . . . . . . . . . . . . . . . . . . . .379Understanding failover in NetApp-based resource monitoring379

Disaster Recovery policy planning considerations . . . . . . . . . . . . .380Account requirements for Disaster Recovery policies. . . . . . .381Requirements for Disaster Recovery policy links . . . . . . . . . .381

Creating Disaster Recovery policies . . . . . . . . . . . . . . . . . . . . . . . .381

Scheduling Disaster Recovery policies . . . . . . . . . . . . . . . . . . . . . .384

Manually failing over Disaster Recovery policies . . . . . . . . . . . . . .385

xii StorageX Administrator’s Guide

Page 15: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying Disaster Recovery policies completed successfully . . . .386

Manually failing back Disaster Recovery policies . . . . . . . . . . . . . .391

Resynchronizing SnapMirrors for Disaster Recovery failback . . . .392

Managing Disaster Recovery policies . . . . . . . . . . . . . . . . . . . . . . .392Modifying Disaster Recovery policy properties . . . . . . . . . . . .392Modifying the failover topology for a monitored link . . . . . . . .392Adding DFS links to Disaster Recovery policies. . . . . . . . . . . .393Configuring email notification options for Disaster Recovery policies394Configuring Disaster Recovery policies to monitor master links395Removing DFS links from Disaster Recovery policies . . . . . . .396Deleting Disaster Recovery policies . . . . . . . . . . . . . . . . . . . . .396

Understanding Disaster Recovery discovery. . . . . . . . . . . . . . . . . .396Adding DFS search paths to Disaster Recovery policies. . . . .397Manually discovering new links and qtrees . . . . . . . . . . . . . . .398Adding discovered links or qtrees to Disaster Recovery policies398

Understanding Replication policies . . . . . . . . . . . . . . . . . . . . . . . . .399

Replication policy planning considerations. . . . . . . . . . . . . . . . . . .400Replication policy requirements . . . . . . . . . . . . . . . . . . . . . . . .401Understanding unsupported file types for replication. . . . . . .401

Creating Replication policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .401

Running Replication immediately . . . . . . . . . . . . . . . . . . . . . . . . . .403

Scheduling Replication policies . . . . . . . . . . . . . . . . . . . . . . . . . . . .403

Verifying Replication policies completed successfully . . . . . . . . . .403

Managing Replication policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . .407Modifying Replication policy properties . . . . . . . . . . . . . . . . . .407Modifying the replication topology . . . . . . . . . . . . . . . . . . . . . .407Adding targets to Replication policies . . . . . . . . . . . . . . . . . . .408Removing targets from Replication policies . . . . . . . . . . . . . .409Configuring email notification options for Replication policies409Deleting Replication policies. . . . . . . . . . . . . . . . . . . . . . . . . . .410

Using batch files with Disaster Recovery or Replication policies .410Using batch files with Disaster Recovery policies . . . . . . . . . .411Using batch files with Replication policies . . . . . . . . . . . . . . . .411Disaster Recovery and Replication batch file requirements. .411Creating batch files for Disaster Recovery policies . . . . . . . . .413Running batch files with Disaster Recovery and Replication policies417

Chapter 8 Working with Reports

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .419

StorageX Administrator’s Guide xiii

Page 16: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .419Understanding Universal Data Engine reports. . . . . . . . . . . . .420Understanding Disaster Recovery reports . . . . . . . . . . . . . . . .420Understanding Migration Project Reports . . . . . . . . . . . . . . . .420Understanding Namespace Policy reports. . . . . . . . . . . . . . . .421Understanding Phased Migration Policy reports . . . . . . . . . . .421Understanding Storage Resource reports . . . . . . . . . . . . . . . .422

Creating reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .423

Viewing reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .426

Customizing displayed reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . .427Adding, removing, reordering, and resizing report columns . .427Sorting data in reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .428Grouping and ungrouping data in reports . . . . . . . . . . . . . . . .428Filtering records in reports . . . . . . . . . . . . . . . . . . . . . . . . . . . .429

Searching for items in reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . .430

Exporting reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .431

Comparing different versions of a Resource Baseline report . . . .431

Appendix A Configuring StorageX to Use SSH Shell Credentials

In this appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .433

Understanding SSH requirements . . . . . . . . . . . . . . . . . . . . . . . . . .434

Checklist: Configuring SSH shell credentials for StorageX. . . . . . .435

Generating an SSH public/private key pair. . . . . . . . . . . . . . . . . . .435

Copying public keys to Linux and VNX OE for File file storage resources and NFS clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .437

Using SSH shell credentials with StorageX . . . . . . . . . . . . . . . . . . .437

Converting PuTTY-generated SSH private keys to OpenSSH-format private keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .438

Appendix B Troubleshooting StorageX

In this appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .441

Initial troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .441Running the Support Site Kit . . . . . . . . . . . . . . . . . . . . . . . . . .441Using LogViewer to view StorageX log files . . . . . . . . . . . . . . .442

Resolving basic issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .443Troubleshooting installation issues . . . . . . . . . . . . . . . . . . . . .443Troubleshooting licensing and permissions issues. . . . . . . . .444Troubleshooting storage resource issues . . . . . . . . . . . . . . . .444Troubleshooting Phased Migration issues . . . . . . . . . . . . . . . .445Troubleshooting Migration Project issues . . . . . . . . . . . . . . . .445Troubleshooting post-migration issues . . . . . . . . . . . . . . . . . .446

xiv StorageX Administrator’s Guide

Page 17: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Troubleshooting known issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . .447Troubleshooting known storage resource management issues447Troubleshooting known Migration Project issues . . . . . . . . . .449Troubleshooting known Phased Migration issues . . . . . . . . . .451Troubleshooting known reporting issues . . . . . . . . . . . . . . . . .453

Understanding StorageX error messages and error codes . . . . . .454

Appendix C Using the StorageX API

In this appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .463

StorageX API requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .463

Using the StorageX API Web interfaces . . . . . . . . . . . . . . . . . . . . . .464

Appendix D Using StorageX for Application Transformation

In this appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .467

StorageX Application Transformation requirements . . . . . . . . . . .467

Configuring StorageX for Application Transformation . . . . . . . . . .467Configuring object endpoints and universal data engines for API usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .467Configuring Application Transform Profiles . . . . . . . . . . . . . . .468

Using the API for Application Transformation . . . . . . . . . . . . . . . . .468

StorageX Administrator’s Guide xv

Page 18: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

xvi StorageX Administrator’s Guide

Page 19: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX Administrator’s Guide

Chapter

1

Planning and Installing StorageX

This section helps you plan your StorageX implementation and install StorageX components. It provides an overview of the StorageX architecture and components, a planning and installation checklist, and requirements for each StorageX component. This section also explains how to install and uninstall StorageX components, as well as work with StorageX license keys.

NOTEThis Guide does not cover StorageX functionality in the StorageX Management Portal or StorageX Retrieval Portal, including installing and configuring those components, scanning file data, analysis of scanned files, archival to object storage, retrieval from object storage, or workload tiering of shares or exports. For information about that StorageX functionality, see the StorageX Analysis, Archival, & Retrieval Guide.

In this chapter•Checklist: Planning and installing StorageX . . . . . . . . . . . . . . . . . . . . . . . . . . 2

•Understanding the StorageX architecture and components . . . . . . . . . . . . . 3

•StorageX requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

•StorageX network connectivity and policy processing considerations . . . . 27

•StorageX installation and configuration worksheet . . . . . . . . . . . . . . . . . . . 28

•Installing StorageX components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

•Opening the StorageX Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

•Working with license keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

•Configuring StorageX access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

•Configuring StorageX auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

•Configuring StorageX to use a custom certificate . . . . . . . . . . . . . . . . . . . . . 50

•Backing up the StorageX database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

•Stopping and restarting the StorageX server . . . . . . . . . . . . . . . . . . . . . . . . 51

•Upgrading StorageX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

•Uninstalling StorageX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

1

Page 20: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Checklist: Planning and installing StorageX1

Checklist: Planning and installing StorageXUse the following checklist to plan your StorageX implementation and install StorageX components in your environment.

TABLE 1 StorageX planning and installing checklist

Task

1 Review the StorageX architecture and components. For more information, see “Understanding the StorageX architecture and components” on page 3.

2 Review StorageX requirements. For more information, see “StorageX requirements” on page 14.

3 Identify the computers that will host StorageX components and verify StorageX readiness. For more information, see “StorageX installation and configuration worksheet” on page 28.

4 Identify the storage resources that you will manage with StorageX. For more information, see “StorageX installation and configuration worksheet” on page 28.

5 If you plan to use StorageX with a DFS namespace, identify the following items:• Types of users in your environment that you want to access file data on storage resources using a

DFS namespace• Types of client computers used by these users• Applications in your environment that access file data on storage resources that you want to

include in the DFS namespaceFor more information, see “Checklist: DFS namespace planning and implementation” on page 160 and “StorageX installation and configuration worksheet” on page 28.

6 Review the existing network connectivity in your storage environment and your potential policy processing requirements to determine if you should consider installing more than one StorageX server. For more information, see “StorageX network connectivity and policy processing considerations” on page 27.

7 Install StorageX components. For more information, see “Installing StorageX components” on page 29.

8 Add storage resources to the My Resources folder in the StorageX Storage Resources view and then configure storage resources as needed in the Storage Resources view. For more information, see “Understanding the Storage Resources view” on page 67.

9 Determine if you want to use StorageX to perform the following tasks:• Use Migration Projects to migrate file data between VNX OE for File sources or destinations• Create and manage NFS exports on Linux file storage resources• Update automount map files stored on NFS clients when running Phased Migration policiesIf you want to use StorageX to perform any of these tasks, configure StorageX to use SSH shell credentials, and then specify the credentials you want StorageX to use when communicating with each of these resources. For more information, see “Configuring StorageX to Use SSH Shell Credentials” on page 433, “Configuring default SSH shell credentials” on page 79, and “Configuring SSH shell credentials for specific file storage resources” on page 107.

10 If you have file storage resources on which you do not want to install universal data engines, specify universal data engine proxy computers for the file storage resources. For more information, see “Specifying universal data engine proxy computers for file storage resources” on page 119.

11 If you have an existing DFS namespace in your environment that you want to manage with StorageX, add the DFS namespace to the My Resources folder in the Storage Resources view. Once you add your existing DFS namespace to the My Resources folder, you can use StorageX to manage it. For more information, see “Adding DFS namespaces to My Resources” on page 186.

12 If you want to create new DFS namespaces and manage your new namespaces using StorageX, design, create, and populate your new DFS namespaces. For more information, see “Checklist: DFS namespace planning and implementation” on page 160.

2 StorageX Administrator’s Guide

Page 21: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding the StorageX architecture and components 1

Understanding the StorageX architecture and componentsStorageX uses a distributed client/server architecture. The StorageX architecture helps you efficiently and centrally manage distributed, heterogeneous storage resources. The following figure shows StorageX architectural components implemented in a sample storage environment.

13 If you want to use StorageX Data Movement policies to migrate file data from source to destination CIFS shared folders or NFS exports on file storage resources, create Phased Migration and Archival Migration policies. For more information, see “Creating and Managing Data Movement Policies” on page 227.

14 If you want to use StorageX Migration Projects to help you migrate file data from source Data ONTAP and VNX OE for File file storage resources to destination Data ONTAP, VNX OE for File, and OneFS file storage resources, which includes automating the creation, or provisioning, of target items on the destination file storage resources, as well as automating the creation of Phased Migration policies that you can then use to migrate file data, create Migration Projects. For more information, see “Creating and Managing Migration Projects” on page 319.

15 If you want to use StorageX Disaster Recovery policies to manage your disaster recovery plan and ensure business continuity, create Disaster Recovery and Replication policies. For more information, see “Creating and Managing Disaster Recovery and Replication Policies” on page 373.

16 If you want to use StorageX Namespace Management policies to back up, restore, or synchronize your DFS namespaces, create Namespace Backup or Namespace Availability policies. For more information, see “Creating and Managing DFS Namespaces” on page 159.

17 Use StorageX reports as needed to help you better understand your storage resource environment and how you are using StorageX policies and Migration Projects to migrate and manage your data and your environment. For more information, see “Working with Reports” on page 419.

TABLE 1 StorageX planning and installing checklist

Task

StorageX Administrator’s Guide 3

Page 22: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding the StorageX architecture and components1

The following descriptions provide additional detail about each item in the previous figure:

StorageX Console computersThe StorageX Console is the StorageX user interface. You use the StorageX Console to connect to the StorageX server and configure your StorageX environment. Use the StorageX Console to perform the following tasks:

• Specify the storage resources you want to manage using StorageX

• Provision heterogeneous storage resources from a central management console

• Configure, manage, back up, and restore DFS namespaces, which allow users to seamlessly access file data without knowing its physical location

• Configure Data Movement Phased Migration and Archival Migration policies, which help you migrate file data from source to destination CIFS shared folders and NFS exports and optimize your file storage environment

• Configure Disaster Recovery and Replication policies, which enable you to set up your disaster recovery plan and ensure business continuity in the event of a failure in your environment

4 StorageX Administrator’s Guide

Page 23: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding the StorageX architecture and components 1

• Create and manage Migration Projects, which help you migrate file data from source Data ONTAP and VNX OE for File file storage resources to destination Data ONTAP, VNX OE for File, and OneFS file storage resources, which includes automating the creation, or provisioning, of target items on the destination file storage resources, as well as automating the creation of Phased Migration policies that you can then use to migrate file data.

StorageX server, database, and universal data engine computerThe StorageX server communicates with the StorageX database, universal data engines, DFS namespace host computers, and the storage resources in your environment. The StorageX server performs the following tasks:

• Provides summary information about storage resources managed by StorageX in your environment

• Maintains information about your storage environment and StorageX configuration

• Runs Phased Migration, Archival Migration, Disaster Recovery, Replication, Namespace Backup, and Namespace Availability policies

• Validates and executes Migration Projects

• Scans storage resources and runs file-to-object Archive policies

The StorageX server and StorageX database can be installed on the same computer or on different computers.

When you install the StorageX server, StorageX also automatically installs a Windows data engine on the StorageX server computer. StorageX can then use this universal data engine as needed to transfer file data when running policies.

StorageX Management PortalThe StorageX Management Portal is a StorageX Web user interface that is installed on the StorageX server. Use the StorageX Management Portal to perform the following tasks:

• Gather data on managed storage resources in your environment

• Analyze compiled data based on file metadata and custom tags and generate reports on your resources

• Use data analysis to determine which files need to be archived to object storage

• Create and run file-to-object Archive policies to archive data to object storage

For more information about the StorageX Management Portal, see the StorageX Analysis, Archival, & Retrieval Guide.

StorageX Retrieval PortalThe StorageX Retrieval Portal is a StorageX Web user interface that allows users and administrators to find and retrieve specific archived files from one or more object storage resources. The StorageX Retrieval Portal can be installed on any computer that can allow access to and from the StorageX server.

For more information about the StorageX Retrieval Portal, see the StorageX Analysis, Archival, & Retrieval Guide.

StorageX Metadata ServiceThe StorageX Metadata Service is installed on the StorageX server when an administrator deploys the StorageX Management Portal. This service enables StorageX to gather metadata from scanned resources, tag metadata for later analysis, and report on analyzed data.

StorageX Administrator’s Guide 5

Page 24: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding the StorageX architecture and components1

Windows and Linux data engine proxy computersStorageX Windows and Linux data engine proxy computers are computers on which you deploy or install a universal data engine to transfer data from a storage resource. Windows and Linux data engines transfer file data when StorageX policies run.

If you have storage resources on which you cannot deploy a Windows data engine or install a Linux data engine, such as Data ONTAP, VNX OE for File, or OneFS file storage resources or S3-compliant object storage resources, StorageX allows you to deploy the universal data engine to a proxy computer.

When you deploy a universal data engine to a proxy computer, StorageX uses the universal data engine on the proxy computer to migrate and replicate file data when running policies.

DFS namespace serverDFS namespace server computers store information about the DFS namespaces you configure and manage using StorageX. Client computers access the DFS namespace to obtain information about the location of the file data they want to access.

DFS namespace technology simplifies the management of your heterogeneous, distributed storage resources. StorageX enhances and extends DFS namespace technology by allowing you to quickly and easily create and manage new DFS namespaces in your storage environment. StorageX also enhances and extends the capabilities of existing DFS namespaces in your environment through the use of StorageX Phased Migration, Archival Migration, Disaster Recovery, Namespace Availability, and Namespace Backup policies.

Windows file storage resourcesWindows file storage resources store CIFS file data. When you configure and run policies that transfer file data to or from Windows file storage resources using the CIFS protocol, you can enable StorageX to automatically deploy a Windows data engine on the resources. StorageX then uses the Windows data engine to migrate or replicate file data. For more information, see “Understanding standard universal data engine usage and data transfer” on page 10.

You may not always want to deploy a Windows data engine on a Windows file storage resource. If you have a Windows file storage resource on which you do not want to deploy a Windows data engine, you can configure policies to use the Windows data engine installed by default on the StorageX server. You can also choose to have a Windows data engine installed on a proxy computer migrate or replicate CIFS file data. For more information, see “Understanding StorageX universal data engine proxy computers” on page 9.

Linux file storage resourcesLinux file storage resources store NFS file data. When you configure and run policies that transfer file data to or from Linux file storage resources using the NFS protocol, StorageX can use either the universal data engine installed by default on the StorageX server or you can manually install and configure a Linux data engine on the destination or source Linux file storage resource or on a Linux data engine proxy computer and use this Linux data engine to transfer file data. For more information, see “Understanding standard universal data engine usage and data transfer” on page 10.

Data ONTAP, VNX OE for File, and OneFS file storage resourcesData ONTAP, VNX OE for File, and OneFS file storage resources are a standard part of many file storage environments. StorageX can manage Data ONTAP, VNX OE for File, and OneFS file storage resources that host both CIFS and NFS file data.

6 StorageX Administrator’s Guide

Page 25: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding the StorageX architecture and components 1

When running policies that transfer file data to or from Data ONTAP, VNX OE for File, and OneFS file storage resources, StorageX does not deploy universal data engines onto the Data ONTAP, VNX OE for File, or OneFS file storage resources. Instead, StorageX uses either the universal data engine installed by default on the StorageX server computer or universal data engines installed on universal data engine proxy computers to transfer file data.

If you are transferring file data to or from Data ONTAP, VNX OE for File, and OneFS file storage resources using the CIFS protocol, you can specify that StorageX use a Windows data engine installed on a Windows data engine proxy computer to migrate or replicate CIFS file data to or from Data ONTAP, VNX OE for File, or OneFS file storage resources.

If you are transferring file data to or from Data ONTAP, VNX OE for File, and OneFS file storage resources using the NFS protocol, you can specify that StorageX use a Linux data engine installed on a Linux data engine proxy computer to migrate or replicate NFS file data to or from Data ONTAP, VNX OE for File, or OneFS file storage resources.

If your file storage environment contains Data ONTAP, VNX OE for File, or OneFS file storage resources and you want StorageX to use a universal data engine installed on a universal data engine proxy computer, you specify an appropriate universal data engine proxy computer for your Data ONTAP, VNX OE for File, and OneFS file storage resources when you configure your StorageX environment. StorageX uses the proxy universal data engine you specify when policies run and migrate or replicate file data on your Data ONTAP, VNX OE for File, and OneFS file storage resources.

CIFS/NFS client computersClient computers using the CIFS or NFS protocol can seamlessly and transparently access highly available CIFS and NFS file data.

IBM Cloud Object Storage, StorageGRID, and S3-compliant object storage resourcesObject storage resources represent a growing area of many users’ storage environments. StorageX can manage multiple types of object storage resources, including IBM Cloud Object Storage (COS), StorageGRID, and other S3-compliant object storage resources.

The StorageX Console lets you manage and monitor your object storage resources, and the StorageX Management Portal enables you to collect, analyze, and archive your file data to your managed object storage resource. Users can then retrieve the data to which they have access from your object storage resources using the StorageX Retrieval Portal.

For additional information about each of the components in the StorageX architecture, see the following sections:

• “Understanding the StorageX server” on page 8

• “Understanding the StorageX database” on page 8

• “Understanding the StorageX Console” on page 8

• “Understanding StorageX universal data engines” on page 9

StorageX Administrator’s Guide 7

Page 26: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding the StorageX architecture and components1

Understanding the StorageX serverThe StorageX server communicates with the StorageX database, universal data engines, and the storage resources in your environment. The StorageX server performs the following tasks:

• Maintains information about your storage environment and configuration

• Runs Phased Migration, Archival Migration, Disaster Recovery, Replication, Namespace Backup, Namespace Availability, and Archive policies

NOTEIf you want to configure and run both Data Movement and Disaster Recovery and Namespace Management policies, we recommend you set up multiple StorageX servers, with Data Movement policies running on a server separate from a server running other types of policies.

• Provides summary information about your storage environment

When you install StorageX, the StorageX server runs on the installation computer as the StorageX server service.

For more information about StorageX server system requirements and installing the StorageX server, see “StorageX server computer requirements” on page 14 and “Installing the StorageX server and StorageX Console” on page 29.

Understanding the StorageX databaseThe StorageX database is a Microsoft SQL Server database. The StorageX server uses the StorageX database to store the following information:

• Configuration information for storage resources managed by StorageX

• Configured StorageX universal data engines

• Configuration of DFS namespaces created and managed by StorageX

• Configuration of Phased Migration, Archival Migration, Disaster Recovery, Replication, Namespace Availability, and Namespace Backup policies

• Configuration of Migration Projects

• StorageX report information

Each StorageX server in your environment must use its own StorageX database. For more information about StorageX database requirements, see “StorageX database computer requirements” on page 19.

Understanding the StorageX ConsoleThe StorageX Console is the StorageX user interface and communicates with the StorageX server. Use the StorageX Console to perform the following tasks:

• Add storage resources to the StorageX environment

• Configure and provision storage resources

• Create and manage DFS namespaces

• Create and manage Phased Migration, Archival Migration, Disaster Recovery, Replication, Namespace Availability, and Namespace Backup policies

• Create and manage Migration Projects

8 StorageX Administrator’s Guide

Page 27: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding the StorageX architecture and components 1

• Manage the StorageX server

• Manage StorageX universal data engines

Multiple StorageX Consoles can connect to a single StorageX server and manage your StorageX implementation. For more information about StorageX Console computer requirements and installing the StorageX Console, see “StorageX Console computer requirements” on page 17 and “Installing the StorageX server and StorageX Console” on page 29.

Understanding StorageX universal data enginesStorageX universal data engines transfer file data when StorageX policies run. StorageX provides both Windows and Linux data engines.

Windows data engines are installed on Windows file storage resources, transfer file data using the CIFS protocol, and are Windows services.

Linux data engines are installed on Linux file storage resources and transfer file data using the NFS protocol.

If you have Data ONTAP, VNX OE for File, or OneFS file storage resources or S3-compliant object storage resources, StorageX uses Windows and Linux data engines installed on universal data engine proxy computers as needed to scan or transfer data stored on these types of storage resources.

For more information about how StorageX uses universal data engines, see the following topics:

• “Understanding StorageX universal data engine proxy computers” on page 9

• “Understanding standard universal data engine usage and data transfer” on page 10

• “Understanding universal data engine deployment without differential replication” on page 11

• “Understanding universal data engine deployment with differential replication enabled” on page 12

• “Windows data engine computer requirements” on page 21

• “Linux data engine computer requirements” on page 21

• “Installing Windows data engines” on page 34

• “Installing and configuring Linux data engines” on page 35

• “Managing universal data engines” on page 123

Understanding StorageX universal data engine proxy computers

StorageX allows you to specify a universal data engine proxy computer for storage resources and StorageX servers as needed. A universal data engine proxy computer is a computer other than the source storage resource, the destination storage resource, or the StorageX server computer where a StorageX universal data engine is installed.

StorageX uses universal data engines deployed on universal data engine proxy computers to transfer data when a universal data engine cannot be deployed on the source or destination storage resource.

StorageX Administrator’s Guide 9

Page 28: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding the StorageX architecture and components1

Configure universal data engine proxy computers for storage resources in the following situations:

• When you cannot deploy universal data engines on destination or source storage resources, and you do not want to use the universal data engine installed on the StorageX server computer to transfer data.

For example, you may need to configure universal data engine proxy computers when migrating file data to and from Data ONTAP, VNX OE for File, and OneFS file storage resources.

• When your StorageX server is not on the same LAN as the source and destination storage resources and you cannot deploy a universal data engine to the destination or source storage resources.

For example, assume you have a StorageX server computer with a universal data engine installed on one LAN. However, you want to transfer file data between a Data ONTAP source file storage resource and a OneFS file storage resource, and the Data ONTAP source file storage resource and a OneFS file storage resource are on a different LAN from the StorageX server computer with the universal data engine.

In this scenario, install a universal data engine on a proxy computer on the same LAN as the source and destination storage resources. This allows you to use a universal data engine on the same LAN as the source and destination storage resources and avoids transferring data across the WAN when StorageX policies run.

Understanding standard universal data engine usage and data transfer

StorageX uses Windows and Linux data engines to transfer data when running StorageX policies.

If you have Windows file storage resources as sources or destinations, StorageX can deploy Windows data engines automatically to sources and destinations as needed when you run StorageX policies that include Windows source or destination file storage resources. If you want to enable StorageX to automatically deploy Windows data engines to specific source or destination Windows file storage resources, you can specify this on the Computer Properties tab for a file storage resource by selecting the Allow universal data engine to be deployed to this host check box.

For more information, see “Enabling deployment of Windows data engines on Windows file storage resources” on page 126.

NOTEThe Allow universal data engine to be deployed to this host option is not selected by default. If you create a Phased Migration policy that includes a source or destination file storage resource where replication deployment is not enabled, StorageX returns an error.

If you have Linux file storage resources as source or destinations, you can manually install a Linux data engine on either the destination or source file storage resource, or you can specify a Linux data engine proxy computer for StorageX to use to transfer file data. For more information about manually installing Linux data engines, see “Installing and configuring Linux data engines” on page 35. For more information about specifying universal data engine proxy computers for Linux file storage resources, see “Specifying universal data engine proxy computers for file storage resources” on page 119.

If you have Data ONTAP, VNX OE for File, or OneFSfile storage resources or S3-compliant object storage resources, StorageX cannot deploy Windows data engines automatically to these file storage resources. You also cannot manually install a Linux data engine on these types of file storage resources. For these types of file storage resources, you must specify universal data engine

10 StorageX Administrator’s Guide

Page 29: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding the StorageX architecture and components 1

proxy computers as needed. If you are transferring file data using the CIFS protocol, specify a Windows data engine proxy computer for the destination or source as needed. If you are transferring file data using the NFS protocol, specify a Linux data engine proxy computer for the destination or source as needed.

Understanding universal data engine deployment without differential replication

StorageX determines which universal data engine to use to transfer data using the following rules:

1. StorageX first tries to determine if it can use a universal data engine installed on the destination storage resource. The destination storage resource is the storage resource where the data will be transfered.

2. If StorageX can use a universal data engine on the destination storage resource, the universal data engine on the destination storage resource pulls data from the source storage resource to the destination storage resource. The source storage resource is the storage resource where the data currently resides.

3. If StorageX cannot use a universal data engine on the destination storage resource, StorageX checks to see if it can use a universal data engine on the source storage resource.

4. If StorageX can use a universal data engine on the source storage resource, the universal data engine on the source storage resource pushes data from the source storage resource to the destination storage resource.

5. If StorageX cannot use a universal data engine on the source storage resource, StorageX checks to see if a universal data engine proxy computer has been specified for the destination storage resource.

6. If a universal data engine proxy computer has been specified for the destination storage resource, StorageX uses the universal data engine on the universal data engine proxy computer specified for the destination storage resource to pull data from the source storage resource to the destination storage resource.

7. If StorageX cannot use a universal data engine proxy computer specified for the destination storage resource, StorageX checks to see if a universal data engine proxy computer has been specified for the source storage resource.

8. If a universal data engine proxy computer has been specified for the source storage resource, StorageX uses the universal data engine on the universal data engine proxy computer specified for the source storage resource to pull data from the source storage resource to the destination storage resource.

9. If StorageX cannot use a universal data engine on the destination storage resource, a universal data engine on the source storage resource, a universal data engine proxy computer specified for the destination storage resource, or a universal data engine proxy computer specified for the source storage resource, StorageX uses the universal data engine StorageX installs by default on the StorageX server computer to transfer data.

10. If StorageX can use the universal data engine on the StorageX server computer, the universal data engine on the StorageX server computer transfers data from the source storage resource to the destination storage resource.

11. If StorageX cannot use the universal data engine on the StorageX server computer, StorageX checks to see if a universal data engine proxy computer has been specified for the StorageX server computer.

StorageX Administrator’s Guide 11

Page 30: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding the StorageX architecture and components1

12. If a universal data engine proxy computer has been specified for the StorageX server computer, StorageX uses the universal data engine on the universal data engine proxy computer specified for the StorageX server to transfer data from the source to the destination.

For example, assume that your StorageX server computer is on one network segment, but all of your storage resources are on a different network segment. In this scenario, you want to use a universal data engine proxy computer on the same network segment as your storage resources. You do not want to use the universal data engine on the StorageX server computer to transfer data. In this scenario, you specify a universal data engine proxy computer for the StorageX server computer. When you do this, StorageX will use the universal data engine on the universal data engine proxy computer you specified for the StorageX server computer to transfer the data. StorageX will not use the universal data engine installed on the StorageX server computer by default to transfer data.

13. If a universal data engine proxy computer has not been specified for the StorageX server computer, the Phased Migration policy fails, because a universal data engine is not available for StorageX to use to transfer data.

This standard process is how StorageX typically uses universal data engines to transfer data when you run Phased Migration policies. However, the process StorageX uses to transfer data using universal data engines is different when you run Phased Migration policies with differential replication enabled. For more information, see “Understanding universal data engine deployment with differential replication enabled” on page 12.

Understanding universal data engine deployment with differential replication enabled

When you enable differential replication deployment for a Phased Migration policy, StorageX does not use its standard method for using universal data engines to transfer file data.

With differential replication, you send only the parts of a file that change instead of sending the entire file. This considerably reduces replication time and network traffic.

Differential replication works best with uncompressed and unencrypted files, such as Microsoft Word (.doc files), Personal Storage Table (.pst) files, and Virtual Hard Disk (.vhd) files.

Differential replication does not work as well with other file types, such as archive (.zip) files and image files, such as .jpg files. This is because a small change in the content of these types of files causes changes throughout the entire file.

Specifying differential replication settings for a Phased Migration policy reduces the amount of data placed on the network when transferring data over a slow network but also changes how StorageX uses universal data engines to transfer file data.

If you specify that you want a Phased Migration policy to replicate data using differential replication, both the source and destination storage resources must have universal data engines installed on them, or you must specify universal data engine proxy computers for one or both of the storage resources.

StorageX determines which universal data engine to use to transfer file data using the following rules:

12 StorageX Administrator’s Guide

Page 31: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding the StorageX architecture and components 1

1. StorageX first tries to determine if it can use a universal data engine installed on the destination storage resource. The destination storage resource is the storage resource where the data will be transfered.

2. If StorageX can use a universal data engine on the destination storage resource, the universal data engine on the destination file storage resource pulls data from the source storage resource to the destination storage resource. The source storage resource is the storage resource where the data currently resides.

3. If StorageX cannot use a universal data engine on the destination storage resource, StorageX checks to see if a universal data engine proxy computer has been specified for the destination storage resource.

4. If a universal data engine proxy computer has been specified for the destination storage resource, StorageX uses the universal data engine on the universal data engine proxy computer specified for the destination storage resource to pull data from the source storage resource to the destination storage resource.

5. If StorageX cannot use a universal data engine on either the destination storage resource or on a universal data engine proxy computer specified for the destination storage resource, StorageX checks to see if it can use a universal data engine on the source storage resource.

6. If StorageX can use a universal data engine on the source storage resource, the universal data engine on the source storage resource pushes data from the source storage resource to the destination storage resource.

7. If StorageX cannot use a universal data engine on the source storage resource, StorageX checks to see if a universal data engine proxy computer has been specified for the source storage resource.

8. If a universal data engine proxy computer has been specified for the source storage resource, StorageX uses the universal data engine on the universal data engine proxy computer specified for the source storage resource to pull data from the source storage resource to the destination storage resource.

9. If StorageX cannot use a universal data engine on the destination storage resource, a universal data engine proxy computer specified for the destination storage resource, a universal data engine on the source storage resource, or a universal data engine proxy computer specified for the source storage resource, StorageX uses the universal data engine StorageX installs by default on the StorageX server computer to transfer data.

10. If StorageX can use the universal data engine on the StorageX server computer, the universal data engine on the StorageX server computer transfers data from the source storage resource to the destination storage resource.

11. If StorageX cannot use the universal data engine on the StorageX server computer, StorageX checks to see if a universal data engine proxy computer has been specified for the StorageX server computer.

12. If a universal data engine proxy computer has been specified for the StorageX server computer, StorageX uses the universal data engine on the universal data engine proxy computer specified for the StorageX server to transfer data from the source to the destination.

For example, assume that your StorageX server computer is on one network segment, but all of your storage resources are on a different network segment. In this scenario, you want to use a universal data engine proxy computer on the same network segment as your storage resources. You do not want to use the universal data engine on the StorageX server computer to transfer data. In this scenario, you specify a universal data engine proxy computer for the

StorageX Administrator’s Guide 13

Page 32: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX requirements1

StorageX server computer. When you do this, StorageX will use the universal data engine on the universal data engine proxy computer you specified for the StorageX server computer to transfer the data. StorageX will not use the universal data engine installed on the StorageX server computer by default to transfer data.

13. If a universal data engine proxy computer has not been specified for the StorageX server computer, the Phased Migration policy fails because a universal data engine is not available for StorageX to use to transfer data.

For more information about specifying differential replication options for a policy, see “Configuring replication options for Phased Migration policies” on page 279. For more information about specifying universal data engine proxy computers, see “Specifying default universal data engine proxy computers” on page 127.

StorageX requirementsThis section provides information about requirements for the following components in a StorageX environment:

• “StorageX server computer requirements” on page 14

• “StorageX server service account requirements” on page 16

• “StorageX Console computer requirements” on page 17

• “StorageX database computer requirements” on page 19

• “Universal data engine computer requirements” on page 20

• “Universal data engine service account requirements” on page 22

• “File storage resource requirements” on page 24

• “Feature-specific requirements” on page 24

• “Network port requirements” on page 25

Ensure each component meets the hardware, operating system, software, and configuration requirements for the component before you install it.

NOTEFor information about requirements for installing the StorageX Management Portal and StorageX Retrieval Portal, see the StorageX Analysis, Archival, & Retrieval Guide.

StorageX server computer requirementsEnsure you install the StorageX server on a secure, highly available computer. The StorageX server must be running in order to run policies.

You should typically install the StorageX server on a server computer rather than on a desktop computer. If you install the StorageX server on a desktop computer, the desktop computer may be shut down at the close of normal business hours rather than left operating at all times, which could impact policy processing.

Consider the following examples of how policy processing may be affected if the StorageX server becomes unavailable:

14 StorageX Administrator’s Guide

Page 33: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX requirements 1

• If a StorageX server that runs a Disaster Recovery policy becomes unavailable, StorageX cannot properly fail over because StorageX must be able to communicate with a DFS namespace in order to initiate a failover.

• If a StorageX server that runs a Replication policy becomes unavailable, StorageX cannot perform data synchronization because StorageX must be able to communicate directly with file storage resources to initiate data synchronization.

When configuring your environment, we recommend you set up separate StorageX servers to run Data Movement policies and Disaster Recovery or Namespace Management policies.

Each StorageX server in your StorageX environment must have its own StorageX database. You can install a StorageX server and its associated StorageX database on the same computer or on different computers.

For more information about the StorageX database and StorageX database requirements, see “Understanding the StorageX database” on page 8 and “StorageX database computer requirements” on page 19.

The following table lists StorageX server requirements. For more information about the StorageX server, see “Understanding the StorageX server” on page 8.

TABLE 2 StorageX server requirements

Component Minimum Requirements

Hardware • At least 2 cores (4 or more cores recommended), each 2 GHz or faster• 4 GB of memory• 500 MB available disk spaceIf you will also install the StorageX Console and the StorageX database on the StorageX server computer, ensure the computer also meets StorageX Console and StorageX database requirements for available disk space. For more information, see “StorageX Console computer requirements” on page 17 and “StorageX database computer requirements” on page 19.

Operating System One of the following operating systems with the latest service pack:• Microsoft Windows Server 2012 Essentials, Standard, or Datacenter

Edition• Microsoft Windows Server 2012 R2 Essentials, Standard, or Datacenter

Edition• Microsoft Windows Server 2016 Essentials, Standard, or Datacenter

Edition

StorageX Administrator’s Guide 15

Page 34: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX requirements1

StorageX server service account requirementsYou must specify a service account for the StorageX server when you install the StorageX server.

The service account must have the permissions required to log on as a service on the computer where you want to install the StorageX server.

In addition to logging onto the server as a service, the service account must be able to perform other storage management tasks. The simplest approach is for the StorageX server service account be a member of the Domain Admins group. This ensures that the StorageX server service account has appropriate permissions to perform the following tasks on remote computers:

• Create, manage, and delete network folders, shares and exports

• Manage permissions during file data migration

• Execute backup procedures

• If you use StorageX for DFS namespace management, the StorageX server service account must have permissions to manage domain-based DFS namespaces.

Additional Software • Microsoft .NET Framework 4.6.2• Modern web browser with appropriate security updates for viewing locally

installed help system and release notes

Additional Configuration • The StorageX server must be installed on local fixed NTFS disks.• The HTTP service must be running on the StorageX server. To verify that

the HTTP service is running, open a command prompt and enter the following command:sc query http

• If you want to configure StorageX to use SSH shell credentials to migrate file data between VNX OE for File sources and destinations using Migration Projects, to create and manage NFS exports on Linux file storage resources, or to update automount map files stored on NFS clients and you want to use an SSH public/private key pair for authentication, ensure that the StorageX server computer can access the SSH public/private key pair you want to use.StorageX can use SSH to execute shell commands to create and clone NFS exports on VNX OE for File file storage resources and Linux file storage resources and to update automount map files stored on NFS clients.For information about configuring StorageX to use SSH to execute shell commands, see “Configuring StorageX to Use SSH Shell Credentials” on page 433.

• If you install the StorageX server on a computer running the Microsoft Windows Server 2012 or Microsoft Windows Server 2016 operating system, ensure the Windows Computer Browser service is running on the computer. The Windows Computer Browser service must be running in order to enumerate domains and workgroups. In Windows Server, this service is disabled by default. If the Computer Browser service is not running, Windows is not able to enumerate domains and workgroups in Network Neighborhood, and Windows displays Error 6118: The list of servers for the workgroup is not currently available.

TABLE 2 StorageX server requirements

Component Minimum Requirements

16 StorageX Administrator’s Guide

Page 35: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX requirements 1

• If you use StorageX to view NFS exports on Linux, Data ONTAP, VNX OE for File, or OneFS file storage resources, the StorageX server service account must have Run as Root permissions on each file storage resource where you want to view NFS exports. For more information, see “Viewing NFS export properties” on page 147.

• If you use StorageX to copy, or move file data to destination OneFS file storage resources, to ensure there are no errors during file migration, the StorageX server service account must have the Run as Root permission set on all CIFS shares that are destinations in Phased Migration policies. If the StorageX server service account does not have Run as Root permissions on the destination share, you will see access denied errors in the policy manifest when the Phased Migration policy runs, and StorageX will not be able to migrate the data.

If you do not make the StorageX server service account a member of the Domain Admins group, complete the following tasks:

• Add the StorageX server service account to the local Administrators group on all StorageX components, including the StorageX server and all computers where the StorageX Console is installed.

• Ensure the StorageX server service account has the following permissions on the computer where the StorageX server is installed:

• Log on as a service

• Back up files and directories

• Restore files and directories

• Manage auditing and security log

• Take ownership of files or other objects

• If you are using StorageX to manage CIFS file storage resources, add the StorageX server service account to the local Administrators group on every CIFS file storage resource managed by StorageX.

• If you are using StorageX to manage NFS file storage resources, specify root credentials for the StorageX server service account on every NFS file storage resource managed by StorageX.

• If you are using StorageX to manage Data ONTAP file storage resources, the StorageX server service account must be a member of the local Administrators group on the Data ONTAP file storage resource in order to access the \\DataONTAPFileStorageResourceName\ETC$ share and to read and write files in the ETC$ or C$/etc directory of the Data ONTAP file storage resource.

• If you are using StorageX to manage domain-based DFS namespaces, the StorageX server service account must have Administrator permissions on both the domain controller computer and on the server computer that hosts the DFS namespace. For more information about permissions required for DFS namespace management, see the Delegate Management Permissions for DFS Namespaces article, available on the Microsoft TechNet web site at http://technet.microsoft.com/en-us/library/cc754770.aspx.

• If you are using StorageX to manage standalone DFS namespaces, the StorageX server service account must be a member of the local Administrators group on the computer that hosts the standalone DFS namespace, and the StorageX server service account must have permissions to write to the network share that stores the DFS namespace configuration information on the computer that hosts the DFS namespace.

StorageX Console computer requirementsYou can install the StorageX Console in the following locations:

StorageX Administrator’s Guide 17

Page 36: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX requirements1

• On the same computer where you install the StorageX server

• On the desktop computers of the storage administrators responsible for managing storage resources using StorageX

• On a desktop computer or server computer convenient to the storage resources StorageX manages

The following table lists StorageX Console requirements. For more information about the StorageX Console, see “Understanding the StorageX Console” on page 8.

Typically, you will run the StorageX Console using a user account with permissions to administer storage resources in your StorageX environment. However, in some cases you may choose to run the StorageX Console using the StorageX server service account, such as when user accounts used to administer StorageX are denied login access to StorageX and you need to restore access. The

TABLE 3 StorageX Console requirements

Component Minimum Requirements

Hardware • 2 GHz or faster processor• If you plan to extensively use Disaster Recovery and Namespace

Management policies, Data Dynamics, Inc. recommends that you use a minimum of 4 processor cores.

• 4GB of memory• 500 MB available disk space

Operating System One of the following operating systems with the latest service pack:• Microsoft Windows Server 2012 Essentials, Standard, or Datacenter

Edition• Microsoft Windows Server 2012 R2 Essentials, Standard, or Datacenter

Edition• Microsoft Windows Server 2016 Essentials, Standard, or Datacenter

Edition• Microsoft Windows 8 Pro or Enterprise Edition (64-bit version)• Microsoft Windows 8.1 Pro or Enterprise Edition (64-bit version)• Microsoft Windows 10 Pro or Enterprise Edition (64-bit version)

Additional Software • Microsoft .NET Framework 4.6.2• Modern web browser with appropriate security updates for viewing locally

installed help system and release notes

Additional Configuration • The StorageX client must be installed on local fixed NTFS disks.• The HTTP service must be running on the StorageX Console computer. To

verify that the HTTP service is running, open a command prompt and enter the following command:sc query http

• Minimum video display of 1,024 by 768 and 256 colors. For the best display, use more than 256 colors.

• Ensure in Windows Control Panel > Display that the Smaller - 100% option is selected. If you specify a higher option, such as Medium - 125%, some dialog boxes in StorageX may not display correctly. For example, you may not be able to see buttons on some dialog boxes.

• Use the Remote Desktop Protocol (RDP) to connect to remote computers. Other products that provide remote desktop access, such as Virtual Network Computing (VNC), may exhibit screen rendering problems when connected with remote StorageX components.

18 StorageX Administrator’s Guide

Page 37: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX requirements 1

StorageX server service account has special privileges. When you run the StorageX Console using the StorageX server service account, StorageX bypasses normal StorageX security access checks and always grants Login and Config Access Controls permissions to the StorageX server service account.

StorageX database computer requirementsThe StorageX database is a Microsoft SQL Server database. You can install the StorageX server, the StorageX Console, and the StorageX database all on the same computer, or you can install the StorageX server, the StorageX Console, and the StorageX database on different computers.

The StorageX server can communicate with the StorageX database using either Windows authentication or Microsoft SQL Server authentication. Data Dynamics, Inc. recommends using Windows authentication for communication between the StorageX server and the StorageX database.

For StorageX product evaluations, you can use either a full version of Microsoft SQL Server or Microsoft SQL Server Express. A download of Microsoft SQL Server Express 2014 is available from the Microsoft Download Center at http://www.microsoft.com/en-us/download/details.aspx?id=42299.

For any StorageX production installations, Data Dynamics, Inc. recommends using a full version of Microsoft SQL Server.

ATTENTIONIf you try to use Microsoft SQL Server Express for a production installation of StorageX, you may encounter serious performance issues.

StorageX Administrator’s Guide 19

Page 38: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX requirements1

The following table lists the detailed database requirements for StorageX. For more information about the StorageX database, see “Understanding the StorageX database” on page 8.

Universal data engine computer requirementsStorageX provides Windows and Linux data engines. StorageX policies use these Windows and Linux data engines to transfer file data. This following topics in this section provide universal data engine computer requirements for Windows and Linux data engines:

• “Windows data engine computer requirements” on page 21

• “Linux data engine computer requirements” on page 21

TABLE 4 StorageX database requirements

Component Minimum Requirements

Hardware • 2 GHz or faster processor• 4 GB of memoryConsult the documentation for the version of Microsoft SQL server you plan to use for the StorageX database for specific processor and disk space minimum requirements.Data Dynamics, Inc. provides the following recommendations, depending on how you want to install the product:• Data Movement only: If you want to use only the Data Movement features

of StorageX, we recommend that you use a minimum of 4 processor cores and allocate a minimum of 5 GB available disk space for the StorageX database.

• Disaster Recovery, Replication, or Namespace Management functionality: If you want to use any other StorageX features, including Disaster Recovery, Replication, or Namespace Management, we recommend that you use a minimum of 4 processor cores and allocate a minimum of 20 GB available disk space for the StorageX database.

• Combined StorageX server and database installation: If you want to install the StorageX server and database on the same computer, we recommend that you use a minimum of 4 processor cores.

Additional Software One of the following versions of Microsoft SQL Server with the latest service pack, depending upon product usage.For production installations of StorageX:• Microsoft SQL Server 2012 Standard or Enterprise Edition• Microsoft SQL Server 2014 Standard or Enterprise EditionFor StorageX product evaluations only:• Microsoft SQL Server 2012 Express• Microsoft SQL Server 2014 Express

Additional Configuration The collation of a SQL Server instance is set when you install it. StorageX requires that the collation of the SQL Server instance where you install the StorageX database be case insensitive. To check whether the collation of a SQL Server instance is case insensitive, run the following SQL statement:SELECT CONVERT (varchar, SERVERPROPERTY('collation'));The string returned will be similar to the following string:"SQL_Latin1_General_CP1_CI_AS"The CI in the middle of the string indicates that the collation is case insensitive.

20 StorageX Administrator’s Guide

Page 39: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX requirements 1

For more information about StorageX universal data engines, universal data engine service account requirements, and managing universal data engines, see “Understanding StorageX universal data engines” on page 9, “Universal data engine service account requirements” on page 22, and “Managing universal data engines” on page 123.

Windows data engine computer requirements

The following table lists StorageX Windows data engine computer requirements. For more information about Windows data engines, see “Understanding StorageX universal data engines” on page 9.

When StorageX automatically deploys Windows data engines, StorageX uses the ADMIN$ share on the file storage resource where the Windows data engine is installed. When you manually deploy a universal data engine in the Control Panel view, you specify the service account credentials you want the Windows data engine to use. You can use the same service account for the Windows data engine that you used for the StorageX server or you can specify different service account credentials for the Windows data engines you manually deploy. For more information about manually deploying a Windows data engine, see “Manually deploying Windows data engines” on page 124.

Linux data engine computer requirements

You can install a Linux data engine on a computer running the 64-bit version of Red Hat Enterprise Linux 7 or later.

NFS must be installed on the source and destination file storage resources in order for the Linux data engine to access files across the network. NFS does not have to be installed on the computer where the Linux data engine is installed.

TABLE 5 Windows data engine computer requirements

Component Minimum Requirements

Hardware • At least 2 cores (4 or more cores recommended), each 2 GHz or faster• 4GB of memory• 1GB available disk space minimum. More available disk space may be

required or less available disk space may be needed based on the level of logging you configure in the Event details field for each policy on the General Options tab for the policy.

Operating System One of the following operating systems with the latest service pack:• Microsoft Windows Server 2012 Essentials, Standard, or Datacenter

Edition• Microsoft Windows Server 2012 R2 Essentials, Standard, or Datacenter

Edition• Microsoft Windows Server 2016 Essentials, Standard, or Datacenter

Edition• Microsoft Windows 8 Pro or Enterprise Edition (64-bit version)• Microsoft Windows 8.1 Pro or Enterprise Edition (64-bit version)• Microsoft Windows 10 Pro or Enterprise Edition (64-bit version)

Additional Configuration • The StorageX Windows data engine must be installed on local fixed NTFS disks.

• The Remote Registry service must be running on the computer where you want to deploy a Windows data engine. For information on enabling the Remote Registry service, see the Microsoft TechNet Library.

StorageX Administrator’s Guide 21

Page 40: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX requirements1

The following table lists StorageX Linux data engine computer requirements. For more information about Linux data engines, see “Understanding StorageX universal data engines” on page 9.

Universal data engine service account requirementsStorageX automatically deploys a Windows data engine on the computer where you install the StorageX server. When StorageX automatically deploys this universal data engine, StorageX uses the service account and service account credentials you specified for the StorageX server when you installed these components as the service account for the Windows data engine. After you install the StorageX server, you can continue to use the same service account and service account credentials for the StorageX server and universal data engine, or you can change the service account and service account credentials specified for the universal data engine. For more information about changing the default universal data engine credentials, see “Specifying default service account credentials for Windows data engines” on page 124.

If you deploy Windows data engines using the same service account credentials that you used for the StorageX server service account, when you update the service account credentials for the StorageX server, you must also update the service account credentials for all of the Windows data engines deployed by the server. If you do not update the service account credentials on the deployed universal data engines, you cannot perform data transfer and replication tasks using the universal data engines. For more information about updating the service account credentials for Windows data engines, see “Changing deployed Windows data engine service account credentials” on page 128.

If you change the default universal data engine credentials for Windows data engines, you must also update the credentials of any deployed universal data engines that use the default credentials. If you do not change the credentials for the deployed universal data engines, you cannot perform data transfer and replication tasks using the universal data engines. For more information about changing the default universal data engine credentials, see “Specifying default service account credentials for Windows data engines” on page 124.

In addition to the Windows data engine StorageX automatically deploys on the StorageX server computer and the Windows data engines StorageX can automatically deploy on Windows file storage resources when transferring data, you can also choose to deploy additional Windows data engines. However, before you deploy additional universal data engines, review service account requirements. For more information, see “Windows data engine service account requirements” on page 23.

TABLE 6 Linux data engine computer requirements

Component Minimum Requirements

Hardware • At least 2 cores (4 or more cores recommended), each 2 GHz or faster• 4GB of memory• 1GB available disk space minimum. More available disk space may be

required or less available disk space may be needed based on the level of logging you configure in the Event details field for each policy on the General Options tab for the policy.

Operating System Red Hat Enterprise Linux 7 (64-bit version) or later with the following package installed:• OpenSSL 1.0.2

22 StorageX Administrator’s Guide

Page 41: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX requirements 1

Windows data engine service account requirements

In order for StorageX to deploy a Windows data engine, the universal data engine service account specified for the universal data engine must have the following permissions on the Windows computer where StorageX deploys the universal data engine:

• Log on as a service

• Create, manage, and delete network folder, shares and exports

• Manage permissions during file data migration

• Execute backup procedures

• If you use StorageX for DFS namespace management, the StorageX server service account must have permissions to manage of domain-based DFS namespaces.

• If you are using StorageX to manage OneFS file storage resources, to ensure there are no errors during file migration, the Windows data engine service account must have Run as Root permission set on all CIFS shares that are destinations in StorageX policies. If the Windows data engine server service account does not have Run as Root permissions on the destination share, you will see access denied errors in the policy manifest when the StorageX policy runs, and StorageX will not be able to migrate the data.

The simplest approach is for the universal data engine service account to use the StorageX server service account, where the StorageX server service account is a member of the Domain Admins group. This ensures that universal data engine service account has appropriate permissions to perform storage management tasks on remote computers. You should also ensure that the universal data engine service account has the permissions listed in the previous paragraph.

If you do not make the universal data engine service account a member of the Domain Admins group, complete the following tasks:

• If you are deploying a universal data engine to a Windows computer, ensure the universal data engine service account has the following permissions on the computer where the universal data engine is installed:

• Log on as a service

• Back up files and directories

• Restore files and directories

• Manage auditing and security log

• Take ownership of files or other objects

Some storage resources also may require the universal data engine service account to be a member of both the local Administrators and Backup Operators groups on the Windows computer where the universal data engine is installed.

• If you are using StorageX to manage CIFS file storage resources, add the universal data engine service account to the local Administrators group on every CIFS file storage resource managed by StorageX.

• If you are using StorageX to manage NFS file storage resources, specify root credentials for the StorageX server service account on every NFS file storage resource managed by StorageX.

• If you are using StorageX to manage Data ONTAP file storage resources, the universal data engine service account must be a member of the local Administrators group on the Data ONTAP file storage resource in order to access the \\DataONTAPFileStorageResourceName\C$ share and to read and write files in the C$/etc directory of the Data ONTAP file storage resource.

StorageX Administrator’s Guide 23

Page 42: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX requirements1

File storage resource requirementsStorageX uses standard implementations of the CIFS and NFS protocols to manage file data on many different types of heterogeneous file storage resources, including on Windows, Linux, Data ONTAP, VNX OE for File, and OneFS file storage resources. StorageX can also manage many different types and versions of file storage resources from many different hardware vendors.

However, although the StorageX product uses the standard implementations of the CIFS and NFS protocols, CIFS and NFS implementations can vary between hardware vendors. In addition, file storage resources developed by the same hardware vendor may have differences in the way CIFS and NFS protocols are implemented across the different product lines and product versions.

For more information about vendor-specific implementation of the CIFS and NFS protocols, contact your hardware vendor.

If you plan to use StorageX to migrate file data between VNX OE for File sources and destination using Migration Projects, to create and clone NFS exports on Linux file storage resources, or to update automount map files stored on NFS clients when running StorageX policies, you must specify the following items for StorageX to use when communicating with these resources:

• SSH shell credentials. For more information, see the following topics:

• “Configuring StorageX to Use SSH Shell Credentials” on page 433

• “Configuring default SSH shell credentials” on page 79

• “Configuring SSH shell credentials for specific file storage resources” on page 107

• SNMP settings. For more information, see “Configuring the SNMP community name for file storage resources” on page 113.

• NFS credentials. For more information, see “Configuring NFS credentials” on page 113.

• Universal data engine proxy computers. For more information, see “Specifying universal data engine proxy computers for file storage resources” on page 119.

For more information about how StorageX policies can update DFS namespaces or automount map files, see “How StorageX manages data access in CIFS environments with DFS namespaces” on page 242 and “How StorageX manages data access in NFS environments with automount map files” on page 245.

Feature-specific requirementsIn addition to requirements for StorageX components such as the StorageX server, StorageX Console, and StorageX database computers, there are also some specific operating system and protocol requirements for specific StorageX features.

The following table provides feature-specific requirements.

24 StorageX Administrator’s Guide

Page 43: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX requirements 1

Network port requirementsStorageX uses the following TCP ports for communication between its components:

• The StorageX server listens on TCP ports 9451, 9453, and 9463.

• The StorageX universal data engine listens on TCP port 9452.

• The StorageX Console listens on TCP port 9445.

• The StorageX Management Portal and REST API listen on TCP port 9777.

• The StorageX Retrieval Portal listens on TCP port 9888.

• The StorageX Migration REST API listens on TCP port 9454.

• The StorageX Metadata service listens on TCP port 9464.

• The StorageX Metadata service REST API listens on TCP port 9462.

These ports must be open in any firewalls located between these StorageX components.

TABLE 7 Feature-specific requirements

StorageX Feature For more information...

Provisioning file storage resources in the Storage Resources view

If you want to use StorageX as a central management console to provision heterogeneous file storage resources, ensure you understand provisioning and provisioning operating system requirements. For more information, see “Understanding provisioning” on page 138 and “Provisioning operating system requirements” on page 138.

Creating and managing DFS namespaces in the Storage Resources view

If you want to use StorageX to create and manage DFS namespaces, ensure you understand how DFS namespaces work and DFS namespace operating system requirements. For more information, see “Understanding DFS namespaces” on page 161 and “DFS namespace operating system requirements” on page 166.

Migrating file data from source to destination CIFS shared folders or NFS exports in the Data Movement view

If you want to use StorageX Data Movement policies to migrate file data from source to destination CIFS shared folders or NFS exports, ensure you understand how StorageX Data Movement policies work and Data Movement policy CIFS and NFS protocol requirements. For more information, see “Understanding Data Movement templates and policies” on page 228, “Data Movement policy operating system requirements” on page 237, and “Data Movement policy protocol requirements” on page 237.We also recommend installing a separate StorageX server when creating and running Data Movement policies.

Creating and executing Migration Projects that automate the provisioning of file storage resources and the generation of Data Movement policies in the Migration Projects view

If you want to use StorageX Migration Projects to help you migrate file data from source Data ONTAP and VNX OE for File file storage resources to destination Data ONTAP, VNX OE for File, and OneFS file storage resources, which includes automating the creation, or provisioning, of target items on the destination file storage resources, as well as automating the creation of Phased Migration policies that you can then use to migrate file data, ensure you understand how Migration Projects work and Migration Project operating system requirements. For more information, see “Understanding Migration Projects” on page 321 and “Migration Project operating system requirements” on page 332.

Configuring your disaster recovery plan and managing Disaster Recovery and Replication policies in the Disaster Recovery view

If you want to use StorageX Disaster Recovery and Replication policies to replicate file data from a primary resource to a backup resource, ensure you understand how StorageX Disaster Recovery and Replication policies work. For more information, see “Understanding Disaster Recovery policies” on page 374 and “Understanding Replication policies” on page 399.

StorageX Administrator’s Guide 25

Page 44: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX requirements1

NOTEIf you want to use the StorageX Management Portal or StorageX Retrieval Portal, you must also configure ports for use by the Apache Cassandra repository. For more information, see the StorageX Analysis, Archival, & Retrieval Guide.

StorageX transfers CIFS file data using standard Microsoft networking protocols. StorageX components access remote files and folders using their UNC path names. This access requires that the standard ports required for Microsoft networking must be opened in any firewall between the StorageX Console, StorageX server, universal data engines, and the file storage resources that host the file data StorageX replicates or migrates.

The StorageX server and Linux data engines communicate with file storage resources using the NFS protocol when transferring NFS file data. Ensure the standard ports required for NFS are opened in any firewall when transferring NFS file data.

The StorageX server uses SNMP (Simple Network Management Protocol) when identifying Data ONTAP file storage resources and uses SSH shell commands when migrating file data between VNX OE for File file sources and destinations using Migration Projects, creating or cloning exports on Linux file storage resources, and updating automount map files stored on NFS clients when running Phased Migration policies. Ensure the standard ports required for SNMP and SSH are opened in any firewall when using StorageX to migrate file data between VNX OE for File file sources and destinations using Migration Projects, to create and clone NFS exports on Linux file storage resources, or to update automount map files stored on NFS clients.

Network ports used by StorageX

The following table lists the network ports used by StorageX.

TABLE 8 Network ports used by StorageX

Service Name UDP TCP

StorageX server 9451, 9453, and 9463

StorageX universal data engine 9452

StorageX Console 9445

StorageX Management Portal/API 9777

StorageX Retrieval Portal 9888

StorageX Migration API 9454

StorageX Metadata service API 9462

26 StorageX Administrator’s Guide

Page 45: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX network connectivity and policy processing considerations 1

Network ports used by DFS

The following table lists the network ports used by DFS.

Network ports used by CIFS

CIFS uses the following standard Windows networking ports:

• 138

• 139

• 445

Network ports used by NFS

The following table lists the network ports used by NFS.

StorageX network connectivity and policy processing considerationsAs you plan your StorageX implementation, consider the following items:

• Whether the StorageX components and file storage resources are on a LAN or a WAN.

• The possible policy processing load on the StorageX server.

If you have a large number of policies that you want to run for file storage resources, consider installing additional StorageX servers to distribute the policy processing load.

Plan your StorageX implementation to ensure adequate connectivity between the StorageX server, universal data engines, and the file storage resources StorageX manages. Wherever possible, try to place StorageX components on the same local area network (LAN) as the file storage resources StorageX manages, rather than distributing StorageX components across a wide area network (WAN).

TABLE 9 Network ports used by DFS

Service Name UDP TCP

NetBIOS Datagram Service 138

NetBIOS Session Service 139

LDAP Server 389 389

Remote Procedure Call (RPC) 135

Server Message Block (SMB) 445 445

TABLE 10 Network ports used by NFS

Service Name UDP TCP

NFS mount daemon (mountd) 602 603

NFS status daemon (statd,statmon) 604 605

NFS lock manager (lockd,nlockmgr) 606 607

NFS quota daemon (quotad,rquotad) 608

StorageX Administrator’s Guide 27

Page 46: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX installation and configuration worksheet1

For example, consider the following scenarios as you plan your StorageX implementation:

• If all of your file storage resources are located on the same LAN, you may choose to install one StorageX server and then use this StorageX server to manage all of your file storage resources, run all of your policies, and manage all of your universal data engines.

• If some of your file storage resources are in one physical location and other file storage resources are in a different physical location connected through a WAN, consider installing two primary StorageX servers in two different locations. For example, if you have an office in Seattle and an office in San Francisco, install one StorageX server in Seattle and use that StorageX server to manage your file storage resources in Seattle. Install a second StorageX server in San Francisco, and use that StorageX server to manage your file storage resources in San Francisco.

StorageX installation and configuration worksheetUse this worksheet to help you plan your StorageX installation and configuration.

TABLE 11 StorageX installation and configuration worksheet

Required Information Your Information

Identify the computers on which you will install StorageX components.

StorageX server computer:StorageX database computer:StorageX Console computers:

Validate network identity and connectivity for each computer on which you will install a StorageX component. Validate the following items:• Computer name and domain membership• Accurate forward and reverse DNS lookups• Required ports open and available for StorageX

use

StorageX server computer verified? StorageX database computer verified?StorageX Console computers verified?

Identify the file storage resources StorageX will manage and verify network connectivity and permissions to install and run the universal data engine on the file storage resources, as necessary.

If you will use StorageX to manage Data ONTAP, VNX OE for File, or OneFS file storage resources, ensure you identify proxy computers where you can install universal data engines that StorageX can use when running Phased Migration policies that transfer file data to and from Data ONTAP, VNX OE for File, or OneFSfile storage resources.

For more information about validating network identity and DNS configuration for the file storage resources StorageX will manage, see “Verifying file storage resource DNS configuration” on page 71.

Identify the object storage resources StorageX will manage and verify the needed accounts and credentials for each object storage resource.

File storage resource name:• Network connectivity and permissions verified?• Universal data engine proxy computer required?File storage resource name:• Network connectivity and permissions verified?• Universal data engine proxy computer required?File storage resource name:• Network connectivity and permissions verified?• Universal data engine proxy computer required?File storage resource name:• Network connectivity and permissions verified?• Universal data engine proxy computer required?File storage resource name:• Network connectivity and permissions verified?• Universal data engine proxy computer required?File storage resource name:• Network connectivity and permissions verified?• Universal data engine proxy computer required?

28 StorageX Administrator’s Guide

Page 47: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Installing StorageX components 1

Installing StorageX componentsThis section explains how to install the following StorageX components:

• StorageX server and StorageX Console. For more information, see “Installing the StorageX server and StorageX Console” on page 29.

• StorageX Windows data engines. For more information, see “Installing Windows data engines” on page 34.

• StorageX Linux data engines. For more information, see “Installing and configuring Linux data engines” on page 35

NOTEFor information about installing the StorageX Management Portal and StorageX Retrieval Portal, see the StorageX Analysis, Archival, & Retrieval Guide.

Installation account requirementsWhen installing StorageX components, you must use an account that meets the following requirements:

• The installation account must be a member of the local Administrators group.

• If you want to install the StorageX server and database, the installation account must have at least the dbcreator role or otherwise have permission to create databases on the server where you want to install the database.

Installing the StorageX server and StorageX ConsoleYou can install the StorageX server and StorageX Console using the StorageX Setup Wizard. Before you install these StorageX components, ensure the computer on which you plan to install the StorageX component meets the requirements. For more information, see “StorageX server computer requirements” on page 14 and “StorageX Console computer requirements” on page 17.

If you plan to implement DFS namespaces in your environment, identify the computers that will host the DFS namespaces you will create and manage with StorageX.

DFS namespace name:Host computer:DFS namespace name:Host computer:

If you plan to implement DFS namespaces in your environment, identify the applications accessing data on each file storage resource you plan to manage with StorageX and determine how the introduction of DFS namespaces will affect these applications.

Application name:Application name:Application name:Application name:

If you plan to implement DFS namespaces in your environment, identify the types of client computers that will access data on file storage resources through a DFS namespace.

Computer type:Computer type:Computer type:Computer type:

TABLE 11 StorageX installation and configuration worksheet

Required Information Your Information

StorageX Administrator’s Guide 29

Page 48: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Installing StorageX components1

When you install the StorageX server, you will be prompted to specify a Microsoft SQL Server database instance for the StorageX database. Ensure you have identified the Microsoft SQL Server database instance you want to use for the StorageX database before you install the StorageX server. For more information about the StorageX database, see “Understanding the StorageX database” on page 8 and “StorageX database computer requirements” on page 19.

You can select one of the following component combinations when you install StorageX:

StorageX Console and StorageX serverInstalls both the StorageX server and the StorageX Console on a single computer.

StorageX serverInstalls only the StorageX server. Install the StorageX server on a remote computer or highly available computer, and then access the StorageX server using a StorageX Console installed on different computer, such as your desktop computer.

StorageX Console Installs only the StorageX Console. Install only the StorageX Console when you want to install the StorageX server on a remote computer or highly available computer and then access the StorageX server from a StorageX Console installed on a different computer, such as your desktop computer.

The simplest approach is to install the StorageX server and the StorageX Console on the same computer, and then use the Remote Desktop Protocol (RDP) to connect to the StorageX Console installed on the StorageX server computer.

If you want to install the StorageX server and StorageX Console on different computers, first install the StorageX server. Then install the StorageX Console.

To install the StorageX server and StorageX Console

1. Log on to the computer where you want to install the StorageX server and StorageX Console using a user account that is a member of the local Administrators group on the computer.

2. Install the Microsoft .NET Framework 4.6.2, available at www.microsoft.com.

3. Browse to the location where you saved the StorageX installation package.

4. Double-click the Setup.exe file.

5. If a User Account Control dialog box displays, click Yes to confirm that you want to run the StorageX installation package.

6. On the Setup tab, click System Requirements and review the system requirements.

7. Click Release Notes to review the Release Notes.

8. Click Install StorageX.

9. On the StorageX Setup Wizard Welcome dialog box, review the welcome message and then click Next.

10. On the End-User License Agreement dialog box, review the terms of the license agreement, select the I accept the terms in the License Agreement check box, and then click Next.

11. On the Custom Setup dialog box, select which StorageX components you want to install by completing the following steps:

30 StorageX Administrator’s Guide

Page 49: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Installing StorageX components 1

a. If you want to install both the StorageX server and the StorageX Console on the same computer, select both components. Typically both components are selected by default.

b. If you want to install only the StorageX server, deselect the StorageX Console component by selecting Entire feature will be unavailable on the StorageX Console drop-down box.

NOTEIf you want to install the StorageX server and the StorageX Console on different computers, first install the StorageX server, and then install the StorageX Console. If you later want to change the combination of product components installed on the computer, first uninstall the existing components on that computer before reinstalling new components.

c. If you want to install only the StorageX Console, deselect the StorageX server component. by selecting Entire feature will be unavailable on the StorageX server drop-down box.

d. If you want to change the default location where the setup program installs files, click Browse to browse to and select a different folder. By default, the StorageX Setup program installs StorageX in the \Program Files\Data Dynamics\StorageX folder.

12. Click Next.

13. On the StorageX Server Service Account dialog box, specify the login credentials for the StorageX server service account.

NOTEThis dialog box displays when you specify that you want to install both the StorageX server and the StorageX Console on the same computer or when you specify you want to install only the StorageX server on the computer. StorageX does not display this dialog box when you specify that you want to install only the StorageX Console on the computer.

In the Account field, type the name of the domain user account you want to use for the StorageX server service account, and in the Password field, type the password for the account.

For example, in the Account field, type DomainName\UserName, where DomainName is the name of the domain the user account is a member of, and UserName is the name of the user account you want to use for the StorageX server service account.

NOTEData Dynamics, Inc. strongly recommends using an Active Directory user account with Domain Admin permissions for the StorageX server service account. If you cannot use an account with Domain Admin permissions for the StorageX server service account, review the permissions required for the StorageX server service account and ensure that the account you specify has appropriate permissions. For more information, see “StorageX server service account requirements” on page 16.

14. Click Next.

NOTEIn order to complete the installation, the specified service account must have Logon as a Service permissions on the installation computer. If the account you specified does not have Logon as a Service permissions, the installation wizard prompts you to grant the account permission or specify a different account.

StorageX Administrator’s Guide 31

Page 50: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Installing StorageX components1

15. On the StorageX Database dialog box, select or specify a database instance for the StorageX database, and then click Next.

NOTEThis dialog box displays when you specify that you want to install both the StorageX server and the StorageX Console on the same computer or when you specify you want to install only the StorageX server on the computer. StorageX does not display this dialog box when you specify that you want to install only the StorageX Console on the computer.

The dialog box displays any SQL Server instances available in your environment. Select a database instance from the drop-down list or type the name of the database instance using the following format:

hostname\instancename or hostname:portnumber

When specifying a database instance to use, keep the following considerations in mind:

• If you want to select a SQL Server instance from the drop-down list, you must have the SQL Server Browser service enabled and started on the server where you want to install the StorageX database. For more information about enabling and starting the SQL Server Browser service, see the Microsoft SQL Server documentation.

• If the SQL Server Browser service is not running on the destination server, the drop-down list only displays the server name, without the database instance name.

• If you do not know the name of the Microsoft SQL Server instance you want to use for the StorageX database, but you do know the name of the computer that hosts the Microsoft SQL Server instance you want to use for the StorageX database, connect to the computer that hosts the database and then open the Services snap-in to see the name of the Microsoft SQL Server instance.

• If you are using a default instance of Microsoft SQL Server Express installed locally, specify .\SQLEXPRESS.

ATTENTIONData Dynamics, Inc. recommends only using Microsoft SQL Server Express for product evaluations of StorageX. For a production installation of StorageX, you should use a full installation of Microsoft SQL Server.

16. On the StorageX Database Credentials dialog box, specify credentials for the StorageX server to use when connecting to the StorageX database by completing the following steps:

NOTEThis dialog box displays when you specify that you want to install both the StorageX server and the StorageX Console on the same computer or when you specify you want to install only the StorageX server on the computer. StorageX does not display this dialog box when you specify that you want to install only the StorageX Console on the computer.

a. If you want to use Windows authentication, click Windows Authentication.

NOTEThe StorageX server can communicate with the StorageX database using either Windows authentication or Microsoft SQL Server authentication. Data Dynamics, Inc. recommends using Windows authentication for communication between the StorageX server and the StorageX database.

32 StorageX Administrator’s Guide

Page 51: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Installing StorageX components 1

b. If you want to use Microsoft SQL Server Authentication, click Microsoft SQL Server Authentication, and then specify a login ID and password.

c. Click Test Connection. StorageX checks to confirm that the credentials you specified have permissions to connect to the StorageX database. When the green check mark displays, click Next.

17. On the Specify SSL Certificate dialog box, specify the certificate you want StorageX to use to make SSL connections. You can either specify that you want StorageX to use the default certificate installed with the product or use a custom certificate generated outside of StorageX. Complete the following steps:

a. If you want to use the default certificate, select Use self-signed certificate.

b. If you want to use a custom certificate, select Use the following certificate, then select the certificate you want to use from the list of certificates displayed.

NOTEThe custom certificate must be valid, must not have expired, and must be stored locally. If a certificate is not installed locally, the certificate will not be displayed in the list.

c. After you select an option, click Next.

18. On the StorageX Server dialog box, specify the StorageX server that you want the StorageX Console to connect to by completing the following steps:

NOTEThis dialog box displays only when you specify that you want to install only the StorageX Console on a computer. StorageX does not display this dialog box when you specify that you want to install both the StorageX Console and the StorageX server on the same computer or when you specify that you want to install only the StorageX server on the computer.

a. Click Browse to browse to and select the StorageX server computer that you want the StorageX Console to connect to.

b. Click Next.

19. On the Ready to install StorageX dialog box, complete the following steps:

a. If you are installing the StorageX Console and you want to create a desktop shortcut for the StorageX Console, ensure the Create a Desktop shortcut for the StorageX Console is selected.

NOTEThis option only displays if you are installing both the StorageX server and the StorageX Console or if you are installing only the StorageX Console. StorageX does not display this option if you are installing only the StorageX server.

b. Click Install to begin the installation.

20. On the Installation Complete dialog box, complete the following steps:

a. If you are installing the StorageX Console and you want to open the StorageX Console after installation completes, verify that the Run StorageX Console check box is selected.

When you select this check box, the StorageX Console will automatically open after you click Finish and prompt you to add your license keys for StorageX and specify license notifications.

StorageX Administrator’s Guide 33

Page 52: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Installing StorageX components1

If you clear the Run StorageX Console check box, the StorageX Console will not automatically open and prompt you to add your license keys for StorageX after you click Finish. You must open the StorageX Console and add your license keys before you can start using StorageX.

For more information about opening the StorageX Console and adding license keys, see “Opening the StorageX Console” on page 37 and “Adding license keys and specifying license notifications” on page 39.

b. Click Finish to close the setup program.

Installing Windows data enginesStorageX automatically installs a Windows data engine on the StorageX server computer when you install the StorageX server. You can also enable StorageX to automatically install Windows data engines on destination or source Windows file storage resources when transferring CIFS data to or from Windows file storage resources when running StorageX policies.

NOTEIf you have Data ONTAP, VNX OE for File, or OneFS file storage resources, StorageX can use Windows data engines installed on universal data engine proxy computers to transfer file data stored on these types of file storage resources. For more information about universal data engine proxy computers, see “Understanding StorageX universal data engine proxy computers” on page 9.

For more information about how StorageX automatically deploys Windows data engines, see “Understanding standard universal data engine usage and data transfer” on page 10. For more information about enabling StorageX to deploy universal data engines, see “Enabling deployment of Windows data engines on Windows file storage resources” on page 126. You can also manually deploy Windows data engines in the Control Panel view. For more information about manually deploying Windows data engines, see “Manually deploying Windows data engines” on page 124. For more information about configuring universal data engine proxy computers, see “Specifying default universal data engine proxy computers” on page 127.

NOTEThe Remote Registry service must be running on the computer where you want to deploy a Windows data engine. For information on enabling the Remote Registry service, see the Microsoft TechNet Library.

In some cases, you may not be able to install a Windows data engine on a destination or source file storage resource where you want to transfer CIFS file data. For example, in a CIFS file data migration, a destination or source file storage resource may be a Data ONTAP, VNX OE for File, or OneFS file storage resource, and you cannot install a Windows data engine on these types of file storage resources. You may also have one or more Windows file storage resources where you do not want to install Windows data engines.

In these scenarios, install Windows data engines on Windows data engine proxy computers as needed or use the universal data engine installed on the StorageX server to migrate the CIFS file data. For more information about universal data engine proxy computers, see “Understanding StorageX universal data engine proxy computers” on page 9.

34 StorageX Administrator’s Guide

Page 53: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Installing StorageX components 1

Installing and configuring Linux data enginesYou can use the Windows data engine on the StorageX server that StorageX installs by default when you install the StorageX server to migrate NFS file data. You can also manually install and configure Linux data engines on destination and source Linux file storage resources or you can install and configure a Linux data engine on a Linux data engine proxy computer to migrate NFS data.

Data Dynamics, Inc. recommends that you install Linux data engines on Linux destination file storage resources when migrating NFS file data stored on Linux file storage resources. This typically reduces the amount of time required to complete the migration. If you cannot install a Linux data engine on the destination file storage resource, install a Linux data engine on the source file storage resource.

In some cases, you may not be able to install a Linux data engine on a destination or source file storage resource where you want to transfer NFS file data. For example, in an NFS file data migration, a destination or source file storage resource may be a Data ONTAP, VNX OE for File, or OneFS file storage resource, and you cannot install a Linux data engine on these types of file storage resources. You may also have one or more Linux file storage resources where you do not want to install Linux data engines. In these scenarios, install Linux data engines on Linux data engine proxy computers as needed or use the universal data engine installed on the StorageX server to migrate the NFS file data. For more information about universal data engine proxy computers, see “Understanding StorageX universal data engine proxy computers” on page 9.

Before you install a Linux data engine, ensure the Linux computer where you want to install the Linux data engine meets system requirements. For more information, see “Linux data engine computer requirements” on page 21.

To install and configure a Linux data engine

1. Copy the Linux data engine RPM file from the following folder in the StorageX installation package or CD to the Linux computer where you want to install the Linux data engine:

\Replication Agents\Linux\storagexra-Version.rpmwhere Version is the version of the StorageX Linux data engine you want to install.

2. Connect to the Linux computer where you want to install the Linux data engine and open a command prompt.

ATTENTIONThe user account you use to install the Linux data engine must have root access permissions on the computer where you want to install.

3. Type rpm -i and then the path to the Linux data engine .rpm file. Then press Enter.

For example, if you placed the Linux data engine in the /tmp folder, type:

rpm -i /tmp/storagexra-Version.rpm

where Version is the version of the StorageX Linux data engine you want to install.

StorageX installs the Linux data engine in the /usr/local/URA folder.

4. After the Linux data engine installation completes, configure the Linux data engine by completing the following steps:

a. In the command prompt, type:/etc/init.d/ura configure

StorageX Administrator’s Guide 35

Page 54: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Installing StorageX components1

b. If the following error message displays, the required OpenSSL 1.0.2 package is not installed on the computer:

/lib64/libcrypto.so.10: version 'OPENSSL_1.0.2' not foundTo install the required package, type the following command:

sudo yum install openssl

c. When prompted to enter the TCP port the Linux data engine should listen on, press Enter to accept the default or specify a TCP port for the universal data engine. Ensure that the Linux firewall is configured to allow communication on the TCP port you specify for the Linux data engine. For more information about universal data engine listening ports, see “Network ports used by StorageX” on page 26.

d. When prompted to enter the TCP port the StorageX server should listen on, press Enter to accept the default or specify a TCP for the StorageX server. Ensure that the Windows firewall is configured to allow communication on the TCP port you specify for the StorageX server. For more information about StorageX server ports, see “Network ports used by StorageX” on page 26.

e. When prompted, type the fully qualified domain name of the StorageX server the Linux data engine will communicate with and then press Enter. For example, type ComputerName.DomainName, where ComputerName is the name of the computer where the StorageX server is installed and DomainName is the name of the domain to which the StorageX server computer belongs.

f. When the second prompt displays that allows you to specify a second name for a second StorageX server, if you have a second StorageX server that you want the Linux data engine to communicate with, type the fully qualified domain name for the server. If you do not have a second StorageX server, press Enter to continue.

5. After StorageX finishes collecting information, type p and then press Enter to proceed with the installation.

6. Start the Linux data engine by typing the following command at the command prompt:

/etc/init.d/ura start7. To verify the Linux data engine is running on the computer, at the command prompt type ps

-ef | grep Rep and then press Enter.

8. Open the StorageX Console and confirm that the Linux data engine installed displays in the list of deployed data engines by completing the following steps:

a. Click the Control Panel tab.

b. In the left pane, click Deployed Data Engines.

c. In the center pane, verify that the name of the Linux computer where you installed the Linux data engine displays in the Host column and that Running displays in the Status column.

36 StorageX Administrator’s Guide

Page 55: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Opening the StorageX Console 1

Opening the StorageX ConsoleOpen the StorageX Console after you install it using the StorageX Setup Wizard. You can use the StorageX Console to perform the following tasks:

• Specify StorageX license keys

• Add file storage resources to StorageX for management

• Configure and provision file storage resources

• Create and manage DFS namespaces

• Create and manage Data Movement policies, including Phased Migration and Archival Migration policies

• Create and manage Migration Projects

• Create and manage Disaster Recovery and Replication policies

• Create and manage Namespace Backup and Availability policies

For more information about installing the StorageX Console, see “Installing StorageX components” on page 29 and “Installing the StorageX server and StorageX Console” on page 29.

To open the StorageX Console

1. On the Start menu, click All Programs > Data Dynamics > StorageX > StorageX Console.

2. If the License Configuration Wizard displays, specify a license key for the StorageX installation. The License Configuration Wizard displays the first time you open the StorageX Console after installation. It will continue to display until you specify a license key for your installation. For more information about specifying a license key for your installation, see “Adding license keys and specifying license notifications” on page 39.

3. If the License Configuration Wizard does not display, a license for your StorageX installation has been specified and you are ready to being using StorageX. For more information about getting started using StorageX, see “Checklist: Planning and installing StorageX” on page 2.

Working with license keysThis section provides information about working with license keys, and includes the following topics:

• “Understanding StorageX licensing” on page 38

• “Adding license keys and specifying license notifications” on page 39

• “Viewing product version and license information” on page 40

• “Obtaining license keys” on page 40

• “Updating license keys” on page 41

• “Verifying license keys” on page 42

StorageX Administrator’s Guide 37

Page 56: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Working with license keys1

Understanding StorageX licensingStorageX license keys allow you to use one or more product features on a feature-by-feature basis, with different licensing structures depending on the feature. For example, you could have a license that only enabled you to use StorageX to migrate data from one resource to another using Data Movement policies but not configure Disaster Recovery policies or use Analytics to scan the resources in your environment.

StorageX licenses can include one or more of the following features:

MigrationApplies to all migration features, including Phased Migration policies, Archival Migration policies, and Migration Projects.

AnalyticsApplies to all analysis-related features, including resource data scans and analysis sets in the StorageX Management Portal.

Archive/RestoreApplies to all object-archival and retrieval features, including Archive policies in the StorageX Management Portal and retrieving files using the StorageX Retrieval Portal.

TransformApplies to all application transform features, including using the StorageX APIs to transform file application data into custom objects.

TierApplies to all workload tiering features, including Workload Tiering policies generated using the StorageX Management Portal.

ReplicationApplies to all replication features, including Replication policies.

Disaster RecoveryApplies to all disaster recovery features, including Disaster Recovery policies.

NamespaceApplies to advanced namespace features, including Namespace Availability and Namespace Backup policies.

ReportingApplies to all reporting features.

DiscoveryApplies to all discovery features, including the File Insight tool.

NOTEWith all features, if your license expires while running a scan or policy, StorageX allows the current scan or policy to finish running. Future scans or policies cannot be started until the license is renewed or a new license has been applied.

38 StorageX Administrator’s Guide

Page 57: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Working with license keys 1

For information about adding license keys to your StorageX installation, see “Adding license keys and specifying license notifications” on page 39.

Adding license keys and specifying license notificationsSpecify StorageX license keys using the License Configuration Wizard. The License Configuration Wizard displays the first time you open the StorageX Console. You can also open the License Configuration Wizard any time you need to view or update license keys.

When you specify license keys, you can also enable license notifications. Enable license notifications to receive email notifications related to expiring licenses prior to license expiration. Enabling license notifications when adding licenses helps ensure the appropriate people in your organization receive proactive email notifications about expiring licenses 45, 30, and 15 days prior to license expiration, and then once a day when a license will expire in 15 days or less. This also helps prevent automated tasks, such as the running of Phased Migration or Archival Migration policies, from failing due to an expired license.

For example, assume that you configured a Phased Migration policy, Archival Migration policy, or other automated task several months ago, but now your license key will expire in 45 days or less. If license notifications are enabled, you and others in your organization, such as the corporate team that handles license renewals, as well as the storage administrators who use StorageX on a weekly or daily basis, will receive proactive notifications about expiring licenses prior to the license keys actually expiring.

For more information about obtaining license keys, see “Obtaining license keys” on page 40. For more information about viewing product version and license key information, see “Viewing product version and license information” on page 40.

To specify StorageX license keys

1. Open the StorageX Console.

2. If you are opening the StorageX Console for the first time, the License Configuration Wizard displays. Review the welcome message, and then click Next to display license keys.

3. If you have previously installed StorageX and specified license keys, on the Help menu, click About Data Dynamics StorageX and then click Edit License Keys and Notifications.

4. Click Add, and then paste in the license key string or click Browse for license file to browse to and select a StorageX license key.

If you browse for the license file, the user account you use to run the StorageX Console must have permissions to the folder where the license file is stored.

5. Click OK, and then click Next.

6. If you want to use an existing notification profile for sending licensing reminders, click the Select an existing notification profile or create a new profile list and select the profile you want to use, then click Email is enabled for the selected notification profile.

7. If you want to create a new notification profile to use to send licensing reminders, complete the following steps:

a. Click the Select an existing notification profile or create a new profile list.

b. Click New.

c. Specify the SMTP settings you want to use for the new profile. For more information about the SMTP settings, click the Help button on the dialog box.

StorageX Administrator’s Guide 39

Page 58: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Working with license keys1

d. Specify the message settings you want to use for the new profile. For more information about the message settings, click the Help button on the dialog box.

e. Click Send Test Message to verify the profile settings are correct.

f. If you want to use the new notification profile for all notifications, click Enable all usage of this notification.

g. Click OK.

8. Click Next.

9. Click Finish.

Viewing product version and license informationYou can view product version and license information at any time in the StorageX Console.

NOTEYou can also view product version and general license information in the StorageX Management Portal. For information about installing and accessing the Management Portal, see the StorageX Analysis, Archival, & Retrieval Guide.

To view product version and license information

1. Open the StorageX Console.

2. On the Help menu, click About Data Dynamics StorageX.

StorageX displays the About Data Dynamics StorageX dialog box, which provides information about the product version and build number.

3. Click Edit License Keys and Notifications. StorageX displays information about each installed license.

4. If a license key displays in red italics, the license key has expired. For more information about obtaining a new license key and updating a license key, see “Obtaining license keys” on page 40 and “Updating license keys” on page 41.

5. If you want to view details for a specific license key, double-click the license key and view the license details in the License Details dialog box. For more information about each field, click the Help button on the dialog box.

Obtaining license keysYou can purchase new licenses for StorageX or extend your StorageX evaluation period by sending an e-mail message to:

[email protected]

If you want to purchase new licenses for StorageX, include the following information in your e-mail message:

• Company name

• Your name, job title, and a phone number where you can be contacted

• Product name and version you want to purchase

40 StorageX Administrator’s Guide

Page 59: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Working with license keys 1

If you want to extend your StorageX evaluation period, include the following information in your e-mail message:

• Company name

• Your name, job title, and a phone number where you can be contacted

• Operating system on which the StorageX server and StorageX Console are installed

• Product information, including the following information:

• Product name

• Version number

• Build number

• License details for the StorageX evaluation you want to extend, including created date, customer contact name, and ID, and features you want enabled in the product.

For more information about obtaining product information such as version and license key information, see “Viewing product version and license information” on page 40.

For more information about adding license keys, see “Adding license keys and specifying license notifications” on page 39. For more information about updating license keys, see “Updating license keys” on page 41.

Updating license keysYou may need to add, update, or remove license keys under the following conditions:

• When you want to extend a product evaluation period

• When you purchase the product following a product evaluation

• When you purchase additional licenses or product features

• When a license key expires

NOTEIf a license key displays in red italics, the license key has expired. For more information about obtaining a new license key, see “Obtaining license keys” on page 40.

To update a license key

1. Contact Data Dynamics, Inc. to obtain a new StorageX license key. For more information, see “Obtaining license keys” on page 40.

2. Once you have received the updated license key, open the StorageX Console.

3. On the Help menu, click About StorageX.

4. Click Edit License Keys and Notifications.

5. If you want to remove a license key, select the license key you want to remove, and then click OK.

6. If you want to add a license key, complete the following steps:

a. Click Add, and then paste in the license key string or click Browse for license file to browse to and select a StorageX license key.

If you browse for the license file, the user account you use to run the StorageX Console must have permissions to the folder where the license file is stored.

StorageX Administrator’s Guide 41

Page 60: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Working with license keys1

a. Click OK, and then click Next.

b. If you want to enable email notifications for license reminders, select the Enable License Notifications check box, and then specify the appropriate settings for each field. For more information about each setting, click the Help button on the dialog box.

c. Click Send Test Message.

d. Click Next.

e. Click Finish.

Verifying license keysAfter you obtain, add, or update one or more license keys, you must then verify your new license keys before you can use StorageX functionality. The following workflow diagram explains how to verify your StorageX license key:

42 StorageX Administrator’s Guide

Page 61: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Working with license keys 1

StorageX Administrator’s Guide 43

Page 62: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring StorageX access control1

To verify a license key

1. Open the StorageX Console.

2. On the Help menu, click About Data Dynamics StorageX and then click Edit License Keys and Notifications.

3. Select the license key you want to verify and click Verify.

4. Copy the verification code provided and send it to your Data Dynamics sales contact.

5. When Data Dynamics provides the verification response, copy-and-paste the response into the Please enter the verification response from Data Dynamics into the textbox below text box or click Browse for verification response file to browse to and select a response file.

6. Click OK, and then click Next.

7. Click Next, and then click Finish.

Configuring StorageX access controlAfter you install StorageX, administrators can configure access to the StorageX server and the StorageX Console using role-based access control.

This section provides information about configuring security in StorageX, and includes the following topics:

• “Understanding role-based access control” on page 44

• “Understanding StorageX roles” on page 45

• “Configuring role-based access control” on page 46

• “Viewing assigned roles” on page 47

Understanding role-based access controlWhen you install StorageX, any user that can access the installation computer can use all features of the StorageX Console by default. If you want to restrict access to the StorageX Console, you can enable role-based access control functionality.

This functionality lets you assign specific predefined roles to individual users or groups in your StorageX environment. Each role provides a limited set of permissions to the users or groups to which the role is assigned. You can assign roles to your users to only allow users to view resources or policies in StorageX but not run policies or modify resources, or to allow certain users to have Administrator access to the Console

If you enable role-based access control in StorageX, access to StorageX is limited to only the StorageX service account until you assign roles to your users. The StorageX service account is automatically assigned the Administrator role during installation, and that role cannot be removed from the service account.

Any user not assigned a role will not be able to access the StorageX Console. We recommend that if you enable role-based access control, you immediately assign all potential StorageX Console users in your environment the Read-Only role, at minimum.

StorageX Console users can see what roles they have been assigned in the About Data Dynamics StorageX dialog box. For more information about viewing assigned roles, see “Viewing assigned roles” on page 47.

44 StorageX Administrator’s Guide

Page 63: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring StorageX access control 1

NOTES:

• You cannot use roles to limit access to specific objects within StorageX. For example, you cannot assign a role to a user that lets the user read or run reports but only view Phased Migration policies.

• You cannot customize roles within StorageX. The only roles available for use with role-based access control are the roles initially provided with the product.

Understanding StorageX rolesStorageX uses the following set of roles to allocate permissions to a user or group of users, depending on which role the user or group is assigned: Read-Only; Read and Execute; Read, Write, and Execute; and Administrator.

A user can be assigned roles either individually or as a member of a group. If a user is assigned one role, but a group the user belongs to is assigned another role, the users has all the permissions of the combined roles. For example, if you assign User A to the Read-Only role, and then add Group B, to which User A belongs, to the Read, Write, and Execute role, User A has all the permissions of the Read, Write, and Execute role.

Read-OnlyThis role allows a user to only view StorageX policies, storage resources, or reports in the StorageX Console. A user only assigned the Read-Only role cannot create, modify, run, or delete policies, add or remove storage resources, or create or modify reports.

NOTEWhen configuring role-based access control for StorageX, we recommend you assign all StorageX Console users the Read-Only role at a minimum.

Read and ExecuteThis role allows a user to perform the following tasks:

• View policies, storage resources, or reports

• Run policies

• Refresh the contents of a report.

A user only assigned the Read and Execute role cannot create, modify, or delete policies, add or remove storage resources, or create, modify, or delete reports.

Read, Write, and ExecuteThis role allows a user to perform the following tasks:

• View, create, modify, delete, or run policies

• View, add, or remove storage resources

• View, refresh, create, modify, or delete reports

• Perform other actions in the StorageX Console

A user only assigned the Read, Write, and Execute role cannot modify security settings within StorageX.

StorageX Administrator’s Guide 45

Page 64: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring StorageX access control1

AdministratorThis role allows the user full access to the StorageX server, including security settings that control both role-based access and auditing.

NOTES:

• The StorageX service account is assigned the Administrator role by default and cannot be removed from that role, even if you delete the service account from the Administrators group in the Options dialog box.

• You cannot assign the Administrator role to a group. Only individual users can be assigned the Administrator role.

• Only members of the Administrator role can assign or remove the Administrator role from a user.

Configuring role-based access controlTo restrict access to StorageX based on a user’s role, you must configure the StorageX role-based access control settings located in the Access Control tab of the Options dialog box.

To configure role-based access to StorageX

1. Open the StorageX Console.

2. Click File > Options.

3. Click the Access Control tab.

4. If you want to let non-Administrator users view the Access Control and Auditing tabs, click Allow non-Administrators to view the Security configuration.

NOTEIf you do not select this option, only users assigned the Administrator role can view either the Access Control or Auditing tabs of the Options dialog box.

5. In the Role-based Access Control area, click Enable.

ATTENTIONAfter you enable role-based access control for StorageX, only users or groups assigned a role will be able to view your environment in the StorageX Console.

6. If you want to assign a user the Administrator role, complete the following steps:

a. In the Administrators area, click Add.

b. Specify or browse to and select one or more users to add.

c. Click OK.

7. If you want to assign a user a non-Administrator role, complete the following steps:

a. In the Role-based Access Control area, click Add.

b. Specify or browse to and select one or more users or groups to add.

c. Click OK.

d. If you want to change the default Read Only role assigned to the new user or group, click the role and select the role you want to assign.

46 StorageX Administrator’s Guide

Page 65: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring StorageX auditing 1

8. If you want to remove the Administrator role from a user, select the user and click Delete.

9. If you want to remove a user or group from the role-based access control list, select the user or group and click Delete.

10. Click OK when finished.

Viewing assigned rolesIf you log into the StorageX Console as a non-Administrator user, you can see what roles are assigned to your user account in the About Data Dynamics StorageX dialog box.

To view your assigned roles in StorageX

1. Open the StorageX Console.

2. Click Help > About Data Dynamics StorageX.

3. Find the User Info field. The account currently running the StorageX Console is displayed, with the assigned role or roles in parentheses.

4. Click OK when finished.

Configuring StorageX auditingStorageX Administrators can configure the product to automatically track users’ access to the StorageX server and StorageX Console, including when users start the Console, create or delete a policy, or modify security settings.

This section provides information about configuring StorageX auditing, and includes the following topics:

• “Understanding StorageX auditing” on page 47

• “Understanding StorageX audit events” on page 47

• “Configuring auditing settings” on page 48

• “Viewing StorageX audit events” on page 49

Understanding StorageX auditingWhen a user performs a specific set of actions in StorageX, the product automatically logs an audit event to both the Windows Application event log and the log4net trace log on the StorageX server. This enables StorageX Administrators to track access to the product by users and applications. StorageX auditing is disabled by default.

Understanding StorageX audit eventsStorageX can log an audit event if one of the following types of actions occurs:

Security Configuration Auditing• The security configuration was modified.

StorageX Administrator’s Guide 47

Page 66: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring StorageX auditing1

StorageX logs an event when a user or application modifies StorageX role-based access or auditing settings. This event provides the user name of the user or application that modified the security settings.

Connection Auditing• A connection to the server was made.

StorageX logs an event when a user connects to the StorageX server. This typically occurs when a user opens the StorageX Console. This event provides the user name of the user that successfully connected to the server.

• A connection to the server was denied.

StorageX logs an event when a user is denied access to the StorageX server. This event provides the user name of the user denied access to the server.

• A connection to the server was closed.

StorageX logs an event when a user disconnects from the StorageX server. This occurs when a user closes the StorageX Console or if the user encounters a connection failure of some kind. This event provides the user name of the user that disconnected from the server.

Policy Auditing• A policy was created.

StorageX logs an event when a user creates a new policy. This event provides the user name of the user that created the policy, the type of policy created, and the name of the new policy.

• A policy was deleted.

StorageX logs an event when a user deletes a policy. This event provides the user name of the user that deleted the policy, the type of policy deleted, and the name of the policy.

• A policy was executed.

StorageX logs an event when a user manually runs a policy outside of the policy schedule. This event provides the user name of the user that ran the policy, the type of policy run, and the name of the policy.

• A policy was modified.

StorageX logs an event when a user modifies a policy. This event provides the user name of the user that modified the policy, the type of policy modified, and the name of the policy.

Configuring auditing settingsIf you want StorageX to log audit events for different areas of the product, you must configure the auditing settings located in the Auditing tab of the Options dialog box.

To configure auditing settings for StorageX

1. Open the StorageX Console using an account that is a member of the Administrators role in StorageX.

NOTEUsers who are not Administrators cannot view or modify auditing settings unless the Allow non-Administrators to view the Security configuration setting is selected on the Access Control tab of the Options dialog box. For more information about configuring this setting, see “Configuring role-based access control” on page 46.

48 StorageX Administrator’s Guide

Page 67: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring StorageX auditing 1

2. Click File > Options.

3. Click the Auditing tab.

4. If you want StorageX to log audit events related to the security configuration of the product, select one or more events in the Security Configuration Auditing section. For more information about each audit event, click the Help button on the dialog box.

5. If you want StorageX to log audit events related to user connections to StorageX and access to the StorageX Console, select one or more events in the Connection Auditing section. For more information about each audit event, click the Help button on the dialog box.

6. If you want StorageX to log audit events related to creating, modifying, or running policies, select one or more events in the Policy Auditing section. For more information about each audit event, click the Help button on the dialog box.

7. If you want StorageX to log all types of audit events, click Select All.

8. Click OK when finished.

Viewing StorageX audit eventsOnce auditing settings are configured, Administrators can view StorageX audit events using either Windows Event Viewer on the StorageX server or in the Events panel of the StorageX Console.

Audit events are displayed as Information events, with the Category displayed as Auditing in both the Events panel and event log.

The steps below guide you through viewing StorageX audit events using the StorageX Console. For information about using Windows Event Viewer, see the Windows Event Viewer documentation.

To view StorageX audit events using the StorageX Console

1. Open the StorageX Console using an account that is a member of the Administrators role in StorageX.

NOTEUsers who are not Administrators cannot view or modify auditing settings unless the Allow non-Administrators to view the Security configuration setting is selected on the Access Control tab of the Options dialog box. For more information about configuring this setting, see “Configuring role-based access control” on page 46.

2. Click the Events view to see all events logged by StorageX.

3. Right-click the Category column and select Filter.

4. In the Filter Event Records dialog box, click Category and select Auditing.

5. Click OK. The Events view only displays StorageX audit events.

6. If you want to view all the details for a particular audit event, double-click the event in the Events view to open the Event Viewer dialog box. Click OK when finished.

StorageX Administrator’s Guide 49

Page 68: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring StorageX to use a custom certificate1

Configuring StorageX to use a custom certificateWhen you install StorageX, the setup program automatically creates and installs a default certificate that the StorageX server uses to make an SSL connection with the StorageX Console, the StorageX Metadata Service, the StorageX File Recovery Service, the Support Site Kit, and the StorageX API user interface.

The StorageX default certificate is stored in the Personal > Certificates folder in the certificate repository for the local StorageX server computer, and is configured to valid for 10 years, by default. In addition, the setup program automatically creates a new StorageX certification authority and adds the StorageX Certification Authority root certificate to the Trusted Root Certification Authorities store for the local StorageX server computer.

If you want to use a certificate other than the default certificate for one or more StorageX components, you can use the StorageX Certificate Tool to configure StorageX to use a certificate generated outside of the product. This may be necessary in certain environments, for security reasons. The certificate must be valid, must not have expired, and must be stored on the StorageX server in the location above.

ATTENTIONIf you configure StorageX to use a custom certificate for a component of the product, and the StorageX server cannot find a valid, unexpired certificate, the StorageX service cannot start and returns an error.

To configure StorageX to use a custom certificate

1. Log on to the StorageX server using a user account that is a member of the local Administrators group.

2. Install the custom certificate you want StorageX to use in the Windows certificate store on the server.

3. Navigate to the location of the SSLCertUpdate tool. By default, this file is located in the following folder:

C:\Program Files\Data Dynamics\StorageX\Tools\SSLCertTool

4. Right-click the SSLCertUpdate application and select Run as administrator, then click Yes to confirm.

5. In the Features list, select the component or components for which you want to use a custom certificate.

6. In the Certificate Path field, click Browse.

7. Select the SSL certificate you want to use and click Open.

8. Click Apply Certificate.

9. If you want to use a different custom certificate for another component, repeat step 5 through step 8 above.

10. When finished, click Close.

11. In Windows Administrative Tools, open Services and start the StorageX Server service.

50 StorageX Administrator’s Guide

Page 69: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Backing up the StorageX database 1

Backing up the StorageX databaseThe StorageX database stores configuration information for file storage resources managed by StorageX, configuration information for StorageX policies, configuration information for Migration Projects, and more.

Ensure you back up the StorageX database on a regular schedule to ensure minimal data loss if a resource failure or other critical event occurs. Also ensure you back up the StorageX database after you make configuration or policy changes in StorageX.

To back up the StorageX database

1. Stop all running policies and ensure no policies are scheduled to run in the future. For more information, see the following topics:

• “Canceling Phased Migration policies” on page 269 and “Viewing Phased Migration policies scheduled to run in the future” on page 292

• “Canceling Archival Migration policies” on page 298 and “Viewing Archival Migration policies scheduled to run in the future” on page 312

2. Close all StorageX Consoles.

3. In Windows Administrative Tools, open Services and stop the StorageX Server service.

4. Follow the steps in the following articles, available on the Microsoft Developer Network, that explain how to back up and restore Microsoft SQL Server databases:

• Back Up and Restore of SQL Server Databases, available at https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.

• Full Database Backups (SQL Server), available at https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/full-database-backups-sql-server.

For more information about the StorageX database, see “Understanding the StorageX database” on page 8.

Stopping and restarting the StorageX serverFrom time to time, you may need to shut down and then restart the StorageX server computer. For example, you may need to restart the StorageX server computer after you install patches or perform other required maintenance on the StorageX server computer.

Before you shut down the StorageX server computer, ensure you correctly stop and restart the StorageX server.

To stop and restart the StorageX server

1. Open the StorageX Console.

2. On the Tasks tab, which displays at the bottom of the StorageX Console, cancel any running policies by right-clicking each running policy, and then clicking Cancel.

3. For each policy that you canceled, verify that the policy was successfully canceled by completing the following steps:

StorageX Administrator’s Guide 51

Page 70: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Upgrading StorageX1

a. If the policy you canceled was a Phased Migration or Archival Migration policy created in the Data Movement view, click the Data Movement tab.

b. If StorageX generated the Phased Migration policy when you executed a Migration Project design, click the Migration Projects tab.

a. If the policy you canceled was a Disaster Recovery or Replication policy created in the Disaster Recovery view, click the Disaster Recovery tab.

a. If the policy you canceled was a Namespace Availability or Namespace Backup policy created in the Namespace Policies view, click the Namespace Policies tab.

b. In the left tree pane, under Policy Status, verify that Canceled displays in the Completion State field.

4. Check the Tasks tab once more and do a final confirmation that no policies are running.

5. On the Schedules tab, verify that no policies are scheduled to run in the next five minutes. You do not want any StorageX policies to start while you are shutting down and restarting the StorageX server computer.

6. Close the StorageX Console, and ensure no other copies of the StorageX Console installed on other computers are open.

7. In Windows Administrative Tools, open Services and stop the StorageX Server service.

8. Shut down the StorageX server computer, and then restart the StorageX server computer.

9. Open the StorageX Console after the StorageX server computer restarts.

10. Manually restart any policies as needed. For more information about restarting policies, see “Restarting Phased Migration policies” on page 269 and “Restarting Archival Migration policies” on page 298.

Upgrading StorageXYou can quickly and easily upgrade your existing StorageX 7.8 or later installation to a newer version of StorageX using the installation package for the new version of the product.

NOTES:

• When upgrading StorageX, you must upgrade both the StorageX server and StorageX Console to use the same version of the product.

• StorageX universal data engines must use the same version of the product or a newer revision of the same version of the product. For example, you could have a StorageX server that is running version 7.8.1 and a universal data engine that is running version 7.8.5.

This section provides information about upgrading StorageX, and includes the following topics:

• “Upgrading StorageX servers and databases” on page 53

• “Upgrading StorageX Console computers” on page 54

• “Upgrading StorageX universal data engines” on page 55

52 StorageX Administrator’s Guide

Page 71: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Upgrading StorageX 1

Upgrading StorageX servers and databasesWhen upgrading, you must upgrade each StorageX server and associated database first, followed by any StorageX Console computers. Once you upgrade part of your StorageX environment, you should upgrade all components to the new version of the product.

NOTEWhen you upgrade the StorageX server, the installation program automatically upgrades the StorageX database, even if the database is located on a different server.

To upgrade the StorageX server and database

1. Log on to the StorageX server you want to upgrade using a user account that is a member of the local Administrators group on the computer and that has access to the StorageX database.

2. Open the StorageX Console.

3. On the Tasks tab, which displays at the bottom of the StorageX Console, cancel any running policies by right-clicking each running policy, and then clicking Cancel.

4. Close the console.

5. On the server, browse to the location where you saved the new StorageX installation package.

6. Double-click the Setup.exe file.

7. If a User Account Control dialog box displays, click Yes to confirm that you want to run the StorageX installation package.

8. Click Release Notes to review the Release Notes and see what new features or improvements have been included in the new version of StorageX.

9. Click Install StorageX.

10. On the StorageX Setup Wizard Welcome dialog box, review the welcome message and then click Next.

11. On the Specify SSL Certificate dialog box, specify the certificate you want StorageX to use to make SSL connections. You can either specify that you want StorageX to use the default certificate installed with the product or use a custom certificate generated outside of StorageX. Complete the following steps:

a. If you want to use the default certificate, select Use self-signed certificate.

b. If you want to use a custom certificate, select Use the following certificate, then select the certificate you want to use from the list of certificates displayed.

NOTEThe custom certificate must be valid, must not have expired, and must be stored locally. If a certificate is not installed locally, the certificate will not be displayed in the list.

12. Click Upgrade.

13. When finished, click Finish to close the setup program.

14. Click Yes to restart your StorageX server immediately or click No if you want to restart the server at a later time. You must restart the server to finish the upgrade process.

StorageX Administrator’s Guide 53

Page 72: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Upgrading StorageX1

Upgrading StorageX Console computersAfter upgrading all of your StorageX servers, upgrade any stand-alone StorageX Console computers in your environment.

When upgrading, you must upgrade each StorageX server and associated database first, followed by any StorageX Console computers.

NOTEOnce you upgrade part of your StorageX environment, you should upgrade all components to the new version of the product.

To upgrade a StorageX Console computer

1. Log on to the StorageX Console computer you want to upgrade using a user account that is a member of the local Administrators group on the computer.

2. On the computer, browse to the location where you saved the new StorageX installation package.

3. Double-click the Setup.exe file.

4. If a User Account Control dialog box displays, click Yes to confirm that you want to run the StorageX installation package.

5. Click Install StorageX.

6. On the StorageX Setup Wizard Welcome dialog box, review the welcome message and then click Next.

7. On the Specify SSL Certificate dialog box, specify the certificate you want StorageX to use to make SSL connections. You can either specify that you want StorageX to use the default certificate installed with the product or use a custom certificate generated outside of StorageX. Complete the following steps:

a. If you want to use the default certificate, select Use self-signed certificate.

b. If you want to use a custom certificate, select Use the following certificate, then select the certificate you want to use from the list of certificates displayed.

NOTEThe custom certificate must be valid, must not have expired, and must be stored locally. If a certificate is not installed locally, the certificate will not be displayed in the list.

8. Click Upgrade.

9. When finished, click Finish to close the setup program.

10. If you want to add a StorageX license key, complete the following steps:

a. Open the StorageX Console.

b. Click Help > About Data Dynamics StorageX.

NOTEIf you want to use new functionality included in the upgraded version of StorageX, you may need to add a new license key. For more information about adding license keys, see “Updating license keys” on page 41.

54 StorageX Administrator’s Guide

Page 73: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Uninstalling StorageX 1

c. Click Edit License Keys and Notifications.

d. Click Add.

e. Click Browse for license file.

f. Browse to the new key and click Open.

g. Click OK.

h. Click Next.

i. Click Next again, then click Finish.

j. Click OK.

11. Verify you can access all necessary functionality in the StorageX Console.

Upgrading StorageX universal data enginesWhen upgrading your StorageX server and database, we recommend you also upgrade any universal data engines deployed in your environment. For more information about managing universal data engines, see “Managing universal data engines” on page 123.

You can only use StorageX to upgrade universal data engines deployed on Windows hosts, either automatically or manually. If you want to upgrade a universal data engine installed on a Linux host, you must manually uninstall the universal data engine and then install the new universal data engine on the Linux computer.

For information about uninstalling Linux data engines, see “Uninstalling Linux data engines” on page 58. For information about re-installing Linux data engines, see “Installing and configuring Linux data engines” on page 35.

To upgrade Windows data engines

1. Log on to the upgraded StorageX server.

2. In the StorageX Console, click the Control Panel tab.

3. In the left pane, click Deployed Data Engines.

4. In the right pane, right-click the universal data engine you want to upgrade and select Upgrade.

5. Repeat step 4 for each universal data engine in your environment.

Uninstalling StorageXThis section explains how to uninstall StorageX components. It includes the following topics:

• “Checklist: Uninstalling StorageX components” on page 56

• “Uninstalling universal data engines” on page 56

• “Removing universal data engines from the StorageX database” on page 58

• “Uninstalling the StorageX server and StorageX Consoles” on page 59

• “Deleting the StorageX database” on page 60

• “Deleting StorageX log files, cache files, and remaining program folders” on page 60

StorageX Administrator’s Guide 55

Page 74: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Uninstalling StorageX1

Checklist: Uninstalling StorageX componentsUse the following checklist when uninstalling StorageX components.

Uninstalling universal data enginesUninstall StorageX Windows and Linux data engines when you no longer want to use the universal data engine to migrate file data. For more information about uninstalling universal data engines, see the following topics:

• “Uninstalling Windows data engines using the StorageX Console” on page 56

• “Uninstalling Windows data engines using Windows Add or Remove Programs” on page 57

• “Uninstalling Linux data engines” on page 58

Uninstalling Windows data engines using the StorageX Console

You can uninstall Windows data engines using the StorageX Console. You can also uninstall Windows data engines using the Windows Add/Remove Programs feature.

This topic explains how to uninstall Windows data engines using the StorageX Console. For more information about uninstalling Windows data engines using the Windows Add/Remove Programs feature, see “Uninstalling Windows data engines using Windows Add or Remove Programs” on page 57.

Before you uninstall a Windows data engine, ensure you stop any policies that use the Windows data engine to migrate data. Also ensure no policies are scheduled to run using the Windows data engine in the future. For more information about how to perform these tasks, see the following topics:

• “Canceling Phased Migration policies” on page 269 and “Viewing Phased Migration policies scheduled to run in the future” on page 292

TABLE 12 Uninstalling StorageX checklist

Task

1 Cancel all running policies and ensure no policies are scheduled to run in the future. For more information, see the following topics:• “Canceling Phased Migration policies” on page 269 and “Viewing Phased Migration policies

scheduled to run in the future” on page 292• “Canceling Archival Migration policies” on page 298 and “Viewing Archival Migration policies

scheduled to run in the future” on page 312

2 Uninstall Windows and Linux data engines. For more information, see “Uninstalling universal data engines” on page 56.

3 Close all StorageX Consoles and LogViewer user interfaces.

4 Uninstall the StorageX server. For more information, see “Uninstalling the StorageX server and StorageX Consoles” on page 59.

5 Uninstall all StorageX Consoles. For more information, see “Uninstalling the StorageX server and StorageX Consoles” on page 59.

6 Delete the StorageX database. For more information, see “Deleting the StorageX database” on page 60.

7 Delete StorageX log files, cache files, and remaining program folders. For more information, see “Deleting StorageX log files, cache files, and remaining program folders” on page 60.

56 StorageX Administrator’s Guide

Page 75: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Uninstalling StorageX 1

• “Canceling Archival Migration policies” on page 298 and “Viewing Archival Migration policies scheduled to run in the future” on page 312

To uninstall a Windows data engine using the StorageX Console

1. In the StorageX Console, click the Control Panel tab.

2. In the left pane, click Deployed Data Engines.

3. In the center pane, right-click each universal data engine you want to uninstall and then click Uninstall.

4. If you want to uninstall the selected StorageX universal data engines using the same credentials used to deploy each of the selected data engines, click Uninstall using the same credentials that were used to deploy each of the selected data engines and then type the credentials.

5. If you want to specify the credentials you want StorageX to use to uninstall the selected StorageX universal data engines, click Uninstall the selected data engines using the following credentials. Select this option when the credentials used to run the universal data engine do not have the security permissions to uninstall the data engine.

6. Click OK.

7. Click the Alerts tab to verify that the universal data engine was uninstalled successfully.

8. In the Control Panel view, click Refresh to remove the universal data engine from the list of deployed data engines.

Uninstalling Windows data engines using Windows Add or Remove Programs

You can uninstall Windows data engines using the Windows Add/Remove Programs feature. You can also uninstall Windows data engines using StorageX Console.

This topic explains how to uninstall Windows data engines using the using the Windows Add/Remove Programs feature. For more information about uninstalling Windows data engines using the StorageX Console, see “Uninstalling Windows data engines using the StorageX Console” on page 56.

Before you uninstall a Windows data engine, ensure you stop any policies that use the Windows data engine to migrate data. Also ensure no policies are scheduled to run using the Windows data engine in the future. For more information about how to perform these tasks, see the following topics:

• “Canceling Phased Migration policies” on page 269 and “Viewing Phased Migration policies scheduled to run in the future” on page 292

• “Canceling Archival Migration policies” on page 298 and “Viewing Archival Migration policies scheduled to run in the future” on page 312

The user account used to uninstall the Windows data engine using the Add/Remove Programs feature must have Administrator permissions on the computer where the Windows data engine is installed.

To uninstall a Windows data engine using the Windows Add or Remove Programs feature

1. Connect to the computer where the Windows data engine is installed.

2. In the Windows Control Panel, open Add or Remove Programs.

StorageX Administrator’s Guide 57

Page 76: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Uninstalling StorageX1

3. Select StorageX Universal Data Engine, and then click Uninstall.

4. If a confirmation dialog box displays asking if you are sure you want to uninstall the StorageX universal data engine, click Yes.

StorageX uninstalls the Windows data engine.

5. After the uninstall completes, remove the Windows data engine from the StorageX database. The uninstalled Windows data engine will continue to display in the Control Panel view Deployed Data Engines list until you remove it from the StorageX database. For more information, see “Removing universal data engines from the StorageX database” on page 58.

Uninstalling Linux data engines

Uninstall a Linux data engine when you no longer want to use the Linux data engine to migrate file data.

Before you uninstall a Linux data engine, ensure you stop any policies that use the Linux data engine to migrate data. Also ensure no policies are scheduled to run using the Linux data engine in the future. For more information about how to perform these tasks, see the following topics:

• “Canceling Phased Migration policies” on page 269 and “Viewing Phased Migration policies scheduled to run in the future” on page 292

• “Canceling Archival Migration policies” on page 298 and “Viewing Archival Migration policies scheduled to run in the future” on page 312

The user account used to uninstall the Linux data engine must have root access permissions on the computer where the Linux data engine is installed.

To uninstall a Linux data engine

1. Connect to the Linux file storage resource where the Linux data engine you want to uninstall is installed.

2. Open a command prompt and sign in as an administrator with root access permissions.

3. Type rpm -e storagexra and then press Enter.

StorageX uninstalls the Linus data engine. If the Linux data engine is running, StorageX first stops the Linux data engine and then uninstalls the data engine.

4. Delete the /usr/local/URA directory.

For example, you can delete the /usr/local/URA directory using the following command:

rm -r -f /usr/local/URA5. Remove the Linux data engine from the StorageX database. The uninstalled Linux data engine

will continue to display in the Control Panel view Deployed Data Engines list until you remove it from the StorageX database. For more information, see “Removing universal data engines from the StorageX database” on page 58.

Removing universal data engines from the StorageX databaseYou can remove, or purge, a universal data engine from the StorageX database under the following conditions:

• You cannot uninstall a universal data engine because the computer on which the universal data engine was installed no longer exists or was renamed.

58 StorageX Administrator’s Guide

Page 77: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Uninstalling StorageX 1

• You uninstalled a Windows data engine using the Windows Add or Remove Programs feature. For more information, see “Uninstalling Windows data engines using Windows Add or Remove Programs” on page 57.

• A single Windows data engine is shared by two separate StorageX servers, and you want to remove the data engine from one server while leaving it running on the other. In this situation, ensure you purge the data engine only on the StorageX server that you no longer want to communicate with the data engine.

• You uninstalled a Linux data engine. For more information, see “Uninstalling Linux data engines” on page 58.

If you purge a universal data engine that has not already been uninstalled, that data engine remains installed and running on the computer where it was originally installed.

If you only want to uninstall a running Windows data engine that can communicate with the StorageX Console, we recommend you use the Uninstall option, instead. For more information, see “Uninstalling Windows data engines using the StorageX Console” on page 56.

To remove a universal data engine from the StorageX database

1. In the StorageX Console, click the Control Panel tab.

2. In the left pane, click Deployed Data Engines.

3. In the center pane, right-click the data engine you want to remove from the StorageX database and then click Purge.

4. Click Yes to confirm you want to purge the selected data engine.

The data engine is removed from the database and from the list of data engines.

5. Click Refresh and confirm that the universal data engine is no longer displayed in the list of deployed data engines.

Uninstalling the StorageX server and StorageX ConsolesThis section explains how to uninstall the StorageX server and StorageX Consoles.

To uninstall StorageX components

1. Log on to a computer where the StorageX server or a StorageX Console is installed.

2. Open Windows Control Panel.

3. Open Add or Remove Programs.

4. Select StorageX.

5. Click Uninstall.

6. Click Yes.

7. If a Windows User Account Control dialog box displays, click Yes to confirm you want to uninstall the StorageX component.

The StorageX program uninstalls all StorageX components on the computer.

StorageX Administrator’s Guide 59

Page 78: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Uninstalling StorageX1

Deleting the StorageX databaseAfter you uninstall StorageX components, delete the StorageX database.

This topic explains how to delete the StorageX database. For more information about uninstalling StorageX components, see “Checklist: Uninstalling StorageX components” on page 56.

To delete the StorageX database

1. Connect to the computer where you installed the StorageX database.

2. Use Microsoft SQL Server Management Studio to delete the iStorageX database.

For more information about how to use Microsoft SQL Server Management Studio to delete a SQL Server database, see Delete a Database at https://docs.microsoft.com/en-us/sql/relational-databases/databases/delete-a-database.

Deleting StorageX log files, cache files, and remaining program foldersAfter you uninstall StorageX components, manually delete StorageX log files, cache files, and remaining program folders as needed.

This topic explains how to delete StorageX log files, cache files, and remaining program folders. For more information about uninstalling StorageX components, see “Checklist: Uninstalling StorageX components” on page 56.

To delete StorageX log files, cache files, and remaining program folders

1. Connect to each computer where you installed a StorageX Windows data engine, and then complete the following steps:

a. Open Windows Explorer and browse to \ProgramData\Data Dynamics\StorageX\Logs and delete all of the log files in the Logs folder.

NOTEThe \ProgramData folder is a hidden Windows system folder. If you do not see the \ProgramData folder, ensure you have the Show hidden files, folders, and drives option enabled in Windows Explorer.

b. Browse to \ProgramData\Data Dynamics\StorageX\ReplicationAgent and delete the Windows data engine cache files.

c. Delete the \ProgramData\Data Dynamics folder.

d. Verify that the StorageX uninstallation program removed the \Program Files (x86)\Data Dynamics folder.

2. On each computer where you installed the StorageX server, complete the following steps:

a. Open Windows Explorer and browse to \ProgramData\Data Dynamics\StorageX\Logs, and delete all of the log files in the Logs folder.

NOTEThe \ProgramData folder is a hidden Windows system folder. If you do not see the \ProgramData folder, ensure you have the Show hidden files, folders, and drives option enabled in Windows Explorer.

60 StorageX Administrator’s Guide

Page 79: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Uninstalling StorageX 1

b. Browse to \ProgramData\Data Dynamics\StorageX\ReplicationAgent and delete the Windows data engine cache files.

c. Delete the \ProgramData\Data Dynamics folder.

d. Verify that the StorageX uninstallation program removed the \Program Files (x86)\Data Dynamics folder.

3. On each computer where you installed the StorageX Console, open Windows Explorer, browse to and then delete the \Users\UserName\AppData\Local\Data_Dynamics,_Inc folder, where UserName is the user name used when installing the StorageX Console using the StorageX Setup Wizard.

StorageX Administrator’s Guide 61

Page 80: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Uninstalling StorageX1

62 StorageX Administrator’s Guide

Page 81: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX Administrator’s Guide

Chapter

2

Configuring and Viewing Storage Resources

This section explains what the Storage Resources view is and how to add storage resources that you want to manage using StorageX to My Resources in the Storage Resources view. This section also explains how to configure and view heterogeneous storage resources in the Storage Resources view. Finally, this section explains how to manage your StorageX infrastructure, including configuring and managing StorageX universal data engines.

In this chapter•Checklist: Configuring storage resources and StorageX. . . . . . . . . . . . . . . . 64

•Understanding the Storage Resources view . . . . . . . . . . . . . . . . . . . . . . . . . 67

•Understanding storage resource validation checks . . . . . . . . . . . . . . . . . . . 70

•Verifying file storage resource DNS configuration . . . . . . . . . . . . . . . . . . . . 71

•Adding the StorageX server service account to file storage resources . . . . 71

•Configuring platform API access for file storage resources . . . . . . . . . . . . . 72

•Configuring default credentials for file storage resources . . . . . . . . . . . . . . 76

•Adding storage resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

•Configuring storage resources in My Resources. . . . . . . . . . . . . . . . . . . . . 100

•Configuring credentials for specific storage resources . . . . . . . . . . . . . . . 103

•Configuring virtual file storage resources . . . . . . . . . . . . . . . . . . . . . . . . . . 110

•Configuring the SNMP community name for file storage resources . . . . . 113

•Configuring NFS credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

•Configuring default administrative shares. . . . . . . . . . . . . . . . . . . . . . . . . . 114

•Configuring replication options for clustered file storage resources . . . . . 115

•Configuring intercluster interfaces for NetApp Cluster Mode file storage resources 116

•Verifying storage resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

•Specifying universal data engine settings on file storage resources. . . . . 118

•Viewing storage resource information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

•Removing storage resources from My Resources. . . . . . . . . . . . . . . . . . . . 122

•Exporting storage resource import lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

•Managing universal data engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

•Working with StorageX events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

•Configuring email notification profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

•Working with scheduled tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

63

Page 82: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Checklist: Configuring storage resources and StorageX2

Checklist: Configuring storage resources and StorageXUse the following checklist to help you configure storage resources and StorageX:

TABLE 13 Checklist: Configuring storage resources and StorageX

Task

1 Ensure you understand the Storage Resources view and how you can organize storage resources in the Storage Resources view. For more information, see “Understanding the Storage Resources view” on page 67.

2 If you want to use custom folders to organize your storage resources in the My Resources folder, create custom folders as needed. For more information, see “Understanding custom folders in the Storage Resources view” on page 69 and “Creating custom folders in the Storage Resources view” on page 70.

3 Verify file storage resource DNS configuration for each Windows, Linux, Data ONTAP, VNX OE for File, OneFS,and S3-compliant storage resource you want to manage using StorageX. Also verify the DNS configuration for each storage resource you want to include as either a source or destination in a Data Movement policy. For more information, see “Verifying file storage resource DNS configuration” on page 71.

4 Ensure the StorageX server service account has Administrator or root access permissions on each storage resource you want to manage with StorageX. For more information, see “Adding the StorageX server service account to file storage resources” on page 71.

5 If you have Data ONTAP, VNX OE for File, or OneFS file storage resources, configure API access for these file storage resources as needed. For more information, see “Configuring platform API access for file storage resources” on page 72.

6 If you have Data ONTAP, VNX OE for File, or OneFS file storage resources, configure default credentials for these resources for StorageX to use as needed. For more information, see “Configuring default credentials for file storage resources” on page 76.

7 If you have IBM Cloud Object Storage, StorageGRID, or S3-compliant object storage resources, configure credentials for these resources as needed. For more information, see “Configuring credentials for specific object storage resources” on page 109.

8 If you want StorageX to be able to perform the following tasks, first configure StorageX to use SSH shell credentials, and then configure default SSH shell credentials:• On VNX OE for File file storage resources, to migrate file data between VNX OE for File sources

and destinations using Migration Projects in the Migration Projects view.• On Linux file storage resources, create and clone NFS exports in the Storage Resources view, and

clone NFS exports as needed when creating Phased Migration policies in the Data Movement view.

• Update automount map files stored on NFS clients as needed when running Phased Migration policies in the Data Movement or Migration Projects views.

For more information, see the following topics:• “Configuring StorageX to Use SSH Shell Credentials” on page 433• “Configuring default SSH shell credentials” on page 79• “Configuring SSH shell credentials for specific file storage resources” on page 107• “Creating and managing NFS exports” on page 145• “How StorageX manages data access in NFS environments with automount map files” on

page 245

9 Add the Windows, Linux, Data ONTAP, VNX OE for File, and OneFS file storage resources you want to manage using StorageX to the My Resources folder or a custom folder under My Resources in the Storage Resources view. For more information, see “Understanding the Storage Resources view” on page 67 and “Adding storage resources” on page 80.

64 StorageX Administrator’s Guide

Page 83: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Checklist: Configuring storage resources and StorageX 2

After you have configured StorageX and each file storage resource as needed, you are now ready to perform the following tasks:

• View information about heterogeneous storage resources from a central management console. For more information, see “Viewing storage resource information” on page 121.

• Manage StorageX universal data engines as needed. For more information, see “Understanding StorageX universal data engines” on page 9 and “Managing universal data engines” on page 123.

• Provision heterogeneous file storage resources from a central management console.

For example, you can use StorageX to create and manage CIFS shared folders on Windows, Data ONTAP, VNX OE for File, and OneFS file storage resources that use the CIFS protocol. You can use StorageX to create and manage NFS exports on Linux, Data ONTAP, VNX OE for File, and OneFS file storage resources that use the NFS protocol. You can also use StorageX to create and manage Data ONTAP volumes, qtrees, and SnapMirrors on Data ONTAP file storage resources. For more information, see “Provisioning Storage Resources” on page 137.

• If you want to use DFS namespaces to manage data in your environment, create and manage DFS namespaces as needed. For more information, see “Creating and Managing DFS Namespaces” on page 159.

• If you want to back up or restore your DFS namespaces, or synchronize namespace structures to ensure high availability, create Namespace Backup and Namespace Availability policies. For more information, see “Backing up and restoring DFS namespaces” on page 220 and “Synchronizing DFS namespaces” on page 216.

• If you want to migrate file data stored in CIFS shared folders or NFS exports, create Data Movement policies, including Phased Migration and Archival Migration policies. For more information, see “Creating and Managing Data Movement Policies” on page 227.

10 Configure credentials for specific Linux, Data ONTAP, VNX OE for File, and OneFS file storage resources as needed. For more information, see “Configuring credentials for specific storage resources” on page 103.

11 Configure virtual file storage resources, such as Data ONTAP vFilers, Vservers, or SVMs and EMC VNX CIFS/NFS Servers or access zones, as needed. For more information, see “Configuring virtual file storage resources” on page 110.

12 If you have file storage resources, such as Data ONTAP file storage resources, that use SNMP and you have customized your SNMP community name, specify the appropriate SNMP community name for StorageX to use to communicate with each file storage resource. By default, StorageX uses public as the SNMP community name. For more information, see “Configuring the SNMP community name for file storage resources” on page 113.

13 If you have file storage resources that you want StorageX to manage that use the NFS protocol, configure NFS credentials on each file storage resource as appropriate. By default, StorageX uses 0 as the default user ID and group ID when communicating with file storage resources that use the NFS protocol. If you want StorageX to use a different default user ID and group ID, specify the appropriate user and group IDs for StorageX to use for each file storage resource.

14 Verify that the storage resources you added display correctly in My Resources. For more information, see “Verifying storage resources” on page 117.

15 StorageX uses universal data engines to transfer file data when running Phased Migration policies. Specify universal data engine settings on file storage resources as appropriate. For more information, see “Specifying universal data engine settings on file storage resources” on page 118.

TABLE 13 Checklist: Configuring storage resources and StorageX

Task

StorageX Administrator’s Guide 65

Page 84: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Checklist: Configuring storage resources and StorageX2

• If you want to migrate file data from source Data ONTAP file storage resources, volumes, and qtrees to destination Data ONTAP, VNX OE for File, or OneFS file storage resources, or if you want to migrate file data from source VNX OE for File file storage resources, file systems, volumes, or tree quotas to destination Data ONTAP or OneFS file storage resources, create Migration Projects. For more information, see “Creating and Managing Migration Projects” on page 319.

• If you want to migrate file data from source file storage resources to S3-compliant object storage resources, use the StorageX Management Portal to scan your resources, analyze your data, and create an Archive to move the data to the object store. For more information, see the StorageX Analysis, Archival, & Retrieval Guide.

• If you want to configure a disaster recovery plan for your environment or automatically replicate data from one resource to a backup resource, create Disaster Recovery or Replication policies. For more information, see “Creating and Managing Disaster Recovery and Replication Policies” on page 373.

66 StorageX Administrator’s Guide

Page 85: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding the Storage Resources view 2

Understanding the Storage Resources viewUse the Storage Resources view to view and manage file and object storage resources using StorageX.

The Storage Resources view provides both built-in and custom folders designed to help you easily view and organize storage resources managed by StorageX.

The following figure shows an example of the Storage Resources view.

For more information about the Storage Resources view, see the following topics:

• “Understanding the My Resources folder” on page 67

• “Understanding custom folders in the Storage Resources view” on page 69

• “Creating custom folders in the Storage Resources view” on page 70

• “Deleting custom folders in the Storage Resources view” on page 70

Understanding the My Resources folderStorageX provides a built-in My Resources folder in the Storage Resources view. The My Resources folder displays the storage resources you want to manage using StorageX, as well as the DFS namespaces that you can manage using StorageX.

StorageX Administrator’s Guide 67

Page 86: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding the Storage Resources view2

By default, the My Resources folder is empty when you first install StorageX. Add storage resources to the My Resources folder or a custom folder under the My Resources folder so you can begin managing storage resources using StorageX. You must add storage resources to the My Resources folder or a custom folder under My Resources before you can manage the resources using StorageX.

For example, add the following types of items to My Resources:

• Windows file storage resources

• Linux file storage resources

• Data ONTAP file storage resources

If you want to manage Data ONTAP 7 vFilers using StorageX, add both the vFiler virtual resource as well as the vFiler hosting resource to My Resources.

If you want to manage Data ONTAP 8 or ONTAP 9 Vservers or SVMs using StorageX, add both the Vserver or SVM virtual resource as well as the cluster that hosts the Vserver or SVM virtual resource to My Resources.

• VNX OE for File file storage resources

If you want to manage VNX OE for File Data Movers using StorageX, add both the Data Mover virtual resource as well as the Data Mover hosting resource to My Resources.

• OneFS file storage resources

If you want to manage Isilon access zones using StorageX, add both the access zone virtual resource as well as the access zone hosting resource to My Resources.

• IBM Cloud Object Storage (IBM COS) object storage resources

• NetApp StorageGRID object storage resources

• S3-compliant object storage resources

Once you add a storage resource to the My Resources folder, you can use StorageX to perform the following storage resource management tasks:

• Create and manage CIFS shared folders and NFS exports in the Storage Resources view. For more information, see “Creating and managing CIFS shared folders” on page 139 and “Creating and managing NFS exports” on page 145.

• Create and manage volumes, qtrees, and SnapMirrors on Data ONTAP file storage resources in the Storage Resources view. For more information, see “Creating and managing Data ONTAP volumes and qtrees” on page 149 and “Creating and managing Data ONTAP SnapMirrors” on page 152.

• Update automount map files stored on NFS clients when running Phased Migration policies in the Data Movement view or in the Migration Projects view. For more information, see “How StorageX manages data access in CIFS environments with DFS namespaces” on page 242 and “How StorageX manages data access in NFS environments with automount map files” on page 245.

• Include storage resources in My Resources as sources or destinations in Migration Projects in the Migration Projects view. For more information, see “Creating and Managing Migration Projects” on page 319.

• Scan and analyze file storage resources in My Resources using the StorageX Management Portal, and use the Portal to archive selected data to object storage resources in My Resources. For more information, see the StorageX Analysis, Archival, & Retrieval Guide.

68 StorageX Administrator’s Guide

Page 87: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding the Storage Resources view 2

You can add storage resources one at a time to My Resources, or you can add multiple storage resources at once using a storage resource import list. For more information about adding storage resources to the My Resources folder, see “Adding storage resources” on page 80.

If you simply want to use StorageX to migrate data from existing source CIFS shared folders or NFS exports to existing destination CIFS shared folders or NFS exports, and the file storage resource is not a Data ONTAP, VNX OE for File, or OneFS file storage resource, you do not have to add the file storage resources to My Resources folder.

However, you do need to add file storage resources to My Resources if the file storage resources are Data ONTAP, VNX OE for File, or OneFS file storage resources, or if you want to perform other file storage resource management tasks using StorageX such as creating and managing CIFS shared folders and NFS exports and creating and managing Data ONTAP volumes, qtrees, and SnapMirrors.

In addition, if you specify an entire file storage resource as your source and destination, StorageX can create destinations on the destination file storage resource if the destination does not already exist. However, the file storage resource that is the destination where you want to create CIFS shared folders or NFS exports must be added to the My Resources folder in the Storage Resources view. If you have not added the destination file storage resource to the My Resources folder in the Storage Resources view, StorageX will not be able to create CIFS shared folders or NFS exports on the destination. For more information about adding a file storage resource to My Resources, see “Understanding the Storage Resources view” on page 67 and “Adding storage resources” on page 80.

If you want StorageX to update automount map files stored on NFS clients as needed when creating and running Phased Migration policies in the Data Movement or Migration Projects view, you must add each NFS client with the automount map file you want the policy to update to My Resources.

You also must add any file storage resources you want to include as sources or destination in Migration Projects to My Resources. For more information, see “Creating and Managing Migration Projects” on page 319 and “Adding sources and destinations to Migration Projects” on page 334.

If you use DFS namespaces in your environment, you can also create new DFS namespaces or add existing DFS namespaces in My Resources. This allows you to use StorageX as a central console to manage all of the file storage resources and DFS namespaces in your environment. For more information about creating DFS namespaces in My Resources or adding existing DFS namespaces to My Resources, see “Creating and Managing DFS Namespaces” on page 159 and “Adding DFS namespaces to My Resources” on page 186.

In addition to using the built-in My Resources folder in the Storage Resources view, you can also create custom folders in the Storage Resources view to help you better organize and manage your storage resources. For more information, see “Understanding custom folders in the Storage Resources view” on page 69 and “Creating custom folders in the Storage Resources view” on page 70.

Understanding custom folders in the Storage Resources viewIn addition to the built-in My Resources folder StorageX provides in the Storage Resources view, you can create your own custom folders under My Resources to help you logically group and organize storage resources managed by StorageX. For example, you can create custom folders based on company departments, geographic locations, or cost centers.

StorageX Administrator’s Guide 69

Page 88: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding storage resource validation checks2

You can also add a storage resource to more than one custom folder. For example, you can add a storage resource to more than one custom folder if you want to add a storage resource to a folder that indicates its business function, as well as to another folder that indicates its physical location or platform type.

For more information about custom folders, see the following topics:

• “Creating custom folders in the Storage Resources view” on page 70

• “Deleting custom folders in the Storage Resources view” on page 70

Creating custom folders in the Storage Resources viewYou can create custom folders in the Storage Resources view to help you logically group and organize the storage resources you manage with StorageX.

To create a custom folder in the Storage Resources view

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, under Storage Resources > My Resources, right-click the My Resources folder, and then click Add Folder.

3. Type a name for the custom folder you want to create.

StorageX creates the new custom folder and displays the new folder in the left tree pane under My Resources.

For more information about custom folders, see the following topics:

• “Understanding custom folders in the Storage Resources view” on page 69

• “Deleting custom folders in the Storage Resources view” on page 70

Deleting custom folders in the Storage Resources viewDelete custom folders from the Storage Resources view when you no longer want to use the custom folder to organize storage resources in the Storage Resources view.

To delete a custom folder in the Storage Resources view

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under Storage Resources > My Resources, right-click the custom folder that you want to delete, and then click Delete.

For more information about custom folders, see the following topics:

• “Understanding custom folders in the Storage Resources view” on page 69

• “Creating custom folders in the Storage Resources view” on page 70

Understanding storage resource validation checksWhen you add or import a new storage resource to the My Resources folder in the Storage Resources view, StorageX automatically runs a series of validation checks to determine whether the storage resource is accessible, is properly configured, and can be managed by StorageX.

70 StorageX Administrator’s Guide

Page 89: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying file storage resource DNS configuration 2

After StorageX finishes running validation checks on your resources, the File Storage Resources and Object Storage Resources tabs of the center pane in the Storage Resources view each display a grid listing your managed resources, with an icon indicating the status of each resource:

• The Not Validated icon ( ) indicates that StorageX needs to validate the storage resource.

• The Failed icon ( ) indicates that StorageX could not validate the resource.

• The Warning icon ( ) indicates that the resource passed most validation checks, but that StorageX could not fully validate the resource.

• The Validated icon ( ) indicates that StorageX successfully validated the resource.

You can click on a specific resource and view detailed information about all checks run and any issues that need to be resolved for that resource in the Validation results and Validation details panes. This allows you to more easily address issues with your managed resources. Data Dynamics recommends you resolve any validation issues with your resources before attempting to run StorageX policies using those resources.

If you want to re-run validation checks on all your managed resources, right-click My Resources in the tree view and select Refresh.

NOTEMost validation checks are tailored for the platform type specified when you added the resource. Therefore, if you specified the incorrect platform type for a particular resource, that resource may fail one or more resource checks.

Verifying file storage resource DNS configurationBefore you add file storage resources to the My Resources folder in the Storage Resources view or include a file storage resource as a source or destination in a Data Movement policy, verify the file storage resource DNS configuration.

StorageX uses reverse DNS lookups to verify that StorageX is communicating with the correct file storage resource.

Verify file storage resource DNS configuration by performing an nslookup by file storage resource name and by IP address to ensure that your DNS is configured correctly.

When you perform an nslookup by file storage resource name and then by IP address, verify that your results are the same. If your results are different, contact your DNS administrator to resolve any DNS issues as appropriate before you add the file storage resource to the My Resources folder in the Storage Resources view or include a file storage resource as a source or destination in a Data Movement policy.

Adding the StorageX server service account to file storage resourcesThe StorageX server service account is an account used by the StorageX server service to communicate with and manage file storage resources.

NOTEStorageX does not use the StorageX server service account to communicate with object storage resources. To use object storage resources in StorageX, you must configure the specific credentials for each object storage resource.

StorageX Administrator’s Guide 71

Page 90: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring platform API access for file storage resources2

Add the StorageX server service account to each file storage resource that you want to manage using StorageX, and ensure the StorageX server service account has Administrator or root access permissions on each file storage resource. This ensures that the StorageX server has the permissions needed for StorageX to manage file storage resources.

If the file storage resource is a Windows, Data ONTAP, or VNX OE for File file storage resource, add the StorageX server service account to each Windows, Data ONTAP, or VNX OE for File file storage resource you want to manage using StorageX and ensure the StorageX server service account has Administrator permissions on each resource.

NOTEIf the file storage resource is a Windows file storage resource but the StorageX server service account does not have Administrator permissions on the resource, in the Reporting view, the Shares report will not display information about the shares on the resource. In StorageX reporting, the StorageX server service account must have Administrator permissions on Windows file storage resources in order to obtain and display property information about CIFS shared folders on Windows file storage resources. For more information about StorageX storage resource reports and the Shares report, see “Understanding Storage Resource reports” on page 422.

If the file storage resource is a OneFS file storage resource, add the StorageX server service account to each OneFS file storage resource you want to manage using StorageX and ensure the StorageX server service account has Local Administrator permissions on each resource. In addition, the service account used to run the universal data engine must be given Run As Root access on each share on each resource in order to be able to access the share.

If the file storage resource is a Linux file storage resource, add the StorageX server service account to each Linux file storage resource you want to manage using StorageX and ensure the StorageX server service account has root access permissions on each resource.

For more information about the StorageX server service account, including service account requirements, see “StorageX server service account requirements” on page 16.

Configuring platform API access for file storage resourcesIf you want StorageX to manage Data ONTAP, VNX OE for File, or OneFS file storage resources, ensure you configure platform API access as needed on each file storage resource.

Platform API access must be configured correctly on each file storage resource in order for StorageX to use the appropriate Data ONTAP, VNX OE for File, or OneFS platform APIs to manage the file storage resource.

For more information about enabling platform API access on Data ONTAP, VNX OE for File, or OneFS file storage resources, see the following topics:

• “Enabling platform API access on Data ONTAP file storage resources” on page 72

• “Enabling platform API access on VNX OE for File file storage resources” on page 75

• “Enabling platform API access on OneFS file storage resources” on page 75

Enabling platform API access on Data ONTAP file storage resourcesIf you want StorageX to manage Data ONTAP file storage resources, ensure platform API access is enabled on each Data ONTAP file storage resource by configuring StorageX to use the appropriate protocol to communicate with the file storage resource.

72 StorageX Administrator’s Guide

Page 91: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring platform API access for file storage resources 2

NOTEOn Data ONTAP 8.2 Cluster Mode, Data ONTAP 8.3 Cluster Mode, ONTAP 9, or ONTAP 9.1 file storage resources, platform API access is enabled by default, including the default certificate authority and a temporary certificate.

If the file storage resource is a Data ONTAP 7 file storage resource or a Data ONTAP 8 7-Mode file storage resource, consider the following points:

• Typically, new Data ONTAP 7 file storage resources and Data ONTAP 8 7-Mode file storage resources right out of the box do not have a CIFS server configured. RPC is enabled but not configured, and HTTP and HTTPS are not enabled.

• If you configure a CIFS server on a Data ONTAP 7 or Data ONTAP 8 7-Mode file storage resource and then add the resource to the domain, RPC is automatically configured, and StorageX can use RPC to communicate with the resource.

• If you do not want StorageX to use RPC to communicate with a Data ONTAP 7 or Data ONTAP 8 7-Mode file storage resource, you can specify that you want StorageX to use HTTP or HTTPS to communicate with the resource.

• If you want StorageX to use HTTP or HTTPS to communicate with the resource, you must enable HTTP or HTTPS on the resource. On Data ONTAP 7 and Data ONTAP 8 7-Mode file storage resources, HTTP daemon options are not enabled by default.

• If you want StorageX to use HTTP to communicate with a Data ONTAP file storage resource, you must manually enable HTTP access using the options httpd.admin.enable command.

• If you want StorageX to use HTTPS to communicate with a Data ONTAP file storage resource, in addition to enabling HTTP, you must also manually enable HTTPS access using the options httpd.admin.ssl.enable command.

• If you do not configure a CIFS server on a Data ONTAP 7 or Data ONTAP 8 7-Mode file storage resource, you must enable HTTP or HTTPS on the resource before StorageX can communicate with the resource. For example, if the file storage resource is an NFS-only resource, you must enable either HTTP or HTTPS on the file storage resource before StorageX can communicate with the resource using HTTP or HTTPS.

• If you want StorageX to use HTTP to communicate with a Data ONTAP file storage resource, you must manually enable HTTP access using the options httpd.admin.enable command.

• If you want StorageX to use HTTPS to communicate with a Data ONTAP file storage resource, in addition to enabling HTTP, you must also manually enable HTTPS access using the options httpd.admin.ssl.enable command.

For more information about how to enable HTTP or HTTPS or for more information about how to configure a CIFS server on a Data ONTAP 7 or Data ONTAP 8 7-Mode file storage resources, see the Data ONTAP documentation.

If the file storage resource is a Data ONTAP 7 vFiler, consider the following points:

• When you create the vFiler, RPC settings are automatically configured when you configure a CIFS server and add the resource to the domain. If a CIFS server is enabled on the vFiler and the vFiler has been added to the domain, StorageX can use RPC to communicate with the file storage resource.

• If you want StorageX to use HTTP or HTTPS to communicate with the vFiler, you must enable HTTP or HTTPS on the hosting resource. HTTP or HTTPS settings are inherited from the vFiler hosting resource.

StorageX Administrator’s Guide 73

Page 92: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring platform API access for file storage resources2

• If you want StorageX to use HTTP to communicate with a Data ONTAP file storage resource, you must manually enable HTTP access using the options httpd.admin.enable command.

• If you want StorageX to use HTTPS to communicate with a Data ONTAP file storage resource, in addition to enabling HTTP, you must also manually enable HTTPS access using the options httpd.admin.ssl.enable command.

If the file storage resource is a Data ONTAP 8.2 Cluster Mode, Data ONTAP 8.3 Cluster Mode, ONTAP 9, or ONTAP 9.1 file storage resource, consider the following points:

• RPC is not supported on Data ONTAP 8.2 Cluster Mode, Data ONTAP 8.3 Cluster Mode, ONTAP 9, or ONTAP 9.1 file storage resources. HTTP or HTTPS must be enabled on the file storage resource in order for StorageX to communicate with Data ONTAP Cluster Mode file storage resources. On Data ONTAP 8.2, Data ONTAP 8.3, ONTAP 9, and ONTAP 9.1 file storage resources, HTTP and HTTPS daemon options are enabled by default.

• If you encounter issues when StorageX uses HTTP to communicate with a Data ONTAP 8.2 file storage resource, manually enable HTTP access using the options httpd.admin.enable command. For more information about platform API access on Data ONTAP file storage resources, see the Data ONTAP API documentation.

• If you encounter issues when StorageX uses HTTP to communicate with a Data ONTAP 8.3, ONTAP 9, or ONTAP 9.1 file storage resource, manually enable HTTP access using the vserver services web modify -enabled true command. For more information about platform API access on Data ONTAP file storage resources, see the Data ONTAP API documentation.

• If you encounter issues when StorageX uses HTTPS to communicate with a Data ONTAP 8.2 file storage resource, in addition to enabling HTTP, you must also manually enable HTTPS access using the options httpd.admin.ssl.enable command. For more information about platform API access on Data ONTAP file storage resources, see the Data ONTAP API documentation.

• If you encounter issues when StorageX uses HTTPS to communicate with a Data ONTAP 8.3, ONTAP 9, or ONTAP 9.1 file storage resource, in addition to enabling HTTP, you must also manually enable HTTPS access using the security ssl command. For more information about platform API access on Data ONTAP file storage resources, see the Data ONTAP API documentation.

• There may be firewall policies on Data ONTAP 8.2 Cluster Mode, Data ONTAP 8.3 Cluster Mode, ONTAP 9, or ONTAP 9.1 file storage resources that block HTTP or HTTPS access. If a firewall policy is blocking HTTP or HTTPS access, you must modify the firewall policies to allow StorageX to connect with the file storage resource.

• Data ONTAP 8.2 Cluster Mode, Data ONTAP 8.3 Cluster Mode, ONTAP 9, or ONTAP 9.1 file storage resources may be configured to block the ontapi service on their cluster, cluster node, Vserver, or SVM. By default, the ontapi service is enabled. However, if the ontapi service has been disabled on any level (cluster, cluster node, Vserver, or SVM), you must enable the ontapi service again before StorageX can communicate with the resource.

If the file storage resource is a Data ONTAP 8 Vserver or SVM, consider the following points:

• When you create the Vserver or SVM, RPC settings are automatically configured when you configure a CIFS server and add the resource to the domain. If a CIFS server is enabled on the Vserver or SVM and the Vserver or SVM has been added to the domain, StorageX can use RPC to communicate with the file storage resource.

74 StorageX Administrator’s Guide

Page 93: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring platform API access for file storage resources 2

• If you want StorageX to use HTTP or HTTPS to communicate with a Data ONTAP 8 Vserver or SVM, ensure that HTTP or HTTPS is configured on the Vserver or SVM hosting resource. Data ONTAP 8 or ONTAP 9 Vservers or SVM inherit HTTP and HTTPS settings from the hosting resource.

• If you want StorageX to use HTTP to communicate with a Data ONTAP file storage resource, you must manually enable HTTP access using the options httpd.admin.enable command.

• If you want StorageX to use HTTPS to communicate with a Data ONTAP file storage resource, in addition to enabling HTTP, you must also manually enable HTTPS access using the options httpd.admin.ssl.enable command.

For more information about enabling RPC, HTTP, and HTTPS access on Data ONTAP file storage resources, see the Data ONTAP API documentation.

Enabling platform API access on VNX OE for File file storage resourcesIf you want StorageX to manage VNX OE for File file storage resources, ensure platform API access is enabled on each VNX OE for File file storage resource as needed.

By default, the VNX XML API daemon is disabled on VNX OE for File file storage resources. You must manually enable the VNX XML API daemon on each VNX OE for File file storage resource before StorageX can manage the VNX OE for File file storage resource

To start the VNX XML API daemon

1. As root user, use a text editor to uncomment the following entry in /nas/sys/nas_mcd.cfg:

daemon "XML API Server" executable "/nas/sbin/start_xml_api_server" optional yes canexit yes autorestart yes ioaccess no

2. Restart nas services with the following command:

# service nas start

The VNX XML API starts and is now controlled by the master control daemon.

For more information about enabling platform API access on VNX OE for File file storage resources, see the VNX OE for File API documentation.

Enabling platform API access on OneFS file storage resourcesIf you want StorageX to manage OneFS file storage resources, platform API access is enabled by default. No additional configuration is required for OneFS file storage resources.

For more information about platform API access on OneFS file storage resources, see the OneFS API documentation.

StorageX Administrator’s Guide 75

Page 94: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring default credentials for file storage resources2

Configuring default credentials for file storage resourcesYou can configure the following types of default credentials for StorageX to use when managing file storage resources:

• Default Data ONTAP credentials for StorageX to use to manage Data ONTAP file storage resources. For more information, see “Configuring default Data ONTAP credentials” on page 76.

• Default VNX OE for File credentials for StorageX to use to manage VNX OE for File file storage resources. For more information, see “Configuring default VNX OE for File credentials” on page 78.

• Default OneFS credentials for StorageX to use to manage OneFS file storage resources. For more information, see “Configuring default OneFS credentials” on page 78.

• If you want to use StorageX to migrate file data between VNX OE for File sources and destinations using Migration Projects, to create or clone NFS exports on Linux file storage resources, or to update automount map files on NFS clients when running Phased Migration policies, specify default SSH shell credentials for StorageX to use to use when managing these resources. For more information, see “Configuring default SSH shell credentials” on page 79.

When you configure default credentials, StorageX uses the default credentials to communicate with the file storage resources that are configured to accept the default credentials.

NOTEStorageX does not currently allow you to use a default set of credentials for object storage resources in your environment, because the credentials will typically be different for each object storage resource.

You can also specify specific credentials for StorageX to use with individual file storage resources that are different than the default credentials as needed. For more information, see “Configuring credentials for specific storage resources” on page 103.

Configuring default Data ONTAP credentialsStorageX uses the StorageX server service account to communicate with Data ONTAP file storage resources. StorageX also uses either default or specific Data ONTAP credentials you configure to manage Data ONTAP file storage resources.

When you specify default credentials for StorageX to use with Data ONTAP file storage resources, StorageX uses these credentials by default to manage Data ONTAP resources when you add them to My Resources.

This topic explains how to specify default Data ONTAP credentials for StorageX to use when managing Data ONTAP file storage resources.

For more information about the StorageX server service account, see “StorageX server service account requirements” on page 16. For more information about configuring specific Data ONTAP credentials for StorageX to use to manage specific Data ONTAP file storage resources, see “Configuring default Data ONTAP credentials” on page 76.

You can specify credentials for the following connection types for Data ONTAP file storage resources:

• RPC

• HTTP

76 StorageX Administrator’s Guide

Page 95: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring default credentials for file storage resources 2

• HTTPS

The protocol and credentials you specify for StorageX to use should be based on how you enabled platform API access for your Data ONTAP file storage resources. For more information about enabling platform API access for Data ONTAP file storage resources, see “Enabling platform API access on Data ONTAP file storage resources” on page 72.

If you have Data ONTAP 8.2 Cluster Mode, Data ONTAP 8.3 Cluster Mode, ONTAP 9, or ONTAP 9.1 file storage resources in your environment, StorageX cannot use the StorageX server service account or default Data ONTAP credentials to communicate with these resources. Data ONTAP Cluster Mode does not accept any Windows Active Directory service account, including the StorageX server service account. For these resources, you must specify an account with Administrator permissions that StorageX can use to communicate individually for each file storage resource running Data ONTAP 8.2 Cluster Mode, Data ONTAP 8.3 Cluster Mode, ONTAP 9, or ONTAP 9.1. For more information, see “Configuring credentials for specific Data ONTAP file storage resources” on page 104.

To configure default Data ONTAP credentials

1. Ensure platform API access has been enabled on the Data ONTAP file storage resource as needed to allow StorageX to communicate with the file storage resource using the appropriate protocol. For more information, see “Enabling platform API access on Data ONTAP file storage resources” on page 72.

2. In the StorageX Console, on the File menu, click Options.

3. Click the NetApp Credentials tab.

4. If you want StorageX to use the RPC protocol to communicate with Data ONTAP file storage resources, in the Connection Type field, select RPC from the drop-down list.

In order for StorageX to use RPC to communicate with Data ONTAP file storage resources, a CIFS server must be configured on the resource and the resource must be joined to the domain. For example, you may want to use RPC to communicate with a Data ONTAP file storage resource if the file storage resource is running the Data ONTAP 8 operating system in 7-Mode, a CIFS server has been configured on the resource, the resource has been joined to the domain, and HTTP is disabled on the file storage resource.

5. If you want StorageX to use the HTTP protocol to communicate with Data ONTAP file storage resources, in the Connection Type field, select HTTP from the drop-down list. HTTP must be enabled on the file storage resource in order for StorageX to use HTTP to communicate with the resource.

6. If you want StorageX to use the HTTPS protocol to communicate with Data ONTAP file storage resources, in the Connection Type field, select HTTPS from the drop-down list. In order for StorageX to use HTTPS to communicate with the resource, both SSL and HTTP must be enabled on the file storage resource.

7. In the Username field, type name the name of a user account with Administrator permissions on the Data ONTAP file storage resources you want StorageX to manage.

8. In the Password field, type the password for the user account.

9. Click OK.

StorageX Administrator’s Guide 77

Page 96: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring default credentials for file storage resources2

Once you have specified default Data ONTAP credentials for StorageX to use when communicating with Data ONTAP file storage resources, you can configure credentials other than the default credentials for StorageX to use to communicate with specific Data ONTAP file storage resources. For more information, see “Configuring credentials for specific Data ONTAP file storage resources” on page 104.

Configuring default VNX OE for File credentialsStorageX uses the StorageX server service account to communicate with VNX OE for File file storage resources. StorageX also uses either default or specific VNX OE for File credentials you configure to manage VNX OE for File file storage resources.

When you specify default credentials for StorageX to use with VNX OE for File file storage resources, StorageX uses these credentials by default to manage VNX OE for File resources when you add them to My Resources.

This topic explains how to specify default VNX OE for File credentials for StorageX to use when managing VNX OE for File file storage resources.

For more information about the StorageX server service account, see “StorageX server service account requirements” on page 16. For more information about configuring specific VNX OE for File credentials for StorageX to use to manage specific VNX OE for File file storage resources, see “Configuring default VNX OE for File credentials” on page 78.

To configure default VNX OE for File credentials

1. Ensure platform API access has been enabled on the VNX OE for File file storage resource as needed to allow StorageX to communicate with the file storage resource. For more information, see “Enabling platform API access on VNX OE for File file storage resources” on page 75.

2. In the StorageX Console, on the File menu, click Options.

3. Click the VNX Credentials tab.

4. In the Username field, type name the name of a user account with Administrator permissions on the VNX OE for File file storage resources you want StorageX to manage.

5. In the Password field, type the password for the user account.

6. Click OK.

Once you have specified default VNX OE for File credentials for StorageX to use when communicating with VNX OE for File file storage resources, you can configure credentials other than the default credentials for StorageX to use to communicate with specific VNX OE for File file storage resources. For more information, see to “Configuring credentials for specific VNX OE for File file storage resources” on page 105.

Configuring default OneFS credentialsStorageX uses the StorageX server service account to communicate with OneFS file storage resources. StorageX also uses either default or specific OneFS credentials you configure to manage OneFS file storage resources.

When you specify default credentials for StorageX to use with OneFS file storage resources, StorageX uses these credentials by default to manage OneFS resources when you add them to My Resources.

78 StorageX Administrator’s Guide

Page 97: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring default credentials for file storage resources 2

This topic explains how to specify default OneFS credentials for StorageX to use when managing OneFS file storage resources.

For more information about the StorageX server service account, see “StorageX server service account requirements” on page 16. For more information about configuring specific OneFS credentials for StorageX to use to manage specific OneFS file storage resources, see “Configuring credentials for specific OneFS file storage resources” on page 106.

To configure default OneFS credentials

1. Ensure platform API access has been enabled on the OneFS file storage resource as needed to allow StorageX to communicate with the file storage resource. For more information, see “Enabling platform API access on OneFS file storage resources” on page 75.

2. In the StorageX Console, on the File menu, click Options.

3. Click the Isilon Credentials tab.

4. In the Username field, type the name of a user account with root access permissions on the OneFS file storage resources you want StorageX to manage.

5. In the Password field, type the password for the user account.

6. Click OK.

Once you have specified default OneFS credentials for StorageX to use when communicating with OneFS file storage resources, you can configure credentials other than the default credentials for StorageX to use to communicate with specific OneFS file storage resources. For more information, see “Configuring credentials for specific OneFS file storage resources” on page 106.

Configuring default SSH shell credentials If you want to use StorageX to migrate file data between VNX OE for File sources and destinations using Migration Projects, to create or clone NFS exports on Linux file storage resources, or to update automount map files stored on NFS clients when running Phased Migration policies, configure StorageX to use SSH shell credentials. For more information about how to configure StorageX to use SSH shell commands, see “Configuring StorageX to Use SSH Shell Credentials” on page 433.

After you have configured StorageX to use SSH shell credentials, next configure StorageX to use either default or specific SSH shell credentials to manage the resources. When you configure default SSH shell credentials, StorageX uses these credentials by default each time you add a new VNX OE for File file storage resource, Linux file storage resource or NFS client to manage the resource.

NOTEIf you want StorageX to use SSH shell credentials to manage VNX OE for File file storage resources, all managed VNX resources must use the built-in nasadmin account.

To configure default SSH shell credentials

1. In the StorageX Console, on the File menu, click Options.

2. Click the SSH Options tab.

3. If you want to use a user name and password for SSH, complete the following steps:

StorageX Administrator’s Guide 79

Page 98: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources2

a. In the User name field, type the name of the user account for StorageX to use when communicating with VNX OE for File file storage resources that are sources and destinations in Migration Projects, when communicating with Linux file storage resources where you want to create and clone NFS exports, or when communicating with NFS clients that store automount map files that you want StorageX to update when running Phased Migration policies. Typically this is root.

b. In the User password field, type the password for the user account you specified in the previous field.

4. If you want to use an SSH private key, complete the following steps:

a. In the User name field, type the name of the user account for StorageX to use when communicating with VNX OE for File file storage resources that are sources and destinations in Migration Projects, when communicating with Linux file storage resources where you want to create and clone NFS exports, or when communicating with NFS clients that store automount map files that you want StorageX to update when running Phased Migration policies. Typically this is root.

b. In the Private key file path field, type the UNC path to the location of the SSH private key, either locally or on a remote computer, or click the ellipsis (...) button to browse to and select the SSH private key on the StorageX server computer.

NOTEThe specified private key must be in OpenSSH format. For more information about creating or converting private keys, see “Configuring StorageX to Use SSH Shell Credentials” on page 433.

c. If you specified a passphrase when creating the private key, in the Private key passphrase field, type the passphrase for the private key.

5. Click OK.

Once you have specified default SSH shell credentials for StorageX to use, you can configure SSH shell credentials other than the default SSH shell credentials for StorageX to use to manage specific VNX OE for File sources and destinations included in Migration Projects, to manage Linux file storage resources where you want to create or clone NFS exports, or to manage specific NFS clients where you want to update automount map files. For more information, see “Configuring SSH shell credentials for specific file storage resources” on page 107.

Adding storage resourcesIn order to manage storage resources using StorageX, you must add your storage resources to the My Resources folder or a custom folder under My Resources in the Storage Resources view and configure StorageX to communicate with those resources.

Add the Windows, Linux, Data ONTAP, VNX OE for File, and OneFS file storage resources and the IBM COS, StorageGRID, and S3-compliant object storage resources you want to manage using StorageX to the My Resources folder or a custom folder under My Resources in the Storage Resources view.

For example, add the following types of items to My Resources:

• Windows file storage resources

• Linux file storage resources

80 StorageX Administrator’s Guide

Page 99: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources 2

• Data ONTAP file storage resources

If you want to manage Data ONTAP vFilers using StorageX, add both the vFiler virtual resource, as well as the vFiler hosting resource to My Resources.

If you want to manage Data ONTAP Vservers or Storage Virtual Machines (SVMs) using StorageX, add both the Vserver or SVM virtual resource, as well as the cluster name that hosts the Vserver or SVM virtual resource to My Resources.

NOTEStorageX does not support managing Data ONTAP Vservers or SVMs with Infinite Volumes. For more information about managing Infinite Volumes, see the NetApp documentation.

• VNX OE for File file storage resources

If you want to manage VNX OE for File Data Movers using StorageX, add both the EMC VNX CIFS/NFS Server virtual resource and the EMC VNX hosting resource to My Resources.

NOTEStorageX does not support adding VNXe file storage resources as sources or destinations in Phased Migration policies created by Migration Projects in the Migration Projects view. You also cannot add VNXe file storage resources to the My Resources folder in the Storage Resources view and have StorageX manage the resource.

• OneFS file storage resources

If you want to manage Isilon access zones using StorageX, add both the Isilon access zone virtual resource and the Isilon access zone hosting resource to My Resources.

• Generic CIFS, NFS, or CIFS/NFS file storage resources

• IBM COS object storage resources

• StorageGRID object storage resources

• S3-compliant object storage resources

If you simply want to use StorageX to migrate file data from existing source CIFS shared folders or NFS exports to existing destination CIFS shared folders or NFS exports and the file storage resource is not a Data ONTAP, VNX OE for File, or OneFS file storage resource, you do not have to add the file storage resources to My Resources folder.

However, you do need to add file storage resources to My Resources if the file storage resources are Data ONTAP, VNX OE for File, or OneFS file storage resources, or if you want to perform other file storage resource management tasks using StorageX such as creating and managing CIFS shared folders and NFS exports and creating and managing Data ONTAP volumes, qtrees, and SnapMirrors.

In addition, if you specify an entire file storage resource as your source and destination, StorageX can create destinations on the destination file storage resource if the destination does not already exist. However, the file storage resource that is the destination where you want to create CIFS shared folders or NFS exports must be added to the My Resources folder in the Storage Resources view. If you have not added the destination file storage resource to the My Resources folder in the Storage Resources view, StorageX will not be able to create CIFS shared folders or NFS exports on the destination. For more information about adding a file storage resource to My Resources, see “Understanding the Storage Resources view” on page 67 and “Adding storage resources” on page 80.

StorageX Administrator’s Guide 81

Page 100: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources2

If you want StorageX to update automount map files stored on NFS clients as needed when creating and running Phased Migration policies in the Data Movement or Migration Projects view, you must add each NFS client with the automount map file you want the policy to update to My Resources.

You also must add any storage resources you want to include as sources or destination in Migration Projects to My Resources. For more information, see “Creating and Managing Migration Projects” on page 319 and “Adding sources and destinations to Migration Projects” on page 334.

You can add storage resources to the My Resources folder or a custom folder in one of the following ways:

• Add file storage resources using the Add File Storage Resource Wizard. For more information, see “Adding and configuring file storage resources individually” on page 82.

• Add multiple file storage resources using the File Storage Resource Import Wizard to import a CSV-format list. For more information, see “Creating file storage resource import lists” on page 88 and “Importing lists of file storage resources” on page 95.

• Add object storage resources using the Add Object Storage Resource Wizard. For more information, see “Adding and configuring object storage resources individually” on page 96.

• Add multiple object storage resources using the Object Storage Resource Import Wizard to import a CSV-format list. For more information, see “Creating object storage resource import lists” on page 98 and “Importing lists of object storage resources” on page 99.

Adding and configuring file storage resources individuallyAdd the file storage resources you want to manage using StorageX to the My Resources folder or a custom folder under My Resources in the Storage Resources view. For more information, see “Understanding the Storage Resources view” on page 67 and “Adding storage resources” on page 80.

You must add your file storage resources to the My Resources folder or a custom folder under My Resources in order for StorageX to communicate with the file storage resources and manage the file data stored on the file storage resource.

This topic explains how you can use the Add File Storage Resource Wizard to add file storage resources directly to the My Resources folder or a custom folder under My Resources and configure those new resources.

If you want to add multiple file storage resources in one operation to My Resources or a custom folder, you can do one of the following:

• Manually type the names of multiple resources, separated by a semicolon.

• Create and import a list of file storage resources using the File Storage Resource Import Wizard. For more information, see “Creating file storage resource import lists” on page 88 and “Importing lists of file storage resources” on page 95.

ATTENTIONBefore you add storage resources to StorageX, verify that the storage resource is correctly configured in the domain. For more information, see “Verifying file storage resource DNS configuration” on page 71.

82 StorageX Administrator’s Guide

Page 101: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources 2

To add and configure a file storage resource

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, right-click the My Resources folder or a custom folder under My Resources, and then click Add file storage resource to open the Add File Storage Resources Wizard.

3. Review the welcome message, and then click Next.

4. Click the Platform Type field, select the type of resource for the new file storage resource you want to add, and then click Next.

5. If the file storage resource you want to add is not a virtual resource, complete the following steps:

a. In the Resource Network Name field, type the fully qualified domain name, IP address, or NetBIOS name of the file storage resource you want to manage with StorageX, or click Browse to browse to and select the resource, then click Open.

NOTEYou can use the Shift or Ctrl keys to select multiple resources to add, if necessary. If manually typing the name of more than one resource, you can enter multiple names separated by a semicolon.

If DNS is configured correctly for the file storage resource, IP addresses, NetBIOS names, and fully qualified domain names will all resolve correctly when you add the file storage resource to My Resources. For more information about ensuring DNS is configured correctly for file storage resources, see “Verifying file storage resource DNS configuration” on page 71.

b. Click Next.

6. If the file storage resource you want to add is a Linux file storage resource, and you want StorageX to use credentials other than the default SSH credentials when creating or cloning NFS exports, complete the following steps:

a. Click Actions > Set SSH Credentials.

b. Configure specific SSH shell credentials for the resource. For more information, see “Configuring SSH shell credentials for specific file storage resources” on page 107.

c. Click Next.

7. If the file storage resource you want to add is a Linux file storage resource, and you want StorageX use the default SSH credentials when creating or cloning NFS exports, click Next, then click OK to confirm.

StorageX Administrator’s Guide 83

Page 102: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources2

8. If the file storage resource you want to add is a NetApp 7-Mode Filer or NetApp Cluster, complete the following steps:

a. If you want StorageX to use credentials other than the default Data ONTAP credentials to manage the file storage resource, click Actions > Set API Credentials and configure specific Data ONTAP credentials for StorageX to use when managing the resource. For more information, see “Configuring default Data ONTAP credentials” on page 76 and “Configuring credentials for specific Data ONTAP file storage resources” on page 104.

b. If the file storage resource you added is running Data ONTAP 8.2 in Cluster Mode, Data ONTAP 8.3 in Cluster Mode, ONTAP 9, or ONTAP 9.1, click Actions > Set API Credentials and specify an Administrator account and password for StorageX to use to communicate with the resource.

Data ONTAP 8.2 in Cluster Mode, Data ONTAP 8.3 in Cluster Mode, ONTAP 9, and ONTAP 9.1 do not accept any Windows Active Directory service account credentials, including the StorageX server service account. For these resources, you must specify an account name and password for an account with Administrator permissions that StorageX can use to communicate with each file storage resource running Data ONTAP 8.2 in Cluster Mode, Data ONTAP 8.3 in Cluster Mode, ONTAP 9, or ONTAP 9.1. For more information, see “Configuring credentials for specific Data ONTAP file storage resources” on page 104.

c. If the file storage resource you added has one or more SnapMirrors already configured outside of StorageX, initialize the SnapMirrors to be able to use them in a Disaster Recovery policy. For detailed information on initializing a SnapMirror outside of StorageX, see “Initializing a SnapMirror destination,” in the Data ONTAP® Data Protection Online Backup and Recovery Guide For 7-Mode, available on the NetApp Support web site at https://library.netapp.com/ecmdocs/ECMP1196991/html/GUID-6816A0E6-951B-49F1-AF26-71CD381FB428.html.

d. Click Next.

e. If you want StorageX to use the default Data ONTAP credentials to manage the file storage resource, click OK to confirm.

9. If the file storage resource you want to add is a NetApp 7-Mode vFiler, complete the following steps:

a. If you want to select the hosting NetApp Filer from a list of available Filers in your environment, select Browse the NetApp 7-Mode Filer for a vFiler to add, then select the Filer that hosts the vFiler from the Select NetApp 7-Mode Filer drop-down menu.

b. If you want to manually provide the NetApp vFiler configuration info, select Manually configure the hosting properties of the NetApp 7-Mode vFiler to add, then provide the network name of the vFiler and hosting Filer and the name of the vFiler itself.

For more information about virtual NetApp resources, see “Specifying hosting properties for Data ONTAP vFilers, Vservers, and SVMs” on page 110.

c. Click Next.

d. Select the NetApp vFiler you want to add, and then click Next.

e. If you want StorageX to use credentials other than the default Data ONTAP credentials to manage the file storage resource, click Actions > Set API Credentials and configure specific Data ONTAP credentials for StorageX to use when managing the resource. For more information, see “Configuring default Data ONTAP credentials” on page 76 and “Configuring credentials for specific Data ONTAP file storage resources” on page 104.

84 StorageX Administrator’s Guide

Page 103: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources 2

f. Click Next.

g. If you want StorageX to use the default Data ONTAP credentials to manage the file storage resource, click OK to confirm.

10. If the file storage resource you want to add is a NetApp Cluster Mode Vserver or SVM, complete the following steps:

a. If you want to select the hosting NetApp Cluster from a list of available resources in your environment, select Browse the NetApp Cluster for a Vserver/SVM to add, then select the resource that hosts the Vserver or SVM from the Select NetApp Cluster drop-down menu.

b. If you want to manually provide the NetApp Vserver or SVM configuration info, select Manually configure the hosting properties of the NetApp Cluster Mode Vserver/SVM to add, then provide the network name of the Vserver or SVM and cluster and the name of the Vserver or SVM itself.

For more information about virtual NetApp resources, see “Specifying hosting properties for Data ONTAP vFilers, Vservers, and SVMs” on page 110.

c. Click Next.

d. Select the NetApp Vserver or SVM you want to add, and then click Next.

e. If you want StorageX to use credentials other than the default Data ONTAP credentials to manage the file storage resource, click Actions > Set API Credentials and configure specific Data ONTAP credentials for StorageX to use when managing the resource. For more information, see “Configuring default Data ONTAP credentials” on page 76 and “Configuring credentials for specific Data ONTAP file storage resources” on page 104.

f. Click Next.

g. If you want StorageX to use the default Data ONTAP credentials to manage the file storage resource, click OK to confirm.

11. If the file storage resource you want to add is a VNX OE for File file storage resource, complete the following steps:

a. Click Actions > Set API Credentials and configure specific VNX OE for File credentials for StorageX to use when managing the resource. For more information, see “Configuring default VNX OE for File credentials” on page 78 and “Configuring credentials for specific OneFS file storage resources” on page 106.

b. If the file storage resource you added is a VNX OE for File file storage resource that will be a source or destination in a Migration Project and you want StorageX to use credentials other than the default SSH shell credentials when migrating file data, click Actions > Set SSH Credentials and configure specific SSH shell credentials for the resource. For more information, see “Configuring SSH shell credentials for specific file storage resources” on page 107.

c. Click Next.

d. If you want StorageX to use the default SSH credentials to migrate file data, click OK to confirm.

StorageX Administrator’s Guide 85

Page 104: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources2

12. If the file storage resource you want to add is an EMC VNX CIFS/NFS Server, complete the following steps:

a. If you want to select the hosting EMC VNX resource from a list of available resources in your environment, select Browse the EMC VNX for a CIFS/NFS Server to add, then select the EMC VNX resource that hosts the EMC VNX CIFS/NFS Server from the Select EMC VNX drop-down menu.

b. If you want to manually provide the EMC VNX CIFS/NFS Server configuration info, select Manually configure the hosting properties of the EMC VNX CIFS/NFS Server to add, then provide the network name of the CIFS/NFS Server and hosting EMC VNX resource and the name of the Data Mover.

For more information about EMC VNX Data Mover resources, see “Specifying hosting properties for VNX OE for File Data Movers” on page 111.

c. If the Data Mover is a Virtual Data Mover, select Data Mover is a virtual resource.

d. Click Next.

e. Click Actions > Set API Credentials and configure specific VNX OE for File credentials for StorageX to use when managing the resource. For more information, see “Configuring default VNX OE for File credentials” on page 78 and “Configuring credentials for specific OneFS file storage resources” on page 106.

f. If the file storage resource you added is a VNX OE for File file storage resource that will be a source or destination in a Migration Project and you want StorageX to use credentials other than the default SSH shell credentials when migrating file data, click Actions > Set SSH Credentials and configure specific SSH shell credentials for the resource. For more information, see “Configuring SSH shell credentials for specific file storage resources” on page 107.

NOTEIf you want StorageX to use SSH shell credentials to manage VNX OE for File file storage resources, all managed VNX resources must use the built-in nasadmin account.

g. Click Next.

h. If you want StorageX to use the default SSH credentials to migrate file data, click OK to confirm.

13. If the file storage resource you want to add is an Isilon OneFS file storage resource, complete the following steps:

a. Click Actions > Set API Credentials and configure specific OneFS credentials for StorageX to use when managing the resource. For more information, see “Configuring default OneFS credentials” on page 78 and “Configuring credentials for specific OneFS file storage resources” on page 106.

b. If the file storage resource you added is a Isilon OneFS file storage resource that will be a source or destination in a Migration Project and you want StorageX to use credentials other than the default SSH shell credentials when migrating file data, click Actions > Set SSH Credentials and configure specific SSH shell credentials for the resource. For more information, see “Configuring SSH shell credentials for specific file storage resources” on page 107.

c. Click Next.

86 StorageX Administrator’s Guide

Page 105: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources 2

d. If you want StorageX to use the default SSH credentials to migrate file data, click OK to confirm.

14. If the file storage resource you want to add is an Isilon access zone, complete the following steps:

e. If you want to select the hosting EMC Isilon cluster from a list of available resources in your environment, select Browse the EMC Isilon Cluster for a/an Access Zone to add, then select the resource that hosts the access zone from the Select EMC Isilon Cluster drop-down menu.

f. If you want to manually provide the EMC Isilon access zone configuration info, select Manually configure the hosting properties of the EMC Isilon Access Zone to add, then provide the network name of the access zone, the network name of the cluster, and the name of the access zone itself

For more information about virtual EMC resources, see “Specifying hosting properties for EMC Isilon access zones” on page 112.

g. Click Next.

h. Select the Isilon access zone you want to add, and then click Next.

i. If you want StorageX to use credentials other than the default OneFS credentials to manage the file storage resource, click Actions > Set API Credentials and configure specific OneFS credentials for StorageX to use when managing the resource. For more information, see “Configuring default OneFS credentials” on page 78 and “Configuring credentials for specific OneFS file storage resources” on page 106.

j. Click Next.

k. If you want StorageX to use the default OneFS credentials to manage the file storage resource, click OK to confirm.

15. Click Finish.

16. If StorageX displays any errors or warnings regarding a new resource, check the specified settings for the resource, provide any necessary information, then refresh.

17. If the file storage resource you added is a Windows file storage resource, and you want to allow StorageX to deploy a universal data engine to the resource, right-click the new resource in the Summary pane, select Set Allow Data Engine Install, select Allow universal data engine to be deployed to this host, and click OK. For more information, see “Specifying universal data engine settings on file storage resources” on page 118.

18. Verify that the file storage resource you added to the My Resources folder or a custom folder under My Resources displays correctly. For more information, see “Verifying storage resources” on page 117.

19. Configure SNMP and NFS settings for the file storage resource as needed. For more information, see “Configuring the SNMP community name for file storage resources” on page 113 and “Configuring NFS credentials” on page 113.

After you add and configure the file storage resource, you can modify the initial settings for the resource as needed. For more information about configuring storage resources, see “Configuring storage resources in My Resources” on page 100.

StorageX Administrator’s Guide 87

Page 106: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources2

Creating file storage resource import listsYou can add multiple file storage resources to the My Resources folder or a custom folder under My Resources in the Storage Resources view in one operation, by using the File Storage Resource Import Wizard to import a file storage resource import list.

By default, StorageX provides an example resources.csv file in the \Program Files\Data Dynamics\StorageX\Examples\Import\Resource List folder on the computer where you installed StorageX. You can use this example as a base to create your own .csv file storage resource import list.

The following figure shows a sample .csv file storage resource import list:

Name,Platform Type,API Use Default Credentials,API Username,API Password,Virtual Resource Name,Hosting Resource,Is VDM,SSH Use Default Credentials,SSH Username,SSH Password,SSH Key Filewin-xp-machine.domain.local,windows ntwin7-machine.domain.local,windows ntwin8-machine.domain.local,windows ntwin2k-machine.domain.local,windows ntwin2k3-machine.domain.local,windows ntwin2k3r2-machine.domain.local,windows ntwin2k8-machine.domain.local,windows ntwin2k12-machine.domain.local,windows ntnetapp-736.domain.local,netapp filer,false,root,passwdnetapp-8-7mode.domain.local,netapp filer,false,root,passwdnetapp-8-cmode.domain.local,netapp cluster,false,admin,passwdnetapp-811-7mode.domain.local,netapp filer,true,root,passwdnetapp-811-cmode.domain.local,netapp cluster,false,admin,passwdnetapp-vfiler.domain.local,netapp vfiler,false,root,passwd,vfiler01,netapp-736.domain.localnetapp-vserver.domain.local,netapp vserver,false,root,passwd,vserver01,netapp-811-cmode.domain.localemc-vnx-host.domain.local,emc vnx,false,nasadmin,nasadmin,false,root,passwdemc-vnx-cifs-vdm.domain.local,emc celerra,false,nasadmin,nasadmin,vdm01,emc-vnx-host.domain.local,true,false,root,passwdemc-vnx-nfs-data-mover.domain.local,emc celerra,false,nasadmin,nasadmin,datamover01,emc-vnx-host.domain.local,false,false,root,passwdemc-isilon.domain.local,emc isilon,false,user,passwdlinux.domain.local,linux,,,,,,,false,root,passwd

To create a file storage resource import list, specify the following information in a.csv file:

NameSpecify the IP address, NetBIOS name, or fully qualified domain name for each file storage resource you want to add.

88 StorageX Administrator’s Guide

Page 107: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources 2

NOTEIf you specify a Data ONTAP vFiler, Vserver, or SVM, a VNX OE for File Data Mover, or an Isilon access zone, you do not need to list the individual file storage resources that make up the nodes in the Data ONTAP vFiler, Vserver, or SVM, the VNX OE for File Data Mover, or the Isilon access zone. You only need to specify the NetBIOS name or fully qualified domain name for the Data ONTAP vFiler, Vserver, or SVM, the VNX OE for File Data Mover, or the Isilon access zone, along with Administrator account credential information as needed.

When you import the file storage resource into StorageX, StorageX validates the file storage resource name against the following guidelines from Microsoft and IETEF:

• Naming conventions recommended by Microsoft for computers. For more information, see Naming conventions in Active Directory for computers, domains, sites, and OUs, available on the Microsoft Support site at https://support.microsoft.com/en-us/help/909264/naming-conventions-in-active-directory-for-computers-domains-sites-and.

• Naming conventions specified by the Internet Engineering Task Force (IETF) in RFC 953, available at http://www.ietf.org/rfc/rfc952.txt, and in RFC1123, available at http://www.ietf.org/rfc/rfc1123.txt.

If you specify a file storage resource name that is invalid according to these guidelines, when you try and import the file storage resource list into StorageX, the following error message displays:

You cannot import the following lines because the machine name specified is invalid: Line #Nwhere N is the line number for the file storage resource with the invalid name.

If this error message displays for any of the file storage resources you are trying to import using a file storage resource import list, you cannot add the file storage resource to StorageX using an import list. Add each file storage resource with an invalid name to StorageX one at a time. For more information, see “Adding and configuring file storage resources individually” on page 82.

Platform TypeSpecify the platform type for each file storage resource you want to add. The following table shows the valid platform values you can specify in the .csv file and how the platform values you specify in the .csv file map to the platform values displayed in the Platform Type field on the Computer Properties tab when you select a file storage resource in the Storage Resources view in the StorageX Console.

Platform values

.csv value Value displayed in StorageX Console

Windows NT Microsoft Windows

Linux Linux

EMC EMC Celerra

EMC Celerra EMC Celerra

EMC VNX EMC VNX

EMC Isilon EMC Isilon

EMC Isilon Access Zone EMC Isilon Access Zone

StorageX Administrator’s Guide 89

Page 108: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources2

Specifying a platform type for each file storage resource in the .csv file is optional. If you do not specify the platform type in the .csv file, you can specify it after you import the file storage resource. For more information, see “Specifying file storage resource platform type” on page 122.

Use Default API CredentialsIf the file storage resource is a Data ONTAP, VNX OE for File, or OneFS file storage resource, specify whether you want StorageX to use the default Data ONTAP, VNX OE for File, or OneFS, credentials specified in StorageX, or if you want StorageX to use credentials other than the default credentials when managing the file storage resource.

If you want StorageX to use the default credentials, type yes or true.

If you do not want StorageX to use the default credentials, type no or false.

For more information, see “Configuring default credentials for file storage resources” on page 76.

API User NameIf the file storage resource is a Data ONTAP, VNX OE for File, or OneFS file storage resource and you do not want StorageX to use the default Data ONTAP, VNX OE for File, or OneFS credentials specified in StorageX, specify the name of a different user account with Administrator or root access permissions on the file storage resource. StorageX will use this account when managing the file storage resource. For more information, see “Configuring credentials for specific storage resources” on page 103.

API PasswordIf the file storage resource is a Data ONTAP, VNX OE for File, or OneFS file storage resource and you do not want StorageX to use the default Data ONTAP, VNX OE for File, or OneFS credentials specified in StorageX, specify the password for the user account with Administrator or root access permissions on the file storage resource that you want StorageX to use when managing the file storage resource. StorageX will use this password along with the user account name you specified when managing the file storage resource. For more information, see “Configuring credentials for specific storage resources” on page 103.

Virtual Resource NameIf the file storage resource is a virtual resource, such as a Data ONTAP vFiler, Vserver, or SVM, a VNX OE for File Data Mover, or an Isilon access zone, specify the exact name of the resource that hosts the virtual resource. Consider the following examples:

NetApp Filer NetApp Filer/Cluster

NetApp Cluster NetApp Filer/Cluster

NetApp vFiler NetApp vFiler

NetApp Vserver NetApp vFiler

Generic CIFS Generic CIFS

Generic NFS Generic NFS

Generic CIFS/NFS Generic CIFS/NFS

Platform values

.csv value Value displayed in StorageX Console

90 StorageX Administrator’s Guide

Page 109: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources 2

• If the file storage resource is a Data ONTAP vFiler, Vserver, or SVM, specify the exact name of the vFiler, Vserver, or SVM.

ATTENTIONThe name you type in this field must exactly match the name specified for the vFiler, Vserver, or SVM when it was created using a native NetApp tool such as NetApp OnCommand System Manager. This name may be different than the NetBIOS name or the fully qualified domain name.

If you do not type the name of the vFiler, Vserver, or SVM exactly as it was specified when the vFiler, Vserver, or SVM was created using native NetApp tools, including exact use of upper and lower case letters, StorageX will not be able to display aggregates, volumes, qtrees, and SnapMirrors on the vFiler, Vserver, or SVM. StorageX will also be unable to provision the file storage resource, which includes creating volumes, creating and cloning CIFS shared folders and NFS exports, and creating qtrees and SnapMirrors. For more information about how you can use StorageX to view and provision file storage resources in the Storage Resources view, see “Understanding provisioning” on page 138. For more information about how StorageX can provision file storage resources as a part of a Migration Project, see “Understanding Migration Projects” on page 321.

• If the file storage resource is a VNX OE for File Data Mover, specify the exact name of the VNX OE for File Data Mover.

ATTENTIONThe name you type in this field must exactly match the name specified for the VNX OE for File Data Mover when it was created using a native EMC tool such as EMC Unisphere. This name may be different than the NetBIOS name or the fully qualified domain name.

If you do not type the name of the VNX OE for File Data Mover exactly as it was specified when the Data Mover was created using native EMC tools, including exact use of upper and lower case letters, StorageX will not be able to display file storage resource items such as volumes, tree quotas, CIFS shared folders, and NFS exports on the Data Mover in the Storage Resources view. StorageX will also be unable to provision the file storage resource as a part of a Migration Project. For more information about how you can use StorageX to view file storage resources in the Storage Resources view, see “Viewing storage resource information” on page 121. For more information about how StorageX can provision file storage resources as a part of a Migration Project, see “Understanding Migration Projects” on page 321.

• If the file storage resource is an Isilon access zone, specify the exact name of the Isilon access zone.

ATTENTIONThe name you type in this field must exactly match the name specified for the Isilon access zone when it was created using a native EMC tool such as EMC Unisphere. This name may be different than the NetBIOS name or the fully qualified domain name.

If you do not type the name of the Isilon access zone exactly as it was specified when the access zone was created using native EMC tools, including exact use of upper and lower case letters, StorageX will not be able to display file storage resource items such as CIFS shared folders, and NFS exports on the access zone in the Storage Resources view. StorageX will also be unable to provision the file storage resource as a part of a Migration

StorageX Administrator’s Guide 91

Page 110: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources2

Project. For more information about how you can use StorageX to view file storage resources in the Storage Resources view, see “Viewing storage resource information” on page 121. For more information about how StorageX can provision file storage resources as a part of a Migration Project, see “Understanding Migration Projects” on page 321.

Hosting ResourceIf the file storage resource is a virtual resource, such as a Data ONTAP vFiler, Vserver, or SVM, a VNX OE for File Data Mover, or an Isilon access zone, specify the name of the resource that hosts the virtual resource. Consider the following examples:

• If the file storage resource is a Data ONTAP vFiler, specify the name of the vFiler hosting filer as the hosting resource.

• If the file storage resource is a Data ONTAP Vserver or SVM, specify the name of the Vserver or SVM hosting cluster as the hosting resource.

• If the file storage resource is a VNX OE for File Data Mover, specify the name of the VNX OE for File hosting resource for the VNX OE for File Data Mover.

• If the file storage resource is an Isilon access zone, specify the name of the EMC Isilon cluster hosting resource for the Isilon access zone.

Is Virtual Data MoverIf the file storage resource is a Virtual Data Mover, type yes. If the file storage resource is not a Virtual Data Mover, type no.

Use Default SSH CredentialsIf the file storage resource is a Data ONTAP, VNX OE for File, or OneFS file storage resource, specify whether you want StorageX to use the default Data ONTAP, VNX OE for File, or OneFS, credentials specified in StorageX, or if you want StorageX to use credentials other than the default credentials when managing the file storage resource.

If you want StorageX to use the default credentials, type yes or true.

If you do not want StorageX to use the default credentials, type no or false.

For more information, see “Configuring default credentials for file storage resources” on page 76.

SSH User NameIf the file storage resource is a Data ONTAP, VNX OE for File, or OneFS file storage resource and you do not want StorageX to use the default Data ONTAP, VNX OE for File, or OneFS credentials specified in StorageX, specify the name of a different user account with Administrator or root access permissions on the file storage resource. StorageX will use this account when managing the file storage resource. For more information, see “Configuring credentials for specific storage resources” on page 103.

SSH PasswordIf the file storage resource is a Data ONTAP, VNX OE for File, or OneFS file storage resource and you do not want StorageX to use the default Data ONTAP, VNX OE for File, or OneFS credentials specified in StorageX, specify the password for the user account with Administrator or root access permissions on the file storage resource that you want StorageX to use when managing the file storage resource. StorageX will use this password along with the user account name you specified when managing the file storage resource. For more information, see “Configuring credentials for specific storage resources” on page 103.

92 StorageX Administrator’s Guide

Page 111: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources 2

SSH Private Key FileIf the file storage resource is a Data ONTAP, VNX OE for File, or OneFS file storage resource and you do not want StorageX to use the default Data ONTAP, VNX OE for File, or OneFS credentials specified in StorageX, specify the UNC path for the location of the SSH private key you want StorageX to use. StorageX will use this private key file when managing the file storage resource.

NOTEPrivate keys used by StorageX must use the OpenSSH format. You must convert any PuTTY-format private keys to use the OpenSSH format. For more information, see “Converting PuTTY-generated SSH private keys to OpenSSH-format private keys” on page 438.

For more information, see “Configuring credentials for specific storage resources” on page 103.

NOTEIf you have already added a file storage resource to the My Resources folder or a custom folder under My Resources, you do not need to include it again in the .csv file.

You can also use the Add File Storage Resource Wizard to add file storage resources to the My Resources folder or a custom folder under My Resources one by one as needed. For more information, see “Adding and configuring file storage resources individually” on page 82.

To create a file storage resource import list

1. Open Windows Explorer and browse to the \Program Files\Data Dynamics\StorageX\Examples\Import\Resource List folder.

2. Open the resources.csv file in Microsoft Excel or Notepad.

3. Review the sample information and format used in the resources.csv file.

4. For each file storage resource you want to add to the My Resources folder, type the fully qualified domain name, NetBIOS name, or IP address. For example, type the following entries:

win-xp-machine.domain.localwin7-machine.domain.localwin8-machine.domain.localwin2k-machine.domain.localwin2k3-machine.domain.localwin2k3r2-machine.domain.localwin2k8-machine.domain.localwin2k12-machine.domain.localnetapp-736.domain.localnetapp-8-7mode.domain.localnetapp-8-cmode.domain.localnetapp-811-7mode.domain.localnetapp-811-cmode.domain.localnetapp-vfiler.domain.localnetapp-vserver.domain.localemc-vnx-host.domain.localemc-vnx-data_mover.domain.localemc-isilon.domain.locallinux.domain.local,linux

5. After each file storage resource fully qualified domain name, NetBIOS name, or IP address, type a comma (,) and then type the platform type for the file storage resource. For example, type the following entries:

StorageX Administrator’s Guide 93

Page 112: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources2

win-xp-machine.domain.local,windows ntwin7-machine.domain.local,windows ntwin8-machine.domain.local,windows ntwin2k-machine.domain.local,windows ntwin2k3-machine.domain.local,windows ntwin2k3r2-machine.domain.local,windows ntwin2k8-machine.domain.local,windows ntwin2k12-machine.domain.local,windows ntnetapp-736.domain.local,netapp filernetapp-8-7mode.domain.local,netapp filernetapp-8-cmode.domain.local,netapp clusternetapp-811-7mode.domain.local,netapp filernetapp-811-cmode.domain.local,netapp clusternetapp-vfiler.domain.local,netapp vfilernetapp-vserver.domain.local,netapp vserveremc-vnx_host.domain.local,emc vnxemc-vnx_data_mover.domain.local,emc celerraemc-isilon.domain.local,emc isilonlinux.domain.local,linux

If you do not specify the platform type in the .csv file, you can specify it after you import the file storage resource. For more information, see “Specifying file storage resource platform type” on page 122.

6. If you want StorageX to use specific credentials when communicating with the file storage resource, after the file storage resource name and platform type, type a comma (,), then type no or false, then type a comma (,) then type the name of a user account with Administrator permissions on the file storage resource, then type another comma (,), then type the password for the user account with Administrator permissions on the file storage resource. For example, type the following entries:

netapp-736.domain.local,netapp filer,false,root,passwdnetapp-8-7mode.domain.local,netapp filer,false,root,passwdnetapp-8-cmode.domain.local,netapp cluster,false,admin,passwdnetapp-811-7mode.domain.local,netapp filer,true,root,passwdnetapp-811-cmode.domain.local,netapp cluster,false,admin,passwd

NOTEIf you specify a user account and password and then type yes or true instead of no or false, when you type yes or true, you have specified that you want to use the default Data ONTAP, VNX OE for File, or OneFS credentials specified in StorageX. However, you have also specified specific credentials for StorageX to use to communicate with the file storage resource. In this scenario, because you typed yes or true, StorageX will use the default credentials. However, if you later specify in the StorageX Console that you want StorageX to use specific credentials when managing the resource, StorageX will then use these specific credentials. For more information, see “Configuring default credentials for file storage resources” on page 76 and “Configuring credentials for specific storage resources” on page 103.

7. If you want StorageX to use the default credentials specified for the file storage resource platform type in StorageX when communicating with the file storage resource, after the file storage resource name and platform type, type a comma (,), and then type yes or true. For example, type the following entries:

netapp-736.domain.local,netapp filer,truenetapp-8-7mode.domain.local,netapp filer,truenetapp-8-cmode.domain.local,netapp cluster,truenetapp-811-7mode.domain.local,netapp filer,truenetapp-811-cmode.domain.local,netapp cluster,true

94 StorageX Administrator’s Guide

Page 113: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources 2

netapp-vfiler.domain.local,netapp vfiler,truenetapp-vserver.domain.local,netapp vserver,trueemc-vnx-host.domain.local,emc vnx,false,nasadmin,nasadminemc-vnx-cifs-vdm.domain.local,emc celerra,false,nasadmin,nasadmin,vdm01,emc-vnx-host.domain.local,trueemc-vnx-nfs-data-mover.domain.local,emc celerra,false,nasadmin,nasadmin,datamover01,emc-vnx-host.domain.local,falseemc-isilon.domain.local,emc isilon,true

8. If the file storage resource is a virtual resource, such as a Data ONTAP vFiler, Vserver, or SVM or a VNX OE for File Data Mover, after specifying the resource name, platform type, and credentials, specify the name of the resource that hosts the virtual resource, as well as the exact name of the virtual resource. For example, type the following entries:

netapp-vfiler.domain.local,netapp vfiler,false,root,passwd,vfiler01,netapp-736.domain.localnetapp-vserver.domain.local,netapp vserver,false,root,passwd,vserver01,netapp-811-cmode.domain.localemc-vnx-host.domain.local,emc vnx,false,nasadmin,nasadminemc-vnx-cifs-vdm.domain.local,emc celerra,false,nasadmin,nasadmin,vdm01,emc-vnx-host.domain.local,trueemc-vnx-nfs-data-mover.domain.local,emc celerra,false,nasadmin,nasadmin,datamover01,emc-vnx-host.domain.local,falseemc-isilon.domain.local,emc isilon,false,user,passwd

9. Save the .csv file to a folder where the Windows user account you use to run the StorageX Console has Read permissions.

10. Import the file storage resources listed in the .csv file into the My Resources folder or a custom folder under My Resources. For more information, see “Importing lists of file storage resources” on page 95.

Importing lists of file storage resourcesAfter creating a file storage resource import list .csv file, import the list of file storage resources into the My Resources folder or a custom folder under My Resources in the Storage Resources view.

For more information about creating a file storage resource import list, see “Creating file storage resource import lists” on page 88.

ATTENTIONBefore you import a list of file storage resources into the My Resources folder or a custom folder under My Resources, verify that each file storage resource is correctly configured in the domain. For more information, see “Verifying file storage resource DNS configuration” on page 71.

To import a list of file storage resources into My Resources

1. Click the Storage Resources tab.

2. In the left tree pane, right-click the My Resources folder or a custom folder under My Resources, and then click Add file storage resources from file.

3. Browse to the location of the .csv file that contains the list of file storage resources you want to import, click the file, and then click Open. The user account you use to run the StorageX Console must have at least Read permissions on the folder that contains the .csv file.

StorageX Administrator’s Guide 95

Page 114: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources2

4. Click Next.

5. Review the list of file storage resources that you want to import.

6. If you want to modify any configuration information, select the resource and click Actions, select the properties you want to modify, and configure the resource as necessary, then click OK.

NOTEYou can select multiple resources to modify at once, but you can only modify properties that apply to all selected resources.

7. If you want to allow StorageX to deploy a universal data engine to a Windows resource, click Allow Data Engine Install for that resource.

8. Click Next.

9. If you want StorageX to use the default SSH credentials for the resources to be imported, click OK to confirm.

10. If an error message about an invalid machine name displays, one or more file storage resources in your import list has an invalid name.

When you import the file storage resource into StorageX, StorageX validates the file storage resource name against the following guidelines from Microsoft and IETEF:

• Naming conventions recommended by Microsoft for computers. For more information, see Naming conventions in Active Directory for computers, domains, sites, and OUs, available on the Microsoft Support site at https://support.microsoft.com/en-us/help/909264/naming-conventions-in-active-directory-for-computers-domains-sites-and.

• Naming conventions specified by the Internet Engineering Task Force (IETF) in RFC 953, available at http://www.ietf.org/rfc/rfc952.txt, and in RFC1123, available at http://www.ietf.org/rfc/rfc1123.txt.

If you specify a file storage resource name that is invalid according to these guidelines, when you try and import the file storage resource list into StorageX, the following error message displays:

You cannot import the following lines because the machine name specified is invalid: Line #N,

where N is the line number for the file storage resource with the invalid name.

If this error message displays for any of the file storage resources you are trying to import using a file storage resource import list, you cannot add the file storage resource to StorageX using an import list. Add each file storage resource with an invalid name to StorageX one at a time. For more information, see “Adding and configuring file storage resources individually” on page 82.

11. Click Finish.

Adding and configuring object storage resources individuallyAdd the object storage resources you want to manage using StorageX to the My Resources folder or a custom folder under My Resources in the Storage Resources view. For more information, see “Understanding the Storage Resources view” on page 67 and “Adding storage resources” on page 80.

96 StorageX Administrator’s Guide

Page 115: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources 2

You must add your object storage resources to the My Resources folder or a custom folder under My Resources in order for StorageX to communicate with the object storage resources and archive file data to the object resources or retrieve file data from the object resources.

This topic explains how you can use the Add File Storage Resource Wizard to add file storage resources directly to the My Resources folder or a custom folder under My Resources and configure those new resources.

If you want to add multiple object storage resources in one operation to My Resources or a custom folder, you can create and import a list of object storage resources using the Object Storage Resource Import Wizard. For more information, see “Creating object storage resource import lists” on page 98 and “Importing lists of object storage resources” on page 99.

To add and configure an object storage resource

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, right-click the My Resources folder or a custom folder under My Resources, and then click Add object storage resource to open the Add Object Storage Resources Wizard.

3. Review the welcome message, and then click Next.

4. Click the Platform Type field, select the type of resource for the new object storage resource you want to add, and then click Next.

5. In the URL field, type the full URL and endpoint for the object storage resource you want to manage with StorageX.

6. In the Display Name field, specify the name you want to use as a display name for the new object storage resource.

7. Click Next.

8. If the object storage resource you want to add is an S3-compliant object storage resource, including IBM COS and StorageGRID resources, complete the following steps:

a. Click Actions > Set S3 Credentials.

b. Configure the credentials for the S3-compliant resource. For more information, see “Configuring credentials for specific object storage resources” on page 109.

c. Click Next.

9. Click Finish.

10. If StorageX displays any errors or warnings regarding a new resource, check the specified settings for the resource, provide any necessary information, then refresh.

11. Verify that the object storage resource you added to the My Resources folder or a custom folder under My Resources displays correctly. For more information, see “Verifying storage resources” on page 117.

After you add and configure the storage resource, you can modify the initial settings for the resource as needed. For more information about configuring storage resources, see “Configuring storage resources in My Resources” on page 100.

StorageX Administrator’s Guide 97

Page 116: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources2

Creating object storage resource import listsYou can add multiple object storage resources to the My Resources folder or a custom folder under My Resources in the Storage Resources view in one operation, by using the Object Storage Resource Import Wizard to import an object storage resource import list.

The following figure shows a sample .csv object storage resource import list:

Name,Platform Type,S3Url,S3AccountName,S3AccessKeyId,S3SecretKeymy-s3-store,Generic S3-Compliant,s3-compliant.server.com:8082,B7BAHLW8A5D321AA,jAGHdflfgjkS/Adjjas4235+sdg+43

To create an object storage resource import list, specify the following information in a.csv file:

NameSpecify the display name for each object storage resource you want to add.

Platform TypeSpecify the platform type for each object storage resource you want to add. The following table shows the valid platform values you can specify in the .csv file and how the platform values you specify in the .csv file map to the platform values displayed in the Platform Type field on the Object Storage Properties tab when you select an object storage resource in the Storage Resources view in the StorageX Console.

S3 URLIf the storage resource is an S3-compliant object storage resource, specify the URL or endpoint for the resource, including the port number.

S3 Account NameIf the storage resource is an S3-compliant object storage resource, specify the name of the user account you want to use on the S3-compliant resource. StorageX will use this account when managing the object storage resource. For more information, see “Configuring credentials for specific storage resources” on page 103.

S3 Access Key IDIf the storage resource is an S3-compliant object storage resource, specify the access key for the S3 user account on the object storage resource. StorageX will use this access key, along with the user account name you specified, when managing the object storage resource. For more information, see “Configuring credentials for specific storage resources” on page 103.

S3 Secret Access KeyIf the storage resource is an S3-compliant object storage resource, specify the secret access key for the S3 user account on the object storage resource. StorageX will use this secret access key, along with the access key and user account name you specified, when managing the object storage resource. For more information, see “Configuring credentials for specific storage resources” on page 103.

Platform values

.csv value Value displayed in StorageX Console

Generic S3-Compliant Generic S3-compliant platform

98 StorageX Administrator’s Guide

Page 117: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding storage resources 2

NOTEIf you have already added an object storage resource to the My Resources folder or a custom folder under My Resources, you do not need to include it again in the .csv file.

You can also use the Add Object Storage Resource Wizard to add object storage resources to the My Resources folder or a custom folder under My Resources one by one as needed. For more information, see “Adding and configuring object storage resources individually” on page 96.

To create an object storage resource import list

1. Use a text editor to create a new .csv file.

2. For each object storage resource you want to add to the My Resources folder, type the display name you want to use.

3. After each object storage resource display name, type a comma (,) and then type the platform type for the object storage resource. For example, type the following entry:

my-S3-store,Generic S3-Compliant

4. After the object storage resource name and platform type, type a comma (,), then type the URL for the object storage resource, then type another comma (,), then type the name of the user account you want StorageX to use to access the object storage resource, then type another comma (,), then type the access key for the user account on the object storage resource, then type another comma (,), and then type the secret access key for the user account on the object storage resource. For example, type the following entry:

my-s3-store,Generic S3-Compliant,s3-compliant.server.com:8082,B7BAHLW8A5D321AA,jAGHdflfgjkS/Adjjas4235+sdg+43

5. Save the .csv file to a folder where the Windows user account you use to run the StorageX Console has Read permissions.

6. Import the object storage resources listed in the .csv file into the My Resources folder or a custom folder under My Resources. For more information, see “Importing lists of object storage resources” on page 99.

Importing lists of object storage resourcesAfter creating an object storage resource import list .csv file, import the list of object storage resources into the My Resources folder or a custom folder under My Resources in the Storage Resources view.

For more information about creating an object storage resource import list, see “Creating object storage resource import lists” on page 98.

To import a list of object storage resources into My Resources

1. Click the Storage Resources tab.

2. In the left tree pane, right-click the My Resources folder or a custom folder under My Resources, and then click Add object storage resources from file.

StorageX Administrator’s Guide 99

Page 118: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring storage resources in My Resources2

3. Browse to the location of the .csv file that contains the list of object storage resources you want to import, click the file, and then click Open. The user account you use to run the StorageX Console must have at least Read permissions on the folder that contains the .csv file.

4. Click Next.

5. Review the list of object storage resources that you want to import.

6. If you want to modify any configuration information, select the resource and click Actions, select the properties you want to modify, and configure the resource as necessary, then click OK.

NOTEYou can select multiple resources to modify at once, but you can only modify properties that apply to all selected resources.

7. Click Next.

8. Click Finish.

Configuring storage resources in My ResourcesAfter you add a storage resource to the My Resources folder or a custom folder under My Resources in the Storage Resources view, you can modify the storage resource configuration as needed.

Ensure the storage resource is configured correctly in the domain and the StorageX server service account has been added to the storage resource and/or has Administrator or root access permission on the storage resource before you configure the resource.

Typically, for file storage resources you verify the resource is configured correctly in the domain and add the StorageX server service account to the file storage resource before you add the file storage resource to My Resources. However, if you have not yet done these tasks, complete these tasks before configuring the file storage resource in My Resources. You do not need to perform these tasks beforehand for object storage resources.

For more information, see “Verifying file storage resource DNS configuration” on page 71, “StorageX server service account requirements” on page 16, and “Adding the StorageX server service account to file storage resources” on page 71.

To configure a storage resource in My Resources

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under Storage Resources > My Resources, browse to and select the storage resource you want to configure.

3. If the storage resource you added is a Linux file storage resource and you want StorageX to use credentials other than the default SSH shell credentials when creating or cloning NFS exports, configure specific SSH shell credentials for the resource. For more information, see “Configuring SSH shell credentials for specific file storage resources” on page 107.

100 StorageX Administrator’s Guide

Page 119: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring storage resources in My Resources 2

4. If the storage resource you added is a Data ONTAP file storage resource, complete the following steps:

a. If you want StorageX to use credentials other than the default Data ONTAP credentials to manage the file storage resource, configure specific Data ONTAP credentials for StorageX to use when managing the resource. For more information, see “Configuring default Data ONTAP credentials” on page 76 and “Configuring credentials for specific Data ONTAP file storage resources” on page 104.

b. If the storage resource is a Data ONTAP vFiler, Vserver, or SVM, configure each vFiler, Vserver, or SVM by specifying the vFiler hosting filer or the Vserver or SVM cluster name for each vFiler, Vserver, or SVM you added. For more information, see “Specifying hosting properties for Data ONTAP vFilers, Vservers, and SVMs” on page 110.

c. If the storage resource is a Data ONTAP file storage resource running Data ONTAP 8.2 in Cluster Mode, Data ONTAP 8.3 in Cluster Mode, ONTAP 9, or ONTAP 9.1, specify an Administrator account and password for StorageX to use to communicate with the resource.

Data ONTAP 8.2 in Cluster Mode, Data ONTAP 8.3 in Cluster Mode, ONTAP 9, or ONTAP 9.1 do not accept any Windows Active Directory service account, including the StorageX server service account. For these resources, you must specify an account name and password for an account with Administrator permissions that StorageX can use to communicate with each file storage resource running Data ONTAP 8.2 in Cluster Mode, Data ONTAP 8.3 in Cluster Mode, ONTAP 9, or ONTAP 9.1. For more information, see “Configuring credentials for specific Data ONTAP file storage resources” on page 104.

d. If the storage resource you added has one or more SnapMirrors already configured outside of StorageX, initialize the SnapMirrors to be able to use them in a Disaster Recovery policy.

For detailed information on initializing a SnapMirror outside of StorageX, see “Initializing a SnapMirror destination,” in the Data ONTAP® Data Protection Online Backup and Recovery Guide For 7-Mode, available on the NetApp Support web site at https://library.netapp.com/ecmdocs/ECMP1196991/html/GUID-6816A0E6-951B-49F1-AF26-71CD381FB428.html.

5. If the storage resource you added is a VNX OE for File file storage resource, complete the following steps:

a. If you want StorageX to use credentials other than the default VNX OE for File credentials when to manage the file storage resource, configure specific VNX OE for File credentials for StorageX to use when managing the resource. For more information, see “Configuring default VNX OE for File credentials” on page 78 and “Configuring credentials for specific OneFS file storage resources” on page 106.

b. If the storage resource is a VNX OE for File Data Mover, configure each VNX OE for File Data Mover by specifying the VNX OE for File Data Mover name and hosting resource for each VNX OE for File Data Mover you added. For more information, see “Specifying hosting properties for Data ONTAP vFilers, Vservers, and SVMs” on page 110.

c. If the storage resource you added is a VNX OE for File file storage resource that will be a source or destination in a Migration Project and you want StorageX to use credentials other than the default SSH shell credentials when migrating file data, configure specific SSH shell credentials for the resource. For more information, see “Configuring SSH shell credentials for specific file storage resources” on page 107.

StorageX Administrator’s Guide 101

Page 120: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring storage resources in My Resources2

6. If the storage resource you added is a OneFS file storage resource, complete the following steps:

a. If you want StorageX to use credentials other than the default OneFS credentials to manage the file storage resource, configure specific OneFS credentials for StorageX to use when managing the resource. For more information, see “Configuring default OneFS credentials” on page 78 and “Configuring credentials for specific OneFS file storage resources” on page 106.

b. If the storage resource is an Isilon access zone, configure each Isilon access zone by specifying the access zone name and hosting resource for each Isilon access zone you added. For more information, see “Specifying hosting properties for EMC Isilon access zones” on page 112.

7. If the storage resource you added is an IBM COS, StorageGRID, or S3-compliant object storage resource, specify credentials for StorageX to use to communicate with the resource, including the account name, access key, and secret access key. For more information, see “Configuring credentials for specific object storage resources” on page 109.

8. If the storage resource is an NFS client that stores automount map files that you want Phased Migration policies to update in the Final Phase of the policy and you want StorageX to use credentials other than the default SSH shell credentials when communicating with the NFS client, configure specific SSH shell credentials for the NFS client. For more information, see “Configuring SSH shell credentials for specific file storage resources” on page 107.

9. Configure SNMP and NFS settings for file storage resources as needed. For more information, see “Configuring the SNMP community name for file storage resources” on page 113 and “Configuring NFS credentials” on page 113.

10. Verify that the storage resource you added to the My Resources folder or a custom folder under My Resources displays correctly. For more information, see “Verifying storage resources” on page 117.

11. Specify universal data engine settings for the storage resource as appropriate. For more information, see “Specifying universal data engine settings on file storage resources” on page 118.

After you have added the storage resource to StorageX and configured the file storage resource as needed, you are now ready to perform the following tasks:

• View information about heterogeneous storage resources from a central management console. For more information, see “Viewing storage resource information” on page 121.

• Manage StorageX universal data engines as needed. For more information, see “Understanding StorageX universal data engines” on page 9 and “Managing universal data engines” on page 123.

• Provision heterogeneous file storage resources from a central management console.

For example, you can use StorageX to create and manage CIFS shared folders on Windows, Data ONTAP, VNX OE for File, and OneFS file storage resources that use the CIFS protocol. You can use StorageX to create and manage NFS exports on Linux, Data ONTAP, VNX OE for File, and OneFS file storage resources that support the NFS protocol. You can also use StorageX to create and manage Data ONTAP volumes, qtrees, and SnapMirrors on Data ONTAP file storage resources. For more information, see “Provisioning Storage Resources” on page 137.

• If you want to use DFS namespaces to manage file data in your environment, create and manage DFS namespaces as needed. For more information, see “Creating and Managing DFS Namespaces” on page 159.

102 StorageX Administrator’s Guide

Page 121: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring credentials for specific storage resources 2

• If you want to migrate file data stored in CIFS shared folders or NFS exports, create Phased Migration and Archival Migration policies. For more information, see “Creating and Managing Data Movement Policies” on page 227.

• If you want to migrate file data from source Data ONTAP file storage resources, volumes, and qtrees to destination Data ONTAP, VNX OE for File, or OneFS file storage resources, or if you want to migrate file data from source VNX OE for File file storage resources, file systems, volumes, or tree quotas to destination Data ONTAP, or OneFS file storage resources, create Migration Projects.

For more information about creating Migration Projects, see “Creating and Managing Migration Projects” on page 319.

• If you want to archive file data from file storage resources to an object storage resource, use the StorageX Management Portal to scan your file storage resources, analyze your data, and create an Archive. For more information, see the StorageX Analysis, Archival, & Retrieval Guide.

Configuring credentials for specific storage resourcesYou can configure the following types of credentials for StorageX to use with specific storage resources:

• Specific Data ONTAP credentials for StorageX to use to manage specific Data ONTAP file storage resources. For more information, see “Configuring credentials for specific Data ONTAP file storage resources” on page 104.

• Specific VNX OE for File credentials for StorageX to use to manage specific VNX OE for File file storage resources. For more information, see “Configuring credentials for specific VNX OE for File file storage resources” on page 105.

• Specific OneFS credentials for StorageX to use to manage specific OneFS file storage resources. For more information, see “Configuring credentials for specific OneFS file storage resources” on page 106.

• Specific SSH shell credentials for StorageX to use to perform the following tasks:

• On VNX OE for File file storage resources, when migrating file data between VNX OE for File sources and destinations using Migration Projects in the Migration Projects view.

• On Linux file storage resources, when creating and cloning NFS exports in the Storage Resources view, and to clone NFS exports as needed when creating Phased Migration policies in the Data Movement view.

• When updating automount map files stored on NFS clients as needed when running Phased Migration policies in the Data Movement or Migration Projects views. For more information, see “Configuring SSH shell credentials for specific file storage resources” on page 107.

• Specific credentials for StorageX to use to manage specific IBM COS, StorageGRID, or S3-compliant object storage resources. For more information, see “Configuring credentials for specific object storage resources” on page 109.

When you configure specific credentials to communicate with specific storage resources, StorageX uses these specific credentials to communicate with the storage resources instead of any default credentials that you may have specified in StorageX. For more information, see “Configuring default credentials for file storage resources” on page 76.

StorageX Administrator’s Guide 103

Page 122: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring credentials for specific storage resources2

Configuring credentials for specific Data ONTAP file storage resourcesStorageX uses the StorageX server service account to communicate with Data ONTAP file storage resources. StorageX also uses either default or specific Data ONTAP credentials you configure for StorageX to manage Data ONTAP file storage resources.

This topic explains how to specify credentials for StorageX to use when managing specific Data ONTAP file storage resources. When you specify credentials for StorageX to use with specific Data ONTAP file storage resources, StorageX uses the credentials specified for the specific Data ONTAP file storage resource instead of the default Data ONTAP credentials.

For more information about the StorageX server service account, see “StorageX server service account requirements” on page 16. For more information about configuring default Data ONTAP credentials for StorageX to use when managing Data ONTAP file storage resources, see “Configuring default Data ONTAP credentials” on page 76.

You can specify credentials for the following connection types for Data ONTAP file storage resources:

• RPC

• HTTP

• HTTPS

The protocol and credentials you specify for StorageX to use should be based on how you enabled platform API access for your Data ONTAP file storage resources. For more information about enabling platform API access for Data ONTAP file storage resources, see “Enabling platform API access on Data ONTAP file storage resources” on page 72.

If you have Data ONTAP 8.2 Cluster Mode, Data ONTAP 8.3 Cluster Mode, ONTAP 9, or ONTAP 9.1 file storage resources in your environment, StorageX cannot use the StorageX server service account or default Data ONTAP credentials to communicate with these resources. Data ONTAP Cluster Mode does not accept any Windows Active Directory service account, including the StorageX server service account. For these resources, you must specify an account with Administrator permissions that StorageX can use to communicate individually for each file storage resource running Data ONTAP 8.2 in Cluster Mode, Data ONTAP 8.3 in Cluster Mode, ONTAP 9, or ONTAP 9.1.

To configure credentials for specific Data ONTAP file storage resources

1. Ensure platform API access has been enabled on the Data ONTAP file storage resource as needed to allow StorageX to communicate with the file storage resource using the appropriate protocol. For more information, see “Enabling platform API access on Data ONTAP file storage resources” on page 72.

2. Ensure the Data ONTAP file storage resource displays in the Storage Resources view in the left tree pane under the My Resources folder or a custom folder under My Resources.

If the file storage resource is not displayed under My Resources, add it under My Resources. For more information about adding file storage resources to My Resources, see “Adding storage resources” on page 80.

3. In the Summary pane, click File Storage Resources.

4. Select the Data ONTAP file storage resource for which you want to specify credentials, and click Actions > Set API Credentials.

104 StorageX Administrator’s Guide

Page 123: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring credentials for specific storage resources 2

5. If you want StorageX to use the RPC protocol to communicate with the selected Data ONTAP file storage resource, click Use the following settings, and then in the Connection Type field, select RPC from the drop-down list.

In order for StorageX to use RPC to communicate with Data ONTAP file storage resources, a CIFS server must be configured on the resource and the resource must be joined to the domain. For example, you may want to use RPC to communicate with a Data ONTAP file storage resource if the file storage resource is running the Data ONTAP 8 operating system in 7-Mode, a CIFS server has been configured on the resource, the resource has been joined to the domain, and HTTP is disabled on the file storage resource.

6. If you want StorageX to use the HTTP protocol to communicate with Data ONTAP file storage resources, complete the following steps:

a. Click Use the following settings.

b. In the Connection Type field, select HTTP from the drop-down list. HTTP must be enabled on the file storage resource in order for StorageX to use HTTP to communicate with the resource.

c. In the Username field, type name the name of a user account with Administrator permissions on the selected Data ONTAP file storage resource.

d. In the Password field, type the password for the user account.

7. If you want StorageX to use the HTTPS protocol to communicate with Data ONTAP file storage resources, complete the following steps:

a. Click Use the following settings.

b. In the Connection Type field, select HTTPS from the drop-down list. In order for StorageX to use HTTPS to communicate with the resource, both SSL and HTTP must be enabled on the file storage resource.

c. In the Username field, type name the name of a user account with Administrator permissions on the selected Data ONTAP file storage resource.

d. In the Password field, type the password for the user account.

8. Click OK.

9. In the Summary pane, right-click the file storage resource and select Refresh to verify the specified credentials are correct.

Configuring credentials for specific VNX OE for File file storage resourcesStorageX uses the StorageX server service account to communicate with VNX OE for File file storage resources. StorageX also uses either default or specific VNX OE for File credentials you configure for StorageX to manage VNX OE for File file storage resources.

This topic explains how to specify credentials for StorageX to use when managing specific VNX OE for File file storage resources. When you specify credentials for StorageX to use with specific VNX OE for File file storage resources, StorageX uses the credentials specified for the specific VNX OE for File file storage resource instead of the default VNX OE for File credentials.

StorageX Administrator’s Guide 105

Page 124: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring credentials for specific storage resources2

For more information about the StorageX server service account, see “StorageX server service account requirements” on page 16. For more information about configuring default VNX OE for File credentials for StorageX to use when managing VNX OE for File file storage resources, see “Configuring default VNX OE for File credentials” on page 78.

NOTEIf you want StorageX to use SSH shell credentials to manage VNX OE for File file storage resources, all managed VNX resources must use the built-in nasadmin account.

To configure credentials for specific VNX OE for File file storage resources

1. Ensure platform API access has been enabled on the VNX OE for File file storage resource as needed to allow StorageX to communicate with the file storage resource. For more information, see “Enabling platform API access on VNX OE for File file storage resources” on page 75.

2. Ensure the VNX OE for File file storage resource displays in the Storage Resources view in the left tree pane under the My Resources folder or a custom folder under My Resources.

If the file storage resource is not displayed under My Resources, add it under My Resources. For more information about adding file storage resources to My Resources, see “Adding storage resources” on page 80.

3. In the Summary pane, click File Storage Resources.

4. Select the VNX OE for File file storage resource for which you want to specify credentials, and click Actions > Set API Credentials.

5. Click Use the following settings.

6. In the Username field, type the name of a user account with Administrator permissions on the selected VNX OE for File file storage resource.

7. In the Password field, type the password for the user account with Administrator permissions on the VNX OE for File file storage resource.

8. Click OK.

9. Right-click My Resources and select Refresh to verify the specified credentials are correct.

Configuring credentials for specific OneFS file storage resourcesStorageX uses the StorageX server service account to communicate with OneFS file storage resources. StorageX also uses either default or specific OneFS credentials you configure for StorageX to manage OneFS file storage resources.

This topic explains how to specify credentials for StorageX to use when managing specific OneFS file storage resources. When you specify credentials for StorageX to use with specific OneFS file storage resources, StorageX uses the credentials specified for the specific OneFS file storage resource instead of the default OneFS credentials.

For more information about the StorageX server service account, see “StorageX server service account requirements” on page 16. For more information about configuring default OneFS credentials for StorageX to use when managing OneFS file storage resources, see “Configuring default OneFS credentials” on page 78.

106 StorageX Administrator’s Guide

Page 125: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring credentials for specific storage resources 2

To configure credentials for specific OneFS file storage resources

1. Ensure platform API access has been enabled on the OneFS file storage resource as needed to allow StorageX to communicate with the file storage resource. For more information, see “Enabling platform API access on OneFS file storage resources” on page 75.

2. Ensure the OneFS file storage resource displays in the Storage Resources view in the left tree pane under the My Resources folder or a custom folder under My Resources.

If the file storage resource is not displayed under My Resources, add it under My Resources. For more information about adding file storage resources to My Resources, see “Adding storage resources” on page 80.

3. In the Summary pane, click File Storage Resources.

4. Select the OneFS file storage resource for which you want to specify credentials, and click Actions > Set API Credentials.

5. Click Use the following settings.

6. In the Username field, type the name of a user account with root access permissions on the OneFS file storage resource.

7. In the Password field, type the password for the user account.

8. Click OK.

9. In the Summary pane, right-click the file storage resource and select Refresh to verify the specified credentials are correct.

Configuring SSH shell credentials for specific file storage resourcesStorageX uses SSH shell credentials when migrating file data between VNX OE for File sources and destinations using Migration Projects and when managing Linux file storage resources where you want to create or clone NFS exports. StorageX also uses SSH shell credentials when communicating with NFS clients that store automount map files that you want Phased Migration policies to update.

If you plan to include VNX OE for File sources and destinations in Migration Projects, if you plan to use StorageX to create or clone NFS exports on Linux file storage resources, or if you plan to use StorageX Phased Migration Policies to update automount map files stored on NFS clients when running Phased Migration policies, you must first configure StorageX to use SSH shell credentials. For more information about configuring StorageX to use SSH shell credentials, see “Configuring StorageX to Use SSH Shell Credentials” on page 433.

After you configure StorageX to use SSH shell credentials, configure default SSH shell credentials for StorageX to use. StorageX uses the default credentials to migrate file data between VNX OE for File source and destinations using Migration Projects, to create and clone exports on Linux file storage resources, and to communicate with NFS clients that host automount map files that you want Phased Migration policies to update. For more information, see “Configuring default SSH shell credentials” on page 79.

StorageX Administrator’s Guide 107

Page 126: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring credentials for specific storage resources2

You can also specify SSH shell credentials other than the default SSH shell credential for StorageX to use to manage VNX OE for File file storage resources included in Migration Projects as sources and destinations, to manage Linux file storage resources, and to communicate with NFS clients that store automount map files. When you configure specific SSH shell credentials for specific VNX OE for File file storage resources, Linux file storage resources, or NFS clients that store automount map files, StorageX uses the specific SSH shell credentials instead of the default SSH shell credentials.

This topic explains how to specify SSH shell credentials for StorageX to use when managing specific VNX OE for File and Linux file storage resources and when communicating with NFS clients that host automount map files.

To configure SSH shell credentials for specific file storage resources

1. Ensure the VNX OE for File file storage resource, Linux file storage resource, or NFS client that stores automount map files that you want to configure specific SSH shell credentials for is displayed in the Storage Resources view in the left tree pane under the My Resources folder or a custom folder under My Resources.

If the file storage resource is not displayed in My Resources, add it to My Resources. For more information, see “Adding storage resources” on page 80.

2. In the Summary pane, click File Storage Resources.

3. Select the VNX OE for File or file storage resource, Linux file storage resource, or NFS client that stores automount map files that you want to configure specific SSH shell credentials for, and click Actions > Set SSH Credentials.

4. If you want StorageX to use a user name and password for SSH when communicating with the selected file storage resource or NFS client, instead of the default SSH shell credentials, complete the following steps:

a. Click User name and password.

b. In the User name field, type the name of the user account for StorageX to use when communicating with VNX OE for File file storage resources that are sources and destinations in Migration Projects, when communicating with Linux file storage resources where you want to create and clone NFS exports, or when communicating with NFS clients that store automount map files that you want StorageX to update when running Phased Migration policies. Typically, this is root.

c. In the User password field, type the password for the user account you specified in the previous field.

5. If you want StorageX to use an SSH private key when communicating with the selected file storage resource or NFS client, instead of the default SSH shell credentials, complete the following steps:

a. Click Private key file.

b. In the User name field, type the name of the user account for StorageX to use when communicating with VNX OE for File file storage resources that are sources and destinations in Migration Projects, when communicating with Linux file storage resources where you want to create and clone NFS exports, or when communicating with NFS clients that store automount map files that you want StorageX to update when running Phased Migration policies. Typically, this is root.

108 StorageX Administrator’s Guide

Page 127: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring credentials for specific storage resources 2

c. In the Private key file path field, type the UNC path to the location of the SSH private key on the StorageX server computer or click the ellipsis (...) button to browse to and select the SSH private key on the StorageX server computer.

NOTEThe specified private key must be in OpenSSH format. For more information about creating or converting private keys, see “Configuring StorageX to Use SSH Shell Credentials” on page 433.

d. If you specified a passphrase when creating the private key, in the Private key passphrase field, type the passphrase for the private key.

6. Click OK.

7. In the Summary pane, right-click the file storage resource and select Refresh to verify the specified credentials are correct.

Configuring credentials for specific object storage resourcesUnlike file storage resources, StorageX does not use the StorageX server service account to communicate with object storage resources. Instead, StorageX uses the specific credentials you configure for StorageX to manage each object storage resource.

This topic explains how to specify credentials for StorageX to use when managing specific object storage resources.

NOTEStorageX does not currently allow you to use a default set of credentials for all object storage resources in your environment, because the credentials will typically be different for each resource.

To configure credentials for specific object storage resources

1. Ensure the object storage resource displays in the Storage Resources view in the left tree pane under the My Resources folder or a custom folder under My Resources.

If the object storage resource is not displayed under My Resources, add it under My Resources. For more information about adding storage resources to My Resources, see “Adding storage resources” on page 80.

2. In the Summary pane, click Object Storage Resources.

3. Select the object storage resource for which you want to specify or modify credentials.

4. If the object storage resource is an S3-compliant resource, including IBM COS or StorageGRID, click Actions > Set S3 Credentials.

5. In the Account Name field, type the name of the user account you want to use to access the selected object storage resource.

6. In the Access Key ID field, type the access key for the user account on the object storage resource.

7. In the Secret Access Key field, type the secret access key for the user account on the object storage resource.

8. Click OK.

9. Right-click My Resources and select Refresh to verify the specified credentials are correct.

StorageX Administrator’s Guide 109

Page 128: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring virtual file storage resources2

Configuring virtual file storage resourcesAfter you add virtual file storage resources such as Data ONTAP vFilers, Vservers, or SVMs and VNX OE for File Data Movers, ensure you configure these virtual file storage resources for StorageX by specifying hosting properties for each virtual file storage resource. For more information, see the following topics:

• “Specifying hosting properties for Data ONTAP vFilers, Vservers, and SVMs” on page 110

• “Specifying hosting properties for VNX OE for File Data Movers” on page 111

• “Specifying hosting properties for EMC Isilon access zones” on page 112

Specifying hosting properties for Data ONTAP vFilers, Vservers, and SVMsIf you have Data ONTAP vFilers, Vservers, or SVMs you want to manage using StorageX, after you add each vFiler, Vserver, or SVM to My Resources and configure credentials as appropriate, configure each vFiler, Vserver, and SVM for StorageX by specifying the vFiler hosting filer or the Vserver or SVM cluster name for each vFiler, Vserver, or SVM you added.

For more information about adding vFilers, Vservers, or SVMs to StorageX, see “Adding storage resources” on page 80. For more information about configuring credentials for Data ONTAP file storage resources, including Data ONTAP vFilers, Vservers, and SVMs, see “Configuring default Data ONTAP credentials” on page 76 and “Configuring credentials for specific Data ONTAP file storage resources” on page 104.

To configure a Data ONTAP vFiler, Vserver, or SVM

1. Add the Data ONTAP vFiler, Vserver, or SVM to the My Resources folder or a custom folder under My Resources. For more information, see “Adding storage resources” on page 80.

2. In the Summary pane, select the vFiler, Vserver, or SVM you want to configure, and click Actions > Set Hosting Properties.

3. In the Virtual resource name field, type the exact name of the vFiler, Vserver, or SVM.

ATTENTIONThe name you type in this field must exactly match the name specified for the vFiler, Vserver, or SVM when it was created using a native NetApp tool such as NetApp OnCommand System Manager. This name may be different than the NetBIOS name or the fully qualified domain name.

If you do not type the name of the vFiler, Vserver, or SVM exactly as it was specified when the vFiler, Vserver, or SVM was created using native NetApp tools, including exact use of upper and lower case letters, StorageX will not be able to display aggregates, volumes, qtrees, and SnapMirrors on the vFiler, Vserver, or SVM. StorageX will also be unable to provision the file storage resource, which includes creating volumes, creating and cloning CIFS shared folders and NFS exports, and creating qtrees and SnapMirrors.

For more information about how you can use StorageX to view and provision file storage resources in the Storage Resources view, see “Understanding provisioning” on page 138. For more information about how StorageX can provision file storage resources as a part of a Migration Project, see “Understanding Migration Projects” on page 321.

110 StorageX Administrator’s Guide

Page 129: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring virtual file storage resources 2

4. In the Hosting resource field, type the fully qualified domain name of the vFiler hosting filer or the Vserver or SVM cluster name or click the ellipsis (...) button to browse to and select the vFiler hosting filer or Vserver or SVM cluster name.

5. Click OK.

Specifying hosting properties for VNX OE for File Data MoversIf you have VNX OE for File file storage resources you want to manage using StorageX, after you add each VNX OE for File hosting resource and VNX OE for File Data Mover virtual resource to My Resources and configure credentials as appropriate, configure each VNX OE for File Data Mover for StorageX by specifying the VNX OE for File Data Mover virtual resource name and the VNX OE for File hosting resource for each VNX OE for File Data Mover you added.

For more information about adding VNX OE for File hosting resources and VNX OE for File Data Mover virtual resources to StorageX, see “Adding storage resources” on page 80. For more information about configuring credentials for VNX OE for File file storage resources, including VNX OE for File Data Movers, see “Configuring default VNX OE for File credentials” on page 78 and “Configuring credentials for specific VNX OE for File file storage resources” on page 105.

To configure a VNX OE for File Data Mover

1. Add the VNX OE for FileData Mover to the My Resources folder or a custom folder under My Resources. For more information, see “Adding storage resources” on page 80.

2. In the Summary pane, select the VNX OE for File Data Mover you want to configure, and click Actions > Set Hosting Properties.

3. In the Virtual resource name field, type the exact name of the VNX OE for File Data Mover.

ATTENTIONThe name you type in this field must exactly match the name specified for the VNX OE for File Data Mover when it was created using a native EMC tool such as EMC Unisphere. This name may be different than the NetBIOS name or the fully qualified domain name.

If you do not type the name of the VNX OE for File Data Mover exactly as it was specified when the Data Mover was created using native EMC tools, including exact use of upper and lower case letters, StorageX will not be able to display file storage resources such as volumes, tree quotas, CIFS shared folders, and NFS exports on the Data Mover in the Storage Resources view. StorageX will also be unable to provision the file storage resource as a part of a Migration Project. For more information about how you can use StorageX to view file storage resources in the Storage Resources view, see “Viewing storage resource information” on page 121. For more information about how StorageX can provision file storage resources as a part of a Migration Project, see “Understanding Migration Projects” on page 321.

4. In the Hosting resource field, type the fully qualified domain name of the VNX OE for File file storage resource that hosts the Data Mover, or click the ellipsis (...) button to browse to and select the host.

5. If the hosting resource is a Virtual Data Mover, select the Hosting resource is a Virtual Data Mover check box. For more information about Data Movers and Virtual Data Movers, see the VNX OE for File documentation.

StorageX Administrator’s Guide 111

Page 130: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring virtual file storage resources2

ATTENTIONIf your hosting resource is a Virtual Data Mover and you choose not to select the check box, StorageX may not correctly display information about the resource in Storage Resource Reports in the Reporting view.

6. Click OK.

Specifying hosting properties for EMC Isilon access zonesIf you have EMC Isilon access zones you want to manage using StorageX, after you add each access zone to My Resources and configure credentials as appropriate, configure each access zone for StorageX by specifying the hosting EMC Isilon cluster name for each access zone you added.

For more information about adding access zones to StorageX, see “Adding storage resources” on page 80. For more information about configuring credentials for OneFS file storage resources, including EMC Isilon access zones, see “Configuring default OneFS credentials” on page 78 and “Configuring credentials for specific OneFS file storage resources” on page 106.

To configure an EMC Isilon access zone

1. Add the EMC Isilon access zone to the My Resources folder or a custom folder under My Resources. For more information, see “Adding storage resources” on page 80.

2. In the Summary pane, select the access zone you want to configure, and click Actions > Set Hosting Properties.

3. In the Virtual resource name field, type the exact name of the access zone.

ATTENTIONThe name you type in this field must exactly match the name specified for the access zone when it was created using a native EMC tool such as EMC Unisphere. This name may be different than the NetBIOS name or the fully qualified domain name.

If you do not type the name of the Isilon access zone exactly as it was specified when the access zone was created using native EMC tools, including exact use of upper and lower case letters, StorageX will not be able to display file storage resources such as CIFS shared folders and NFS exports on the access zone in the Storage Resources view. StorageX will also be unable to provision the file storage resource as a part of a Migration Project. For more information about how you can use StorageX to view file storage resources in the Storage Resources view, see “Viewing storage resource information” on page 121. For more information about how StorageX can provision file storage resources as a part of a Migration Project, see “Understanding Migration Projects” on page 321.

For more information about how you can use StorageX to view and provision file storage resources in the Storage Resources view, see “Understanding provisioning” on page 138. For more information about how StorageX can provision file storage resources as a part of a Migration Project, see “Understanding Migration Projects” on page 321.

4. In the Hosting resource field, type the fully qualified domain name of the EMC Isilon cluster name or click the ellipsis (...) button to browse to and select the Isilon cluster name.

5. Click OK.

112 StorageX Administrator’s Guide

Page 131: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring the SNMP community name for file storage resources 2

Configuring the SNMP community name for file storage resourcesStorageX uses the SNMP community name to identify and communicate with file storage resources that use SNMP. An SNMP community name is the name of the group to which file storage resources running SNMP belong. SNMP community names help define where information is sent.

By default, StorageX assumes that the SNMP community name used by file storage resources is public.

If you have file storage resources, such as Data ONTAP file storage resources, that use SNMP and you have customized your SNMP community name, specify the appropriate SNMP community name for StorageX to use to communicate with each file storage resource.

To specify the SNMP community name for Linux and Data ONTAP file storage resources

1. In the StorageX Console, click the Storage Resources tab.

2. Ensure the Linux or Data ONTAP file storage resource for which you want to specify SNMP settings is displayed in the Storage Resources view in the left tree pane under the My Resources folder or a custom under My Resources.

If the file storage resource is not displayed under My Resources, add it to My Resources. For more information about adding file storage resources to My Resources, see “Adding storage resources” on page 80.

3. Right-click the Data ONTAP file storage resource for which you want to specify to specify SNMP settings, and then click Properties.

4. Click the SNMP tab.

5. In the SNMP Community Name field, type the name of the SNMP group to which the file storage resource belongs.

6. Click OK.

Configuring NFS credentialsBy default, StorageX Linux data engines use User ID 0 (root) and Group ID 0 when communicating with file storage resources, such as Linux, Data ONTAP, VNX OE for File, and OneFS file storage resources, that use the NFS protocol.

If you want to configure a different User ID and Group ID as the NFS credentials for StorageX to use when communicating with these types of file storage resources, you can specify different NFS credentials for each file storage resource using the NFS protocol as needed.

To configure NFS credentials for a Linux or Data ONTAP file storage resource

1. In the StorageX Console, click the Storage Resources tab.

2. Ensure the file storage resource for which you want to specify NFS credentials is displayed in the left tree pane under the My Resources folder or in a custom folder under My Resources.

If the file storage resource is not displayed under My Resources, add it to My Resources. For more information about adding file storage resources to My Resources, see “Adding storage resources” on page 80.

StorageX Administrator’s Guide 113

Page 132: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring default administrative shares2

3. Right-click the file storage resource for which you want to specify NFS credentials, and then click Properties.

4. Click the NFS Settings tab.

5. In the Default User ID field, specify the user ID you want the Linux data engine to use when communicating with the file storage resource.

6. In the Default Group ID, specify the group ID you want the Linux data engine to use when communicating with the file storage resource.

7. Click OK.

Configuring default administrative sharesBy default, StorageX uses the StorageX service account, which should have domain and local administrator permissions on both the source and destination shares, to clone shares.

However, if the service account cannot access a shared folder on one of the resources because the shared folder has been configured to not allow access even for local administrators, StorageX may not be able to copy all security descriptors to the destination resource during the share cloning process.

The product instead designates a CIFS shared folder located in a Data ONTAP volume, Data ONTAP qtree, NetApp FlexGroup, EMC VNX filesystem, EMC Isilon machine, or EMC Isilon access zone as an administrative share. StorageX then uses the administrative share to copy the metadata from the source share to the destination share.

You can configure StorageX to automatically select an administrative share, specify a particular share to use as the default administrative share, or create a new share to use as the default administrative share.

For example, you may want to clone a share on a resource to which the StorageX service account has domain and local administrator permissions but where the share folder itself on the resource has very restricted permissions that do not allow the service account access. Because StorageX cannot use the service account to read the metadata from the restricted share, the product uses another local share that does have access as the administrative share. When the share cloning process finishes, StorageX has cloned the share on the destination resource, but the permissions on the clone do not allow the service account access.

For more information about cloning shared folders, see “Cloning CIFS shared folders” on page 143. For more information about the permissions recommended for the StorageX service account, see “StorageX server service account requirements” on page 16.

To configure the default administrative share on a storage resource

1. In the StorageX Console, click the Storage Resources tab.

2. Ensure the file storage resource for which you want to configure the default administrative share is displayed in the left tree pane under the My Resources folder or in a custom folder under My Resources.

If the file storage resource is not displayed under My Resources, add it to My Resources. For more information about adding file storage resources to My Resources, see “Adding storage resources” on page 80.

114 StorageX Administrator’s Guide

Page 133: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring replication options for clustered file storage resources 2

3. If configuring the default administrative share for a volume located on a Data ONTAP Filer, vFiler, or Vserver, a NetApp FlexGroup, or a volume located on an EMC VNX resource, complete the following steps:

a. In the left tree pane, expand the file storage resource and locate the volume or FlexGroup for which you want to configure the default administrative share.

b. Right-click the share and select Set Default Admin Share.

4. If configuring the default administrative share for an EMC Isilon machine or EMC Isilon access zone, right-click the top-level file storage resource and select Set Default Admin Share.

5. If you want StorageX to automatically select the default administrative share, click the drop-down list and select <auto-detect>.

6. If you want to use a specific administrative share on the resource, click the drop-down list and select the share you want to use.

7. If you want to create a new share to use as the administrative share, click Create New, provide a name and description or comment for the new share, and click OK.

NOTEStorageX recommends only creating hidden shares using this dialog box. To create a hidden share, specify a share name that ends with a dollar sign ($).

8. Click OK.

Configuring replication options for clustered file storage resourcesStorageX can handle replication to and from clustered file storage resources in multiple ways. At the most basic level, you can use StorageX to migrate data to or from a cluster just as you would any other type of file storage resource. In that situation, the cluster distributes the data amongst its nodes per the settings configured on the cluster itself.

You can also configure StorageX to use specific nodes or access zones in an EMC Isilon or NetApp cluster when migrating data to or from the resource. For example, you might want to configure StorageX to only use cluster nodes that are not regularly used by the bulk of the users in your environment, or to only use specific groups of nodes that you have tasked for replication work. This can improve migration speeds and reduce the amount of time required to migrate data.

StorageX allows users to specify cluster nodes, EMC Isilon access zones, or EMC Isilon SmartConnect groups on the file storage resource that can be used as migration sources or destinations.

ATTENTIONIf you want to use the Cluster Options settings in your environment to improve migration performance with StorageX, configure your environment to allow for high network throughput between all StorageX components and any source or destination resources. In order to see increased performance using the Cluster Options settings, ensure there are high-bandwidth connections between all components and storage resources or enable some type of NIC teaming. Migration performance is limited by the slowest connection in your environment. With a non-clustered source, performance may be limited by the source itself.

StorageX Administrator’s Guide 115

Page 134: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring intercluster interfaces for NetApp Cluster Mode file storage resources2

To configure clustered resources to use only certain nodes or access zones during migration

1. In the StorageX Console, click the Storage Resources tab.

2. Ensure the file storage resource for which you want to configure cluster replication options is displayed in the left tree pane under the My Resources folder or in a custom folder under My Resources.

If the file storage resource is not displayed under My Resources, add it to My Resources. For more information about adding file storage resources to My Resources, see “Adding storage resources” on page 80.

3. Right-click the clustered file storage resource, and then click Properties.

4. Click the Cluster Options tab.

5. If you want to use one or more specific nodes, access zones, or groups as migration sources, click Retrieve data from specific nodes or zones, then select the nodes, access zones, or groups you want to use.

6. If you want to use one or more specific nodes, access zones, or groups as migration destinations, click Send data to specific nodes or zones, then select the nodes, access zones, or groups you want to use.

7. If you do not see the nodes, access zones, or groups you want to use in either list, click Cancel and verify that you have correctly added the clustered resource to StorageX.

8. Click OK.

Configuring intercluster interfaces for NetApp Cluster Mode file storage resources

If you want to use the default StorageX universal data engine to migrate data to or from a NetApp Cluster Mode file storage resource, you do not need to perform any additional configuration steps.

However, if you want to configure StorageX to use SnapMirror replication when migrating data to a NetApp Cluster Mode resource, you must create a new intercluster interface that includes all nodes of the NetApp cluster.

For more information about using SnapMirror replication for Migration Projects, see “Understanding using SnapMirror replication for Migration Projects” on page 330. For more information about configuring and using NetApp Cluster Mode resources, see the NetApp Support site, http://mysupport.netapp.com/.

NOTES:

• To migrate data to a NetApp cluster using SnapMirror replication, you must also configure SnapMirror replication settings for the Migration Project design you want to use.

• If an intercluster interface already exists for a cluster, you do not need to create a new interface.

• When you validate a Migration Project that uses SnapMirror replication, StorageX checks to see if the destination cluster resource has at least one valid intercluster interface configured.

116 StorageX Administrator’s Guide

Page 135: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying storage resources 2

• If you create a new intercluster interface, StorageX does not automatically add the IP address of the new interface to the cluster subnet pool of IP addresses. You must log into NetApp OnCommand System Manager, log into the cluster, click Configuration > Network, select the Subnets tab, and then edit the subnet to include the IP address of the new intercluster interface.

• If you create a new intercluster interface for an ONTAP 9 or ONTAP 9.1 resource, you must specify the same value for both ONTAP nodes in the IPspace column.

To configure an intercluster interface for a NetApp Cluster Mode file storage resource

1. In the StorageX Console, click the Storage Resources tab.

2. Ensure the cluster for which you want to configure an intercluster interface is displayed in the left tree pane under the My Resources folder or in a custom folder under My Resources.

If the cluster is not displayed under My Resources, add it to My Resources. For more information about adding file storage resources to My Resources, see “Adding storage resources” on page 80.

3. Right-click the cluster for which you want to configure an intercluster interface, and then click Create Intercluster Interface.

NOTEYou must configure all columns for all listed nodes to create the intercluster interface. If you cannot complete all columns for all nodes, click Cancel.

4. In the Interface Name field, specify the name you want to use for the logical interface (LIF) for the selected node.

5. In the IP Address field, specify an IP address you want to use for the selected node in the intercluster interface.

6. In the Netmask field, specify the address of the netmask for the specified IP address.

7. In the Gateway field, specify the address of the network gateway for the specified IP address.

8. In the Port field, select the port you want to use for the node in the intercluster interface.

NOTEYou can only select data or intercluster ports. StorageX only displays applicable ports.

9. Click OK. StorageX creates the new intercluster interface.

Verifying storage resourcesAfter you add storage resources to the My Resources folder or a custom folder under My Resources, verify that the storage resource you added passed all validation checks, and that StorageX displays the new resource correctly under My Resources.

For more information about storage resource validation checks, see “Understanding storage resource validation checks” on page 70.

StorageX Administrator’s Guide 117

Page 136: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Specifying universal data engine settings on file storage resources2

To verify storage resources in My Resources

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, click My Resources.

3. If you want to verify one or more file storage resources, in the Summary pane, click the File Storage Resources tab.

4. If you want to verify one or more object storage resources, in the Summary pane, click the Object Storage Resources tab.

5. In the Summary pane, select the storage resource you want to verify.

6. Wait until StorageX validates the selected resource. If the center pane displays a Not Validated icon ( ) in the Status column for the resource, StorageX has not yet run validation checks on the resource.

The Failed icon ( ) indicates that StorageX could not validate the resource, the Warning icon ( ) indicates that the resource passed most validation checks, but that StorageX could not fully validate the resource, and the Validated icon ( ) indicates that StorageX successfully validated the resource.

7. Review the information displayed in the Validation results pane.

8. If any validation check displays a Failed icon, select the validation check, review the information displayed in the Validation details pane, and follow any steps provided to resolve the issue. For information about configuring storage resources, see “Configuring platform API access for file storage resources” on page 72, “Configuring default credentials for file storage resources” on page 76, “Configuring storage resources in My Resources” on page 100, “Configuring credentials for specific storage resources” on page 103, and “Configuring virtual file storage resources” on page 110.

9. If you want to verify one or more file storage resources, in the left tree pane under Storage Resources > My Resources, expand each file storage resource and confirm that the Exports and Shares folders display as appropriate under each file storage resource.

10. If StorageX does not display the Shares and Exports folders as appropriate under a file storage resource, the StorageX server service account does not have Administrator or root access permissions to obtain all shares and exports on the file storage resource. To resolve this issue, add the StorageX server service account to the file storage resource. For more information, see “Adding the StorageX server service account to file storage resources” on page 71.

11. If you want to verify one or more object storage resources, in the left tree pane under Storage Resources > My Resources, expand each object storage resource and confirm that the Buckets folder displays as appropriate under each object storage resource.

12. If StorageX does not display the Buckets folder as appropriate under an object storage resource, StorageX may not have the correct credentials for the resource. To resolve this issue, verify the object storage resource credentials. For more information, see “Configuring credentials for specific object storage resources” on page 109.

Specifying universal data engine settings on file storage resourcesStorageX uses universal data engines to move file data. The following topics in this section provide information about how to specify universal data engine settings on file storage resources:

• “Specifying universal data engine proxy computers for file storage resources” on page 119

118 StorageX Administrator’s Guide

Page 137: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Specifying universal data engine settings on file storage resources 2

• “Specifying universal data engine data transfer rate limits” on page 120

For more information about universal data engines, see the following topics:

• “Understanding StorageX universal data engines” on page 9

• “Universal data engine computer requirements” on page 20

• “Installing Windows data engines” on page 34

• “Installing and configuring Linux data engines” on page 35

• “Managing universal data engines” on page 123

Specifying universal data engine proxy computers for file storage resourcesA universal data engine proxy computer is a proxy computer where you deploy a universal data engine. After you deploy a universal data engine to a proxy computer, you can then use the universal data engine on the proxy computer to transfer file data from a source file storage resource to a destination file storage resource.

By default, StorageX installs a Windows data engine on the StorageX server computer when you install the StorageX server. By default, StorageX also deploys Windows data engines on Windows file storage resources when StorageX runs policies that migrate or replicate file data on file storage resources. You must manually install and configure Linux data engines on Linux file storage resources. For more information about deploying Windows data engines, see “Installing Windows data engines” on page 34. For more information about manually installing and configuring Linux data engines, see “Installing and configuring Linux data engines” on page 35.

However, you may have specific Windows file storage resources on which you do not want StorageX to deploy a Windows data engine. You may also have Linux file storage resources where you don’t want to install a Linux data engine. Finally, you may have Data ONTAP, VNX OE for File, or OneFS file storage resources running the Data ONTAP, VNX OE for File, or OneFS operating system on which you cannot deploy a Windows data engine or install a Linux data engine. In these types of scenarios, you can specify a universal data engine proxy computer for the file storage resource.

When you specify a universal data engine proxy computer for a file storage resource, StorageX uses the universal data engine on the specified proxy computer to migrate or replicate data when StorageX runs a policy that affects the file storage resource.

To specify a universal data engine proxy computer for a file storage resource

1. In the StorageX Console, click the Storage Resources tab.

2. Ensure the file storage resource for which you want to specify a universal data engine proxy computer is displayed in the left tree pane under Storage Resources > My Resources.

If the file storage resource is not displayed under My Resources, add it to My Resources. For more information about adding file storage resources to My Resources, see “Adding storage resources” on page 80.

3. Click the Control Panel tab.

4. In the left pane, click Data Engine Proxies.

5. In the center pane, click New Proxy.

StorageX Administrator’s Guide 119

Page 138: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Specifying universal data engine settings on file storage resources2

6. In the Host field, type the fully qualified domain name of the file storage resource for which you want to specify a proxy universal data engine or click the ellipsis button (...) to browse to and select the file storage resource.

7. In the Protocol field, specify the protocol that the file storage resource for which you want to specify a proxy universal data engine uses.

If the file storage resource uses the CIFS protocol, select CIFS from the drop-down list.

If the file storage resource uses the NFS protocol, select NFS from the drop-down list.

8. If you want to use the universal data engine on the StorageX server computer as the universal data engine proxy computer for the file storage resource, click Use default proxy.

9. If you want to use a specific universal data engine proxy computer, click Use this specified proxy, and then select the universal data engine proxy computer from the list.

10. If you want to use a universal data engine installed on a proxy computer that is a member of a universal data engine group, click Use this specified data engine group, and then select the data engine group from the list. For more information about universal data engine groups, see “Creating and managing universal data engine groups” on page 130.

11. Click OK.

Specifying universal data engine data transfer rate limits You can specify universal data engine data transfer rate limits for Windows and Linux data engines. Specifying universal data engine data transfer rate limits for universal data engines is also known as bandwidth throttling.

Consider specifying universal data engine data transfer rate limits if the source or destination file storage resource is already busy with normal file data traffic and you want to ensure that any policies that transfer file data between the source and destination do not consume too much network bandwidth.

To specify universal data engine data transfer rate limits

1. In the StorageX Console, click the Control Panel tab.

2. In the left pane, click Deployed Data Engines.

3. In the center pane, right-click a Windows or Linux data engine computer, and then click Properties.

4. On the Settings tab, in the Throttling Settings area, complete the following steps in the Weekdays and Weekends areas:

a. Specify the appropriate business hours.

b. If you want to set a data transfer rate limit for the universal data engine during business hours, select the Enable throttling in business hours check box, and then specify a maximum rate in bytes per second.

c. If you want to set a data transfer rate limit for the universal data engine during non-business hours, select the Enable throttling in non-business hours check box, and then specify a maximum rate in bytes per second.

5. Click OK.

120 StorageX Administrator’s Guide

Page 139: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Viewing storage resource information 2

Viewing storage resource informationYou can view property information for each heterogeneous storage resource in your environment from a central console in the StorageX Storage Resources view. Use the Storage Resources view to perform the following tasks:

• View property information for storage resources. For more information, see “Viewing storage resource properties” on page 121.

• Refresh displayed storage resource information. For more information, “Refreshing displayed storage resource information” on page 121.

• Specify file storage resource identity. For more information, see “Specifying file storage resource platform type” on page 122.

Viewing storage resource propertiesYou can use StorageX to view the properties of storage resources you have added to the My Resources folder in the Storage Resources view. For more information about adding storage resources to the My Resources folder in the Storage Resources view, see “Adding storage resources” on page 80.

To view storage resource properties

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under Storage Resources > My Resources, select the storage resource for which you want to view properties.

3. In the center pane, click Properties. StorageX displays a properties dialog box for the selected storage resource. The properties dialog box has a series of tabs that display additional information about the selected storage resource, such as IP address, operating system, and more, as applicable for that resource type. For more information about the fields and options on each tab, click the Help button on the tab.

Refreshing displayed storage resource informationRefresh storage resource information when you want to display and verify any recent changes you made to the storage resource. When you refresh storage resource information, StorageX updates information about the storage resource and displays this updated information in the Storage Resources view.

To refresh storage resource information

1. In the StorageX Console, click the Storage Resources tab.

2. If you want to refresh the information displayed for all storage resources in the My Resources folder, browse to the Storage Resources > My Resources folder, right-click the My Resources folder, and then click Refresh.

3. If you want to refresh information about all storage resources in a custom folder under the Storage Resources > My Resources folder, right-click the custom folder, and then click Refresh.

4. If you want to refresh information displayed for a specific storage resource, right-click the storage resource, and then click Refresh.

StorageX Administrator’s Guide 121

Page 140: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Removing storage resources from My Resources2

5. If you want to refresh information displayed for a specific item, such as a CIFS shared folder or NFS export, right-click the item and then click Refresh.

Specifying file storage resource platform typeWhen you add file storage resources to the Storage Resources view, the Add File Storage Resources Wizard prompts you to provide the platform type for the file storage resource added, and StorageX displays the file storage resource type in the Properties dialog box on the Computer Properties tab.

NOTEOnce you add an object storage resource to StorageX, you cannot change the platform type for that resource. If you want to change the platform type for an existing object storage resource, you must remove the resource and add it again.

If you configure the wrong platform type for a file storage resource, StorageX may not display all of the appropriate properties tab for the file storage resource. For example, if you configure a Data ONTAP file storage resource as a Windows file storage resource, StorageX will not display the Credentials and Hosting Properties tabs for the Data ONTAP file storage resource.

If you incorrectly specify the platform type for a file storage resource displayed in My Resources, you can modify the properties for that file storage resource and specify the correct platform type.

To specify the platform type for a file storage resource

1. In the StorageX Console, click the Storage Resources tab.

2. In the center pane, select the resource you want to reconfigure, then click Actions > Set Platform Type.

3. On the Computer Properties tab, in the Platform Type field, select the appropriate file storage resource platform type from the list, and then click OK.

Removing storage resources from My ResourcesRemove a storage resource from the My Resources folder or a custom folder under My Resources when you no longer want to use StorageX to manage the storage resource.

If you added the storage resource to more than one custom folder under My Resources, StorageX only removes the storage resource from the custom folder you select. StorageX does not remove the storage resource from any other custom folders.

If you added a storage resource to multiple custom folders, you must remove the storage resource from each custom folder separately.

To remove a storage resource from My Resources

1. In the StorageX Console, click the Storage Resources tab.

2. In the center pane, select the storage resource you want to remove.

3. Click the Remove storage resource icon ( ).

4. Click OK to confirm.

122 StorageX Administrator’s Guide

Page 141: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Exporting storage resource import lists 2

Exporting storage resource import listsAfter you add and configure storage resources in your StorageX environment, you can export your storage resources as a .csv-format storage resource import list. You can then import the exported list into another StorageX installation, as long as the exported resources are accessible from the new installation.

You can export either the top-level My Resources folder or a specific subfolder within My Resources. If you export a folder that has subfolders, StorageX exports all resources, including those located within the subfolders.

NOTEYou cannot export a list of both file and object storage resources, but must instead export each resource type in a separate list.

To export a list of storage resources from My Resources

1. In the StorageX Console, click the Storage Resources tab.

2. If you want to export a list of file storage resources, right-click the My Resources folder or a specific subfolder and then click Export file storage resources.

3. If you want to export a list of object storage resources, right-click the My Resources folder or a specific subfolder and then click Export object storage resources.

4. Click OK to confirm.

5. Browse to the location where you want to export the list of storage resources as a .csv file, and then click Save. The user account you use to run the StorageX Console must have at least Write permissions on the folder that contains the .csv file.

Managing universal data enginesThis section explains how to manage universal data engines. It includes information about how to perform the following tasks:

• Specify default service account credentials for Windows data engines. For more information, see “Specifying default service account credentials for Windows data engines” on page 124.

• Manually deploy Windows data engines. For more information, see “Manually deploying Windows data engines” on page 124.

• Specify default universal data engine proxy computers. For more information, see “Specifying default universal data engine proxy computers” on page 127.

• View universal data engine status information. For more information, see “Viewing universal data engine status” on page 127.

• Stop, start, pause, and resume Windows data engines. For more information, see “Stopping, starting, pausing, and resuming Windows data engines” on page 128.

• Change Windows data engine service account credentials. For more information, see “Changing deployed Windows data engine service account credentials” on page 128.

• Create and manage universal data engine groups. For more information, see “Creating and managing universal data engine groups” on page 130

StorageX Administrator’s Guide 123

Page 142: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing universal data engines2

For more information about universal data engines, universal data engine computer requirements and service account requirements, and deploying universal data engines, see “Understanding StorageX universal data engines” on page 9, “Universal data engine computer requirements” on page 20, “Universal data engine service account requirements” on page 22, “Installing Windows data engines” on page 34, and “Installing and configuring Linux data engines” on page 35.

Specifying default service account credentials for Windows data enginesYou can specify default service account credentials for Windows data engines in the Control Panel view. When you specify default service account credentials for Windows data engines, all Windows data engines that StorageX deploys after you specify those default credentials will use the default service account credentials. However, service account credentials for Windows data engines already deployed by the StorageX server are not affected. For more information about changing the service account credentials for deployed Windows data engines, see “Changing deployed Windows data engine service account credentials” on page 128.

To specify default service account credentials for Windows data engines

1. In the StorageX Console, click the Control Panel tab.

2. In the left pane, click Deployed Data Engines.

3. In the center pane, click Manage Credentials.

4. Click Change.

5. In the User Name field, type the user account name for the service account you want to use as the default service account for universal data engines using the following format:

DomainName\UserAccountName

where DomainName is the name of the domain that the user account is a member of and UserAccountName is the name of a user account that meets Windows data engine service account requirements.

6. In the Password field, type the password for the service account you want to use for the default universal data engine service account.

7. In the Confirm field, type the password again.

8. Click OK.

Manually deploying Windows data enginesYou can enable StorageX to automatically deploy Windows data engines to manage data transfers. However, you can also manually deploy Windows data engines. For example, you may want to manually deploy Windows data engines under the following conditions:

• You want to deploy a Windows data engine to a file storage resource before you run a Phased Migration policy that uses the universal data engine on the file storage resource. Deploying the universal data engine manually before running the policy allows you to verify that the universal data engine was successfully deployed on the file storage resource before the policy runs.

• You may want to deploy a universal data engine to a universal data engine proxy computer and verify that the universal data engine deployed successfully before configuring Phased Migration policies that use the universal data engine on the proxy computer.

124 StorageX Administrator’s Guide

Page 143: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing universal data engines 2

NOTES:

• The Remote Registry service must be running on the computer where you want to deploy a Windows data engine. For information on enabling the Remote Registry service, see the Microsoft TechNet Library.

• If you manually deploy a Windows data engine using credentials other than the default universal data engine credentials and then upgrade the StorageX Console and StorageX server, upgrade the remote universal data engine using the Control Panel before using the data engine to run any policies. If StorageX tries to use a down-level remote Windows data engine to run a policy, the application cannot automatically upgrade the data engine. For more information about upgrading Windows data engines, see “Upgrading StorageX universal data engines” on page 55.

Before you manually deploy Windows data engines, ensure that you select the Allow universal data engine to be deployed to this host option on the storage resource. Also ensure that the Windows data engine service account has appropriate permissions on the computer where you want to deploy the universal data engine.

For example, the Windows replication service account must have Logon as a Service permissions on the computer where you want to deploy the data engine. For more information about universal data engine service account requirements, see “Universal data engine service account requirements” on page 22.

To manually deploy a Windows data engine

1. In the StorageX Console, click the Storage Resources tab.

2. In the left pane under Storage Resources > My Resources, browse to and right-click the Windows file storage resource where you want to manually deploy a Windows data engine, and then click Properties.

3. On the Computer Properties tab, select the Allow universal data engine to be deployed to this host check box, and then click OK.

4. Click the Control Panel tab.

5. In the left pane, click Deployed Data Engines.

6. In the center pane, click Deploy.

7. In the Host field, type the fully qualified domain name of the computer where you want to deploy the universal data engine or click the ellipsis button (...) to browse to and select the computer where you want to deploy the universal data engine.

8. If you want to specify a listening port other than 9452 for the universal data engine, in the Port field, type the number of the port you want the universal data engine to use.

By default, StorageX uses port 9452 to communicate with universal data engines. If you change the universal data engine listening port, make sure that the port you specify allows the StorageX server to communicate through any firewalls with the StorageX Console and universal data engines deployed by the StorageX server.

9. If you want to use the default service account credentials specified for universal data engine service accounts, click The default user name. For more information about specifying default universal data engine credentials, see “Specifying default service account credentials for Windows data engines” on page 124.

10. If you want to use one of the credentials in the credentials vault, click One of the credentials in the credentials vault, and then complete the following steps:

StorageX Administrator’s Guide 125

Page 144: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing universal data engines2

NOTEStorageX stores all the credentials currently specified or previously specified for StorageX server and universal data engine service accounts in a credentials vault. The credentials vault that StorageX uses is the built-in Local Security Authority (LSA) provided in the Windows operating system. This vault is accessible only to SYSTEM account processes, and credentials are stored in encrypted form on the hard disk drive. The Windows operating system uses LSA to store account passwords for Windows services that are configured on computers.

a. In the User name field, select the service account name from the list.

b. Click OK.

11. If you want to specify new credentials for the universal data engine service account, click The credentials specified below, and then complete the following steps:

NOTEBefore you specify new service account credentials for the universal data engine, ensure the new service account you specify meets universal data engine service account requirements. For more information about universal data engine service account requirements, see “Universal data engine service account requirements” on page 22.

a. In the User Name field, type the name of the user account you want to use for the universal data engine service account using the following format:

DomainName\UserAccountName

where DomainName is the name of the domain that the user account is a member of and UserAccountName is the name of a user account that meets Windows data engine service account requirements.

a. In the Password field, type the password for the user account you want to use for the universal data engine service account.

b. In the Confirm field, type the password again.

c. Click OK.

12. On the Alerts tab, verify that StorageX deployed the universal data engine successfully.

13. Click Refresh to display the new universal data engine.

Enabling deployment of Windows data engines on Windows file storage resourcesIf you have Windows file storage resources specified as sources or destinations in Phased Migration policies, you can configure StorageX to automatically deploy Windows data engines to destinations or sources when you run Phased Migration policies. To enable StorageX to deploy a Windows data engine on a storage resource, select the Allow universal data engine to be deployed to this host check box on the Computer Properties tab for the Windows file storage resource.

126 StorageX Administrator’s Guide

Page 145: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing universal data engines 2

To enable StorageX to automatically deploy a Windows data engine

1. In the StorageX Console, click the Storage Resources tab.

2. In the left pane under Storage Resources > My Resources, browse to and right-click the Windows file storage resource where you want to enable StorageX to automatically deploy a Windows data engine, and then click Properties.

3. On the Computer Properties tab, select the Allow universal data engine to be deployed to this host check box.

4. Click OK.

For more information about how StorageX uses universal data engines, including Windows data engines, see “Understanding StorageX universal data engines” on page 9.

Specifying default universal data engine proxy computersYou can specify a default universal data engine proxy computer for Phased Migration policies to use when transferring file data on Windows, Linux, Data ONTAP, VNX OE for File, and OneFS file storage resources.

When you specify a universal data engine proxy computer, StorageX uses the universal data engine on the proxy computer to migrate or replicate the appropriate file data.

To specify a universal data engine proxy computer

1. In the StorageX Console, click the Control Panel tab.

2. In the left pane, click Data Engine Proxies.

3. In the center pane, click New Proxy.

4. In the Host field, type the fully qualified domain name of the file storage resource for which you want to specify a universal data engine proxy computer or click the ellipsis (...) button to browse to and select the host.

5. In the Protocol field, select the protocol you want to use to move the file data.

6. If you want to associate the file storage resource with a universal data engine deployed on the StorageX server, click Use default proxy.

7. If you want to specify a specific universal data engine proxy computer for the file storage resource, click Use this specified proxy, and then select the universal data engine proxy computer from the list.

8. If you want to specify a universal data engine group for the file storage resource, click Use this specified data engine group and then select a group from the drop-down list. For more information about universal data engine groups, see “Creating and managing universal data engine groups” on page 130.

9. Click OK.

Viewing universal data engine statusYou can view information about the status, or health, of a universal data engine in the Control Panel view.

StorageX Administrator’s Guide 127

Page 146: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing universal data engines2

To view the status, or health, of a universal data engine

1. In the StorageX Console, click the Control Panel tab.

2. In the left pane, click Deployed Data Engines.

3. In the center pane, right-click the universal data engine you that you want to view the status for, and then click Check Health.

4. On the Alerts tab, review the alerts to see information about the status of the universal data engine.

Stopping, starting, pausing, and resuming Windows data enginesYou can stop, start, pause, and resume Windows data engines in the Control Panel view.

If you stop a Windows data engine when it is transferring data, the data transfer stops. Restarting the universal data engine does not restart the data transfer. The data transfer restarts when you run the policy manually or during the next scheduled run of the policy.

NOTEYou cannot stop, start, pause, or resume a Linux data engine from the Control Panel view. The Stop, Start, Pause, and Resume menu options are only available for Windows data engines.

To start, stop, pause, or resume a Windows data engine

1. In the StorageX Console, click the Control Panel tab.

2. In the left pane, click Deployed Data Engines.

3. If you want to stop a Windows data engine, in the right pane right-click the running universal data engine you want to stop, and then click Stop. StorageX stops the universal data engine and updates the status of the universal data engine to Not Running in the Status column. Click Refresh to view the updated status of the universal data engine.

4. If you want to start a stopped Windows data engine, in the right pane right-click the universal data engine you want to start, and then click Start. StorageX starts the universal data engine and updates the status of the universal data engine to Running in the Status column. Click Refresh to view the updated status of the universal data engine.

5. If you want to pause a running Windows data engine, in the right pane right-click the universal data engine you want to pause, and then click Pause. StorageX pauses the universal data engine and updates the status of the universal data engine to Paused in the Status column. Click Refresh to view the updated status of the universal data engine.

6. If you want to resume a paused Windows data engine, in the right pane right-click a paused universal data engine that you want to resume, and then click Resume. StorageX resumes the universal data engine and updates the status of the universal data engine to Running in the Status column. Click Refresh to view the updated status of the universal data engine.

Changing deployed Windows data engine service account credentialsYou can the credentials of deployed Windows data engines in the Control Panel view. Before you change the universal data engine service account credentials, review the requirements for Windows data engine service accounts. For more information, see “Windows data engine service account requirements” on page 23.

128 StorageX Administrator’s Guide

Page 147: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing universal data engines 2

To change deployed Windows data engine service account credentials

1. In the StorageX Console, click the Control Panel tab.

2. In the left pane, click Deployed Data Engines.

3. In the center pane, right-click the Windows data engine that you want to change universal data engine service account credentials for, and then click Change Credentials.

4. If you want to use the default service account credentials specified for Windows data engine service accounts, click The default user name. For more information about specifying default Windows data engine credentials, see “Specifying default service account credentials for Windows data engines” on page 124.

5. If you want to use one of the credentials in the credentials vault, click One of the credentials in the credentials vault, and then complete the following steps:

NOTEStorageX stores all the credentials currently specified or previously specified for StorageX server and universal data engine service accounts in a credentials vault. The credentials vault that StorageX uses is the built-in Local Security Authority (LSA) provided in the Windows operating system. This vault is accessible only to SYSTEM account processes, and credentials are stored in encrypted form on the hard disk drive. The Windows operating system uses LSA to store account passwords for Windows services that are configured on computers.

a. In the User name field, select the service account name from the list.

b. Click OK.

6. If you want to specify new credentials for the universal data engine service account, click The credentials specified below, and then complete the following steps:

NOTEBefore you specify new service account credentials for the universal data engine, ensure the new service account you specify meets Windows data engine service account requirements. For more information about Windows data engine service account requirements, see “Windows data engine service account requirements” on page 23.

a. In the User Name field, type the name of the user account you want to use for the universal data engine service account using the following format:

DomainName\UserAccountName

where DomainName is the name of the domain that the user account is a member of and UserAccountName is the name of a user account that meets Windows data engine service account requirements.

b. In the Password field, type the password for the user account you want to use for the universal data engine service account.

c. In the Confirm field, type the password again.

d. Click OK.

For more information about universal data engines and deploying universal data engines, see “Understanding StorageX universal data engines” on page 9 and “Installing Windows data engines” on page 34.

StorageX Administrator’s Guide 129

Page 148: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing universal data engines2

Creating and managing universal data engine groupsUse universal data engine groups if you want to distribute data transfer workloads or increase the performance and availability of universal data engines when transferring data using Phased Migration policies. You can use universal data engine groups with Phased Migration policies to specify which universal data engine or universal data engine group you want to perform data transfer operations. For more information about assigning universal data engine groups to policies, see “Distributing file data transfer workloads using universal data engine groups” on page 248.

To use universal data engine groups, create the universal data engine group, add universal data engines to the group, and then assign the group to a policy. After you create universal data engine groups and associate them with policies, StorageX can perform the following actions:

• If a computer where a universal data engine is installed is not available, StorageX can use a different universal data engine in the group to run the policy.

• If a data transfer operation specified by the policy contains multiple tasks, StorageX can distribute the workload among universal data engines in the group.

NOTEA universal data engine can belong to only one universal data engine group. There is no limit to the number of universal data engines each universal data engine group can contain.

To create and manage universal data engine groups

1. In the StorageX Console, click the Control Panel tab.

2. In the left pane, click Deployed Data Engines.

3. In the right pane, click Manage Data Engine Groups...

4. If you want to create a universal data engine group, complete the following steps:

a. Click Create Group.

b. In the Group Name field, type a name for the group.

c. In the Group Description field, type a description for the group.

d. Click OK.

5. If you want to delete a universal data engine group, complete the following steps:

a. Select the universal data engine group you want to delete from the Group drop-down box.

b. Click Delete Group.

6. If you want to assign a universal data engine to a universal data engine group, complete the following steps:

a. Select the universal data engine group you want to modify from the Group drop-down box.

b. Select the data engine you want to assign to that group in the Data Engines Not In Any Group pane on the left.

c. Click the Right arrow button to move that data engine into the Data Engines In Selected Group pane on the right.

7. If you want to remove a universal data engine from a universal data engine group, complete the following steps:

130 StorageX Administrator’s Guide

Page 149: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Changing StorageX server service account credentials 2

a. Select the universal data engine group you want to modify from the Group drop-down box.

b. Select the data engine you want to remove from that group in the Data Engines In Selected Group pane on the right.

c. Click the Left arrow button to move that data engine into the Data Engines Not In Any Group pane on the left.

Changing StorageX server service account credentialsUse the Windows Services snap-in to change credentials for the StorageX server service account. You cannot change the StorageX server service account credentials in the StorageX Console.

To change StorageX server service account credentials

1. Connect to the computer where the StorageX server is installed.

2. Open the Windows Services snap-in.

3. Right-click the StorageX Server service, and then click Stop.

4. After the StorageX server service stops, right-click the StorageX Server service again, and then click Properties.

5. On the Log On tab, specify new credentials for the StorageXserver service account, and then click OK.

NOTEIf you are specifying a different user account for the StorageX server service account, ensure that the account you specify has Log on as a service permissions on the computer where the StorageX server is installed.

6. Right-click the StorageX Server service, and then click Start to restart the StorageX server service.

Working with StorageX eventsThis section explains how to work with StorageX events. It includes the following topics:

• “Viewing StorageX events” on page 131

• “Filtering events” on page 132

Viewing StorageX eventsStorageX displays events for items in the Data Movement view, the Migration Projects view, the Control Panel view, and the Storage Resources view.

To view StorageX events

1. Select the item for which you want to view events in the Data Movement view, the Migration Projects view, the Control Panel view, or in the Storage Resources view.

2. In the center pane, on the Events tab, review event information.

StorageX Administrator’s Guide 131

Page 150: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Working with StorageX events2

Filtering eventsBy default, StorageX displays all of the event history for items on the Events tab. You can also filter event information. For example, you may want to filter events if you only want to see the most recent events for items.

To filter events

1. Select the item that you want to view events for in the Data Movement view, the Migration Projects view, the Control Panel view, or in the Storage Resources view.

2. In the center pane, click the Events tab, and then click Filter.

3. Specify the event types you want to filter by completing the following actions:

• If you want to display informational events about successful operations, select the Information check box.

• If you want to display warning events that may indicate future problems, select the Warning check box.

• If you want to display events about significant problems, select the Error check box.

4. If you want to filter events by event source, in the Event source field, select the event source for which you want to display events.

5. If you want to filter events by category, in the Category field, select the category for which you want to display events.

6. If you want to filter events by event ID, in the Event ID field, type the event ID for which you want to filter.

7. If you want to filter events by user, in the User field, type the name of the user for which you want to display events. Type the name of the user using the exact user name syntax that displays in the User field of an event.

8. If you want to filter events by computer, in the Computer field, type the name of the computer for which you want to filter events. Type the name of computer using the exact computer name syntax that displays in the Computer field of an event.

9. If you want to filter events and only show events that occurred during a specific time, complete the following actions:

a. In the From field, select Events On, and then specify a start date and time from which you want to display events.

b. In the To field, select Events On, and then specify an end date and time for which you want to display events.

10. If you want to display all events in the log, complete the following actions;

a. In the From field, select First Event.

b. In the To field, select Last Event.

11. If you want to return all event filtering options to the default StorageX options, click Restore Defaults.

12. Click OK.

132 StorageX Administrator’s Guide

Page 151: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring email notification profiles 2

Configuring email notification profilesThis section explains how to configure email notification profiles to use with different types of policies in the StorageX Console, as well as in the StorageX Retrieval Portal.

To configure email notification options

1. In the StorageX Console, click File > Options.

2. Click the Notification Profile Properties tab.

3. If you want to modify an existing notification profile, complete the following steps:

a. Select the profile you want to modify.

b. Click Edit.

c. Make changes to profile settings as necessary and click OK.

4. If you want to create a new notification profile, complete the following steps:

a. Click New.

b. Specify the SMTP settings you want to use for the new profile. For more information about the SMTP settings, click the Help button on the dialog box.

c. Specify the message settings you want to use for the new profile. For more information about the message settings, click the Help button on the dialog box.

d. Click Send Test Message to verify the profile settings are correct.

e. If you want to use the new notification profile for all notifications, click Enable all usage of this notification.

f. Click OK.

5. When finished, click OK.

Working with scheduled tasksThis section explains how to work with scheduled tasks in StorageX. You can use the Calendar tab in the Control Panel view to view, modify, or delete schedules configured for policies, reports, and other universal data engine and StorageX server tasks in StorageX.

NOTEYou cannot modify scheduled Server Maintenance tasks. Tasks of this type are internal StorageX tasks and cannot be changed in the calendar.

This section includes the following topics:

• “Viewing scheduled tasks” on page 134

• “Modifying scheduled tasks” on page 135

• “Deleting scheduled tasks” on page 136

StorageX Administrator’s Guide 133

Page 152: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Working with scheduled tasks2

For more information about configuring schedules for policies, see “Scheduling Phased Migration policies” on page 263, “Scheduling Archival Migration policies” on page 297, “Scheduling Disaster Recovery policies” on page 384, “Scheduling Replication policies” on page 403, “Scheduling Namespace Availability policies” on page 219, and “Scheduling Namespace Availability policies” on page 219. For more information about configuring schedules for reports, see “Creating reports” on page 423.

Viewing scheduled tasksStorageX displays all scheduled tasks in the Calendar tab of the Control Panel view. You can use the options in the ribbon to view scheduled tasks by day, week, or month, and you can filter tasks so that the calendar only displays the tasks you want to see.

You can view tasks by type using any of the following types:

• Phased Migration

• Replication

• Archival Migration

• Monitoring

• Discovery

• Namespace Backup

• Namespace Availability

• Reporting

• Server Maintenance

Tasks in the calendar are color-coded by type so that you can more easily identify the types of task you have configured at any given time.

You can also group tasks by universal data engine, migration source, or migration destination.

To view scheduled tasks

1. In the StorageX Console, click the Control Panel tab.

2. In the left pane, click Calendar.

3. If you want to view scheduled tasks for a particular day, click Arrange > Day View in the ribbon.

4. If you want to view scheduled tasks in a particular week, click Arrange > Week View in the ribbon.

5. If you want to view scheduled tasks in a particular month, click Arrange > Month View in the ribbon.

6. If you want to view all scheduled tasks for a specific date range, complete the following steps:

a. In the right-side multi-month calendar, click the date you want to use as the start of the date range.

b. Use the Ctrl or Shift buttons to select other dates in the date range you want to view. The Console automatically adjusts the view to fit the range selected.

7. If you only want to view specific types of scheduled tasks, select or clear types in the Data Engine Tasks or Server Tasks area of the ribbon, as necessary.

134 StorageX Administrator’s Guide

Page 153: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Working with scheduled tasks 2

8. If you only want to view scheduled tasks related to one or more specific universal data engines, complete the following steps:

a. In the ribbon, click Data Engine.

b. In the Data engines to Display area of the ribbon, click the drop-down menu and select one or more data engines for which you want to view scheduled tasks.

c. Click OK.

9. If you only want to view scheduled tasks for one or more specific source or destination storage resources, complete the following steps:

a. In the ribbon, click Source Or Destination.

b. In the Sources or Destinations to Display area of the ribbon, click the drop-down menu and select one or more storage resources for which you want to view scheduled tasks.

c. Click OK.

10. If you want to remove any universal data engine, source, or destination filtering from the calendar, in the ribbon, click Ungroup.

Modifying scheduled tasksYou can modify any scheduled task either by modifying the policy or report that uses the configured schedule or by modifying the task itself in the Calendar tab.

ATTENTIONWhen you modify a recurring scheduled task in the Calendar tab, you are modifying every instance of the recurring task in the entire configured schedule, not just one occurrence of the task.

To modify scheduled tasks in the Calendar tab

1. In the StorageX Console, click the Control Panel tab.

2. In the left pane, click Calendar.

3. In the calendar, navigate to the scheduled task you want to modify.

4. If you want to move a scheduled task to a different time, click the task and drag and drop it to the time slot you want within the day displayed in the calendar.

NOTEYou cannot drag a daily, hourly, or per-minute scheduled task to a different day in the calendar. You can only modify the time at which the daily, hourly, or per-minute task occurs.

5. If you want to move a one-time or weekly scheduled task to a different day, click the task and drag and drop it to the day to which you want to move the task, either in the Week View, Month View, or right-side overview calendar.

NOTEYou cannot drag a weekly scheduled task to a day for which the task is already configured on the calendar.

6. If you want to set a specific duration for a scheduled task, complete the following steps:

StorageX Administrator’s Guide 135

Page 154: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Working with scheduled tasks2

a. Click the top or bottom edge of the task in the calendar.

b. Drag the edge of the task up or down, as necessary, to configure the task duration.

c. Click Yes to confirm.

NOTEIf you configure a duration for a scheduled task, the task will stop once the specified duration period has been exceeded, even if the task itself is not completed.

7. If you want to modify multiple properties for a scheduled task, complete the following steps:

a. Double-click the scheduled task.

b. In the Properties window, make changes to the configured schedule, as necessary.

c. Click OK.

Deleting scheduled tasksYou can delete a scheduled task either by modifying the policy or report that uses the configured schedule or by deleting the task itself in the Calendar tab.

NOTES:

• When you delete a scheduled task in the Calendar tab, you are deleting every instance of the scheduled task in the entire configured schedule, not just one occurrence of the scheduled task.

• If you delete a scheduled task for a particular policy or report and then want to re-configure a schedule for that policy or report, you must navigate to the policy or report, view the policy or report Properties, and manually configure the schedule there.

To delete one or more scheduled tasks in the Calendar tab

1. In the StorageX Console, click the Control Panel tab.

2. In the left pane, click Calendar.

3. If you want to delete one scheduled task, navigate to and select the task in the calendar.

4. If you want to delete multiple scheduled tasks at one time, use the Ctrl or Shift keys to select multiple tasks in the calendar.

5. Right-click the selected task or tasks and select Delete.

6. Click Yes to confirm.

136 StorageX Administrator’s Guide

Page 155: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX Administrator’s Guide

Chapter

3

Provisioning Storage Resources

This section explains how to provision heterogeneous file and object storage resources using the Storage Resources view.

In this chapter•Understanding provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

•Provisioning operating system requirements . . . . . . . . . . . . . . . . . . . . . . . 138

•Creating and managing CIFS shared folders. . . . . . . . . . . . . . . . . . . . . . . . 139

•Creating and managing NFS exports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

•Creating and managing Data ONTAP volumes and qtrees . . . . . . . . . . . . . 149

•Creating and managing Data ONTAP SnapMirrors . . . . . . . . . . . . . . . . . . . 152

•Creating and managing object storage resource buckets . . . . . . . . . . . . . 157

137

Page 156: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding provisioning3

Understanding provisioningAfter you add storage resources to My Resources in the Storage Resources view, you can use StorageX as a central management console to provision heterogeneous file and object storage resources. For example, you can use StorageX to perform the following provisioning tasks:

• Create CIFS shared folders on file storage resources that support the CIFS protocol

For example, you can use StorageX to create CIFS shared folders on Windows, Data ONTAP, VNX OE for File, and OneFS file storage resources.

• Create NFS exports on file storage resources that support the NFS protocol

For example, you can use StorageX to create NFS shared folders on Linux, Data ONTAP, VNX OE for File, and OneFS file storage resources.

• If you have Data ONTAP file storage resources, you can create and manage volumes and qtrees on those Data ONTAP file storage resources, as well as create and manage SnapMirrors.

NOTEYou cannot create new FlexGroups or modify existing FlexGroups on Data ONTAP resources using StorageX.

• If you have IBM Cloud Object Storage (IBM COS) object storage resources, you can create buckets on those IBM COS object storage resources.

For more information about using StorageX as a central management console to provision heterogeneous file and object storage resources, see the following topics:

• “Creating and managing CIFS shared folders” on page 139

• “Creating and managing NFS exports” on page 145

• “Creating and managing Data ONTAP volumes and qtrees” on page 149

• “Creating and managing Data ONTAP SnapMirrors” on page 152

• “Creating and managing object storage resource buckets” on page 157

Provisioning operating system requirementsIn order to perform provisioning tasks, file and object storage resources must be running one of the following operating systems:

TABLE 14 Supported operating systems for provisioning tasks

Operating System Versions

Windows • Windows Server 2003 or later• Windows Server 2008 or later• Windows Server 2012 or later• Windows Server 2016 or later

Linux • Red Hat Linux 6• Red Hat Linux 7

Data ONTAP 7G • 7.3.1 V-Series• 7.3.2 NetApp Storage Systems

138 StorageX Administrator’s Guide

Page 157: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing CIFS shared folders 3

Creating and managing CIFS shared foldersThis section explains how you can create and manage CIFS shared folders on file storage resources managed by StorageX that support the CIFS protocol and meet provisioning operating system requirements. This section includes the following topics:

• “Understanding the CIFS protocol” on page 139

• “Creating CIFS shared folders” on page 140

• “Viewing CIFS shared folder properties” on page 142

• “Viewing CIFS shared folder contents” on page 142

• “Cloning CIFS shared folders” on page 143

For more information about provisioning operating system requirements, see “Provisioning operating system requirements” on page 138.

Understanding the CIFS protocolThe Common Internet File System (CIFS) protocol is commonly used with Windows systems. Client computers use the CIFS protocol to request file and print services from server systems over a network. With CIFS, a client computer program makes a request to a server program, typically on another computer, to access file data or to pass a message to a program that runs on the server computer. The server processes the request and returns a response. CIFS is a public, or open, variation of the Server Message Block (SMB) Protocol developed and used by Microsoft. The SMB Protocol is widely used in local area networks for server file access and printing.

Data ONTAP 8 • 8.0.2 7-Mode• 8.0.3 7-Mode• 8.0.4 7-Mode• 8.0.5 7-Mode• 8.1 7-Mode• 8.1.1 7-Mode• 8.1.2 7-Mode• 8.2 Cluster Mode• 8.2 7-Mode• 8.3 Cluster Mode

ONTAP 9 • 9.0• 9.1

VNX OE for File • 7.1.47• 8.1

OneFS • 7.0.X• 7.1.X• 7.2.X• 8.0

IBM Cloud Object Storage

• Any S3-compliant IBM COS object storage resource

TABLE 14 Supported operating systems for provisioning tasks

Operating System Versions

StorageX Administrator’s Guide 139

Page 158: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing CIFS shared folders3

Creating CIFS shared foldersYou can use the Share Creation Wizard to create CIFS shared folders on file storage resources managed by StorageX that support the CIFS protocol.

In order to use the Share Creation Wizard to create CIFS shared folders on file storage resources that support the CIFS protocol, the StorageX server service account must have appropriate permissions on each file storage resource where you want to create CIFS shared folders. For more information about the StorageX server service account, see “StorageX server service account requirements” on page 16.

If you are creating a CIFS shared folder on a Windows file storage resource, the Share Creation Wizard allows you to create both the folder and the share in one operation.

If you are creating a CIFS shared folder on a different type of file storage resource, such as a Data ONTAP, VNX OE for File, or OneFS file storage resource, you must first create the folder you want to share on the file storage resource using a native tool such as NetApp OnCommand System Manager for Data ONTAP file storage resources, EMC Unisphere for VNX OE for File file storage resources, or One FS for OneFS file storage resources. After you create the folder you want to share, you can then use StorageX to share the folder.

If you use DFS namespaces, after you create shared folders, you can create a DFS link for the shared folders or add the shared folders you created as a target to a new or existing DFS link. The Share Creation Wizard steps you through the process for not only creating a shared folder, but also for creating a DFS link for the shared folder or adding the shared folders as a target to a new or existing DFS link.For more information about DFS namespaces and DFS links, see “Creating and Managing DFS Namespaces” on page 159.

NOTEWhen you create a new CIFS shared folder on a Data ONTAP Vserver in the Storage Resources view using the Share Creation wizard, when you click Finish, the StorageX user interface immediately refreshes. However, the new CIFS shared folder does not immediately display in the list of CIFS shared folders on the Data ONTAP Vserver. This is because the Data ONTAP Vserver has not yet finished initializing the new CIFS shared folder. To work around this issue, right-click the parent folder, and then click Refresh. After the refresh, the new CIFS shared folder should now display in the list of CIFS shared folders on the Data ONTAP Vserver.

To create a CIFS shared folder

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under Storage Resources > My Resources, browse to and select the file storage resource where you want to create the share.

NOTEIf the file storage resource is a VNX OE for File file storage resource, select the VNX OE for File Data Mover. You create CIFS shared folders on the VNX OE for File Data Mover, and not on the file storage resource that hosts the VNX OE for File Data Mover.

3. Right-click the file storage resource where you want to create the CIFS shared folder, and then click Create Share.

4. Review the welcome message, and then click Next.

5. Specify properties for the CIFS shared folder by completing the following steps:

140 StorageX Administrator’s Guide

Page 159: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing CIFS shared folders 3

a. In the Local path field, specify the local path for the folder that will be shared.

If you are creating a CIFS shared folder on a Windows file storage resource, type the local path to an existing folder or type the path to use for a new folder using the appropriate Windows syntax. For example, type DriveLetter:\FolderName\FolderName, where DriveLetter is the drive letter on the file storage resource, and FolderName is the name of an existing folder that you want to share or the name of a new folder that you want to create and share in one operation.

If you are creating a CIFS shared folder on a Data ONTAP file storage resource, type the local path to an existing folder using the appropriate Data ONTAP syntax. For example, type /vol/VolumeName/FolderName, where VolumeName is the appropriate volume name and FolderName is the name of the folder to be shared.

If you are creating a CIFS shared folder on an VNX OE for File file storage resource, type the local path to an existing folder or tree quota using the appropriate VNX OE for File path syntax. For example, type /MountPath where MountPath is the path where the file system is mounted.

If you are creating a CIFS shared folder on a OneFS file storage resource, type the local path to an existing folder using the appropriate OneFS syntax. For example, type /ifs/Path where Path is the path to the folder you want to share.

b. In the Name field, type a name for the CIFS shared folder.

c. In the Comment field, type a word or phrase that describes the CIFS shared folder.

d. Specify user limits for the CIFS shared folder and permissions for users who will access the CIFS shared folder by selecting the appropriate options. For more information about each option, click the Help button on the dialog box.

e. Click Next.

6. If you do not want to add the CIFS shared folder to a DFS link, click Do not modify any DFS links, and then click Next and Finish.

7. If you want to add the new CIFS shared folder, as a target, to a new DFS link, complete the following steps:

a. Click Add the new share, as a target, to a new DFS link, and then click Next.

b. Browse to and select the DFS namespace or a folder in a DFS namespace where you want to host the new DFS link for the CIFS shared folder, and then click Next.

c. In the Name field, type a name for the new DFS link, in the Comment field, type a word or phrase that describes the new DFS link, specify how long you want client computers to cache link information for, and then click Next.

d. Click Finish.

8. If you want to add the new CIFS shared folder as a target to an existing DFS link, complete the following steps:

a. Click Add the new shares, as target, to an existing DFS link, and then click Next.

b. Browse to and select an existing DFS link that will target the new CIFS shared folder, and then click Next.

c. Click Finish.

StorageX Administrator’s Guide 141

Page 160: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing CIFS shared folders3

Viewing CIFS shared folder propertiesYou can use StorageX to view the properties of a CIFS shared folder for a file storage resource managed by StorageX in the Storage Resources view. The Storage Resources view displays both shared folders that participate in DFS namespaces as well as shared folders that do not participate in DFS namespaces.

In order to view CIFS shared folder properties on file storage resources that support the CIFS protocol, the StorageX server service account must have appropriate permissions on each file storage resource. For more information about the StorageX server service account, see “StorageX server service account requirements” on page 16.

NOTEStorageX displays the CIFS shared folder information returned by the file storage resource that hosts the shared folder. StorageX may not display some CIFS shared folder information, such as local paths and connection limits, if the file storage resource hosting the CIFS shared folder does not provide this information.

To view CIFS shared folder properties

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under Storage Resources > My Resources, browse to and select the file storage resource with the CIFS shared folder you want to view properties for.

3. Expand the Shares folder to display a list of CIFS shared folders on the file storage resource.

4. Right-click the CIFS shared folder you want to view properties for, and then click Properties.

5. StorageX displays the properties for the CIFS shared folder. For more information about each property, click the Help button on the dialog box.

Viewing CIFS shared folder contentsYou can use StorageX to view the contents of a CIFS shared folder or folder under a CIFS share folder for a file storage resource managed by StorageX in the Storage Resources view. The Storage Resources view displays both shared folders that participate in DFS namespaces as well as shared folders that do not participate in DFS namespaces.

In order to view the contents of a CIFS shared folder or a folder under a CIFS shared folder on file storage resources that support the CIFS protocol, the StorageX server service account must have appropriate permissions on each file storage resource. For more information about the StorageX server service account, see “StorageX server service account requirements” on page 16.

To view the contents of a CIFS shared folder

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under Storage Resources > My Resources, browse to and select the file storage resource with the CIFS shared folder you want to view the contents of.

3. Expand the Shares folder to display a list of CIFS shared folders on the file storage resource.

4. Right-click the CIFS shared folder you want to view the contents of, and then click Explorer.

5. StorageX uses Windows Explorer to display the contents of the CIFS shared folder.

142 StorageX Administrator’s Guide

Page 161: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing CIFS shared folders 3

Cloning CIFS shared foldersYou can use the StorageX Share Creation Wizard to quickly duplicate, or clone, multiple CIFS shared folders from a source file storage resource to a destination file storage resource.

You can specify whether you want to clone all of the CIFS shared folders on a source file storage resource to a destination file storage resource, or if you want to clone only a few of the CIFS shared folders on the source file storage resource to the destination file storage resource.

If you are cloning a CIFS shared folder on a source file storage resource to a Windows file storage resource destination, the Share Creation Wizard allows you to create both the folders and the shares on the destination file storage resource as needed. Consider the following examples:

• If the destination folders do not already exist on the Windows file storage resource, the Share Creation Wizard creates the folders on the destination Windows file storage resource as well as shares the folders on the Windows destination in one operation.

• If the destination folders already exist on the Windows file storage resource, the Share Creation Wizard simply shares the existing folders on the destination.

If you are cloning a CIFS shared folder on a non-Windows destination file storage resource, such as a Data ONTAP, VNX OE for File, or OneFS destination file storage resource, you must first create the folder you want to share on the destination file storage resource using a native tool such as NetApp OnCommand System Manager for Data ONTAP file storage resources, EMC Unisphere for VNX OE for File file storage resources, or One FS for OneFS file storage resources. After you create the folder you want to share on the destination, you can then use the Share Creation Wizard to clone CIFS shared folders from the source to the destination.

When StorageX clones shares, StorageX clones the share settings on the source share to the destination share. However, StorageX does not clone share security settings for local users or groups from the source to the destination. StorageX clones only security settings for local built-in accounts on the source to the destination, such as the local Admin account. StorageX does not clone security settings for other local users or groups.

If you use a DFS namespace in your environment, you can use the Share Creation Wizard to duplicate, or clone, only the CIFS shared folders referenced by a DFS namespace on the source file storage resource to the destination file storage resource.

If you use a Phased Migration policy to migrate data stored in a CIFS shared folder with additional nested CIFS shared folders underneath the parent folder, after you run the Phased Migration policy and migrate the data, you can use the Share Creation Wizard to quickly and easily re-share the nested CIFS shared folders under the parent CIFS shared folder as needed.

NOTES:

• If the StorageX service account cannot access the share you want to clone, you may need to configure a default administrative share on the resource to allow StorageX to complete the share cloning process. For more information about configuring default administrative shares, see “Configuring default administrative shares” on page 114.

• When you use StorageX to duplicate, or clone, CIFS shared folders, StorageX does not copy the file data stored in the source CIFS shared folders to the new destination CIFS shared folders. If you want to copy the file data in the source CIFS shared folders to the destination CIFS shared folders, create Phased Migration policies to copy the file data. For more information about creating Phased Migration policies, see “Creating Phased Migration policies” on page 250.

StorageX Administrator’s Guide 143

Page 162: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing CIFS shared folders3

To clone CIFS shared folders

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under Storage Resources > My Resources, browse to and select the file storage resource with the CIFS shared folders you want to duplicate.

3. Right-click the file storage resource, and then click Clone Shares.

4. Review the welcome message, and then click Next.

5. In the Source field, verify that the name of the source file storage resource is the file storage resource with the CIFS shared folders you want to duplicate.

6. If you want to display hidden CIFS shared folders on the source file storage resource so you can view and select hidden CIFS shared folders to duplicate when needed, select the Show Hidden Shares check box.

7. In the Destination field, type the name of the destination file storage resource where you want to duplicate the CIFS shared folders, or click Browse to browse to and select the destination file storage resource.

8. Click Next.

9. In the left column, select each source CIFS shared folder you want to duplicate. The CIFS shared folders listed in the Source share column will be duplicated to the corresponding path listed in the New Share column. Clear the check box for any CIFS shared folder you do not want to duplicate.

If you want to change the name of the CIFS shared folder on the destination, click the name of the new share on the destination, and then specify a new name for the CIFS shared folder.

10. Click Next.

11. Verify the suggested local path for the destination CIFS shared folders you want to create, and complete the following steps as needed:

a. If your destination file storage resource is a CIFS file storage resource and you want to change the local path for a specific destination CIFS shared folder, select the destination folder, click Edit Path, and then browse to and select a new local path.

This option is available only for CIFS file storage resources.

b. If you want to change the local path for multiple destination CIFS shared folders, click Edit Path, and then in the Replace this portion of the path field, type the portion of the local path for the destination shared folder that you want to replace or click Browse, and then browse to and select the updated portion of the local path for the destination shared folder. After you select the updated portion of the path, the updated portion of the path displays in the with field. Click OK.

You can use this option if the local path for the CIFS shared folders on the destination file storage resource is slightly different than the local path on the destination file storage resource. This option allows you to quickly specify a different local path for multiple destination shared folders in one option.

c. Click Next.

d. Click Finish.

144 StorageX Administrator’s Guide

Page 163: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing NFS exports 3

Creating and managing NFS exportsThis section explains how you can create and manage NFS exports on file storage resources managed by StorageX that support the NFS protocol and meet provisioning operating system requirements. This section includes the following topics:

• “Understanding the NFS protocol” on page 145

• “Creating NFS exports” on page 145

• “Viewing NFS export properties” on page 147

• “Cloning NFS exports” on page 147

For more information about provisioning operating system requirements, see “Provisioning operating system requirements” on page 138.

Understanding the NFS protocolThe Network File System (NFS) protocol, originally developed by Sun Microsystems, allows client computers running the NFS protocol to access files over a network as if the files were located on the client computer’s local hard drive. Mounted files that are stored in several different locations can appear to be organized into one tree-structure directory, and are accessible without any passwords or special commands.

NFS uses a client/server architecture and consists of a client program, a server program, and a protocol used to communicate between the two.

• The server program makes file systems available for access by other computers using a process called exporting. File systems that are available for access across the network are often referred to as exported file systems.

• NFS client computers access shared file systems by mounting them from an NFS server computer. When a file system is mounted, it is integrated into the directory tree. An advanced form of this service is the automounter, which automatically mounts and unmounts file systems on an as-needed basis.

NFS is commonly used by Linux, Data ONTAP, VNX OE for File, and OneFS file storage resources. Many other platforms also use the protocol. Like many other protocols, NFS builds on the Open Network Computing Remote Procedure Call (ONC RPC) system.

Creating NFS exportsYou can use StorageX to create NFS exports on file storage resources managed by StorageX that support the NFS protocol in the Storage Resources view.

The NFS service must be running on the file storage resource that is exporting the NFS file system.

You also must first create the folder you want to export on the file storage resource using a native tool such as NetApp OnCommand System Manager for Data ONTAP file storage resources, EMC Unisphere for VNX OE for File file storage resources, or One FS for OneFS file storage resources. After you create the folder you want to export on the file storage resource using native tools, you can then use StorageX to create the NFS export.

If the folder you want to export does not exist, StorageX displays an error asking you to specify an existing local path on the file storage resource when you try to create the NFS export.

StorageX Administrator’s Guide 145

Page 164: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing NFS exports3

If you want to create NFS exports on Linux file storage resources, you must configure SSH shell credentials for StorageX to use to communicate with each of Linux file storage resource where you want to create NFS exports before you can create NFS exports. For more information, see “Configuring StorageX to Use SSH Shell Credentials” on page 433.

NOTES:

• If your environment includes Data ONTAP 8.2 or earlier Vservers or SVMs, you can use StorageX to view exports on those resources, but you cannot create exports on Data ONTAP 8.2 or earlier Vservers or SVMs using StorageX.

• If your environment includes OneFS resources, you cannot use StorageX to create or manage User Space NFS (uNFS) exports or aliased NFS exports.

To create an NFS export

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under Storage Resources > My Resources, browse to and select the file storage resource where you want to create the NFS export.

NOTEIf the file storage resource is a VNX OE for File file storage resource, select the VNX OE for File Data Mover. You create NFS exports on the VNX OE for File Data Mover, and not on the file storage resource that hosts the VNX OE for File Data Mover.

3. Right-click the file storage resource where you want to create the export, and then click Create Export.

4. Specify the local path of an existing folder, volume, or qtree on the destination for the NFS export.

The local path you specify must already exist on the destination file storage resource. The syntax used to specify the local path varies based on the type of file storage resource.

If you are creating an NFS export on a Linux file storage resource, type the local path to an existing folder on the destination in the Local path field, using the appropriate Linux syntax, or click Browse to browse to and select an existing folder on the destination. For example, type /LocalPath, where LocalPath is the path the to folder on the Linux file storage resource that you want export.

If you are creating an NFS export on a non-virtual Data ONTAP file storage resource, type the local path to an existing folder on the destination in the Local path field, using the appropriate Data ONTAP syntax, or click Browse to browse to and select an existing folder on the destination. For example, type /vol/VolumeName/FolderName, where VolumeName is the appropriate volume name and FolderName is the name of the folder that you want to export.

If you are creating an NFS export on a Data ONTAP Vserver or SVM, type the local path to an existing volume or qtree on the destination in the Volume/Qtree path field, using the appropriate Data ONTAP syntax, or click Browse to browse to and select an existing volume or qtree on the destination. For example, type /vol/VolumeName, where VolumeName is the name of the volume or qtree that you want to export.

If you are creating an NFS export on an VNX OE for File file storage resource, type the local path to an existing folder or tree quota on the destination in the Local path field, using the appropriate VNX OE for File path syntax, or click Browse to browse to and select an existing folder or tree quota on the destination. For example, type /MountPath where MountPath is the path where the file system is mounted.

146 StorageX Administrator’s Guide

Page 165: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing NFS exports 3

If you are creating an NFS export on a OneFS file storage resource, type the local path to an existing folder on the destination in the Local path field, using the appropriate OneFS syntax, or click Browse to browse to and select an existing folder on the destination. For example, type /ifs/Path where Path is the path to the folder you want to export.

5. Specify how you want to publish the NFS export by selecting the appropriate options. For more information about each option, click the Help button on the dialog box.

6. Click OK.

Viewing NFS export propertiesYou can use StorageX to view the properties of any NFS export on a file storage resource managed by StorageX that supports the NFS protocol. The Storage Resources view displays both NFS exports used in automount map files as well as exports that are not used in automount map files.

To view NFS export properties using StorageX, the StorageX server service account must have Administrator or root access permissions on each file storage resource in order to view all exports. For more information, see “StorageX server service account requirements” on page 16.

To view NFS export properties

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under Storage Resources > My Resources, browse to and select the file storage resource with the NFS export you want to view the properties of.

3. Expand the Exports folder for the file storage resource to display a list of NFS exports on the file storage resource.

4. Select the NFS export you want to view properties for.

5. In the center pane, in the General area, review the NFS export properties. For more information about each property, click the Help button on the dialog box.

Cloning NFS exportsYou can use the StorageX Clone Exports Wizard to quickly duplicate, or clone, multiple NFS exports from a source file storage resource to a destination file storage resource. You can specify whether to clone all the NFS exports on the source file storage resource, or only selected NFS exports.

The NFS service must be running on the file storage resource that is exporting the NFS file system.

You also must first create the folders for the NFS exports you want to clone on the destination file storage resource using a native tool such as NetApp OnCommand System Manager for Data ONTAP file storage resources, EMC Unisphere for VNX OE for File file storage resources, or One FS for OneFS file storage resources. After you create the folders for the NFS exports you want to clone on the destination file storage resource using native tools, you can then use StorageX to clone the NFS exports from the source to the destination.

If the folders do not exist on the destination, when you try to clone NFS exports from the source to the destination, an error will display in the wizard asking you to specify an existing local path on the destination before you can continue.

StorageX Administrator’s Guide 147

Page 166: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing NFS exports3

If you want to clone NFS exports to a destination Linux file storage resource, you must configure SSH shell credentials for StorageX to use to communicate with the destination resource where you want to clone NFS exports before you can clone the NFS exports. For more information, see “Configuring StorageX to Use SSH Shell Credentials” on page 433.

ATTENTIONWhen you use StorageX to clone NFS exports, StorageX does not copy the file data stored in the source NFS exports to the destination NFS exports. If you want to copy the file data stored in the source NFS exports to the destination NFS exports, create Phased Migration policies to move the file data. For more information, see “Creating Phased Migration policies” on page 250.

To clone NFS exports

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under Storage Resources > My Resources, browse to and select the file storage resource with the NFS exports you want to duplicate.

3. Right-click the file storage resource, and then click Clone Exports.

4. Review the welcome message, and then click Next.

5. Specify the source and destination by completing the following steps:

a. In the Source field, verify that the name of the source file storage resource with the NFS exports you want to duplicate is correct. If you want to change the source file storage resource, click Browse to browse to and select a different source file storage resource.

b. In the Destination field, type the fully qualified domain name of the destination file storage resource where you want to duplicate the NFS exports, or click Browse to browse to and select a destination file storage resource.

c. Click Next.

6. In the left column of the Specify Exports to Duplicate dialog box, select each source NFS export you want to duplicate. The NFS folders listed in the Source column will be duplicated to the corresponding path listed in the Destination column. Clear the check box for any NFS export you do you want to duplicate.

7. In the Destination column, verify the local path for the destination NFS exports you want to create.

8. If you want to change the local path for a specific destination NFS export, select the click the destination path, click Edit Path, and then type in a new local path. You can only edit the path for one destination export at a time.

9. Click Next.

10. Review the paths for the source and destination NFS exports, and then click Finish to create the exports on the destination.

148 StorageX Administrator’s Guide

Page 167: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing Data ONTAP volumes and qtrees 3

Creating and managing Data ONTAP volumes and qtreesThis section explains how you can create volumes and qtrees on Data ONTAP file storage resources managed by StorageX ad that meet provisioning operating system requirements. This section includes the following topics:

• “Creating volumes on Data ONTAP file storage resources” on page 149

• “Creating qtrees on Data ONTAP file storage resources” on page 150

• “Viewing qtree properties on Data ONTAP file storage resources” on page 151

• “Sharing qtrees on Data ONTAP file storage resources” on page 151

• “Deleting qtrees on Data ONTAP file storage resources” on page 152

For more information about provisioning operating system requirements, see “Provisioning operating system requirements” on page 138.

NOTEYou cannot create new FlexGroups or modify existing FlexGroups on Data ONTAP resources using StorageX.

Creating volumes on Data ONTAP file storage resourcesIf you use StorageX to manage Data ONTAP file storage resources, you can create traditional and flex volumes on Data ONTAP file storage resources using StorageX.

To create a volume on a Data ONTAP file storage resource

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under Storage Resources > My Resources, browse to and select the file storage resource where you want to create the volume.

3. Right-click the file storage resource where you want to create a volume, and then click Create Volume.

4. Review the welcome message, and then click Next.

5. If the Volume Type dialog box displays, specify whether you want to create a traditional volume or flex volume, and then click Next.

If you are creating a volume on a Data ONTAP vFiler, Data ONTAP 8 cluster, or ONTAP 9 cluster, StorageX does not display the Volume Type dialog box. The Volume Settings - Flex Volume dialog box displays. This is because you can create only flex volumes on Data ONTAP Vservers, SVMs, and vFilers.

If you are creating a volume on a Data ONTAP 7 or Data ONTAP 8 7-Mode file storage resource, StorageX displays the Volume Type dialog box. Specify whether you want to create a traditional volume or flex volume, and then click Next.

6. If you want to create a flex volume, complete the following steps:

a. In the Volume Name field, type the name of the volume. The name can contain alphanumeric characters and underscores (_). The first character must be a letter or an underscore.

b. Specify other volume settings as appropriate, and then click Next. For more information about each setting, click the Help button on the dialog box.

StorageX Administrator’s Guide 149

Page 168: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing Data ONTAP volumes and qtrees3

c. Click Finish to create the volume.

7. If you want to create a traditional volume, complete the following steps:

a. In the Volume Name field, type the name of the volume. The name can contain alphanumeric characters and underscores (_). The first character must be a letter or an underscore.

b. Specify other volume settings as appropriate, and then click Next. For more information about each setting, click the Help button on the dialog box.

c. Click Next.

d. Specify the disks to use for the new volume by specifying the appropriate settings, and then click Next. For more information about each setting, click the Help button on the dialog box.

e. Click Finish to create the volume.

Creating qtrees on Data ONTAP file storage resourcesIf you manage Data ONTAP file storage resources that support qtrees, you can use StorageX to create qtrees on the Data ONTAP file storage resources. A qtree is a logically defined file system on a Data ONTAP file storage resource that can exist as a special subdirectory of the root directory within a volume. You can create a qtree when you want to partition data within a volume. For example, you might create a qtree if you want to specify user-based or workgroup-based quotas to limit the amount of storage space specified users or workgroups can use on a qtree. When you create a qtree, you can assign one of the following security styles to the qtree:

• NTFS

• UNIX

• Mixed security

NOTEYou cannot use StorageX to create a qtree on an ONTAP 9.1 FlexGroup.

To create a qtree on a Data ONTAP file storage resource

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under Storage Resources > My Resources, browse to the file storage resource with the volume where you want to create the qtree.

3. Browse to the volume where you want to create the qtree.

4. Right-click the volume, and then click Create Qtree.

5. In the QTree Name field, type a name for the qtree.

6. In the Style field, select the appropriate security style.

7. In the Oplocks field, specify if you want CIFS oplocks, or opportunistic locks, enabled or disabled.

8. Click OK.

150 StorageX Administrator’s Guide

Page 169: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing Data ONTAP volumes and qtrees 3

Viewing qtree properties on Data ONTAP file storage resourcesYou can use StorageX to view qtree properties for qtrees on Data ONTAP file storage resources.

The Storage Resources view displays both qtrees that participate in DFS namespaces well as qtrees that do not participate in DFS namespaces.

To view qtree properties

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under the Storage Resources folder, expand the folder that contains the file storage resource with the qtree that you want to view properties for, and then expand the volume for the file storage resource with the qtree.

3. Right-click the qtree you want to view properties for, and then click Properties.

4. StorageX displays the properties for the qtree. For more information about each property, click the Help button on the dialog box.

Sharing qtrees on Data ONTAP file storage resourcesYou can use StorageX to share qtrees on Data ONTAP file storage resources.

To share a qtree on a Data ONTAP file storage resource

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under the Storage Resources folder, expand the folder that contains the file storage resource with the qtree you want to share.

3. Browse to the volume with the qtree you want to share.

4. Right-click the qtree you want to share, and then click Share this QTree.

5. Review the welcome message, and then click Next.

a. In the Name field, type a name for the shared qtree.

b. In the Comment field, type a word or phrase that describes the shared qtree.

c. Specify user limits for the shared qtree and permissions for users who will access the shared qtree by selecting the appropriate options. For more information about each option, click the Help button on the dialog box.

d. Click Next.

6. If you do not want to add the shared qtree to a DFS link, click Do not modify any DFS links, and then click Next and Finish.

7. If you want to add the new shared qtree, as a target, to a new DFS link, complete the following steps:

a. Click Add the new share, as a target, to a new DFS link, and then click Next.

b. Select the DFS namespace that you want to host the new DFS link for the shared qtree, and then click Next.

c. In the Name field, type a name for the new DFS link, in the Comment field, type a word or phrase that describes the new DFS link, specify how long you want client computers to cache link information for, and then click Next.

StorageX Administrator’s Guide 151

Page 170: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing Data ONTAP SnapMirrors3

d. Click Finish.

8. If you want to add the new shared folder as a target to an existing DFS link, complete the following steps:

a. Click Add the new shares, as target, to an existing DFS link, and then click Next.

b. Select an existing DFS link that will target the new share, and then click Next.

c. Click Finish.

Deleting qtrees on Data ONTAP file storage resourcesYou can use StorageX to delete qtrees on Data ONTAP file storage resources.

In order to delete a qtree, the qtree must not be shared or have any data stored in it. If the qtree is shared or data is stored in it, you will not be able to delete the qtree.

To delete a qtree on a Data ONTAP file storage resource

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under the Storage Resources folder, expand the folder that contains the file storage resource with the qtree you want to delete.

3. Browse to the volume with the qtree you want to delete.

4. Right-click the qtree you want to delete, and then click Delete.

5. Click Yes to confirm you want to delete the qtree.

Creating and managing Data ONTAP SnapMirrorsThis section explains how you can create SnapMirrors on Data ONTAP file storage resources managed by StorageX and that meet provisioning operating system requirements. This section includes the following topics:

• “Understanding SnapMirrors” on page 153

• “Creating SnapMirrors on Data ONTAP file storage resources” on page 153

• “Initializing SnapMirrors on Data ONTAP file storage resources” on page 154

• “Quiescing and resuming SnapMirrors on Data ONTAP file storage resources” on page 154

• “Updating SnapMirrors on Data ONTAP file storage resources” on page 155

• “Interrupting SnapMirror data transfers on Data ONTAP file storage resources” on page 155

• “Breaking SnapMirror relationships on Data ONTAP file storage resources” on page 156

• “Deleting SnapMirrors from StorageX for Data ONTAP file storage resources” on page 157

If you have Data ONTAP file storage resources you want to include in a Migration Project, you can also generate SnapMirror reports. SnapMirror reports allow you to identify SnapMirror relationships that exist between Data ONTAP file storage resources in your environment. For more information about Migration Projects and SnapMirror reports, see “Creating and Managing Migration Projects” on page 319 and “Generating Data ONTAP SnapMirror reports” on page 338.

For more information about provisioning operating system requirements, see “Provisioning operating system requirements” on page 138.

152 StorageX Administrator’s Guide

Page 171: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing Data ONTAP SnapMirrors 3

Understanding SnapMirrorsSnapMirror software on Data ONTAP file storage resources creates SnapMirrors by replicating data from a source volume or qtree to another volume or qtree called a mirror. The SnapMirror software then periodically updates the mirror to reflect incremental changes on the source. When you use SnapMirror software to create a SnapMirror, you have an online, read-only mirror, or volume, that contains the same data as the source volume at the time of the most recent update. SnapMirrors allow users to access mirrored data in the event of a disaster that makes the source volume or qtree unavailable. You can also use the SnapMirror to update the source when you need to recover from a qtree data corruption issue or user error.

For more information about using StorageX to create SnapMirrors, see “Creating SnapMirrors on Data ONTAP file storage resources” on page 153.

Creating SnapMirrors on Data ONTAP file storage resourcesYou can use StorageX to create SnapMirrors on Data ONTAP file storage resources.

If you are creating SnapMirrors on Data ONTAP 7.x file storage resources or vFilers, ensure you enable the SnapMirror feature on the file storage resource. You must enable the SnapMirror feature on Data ONTAP 7 file storage resources or vFilers before you can create SnapMirrors using StorageX. Steps for enabling SnapMirrors and setting SnapMirror options vary based on the type of Data ONTAP file storage resource you are using.

For more information about enabling SnapMirrors and configuring SnapMirror options on Data ONTAP file storage resources, see the Data ONTAP® Data Protection Online Backup and Recovery Guide For 7-Mode, available on the NetApp Support web site at https://library.netapp.com/ecmdocs/ECMP1368826/html/frameset.html.

If you are creating SnapMirrors on Data ONTAP 8 file storage resources, ensure you understand the following requirements:

• In Data ONTAP 8, the SnapMirror feature is enabled by default. However, you must create the SnapMirrors on the cluster management node interface. You cannot create SnapMirrors on Vservers or SVMs.

• When you create SnapMirrors on Data ONTAP 8 file storage resources using StorageX, if the destination for the SnapMirror is outside of the cluster, you must create a cluster peer relationship between the source and destination using a native Data ONTAP tool such as NetApp OnCommand System Manager. This peer relationship must be created between the two clusters before you create the SnapMirror.

• When you create SnapMirrors on Data ONTAP 8 file storage resources using StorageX, first created the restricted volume for the SnapMirror using a native Data ONTAP tool such as NetApp OnCommand System Manager. After you created the restricted volume, you can then select it when you create the SnapMirror.

To create a SnapMirror on a Data ONTAP file storage resource

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under the Storage Resources folder, browse to the Data ONTAP file storage resource, volume or qtree that you want to create a SnapMirror for.

3. Right-click the Data ONTAP file storage resource, volume or qtree that you want to create a SnapMirror for, and then click Create SnapMirror.

StorageX Administrator’s Guide 153

Page 172: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing Data ONTAP SnapMirrors3

4. On the Source and Destination tab, specify the destination where you want to create the SnapMirror.

NOTEYou must specify a new qtree as the destination qtree. Data ONTAP does not support using an existing qtree as the destination when creating a SnapMirror on a qtree. When StorageX creates the SnapMirror, StorageX also creates the new qtree on the destination. If the destination qtree already exists, StorageX will not be able to successfully create the SnapMirror. Type the destination qtree name without the volume prefix for the qtree.

For more information about each field, click the Help button on the dialog box.

5. On the Options and Schedule tab, specify the replication schedule as appropriate. For more information about each setting, click the Help button on the dialog box.

6. Click OK.

Initializing SnapMirrors on Data ONTAP file storage resourcesAfter you create a new SnapMirror, you must initialize the SnapMirror before you can use it in a Phased Migration or Disaster Recovery policy.

For detailed information about initializing SnapMirrors, see the Data ONTAP® Data Protection Online Backup and Recovery Guide For 7-Mode, available on the NetApp Support web site at https://library.netapp.com/ecmdocs/ECMP1368826/html/frameset.html.

To initialize a SnapMirror

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under the Storage Resources folder, browse to the Data ONTAP file storage resource that hosts the SnapMirror you want to initialize.

3. Right-click the SnapMirror, and then click Actions > Initialize. The State displayed in the center pane changes to snapmirrored.

Quiescing and resuming SnapMirrors on Data ONTAP file storage resourcesAfter you initialize a SnapMirror, the SnapMirror remains in snapmirrored state and continues to transfer data per its configured schedule.

If you want to disable a SnapMirror and stop the next scheduled transfer, you can use StorageX to quiesce the SnapMirror. When you want to re-enable the SnapMirror, you can then use StorageX to resume the SnapMirror.

NOTES:

• You cannot quiesce a SnapMirror that has not been initialized.

• If you quiesce a SnapMirror currently being used to transfer data, you must manually resume the data transfer. StorageX does not automatically restart SnapMirror data transfers when the SnapMirror is quiesced. In addition, any policy currently using the SnapMirror to transfer data will not correctly display the number of bytes copied in the manifest.

154 StorageX Administrator’s Guide

Page 173: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing Data ONTAP SnapMirrors 3

For detailed information about quiescing and resuming SnapMirrors, see the Data ONTAP® Data Protection Online Backup and Recovery Guide For 7-Mode, available on the NetApp Support web site at https://library.netapp.com/ecmdocs/ECMP1368826/html/frameset.html.

To quiesce or resume a SnapMirror

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under the Storage Resources folder, browse to the Data ONTAP file storage resource that hosts the SnapMirror you want to quiesce or resume.

3. If you want to disable the SnapMirror, right-click the SnapMirror, and then click Actions > Quiesce. The State displayed in the center pane changes to quiesced.

4. If you want to re-enable the SnapMirror, right-click the SnapMirror, and then click Actions > Resume. The State displayed in the center pane changes to snapmirrored.

Updating SnapMirrors on Data ONTAP file storage resourcesBy default, SnapMirrors automatically update based on the schedule configured in the /etc/snapmirror.conf file on the Data ONTAP file storage resource. However, you can manually force a SnapMirror to update using StorageX.

NOTEYou cannot update a quiesced SnapMirror. Initialize the SnapMirror, then update.

For detailed information about updating SnapMirrors, see the Data ONTAP® Data Protection Online Backup and Recovery Guide For 7-Mode, available on the NetApp Support web site at https://library.netapp.com/ecmdocs/ECMP1368826/html/frameset.html.

To update a SnapMirror

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under the Storage Resources folder, browse to the Data ONTAP file storage resource that hosts the SnapMirror you want to update.

3. Right-click the SnapMirror, and then click Actions > Update.

Interrupting SnapMirror data transfers on Data ONTAP file storage resourcesIf a SnapMirror is currently updating or transferring data and you need to stop the transfer process, you can manually interrupt the transfer using StorageX.

NOTEYou can only interrupt a SnapMirror if the SnapMirror is updating or otherwise transferring data.’

For detailed information about interrupting SnapMirrors, see the Data ONTAP® Data Protection Online Backup and Recovery Guide For 7-Mode, available on the NetApp Support web site at https://library.netapp.com/ecmdocs/ECMP1368826/html/frameset.html.

StorageX Administrator’s Guide 155

Page 174: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing Data ONTAP SnapMirrors3

To interrupt a SnapMirror

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under the Storage Resources folder, browse to the Data ONTAP file storage resource that hosts the SnapMirror you want to interrupt.

3. Right-click the SnapMirror, and then click Actions > Interrupt. The Status displayed in the center pane changes to idle.

Breaking SnapMirror relationships on Data ONTAP file storage resourcesYou can use StorageX to break Data ONTAP SnapMirror relationships on file storage resources in the Storage Resources view.

For detailed information about breaking SnapMirror relationships, see the Data ONTAP® Data Protection Online Backup and Recovery Guide For 7-Mode, available on the NetApp Support web site at https://library.netapp.com/ecmdocs/ECMP1368826/html/frameset.html.

To break a SnapMirror relationship

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under the Storage Resources folder, browse to the Data ONTAP file storage resource that hosts the SnapMirror with the relationship you want to break.

3. Right-click the SnapMirror, and then click Actions > Quiesce.

NOTEIf you quiesce a SnapMirror currently being used to transfer data, you must manually resume the data transfer. StorageX does not automatically restart SnapMirror data transfers when the SnapMirror is quiesced. In addition, any policy currently using the SnapMirror to transfer data will not correctly display the number of bytes copied in the manifest.

4. In the center pane, when the State field displays quiesced, right-click the SnapMirror again, and then click Actions > Break to break the SnapMirror relationship.

Resyncing SnapMirrors on Data ONTAP file storage resourcesIf you break a Data ONTAP SnapMirror relationship and then need to use that SnapMirror, you can use StorageX to resync the SnapMirror and re-establish the broken relationship.

For detailed information about resyncing SnapMirrors, see the Data ONTAP® Data Protection Online Backup and Recovery Guide For 7-Mode, available on the NetApp Support web site at https://library.netapp.com/ecmdocs/ECMP1368826/html/frameset.html.

To resync a SnapMirror

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under the Storage Resources folder, browse to the Data ONTAP file storage resource that hosts the SnapMirror with the relationship you want to re-establish.

3. Right-click the SnapMirror, and then click Actions > Resync. The State displayed in the center pane changes to snapmirrored.

156 StorageX Administrator’s Guide

Page 175: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing object storage resource buckets 3

Deleting SnapMirrors from StorageX for Data ONTAP file storage resourcesYou can delete existing SnapMirrors from StorageX for Data ONTAP file storage resources.

ATTENTIONIf you delete a SnapMirror from StorageX, you can no longer resume or resync the SnapMirror. Also, deleting a SnapMirror in StorageX does not delete the SnapMirror from Data ONTAP, but instead leaves the SnapMirror in Data ONTAP in a broken-off state.

For detailed information about deleting SnapMirrors, see the Data ONTAP® Data Protection Online Backup and Recovery Guide For 7-Mode, available on the NetApp Support web site at https://library.netapp.com/ecmdocs/ECMP1368826/html/frameset.html.

To delete a SnapMirror

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under the Storage Resources folder, browse to the Data ONTAP file storage resource that hosts the SnapMirror you want to delete.

3. Right-click the SnapMirror, and then click Delete.

4. Click OK to confirm.

Creating and managing object storage resource bucketsThis section explains how you can create and manage buckets on S3-compliant object storage resources. This section includes the following topics:

• “Creating object storage resource buckets” on page 157

• “Viewing object storage resource bucket properties” on page 158

For more information about provisioning operating system requirements, see “Provisioning operating system requirements” on page 138.

NOTEIn the current version of StorageX, you cannot delete or modify a bucket created on an S3-compliant object storage resource.

Creating object storage resource bucketsYou can create new buckets on S3-compliant resources from the Storage Resources view of the StorageX Console.

To create a bucket on an S3-compliant object storage resource

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under Storage Resources > My Resources, browse to and select the S3-compliant object storage resource where you want to create the bucket.

3. Expand the object storage resource.

StorageX Administrator’s Guide 157

Page 176: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing object storage resource buckets3

4. Right-click Buckets and select Create Bucket.

5. In the Bucket Name field, specify the name you want to use for the new bucket.

6. Click OK.

Viewing object storage resource bucket propertiesYou can use StorageX to view the properties of a bucket on an S3-compliant object storage resource managed by StorageX in the Storage Resources view. The Storage Resources view displays both buckets created both inside and outside of StorageX.

To view S3-compliant object storage resource bucket properties

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane under Storage Resources > My Resources, browse to and select the S3-compliant object storage resource with the bucket you want to view properties for.

3. Expand the Buckets folder to display a list of buckets on the object storage resource.

4. Select the bucket you want to view properties for.

5. In the Summary pane, view the available properties for the selected bucket.

NOTEIf your user account does not have Full Control to the selected bucket, the StorageX Console does not display the permissions for the bucket in the Permissions field.

158 StorageX Administrator’s Guide

Page 177: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX Administrator’s Guide

Chapter

4

Creating and Managing DFS Namespaces

This section discusses DFS namespaces. It explains what DFS namespaces are and the different types of DFS namespaces you can create with StorageX. It also explains what the different DFS namespace components are, such as DFS namespace servers and DFS links, how to create and manage these components in StorageX, and how to synchronize, back up, and restore DFS namespaces using StorageX.

In this chapter•Checklist: DFS namespace planning and implementation. . . . . . . . . . . . . 160

•Understanding DFS namespaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

•DFS namespace operating system requirements. . . . . . . . . . . . . . . . . . . . 166

•Understanding DFS namespace validation checks. . . . . . . . . . . . . . . . . . . 169

•Creating and configuring DFS namespaces . . . . . . . . . . . . . . . . . . . . . . . . 169

•Managing DFS namespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

•Creating domain-based DFS namespace servers . . . . . . . . . . . . . . . . . . . . 189

•Managing domain-based DFS namespace servers . . . . . . . . . . . . . . . . . . 190

•Adding DFS links to DFS namespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

•Managing DFS links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

•Searching for DFS objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

•Converting stand-alone namespaces to domain-based namespaces. . . . 214

•Synchronizing DFS namespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

•Backing up and restoring DFS namespaces . . . . . . . . . . . . . . . . . . . . . . . . 220

•Configuring email notification options for Namespace policies. . . . . . . . . 224

159

Page 178: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Checklist: DFS namespace planning and implementation4

Checklist: DFS namespace planning and implementationThis checklist guides you through the planning and implementation of a DFS namespace. Before you implement a DFS namespace using StorageX, ensure you understand DFS namespaces, their components, and the different types of namespaces you can create with StorageX. For more information, see “Understanding DFS namespaces” on page 161.

If you already have existing DFS namespaces in your environment that you want to manage with StorageX, add your existing DFS namespaces in StorageX. Once you add your existing DFS namespaces in StorageX, you can begin to use StorageX to manage the namespace. For more information, see “Adding DFS namespaces to My Resources” on page 186”.

TABLE 15 Checklist: DFS namespace planning and implementation

Task

1 Identify the types of users in your environment that you want to access file data on file storage resources using a DFS namespace. Also identify the types of client computers used by these users.

2 Identify the applications in your environment that access file data on file storage resources that you want to include in the DFS namespace.

3 Determine what type of DFS namespace you want to implement. For more information about the different types of DFS namespaces and how the different types of DFS namespaces work, see “Understanding DFS namespaces” on page 161.

4 Review DFS namespace operating system requirements. For more information, see “DFS namespace operating system requirements” on page 166

5 Review the DFS namespace configuration requirements for the type of DFS namespace you want to implement. For more information about DFS namespace configuration requirements, see the following topics:• “Domain-based DFS namespace configuration requirements” on page 169• “Stand-alone DFS namespace configuration requirements” on page 172• “Consolidation DFS namespace configuration requirements” on page 175

6 Create the DFS namespace. For more information about creating a DFS namespace, see the following topics:• “Creating domain-based DFS namespaces” on page 171• “Creating stand-alone DFS namespaces” on page 173• “Creating consolidation DFS namespaces” on page 176

7 If you created a domain-based DFS namespace, create additional domain-based DFS namespace servers as needed. For more information, see “Creating domain-based DFS namespace servers” on page 189.

8 Add DFS links to your namespace. For more information, see “Adding DFS links to DFS namespaces” on page 193.

160 StorageX Administrator’s Guide

Page 179: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding DFS namespaces 4

Understanding DFS namespacesA DFS namespace is a single, logical view of folders and file data distributed across primary and extended file storage resources. A DFS namespace allows you to logically unify file data distributed across multiple file storage resources and transparently provide users with access to data. With a DFS namespace, you can logically organize and view files and folders across file storage resources based on your organization’s needs. For example, you can logically organize file data by department or by geographic region.

If you have already implemented a DFS namespace in your environment, you can quickly and easily improve your file storage resource capacity management by adding existing DFS namespaces to StorageX. For more information, see “Adding DFS namespaces to My Resources” on page 186.

If you have not yet implemented DFS namespaces in your environment, you can use StorageX to create DFS namespaces and perform DFS namespace management tasks.

For more information about DFS namespaces, see the following topics:

• “DFS Namespace components” on page 161

• “How DFS namespaces work” on page 162

• “Understanding DFS namespace size limits and recommendations” on page 163

• “Understanding DFS namespace types” on page 164

DFS Namespace componentsA DFS namespace consists of the following components:

DFS namespace folderShared folder at the top of a DFS namespace topology that stores the logical structure of the DFS namespace.

DFS namespace serverServer that contains a shared folder with copies of the logical structure of a DFS namespace and increases the availability of the DFS namespace by providing an alternate path for DFS links for fault tolerance and load balancing.

DFS linkFile that contains reference information for a CIFS shared folder or a folder under a CIFS shared folder in a different location on the network.

DFS link targetCIFS shared folder or folder under a CIFS shared folder that the DFS link references.

StorageX Administrator’s Guide 161

Page 180: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding DFS namespaces4

How DFS namespaces workYou create DFS namespaces on a Windows server computer. The following section describes how a DFS namespace works when a user initially requests the contents of a folder called Engineering that is targeted by a DFS link in a DFS namespace. It also describes how a DFS namespace works when a user repeats a request for the contents of the Engineering folder targeted by a DFS link in a DFS namespace.

Initial Request in a DFS namespace

The following figure illustrates what happens when a user initially requests the contents of a folder called Engineering that is a target of a DFS link in a DFS namespace.

The following steps explain what happens when a user initially requests the contents of a folder called Engineering that is the target of a DFS link in a DFS namespace:

1. A user on a client computer requests the contents of the Engineering folder by typing in a folder path or clicking on a mapped drive. For example, the user types \\Domain.com\DFSNamespace, where Domain.com is the name of the domain that hosts the DFS namespace, and DFSNamespace is the name of the namespace.

2. A domain controller in the specified domain receives the client computer request, accesses Active Directory to obtain a list of UNC paths to DFS namespace servers, and provides the list of DFS namespace servers to the client computer.

3. The client computer processes the list of UNC paths to DFS namespace servers and connects to an available DFS namespace server.

4. DFS performs the following actions:

a. Obtains namespace configuration information from the DFS namespace server.

b. Reads the namespace configuration information stored on the DFS namespace server

c. Identifies a DFS link for the Engineering folder

d. Reads the DFS link and determines that the contents of the Engineering folder are currently stored on FileStorageResource-01.

162 StorageX Administrator’s Guide

Page 181: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding DFS namespaces 4

e. Provides referral information obtained from the DFS namespace server for the contents of the Engineering folder to the client computer.

5. The client computer caches the referral information for the Engineering folder and then requests the contents of the Engineering folder from FileStorageResource-01.

6. FileStorageResource-01 receives the request for the contents of the Engineering folder from the client computer and returns the contents of the Engineering folder to the client computer.

Repeat Request in a DFS namespace

The following figure shows what happens when a user repeats a request for the contents of a folder called Engineering that is the target of a DFS link in a DFS namespace.

The following steps explain what happens when a user on the client computer repeats a request for the contents of the Engineering folder:

1. The client computer repeats a request for the contents of the Engineering folder. The client computer uses the cached referral information obtained previously from the DFS namespace server to access the Engineering folder on FileStorageResource-01 directly. The client computer does not access the DFS namespace server again to obtain referral information.

2. FileStorageResource-01 forwards the contents of the Engineering folder to the client computer.

Understanding DFS namespace size limits and recommendationsBefore you create a DFS namespace, ensure you understand DFS namespace size limits and recommendations from Microsoft. For the latest information on DFS namespace size limits and recommendations, review the DFS namespace information provided by Microsoft.

The following article, “DFS Namespace Scalability Considerations,” provides detailed information for DFS namespaces:

https://blogs.technet.microsoft.com/filecab/2012/08/26/dfs-namespace-scalability-considerations/

StorageX Administrator’s Guide 163

Page 182: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding DFS namespaces4

Understanding DFS namespace typesThe first step in creating a DFS namespace is to decide on the type of namespace you want to create. Then create the appropriate DFS namespace of the type you want.

After you create the DFS namespace, you add DFS links to the DFS namespace that target CIFS shared folders or folders under CIFS shared folders. CIFS shared folders are shared folders created with the CIFS file sharing protocol used in Windows-based networks. The CIFS protocol defines a standard for remote file access using millions of computers at a time. With CIFS, users with different platforms and computers can share files without having to install new software.

You can use StorageX to create the following types of namespaces:

• Domain-based DFS namespaces

• Stand-alone DFS namespaces

• Consolidation DFS namespaces

Create a domain-based DFS namespace if any of the following conditions apply to your environment:

• You want to ensure the availability of the namespace by using multiple DFS namespace servers.

• You want to hide the name of the primary DFS namespace server from users. This makes it easier to replace the namespace server or migrate the namespace to another server.

• If you choose to create a domain-based DFS namespace, you must also choose a domain-based DFS namespace mode. Fore more information, see “Choosing a domain-based DFS namespace mode” on page 164 and “Comparing DFS namespace types and modes” on page 165.

Create a stand-alone DFS namespace if any of the following conditions apply to your environment:

• Your organization does not use Active Directory Domain Services.

• You want to increase the availability of the namespace by using a failover cluster.

• You need to create a single namespace with more than 5,000 DFS folders in a domain that does not meet the requirements for a domain-based DFS namespace (Windows Server 2008 mode). For more information, see “Choosing a domain-based DFS namespace mode” on page 164 and “Comparing DFS namespace types and modes” on page 165.

Consolidation DFS namespaces are special stand-alone namespaces. Consolidation DFS namespaces reduce the impact of file server consolidation or migration on end users by maintaining the original Universal Naming Convention (UNC) paths of files and folders when they are copied to a new file storage resource. Because the original UNC paths are maintained, you do not need to inform users about new server names, and line-of-business applications as well as shortcuts and OLE links in user files and e-mail messages continue to work after the consolidation or migration is complete. For more information about consolidation DFS namespaces, see “Understanding consolidation DFS namespaces” on page 175.

Choosing a domain-based DFS namespace mode

If you want to create a domain-based DFS namespace, you must choose whether to use the Windows 2000 Server mode or the Windows Server 2008 mode when you create the namespace.

164 StorageX Administrator’s Guide

Page 183: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding DFS namespaces 4

The Windows Server 2008 mode includes support for access-based enumeration and increased scalability. The older domain-based namespace introduced in Windows 2000 Server does not support these features, and is now referred to as "domain-based namespace (Windows 2000 Server mode)".

To use the Windows Server 2008 mode, the domain and DFS namespace must meet the following minimum requirements:

• The forest uses the Windows Server 2003 or higher forest functional level.

• The domain uses the Windows Server 2008 domain functional level.

• All DFS namespace servers are running Windows Server 2008 or later.

If your environment supports using domain-based DFS namespaces in Windows Server 2008 mode, choose the Windows Server 2008 mode when you create new domain-based DFS namespaces. This mode provides additional features and scalability, and also eliminates the possible need to migrate a namespace from the Windows 2000 Server mode.

If your environment does not support domain-based namespaces in Windows Server 2008 mode, use the existing Windows 2000 Server mode for the namespace.

If you create a Windows 2000 Server mode DFS namespace and then upgrade your environment, you can use StorageX to upgrade the existing namespace to Windows Server 2008 mode. For more information about upgrading a DFS namespace, see “Upgrading DFS namespaces to Windows Server 2008 mode” on page 184.

Comparing DFS namespace types and modes

The following table compares the features of different DFS namespace types and modes that you can create using StorageX.

TABLE 16 Comparing DFS namespace types and modes

Characteristic Domain-based DFS namespace (Windows 2000 server mode)

Domain-based DFS namespace (Windows Server 2008 mode)

Stand-alone DFS namespace

Consolidation DFS namespace

Path to namespace \\NetBIOSDomainName\NamespaceName

\\DNSDomainName\NamespaceName

\\NetBIOSDomainName\NamespaceName

\\DNSDomainName\NamespaceName

\\ServerName\NamespaceName

\\ServerName\#ConsolidatedServerName or\\ConsolidatedServerName

\\ConsolidatedServerName will work only after DNS changes have been committed

Namespace information storage location

In Active Directory Domain Services and in a memory cache on each namespace server

In Active Directory Domain Services and in a memory cache on each namespace server

In the registry and in a memory cache on the namespace server

In the registry and in a memory cache on the namespace server

StorageX Administrator’s Guide 165

Page 184: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

DFS namespace operating system requirements4

Before you create a DFS namespace, review DFS namespace server operating system requirements and DFS namespace client computer operating system requirements. For more information, see “DFS namespace server operating system requirements” on page 167 and “DFS namespace client computer operating system requirements” on page 168.

DFS namespace operating system requirementsWhen creating and managing DFS namespaces, ensure you understand operating system requirements for the following DFS components:

Namespace size recommendations

The size of the namespace object in Active Directory Domain Services should be less than 5 megabytes (MB) to maintain compatibility with domain controllers that are not running Windows Server 2008. This means no more than approximately 5,000 folders with targets.

The namespace can contain more than 5,000 folders with targets; the recommended limit is 50,000 folders with targets

The namespace can contain more than 5,000 folders with targets; the recommended limit is 50,000 folders with targets

The namespace can contain more than 5,000 folders with targets; the recommended limit is 50,000 folders with targets

Minimum Active Directory Domain Services forest functional level

Windows 2000 Windows Server 2003

Active Directory Domain Services is not required

Active Directory Domain Services is not required

Minimum Active Directory Domain Services domain functional level

Windows 2000 mixed

Windows Server 2008 or later

Active Directory Domain Services is not required

Active Directory Domain Services is not required

Minimum supported namespace servers

Windows 2000 Server

Windows Server 2008 or later

Windows 2000 Server

Windows 2000 Server

Support for access-based enumeration (if enabled)

No Yes Yes, requires Windows Server 2008 namespace server

No

Supported methods to ensure namespace availability

Use multiple namespace servers to host the namespace. (The namespace servers must be in the same domain.)

Use multiple namespace servers to host the namespace. (The namespace servers must be in the same domain.)

Create a stand-alone namespace on a failover cluster

Create a consolidated namespace on a failover cluster

TABLE 16 Comparing DFS namespace types and modes

Characteristic Domain-based DFS namespace (Windows 2000 server mode)

Domain-based DFS namespace (Windows Server 2008 mode)

Stand-alone DFS namespace

Consolidation DFS namespace

166 StorageX Administrator’s Guide

Page 185: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

DFS namespace operating system requirements 4

• DFS namespace servers. For more information, see “DFS namespace server operating system requirements” on page 167.

• DFS client computers. For more information, see “DFS namespace client computer operating system requirements” on page 168.

DFS namespace server operating system requirementsA DFS namespace server is a domain controller or member server that hosts a DFS namespace. The number of DFS namespaces you can host on a server is determined by the operating system running on the DFS namespace server.

The following servers can host multiple domain-based DFS namespaces and stand-alone DFS namespaces:

• Windows Server 2016

• Windows Server 2012 R2

• Windows Server 2012

• Windows Server 2008 R2 Enterprise

• Windows Server 2008 R2 Datacenter

• Windows Server 2003 R2, Enterprise Edition

• Windows Server 2003 R2, Datacenter Edition

• Windows Server 2003, Enterprise Edition

• Windows Server 2003, Datacenter Edition

Servers that are running the following operating systems can host multiple domain-based DFS namespaces in addition to a single stand-alone DFS namespace:

• Windows Server 2008 R2 Standard

• Windows Server 2003 R2, Standard Edition with Service Pack 2 or later

• Windows Server 2003, Standard Edition with Service Pack 2 or later

The following table describes additional guidelines to consider when choosing servers to host a DFS namespace.

StorageX Administrator’s Guide 167

Page 186: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

DFS namespace operating system requirements4

DFS namespace client computer operating system requirementsClient computers running the following operating systems can access DFS namespaces and include full support for DFS namespaces, including support for client failback to the preferred folder target:

• Windows 10

• Windows Server 2016

• Windows 8.1

• Windows Server 2012 R2

• Windows 8

• Windows Server 2012

• Windows 7

• Windows Server 2008 R2

• Windows Vista Business, Windows Vista Enterprise, Windows Vista Ultimate

• Windows Server 2003 R2

• Windows Storage Server 2003 R2

• Windows Server 2003 with SP2, or SP1 and the Windows Server 2003 client failback hotfix

• Windows XP Professional with SP3, or SP2 and the Windows XP client failback hotfix

The Windows Server 2003 and Windows XP client failback hotfixes are describes in Microsoft Knowledge Base article 898900 available at https://support.microsoft.com/en-us/help/898900/an-update-is-available-to-support-the-dfs-namespaces-client-failback-f.

Client computers running the following operating systems can access DFS namespaces, but if a DFS link target becomes unavailable and then later comes back online, the client computer will not fail back (return) to the preferred DFS link target:

• Windows Storage Server 2003

TABLE 17 Guidelines for servers that host DFS namespaces

Servers Hosting Domain-Based Namespaces Servers Hosting Stand-Alone Namespaces

• Only servers running Windows Server 2008 can host domain-based namespaces in Windows Server 2008 mode.

• Must contain an NTFS volume to host the namespace.

• Must be a member server or domain controller in the domain in which the namespace is configured. (This requirement applies to every namespace server that hosts a given domain-based namespace.)

• Can use multiple namespace servers to increase the availability of the namespace

• The namespace cannot be a clustered resource in a failover cluster. However, you can locate the namespace on a server that also functions as a node in a failover cluster if you configure the namespace to use only local resources on that server.

• Only servers running Windows Server 2008 support access-based enumeration for stand-alone or domain-based (Windows Server 2008 mode) namespaces.

• Must contain an NTFS volume to host the namespace.

• Can be a member server or domain controller.• Can be hosted by a failover cluster to increase the

availability of the namespace.

168 StorageX Administrator’s Guide

Page 187: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding DFS namespace validation checks 4

• Windows XP Professional

• Windows 2000 Server

• Windows 2000 Professional

Understanding DFS namespace validation checksWhen you add a new DFS namespace to the My Resources folder in the Storage Resources view, StorageX automatically runs a series of validation checks to determine whether the namespace is accessible, is properly configured, and can be managed by StorageX.

After StorageX finishes running validation checks on your namespaces, the DFS Namespaces tab of the center pane in the Storage Resources view displays a grid listing your managed namespaces, with an icon indicating the status of each namespace:

• The Not Validated icon ( ) indicates that StorageX needs to validate the namespace.

• The Failed icon ( ) indicates that StorageX could not validate the namespace.

• The Warning icon ( ) indicates that the namespace passed most validation checks, but that StorageX could not fully validate the namespace.

• The Validated icon ( ) indicates that StorageX successfully validated the namespace.

You can click on a specific namespace and view detailed information about all checks run and any issues that need to be resolved for that namespace in the Validation results and Validation details panes. This allows you to more easily address issues with your managed namespaces. Data Dynamics recommends you resolve any validation issues with your namespaces before attempting to run StorageX policies using those namespaces.

If you want to re-run validation checks on all your managed namespaces, click the DFS Namespaces tab in the center pane, then right-click My Resources in the tree view and select Refresh.

Creating and configuring DFS namespacesThis section explains how to create and configure DFS namespaces using StorageX. For more information, see the following topics:

• “Domain-based DFS namespace configuration requirements” on page 169 and “Creating domain-based DFS namespaces” on page 171.

• “Stand-alone DFS namespace configuration requirements” on page 172 and “Creating stand-alone DFS namespaces” on page 173.

• “Consolidation DFS namespace configuration requirements” on page 175 and “Creating consolidation DFS namespaces” on page 176.

Domain-based DFS namespace configuration requirementsA domain-based DFS namespace must be hosted on a domain controller or on a domain member server. A domain-based DFS namespace provides better fault tolerance than a stand-alone DFS namespace. However, domain-based DFS namespaces may impact Active Directory replication, because a domain-based DFS namespace stores its configuration information in Active Directory. A domain-based DFS namespace also supports fewer links than a stand-alone DFS namespace.

StorageX Administrator’s Guide 169

Page 188: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and configuring DFS namespaces4

Before you create a domain-based DFS namespace, review the following configuration requirements:

• Microsoft Active Directory must be installed and operational in the domain where you want to create a domain-based DFS namespace.

• Microsoft DFS server software (Distributed File System Service dfssvc.exe) must be running on the server computer that hosts the DFS namespace.

• The StorageX server service account must have adequate permissions for both the domain and for the computer that hosts the domain-based DFS namespace. The StorageX server service account must also have full permissions on the share that stores the domain-based DFS namespace configuration information. For more information about the StorageX server service account, see “StorageX server service account requirements” on page 16.

• Whenever possible, the StorageX server and the DFS namespaces it manages should be on the same LAN.

• Ensure the user account running the StorageX Console has Administrator permissions on the computers that host DFS namespaces in your StorageX implementation. If you do not have the required permissions on computers that host DFS namespaces, you may have problems administering DFS namespaces and creating, modifying, and deleting namespaces and links in namespaces managed by StorageX. For more information, see the “Delegate Management Permissions for DFS Namespaces” article, available on the Microsoft TechNet web site at https://technet.microsoft.com/en-us/library/cc754770.aspx. This document provides detailed information about permissions required to create and manage domain-based DFS namespaces.

• All users in the domain that will access the DFS namespace must have read only permissions on the domain-based DFS namespace.

• When creating domain-based DFS namespaces, you must run the StorageX server on a computer that is a member of the domain that hosts the DFS namespace.

• A best practice for DFS namespaces is for file data to not reside physically on the computer that hosts the DFS namespace. When the computer that hosts the DFS namespace also hosts file data, this increases the load on the server because the server is forced to serve files as well as host the logical DFS namespace. If you have file data in folders on the computer that hosts your DFS namespace, move the file data to a new location.

For more information about specific operating system requirements for the server computer hosting the domain-based DFS namespace, see “DFS namespace server operating system requirements” on page 167. For more information about the different types of DFS namespaces, see “Understanding DFS namespace types” on page 164. For more information about creating domain-based DFS namespaces, see “Creating domain-based DFS namespaces” on page 171.

170 StorageX Administrator’s Guide

Page 189: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and configuring DFS namespaces 4

Creating domain-based DFS namespacesCreate a domain-based DFS namespace when you want to provide fault tolerance for your DFS namespace. Domain-based DFS namespaces can have multiple DFS namespace servers. Multiple DFS namespace servers provide fault tolerance and load sharing at the namespace level. Before you create a domain-based DFS namespace, ensure you meet domain-based DFS namespace requirements. For more information about domain-based DFS namespace requirements, see “Domain-based DFS namespace configuration requirements” on page 169.

To create a domain-based DFS namespace

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, right-click the My Resources folder, and then click Create DFS namespace to open the Namespace Creation Wizard.

3. Review the welcome message, and then click Next.

4. Click Create a domain-based DFS namespace, and then click Next.

5. In the Host server computer name field, type the fully qualified name of the server computer that you want to host the domain-based DFS namespace or click Browse to browse to and select the server computer you want to host the namespace.

For example, type \\ComputerName.DomainName.com, where ComputerName is the name of the server computer that you want to host the domain-based DFS namespace, and DomainName is the name of the domain to which the server computer belongs.

6. Click Next.

7. If you want to use an existing network share to store DFS namespace configuration information, click Use an existing share, and then select an existing network share from the list.

8. If you want to create a new network share to store DFS namespace configuration information, click Create a new share, and then complete the following steps:

a. In the Local path to share field, type the local path to the folder on the server computer you want to host the DFS namespace.

For example, type c:\FolderName, where c is the drive on the computer that will host the namespace, and FolderName is the name of the folder that will contain the domain-based DFS namespace configuration information.

b. In the Share name field, type the name of the share for the DFS namespace.

NOTEMicrosoft requires that the name of the share you use to store DFS namespace configuration information match the name of the domain-based DFS namespace you plan to create.

For example, type ShareName, where ShareName is the name of the share that will contain the domain-based DFS namespace server information.

9. Click Next.

10. In the Comment field, type a word or phrase that describes the domain-based DFS namespace.

StorageX Administrator’s Guide 171

Page 190: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and configuring DFS namespaces4

11. In the Client computers cache this referral for [x] seconds field, specify the number of seconds client computers should cache referral information for the domain-based DFS namespace.

12. If you want to enable DFS in Windows Server 2008 mode, select the Enable Windows Server 2008 Mode check box. The Windows Server 2008 mode includes support for access-based enumeration and increased scalability. To use the Windows Server 2008 mode, the domain and the namespace must meet the following minimum requirements:

• The forest uses the Windows Server 2003 or higher forest functional level.

• The domain uses the Windows Server 2008 domain functional level.

• All namespace servers are running Windows Server 2008 R2 or later.

If your environment supports using DFS namespaces in Windows Server 2008 mode, select the Enable Windows Server 2008 Mode check box when you create new domain-based DFS namespaces. This mode provides additional features and scalability, and also eliminates the possible need to migrate a namespace from the Windows 2000 Server mode.

If StorageX does not display the Enable Windows Server 2008 Mode check box, your environment does not meet the requirements for running DFS namespaces in Windows Server 2008 mode.

13. Click Next.

14. Review the summary information, and then click Finish.

StorageX creates the domain-based DFS namespace and displays the namespace in the Storage Resources view in the My Resources folder.

For more information about viewing domain-based DFS namespaces, see “Viewing DFS namespaces” on page 180. For more information about the Storage Resources view and the My Resources folder in the Storage Resources view, see “Understanding the Storage Resources view” on page 67.

Stand-alone DFS namespace configuration requirementsA stand-alone DFS namespace stores its configuration information locally on the host server. Stand-alone DFS namespaces have a single DFS namespace server. When the DFS namespace server is unavailable, the data referenced by links under a stand-alone DFS namespace is inaccessible. Stand-alone DFS namespaces can support more links than a domain-based DFS namespace.

Before you create a stand-alone DFS namespace, review the following requirements:

• Microsoft DFS server software (Distributed File System Service dfssvc.exe) must be running on the server computer that hosts the DFS namespace.

• The StorageX server service account must have adequate permissions on the server computer hosting the stand-alone DFS namespace. The StorageX server service account must also have full permissions on the share that stores the stand-alone DFS namespace configuration information. For more information about the StorageX server service account, see “StorageX server service account requirements” on page 16.

• Whenever possible, the StorageX server and the DFS namespaces it manages should be on the same LAN.

• Ensure the user account used to run the StorageX Console has the following permissions on the computer that hosts the DFS namespace;

• Member of the local Administrators group

172 StorageX Administrator’s Guide

Page 191: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and configuring DFS namespaces 4

• Permissions to write to the folder that hosts the DFS namespace

• All users in the domain that will be accessing the namespace must have read only permissions on the stand-alone DFS namespace.

• A best practice for DFS namespaces is for file data to not reside physically on the computer that hosts the namespace. When the computer that hosts the DFS namespace also hosts file data, this increases the load on the server because the server is forced to serve files as well as host the logical DFS namespace. If you have file data in folders on the computer that hosts your DFS namespace, move the file data to a new location.

For more information about specific operating system requirements for the server computer hosting the stand-alone DFS namespace, see “DFS namespace server operating system requirements” on page 167. For more information about the different types of DFS namespaces, see “Understanding DFS namespace types” on page 164. For more information about creating stand-alone DFS namespaces, see “Creating stand-alone DFS namespaces” on page 173.

Creating stand-alone DFS namespacesCreate a stand-alone DFS namespace if you do not have Active Directory in your environment, if you do not require namespace fault-tolerance in your environment, or if you need to support a very large number of links.

A stand-alone DFS namespace stores its configuration information locally on the host server computer, and stand-alone DFS namespaces have a single namespace server. When the DFS namespace server is unavailable, the data referenced by DFS links under a stand-alone DFS namespace is inaccessible. Before you create a stand-alone DFS namespace, review stand-alone DFS namespace requirements. For more information about stand-alone DFS namespace requirements, see “Stand-alone DFS namespace configuration requirements” on page 172.

To create a stand-alone DFS namespace

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, right-click the My Resources folder, and then click Create DFS namespace to open the Namespace Creation Wizard.

3. Review the welcome message, and then click Next.

4. Click Create a stand-alone DFS namespace, and then click Next.

5. In the Host server computer name field, type the fully qualified name of the server computer that you want to host the stand-alone DFS namespace or click Browse to browse to and select the server computer you want to host the namespace.

For example, type \\ComputerName.DomainName.com, where ComputerName is the name of the server computer that you want to host the stand-alone DFS namespace, and DomainName is the name of the domain to which the server computer belongs.

6. Click Next.

7. If you want to use an existing network share to store DFS namespace configuration information, click Use an existing share, and then select an existing network share from the list.

8. If you want to create a new network share to store DFS namespace configuration information, click Create a new share, and then complete the following steps:

StorageX Administrator’s Guide 173

Page 192: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and configuring DFS namespaces4

a. In the Local path to share field, type the local path to the network share on the server computer you want to host the DFS namespace.

For example, type c:\FolderName, where c is the drive on the computer that will host the namespace, and FolderName is the name of the folder that will contain the stand-alone DFS namespace configuration information.

b. In the Share name field, type the name of the share for the DFS namespace.

NOTEData Dynamics, Inc. recommends that the name of the share you use to store DFS namespace configuration information match the name of the stand-alone DFS namespace you plan to create.

For example, type ShareName, where ShareName is the name of the share that will contain the stand-alone DFS namespace server information.

9. Click Next.

10. In the Comment field, type a word or phrase that describes the stand-alone DFS namespace.

11. In the Client computers cache this referral for [x] seconds field, specify the number of seconds client computers should cache referral information for the stand-alone DFS namespace.

12. If you want to enable DFS in Windows Server 2008 mode, select the Enable Windows Server 2008 Mode check box. The Windows Server 2008 mode includes support for access-based enumeration and increased scalability. To use the Windows Server 2008 mode, the domain and the namespace must meet the following minimum requirements:

• The forest uses the Windows Server 2003 or higher forest functional level.

• The domain uses the Windows Server 2008 domain functional level.

• All namespace servers are running Windows Server 2008 R2 or later.

If your environment supports using DFS namespaces in Windows Server 2008 mode, select the Enable Windows Server 2008 Mode check box when you create new standalone DFS namespaces. This mode provides additional features and scalability, and also eliminates the possible need to migrate a namespace from the Windows 2000 Server mode.

If StorageX does not display the Enable Windows Server 2008 Mode check box, your environment does not meet the requirements for running DFS namespaces in Windows Server 2008 mode.

13. Click Next.

14. Review the summary information, and then click Finish.

StorageX creates the stand-alone DFS namespace and displays the namespace in the Storage Resources tab in the My Resources folder.

For more information about viewing stand-alone DFS namespaces, see “Viewing DFS namespaces” on page 180. For more information about the Storage Resources view and the My Resources folder in the Storage Resources view, see “Understanding the Storage Resources view” on page 67.

174 StorageX Administrator’s Guide

Page 193: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and configuring DFS namespaces 4

Understanding consolidation DFS namespacesConsolidation DFS namespaces are special stand-alone namespaces. Create a consolidation DFS namespace when you want to change the storage locations for files or folders and you want the Universal Naming Convention (UNC) paths to remain unchanged when the underlying files are moved to other servers or to other paths. The paths may be embedded in links, in line-of-business applications, and in other places where the names are difficult to change.

Consolidation DFS namespaces allow you to move files referenced in UNC paths embedded in links, in line-of-business applications, and in other places where the names are difficult to change without affecting users. Consolidation DFS namespaces allow UNC paths to remain unchanged when you move the underlying files to different locations or to other paths. The consolidation DFS namespace redirects the user from the old location referenced by the UNC path to the new location.

For example, you may want to configure a consolidation DFS namespace when you want to move file data on a server computer that hosts files referenced in user documents or applications. If you manually move files referenced in user documentation or applications from an old server computer to a new server computer, you must manually update all UNC path references to the files on the old server computer to point to the new file locations on the new server computer. However, if you create a consolidation DFS namespace, you can move the files without manually updating UNC path references.

A consolidation DFS namespace only redirects UNC paths.

If the server computer being consolidated provides other services, such as FTP, print, or web services, these services will not be redirected by the consolidation DFS namespace. Ensure you consider any additional services hosted on the server computer being consolidated and ensure you determine how these services will continue to be supported as part of your consolidation planning.

Consolidation DFS namespace configuration requirementsBefore you create a consolidation DFS namespace, review the following requirements:

• Microsoft DFS server software (Distributed File System Service dfssvc.exe) must be running on the computer that hosts the DFS namespace.

• Whenever possible, the StorageX server and the DFS namespaces it manages should be on the same LAN.

• You must install a software update from Microsoft that enables you to host a consolidation DFS namespace on the server you select. For more information about this software update, see Microsoft Knowledge Base article 829885, available on the Microsoft web site at https://support.microsoft.com/en-us/help/829885/distributed-file-system-update-to-support-consolidation-roots-in-windo. After you apply the software update, you must restart the Distributed File System service.

• Before you configure the consolidation DFS namespace, you must rename the server computer to be consolidated. For more information, see “Creating consolidation DFS namespaces” on page 176 and “Configuring consolidation DFS namespaces” on page 177.

• Consolidation DFS namespaces must be created on Windows Server 2003 R2 (32-Bit x86), Windows Server 2003 Service Pack 2, or Windows Server 2008 R2 server computers.

• The consolidation DFS namespace must be hosted on a member server computer and not on a domain controller. Server consolidation logic is disabled if the consolidation DFS namespace is hosted on a domain controller computer.

StorageX Administrator’s Guide 175

Page 194: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and configuring DFS namespaces4

• The NETBIOS name of the server computer that hosts the consolidation DFS namespace must be the same as the host name part of its fully qualified domain name.

• The consolidation of UNC paths from two servers that have the same host name is not supported. For example, you cannot consolidate two servers that are named server1.domain.com and server1.<subdomain>.domain.com.

• The StorageX server service account must have adequate permissions on the server computer where you create the consolidation DFS namespace. For more information about the StorageX server service account, see “StorageX server service account requirements” on page 16.

• All users in the domain that will access the namespace must have read only permissions on the consolidation DFS namespace.

Creating consolidation DFS namespacesBefore you create a consolidation DFS namespace, review consolidation DFS namespace requirements. For more information about consolidation DFS namespace requirements, see “Consolidation DFS namespace configuration requirements” on page 175.

After you create the consolidation DFS namespace, you must perform additional configuration and move the data from the old file server to the new file server. For more information, see “Configuring consolidation DFS namespaces” on page 177.

Use the following checklist to help you create a consolidation DFS namespace:

After you create the consolidation DFS namespace, when a client computer requests the old UNC path references to CIFS shared folders on the old file storage resource, the DFS consolidation namespace redirects the client computer to the new location of the CIFS shared folders on the new file storage resource.

You can host file data on the same computer on which you configured your consolidation DFS namespace. You can also migrate file data to a file storage resource and then target the file data using DFS links on the consolidation DFS namespace.

To create a consolidation DFS namespace

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, right-click the My Resources folder, and then click Create DFS namespace to open the Namespace Creation Wizard.

3. Review the welcome message, and then click Next.

4. Click Create a consolidation DFS namespace, and then click Next.

5. In the Host server computer name field, type the fully qualified name of the server computer that you want to host the consolidation DFS namespace, or click Browse to browse to and select the server computer you want to host the namespace.

TABLE 18 Checklist: Creating a consolidation DFS namespace

Task

1 Create a consolidation DFS namespace. For more information about creating a consolidation DFS namespace, see “Creating consolidation DFS namespaces” on page 176.

2 Configure the consolidation DFS namespace. For more information about configuring the consolidation DFS namespace, see “Configuring consolidation DFS namespaces” on page 177.

3 Move the file data from the old file storage resource to the new file storage resource.

176 StorageX Administrator’s Guide

Page 195: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and configuring DFS namespaces 4

For example, type \\ComputerName.DomainName.com, where ComputerName is the name of the server computer that you want to host the consolidation DFS namespace and DomainName is the name of the domain to which the server computer belongs.

6. Click Next.

7. In the Server computer name field, type the fully qualified name of the server computer you want to consolidate, or click Browse to browse to and select the server computer you want to consolidate.

For example, type \\ComputerName.DomainName.com, where ComputerName is the name of the server computer you want to consolidate, and DomainName.com is the name of the domain to which the server computer you want to consolidate belongs.

8. In the Local path of new share field, type the local path to the folder on the server computer you want to share as the consolidation DFS namespace.

For example, type c:\FolderName, where c is the drive on the server computer that will host the consolidation DFS namespace, and FolderName is the name of the share that will contain the consolidation DFS namespace information.

9. Click Next.

10. Review the Preview of the UNC path to the namespace and DFS namespace name fields, and note that StorageX uses the name of the server computer you want to consolidate as the name of the DFS namespace. StorageX adds a pound (#) character as the first character of the name of the server computer you want to consolidate when it names the DFS namespace, to indicate that the namespace is a consolidation DFS namespace.

For example, #ConsolidatedServer is the name of the consolidation DFS namespace, where #ConsolidatedServer is the name of the server computer you are consolidating.

11. In the Comment field, type a word or phrase that describes the consolidation DFS namespace.

12. In the Client computers cache this referral for [x] seconds field, specify the number of seconds client computers should cache referral information for the namespace.

13. Click Next.

14. Review the summary information, and then click Finish.

StorageX creates the consolidation DFS namespace and displays the namespace in the Storage Resources tab in the My Resources folder.

For more information about viewing consolidation DFS namespaces, see “Viewing DFS namespaces” on page 180. For more information about the Storage Resources view and the My Resources folder in the Storage Resources view, see “Understanding the Storage Resources view” on page 67.

After you create the consolidation DFS namespace, configure the namespace. For more information, see “Configuring consolidation DFS namespaces” on page 177.

Configuring consolidation DFS namespacesAfter you create a consolidation DFS namespace, you must configure the namespace.

This section explains how to configure a consolidation DFS namespace.

StorageX Administrator’s Guide 177

Page 196: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and configuring DFS namespaces4

For more information about creating a consolidation DFS namespace, see “Creating consolidation DFS namespaces” on page 176. For more information about consolidation DFS namespace requirements, see “Consolidation DFS namespace configuration requirements” on page 175.

To configure a consolidation DFS namespace

1. If you use a Microsoft Windows 2000 DHCP server, ensure that the Automatically update DHCP client information in DNS check box is selected only at the server level. Ensure that the Automatically update DHCP client information in DNS check box is not selected at the DHCP scope level.

2. If you use a Microsoft Windows 2003 DHCP server, ensure that the Enable DNS dynamic updates according to the settings below check box is selected only at the server level. Ensure that the Enable DNS dynamic updates according to the settings below check box is not selected at the DHCP scope level.

3. If you need to clear the DHCP scope level, complete the following steps:

a. On the DHCP server, in the Administrative Tools program folder, click DHCP.

b. Expand the DHCP server name, right-click the first Scope on the list, and then click Properties.

c. If you need to clear the DHCP scope level for a Microsoft Windows 2000 DHCP server, on the DNS tab, clear the Automatically update DHCP client information in DNS check box.

d. If you need to clear the DHCP scope level for a Microsoft Windows 2003 DHCP server, on the DNS tab, clear the Enable DNS dynamic updates according to the settings below check box.

e. Repeat step b through step d for each DHCP scope.

4. On the Windows Internet Name Service (WINS) server, verify that static WINS entries do not exist for the server to be consolidated.

For example, ensure that WINS entries do not exist for ServerA, where ServerA is the name of the server to be consolidated. If WINS entries exist, delete them. For more information about how to delete static WINS entries, contact Microsoft.

5. Rename the file storage resource you want to consolidate.

ATTENTIONYou must rename the existing file storage resource before you run the following ipconfig command. If you run ipconfig first without renaming the original resource, you may encounter a name conflict, as both resources will be using the same name.

6. Open a command prompt on the server hosting the consolidation DFS namespace and type the following command: ipconfig /registerdns.

7. Restart the Server service on the server hosting the consolidation DFS namespace.

NOTEIf you stop and restart the Server service instead of restarting it, you must start the DFS service and Computer Browser service. When you stop the Server service, the DFS and Computer Browser services are also stopped.

178 StorageX Administrator’s Guide

Page 197: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and configuring DFS namespaces 4

8. If you want to see which clients continue accessing the consolidated data through the old computer name, you can log a system event every time that the DFS namespace consolidation server computer successfully resolves a referral. The log enables you to see which clients are accessing the consolidated data through the old server computer name.

To create a system event every time the DFS namespace consolidation server computer successfully resolves a referral, complete the following steps:

a. Locate the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dfs\Parameters\Replicated

b. Click the registry key.

c. On the Edit menu, click to New, and then click DWORD Value.

d. Type LogServerConsolidation, and then press Enter.

e. In the Value data field, type 1, and then click OK.

Windows logs the logical path and the client IP address to the system event log as event ID: 14318. Allocate sufficient space to the system log. Microsoft recommends that you set the system event log to at least 64 megabytes. Ensure you set the system event log to overwrite events as needed.

9. If you want to configure a consolidation DFS namespace in a cluster server environment, for more information see Microsoft Knowledge Base article 829885, available on the Microsoft web site at www.microsoft.com.

10. After you create the consolidation DFS namespace, perform the following steps:

a. Create DFS links in the consolidation DFS namespace that target the data on the renamed original file server.

b. Migrate the data to the new location using Phased Migration policies. For more information about Phased Migration policies, see “Understanding Phased Migration policies” on page 230.

c. Update the DFS links in the consolidation DFS namespace to target CIFS shared folders in the new location that will be redirected. For example, a DFS link under the consolidation namespace \\ConsolidationServer\#Server1 would target the location of a CIFS shared folder on ConsolidationServer.

DFS links in a consolidation namespace cannot be referenced under a DFS namespace folder in the DFS namespace. DFS links must always be directly under the consolidation namespace.

If you try to access a DFS link under a DFS namespace folder, StorageX displays the following error:

No network provider accepted the given path.

The following figure shows a correctly configured consolidation DFS namespace. DFS links are listed directly under the namespace.

StorageX Administrator’s Guide 179

Page 198: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS namespaces4

The following figure shows an incorrectly configured consolidation DFS namespace. The targets of links Engineering and Marketing cannot be accessed because they are configured under the DFS namespace folder Consolidation Data.

For more information about DFS namespace folders, see “Creating folders in DFS namespaces” on page 198.

Managing DFS namespacesThis section explains how to manage DFS namespaces. For more information, see the following topics:

• “Viewing DFS namespaces” on page 180

• “Viewing DFS namespace properties” on page 181

• “Modifying DFS namespace properties” on page 181

• “Enabling access-based enumeration for DFS namespaces” on page 182

• “Delegating management for DFS namespaces” on page 183

• “Specifying referral settings for DFS namespaces” on page 183

• “Refreshing DFS namespaces” on page 184

• “Upgrading DFS namespaces to Windows Server 2008 mode” on page 184

• “Adding DFS namespaces to My Resources” on page 186

• “Verifying DFS namespaces” on page 186

• “Removing DFS namespaces from My Resources” on page 187

• “Deleting DFS namespaces” on page 188

For more information about creating and configuring DFS namespaces, see “Creating and configuring DFS namespaces” on page 169.

Viewing DFS namespacesUse the StorageX Console to display the DFS namespaces managed by StorageX. Open the StorageX Console and click Storage Resources, then expand the My Resources folder. StorageX displays all managed DFS namespaces.

For more information about creating DFS namespaces, see “Creating and configuring DFS namespaces” on page 169.

180 StorageX Administrator’s Guide

Page 199: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS namespaces 4

Viewing DFS namespace propertiesYou can use the StorageX Console to view DFS namespace properties for namespaces StorageX manages. For more information about creating DFS namespaces, see “Creating and configuring DFS namespaces” on page 169.

To view DFS namespace properties

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

3. Right-click the DFS namespace for which you want to view properties, and then click Properties.

4. Click the Namespace Properties tab. The Namespace Properties tab displays information about the type of namespace, whether access-based enumeration is enabled for the namespace, and management delegation for the namespace. For more information about each setting, click the Help button on the dialog box.

5. Click the Referral Settings tab. The Referral settings tab displays referral settings for the selected DFS namespace. For more information about each setting, click the Help button on the dialog box.

6. Click OK.

Modifying DFS namespace propertiesYou can modify the comment and client cache referral interval for DFS namespaces and add DFS namespace servers to and remove DFS namespace servers from domain-based DFS namespaces. For more information about creating DFS namespaces, see “Creating and configuring DFS namespaces” on page 169.

Before modifying your DFS namespace, you may want to consider backing up the namespace using a Namespace Backup policy, so that you can restore the namespace to a previous state at a later time. For more information about backing up and restoring namespaces in StorageX, see “Backing up and restoring DFS namespaces” on page 220.

To modify DFS namespace properties

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

3. Right-click the namespace for which you want to modify properties, and then click Properties.

4. If you want to modify the comment displayed for a DFS namespace, on the Namespace Properties tab, in the Comment field, type a new comment for the DFS namespace.

5. If you want to enable access-based enumeration, on the Namespace Properties tab, select the Enable access-based enumeration for this namespace check box. For more information, see “Enabling access-based enumeration for DFS namespaces” on page 182.

6. If you want to modify the client computer cache referral interval for the DFS namespace, on the Referral Settings tab, in the Client computers cache referrals for [x] seconds field, specify the number of seconds for which you want client computers to cache referral information for the DFS namespace.

StorageX Administrator’s Guide 181

Page 200: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS namespaces4

7. If you want to specify additional referral settings, such as an ordering method for DFS namespace servers outside the a client’s site and whether you want clients to fail back to preferred targets, on the Namespace Properties tab, specify the appropriate settings. For more information, see “Specifying referral settings for DFS namespaces” on page 183 or click the Help button on the dialog box.

For more information about domain-based DFS namespace servers, see “Creating domain-based DFS namespace servers” on page 189.

8. Click OK.

Enabling access-based enumeration for DFS namespacesIf you have a domain-based DFS namespace operating in Windows Server 2008 mode, you can enable access-based enumeration for the namespace. Access-based enumeration hides files and folders that users do not have permission to access. By default, this feature is not enabled for domain-based DFS namespaces operating in Windows Server 2008 mode.

This topic explains how to enable access-based enumeration for domain-based DFS namespaces operating in Windows Server 2008 mode.

After you enable access-based enumeration for the DFS namespace, you can specify which users and groups can view specific DFS link targets by selecting DFS link targets and specifying permissions for the DFS link target. For more information, see “Specifying which users and groups can view specific DFS link targets” on page 207.

ATTENTIONAccess-based enumeration does not prevent users from getting a referral to a DFS link target if they already know the DFS path. Only the share permissions or the NTFS file system permissions of the DFS link target itself can prevent users from accessing a DFS link target. DFS link target permissions are used only for displaying or hiding DFS links, not for controlling access. Read access is the only relevant permission for DFS links.

To enable access-based enumeration for a domain-based DFS namespace

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

3. Right-click the domain-based DFS namespace where you want to enable access-based enumeration, and then click Properties.

4. On the Namespace Properties tab, in the Type field, verify that Domain-based DFS (Windows Server 2008 mode) displays.

You can only enable access-based enumeration for domain-based DFS namespaces operating in Windows Server 2008 mode.

5. Select the Enable access-based enumeration for this namespace check box to enable access-based enumeration for the DFS namespace.

If the Enable access-based enumeration for this namespace check box is not displayed, the namespace is not a domain-based DFS namespace operating in Windows Server 2008 mode, and you cannot enable access-based enumeration on the namespace. The Enable access-based enumeration for this namespace check box only displays for domain-based DFS namespaces operating in Windows Server 2008 mode.

182 StorageX Administrator’s Guide

Page 201: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS namespaces 4

After you enable access-based enumeration for the domain-based DFS namespace, specify which users and groups can view specific DFS link targets as needed. For more information, see “Specifying which users and groups can view specific DFS link targets” on page 207.

Delegating management for DFS namespacesYou can delegate management for DFS namespaces.

Delegate management for DFS namespaces when you want to allow additional users or groups to manage the DFS namespace.

To delegate management for a DFS namespace

1. In the StorageX Console, click the Storage Resources tab.

2. Right-click the DFS namespace where you want to delegate management, and then click Properties.

3. On the Namespace Properties tab, complete the following steps:

a. If you want to add a new user or group, in the Management Delegation area, click the folder icon and then browse to the Users container in the domain and select the user or group you want to add.

b. If you want to remove a user or group, select the user or group, and then click the red x icon.

NOTEIf a user or group has Inherited permissions, you cannot remove the user or group from the delegation list in this dialog box. Inherited management permissions are set in Active Directory Domain Services.

4. Click OK.

Specifying referral settings for DFS namespacesA referral is an ordered list of DFS link targets that client computers receive from a domain controller or DFS namespace when a client computer accesses the DFS namespace or a DFS link with link targets. After the client computer receives the referral, the client computer attempts to access the first DFS link target in the list. If the DFS link target is not available, the client computer attempts to access the next target.

DFS link targets in the client’s site are always listed first in a referral.

DFS link targets outside of the client’s site are listed according to the ordering method you specify on the DFS namespace.

DFS links for the namespace inherit the ordering method you specify for the DFS namespace. However, you can override the ordering method specified on the DFS namespace for specific DFS links.

This topic explains how to specify referral settings for DFS namespaces, including how long client computers should cache referrals.

For more information about overriding the order method specified on the DFS namespace for specific DFS links, see “Specifying referral settings for DFS links” on page 197.

StorageX Administrator’s Guide 183

Page 202: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS namespaces4

To specify referral settings for a DFS namespace

1. In the StorageX Console, click the Storage Resources tab.

2. Right-click the DFS namespace where you want to specify referral settings, and then click Properties.

3. On the Referral Settings tab, complete the following steps:

a. In the Client computers cache referrals for [x] seconds field, specify the duration in seconds for how long client computers should cache referrals.

b. Specify the ordering method you want to use for ordering DFS link targets outside of the client’s site. For more information about each option, click the Help button on the dialog box.

c. If DFS link targets become unavailable, you can configure client computers to fail back to preferred DFS link targets after they are restored.

Select the Clients fail back to preferred targets check box if you want client computers to fail back to preferred DFS link targets after the DFS link targets are restored.

NOTEFor fail back to work, client computers must meet DFS namespace client computer requirements. For more information, see “DFS namespace client computer operating system requirements” on page 168.

Refreshing DFS namespacesYou can refresh DFS namespaces. Refreshing a DFS namespace updates the information about the DFS namespace displayed in the Storage Resources view. For more information about creating DFS namespaces, see “Understanding DFS namespace types” on page 164.

To refresh a DFS namespace

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

3. Right-click the namespace for which you want to refresh information, and then click Refresh. StorageX obtains updated information from the network for all the items that the DFS namespace contains.

NOTEGathering and displaying updated DFS namespace information may take some time if the DFS namespace is large.

Upgrading DFS namespaces to Windows Server 2008 modeIf you previously created a domain-based DFS namespace using Windows 2000 Server mode and then upgrade to a Windows Server 2008 environment, you can use StorageX to automatically upgrade the original DFS namespace to Windows Server 2008 mode.

184 StorageX Administrator’s Guide

Page 203: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS namespaces 4

Windows Server 2008 mode offers several improvements over Windows 2000 Server mode, like access-based enumeration support and the ability to have a much larger number of links. For more information about Windows Server 2008 mode, see the “Distributed File System” article, available on the Microsoft TechNet web site at https://technet.microsoft.com/en-us/library/cc753479.aspx.

To upgrade a DFS namespace to Windows Server 2008 mode, the domain and DFS namespace must meet the following minimum requirements:

• The forest uses the Windows Server 2003 or higher forest functional level.

• The domain uses the Windows Server 2008 domain functional level.

• All DFS namespace servers are running Windows Server 2008.

The upgrade process may take a significant amount of time, depending on the size and complexity of your environment. While the upgrade process is occurring, your DFS namespace will be unavailable.

NOTEIf you upgrade a Windows Server 2000 mode namespace with more than one namespace server, the upgraded Windows Server 2008 mode namespace will only have one namespace server, located on the host server you specified in the Namespace Upgrade Wizard. You must manually add any additional namespace servers to the upgraded namespace after the upgrade process is complete.

For more information about DFS namespaces, Windows 2000 Server mode, and Windows Server 2008 mode, see “Understanding DFS namespace types” on page 164.

To upgrade a Windows 2000 Server mode DFS namespace to Windows Server 2008 mode

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

3. Right-click the Windows 2000 Server mode DFS namespace that you want to upgrade and select Upgrade Namespace to 2008 Mode to open the Namespace Upgrade Wizard.

4. Review the welcome message, and then click Next.

5. In the Host server computer name field, type the fully qualified name of the Windows Server 2008 computer that you want to host the upgraded DFS namespace or click Browse to browse to and select the Windows Server 2008 computer you want to host the upgraded DFS namespace.

For example, type \\ComputerName.DomainName.com, where ComputerName is the name of the server computer that you want to host the upgraded DFS namespace, and DomainName is the name of the domain to which the server computer belongs.

6. Click Next.

7. If you specified a host server other than the original host server for the namespace, type the local path of the new share you want to use to host the upgraded DFS namespace, then click Next.

NOTEYou cannot use an existing share when upgrading to Windows Server 2008 mode.

8. Review the summary information, and then click Finish to upgrade the namespace to Windows Server 2008 mode.

StorageX Administrator’s Guide 185

Page 204: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS namespaces4

StorageX creates a backup of the original Windows 2000 Server mode namespace and stores the namespace backup in the My Backups folder in the Namespace Policies view. Then StorageX creates a new Windows Server 2008 mode namespace with the same properties as the original namespace and displays the upgraded DFS namespace in the Storage Resources view in the My Resources folder.

Adding DFS namespaces to My ResourcesEnsure all DFS namespaces you want to manage with StorageX display directly under in the My Resources folder in the Storage Resources view. For more information about creating DFS namespaces, see “Understanding DFS namespace types” on page 164.

If you have implemented DFS in your environment and you have existing DFS namespaces created with a tool other than StorageX, you can manage these DFS namespaces with StorageX. However, before you can manage these DFS namespaces with StorageX, you must add these DFS namespaces to My Resources.

NOTES:

• If you add a DFS namespace to My Resources and then modify the namespace outside of StorageX, you must refresh the namespace in StorageX to see the changes.

• If you add a DFS namespace to My Resources and then delete the namespace outside of StorageX, you must manually remove the namespace from My Resources. For more information about removing a namespace, see “Removing DFS namespaces from My Resources” on page 187.

• You cannot add a stand-alone DFS namespace to My Resources unless you first add the server that hosts the stand-alone namespace. You cannot browse a hosting server that is not managed by StorageX and view the stand-alone namespaces that server hosts.

To add a DFS namespace to My Resources

1. In the StorageX Console, click the Storage Resources tab.

2. Right-click the My Resources folder, and then click Add DFS namespace.

3. Type the path of the DFS namespace you want to add to the My Resources folder or click Browse to browse to and select the DFS namespace you want to add to the My Resources folder.

4. Click OK. StorageX adds the namespace to the My Resources folder, and you can now manage the namespace using StorageX.

Verifying DFS namespacesAfter you add DFS namespaces to the My Resources folder or a custom folder under My Resources, verify that the namespace you added passed all validation checks, and that StorageX displays the new namespace correctly under My Resources.

For more information about namespace validation checks, see “Understanding DFS namespace validation checks” on page 169.

186 StorageX Administrator’s Guide

Page 205: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS namespaces 4

To verify DFS namespaces in My Resources

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, click My Resources.

3. In the center pane, click the DFS Namespaces tab.

4. In the list of namespaces displayed in the center pane, select the namespace you want to verify.

5. Wait until StorageX validates the selected namespace. If the center pane displays a Not Validated icon ( ) in the Status column for the namespace, StorageX has not yet run validation checks on the namespace.

The Failed icon ( ) indicates that StorageX could not validate the namespace, the Warning icon ( ) indicates that the namespace passed most validation checks, but that StorageX could not fully validate the namespace, and the Validated icon ( ) indicates that StorageX successfully validated the namespace.

6. Review the information displayed in the Validation results pane.

7. If any validation check displays a Failed icon, select the validation check, review the information displayed in the Validation details pane, and follow any steps provided to resolve the issue. For information about configuring namespaces, see “Creating and configuring DFS namespaces” on page 169 and “Modifying DFS namespace properties” on page 181.

8. In the left tree pane under Storage Resources > My Resources, expand each namespace you added and confirm that all shares, folders, and links display as appropriate under each namespace.

Removing DFS namespaces from My ResourcesAll DFS namespaces managed by StorageX must be in the My Resources folder in the Storage Resources view.

If you remove a namespace from the My Resources folder, you can no longer use StorageX to manage the namespace.

If the My Resources folder in the Storage Resources view displays too many DFS namespaces to manage effectively, or if you complete the management of a DFS namespace and you no longer want to view and manage the namespace using the My Resources folder in the Storage Resources tab, you can configure the DFS namespace to no longer display in the My Resources folder. Configuring the DFS namespace to no longer display in the My Resources folder does not delete the DFS namespace from the namespace server computer. Client computers can also continue to access the DFS namespace.

Before removing your DFS namespace from My Resources, you may want to consider backing up the namespace using a Namespace Backup policy, so that you can restore the namespace at a later time. For more information about backing up and restoring namespaces in StorageX, see “Backing up and restoring DFS namespaces” on page 220.

To remove a DFS namespace from display in the My Resources folder

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

StorageX Administrator’s Guide 187

Page 206: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS namespaces4

3. Right-click the DFS namespace that you want to remove from display in the My Resources folder, and then click Remove from display.

4. Click Yes to confirm that you want to remove the namespace from the My Resources folder.

Deleting DFS namespacesWhen you delete a DFS namespace, StorageX removes the namespace from the server computer by deleting the DFS namespace configuration files. However, StorageX does not delete CIFS shared folders or folders under CIFS shared folders on the file storage resource that were referenced by the DFS namespace.

When you delete a DFS namespace, client computers can no longer browse the namespace. However, folders and files remain in their current location.

When you delete a DFS namespace, carefully consider the impact of client computer access to the file data referenced by the DFS namespace. Once you delete a DFS namespace, client computers will no longer be able to access any file data referenced by the namespace.

Before deleting your DFS namespace, you may want to consider backing up the namespace using a Namespace Backup policy, so that you can restore the namespace at a later time. For more information about backing up and restoring namespaces in StorageX, see “Backing up and restoring DFS namespaces” on page 220.

To delete a DFS namespace

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

3. Select the DFS namespace for that you want to delete.

4. Right-click the namespace, and then click Delete DFS Namespace.

5. Click Yes to confirm that you want to delete the namespace.

6. Click the Events view to see events associated with deleting the DFS namespace, including any errors or warnings associated with deleting the namespace.

7. Open the event associated with the deletion of the namespace by double-clicking the event in the Events view to open the Event Viewer dialog box.

8. If you want to view all details for the event, click Details.

9. If you want to save the event details associated with deleting the DFS namespace, in the Event Details dialog box, click Export and complete the following steps:

a. In the File name field, type a name for the file you want to export.

b. In the File location field, type the UNC path for the location where you want to save the report file or click Browse to browse to and select a location on the network where you want to save the file.

c. Click OK.

d. Click Close when the download completes. After you save the event details, you can review the information about what folders were formerly targeted by DFS links in the namespace and use this information as needed for troubleshooting.

188 StorageX Administrator’s Guide

Page 207: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating domain-based DFS namespace servers 4

Creating domain-based DFS namespace serversYou can use StorageX to create domain-based DFS namespace servers. You cannot create DFS namespace servers for stand-alone DFS namespaces or consolidation DFS namespaces.

Domain-based DFS namespace servers host copies of the logical structure of a domain-based DFS namespace and provide fault tolerance and load balancing.

You create domain-based DFS namespace servers by specifying additional servers to host copies of the logical structure of a domain-based DFS namespace to provide fault tolerance and load balancing.

For more information about domain-based DFS namespaces, see “Understanding DFS namespace types” on page 164.

When you create or select a share for your DFS namespace server, a best practice is for the share name to match the name of the DFS namespace.

To create a domain-based DFS namespace server

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

3. Select the domain-based DFS namespace for which you want to create a domain-based DFS namespace server.

4. Right-click the domain-based DFS namespace, and then click Add Namespace Server.

5. Review the welcome message, and then click Next.

6. In the Host server computer name field, type the fully qualified name of the server computer where you want to create the domain-based DFS namespace server or click Browse to browse to and select an available server computer.

For example, type \\ComputerName.DomainName.com, where ComputerName is the name of the server computer that you want to host the domain-based DFS namespace server, and DomainName.com is the name of the domain to which the server computer belongs.

7. Click Next.

8. If you want to use an existing share to host the domain-based DFS namespace server, complete the following steps:

a. Click Use an existing share.

b. Select a shared folder from the list.

9. If you want to create a new share to host the domain-based DFS namespace server, click Create a new share, and then in the Local path to share field, type the local path to the network share on the server computer you want to host the domain-based DFS namespace server.

For example, type c:\FolderName, where c is the drive on the computer that will host the namespace, and FolderName is the name of the folder that will contain the domain-based DFS namespace server configuration information.

10. Click Next.

11. Review the DFS namespace server settings, and then click Finish.

StorageX Administrator’s Guide 189

Page 208: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing domain-based DFS namespace servers4

StorageX creates the domain-based DFS namespace server. For more information about managing domain-based DFS namespace servers, see “Managing domain-based DFS namespace servers” on page 190.

Managing domain-based DFS namespace serversDomain-based DFS namespace servers host copies of the logical structure of a domain-based DFS namespace and provide fault tolerance and load balancing. The following topics provide information about managing domain-based DFS namespace servers:

• “Viewing and modifying domain-based DFS namespace servers” on page 190

• “Enabling and disabling referrals for domain-based DFS namespace servers” on page 191

• “Overriding referral ordering for domain-based DFS namespace servers” on page 192

• “Removing domain-based DFS namespace servers” on page 193

For more information about creating domain-based DFS namespace servers, see “Creating domain-based DFS namespace servers” on page 189.

Viewing and modifying domain-based DFS namespace serversYou can view and modify domain-based DFS namespace server properties in the Storage Resources view.

This topic explains how to view and modify domain-based DFS namespace servers. For more information about creating domain-based DFS namespace servers, see “Creating domain-based DFS namespace servers” on page 189.

To view or modify a domain-based DFS namespace server

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, expand the My Resources folder.

3. Select the domain-based DFS namespace with the domain-based DFS namespace server you want to view or modify.

4. In the center pane, under Namespace Servers, StorageX displays the domain-based DFS namespace servers configured for the selected domain-based DFS namespace. Right-click the domain-based DFS namespace server you want to view or modify, and then click Properties.

5. If you want to enable referrals for the DFS namespace server, select the Enable referrals for this target check box. If you want to disable referrals, clear the check box. For more information about enabling or disabling referrals, see “Enabling and disabling referrals for domain-based DFS namespace servers” on page 191, or click the Help button on the dialog box.

6. If you want to override referral ordering for the selected DFS namespace server, select the Override referral ordering check box, and then select the target priority setting you want to use. For more information about overriding referral ordering for domain-based DFS namespaces, see “Overriding referral ordering for domain-based DFS namespace servers” on page 192 or click the Help button on the dialog box.

7. Click OK.

190 StorageX Administrator’s Guide

Page 209: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing domain-based DFS namespace servers 4

For more information about creating domain-based DFS namespace servers, see “Creating domain-based DFS namespace servers” on page 189. For more information about managing domain-based DFS namespace servers, see “Managing domain-based DFS namespace servers” on page 190.

Enabling and disabling referrals for domain-based DFS namespace serversYou can enable or disable referrals for domain-based DFS namespace in the Storage Resources view.

A referral is an ordered list of targets that a client computer receives from a domain controller or domain-based DFS namespace when the user accesses a domain-based namespace with DFS namespace servers.

After the client computer receives the referral, the client computer attempts to access the first domain-based DFS namespace server in the list. If the computer that hosts the domain-based DFS namespace server is not available, the client attempts to access the next domain-based DFS namespace server on the list.

If referrals are enabled for a domain-based DFS namespace server, client computers can use the referral information provided by the domain-based DFS namespace server to access data if the domain-based DFS namespace is offline.

By default, domain-based DFS namespace servers are enabled when you create them using the StorageX Namespace Server Wizard. For more information, see “Creating domain-based DFS namespace servers” on page 189.

If referrals are disabled for a domain-based DFS namespace server, client computers cannot use the referral information provided by the domain-based DFS namespace server to access data. The ability to disable a domain-based DFS namespace server is useful if you need to temporarily take a computer that hosts the domain-based DFS namespace server offline for maintenance.

To enable or disable referrals for a domain-based DFS namespace server

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, expand the My Resources folder.

3. Select the domain-based DFS namespace with the domain-based DFS namespace server where you want to enable or disable referrals.

4. In the center pane, under Namespace Servers, StorageX displays the domain-based DFS namespace servers configured for the selected domain-based DFS namespace.

The Target field displays the name of the domain-based DFS namespace server, and the State field displays if the domain-based DFS namespace server is enabled or disabled.

If the domain-based DFS namespace server is enabled, Enabled displays.

If the domain-based DFS namespace server is disabled, Disabled displays.

5. If you want to enable referrals for a domain-based DFS namespace server, complete the following steps:

a. Right-click the domain-based DFS namespace server you want to enable, and then click Properties.

b. Select the Enable referrals for this target check box.

StorageX Administrator’s Guide 191

Page 210: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing domain-based DFS namespace servers4

c. Click OK.

6. If you want to disable referrals for a domain-based DFS namespace server, complete the following steps:

a. Right-click the domain-based DFS namespace server you want to disable, and then click Properties.

b. Clear the Enable referrals for this target check box.

c. Click OK.

7. If you want to enable all referrals for a domain-based DFS namespace server, right-click the namespace server in the left tree pane and select Enable all referrals.

8. If you want to disable all referrals for a domain-based DFS namespace server, right-click the namespace server in the left tree pane and select Disable all referrals.

ATTENTIONIf you use the Disable all referrals option on a DFS namespace, this will disable all namespace targets. If all namespace targets are disabled when the referral cache expires, the associated namespace will no longer be accessible. We recommend you use caution when disabling all referrals. This option should only be used to temporarily disable a namespace, unless you plan on discontinuing the namespace permanently. Instead, you may want to consider disabling referrals as needed using the namespace server Properties dialog box. This will ensure that at least one referral will always remain online.

For more information about creating domain-based DFS namespace servers, see “Creating domain-based DFS namespace servers” on page 189. For more information about managing domain-based DFS namespace servers, see “Managing domain-based DFS namespace servers” on page 190.

Overriding referral ordering for domain-based DFS namespace serversYou can override referral order for domain-based DFS namespace servers in the Storage Resources view.

A referral is an ordered list of targets that a client computer receives from a domain controller or domain-based DFS namespace when the user accesses a domain-based DFS namespace with domain-based DFS namespace servers.

By default, each domain-based DFS namespace server in a referral is ordered according to the ordering method specified for the DFS namespace. For more information about specifying the ordering method for a DFS namespace, see “Specifying referral settings for DFS namespaces” on page 183.

However, you can refine how domain-based DFS namespace servers are ordered by setting priority on individual DFS namespace servers. For example, you can specify that a DFS namespace server is first among all DFS namespace servers, last among all DFS namespace servers, or first (or last) among all DFS namespace servers of equal cost.

To override referral ordering for a domain-based DFS namespace server

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, expand the My Resources folder.

192 StorageX Administrator’s Guide

Page 211: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding DFS links to DFS namespaces 4

3. Select the domain-based DFS namespace with the domain-based DFS namespace server where you want to override referral ordering.

4. In the center pane, under Namespace Servers, StorageX displays the domain-based DFS namespace servers configured for the selected domain-based DFS namespace. Right-click the domain-based DFS namespace server where you want to override referral ordering, and then click Properties.

5. Select the Override referral ordering check box, and then select the target priority setting you want to use. For more information about each setting, click the Help button on the dialog box.

For more information about creating domain-based DFS namespace servers, see “Creating domain-based DFS namespace servers” on page 189. For more information about managing domain-based DFS namespace servers, see “Managing domain-based DFS namespace servers” on page 190.

Removing domain-based DFS namespace serversYou can remove domain-based DFS namespace servers when you no longer want to use the domain-based DFS namespace servers.

To remove a domain-based DFS namespace server

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, expand the My Resources folder.

3. Select the domain-based DFS namespace with the DFS namespace server you want to remove.

4. In the center pane, under Namespace Servers, StorageX displays the domain-based DFS namespace servers configured for the selected domain-based DFS namespace. Right-click the domain-based DFS namespace server you want to remove, and then click Remove.

StorageX removes the domain-based DFS namespace server, and it no longer displays in the center pane under Namespace Servers.

For more information about creating domain-based DFS namespace servers, see “Creating domain-based DFS namespace servers” on page 189. For more information about viewing and modifying domain-based DFS namespace servers, see “Viewing and modifying domain-based DFS namespace servers” on page 190.

Adding DFS links to DFS namespacesAfter you create a DFS namespace, add DFS links to the DFS namespace.

A DFS link is an object that contains reference information that points to a DFS link target. A DFS link target can be any UNC path. For example, a DFS link target could be a CIFS shared folder or a folder under a CIFS shared folder. A DFS link target can also be another DFS namespace, DFS link, or DFS namespace folder in the namespace.

Adding a DFS link that targets a folder under a CIFS shared folder effectively adds the folder to the DFS namespace. You can run StorageX policies on CIFS shared folders and subfolders that are a part of the DFS namespace.

StorageX Administrator’s Guide 193

Page 212: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding DFS links to DFS namespaces4

A DFS link can have multiple targets. When a DFS link has two or more targets, the DFS namespaces or shared folders that are the targets of the DFS link provide alternate paths for the DFS link.

You can add the same DFS link to multiple DFS namespaces. Adding DFS links to multiple DFS namespaces is useful if you have multiple stand-alone DFS namespaces and you need to manually keep the DFS links synchronized between stand-alone DFS namespaces.

The permissions on a DFS namespace share controls whether you can add links to a DFS namespace. If the permissions on a DFS namespace share are read-only, you cannot create DFS links. Windows Server 2003, 2008, 2012, and 2016 defaults share permissions to read-only and Windows 2000 Server defaults share permissions to allow everyone full access. If you want to create DFS links on a DFS namespace share on a Windows Server 2003, 2008, 2012, or 2016 server computer, ensure the StorageX server service account has full permissions on the share that hosts the DFS namespace. For more information, see “StorageX server service account requirements” on page 16.

To add DFS links

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

3. Right-click the DFS namespace to which you want to add a DFS link, and then click Add Link.

4. In the Link name field, type a name for the DFS link.

5. In the Link targets field, type the UNC path to the CIFS shared folder or folder under a CIFS shared folder that you want the DFS link to target or click Browse to browse to and select the CIFS shared folder or folder under a CIFS shared folder that you want the DFS link to target.

For example, type \\FileStorageResourceName.DomainName.com\FolderName, where FileStorageResourceName is the name of the file storage resource that hosts the folder you want to specify as the link target, DomainName is the name of the domain to which the file storage resource belongs, and FolderName is the name of the CIFS shared folder you want to specify as the DFS link target.

6. If you want to create a DFS link with multiple targets, type the additional UNC paths to the CIFS shared folder or folder under a CIFS shared folder that you want the DFS link to target.

Adding multiple copies of a CIFS shared folder or of a folder under a CIFS shared folder to a DFS link provides fault tolerance and load balancing and helps control network traffic at the share level.

NOTEYou cannot add a DFS link target to a DFS link unless you first add the server that hosts the link target to My Resources.

7. In the Comment field, type a word or phrase that describes the DFS link.

8. In the Client computers cache referrals for [x] seconds field, specify the duration in seconds for how long client computers should cache link information for the DFS link.

9. If you want to specify access permissions for a DFS link target, select the DFS link target, and then complete the following steps:

a. Click Link Permissions.

b. Add or remove groups or users by clicking Add or Remove.

194 StorageX Administrator’s Guide

Page 213: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS links 4

c. If you want to allow users to see the DFS link target, select the group or user and then select the Allow check box.

d. If you want to hide the DFS link target from a group or user, select the group or user and then select the Deny check box.

10. Click OK. StorageX displays the DFS link below the name of the DFS namespace to which you added the DFS link.

After you add a DFS link, you can manage DFS links as needed. For more information, see “Managing DFS links” on page 195.

Managing DFS linksThe following topics provide information about managing DFS links:

• “Viewing DFS link properties” on page 195

• “Modifying DFS link properties” on page 196

• “Specifying referral settings for DFS links” on page 197

• “Refreshing DFS links” on page 198

• “Creating folders in DFS namespaces” on page 198

• “Deleting folders in DFS namespaces” on page 199

• “Renaming DFS links and DFS namespace folders” on page 201

• “Converting DFS links to folders” on page 201

• “Deleting DFS links” on page 202

• “Viewing DFS link targets” on page 205

• “Adding additional DFS link targets to DFS links” on page 205

• “Changing the status of DFS link targets” on page 206

• “Specifying which users and groups can view specific DFS link targets” on page 207

• “Enabling or disabling referrals for DFS link targets” on page 208

• “Overriding referral ordering for DFS link targets” on page 209

• “Deleting DFS link targets” on page 210

For more information about creating DFS links, see “Adding DFS links to DFS namespaces” on page 193.

Viewing DFS link propertiesYou can view the properties of a DFS link by selecting the DFS link in the Storage Resources view.

To view DFS link information

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

3. Expand the DFS namespace that contains the link for which you want to view properties.

4. Right-click the link, and then click Properties.

StorageX Administrator’s Guide 195

Page 214: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS links4

5. Review the DFS link property information. For more information about each field, click the Help button.

For more information about DFS links, see “Adding DFS links to DFS namespaces” on page 193 and “Managing DFS links” on page 195.

Modifying DFS link propertiesYou can modify the DFS link name and DFS link target for a DFS link in the Storage Resources view. You can also modify link comments and the duration in seconds for how long client computers cache information for the link for DFS links in the Storage Resources view.

To modify DFS link properties

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

3. Expand the DFS namespace that contains the DFS link for which you want to modify properties, right-click the DFS link, and then click Properties.

4. If you want to change the name of a DFS link, click the Link Properties tab, then type a new name for the DFS link in the Link name field.

5. If you want to change the comment for a DFS link, click the Link Properties tab, then type a new description for the DFS link in the Comment field.

6. If you want to change the target of a DFS link, click the Link Properties tab, then select the DFS link target you want to change in the Link targets field and type the UNC path to the new shared folder or folder under a shared folder that you want the DFS link to target or click Browse to browse to and select the new shared folder or folder under a shared folder that you want the DFS link to target.

For example, type \\ComputerName.DomainName.com\FolderName, where ComputerName is the name of the computer that hosts the folder you want to specify as the DFS link target, DomainName is the name of the domain to which the computer belongs, and FolderName is the name of the shared folder you want to specify as the link target.

7. If you want to specify access permissions for a DFS link target, click the Link Properties tab, then select the DFS link target and complete the following steps:

a. Click Link Permissions.

b. Add or remove groups or users by clicking Add or Remove.

c. If you want to allow users to see the DFS link target, select the group or user and then select the Allow check box.

d. If you want to hide the DFS link target from a group or user, select the group or user and then select the Deny check box.

8. If you want to change the duration in seconds for how long client computers should cache link information for the DFS link, click the Referral Settings tab, then specify the duration in seconds. When the cache period for the DFS link expires, the client computer requests new referral information for the DFS link.

196 StorageX Administrator’s Guide

Page 215: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS links 4

Entering a low value in the Client computers cache referrals for [x] seconds field increases network traffic. Entering a high value reduces network traffic at the possible expense of updated share information. If you set the DFS link cache value too high, client computers may not pick up changes to DFS links until they restart.

9. Click OK.

10. If you have an identical link under a different DFS namespace, when StorageX displays the Modify Related Namespace Links dialog box, complete the following steps:

a. If you want to modify the identical link, select the check box in front of the identical link you want to modify.

b. If you do not want to modify the identical link, clear the check box in front of the identical link.

c. Click OK.

For more information about DFS links, see “Adding DFS links to DFS namespaces” on page 193 and “Managing DFS links” on page 195.

Specifying referral settings for DFS linksA referral is an ordered list of DFS link targets that client computers receive from a domain controller or DFS namespace when a client computer accesses the DFS namespace or a DFS link with link targets. After the client computer receives the referral, the client computer attempts to access the first DFS link target in the list. If the DFS link target is not available, the client computer attempts to access the next target.

DFS link targets in the client’s site are always listed first in a referral.

DFS link targets outside of the client’s site are listed according to the ordering method you specify on the DFS namespace.

DFS links inherit the DFS link target ordering method you specify for the DFS namespace. However, you can override the ordering method specified on the DFS namespace for specific DFS links.

This topic explains how to override the referral order method specified on the DFS namespace for specific DFS links, including how long client computers should cache referrals.

For more information specifying referral settings for DFS namespaces, see “Specifying referral settings for DFS namespaces” on page 183.

To specify referral settings for a DFS link

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

3. Browse to the DFS link where you want to specify referral settings, and then click Properties.

4. Click the Referral Settings tab.

5. In the Client computers cache referrals for [x] seconds field, specify the duration in seconds for how long client computers should cache referrals.

6. If you want to override the DFS namespace referral settings and exclude DFS link targets outside of the client computer’s site, select the Exclude targets outside of the client’s site check box. For more information about this option, click the Help button on the dialog box.

StorageX Administrator’s Guide 197

Page 216: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS links4

7. If DFS link targets become unavailable, you can configure client computers to fail back to preferred DFS link targets after they are restored.

Select the Clients fail back to preferred targets check box if you want client computers to fail back to preferred DFS link targets after the DFS link targets are restored.

NOTEFor fail back to work, client computers must meet DFS namespace client computer requirements. For more information, see “DFS namespace client computer operating system requirements” on page 168.

8. Click OK.

9. If you have an identical link under a different DFS namespace, when StorageX displays the Modify Related Namespace Links dialog box, complete the following steps:

a. If you want to modify the identical link, select the check box in front of the identical link you want to modify.

b. If you do not want to modify the identical link, clear the check box in front of the identical link.

c. Click OK.

Refreshing DFS linksRefreshing DFS links updates the contents for a DFS link displayed in the Storage Resources view. When you refresh DFS links, StorageX gathers updated information from the network for all of the DFS link targets specified for the DFS link.

To refresh a DFS link

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

3. Expand the DFS namespace that contains the DFS link that you want to refresh, right-click the DFS link, and then click Refresh.

For more information about DFS links, see “Adding DFS links to DFS namespaces” on page 193 and “Managing DFS links” on page 195.

Creating folders in DFS namespacesYou can create folders in your DFS namespace to organize your links. StorageX displays the DFS namespace folders you create to help you organize DFS links in a DFS namespace alphabetically in the Storage Resources view. You can add DFS links to DFS namespace folders and move folders in a DFS namespace and their links to another folder in the DFS namespace.

The permissions on a DFS namespace share control whether you can create folders in the DFS namespace.

If the permissions on a DFS namespace share are read-only, you cannot select the DFS namespace and right-click to create folders to logically organize DFS links in the DFS namespace. Windows Server 2003, 2008, 2012, and 2016 defaults share permissions to read-only. Windows 2000 Server defaults share permissions to allow everyone full access. If you want to create folders

198 StorageX Administrator’s Guide

Page 217: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS links 4

to organize DFS links in a DFS namespace on a Windows Server 2003, 2008, 2012, or 2016 server computer, ensure the StorageX server service account has full permissions on the share that hosts the DFS namespace. For more information, see “StorageX server service account requirements” on page 16.

You can move a DFS namespace folder and its DFS links to another folder or DFS namespace by dragging the folder to its new location. Dragging a DFS namespace folder moves only the folder structure. It does not move the file data physically stored on the file storage resource and referenced by the DFS links in the folder.

There are some differences between the way folders in DFS namespaces display in StorageX and the way folders in DFS namespaces display in the Microsoft DFS Management console. Consider the following examples:

• If you create an empty DFS namespace folder in a DFS namespace that is managed by StorageX and displays under My Resources in the Storage Resources view, StorageX displays the DFS namespace folder. However, the Microsoft DFS Management snap-in does not display the empty folder until you add DFS links to the folder.

• If you create an empty DFS namespace folder for a DFS namespace in the Microsoft DFS Management snap-in, the empty folder displays in both the Microsoft DFS Management snap-in and in StorageX. In addition, when you create an empty DFS namespace folder under a DFS namespace in the Microsoft DFS Management snap-in, by default Microsoft DFS Management creates a .DFSFolderLink link inside the folder which points to an unavailable location. The Microsoft DFS Management snap-in does not display this hidden link. However, this hidden link does display when you view the DFS namespace folders using Windows Explorer.

To create a folder for DFS links in a DFS namespace

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

3. If you want to create a folder under a DFS namespace, right-click the DFS namespace where you want to create a folder, and then click Add Folder.

4. If you want to create a folder underneath another folder, complete the following steps:

a. Expand the DFS namespace that contains the folder underneath which you want to create another folder.

b. Browse to and right-click the folder, and then click Add Folder.

5. In the Folder name field, type a name for the folder, and then click OK.

For more information about DFS links, see “Adding DFS links to DFS namespaces” on page 193 and “Managing DFS links” on page 195.

Deleting folders in DFS namespacesDelete folders that organize links in a DFS namespace when you no longer want to use the folder to organize DFS links in the DFS namespace or when you no longer want to use the DFS links in the folder.

When you delete the folder, StorageX removes the folder from the DFS namespace structure. Carefully consider the impact on client computer access to file data referenced by DFS links in DFS namespace folders.

StorageX Administrator’s Guide 199

Page 218: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS links4

If you delete a DFS namespace folder, client computers will no longer be able to access any data referenced by DFS links in the folder or any file data referenced by DFS links in other DFS namespace folders below the folder you delete.

If you placed links in a DFS namespace in a folder, when you delete all the DFS links in a folder in a DFS namespace, StorageX operates identically to the way Microsoft Windows operates:

• If Microsoft Windows Server 2003, 2008, 2012, or 2016 hosts the DFS namespace and you delete all the links under a folder, StorageX removes the folder.

• If Windows 2000 Server hosts the DFS namespace and you delete all the links under a folder, StorageX does not remove the folder. This is Microsoft Windows behavior.

Example

The DFS namespace folder Marketing under a DFS namespace contains two DFS links, a link to Brochures, and a link to Presentations. If Windows Server 2003, 2008, 2012, or 2016 hosts the DFS namespace, when you delete the DFS links Brochures and Presentations, StorageX also deletes the Marketing DFS namespace folder. If Windows 2000 Server hosts the DFS namespace, when you delete the DFS links Brochures and Presentations, StorageX does not delete the Marketing DFS namespace folder.

To delete a folder in a DFS namespace

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

3. Expand the DFS namespace that contains the folder you want to delete.

4. Browse to and select the folder you want to delete, right-click the folder, and then click Delete.

5. Click Yes.

6. Click the Events view to see events associated with deleting the folder, including any errors or warnings associated with deleting the folder.

7. Open the event associated with the deletion of the folder by double-clicking the event in the Events view to open the Event Viewer dialog box.

8. If you want to view all details for the event, click Details.

9. If you want to save the event details associated with deleting a folder that contained DFS links, in the Event Details dialog box, click Export and complete the following steps:

a. In the File name field, type a name for the file you want to export.

b. In the File location field, type the UNC path for the location where you want to save the report file or click Browse to browse to and select a location on the network where you want to save the file.

c. Click OK.

d. Click Close when the download completes. After you save the event details, you can review the information about what folders were formerly targeted by DFS links in the folder and use this information as needed for troubleshooting.

For more information about DFS links, see “Adding DFS links to DFS namespaces” on page 193 and “Managing DFS links” on page 195.

200 StorageX Administrator’s Guide

Page 219: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS links 4

Renaming DFS links and DFS namespace foldersRename DFS links or DFS namespace folders when you want to improve the organizational structure of DFS links or DFS namespace folders in a DFS namespace or when you want to revise your DFS link and folder organizational structure in the Storage Resources view.

To rename a DFS link or DFS namespace folder

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

3. Expand the DFS namespace that contains the DFS link or DFS namespace folder you want to rename.

4. Browse to and select the DFS link or DFS namespace folder you want to rename.

5. Right-click the DFS link or DFS namespace folder you want to rename, and then click Rename.

6. Type a new name for the DFS link or DFS namespace folder, and then press Enter.

7. If you have an identical link under a different DFS namespace, when StorageX displays the Modify Related Namespace Links dialog box, complete the following steps:

a. If you want to rename the identical link, select the check box in front of the identical link you want to rename.

b. If you do not want to rename the identical link, clear the check box in front of the identical link.

c. Click OK.

For more information about DFS links, see “Adding DFS links to DFS namespaces” on page 193 and “Managing DFS links” on page 195.

Converting DFS links to foldersIn the Storage Resources view, you can convert a DFS link to a DFS namespace folder. This allows you to better load-balance your storage resources by moving data in subfolders of the new namespace folder to a different resource and to make data contained in subfolders available from different locations in the namespace.

When you convert a link to a folder, the original link becomes a DFS folder, and all of the original link subfolders become DFS links. The “new” DFS links all include the settings of the original link.

If you convert a DFS link that has multiple link targets, StorageX automatically merges the subfolders for each link target, converting all subfolders into links under the same new namespace folder.

NOTEYou cannot reverse the conversion process.

To convert a DFS link to a DFS namespace folder

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

StorageX Administrator’s Guide 201

Page 220: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS links4

3. Expand the DFS namespace that contains the DFS link you want to convert to a DFS namespace folder.

4. If any targets of the DFS link you want to convert contain files in their top-level path, move or copy those files to a subfolder or other location.

NOTEIf you do not move files stored in the top level of a link target and convert the link to a namespace folder, users can no longer access those files. In that situation, the administrator needs to move the files to a different location after the fact.

5. Right-click the DFS link, and then select Convert to Folder.

6. Click Yes to confirm.

7. If you want to create a Phased Migration policy to migrate data from the original shared link folder, click Yes and follow the steps in the New Phased Migration Policy Wizard. For more information about creating Phased Migration policies, see “Creating Phased Migration policies” on page 250.

8. If you want to convert the link to a folder without migrating data, click No.

9. When finished, click OK.

For more information about DFS links, see “Adding DFS links to DFS namespaces” on page 193 and “Managing DFS links” on page 195.

Deleting DFS linksDelete a DFS link when the file data targeted by the DFS link is obsolete or no longer available. When you delete a DFS link, StorageX removes the DFS link from the DFS namespace structure. However, StorageX does not delete the CIFS shared folder or folder under a CIFS shared folder that was the target of the DFS link.

Carefully consider the impact of client computer access to the file data referenced by the DFS link before you delete the DFS link. Once you delete a DFS link, client computers that use the DFS link to access file data will no longer be able to access any data referenced by the DFS link.

If you delete a DFS link and the DFS link is the last object in a folder, in addition to deleting the DFS link, DFS also deletes the parent folder. DFS also performs a recursive check to see if the next parent folder in the hierarchy no longer contains objects due to the deletion of the DFS link. If the next parent folder in the hierarchy also no longer contain objects, DFS deletes this parent folder as well. DFS continues these recursive checks and deletions until it either finds a parent folder with more than one object in it or it reaches the DFS namespace level. This recursive behavior is standard Microsoft DFS behavior.

Consider the following examples:

Example 1Assume you have a DFS namespace with the structure shown in the following image:

202 StorageX Administrator’s Guide

Page 221: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS links 4

You delete the 2013 Q1 Financials DFS link. When you delete the 2013 Q1 Financials DFS link, DFS performs a recursive deletion as follows:

• DFS determines that the 2013 Q1 Financials DFS link was the only object in the 2013 folder, so DFS deletes the 2013 folder.

• DFS then looks at the 2013 parent folder, the Finance folder. Since there is no other object in the Finance folder, DFS also deletes the Finance folder.

• DFS is now at the DFS namespace level, so the recursive checks stop.

In this scenario, after you delete the 2013 Q1 Financials DFS link your DFS namespace structure now displays as shown in the following image:

Example 2Assume you have a DFS namespace with the structure shown in the following image:

Once again, you delete the 2013 Q1 Financials DFS link. When you delete the 2013 Q1 Financials DFS link, DFS performs a recursive deletion as follows:

• DFS determines that the 2013 Q1 Financials DFS link was the only object in the 2013 folder, so DFS deletes the 2013 folder.

• DFS then looks at the 2013 parent folder, the Finance folder. However, since there is another object in the Finance folder, the 2012 folder, in the parent Finance folder, the recursive deletion stops.

In this scenario, after you delete the 2013 Q1 Financials DFS link, your DFS namespace structure now displays as shown in the following image:

StorageX Administrator’s Guide 203

Page 222: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS links4

To delete a DFS link

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

3. Expand the DFS namespace that contains the DFS link you want to delete.

4. Right-click the DFS link that you want to delete, and then click Delete.

5. Click Yes.

6. If you have an identical link under a different DFS namespace, when StorageX displays the Delete Related Namespace Links dialog box, complete the following steps:

a. If you want to delete the identical link, select the check box in front of the identical link you want to delete.

b. If you do not want to delete the identical link, clear the check box in front of the identical link.

c. Click OK.

7. Click the Events view to see events associated with deleting a DFS link, including any errors or warnings associated with deleting the DFS link.

8. Open the event associated with the deletion of the DFS link by double-clicking the event in the Events view to open the Event Viewer dialog box.

9. If you want to view all details for the event, click Details.

10. If you want to save the event details associated with deleting a DFS link, in the Event Details dialog box, click Export and complete the following steps:

a. In the File name field, type a name for the file you want to export.

b. In the File location field, type the UNC path for the location where you want to save the report file or click Browse to browse to and select a location on the network where you want to save the file.

c. Click OK.

d. Click Close when the download completes. After you save the event details, you can review the information about what folders were formerly targeted by DFS links and use this information as needed for troubleshooting.

For more information about DFS links, see “Adding DFS links to DFS namespaces” on page 193 and “Managing DFS links” on page 195.

204 StorageX Administrator’s Guide

Page 223: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS links 4

Viewing DFS link targetsA DFS link target is the CIFS shared folder or folder under a CIFS shared folder that a DFS link references. You can view one target or all the targets of a DFS link.

To view the target of a DFS link

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, expand the My Resources folder.

3. Expand the DFS namespace that contains the DFS link for which you want to view DFS link targets.

4. Select the DFS link for which you want to view DFS link targets.

5. Right-click the DFS link for which you want to view DFS link targets, and then click Properties.

6. In the Link targets field, review the list of DFS link targets.

For more information about DFS links, see “Adding DFS links to DFS namespaces” on page 193 and “Managing DFS links” on page 195.

Adding additional DFS link targets to DFS linksA DFS link can have one or more DFS link targets. A DFS link target is the CIFS shared folder or a folder under a CIFS shared folder that the DFS link references.

When you create a DFS link, you must specify at least one DFS link target. However, a DFS link can have more than one DFS link target.

For fault-tolerance, it is often useful to have multiple copies of the same file data stored on different file storage resources. If one file storage resource is unavailable, client computers can still access the file data on a different resource.

It may also be useful to have multiple copies of the same file data stored on different file storage resources for performance reasons. For example, if users in a branch office want to access a very large file, users will typically experience much better performance getting a copy of the file from a file storage resource in their local branch, rather than getting a copy of the file from a file storage resource located across the country or across the world.

Once you create a DFS link with an initial link target, you can go back and add additional DFS link targets as needed.

This topic explains how to add additional DFS link targets to DFS links. For more information about creating a new DFS link, see “Adding DFS links to DFS namespaces” on page 193.

To add an additional DFS link target to a DFS link

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, expand the My Resources folder.

3. Expand the DFS namespace and browse to the DFS link where you want to add an additional DFS link target.

4. Right-click the DFS link for which you want to specify an additional target, and then click Properties.

5. On the Link Properties tab, under Link targets, click the folder icon.

StorageX Administrator’s Guide 205

Page 224: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS links4

6. Type the UNC path to the CIFS shared folder or folder under a CIFS shared folder you want to add as an additional DFS link target, or click the ellipsis button (...) to browse to and select the folder you want to add as an additional DFS link target.

NOTEYou cannot add a DFS link target to a DFS link unless you first add the server that hosts the link target to My Resources.

7. If you do not want the new link target to be enabled by default, clear the checkbox next to the new target.

8. Click OK.

9. If you have an identical link under a different DFS namespace, when StorageX displays the Modify Related Namespace Links dialog box, complete the following steps:

a. If you want to add the new target to the identical link, select the check box in front of the identical link you want to modify.

b. If you do not want to add the new target to the identical link, clear the check box in front of the identical link.

c. Click OK.

Changing the status of DFS link targetsYou can change the storage status of a DFS link target associated with a DFS link.

A DFS link target is the CIFS shared folder or a folder under a CIFS shared folder that the DFS link references.

Changing the storage status of a DFS link target associated with a DFS link does not remove the target from the DFS link. The target becomes temporarily unavailable to client computers and information about the DFS link is not included in referrals to the client computers. Referrals for the DFS link do not contain information about the offline DFS link target, although client computers already accessing the target continue to do so until they request a fresh referral.

Consider changing the storage status of a DFS link target for a DFS link in a disaster recovery scenario. If a DFS link has multiple DFS link targets, when a file storage resource that stores data referenced by a DFS link target becomes unavailable, you can specify that the DFS link target that refers to that storage location is offline. You can also specify that a different DFS link target that refers client computers to the same folder on a different file storage resource be brought online.

To change the status of a DFS link target on a DFS namespace

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, expand the My Resources folder.

3. Expand the DFS namespace that contains the DFS link with the DFS link target for which you want to change the status, and browse to and select the DFS link.

4. In the center pane, under Link Targets, right-click the DFS link target for which you want to change the status.

5. If the DFS link target is currently enabled, and you want to disable the DFS link target, click Disable Target.

206 StorageX Administrator’s Guide

Page 225: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS links 4

6. If the DFS link target is currently disabled, and you want to enable the DFS link target, click Enable Target.

7. If you have an identical link under a different DFS namespace, when StorageX displays the Modify Related Namespace Links dialog box, complete the following steps:

a. If you want to modify link targets for the identical link, select the check box in front of the identical link you want to modify.

b. If you do not want to modify link targets for the identical link, clear the check box in front of the identical link.

c. Click OK.

For more information about DFS links, see “Adding DFS links to DFS namespaces” on page 193 and “Managing DFS links” on page 195.

Specifying which users and groups can view specific DFS link targetsIf you have a domain-based DFS namespace operating in Windows 2008 Server mode with access-based enumeration enabled on the namespace, you can specify which users and groups can view specific DFS link targets.

This topic explains how to specify which users and groups can view specific DFS link targets.

For more information about enabling access-based enumeration for domain-based DFS namespaces, see “Enabling access-based enumeration for DFS namespaces” on page 182.

To specify which users and groups can view specific DFS link targets

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

3. Expand the domain-based DFS namespace and browse to the DFS link where you want to specify access permissions.

4. Right-click the DFS link for which you want to specify access permissions, and then click Properties.

5. On the Link Properties tab, under Link targets, select the DFS link target for which you want to specify access permissions.

6. Click Link Permissions.

7. Add or remove groups or users by clicking Add or Remove.

8. If you want to allow specific groups or users to see the DFS link target, select the group or user and then select the Allow check box.

9. If you want to hide the DFS link target from specific groups or users, select the group or user and then select the Deny check box.

10. Click OK, and then click OK again.

11. If you have an identical link under a different DFS namespace, when StorageX displays the Modify Related Namespace Links dialog box, complete the following steps:

StorageX Administrator’s Guide 207

Page 226: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS links4

a. If you want to modify the identical link, select the check box in front of the identical link you want to modify.

b. If you do not want to modify the identical link, clear the check box in front of the identical link.

c. Click OK.

Enabling or disabling referrals for DFS link targetsYou can enable or disable referrals for DFS link targets in the Storage Resources view.

A DFS link target is the CIFS shared folder or a folder under a CIFS shared folder that the DFS link references.

When you create a DFS link, you must specify at least one DFS link target. However, a DFS link can have more than one DFS link target.

A referral is an ordered list of targets that a client computer receives from a domain controller or domain-based DFS namespace when the user accesses the namespace.

After the client computer receives the referral, the client computer uses the DFS link targets provided by the DFS link to access data stored in the CIFS shared folder or folder under a CIFS shared folder that the DFS link target references.

If the file storage resource that hosts the CIFS shared folder or folder under a CIFS shared folder that the DFS link target references is not available, the client computer attempts to access the next DFS link target on the list.

If referrals are enabled for a DFS link target, client computers can use the DFS link target to access the data the DFS link target references. By default, DFS link targets are enabled when you create them. For more information, see “Adding DFS links to DFS namespaces” on page 193 and “Adding additional DFS link targets to DFS links” on page 205.

If referrals are disabled for a DFS link target, client computers are not directed to the data the DFS link target references. This is useful if you need to temporarily take a file storage resource that hosts the data referenced by the DFS link target offline for maintenance.

To enable or disable referrals for DFS link targets

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, expand the My Resources folder.

3. Expand the DFS namespace and browse to and select the DFS link where you want to enable or disable referrals for DFS link targets.

4. In the center pane, under Link Targets, StorageX displays the DFS link targets configured for the selected DFS link.

The Target field displays the name of the DFS link target, and the State field displays if the DFS link target is enabled or disabled.

If the domain-based DFS namespace server is enabled, Online displays.

If the domain-based DFS namespace server is disabled, Offline displays.

5. If you want to enable referrals for a DFS link target, complete the following steps:

208 StorageX Administrator’s Guide

Page 227: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS links 4

a. Right-click the DFS link target you want to enable, and then click Properties.

b. Select the Enable referrals for this target check box.

6. If you want to disable referrals for a DFS link target, complete the following steps:

a. Right-click the DFS link target you want to disable, and then click Properties.

b. Clear the Enable referrals for this target check box.

7. Click OK.

8. If you have an identical link under a different DFS namespace, when StorageX displays the Modify Related Namespace Links dialog box, complete the following steps:

a. If you want to modify the target for the identical link, select the check box in front of the identical link you want to modify.

b. If you do not want to modify the target for the identical link, clear the check box in front of the identical link.

c. Click OK.

For more information about creating DFS link targets, see “Adding DFS links to DFS namespaces” on page 193 and “Adding additional DFS link targets to DFS links” on page 205. For more information about overriding referral ordering for DFS link targets, see “Overriding referral ordering for DFS link targets” on page 209.

Overriding referral ordering for DFS link targetsYou can override referral order for DFS link targets in the Storage Resources view.

A DFS link target is the CIFS shared folder or a folder under a CIFS shared folder that the DFS link references.

When you create a DFS link, you must specify at least one DFS link target. However, a DFS link can have more than one DFS link target.

A referral is an ordered list of targets that a client computer receives from a domain controller or domain-based DFS namespace when the user accesses the namespace.

After the client computer receives the referral, the client computer uses the DFS link targets provided by the DFS link to access data stored in the CIFS shared folder or folder under a CIFS shared folder that the DFS link target references.

If the file storage resource that hosts the CIFS shared folder or folder under a CIFS shared folder that the DFS link target references is not available, the client computer attempts to access the next DFS link target on the list.

By default, each DFS link target in a referral is ordered according to the ordering method specified for the DFS link on the Referral Settings tab on the DFS Link Properties dialog box. For more information about specifying the ordering method for a DFS link, see “Specifying referral settings for DFS links” on page 197.

However, you can refine how DFS link targets are ordered by setting priority on individual DFS link targets. For example, you can specify that a DFS link target is first among all DFS link targets, last among all DFS link targets, or first (or last) among all DFS link targets of equal cost.

StorageX Administrator’s Guide 209

Page 228: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS links4

To override referral ordering for DFS link targets

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, expand the My Resources folder.

3. Expand the DFS namespace and browse to and select the DFS link with the DFS link target where you want to override referral ordering.

4. In the center pane, under Link Targets, StorageX displays the DFS link targets configured for the selected DFS link.

5. Right-click the DFS link target where you want to override referral ordering, and then click Properties.

6. Select the Override referral ordering check box, and then select the target priority setting you want to use. For more information about each setting, click the Help button on the dialog box.

7. Click OK.

8. If you have an identical link under a different DFS namespace, when StorageX displays the Modify Related Namespace Links dialog box, complete the following steps:

a. If you want to modify the target for the identical link, select the check box in front of the identical link you want to modify.

b. If you do not want to modify the target for the identical link, clear the check box in front of the identical link.

c. Click OK.

For more information about creating domain-based DFS namespace servers, see “Creating domain-based DFS namespace servers” on page 189. For more information about managing domain-based DFS namespace servers, see “Managing domain-based DFS namespace servers” on page 190.

Deleting DFS link targetsDelete a DFS link target when you no longer want the DFS link to target the CIFS shared folder or folder under a CIFS shared folder specified as the link target.

If a DFS link contains multiple DFS link targets, you can delete a DFS link target without deleting the DFS link from the DFS namespace.

If a DFS link has a single DFS link target, when you delete the DFS link target, the DFS link itself is also deleted. However, the DFS link is removed only from the logical structure of the DFS namespace. The CIFS shared folder or folder under a CIFS shared folder on the file storage resource that the DFS link referenced is not deleted from its current storage location.

If you delete a DFS link with a single DFS link target, and the DFS link is the only remaining object in a folder, in addition to deleting the DFS link target and DFS link, DFS also deletes the parent folder. DFS also performs a recursive check to see if the next parent folder in the hierarchy no longer contains objects due to the deletion of the DFS link. If the next parent folder in the hierarchy also no longer contain objects, DFS deletes this parent folder as well. DFS continues these recursive checks and deletions until it either finds a parent folder with more than one object in it or it reaches the DFS namespace level. This recursive behavior is standard Microsoft DFS behavior.

Consider the following examples:

210 StorageX Administrator’s Guide

Page 229: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS links 4

Example 1Assume you have a DFS namespace with the structure shown in the following image:

The DFS link 2013 Q1 Financials has only one DFS link target. When you delete the only DFS link target that the DFS link has, DFS performs a recursive deletion as follows:

• DFS determines that the 2013 Q1 Financials DFS link was the only object in the 2013 folder, so DFS deletes the 2013 folder.

• DFS then looks at the 2013 parent folder, the Finance folder. Since there is no other object in the Finance folder, DFS also deletes the Finance folder.

• DFS is now at the DFS namespace level, so the recursive checks stop.

In this scenario, after you delete the only DFS link target that the 2013 Q1 Financials DFS link had, your DFS namespace structure now displays as shown in the following image:

Example 2Assume you have a DFS namespace with the structure shown in the following image:

Once again, the DFS link 2013 Q1 Financials has only one DFS link target. When you delete the only DFS link target that the DFS link has, DFS performs a recursive deletion as follows:

• DFS determines that the 2013 Q1 Financials DFS link was the only object in the 2013 folder, so DFS deletes the 2013 folder.

• DFS then looks at the 2013 parent folder, the Finance folder. However, since there is another object in the Finance folder, the 2012 folder, in the parent Finance folder, the recursive deletion stops.

StorageX Administrator’s Guide 211

Page 230: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing DFS links4

In this scenario, after you delete the DFS link target for the 2013 Q1 Financials DFS link, your DFS namespace structure now displays as shown in the following image:

To delete a DFS link target

1. In the StorageX Console, click the Storage Resources tab.

2. Expand the My Resources folder.

3. Expand the DFS namespace that contains the DFS link with the DFS link target you want to delete.

4. Right-click the DFS link with the DFS link target you want to delete, and then click Properties.

5. In the Link targets field, select the DFS link target you want to delete, and then click the red x icon.

6. Click OK.

7. If you want to remove the last link target from the current link and delete the link itself, click Yes to confirm.

NOTEIf you delete the last link target from a link, StorageX deletes the link. If the link is the last link in a folder, StorageX also deletes the folder.

8. If you have an identical link under a different DFS namespace, when StorageX displays the Modify Related Namespace Links dialog box, complete the following steps:

a. If you want to delete the target for the identical link, select the check box in front of the identical link you want to modify.

b. If you do not want to delete the target for the identical link, clear the check box in front of the identical link.

c. Click OK.

For more information about DFS links, see “Adding DFS links to DFS namespaces” on page 193 and “Managing DFS links” on page 195.

212 StorageX Administrator’s Guide

Page 231: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Searching for DFS objects 4

Searching for DFS objectsIf you remove an item that stores file data targeted by a DFS namespace or DFS link from the network, client computers cannot access the file data. Confirm that a DFS namespace or DFS link does not target an item you want to remove from the network before you remove the item from the network.

You can search the following items and determine if a DFS namespace or DFS link targets the object:

• File storage resources

• File system folders

• DFS namespace folders

• CIFS shared folders or folders under CIFS shared folders

For example, if you want to remove a file storage resource from the network, search the DFS namespace to confirm that a DFS namespace or DFS link does not target any file system resources on the file storage resource. If the search identifies that a DFS namespace or DFS link does target the file storage resource, update the DFS namespace or DFS link to target a new item before you remove the file storage resource from the network. Once your search results show that no DFS namespaces or DFS links target file system resources on the file storage resource, you can remove the file storage resource from the network.

Searching only finds references to DFS objects in DFS namespaces that you added to StorageX using the Add DFS namespace command or that you created in the Storage Resources view using the Create DFS namespace command. Searching does not find references to DFS objects in existing DFS namespaces that have not been added to StorageX using the Add DFS namespace command or created in StorageX using the Create DFS namespace command.

For example, assume you add a Windows file storage resource called BJP-FSR-01 that hosts two existing standalone DFS namespaces. The first standalone DFS namespace is called BJP Corporate. The second standalone DFS namespace is called BJP Americas. After you add the Windows file storage resource that hosts the two standalone DFS namespaces, BJP-FSR-01, to My Resources, the BJP Corporate and BJP Americas DFS namespaces display under the BJP-FSR-01 Windows computer in My Resources. However, these two standalone DFS namespaces are not yet managed by StorageX, since you have not yet added them to My Resources using the Add DFS namespace command. Once you add both the BJP Corporate as well as the BJP Americas DFS namespaces to My Resources using the Add DFS namespace command, the BJP Corporate and BJP Americas DFS namespaces display directly under the My Resources folder in the Storage Resources view and you can search items and determine whether the BJP Corporate or BJP Americas DFS namespaces or DFS links in the BJP Corporate or BJP Americas DFS namespaces target the item you want to remove.

For more information about adding DFS namespaces to StorageX, see “Adding DFS namespaces to My Resources” on page 186. For more information about creating DFS namespaces using StorageX, see “Creating and configuring DFS namespaces” on page 169.

To search for DFS objects

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, under My Resources, browse to the item you want to search in order to determine if it is referenced by a DFS namespace or DFS link.

3. Right-click the item, and then click Find References.

StorageX Administrator’s Guide 213

Page 232: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Converting stand-alone namespaces to domain-based namespaces4

4. If you want to only search on the item specified in the Search path field, click This object only.

5. If you want to search on the item specified in the Search path field and any subfolders or files underneath the item, click This object and any subfolders and files under the object.

6. Click Search.

7. Review the search results to determine if a DFS namespace or DFS link targets the object.

Converting stand-alone namespaces to domain-based namespacesIf you previously created a stand-alone DFS namespace and now want to store information for that namespace in Active Directory, you can convert the stand-alone namespace to a domain-based namespace.

NOTES:

• You cannot convert a domain-based namespace to a stand-alone namespace. If you convert to a domain-based namespace, you cannot undo the conversion.

• When you convert a stand-alone namespace to a domain-based namespace, StorageX retains any explicit management delegation permissions from the original namespace. However, domain-based namespaces may have a different set of management delegation permissions from stand-alone namespaces, by default. You must manually add any groups not owned by the original namespace to the management delegation list for the converted namespace. For more information about configuring namespace management delegation, see “Delegating management for DFS namespaces” on page 183.

To convert a stand-alone namespace to a domain-based namespace

1. In the StorageX Console, click the Storage Resources tab.

2. In the left tree pane, under My Resources, browse to the stand-alone DFS namespace you want to convert.

3. Right-click the stand-alone namespace and select Convert to a domain namespace to open the Namespace Conversion Wizard.

4. Review the welcome message, and then click Next.

5. In the Host server computer name field, type the fully qualified name of the server computer that you want to host the converted domain-based DFS namespace or click Browse to browse to and select the server computer you want to host the converted domain-based DFS namespace.

For example, type \\ComputerName.DomainName.com, where ComputerName is the name of the server computer that you want to host the domain-based DFS namespace, and DomainName is the name of the domain to which the server computer belongs.

6. Click Next.

7. If you want to use an existing network share to store DFS namespace configuration information, click Use an existing share, and then select an existing network share from the list.

214 StorageX Administrator’s Guide

Page 233: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Converting stand-alone namespaces to domain-based namespaces 4

NOTEData Dynamics recommends you create a new network share to store namespace configuration information. If you select a share that already exists on the host server, StorageX may encounter issues with the namespace.

8. If you want to create a new network share to store DFS namespace configuration information, click Create a new share, and then complete the following steps:

a. In the Local path to share field, type the local path to the folder on the server computer you want to host the DFS namespace.

For example, type c:\FolderName, where c is the drive on the computer that will host the namespace, and FolderName is the name of the folder that will contain the domain-based DFS namespace configuration information.

b. In the Share name field, type the name of the share for the DFS namespace.

NOTEMicrosoft requires that the name of the share you use to store DFS namespace configuration information match the name of the domain-based DFS namespace you plan to create.

For example, type ShareName, where ShareName is the name of the share that will contain the domain-based DFS namespace server information.

9. Click Next.

10. In the Comment field, type a word or phrase that describes the converted domain-based DFS namespace.

11. In the Client computers cache this referral for [x] seconds field, specify the number of seconds client computers should cache referral information for the domain-based DFS namespace.

12. If you want to enable DFS in Windows Server 2008 mode, select the Enable Windows Server 2008 Mode check box. The Windows Server 2008 mode includes support for access-based enumeration and increased scalability. To use the Windows Server 2008 mode, the domain and the namespace must meet the following minimum requirements:

• The forest uses the Windows Server 2003 or higher forest functional level.

• The domain uses the Windows Server 2008 domain functional level.

• All namespace servers are running Windows Server 2008 R2 or later.

If your environment supports using DFS namespaces in Windows Server 2008 mode, select the Enable Windows Server 2008 Mode check box when you create new domain-based DFS namespaces. This mode provides additional features and scalability, and also eliminates the possible need to migrate a namespace from the Windows 2000 Server mode.

If StorageX does not display the Enable Windows Server 2008 Mode check box, your environment does not meet the requirements for running DFS namespaces in Windows Server 2008 mode.

13. Click Next.

14. If you want StorageX to automatically remove the original stand-alone namespace after converting the namespace, select the Remove the stand-alone namespace after converting check box.

StorageX Administrator’s Guide 215

Page 234: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Synchronizing DFS namespaces4

NOTEIf you click this option, all targeting options are selected and cannot be cleared.

15. If you want StorageX to automatically update any Namespace Availability policies that reference the original namespace to reference the converted namespace without removing the namespace, select the Retarget Namespace Availability policies to reference the new domain-based namespace check box.

16. If you want StorageX to automatically update any Namespace Backup policies that reference the original namespace to reference the converted namespace without removing the namespace, select the Retarget Namespace Backup policies to reference the new domain-based namespace check box.

17. If you want StorageX to automatically update any Disaster Recovery policies that reference the original namespace to reference the converted namespace without removing the namespace, select the Retarget Disaster Recovery policies to reference the new domain-based namespace check box.

NOTEWhen you convert a stand-alone namespace that a Disaster Recovery policy uses to discover new links to monitor, StorageX does not automatically retarget the Disaster Recovery namespace path. You must manually update the Disaster Recovery policy discovery settings to use the new domain-based namespace path.

18. If you want StorageX to automatically update any Replication policies that reference the original namespace to reference the converted namespace without removing the namespace, select the Retarget Replication policies to reference the new domain-based namespace check box.

19. Click Next.

20. Review the summary information, and then click Finish to convert the stand-alone namespace to a domain-based namespace.

StorageX creates a backup of the original stand-alone namespace and stores the namespace backup in the My Backups folder in the Namespace Policies view. Then StorageX creates a new domain-based namespace with the same properties as the stand-alone namespace and displays the domain-based DFS namespace in the Storage Resources view in the My Resources folder.

For more information about backing up and restoring DFS namespaces, see “Backing up and restoring DFS namespaces” on page 220. For more information about viewing domain-based DFS namespaces, see “Viewing DFS namespaces” on page 180. For more information about the Storage Resources view and the My Resources folder in the Storage Resources view, see “Understanding the Storage Resources view” on page 67.

Synchronizing DFS namespacesStorageX enables users to synchronize the logical structures of DFS namespaces across multiple Windows servers, using Namespace Availability policies. You can designate a primary namespace to use as your master and then select one or more target namespaces you want to keep synchronized with the primary.

216 StorageX Administrator’s Guide

Page 235: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Synchronizing DFS namespaces 4

This approach lets you use the same namespace structure throughout your environment without funneling all traffic through a single namespace server. This can help with load balancing, as well as with fault tolerance.

The following topics provide information about synchronizing namespaces:

• “Creating Namespace Availability policies” on page 217

• “Running Namespace Availability policies immediately” on page 218

• “Adding or Removing Namespaces in a Namespace Availability policy” on page 219

• “Scheduling Namespace Availability policies” on page 219

For more information about adding DFS namespaces to StorageX, see “Adding DFS namespaces to My Resources” on page 186. For more information about creating DFS namespaces using StorageX, see “Creating and configuring DFS namespaces” on page 169.

Creating Namespace Availability policiesIf you want to configure DFS namespace synchronization, you can use the Namespace Availability Policy Wizard to create one or more Namespace Availability policies. Namespace Availability policies automatically synchronize your target namespaces with the specified primary namespace.

To create a new Namespace Availability policy

1. In the StorageX Console, click the Namespace Policies tab.

2. In the left tree pane, right-click the My Policies folder, and then select New > Create Availability Policy to open the Namespace Availability Policy Wizard.

3. Review the welcome message, and then click Next.

4. Specify a name and description for the new policy, and then click Next.

5. In the Select Primary Namespace dialog box, select the DFS namespace you want to use as the primary namespace.

6. If you want to select a namespace that is not already listed, complete the following steps:

a. Click Add Namespace.

b. Type the DFS namespace path of the DFS namespace you want to add to the Select Primary Namespace window or click Browse to browse to and select the DFS namespace you want to add.

c. Click OK. StorageX adds the namespace to the Select Primary Namespace window and selects the new namespace by default.

7. Click Next.

8. In the Select Target Namespaces dialog box, select one or more DFS namespaces you want to synchronize with the primary namespace.

9. If you want to select a namespace that is not already listed, complete the following steps:

a. Click Add Namespace.

b. Type the DFS namespace path of the DFS namespace you want to add to the Select Target Namespaces window or click Browse to browse to and select the DFS namespace you want to add.

StorageX Administrator’s Guide 217

Page 236: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Synchronizing DFS namespaces4

c. Click OK. StorageX adds the namespace to the Select Target Namespaces window and selects the new namespace by default.

10. Click Next.

11. If you want to automatically run the Namespace Availability policy on a schedule, complete the following steps:

a. In the Namespace Availability Policy Schedule dialog box, select Use schedule.

NOTEThis option is selected by default.

b. Select an existing schedule to use or click New to define a new schedule.

c. In the Schedule Task field, specify whether you want to run the policy only once, or on a per minute, hourly, daily, or weekly basis.

d. Specify a start time for the schedule you want to use.

e. Specify how frequently you want the policy to run, depending on the Schedule Task setting.

f. If you want to configure an end date for the policy, click Advanced, specify an end date, and then click OK.

g. If you want to configure a one-time, daily, or weekly scheduled policy to repeat, click Advanced, specify how frequently you want the policy to repeat, and then click OK.

12. Click Next.

13. Review the summary information, and then click Finish.

StorageX creates the Namespace Availability policy and displays the policy in the Namespace Policies view in the My Policies folder.

StorageX does not run the policy until the first schedule event occurs. If you want to force a Namespace Availability policy to run before or between schedule events, right-click the policy name in the tree and select Run.

Running Namespace Availability policies immediatelyAfter you create a Namespace Availability policy, you can wait for the policy to run on the default schedule specified for the policy on the Policy Schedule tab, or you can choose to run the policy immediately. This topic explains how to run Namespace Availability policies immediately.

For more information about scheduling Namespace Availability policies, see “Scheduling Namespace Availability policies” on page 219.

For more information about using the Namespace Availability Policy Wizard to create Namespace Availability policies, see “Creating Namespace Availability policies” on page 217.

To run a Namespace Availability policy immediately

1. In the StorageX Console, click the Namespace Policies tab.

2. In the left tree pane, browse to and select the Namespace Availability policy you want to run, and then in the right pane, review the policy summary information.

3. In the left tree pane, right-click the policy and then click Properties.

218 StorageX Administrator’s Guide

Page 237: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Synchronizing DFS namespaces 4

4. Click each tab and verify that the policy is configured with the appropriate settings, and then click OK.

For more information about the settings on each tab, click the Help button on the dialog box.

5. In the left tree pane, right-click the Namespace Availability policy and then click Run.

Adding or Removing Namespaces in a Namespace Availability policyIf you create a Namespace Availability policy and then need to add additional target namespaces, remove a namespace, or designate a target namespace as the new primary namespace, you can add, remove, or modify your primary and target namespaces on the Namespaces To Keep in Sync tab of the policy Properties.

For more information about using the Namespace Availability Policy Wizard to create Namespace Availability policies, see “Creating Namespace Availability policies” on page 217.

To add, remove, or configure synchronized namespaces

1. In the StorageX Console, click the Namespace Policies tab.

2. In the left tree pane, right-click the policy you want to modify and then click Properties.

3. Click the Namespaces to Keep in Sync tab.

4. If you want to add a namespace that is not already listed, complete the following steps:

a. Click Add Namespace.

b. Type the DFS namespace path of the DFS namespace you want to add to the window or click Browse to browse to and select the DFS namespace you want to add.

c. Click OK.

5. If you want to remove a listed namespace, select the namespace and click Remove Namespace.

6. If you want to designate a target namespace as the primary namespace for the policy, select the namespace and click Make Primary Namespace. StorageX will use the designated namespace as the primary namespace when running the Namespace Availability policy.

NOTEYou must designate one primary namespace for each Namespace Availability policy. You cannot have a policy with only target namespaces or a policy with more than one primary namespaces.

7. When finished, click OK.

Scheduling Namespace Availability policiesIf you did not configure a schedule when creating a Namespace Availability policy or want to change an existing schedule, you can modify the policy schedule settings on the Policy Schedule tab of the policy Properties.

StorageX Administrator’s Guide 219

Page 238: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Backing up and restoring DFS namespaces4

To schedule a Namespace Availability policy

1. In the StorageX Console, click the Namespace Policies tab.

2. In the left tree pane, right-click the policy you want to schedule and then click Properties.

3. Click the Policy Schedule tab.

4. Select the Enabled check box.

5. If you want to create a new schedule, click New and configure a new schedule.

6. If you want to modify an existing schedule, select the schedule from the list and modify it as needed.

7. If you want to delete a schedule, select the schedule from the list and click Delete.

8. When finished, click OK.

Backing up and restoring DFS namespacesStorageX provides users the ability to back up and restore namespace structures using Namespace Backup policies. These policies help you to avoid losing valuable DFS namespace configuration information in the event of a failure in your environment.

You can schedule a Namespace Backup policy to run on a schedule you configure. StorageX can automatically run Namespace Backup policies on an hourly, daily, or weekly basis, as necessary. You can also manually back up a selected namespace at any time.

After backing up a namespace, you can then restore that namespace when necessary.

NOTENamespace Backup policies do not back up file data referenced by the links in a namespace, only the structure of the namespace itself. If you want to back up your file data, create a Disaster Recovery or Replication policy. For more information about Disaster Recovery or Replication policies, see “Creating and Managing Disaster Recovery and Replication Policies” on page 373.

The following topics provide information about backing up and restoring namespaces:

• “Creating Namespace Backup policies” on page 220

• “Manually backing up namespaces” on page 222

• “Browsing namespace backups” on page 222

• “Restoring namespace backups” on page 223

For more information about adding DFS namespaces to StorageX, see “Adding DFS namespaces to My Resources” on page 186. For more information about creating DFS namespaces using StorageX, see “Creating and configuring DFS namespaces” on page 169.

Creating Namespace Backup policiesIf you want to regularly back up your DFS namespaces on a specific schedule, you can use the Namespace Backup Policy Creation Wizard to create one or more Namespace Backup policies. Namespace Backup policies let you automatically back up your namespace metadata and configure how many backups you want to retain at a given time.

220 StorageX Administrator’s Guide

Page 239: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Backing up and restoring DFS namespaces 4

To create a new Namespace Backup policy

1. In the StorageX Console, click the Namespace Policies view.

2. In the left tree pane, right-click the My Policies folder, and then select New > Create Backup Policy to open the Namespace Backup Policy Creation Wizard.

3. Review the welcome message, and then click Next.

4. Specify a name and description for the new policy, and then click Next.

5. In the Select Namespaces window, select the DFS namespace or namespaces you want to back up.

6. If you want to back up a namespace that is not already listed, complete the following steps:

a. Click Add Namespace.

b. Type the DFS namespace path of the DFS namespace you want to add to the Select Namespaces window or click Browse to browse to and select the DFS namespace you want to add.

c. Click OK. StorageX adds the namespace to the Select Namespaces window and selects the new namespace by default.

7. Click Next.

8. In the Start Date/Time field, specify the date and time you want to start using the Namespace Backup policy.

9. If you want to back up your DFS namespace(s) on an hourly basis, select Perform Hourly Backups, then specify how frequently you want the backup policy to run and the number of backups you want to keep.

10. If you want to back up your DFS namespace(s) on a daily basis, select Perform Daily Backups, then specify how frequently you want the backup policy to run and the number of backups you want to keep.

11. If you want to back up your DFS namespace(s) on a weekly basis, select Perform Weekly Backups, then specify how frequently you want the backup policy to run and the number of backups you want to keep.

NOTEYou can specify multiple schedules to use for the same backup policy. For example, you can configure a policy to back up a particular namespace both once a day and once a month, if necessary in your environment.

12. Click Next.

13. Review the summary information, and then click Finish.

StorageX creates the Namespace Backup policy and displays the policy in the Namespace Policies view in the My Policies folder.

StorageX does not run the policy until the first schedule event occurs. If you want to force a Namespace Backup policy to run before or between schedule events, right-click the policy name in the tree and select Run.

StorageX Administrator’s Guide 221

Page 240: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Backing up and restoring DFS namespaces4

Manually backing up namespacesIn addition to backing up your DFS namespaces automatically, you can back up one or more namespaces manually, without specifying a recurring schedule of any kind.

You can back up a DFS namespace either from the Namespace Policies view or the Storage Resources view. You can manually back up multiple namespaces at one time in the Namespace Policies view. You can only back up a single namespace in the Storage Resources view. To back up a namespace in the Storage Resources view, right-click the namespace and select Create Backup, then follow the steps in the Namespace Backup Wizard. To back up multiple namespaces, follow the steps provided below.

To manually back up one or more namespaces

1. In the StorageX Console, click the Namespace Policies view.

2. In the left tree pane, right-click the My Backups folder, and then select New > Create Backup to open the Namespace Backup Wizard.

3. Review the welcome message, and then click Next.

4. Specify a name and description for the new backup, and then click Next.

5. In the Select Namespaces window, select the DFS namespace or namespaces you want to back up.

6. If you want to back up a namespace that is not already listed, complete the following steps:

a. Click Add Namespace.

b. Type the DFS namespace path of the DFS namespace you want to add to the Select Namespaces window or click Browse to browse to and select the DFS namespace you want to add.

c. Click OK. StorageX adds the namespace to the Select Namespaces window and selects the new namespace by default.

7. Click Next.

8. Review the summary information, and then click Finish.

StorageX backs up the specified namespace(s) and displays the backup in the Namespace Policies view in the My Backups folder.

Browsing namespace backupsIf you want to view the contents of a specific namespace backup, you can use the Namespace Backup Browser to review the namespaces and links the backup contains.

To view the contents of a namespace backup

1. In the StorageX Console, click the Namespace Policies tab.

2. In the left tree pane, click the My Backups folder.

3. In the center pane, right-click the backup you want to view and select Browse Backup.

4. When finished, click OK.

222 StorageX Administrator’s Guide

Page 241: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Backing up and restoring DFS namespaces 4

Restoring namespace backupsIf you need to restore a namespace to a previously backed-up state, you can use the Namespace Restore Wizard to merge changes with an existing namespace or overwrite an existing namespace entirely.

When you select the Merge option in the Namespace Restore Wizard, StorageX retains any links added since the namespace backup was created and restores any links that have been changed.

When you select the Overwrite option, StorageX restores the backed-up namespace over the target namespace, making the target namespace an exact copy of the backed-up namespace. In this process, StorageX removes any links which exist in the target namespace but do not exist in the backup.

You can also restore a backed-up namespace to a specific sub-folder within another namespace. Before restoring a backup to a sub-folder within a namespace, we recommend you back up the target namespace itself.

NOTES:

• The Merge option does not merge link properties or targets, only the links themselves. For example, if you back up a namespace, add a link target in the live namespace, and then restore the backup to the live namespace using the Merge option, StorageX overwrites the live link with the backed-up link, removing the added link target.

• If you create a backup of a stand-alone DFS namespace and convert the namespace to a domain-based DFS namespace, StorageX cannot restore the domain-based namespace to its original stand-alone state. StorageX does not modify the namespace type during the restore process.

• If you restore a backup of a stand-alone namespace to a domain-based namespace, StorageX retains any explicit management delegation permissions from the original namespace. However, domain-based namespaces may have a different set of management delegation permissions from stand-alone namespaces, by default. You must manually add any groups not owned by the original namespace to the management delegation list for the restored namespace. For more information about configuring namespace management delegation, see “Delegating management for DFS namespaces” on page 183.

To restore a namespace backup

1. In the StorageX Console, click the Namespace Policies tab.

2. In the left tree pane, right-click the My Backups folder, and then select Restore Backup to open the Namespace Restore Wizard.

3. Review the welcome message, and then click Next.

4. In the Select Backup window, select the namespace backup you want to restore, then click Next.

5. In the Select Namespace from Backup window, select the namespace you want to restore, then click Next.

NOTEA namespace backup can contain multiple backed-up namespaces, but you can only restore one namespace at a time.

StorageX Administrator’s Guide 223

Page 242: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring email notification options for Namespace policies4

6. In the Select Target Namespace or Folder window, select the namespace or namespace sub-folder to which you want to restore the selected namespace backup.

7. If you want to select a namespace that is not already listed, complete the following steps:

a. Click Add Namespace.

b. Type the DFS namespace path of the DFS namespace you want to add to the Select Target Namespace or Folder window or click Browse to browse to and select the DFS namespace you want to add.

c. Click OK. StorageX adds the namespace to the Select Target Namespace or Folder window and selects the new namespace by default.

8. Click Next.

9. If you want to merge changes in the backup with the data contained in the specified target namespace and keep any recently added links, click the drop-down menu and select Merge.

10. If you want to overwrite the target namespace with the restored namespace backup and remove any recently added links, click the drop-down menu and select Overwrite.

11. If you want to only merge or overwrite specific folders or links in the target namespace with folders or links in the backup, complete the following steps:

a. Click the drop-down menu and select Merge.

b. Click the Toggle the ability to customize the restore button.

c. Clear the check box for any change you do not want to include in the restore process.

12. Click Next.

13. Review the summary information, and then click Finish.

StorageX restores the specified namespaces and displays the restored namespaces in the Storage Resources view in the My Resources folder.

Configuring email notification options for Namespace policiesYou can configure a Namespace Availability or Namespace Backup policy to automatically notify one or more users each time the policy runs. You can set a policy to send email notifications when the policy is canceled, when the policy completes successfully, when the policy completes with warnings, or when the policy completes with errors, as necessary.

StorageX sends Namespace policy email notifications either using an existing notification profile or a new notification profile created specifically for the policy.

To configure Namespace policy email notification options

1. In the StorageX Console, click the Namespace Policies tab.

2. In the left tree pane, browse to and right-click a Namespace policy, and click Properties.

3. In the left pane, click Email Notification Settings.

4. If you want to use an existing notification profile, click the Select an existing notification profile or create a new profile list and select the profile you want to use, then click Email is enabled for the selected notification profile.

5. If you want to create a new notification profile for the policy, complete the following steps:

224 StorageX Administrator’s Guide

Page 243: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring email notification options for Namespace policies 4

a. Click the Select an existing notification profile or create a new profile list.

b. Click New.

c. Specify the SMTP settings you want to use for the new profile. For more information about the SMTP settings, click the Help button on the dialog box.

d. Specify the message settings you want to use for the new profile. For more information about the message settings, click the Help button on the dialog box.

e. Click Send Test Message to verify the profile settings are correct.

f. If you want to use the new notification profile for all notifications, click Enable all usage of this notification.

g. Click OK.

6. Click one or more criteria you want StorageX to use when sending email notifications. For more information about the possible notification criteria, click the Help button on the dialog box.

7. Click OK.

StorageX Administrator’s Guide 225

Page 244: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring email notification options for Namespace policies4

226 StorageX Administrator’s Guide

Page 245: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX Administrator’s Guide

Chapter

5

Creating and Managing Data Movement Policies

This section provides information about Data Movement (Phased Migration and Archival Migration) policies and templates. This section explains what Phased Migration and Archival Migration policies and templates are, how to create them, and how to manage them.

In this chapter•Checklist: Creating and managing Data Movement policies . . . . . . . . . . . 228

•Understanding Data Movement templates and policies . . . . . . . . . . . . . . 228

•Data Movement policy operating system requirements. . . . . . . . . . . . . . . 237

•Data Movement policy protocol requirements . . . . . . . . . . . . . . . . . . . . . . 237

•Data Movement policy planning considerations . . . . . . . . . . . . . . . . . . . . . 239

•Creating and managing templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

•Creating Phased Migration policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

•Validating Phased Migration policy settings . . . . . . . . . . . . . . . . . . . . . . . . 260

•Running Phased Migration policies immediately . . . . . . . . . . . . . . . . . . . . 262

•Scheduling Phased Migration policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

•Planning for storage resource cutover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

•Canceling Phased Migration policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

•Restarting Phased Migration policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

•Verifying Phased Migration policies completed successfully . . . . . . . . . . . 271

•Managing Phased Migration policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

•Creating Archival Migration policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

•Running Archival Migration policies immediately . . . . . . . . . . . . . . . . . . . . 296

•Scheduling Archival Migration policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

•Canceling Archival Migration policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

•Restarting Archival Migration policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

•Verifying Archival Migration policies completed successfully . . . . . . . . . . 299

•Managing Archival Migration policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

•Configuring email notification options for Data Movement policies and templates 313

•Bypassing path validation for Data Movement policies . . . . . . . . . . . . . . . 314

•Using batch files with Data Movement policies. . . . . . . . . . . . . . . . . . . . . . 315

227

Page 246: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Checklist: Creating and managing Data Movement policies5

Checklist: Creating and managing Data Movement policiesUse the following checklist to help you create and manage Data Movement policies:

Understanding Data Movement templates and policiesData Movement policies facilitate the transfer, or migration, of file data from source file storage resources to destination file storage resources. Data Movement policies include Phased Migration and Archival Migration policies.

Phased Migration policies move file data stored in CIFS shared folders or NFS exports from source file storage resources to destination file storage resources using source and destination paths defined in the policy. You can run Phased Migration policies immediately, or you can configure schedules that specify when you want the Phased Migration policies to run. For more information about Phased Migration policies, see “Understanding Phased Migration policies” on page 230.

TABLE 19 Checklist: Creating and managing Data Movement policies

Task

1 If you want to use a DFS namespace with Phased Migration or Archival Migration policies, create a DFS namespace or add an existing DFS namespace to StorageX. For more information, see “Creating and Managing DFS Namespaces” on page 159.

2 Ensure you understand how Data Movement templates and policies work. For more information, see “Understanding Data Movement templates and policies” on page 228.

3 Review Data Movement policy operating system and protocol requirements. For more information, see “Data Movement policy operating system requirements” on page 237 and “Data Movement policy protocol requirements” on page 237.

4 Review Data Movement policy planning considerations. For more information, see “Data Movement policy planning considerations” on page 239.

5 Create new Phased Migration and Archival Migration templates or modify existing Phased Migration and Archival Migration templates for use in your environment. For more information, see “Creating and managing templates” on page 248.

6 Create new Phased Migration and Archival Migration policies as needed. For more information, see “Creating Phased Migration policies” on page 250 and “Creating Archival Migration policies” on page 294.

7 Run your policies and verify they completed successfully. For more information, see the following topics:• “Running Phased Migration policies immediately” on page 262, “Scheduling Phased Migration

policies” on page 263, and “Verifying Phased Migration policies completed successfully” on page 271.

• “Running Archival Migration policies immediately” on page 296, “Running Archival Migration policies immediately” on page 296, and “Verifying Archival Migration policies completed successfully” on page 299.

8 Modify your policies and specify additional properties and actions as needed to ensure the appropriate data is scanned and migrated. For more information, see “Managing Phased Migration policies” on page 278 and “Managing Archival Migration policies” on page 301.

228 StorageX Administrator’s Guide

Page 247: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Data Movement templates and policies 5

Archival Migration policies use scan paths and the migration criteria you define in the policy to scan folders that contain file data and identify folders to move from primary storage to secondary storage. Based on the results of the Archival Migration policy scan, Archival Migration policies can generate a list of migration candidates that meet your defined criteria. You can also configure Archival Migration policies to automatically generate Phased Migration policies for each migration candidate if you prefer. For more information about Archival Migration policies, see “Understanding Archival Migration policies” on page 233.

Phased Migration policies and Archival Migration policies are not dependent on each other. Although Archival Migration policies generate Phased Migration policies, you can run an Archival Migration policy without actually migrating data, and you can create and run a Phased Migration policy by itself without first scanning for migration candidates.

Each Phased Migration and Archival Migration policy is associated with a template. For more information about Phased Migration and Archival Migration templates, see “Understanding Phased Migration and Archival Migration templates” on page 229.

The following topics provide more information about Data Movement policies:

• “Understanding Phased Migration and Archival Migration templates” on page 229

• “Understanding Phased Migration policies” on page 230

• “Understanding Archival Migration policies” on page 233

• “Understanding unsupported file and folder types for migration” on page 236

Understanding Phased Migration and Archival Migration templatesEach Phased Migration policy and Archival Migration policy in the Data Movement view is associated with a template. Templates contain common settings that are used to populate new policies with defaults. You choose a template from which the policy will inherit settings, specify source and destination paths, and modify policy settings as needed.

You can have multiple templates for each Phased Migration or Archival Migration policy type. For example, by default StorageX provides seven Phased Migration templates and four Archival Migration templates. You can modify these default templates as needed for your environment. You can also copy these existing templates to create new templates or create new templates from scratch.

Although each policy references a template, the template exists separately from the policy. Since templates are separate from policies, you can create and maintain them separately, and each template can be referenced by zero to many policies.

If you need to change multiple policies that reference the same policy template, you can just update the policy template. For example, you can change settings such as schedules, replication options, and migration options in one place, and policies associated with the template will automatically inherit the updated settings.

In addition, StorageX also provides template inheritance options that allow you to:

• Override any inherited settings on a policy

• Disassociate a policy from its template

• Re-associate a policy with a template

StorageX Administrator’s Guide 229

Page 248: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Data Movement templates and policies5

In general, updates to any settings in a template affect any policies that use that template. However, if you override a template setting in a policy, the template setting no longer applies. As an advanced option, you can force settings, which causes all settings in the policy to be overridden by the common settings in the template. For more information about managing templates, see “Creating and managing templates” on page 248.

Understanding Phased Migration policiesPhased Migration policies are policies that move file data. They can move file data stored in a source CIFS shared folder to a destination CIFS shared folder using the CIFS protocol or move file data stored in a source NFS export to a destination NFS export using the NFS protocol. In addition, Phased Migration policies can move file data from a source to a destination using the legacy Server Message Block (SMB) protocol and the Network Data Management Protocol (NDMP) in specific environments.

Phased Migration policies work at the shared folder level, not at the file storage resource, volume, storage pool, FlexGroup, or file system level. If you want to migrate file data at the file storage resource, volume, storage pool, or file system level, create Migration Projects. For more information, see “Creating and Managing Migration Projects” on page 319.

In addition to migrating or copying file data from a source resource to a destination resource, Phased Migration policies copy file and directory attributes and permissions.

NOTES:

• Phased Migration policies do not copy the offline attribute (FILE_ATTRIBUTE_OFFLINE) when copying file or directory attributes during the migration process, because the file or directory is online by default after migration. If you want to configure the migrated file or directory to be offline, you must use a third-party tool to set the offline attribute after the migration process finishes.

• When you migrate data from a folder on the source that inherits permissions from a parent folder, that inheritance is not automatically recreated on the destination. You must manually reconfigure the destination folder to inherit permissions from the new parent folder on the destination.

Phased Migration policies migrate file data in phases. This allows you to copy file data when users have access to the data, and then configure a final replication to occur at a time you specify when users are temporarily denied access to the source file data and are directed to the file data at its new location on the destination.

Phased Migration policies are divided into the following phases:

• Initial Phase

• Incremental Phase

• Final Phase

Policy Actions

Each phase can include multiple actions, depending on where in the migration process the phase occurs. When you run a Phased Migration policy, StorageX executes each action, as configured in the policy Properties.

230 StorageX Administrator’s Guide

Page 249: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Data Movement templates and policies 5

You can also run policy actions manually in the Data Movement Policies view by right-clicking the policy name and selecting Policy Actions. From that menu, you can execute the first action in the policy, re-execute the action that was last executed, or force the policy to execute the next action.

The latter option is useful if the policy previously encountered an error, or if you canceled and need to restart the policy. For more information about restarting Phased Migration policies, see “Restarting Phased Migration policies” on page 269.

Initial Phase

In the Initial Phase, the Phased Migration policy performs the following actions:

• If you want to run a batch file during the Initial Phase and you know how to write scripts and create batch files, the policy runs a batch file you specify. For more information, see “Using batch files with Data Movement policies” on page 315 and “Running batch files with Phased Migration policies” on page 286.

• Performs a baseline copy of the data

You can specify whether you always want the Phased Migration policy to proceed after each action, or if you want the Phased Migration policy to pause after each action. For example, assume that in the Initial Phase you want to pause the policy after the baseline copy of the data so you can review details about the policy run in the policy manifest, such as the data copy speed in the Initial Phase. You can then use this information to help you identify the schedule you want to specify in the Incremental phase before you advance the policy to the Incremental phase.

Incremental Phase

In the Incremental Phase, the Phased Migration policy copies file data from the source to the destination continuously according the to migration schedule you specify on the Migration Schedule tab for the policy.

You also specify one of the following options as the criteria you want StorageX to use before advancing to the Final Phase of the migration:

• Never advance automatically. The Phased Migration policy will remain in the Incremental Phase until you manually advance it to the Final Phase.

• After the next Incremental Phase run starts according to the migration schedule specified on the Migration Schedule tab, automatically advance the policy to the Final Phase immediately after the file data copy completes.

• End the Incremental Phase after the end data specified on the Incremental Phase tab. Then advance to the Final Phase based on the migration schedule specified on the Migration Schedule tab or manually advance the policy to the Final Phase.

Consider the following scenario:

If the Phased Migration policy starts two minutes before end date and time specified for the Incremental Phase, the policy will run in the Incremental Phase. However, when the Phased Migration policy advances to the Final Phase depends on when the policy run in the Incremental Phase finishes.

StorageX Administrator’s Guide 231

Page 250: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Data Movement templates and policies5

If the policy run in the Incremental Phase finishes after the end date specified on the Incremental Phase tab, the policy will immediately advance to the Final Phase.

If the policy run in the Incremental Phase finishes before the date and time specified on the Incremental Phase tab, the policy will not advance to the Final Phase until after the date and time specified on the Incremental Phase tab is reached and the policy is either scheduled to run in the Final Phase or you choose to manually run the policy.

You can also specify that you do not want the Phased Migration policy to advance if the Incremental Phase completed with any errors. When you select this option, the Phased Migration policy does not advance until you address the errors and manually advance the policy to the Final Phase.

In addition, you can specify that you want the policy to copy file data in the Incremental Phase even if the previous Incremental Phase file copy was canceled.

Final Phase

In the Final Phase, the Phased Migration policy performs the following actions:

• Updates DFS namespaces and automount map files as needed. For more information, see “How StorageX manages data access in CIFS environments with DFS namespaces” on page 242 and “How StorageX manages data access in NFS environments with automount map files” on page 245.

• If the source is a CIFS shared folder, prevents users from connecting to the file data during the final copy

• Performs a final copy of the file data

• Stops sharing the file data on the source

• If you want to run a batch file during the Final Phase and you know how to write scripts and create batch files, the policy runs a batch file you specify. For more information, see “Using batch files with Data Movement policies” on page 315 and “Running batch files with Phased Migration policies” on page 286.

You can configure a Phased Migration policy to execute all three phases in one policy run, which is typical for many file data migrations, or you can configure the Phased Migration policy to execute one or two phases and then pause and wait until you manually specify that you want the policy to continue.

Understanding Phased Migration policy creation

When you create a Phased Migration policy, first identify the Phased Migration template you want to use as a base for the Phased Migration policy. For more information, see “Creating and managing templates” on page 248 and “Viewing and modifying template properties” on page 249.

After you identify the Phased Migration template you want to use, create the new Phased Migration policy using the New Phased Migration Policy Wizard. When you use the New Phased Migration Policy Wizard, you specify the source that contains the file data you want to migrate, as well as the destination that you want to migrate the data to. For more information, see “Creating Phased Migration policies” on page 250.

After you create the Phased Migration policy, you can review the many policy settings Phased Migration policies provide and specify additional details about how you would like the Phased Migration policy to migrate file data. For more information, see “Modifying Phased Migration policy properties” on page 279, “Configuring replication options for Phased Migration policies” on page 279, and “Specifying migration options for Phased Migration policies” on page 280.

232 StorageX Administrator’s Guide

Page 251: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Data Movement templates and policies 5

If you use a DFS namespace or automount map files, you can specify that you want StorageX to update DFS namespaces or automount map files to reference the data at its new location on the destination during the Final Phase of the migration. For more information, see “How StorageX manages data access in CIFS environments with DFS namespaces” on page 242 and “How StorageX manages data access in NFS environments with automount map files” on page 245.

After you have ensured the Phased Migration policy is configured using the settings you want, you can choose to run the Phased Migration policy immediately, or you can schedule the policy. For more information, see “Running Phased Migration policies immediately” on page 262 and “Scheduling Phased Migration policies” on page 263.

After the policy runs, you can review the policy status and verify the policy completed successfully and file data migration occurred as expected. For more information, see “Verifying Phased Migration policies completed successfully” on page 271.

If you want to migrate only file data that meets specific parameters, create and run an Archival Migration policy. When you run an Archival Migration policy, the Archival Migration policy identifies a list of migration candidates. You can review the list of migration candidates identified by StorageX prior to moving the file data using Phased Migration policies. For more information, see “Understanding Archival Migration policies” on page 233 and “Creating Archival Migration policies” on page 294.

Understanding Archival Migration policiesArchival Migration policies allow you to identify folders that are candidates for migration based on the criteria you specify.

You can choose to identify the folders you want to migrate using a batch file if you know how to write scripts and create batch files. In this scenario, you can create a batch file that identifies migration candidates using the criteria that meets your organizations needs. For more information about using batch files in Archival Migration policies, see “Using batch files with Data Movement policies” on page 315 and “Running batch files with Archival Migration policies” on page 308.

You can also choose to use scan paths and migration criteria to identify the folders you want to migrate. When you specify that you want to use scan paths and migration criteria to identify the folders you want to migrate, you can specify a physical path as your source path or, if you have implemented DFS namespaces in your environment, you can specify a DFS link with a single link target as your source path.

In StorageX, a physical path is a path directly to the file storage resource. For example, a physical path is the UNC path \\FileStorageResource\ShareName, where FileStorageResource is the actual name of the file storage resource. If the file storage resource is a virtual file storage resource, or if the file storage resource has its own virtualization layer, the physical path is the UNC path to the resource.

You also specify the migration criteria you want the Archival Migration policy to use to identify migration candidates. For example, you can specify that a folder is a migration candidate when it meets one of the following conditions:

• 80% or more of its files have not been accessed with the past 9 days

• 80% or more of its files have not been created in the last two years

• The folder is more than five years old

• The folder size is greater than 5GB

StorageX Administrator’s Guide 233

Page 252: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Data Movement templates and policies5

When you create an Archival Migration policy, you first identify the Archival Migration template you want to use as a base for the Archival Migration policy. For more information, see “Creating and managing templates” on page 248 and “Viewing and modifying template properties” on page 249.

After you identify the Archival Migration template you want to use, create the new Archival Migration policy using the New Archival Migration Policy Wizard and specify whether you want to identify folders that are migration candidates using a batch file or by specifying source scan paths and migration criteria. For more information, see “Creating Archival Migration policies” on page 294.

After you create the Archival Migration policy, review the additional policy settings Archival Migration policies provide and specify additional details for the Archival Migration policy as needed. For example, you can specify if you want to receive an email notification when the Archival Migration policy completes. You can specify if you want the Archival Migration policy to automatically generate Phased Migration policies to migrate folders that are migration candidates. You can also specify when you want the Archival Migration policy scan to run. For more information, see “Modifying Archival Migration policy properties” on page 302.

You can then run the Archival Migration policy immediately, or you can run the policy according to the schedule you specified for the policy. For more information, see “Running Archival Migration policies immediately” on page 296 and “Scheduling Archival Migration policies” on page 297.

When an Archival Migration policy runs, StorageX uses the batch file or the scan paths and migration criteria you specified in the policy to identify a list of folders that meet your migration criteria. StorageX also either generates a Phased Migration policy for you to use to migrate each folder that meets your criteria or simply identifies folders that are migration candidates based on your criteria. If you want StorageX to only identify folders that are migration candidates and not create Phased Migration policies for the candidates, after StorageX identifies the candidates, you can review the migration candidates and create Phased Migration policies for candidates manually as needed in just a few clicks.

Once you have Phased Migration policies for the folders that are migration candidates, you migrate the folders using Phased Migration policies. You can run the Phased Migration policies immediately, or you can schedule the Phased Migration policies to migrate the folders using a schedule you specify in the policy. For more information, see “Running Phased Migration policies immediately” on page 262 and “Scheduling Phased Migration policies” on page 263.

Like non-archival Phased Migration policies, Phased Migration policies created as part of an Archival Migration policy also copy file and directory attributes and permissions.

NOTEPhased Migration policies do not copy the offline attribute (FILE_ATTRIBUTE_OFFLINE) when copying file or directory attributes during the migration process, because the file or directory is online by default after migration. If you want to configure the migrated file or directory to be offline, you must use a third-party tool to set the offline attribute after the migration process finishes.

The way Archival Migration policies work can vary slightly based on whether or not you are using a DFS namespace in your environment and on how you configure policy options.

If you are not using DFS namespaces in your environment, when you create Archival Migration policies, you must specify physical paths as your scan paths. When you use Archival Migration policies to identify folders you want to migrate and then generate the Phased Migration policies to actually migrate the folders, after StorageX migrates the folders from the source physical paths to the destination physical paths, users who try to access data by connecting to the old source

234 StorageX Administrator’s Guide

Page 253: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Data Movement templates and policies 5

location will no longer see the folders StorageX migrated. If you want users to be able to access data in the new destination location, you must tell users how to access the folders in the new location. In addition, based on the migration criteria you specify, some folders may be migrated to the new destination location, while other folders remain in the original source location.

For example, assume that you have a CIFS shared folder called Finance. Under the Finance CIFS shared folder, you have four additional subfolders, 2010 Data, 2011 Data, 2012 Data, and 2013 Data. You create an Archival Migration policy with the Finance CIFS shared folder as your source, and you specify as your migration criteria that you want to migrate a folder when 80% or more of its files have not been accessed within the past 90 days. You also specify that you want the Archival Migration policy to automatically generate Phased Migration policies for migration candidates.

When you run the Archival Migration policy, the Archival Migration policy analyzes the Finance folder and its subfolders determines that the 2010 Data and 2011 Data folders meet the migration criteria where 80% or more of the files have been not been accessed in the last 90 days. However, the 2012 Data and 2013 Data folders do not meet this criteria. The Archival Migration policy then generates Phased Migration policies that you can use to migrate the 2010 Data and 2011 Data folders. However, the Archival Migration policy does not generate Phased Migration policies for the 2012 Data and 2013 Data folders, because they did not meet your criteria.

When you run the Phased Migration policies, StorageX moves the 2010 Data and 2011 Data folders to a new location. However, the 2012 Data and 2013 Data folders remain in their current location, since they did not meet the migration criteria. Users who access the Finance CIFS shared folder will no longer see the 2010 Data and 2011 Data folders. However, they will still see the 2012 Data and 2013 Data folders, since these folders were not migrated. If you want users to be able to access the data in the moved folders, you must tell the users the new location of the 2010 Data and 2011 Data folders.

If you are using DFS namespaces in your environment, when you use Archival Migration policies to identify the file data you want to migrate, you can specify either a physical path or a DFS link with a single DFS link target as the source scan path for an Archival Migration policy.

NOTEYou can only specify a DFS link with a single link target as a scan path in an Archival Migration policy. If you specify a DFS link with more then one link target as a scan path in an Archival Migration policy, the Archival Migration policy ignores the DFS link with multiple targets. The Archival Migration policy does not evaluate DFS links with multiple targets when they are specified as a search path or attempt to identify any migration candidates for a DFS link with multiple targets.

When you specify a DFS link with a single target as a source scan path and then run the Archival Migration policy, StorageX uses the DFS link as the source search path, identifies migration candidates, and generates a Phased Migration policy based on the migration criteria specified in the policy. StorageX also automatically adds the DFS link to the Namespaces tab for the Phased Migration policy when generating Phased Migration policies for the Archival Migration policy.

If you have also selected the Update DFS namespace or automounts option on the Final Phase tab of the Phased Migration template associated with the Archival Migration policy, or if you select this option after the Archival Migration policy generates the Phased Migration policy, when you run the Phased Migration policy, StorageX migrates the folders based on the migration criteria you specify. StorageX also updates the DFS link to target the data in the new location.

However, the process StorageX uses to migrate folders varies when the source scan path is a DFS link with a single target rather than a physical path.

StorageX Administrator’s Guide 235

Page 254: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Data Movement templates and policies5

For example, assume that you have a CIFS shared folder called Finance. Under this CIFS shared folder, you have four additional subfolders, 2010 Data, 2011 Data, 2012 Data, and 2013 Data. You also have a DFS namespace in your environment, and in this DFS namespace is a DFS link called Finance with a single link target, the Finance CIFS shared folder.

You create an Archival Migration policy with the Finance DFS link as your source scan path. You specify as your migration criteria that you want to migrate folders when 80% or more of their files have not been accessed within the past 90 days. You also specify that you want the Archival Migration policy to automatically generate Phased Migration policies for migration candidates.

When you run the Archival Migration policy, the Archival Migration policy analyzes the 2010 Data, 2011 Data, 2012 Data, and 2013 Data folders as a group and determines that as a group, these folders meet the migration criteria where 80% or more of the files have been not been accessed in the last 90 days. The Archival Migration policy then generates a singled Phased Migration policy that you can use to migrate the Finance folder, which includes migration of the 2010 Data, 2011 Data, 2012 Data, and 2013 Data subfolders. When you run this Phased Migration policy, StorageX moves the Finance folder as well as the 2010 Data, 2011 Data, 2012 Data, and 2013 Data subfolders. Since you also selected the Update DFS namespace or automounts option on the Final Phase tab of the Phased Migration policy, the Phased Migration policy also updates the Finance DFS link to reference the Finance folder in its new location. When clients use the Finance DFS link, they continue to see the Finance folder, as well as all four subfolders.

For more information about Archival Migration templates and creating Archival Migration policies, see “Understanding Phased Migration and Archival Migration templates” on page 229 and “Creating Archival Migration policies” on page 294.

For more information about Phased Migration policies, see “Understanding Phased Migration policies” on page 230. For more information about DFS namespaces, see “Creating and Managing DFS Namespaces” on page 159.

Understanding unsupported file and folder types for migrationWhile StorageX can migrate most types of files from a source to a destination, there are some specific file and folder types that StorageX ignores during the migration process.

StorageX does not support migrating the following types of files and folders:

• Encrypted files

• Reparse points

• CIFS symbolic links

NOTEStorageX does support migrating NFS symbolic links.

• Snapshot folders

• System volume information

• Local users

• Recycle Bin

236 StorageX Administrator’s Guide

Page 255: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Data Movement policy operating system requirements 5

Data Movement policy operating system requirementsFile storage resources included in Data Movement policies must be running one of the following operating system versions:

Data Movement policy protocol requirementsIn order to use Phased Migration and Archival Migration Data Movement policies, file storage resources must be running a supported version of the CIFS, NFS, SMB, or NDMP protocol.

The following table lists supported protocol versions. For more information about supported protocols for specific resources, see the Microsoft, EMC, NetApp, and Red Hat documentation.

TABLE 20 Data Movement policy operating system requirements

Operating System Versions

Windows • Windows Server 2008 or later• Windows Server 2012 or later• Windows Server 2016 or later

Linux • Red Hat Linux 6• Red Hat Linux 7

Data ONTAP 7G • 7.2 or later

Data ONTAP 8 • 8.2 or later Cluster Mode• 8.2 7-Mode

ONTAP 9 9.0 or later

VNX OE for File 7.1.65 or later

VNXe OF for File 7.1.65 or later

OneFS • 7.0.X• 7.1.X• 7.2.X• 8.0

TABLE 21 Supported protocols

Microsoft Windows Server 2008 or later

Microsoft Windows Server 2012 or later

Microsoft Windows Server 2016 or later

EMC Isilon OneFS 7.0.X to 8.0

EMC VNX VNX OE for File 7.1.65 or later

EMC VNXe VNX OE for File 7.1.65 or later

NetApp Data ONTAP 7.2 or later

NetApp Data ONTAP 8.2 7 Mode

NetApp Data ONTAP 8.2 or later Cluster Mode

NetApp ONTAP 9.0 or later

Red Hat Enterprise Linux 6 or later

Microsoft Windows Server 2008 or later

CIFSSMB 2.1

CIFS SMB 2.1

CIFS SMB 2.1

CIFS SMB 2NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 2.0NFS 3.0

CIFS SMB 2.1NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

NFS 3.0

Microsoft Windows Server 2012 or later

CIFS SMB 2.1

CIFS SMB 3.0

CIFS SMB 3.1.1

CIFS SMB 2NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 2.0NFS 3.0

CIFS SMB 2.1NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

NFS 3.0

StorageX Administrator’s Guide 237

Page 256: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Data Movement policy protocol requirements5

Microsoft Windows Server 2016 or later

CIFS SMB 2.1

CIFS SMB 3.0

CIFS SMB 3.1.1

CIFS SMB 2NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 2.0NFS 3.0

CIFS SMB 2.1NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.1.1NFS 3.0

NFS 3.0

EMC Isilon OneFS 7.0.X to 8.0

CIFS SMB 2NFS 3.0

CIFS SMB 2NFS 3.0

CIFS SMB 2NFS 3.0

CIFS SMB 2NFS 3.0

CIFS SMB 2NFS 3.0

CIFS SMB 2NFS 3.0

CIFS SMB 2.0NFS 3.0

CIFS SMB 2.1NFS 3.0

CIFS SMB 2NFS 3.0

CIFS SMB 2NFS 3.0

NFS 3.0

EMC VNX VNX OE for File 7.1.65 or later

CIFSSMB 3.0NFS 3.0

CIFSSMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 2NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 2.0NFS 3.0

CIFS SMB 2.1NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

NFS 3.0

EMC VNXe VNX OE for File 7.1.65 or later

CIFSSMB 3.0NFS 3.0

CIFSSMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 2NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 2.0NFS 3.0

CIFS SMB 2.1NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

NFS 3.0

NetApp Data ONTAP 7.2 or later

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 2.0NFS 3.0

CIFS SMB 2NFS 3.0NDMP 4*

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 2.0NFS 3.0

CIFS SMB 2.0NFS 3.0

CIFS SMB 2.0NFS 3.0

CIFS SMB 2.0NFS 3.0

NFS 3.0

NetApp Data ONTAP 8.2 7 Mode

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 2.1NFS 3.0

CIFS SMB 2NFS 3.0NDMP 4*

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 2.0NFS 3.0

CIFS SMB 2.1NFS 3.0

CIFS SMB 2.1NFS 3.0

CIFS SMB 2.1NFS 3.0

NFS 3.0

NetApp Data ONTAP 8.2 or later Cluster Mode

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 2NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 2.0NFS 3.0

CIFS SMB 2.1NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

NFS 3.0

NetApp ONTAP 9 or later

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.1.1NFS 3.0

CIFS SMB 2NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 2.0NFS 3.0

CIFS SMB 2.1NFS 3.0

CIFS SMB 3.0NFS 3.0

CIFS SMB 3.0NFS 3.0

NFS 3.0

Red Hat Enterprise Linux 6 or later

NFS 3.0 NFS 3.0 NFS 3.0 NFS 3.0 NFS 3.0 NFS 3.0 NFS 3.0 NFS 3.0 NFS 3.0 NFS 3.0 NFS 3.0

TABLE 21 Supported protocols

Microsoft Windows Server 2008 or later

Microsoft Windows Server 2012 or later

Microsoft Windows Server 2016 or later

EMC Isilon OneFS 7.0.X to 8.0

EMC VNX VNX OE for File 7.1.65 or later

EMC VNXe VNX OE for File 7.1.65 or later

NetApp Data ONTAP 7.2 or later

NetApp Data ONTAP 8.2 7 Mode

NetApp Data ONTAP 8.2 or later Cluster Mode

NetApp ONTAP 9.0 or later

Red Hat Enterprise Linux 6 or later

238 StorageX Administrator’s Guide

Page 257: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Data Movement policy planning considerations 5

NOTE* StorageX only supports using NDMP for migrating data from NetApp Data ONTAP 8 7-Mode resources or NetApp Data ONTAP 7 resources to EMC Isilon OneFS resources, using the isi_vol_copy utility. StorageX cannot use the isi_vol_copy utility to migrate data from Isilon resources to NetApp resources. StorageX also cannot use isi_vol_copy to migrate data to or from NetApp Data ONTAP vFilers or EMC Isilon access zones. For more information about NDMP protocol requirements, see “NDMP-specific data transfer requirements and configuration” on page 246.

Data Movement policy planning considerationsReview the following planning considerations before you begin to migrate file data using Phased Migration policies or identify migration candidates using Archival Migration polices:

• “General data transfer planning considerations” on page 239

• “CIFS-specific data transfer planning considerations” on page 241

• “How StorageX manages data access in CIFS environments with DFS namespaces” on page 242

• “NFS-specific data transfer planning considerations” on page 243

• “How StorageX manages data access in NFS environments with automount map files” on page 245

• “NDMP-specific data transfer requirements and configuration” on page 246

• “Distributing file data transfer workloads using universal data engine groups” on page 248

• “Distributing file data transfer workloads using specific cluster nodes or groups” on page 248

General data transfer planning considerationsReview the following planning considerations before you configure Phased Migration and Archival Migration policies in your StorageX environment:

NOTEIf you are planning to use StorageX to transfer file data using the CIFS protocol, ensure you also review CIFS-specific data transfer planning considerations. For more information, see “CIFS-specific data transfer planning considerations” on page 241. If you are planning to use StorageX to transfer file data using the NFS protocol, ensure you also review NFS-specific data transfer planning considerations. For more information, see “NFS-specific data transfer planning considerations” on page 243. If you are planning to transfer data using the NDMP protocol, ensure you also review NDMP-specific data transfer planning considerations and requirements. For more information, see “NDMP-specific data transfer requirements and configuration” on page 246.

• Identify how much data you want to migrate and how much time it will take to migrate the data.

Use include and exclude filters sparingly because they add processing time to the migration operation and consume additional resources in the universal data engine. You can specify include and exclude filters on the Replication Filters tab for a Phased Migration policy.

• Users and applications should not be accessing the source or destination folders while StorageX is copying files from the source to the destination. If users are accessing files in source or destination folders while the Phased Migration policy is running, the files the users are accessing will be locked and StorageX will not be able to copy the files.

StorageX Administrator’s Guide 239

Page 258: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Data Movement policy planning considerations5

• Configure Phased Migration policies to copy data incrementally at night or on weekends, when either no or a low number of users are accessing the files, by specifying a migration schedule for the policy on the Migration Schedule tab.

• Decide when “cutover” will occur, or when you will stop sharing the source and preventing user connections to the source and start redirecting users to the file data in the new location. You can configure Phased Migration policies in a variety of ways to support a variety of cutover scenarios. For example, if you are migrating 100 shares, you can decide to cutover 20 shares a weekend until the cutover is complete, or you could decide that you want to cutover all 100 shares in one weekend. You can use the Cutover Estimation tab in the Control Panel view to estimate when your policies will be completed and when to best begin the cutover process. For more information, see “Planning for storage resource cutover” on page 265.

• Do not enable real-time virus scanning on file storage resources because migration throughput can be severely reduced.

• When you perform full backups during a migration operation, backups can change archive attribute settings and trigger massive differences between source and destination. However, using StorageX allows you to help mitigate this problem, because Phased Migration policies allow you to specify how you want to set attributes of destination files. You can set attributes of destination files on the CIFS Attribute Replication tab for a Phased Migration policy.

• Do not use differential replication on a LAN. When operating on a high-speed network, the computational cost of calculating the file differences is more expensive in terms of time than simply copying the entire file from source to destination. You can specify differential replication settings on the Differential Replication tab for a Phased Migration policy.

• When configuring replication options, consider carefully how much event detail you need. Gathering event details about all files replicated can negatively impact performance. As a compromise between performance and the need for detailed information on fies replicated, gather information only when an error is encountered. You can specify the event details you want to gather when a policy runs on the General Options tab for a Phased Migration policy.

• By default, StorageX copies the security descriptor (CIFS) or mode (NFS) of a file every time a file is copied. However, StorageX provides additional options for controlling how file security or permissions are copied during data migration. You can specify how you want StorageX to copy or set security descriptors or modes on the CIFS Security Replication or NFS Security Replication tabs for a Phased Migration policy or policy template. For more information, see “Configuring replication options for Phased Migration policies” on page 279.

• When configuring Phased Migration policies or Archival Migration policies, you should not configure overlapping source and destination directory hierarchies. This can result in unintended duplication of files and can interfere with StorageX replication.

• Exclusive locks on files on source or destination prevent StorageX from accessing those files for transfer. Find out who or what program is locking the files, and make the files available to StorageX.

• You can migrate NFS file data from one NFS file storage resource to another, and you can migrate CIFS file data from one CIFS file storage resource to another. However, you cannot migrate NFS file data to CIFS file storage resources or CIFS file data to NFS file storage resources.

• When the StorageX server shuts down, the Phased Migration policy and the migration tasks running on the server are canceled. StorageX also tries to cancel replication jobs on the universal data engine. The state of the Phased Migration policy and the migration task are persisted. If the StorageX server is shut down gracefully, when the StorageX server restarts, the Phased Migration policy starts again where it left off.

240 StorageX Administrator’s Guide

Page 259: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Data Movement policy planning considerations 5

CIFS-specific data transfer planning considerationsStorageX supports identifying migration candidates using Archival Migration policies and moving file data in CIFS shared folders using Phased Migration policies.

Ensure you review the following CIFS-specific data transfer planning considerations before using StorageX to migrate file data using the CIFS protocol:

NOTEAlso ensure you review the more general planning considerations for migrating data. For more information, see “General data transfer planning considerations” on page 239

• The account used by the StorageX server service or a StorageX universal data engine must have the following permissions in order to transfer CIFS data:

• SeBackupPrivilege (Back up files and directories) - required to open source directories/files with backup semantics.

• SeRestorePrivilege (Restore files and directories) - required to open destination directories/files with backup semantics.

• SeSecurityPrivilege (Manage auditing and security log) - required to access SACLs (System Access Control Lists)

• SeTakeOwnershipPrivilege (Take ownership of files or other objects) - required to delete directories/files.

• If you specify an entire source file storage resource as your source in a Phased Migration policy and then you specify that you want to migrate all CIFS shared folders, when you create the Phased Migration policy using the New Phased Migration Policy Wizard, the New Phased Migration Policy Wizard will determine if there are existing CIFS shared folders on the destination and clone the shared folders, including the share settings, if the share does not already exist on the destination. However, StorageX does not clone share security settings for local users or groups from the source to the destination. StorageX clones only security settings for local built-in accounts on the source to the destination, such as the local Administrator account. StorageX does not clone security settings for other local users or groups.

When the Phased Migration policy runs, StorageX creates the directory structure based on the destination path specified in the policy and migrates file data to the destination.

• If you are using StorageX to manage OneFS file storage resources, to ensure there are no errors during file migration, the StorageX server service account or Windows data engine service account must have Run as Root permission set on all CIFS shares that are destinations in Phased Migration policies. If the StorageX server service account or Windows data engine service account does not have Run as Root permissions on the destination share, you will see access denied errors in the policy manifest when the Phased Migration policy runs, and StorageX will not be able to migrate the data.

• If your source is a compressed NTFS file system and your destination is a VNX OE for File file system, the VNX OE for File file system must have deduplication enabled and set to Deep. For more information, see the EMC VNX Deduplication and Compression white paper, available at https://www.emc.com/collateral/hardware/white-papers/h8198-vnx-deduplication-compression-wp.pdf.

• When transferring data between an NTFS source and destination, you should consider inherited permissions on the destination. If the source and destination are inheriting different permission settings from their parents, the result will be different file permissions between the source and destination.

StorageX Administrator’s Guide 241

Page 260: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Data Movement policy planning considerations5

Before you migrate file data using the CIFS protocol, it is important that you understand transfer results when different file systems that use the CIFS protocol, such as NTFS and FAT, are involved. Some file attribute information, such as security attributes, may be lost when copying or moving files from one file system to another because of the inherent differences between the file systems. The following table displays transfer results between different file systems.

ATTENTIONYou can migrate file data from one file storage resource that uses the NFS protocol to another file storage resource that uses the NFS protocol. You can also migrate file data from one file storage resource that uses the CIFS protocol to another files storage resource that uses the CIFS protocol. However, you cannot migrate NFS file data to CIFS file storage resources or CIFS file data to NFS file storage resources.

How StorageX manages data access in CIFS environments with DFS namespacesIn a CIFS environment, you can configure a DFS namespace. Once you configure the DFS namespace, when client computers access a DFS link in the DFS namespace, the DFS server redirects the client computers to the DFS link target where client computers can access data. For more information about DFS namespaces, see “Understanding DFS namespaces” on page 161.

TABLE 22 Transfer results between differing file systems

Source Destination

NTFS FAT FAT32

NTFS Attributes are maintainedCopying reparse points or NTFS encrypted files are not supported.

Some attributes are lost• NTFS stores access

times in UTC, while FAT stores access time in LocalTime. StorageX does not adjust between UTC and LocalTime.

• FAT also maintains a very limited set of attributes relative to the set maintained by NTFS. When files are transferred to a FAT file system from an NTFS file system, their access times, extended attributes, indexing attributes, and alternate streams (including security) are lost when the files are written to the FAT destination.

Some attributes are lost• NTFS stores access

times in UTC, while FAT stores access time in LocalTime. StorageX does not adjust between UTC and LocalTime.

• FAT also maintains a very limited set of attributes relative to the set maintained by NTFS. When files are transferred to a FAT file system from an NTFS file system, their access times, extended attributes, indexing attributes, and alternate streams (including security) are lost when the files are written to the FAT destination.

FAT Attributes are maintained Attributes are maintained Attributes are maintained

FAT32 Attributes are maintained Some attributes are lost Attributes are maintained.

242 StorageX Administrator’s Guide

Page 261: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Data Movement policy planning considerations 5

StorageX supports identifying migration candidates using Archival Migration policies and moving file data stored in CIFS shared folders using Phased Migration policies. StorageX can also automatically update DFS links that target file data in shared folders managed by the DFS namespace in the Final Phase of a Phased Migration policy as long as the source path and the DFS link target paths match.

If you do want StorageX to update DFS links that target the source to now target the new destination, you can specify how you want StorageX to update DFS links by selecting the Update automounts or update DFS namespaces using the following method check box on the Final Phase tab of a Phased Migration policy, and then specifying how you want StorageX to update the links. You can specify how you want StorageX to update DFS links that target the source by selecting one of the following options:

• by retargeting links - StorageX replaces the source as a target of a DFS link with the destination.

• by adding online link targets - StorageX adds the destination as an online target of a DFS link.

• by adding offline link targets - StorageX adds the destination as an offline target of a DFS link.

• by removing the link targets - StorageX deletes the DFS link target. If the DFS link has only one link target, when StorageX deletes the DFS link target, StorageX also deletes the DFS link.

For more information about using StorageX with DFS namespaces, see “Creating and Managing DFS Namespaces” on page 159, For more information about configuring options on the Final Phase tab of Phased Migration policy, including options for specifying whether you want StorageX to update DFS namespaces as a part of the Final Phase, see “Specifying migration options for Phased Migration policies” on page 280.

NFS-specific data transfer planning considerationsStorageX supports identifying migration candidates using Archival Migration policies and moving file data in NFS exports using Phased Migration policies.

Ensure you review the following NFS-specific data transfer planning considerations before using StorageX to migrate file data using the NFS protocol.

NOTEAlso ensure you review the more general planning considerations for migrating data. For more information, see “General data transfer planning considerations” on page 239

• StorageX requires Version 3 of the NFS protocol in order to use Phased Migration and Archival Migration policies.

• Copying files from NFS sources is typically performed using the StorageX Linux data engine. You can, however, also use the universal data engine installed on the StorageX server computer by default to migrate data.

StorageX Administrator’s Guide 243

Page 262: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Data Movement policy planning considerations5

You can install a Linux data engine on the source or destination file storage resource, you can specify a Linux data engine proxy computer, or you can use the universal data engine installed by default on the StorageX server computer to transfer data between sources and destinations using the NFS protocol. For more information about Linux data engines and specifying universal data engine proxy computers for file storage resources, see “Understanding StorageX universal data engines” on page 9 and “Specifying default universal data engine proxy computers” on page 127.

• The Linux data engine must be installed using an account with root permissions. NFS exports on file storage resources must also have root squash turned off. If root squash is turned on, the StorageX server service account will not have the permissions it needs to access and copy file data from sources to destinations.

• The source and destination file storage resources must be configured to allow the IP address of the Linux data engine access to exports.

• Exports on both source and destination file storage resources must be configured to allow root access.

• The source and destination must be NFS paths, such as <hostname>:/filepath

• If the export on the destination already exists, the source UID and GID permissions are copied to the destination.

• If you specify an entire source file storage resource as your source in a Phased Migration policy and then you specify that you want to migrate all NFS exports, when you create the Phased Migration policy using the New Phased Migration Policy Wizard, the New Phased Migration Policy Wizard will determine if there are existing NFS exports on the destination that correspond to the NFS exports on the source.

If there are existing NFS exports on the destination that correspond to the existing NFS exports on the source, the Phased Migration policy maps the existing NFS exports on the source to the existing NFS exports on the destination.

For example, assume you have an NFS export with the following path on the source:

Source:/Finance/2013/Q1/JanuaryNow assume that you want to migrate the file data in the January directory on the source to the following path on the destination:

Destination:/2013/Q1/JanuaryAn export with the following path already exists on the destination:

Destination:/2013When you create the new Phased Migration policy, the Phased Migration policy does not create any new exports on the destination file storage resource, because an export already exists on the destination. When the Phased Migration policy runs, StorageX mounts the Destination:/2013 directory, creates the Q1 directory under the /2013 directory, creates the January directory under /2013/Q1, and then the Phased Migration policy copies the file data from the source to the destination.

If there are not existing NFS exports on the destination that correspond to the existing NFS exports on the source, when you create the new Phased Migration policy, the Phased Migration policy clones the NFS exports from the source to the destination, including the export settings.

For example, assume you have an NFS export with the following path on the source:

Source:/Finance/2013/Q1/JanuaryThere is not a an export with a corresponding path on the destination.

244 StorageX Administrator’s Guide

Page 263: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Data Movement policy planning considerations 5

When you create the new Phased Migration policy, the Phased Migration policy creates the following export path on the destination:

Destination:/Finance/2013/Q1/JanuaryWhen the Phased Migration policy runs, StorageX mounts the Destination:/Finance/2013/Q1/January path on the destination and copies the file data to the destination.

• If you are using automount map files for NFS and you want StorageX to update the automount map files in the Final Phase of the migration, you must configure SSH shell credentials for StorageX to use before StorageX can communicate with the source and destination file storage resources and communicate with the computers that host the automount map files and update the automount map files. For more information, see the following topics:

• “How StorageX manages data access in NFS environments with automount map files” on page 245

• “Configuring StorageX to Use SSH Shell Credentials” on page 433

• “Configuring default SSH shell credentials” on page 79

• “Configuring SSH shell credentials for specific file storage resources” on page 107

• “How StorageX manages data access in NFS environments with automount map files” on page 245

How StorageX manages data access in NFS environments with automount map filesStorageX supports identifying NFS exports that are migration candidates using Archival Migration policies and moving file data in NFS exports using Phased Migration policies.

If you use automount map files in your NFS environment, you can specify that you want StorageX to update your automount map files in the Final Phase of the Phased Migration policy.

If you use StorageX to migrate file data referenced in an automount map files, when you configure a Phased Migration policy, you have the option of specifying whether you want StorageX to update automount map files by selecting the Update automounts or update DFS namespaces using the following method check box on the Final Phase tab for a Phased Migration policy and then specifying the path to the automount map file you want to update during the Final Phase of the migration on the Automounts tab.

When you select this option, StorageX updates the automount map files you specified on the Automounts tab in the Final Phase of the Migration. StorageX updates the automount map entries that referenced the source information to now reference the new destination location.

For example, assume that you want to migrate file data from the following source to the following destination:

Source: SourceFileStorageResource.domain.com:/export/homeDestination: DestinationFileStorageResource.domain.com:/export/new/homeThe automount map file referenced on the Automounts tab contains the following entry that references the source:

/home SourceFileStorageResource:/export/home/myHome

StorageX Administrator’s Guide 245

Page 264: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Data Movement policy planning considerations5

When StorageX updates the automount map file in the final phase, StorageX updates the entry in the automount map file as follows:

/home DestinationFileStorageResource.domain.com:/export/new/home/myHomeIf you are using automount map files for NFS and you want StorageX to update automount map files stored on NFS clients in the Final Phase of the migration, you must configure SSH shell credentials for StorageX to use before StorageX can communicate with the source and destination file storage resources and communicate with the computers that host the automount map files and update the automount map files. For more information, see the following topics:

• “Configuring StorageX to Use SSH Shell Credentials” on page 433

• “Configuring default SSH shell credentials” on page 79

• “Configuring SSH shell credentials for specific file storage resources” on page 107

The following table illustrates the similarities between the DFS namespace model and the automount map file model.

NDMP-specific data transfer requirements and configurationStorageX supports moving data between certain types of resources using the NDMP protocol, outside of the normal StorageX migration engine.

Ensure you review the following NDMP-specific data transfer planning considerations before using StorageX to migrate file data using the NDMP protocol. In addition, review the requirements specified in the OneFS Migration Tools Guide provided by EMC, available at https://community.emc.com/docs/DOC-36563, prior to using the isi_vol_copy utility for replication.

NOTEAlso ensure you review the more general planning considerations for migrating data. For more information, see “General data transfer planning considerations” on page 239

• StorageX requires Version 4 of the NDMP protocol in order to use Phased Migration policies.

• StorageX only supports using the NDMP protocol for Phased Migration policies. You cannot configure StorageX to use the NDMP protocol for Archival or Disaster Recovery policies or for Migration Projects.

ATTENTIONStorageX currently only supports using NDMP for migrating data from NetApp Data ONTAP 8 7-Mode Filer or NetApp Data ONTAP 7 Filers to EMC Isilon resources, using the isi_vol_copy utility. StorageX does not support using NDMP to migrate data to or from NetApp Data ONTAP vFilers.

TABLE 23 DFS namespace and automount map file comparison

DFS Namespace Automount map file

DFS link Entry in automount map

DFS link target NFS export list of a mapping in automount map

CIFS shared folder NFS export

246 StorageX Administrator’s Guide

Page 265: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Data Movement policy planning considerations 5

• When StorageX uses the NDMP protocol to copy files from one resource to another, the application uses an Isilon native replication tool (isi_vol_copy), rather than the StorageX universal data engine.

• You cannot use the NDMP protocol to migrate data to OneFS resources using User Space NFS (uNFS).

• You cannot use the NDMP protocol to migrate data to or from EMC Isilon access zones.

• Before starting migration using NDMP, the source resource must have NDMP set up and turned on.

• The target resource must allow access by StorageX to initiate the migration process. StorageX uses SSH to initiate the data transfer.

• You must configure the ports you want NDMP replication to use on both the source resource and the destination resource.

• The source resource and the destination resource cannot use the same specific port for NDMP replication.

• If you want NDMP replication to use a specific port on the destination EMC Isilon resource, ensure you first configure that port on the resource itself, using the OneFS user interface. Then, in the Properties for the EMC Isilon resource, click NDMP Options, select Use this specific port, and specify the port you configured the resource to use through OneFS.

• If you select the Use the default port to connect to the NDMP service option on the source resource, ensure you do not configure the destination resource to use the port 0. Selecting 0 in the Use this specific port field forces isi_vol_copy to use the default NDMP port, which is already in use on the source resource. Specify a different port both in the Use this specific port field and in OneFS or select Use any port for replication, instead.

• If you want StorageX to be able to automatically retrieve the password associated with the target resource, you must configure SSH on the source resource. For more information, see the following topics:

• “Configuring StorageX to Use SSH Shell Credentials” on page 433

• “Configuring default SSH shell credentials” on page 79

• “Configuring SSH shell credentials for specific file storage resources” on page 107

To use NDMP to migrate data, you must configure both the source NetApp resource and target Isilon resource, create a Phased Migration policy to migrate from the source to the target, and then modify the policy to enable StorageX to use the NDMP protocol.

ATTENTIONIf you configure a Phased Migration policy to use the NDMP protocol, but either the source or target resource are not correctly configured, when you run the policy, StorageX will revert to the default universal data engine for migration.

For more information about creating Phased Migration policies and configuring Phased Migration policies to use NDMP, see “Creating new Phased Migration policies” on page 251 and “Configuring Phased Migration policies to use native replication” on page 258.

StorageX Administrator’s Guide 247

Page 266: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing templates5

Distributing file data transfer workloads using universal data engine groups You can use universal data engines and universal data engine groups with Phased Migration policies to specify which universal data engine or universal data engine group you want to perform file data transfer operations. Use universal data engine groups if you want to distribute file data transfer workloads or increase the performance and availability of universal data engines when transferring data.

For more information about universal data engines and creating and managing universal data engine groups, see “Understanding StorageX universal data engines” on page 9 and “Creating and managing universal data engine groups” on page 130. For more information about specifying universal data engine groups for creating Phased Migration policies, see “Assigning universal data engines or universal data engine groups to Phased Migration policies” on page 288.

Distributing file data transfer workloads using specific cluster nodes or groupsYou can also configure StorageX to only use one or more specific cluster nodes, on either an EMC Isilon or NetApp clustered file storage resource, as sources or destinations for Phased Migration policies. In Data ONTAP Cluster Mode environments, you can specify one or more nodes, and in OneFS environments, you can specify one or more nodes or EMC Isilon SmartConnect groups.

Specifying a particular node or group of nodes on a clustered resource can significantly improve migration speed and allow you to shift data transfer workloads onto one or more nodes that you designate for migration purposes.

For more information about configuring cluster replication options, see “Configuring replication options for clustered file storage resources” on page 115.

Creating and managing templatesStorageX provides several default Phased Migration and Archival Migration templates that you can use out of the box. You can modify or delete these templates, copy them and then make changes, or create new templates to meet your requirements. Although Phased Migration and Archival Migration templates include different settings, procedures for managing them are essentially the same for both types. For more information about templates, see “Understanding Phased Migration and Archival Migration templates” on page 229.

Creating new templatesYou can create new Phased Migration or Archival Migration templates to meet the requirements of your organization.

To create a new template

1. In the StorageX Console, click the Data Movement tab.

2. If you want to create a new Phased Migration template, in the left tree pane, right-click Data Movement and then click New > Phased Migration Template.

248 StorageX Administrator’s Guide

Page 267: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating and managing templates 5

3. If you want to create a new Archival Migration template, in the tree pane, right-click Data Movement and click New > Archival Migration Template.

4. In the Name and Description dialog box, type a unique name and description for the template.

5. Click each tab in the left pane to display related settings in the right pane and specify settings as appropriate. For more information about each setting, click the Help button on the dialog box.

6. Click OK.

Copying an existing templateYou can create new Phased Migration or Archival Migration templates by copying existing templates and then modifying them as needed.

To copy an existing template

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and right-click the template you want to copy and then click Copy.

3. In the left tree pane, right-click Data Movement, and then click paste.

StorageX paste the copy of the template into the left tree pane and displays the copy in alphabetical order in the list of templates with the default name Copy of TemplateName, where TemplateName is the name of the original template.

4. Rename the template copy by completing the following steps:

a. Right-click the template copy and click Properties.

b. In the Name and Description dialog box, type a new name and description for the template.

c. Click each tab in the left pane to display settings in the right pane and modify settings as needed. For more information about each setting, click the Help button on the dialog box.

d. Click OK.

Viewing and modifying template propertiesYou can view the properties of a Phased Migration or Archival Migration template before using the template in a policy. You can also modify template properties as needed. When you modify template properties, the modifications affect any policies that inherit settings from that template, unless you override the template settings in the policy itself.

To view and modify template properties

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and right-click a template, and then click Properties.

3. Click the tabs in the left pane to view and modify the settings in the right pane. For more information about each setting, click the Help button on the dialog box.

4. Click OK.

StorageX Administrator’s Guide 249

Page 268: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Phased Migration policies5

Renaming templatesYou can rename Phased Migration or Archival Migration templates any time. For example, you might need to rename your templates to conform to new corporate standards. Renaming a template does not affect it in any other way.

To rename a template

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and right-click a template, and then click Rename.

3. Type a new name and press the Enter key.

Deleting templatesYou can delete Phased Migration or Archival Migration templates that you are no longer using.

ATTENTIONUse caution when deleting templates. If you have created policies under a template, deleting the template also deletes the policies associated with that template.

To delete a template

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and right-click the template you want to delete and click Delete.

3. Click Yes to confirm you want to delete the template.

Creating Phased Migration policiesCreate Phased Migration policies to migrate file data from one storage resource to another. You can create new Phased Migration policies using the New Phased Migration Policy Wizard.

StorageX can also automatically generate Phased Migration policies when you execute Migration Project designs or when you run Archival Migration policies that have the Automatically generate Migration policies for migration candidates option selected on the Task Options tab for an Archival Migration policy.

This section explains how to create Phased Migration policies manually.

For more information about generating Phased Migration policies when executing Migration Project designs, see “Understanding Migration Projects” on page 321, “Understanding Migration Project Phased Migration policies” on page 328, and “Executing Migration Project designs” on page 363. For more information about generating Phased Migration policies when running Archival Migration policies, see “Understanding Archival Migration policies” on page 233.

The first time you create a Phased Migration policy, use the New Phased Migration Policy Wizard. Once you have created a Phased Migration policy, you can either continue to use the wizard to create new policies, or you can copy existing policies and modify them as needed. For more information, see the following topics:

• “Creating new Phased Migration policies” on page 251

• “Copying existing Phased Migration policies” on page 257

250 StorageX Administrator’s Guide

Page 269: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Phased Migration policies 5

• “Creating Phased Migration policy import files” on page 258

• “Configuring Phased Migration policies to use native replication” on page 258

Creating new Phased Migration policiesUse the New Phased Migration Policy Wizard to create Phased Migration policies.

When you create a new Phased Migration policy, you can specify that you want to migrate file data from the following sources to the following destinations:

Each Phased Migration policy has one source and destination pair, and both the source and destination must be specified using physical paths.

In StorageX, a physical path is a path directly to the file storage resource. For example, a physical path is the UNC path \\FileStorageResource\ShareName, where FileStorageResource is the actual name of the file storage resource. If the file storage resource is a virtual file storage resource, or if the file storage resource has its own virtualization layer, the physical path is the UNC path to the resource.

If you specify a single CIFS shared folder, folder under a CIFS shared folder, NFS export, or folder under an NFS export as your source, the destination CIFS shared folder or NFS export must already exist on the destination file storage resource. If the CIFS shared folder or NFS export does not already exist on the destination, you can create it in the Storage Resources view. For more information, see “Creating CIFS shared folders” on page 140 and “Creating NFS exports” on page 145.

If you specify an entire file storage resource as your source and destination, StorageX can create destinations on the destination file storage resource if the destination does not already exist. However, the process StorageX uses to create destinations varies based on whether you are using the CIFS or NFS protocol and the destination type. For more information, see “CIFS-specific data transfer planning considerations” on page 241 and “NFS-specific data transfer planning considerations” on page 243. In addition, the file storage resource that is the destination where you want to create CIFS shared folders or NFS exports must be added to the My Resources folder in the Storage Resources view. If you have not added the destination file storage resource to the My Resources folder in the Storage Resources view, StorageX will not be able to create CIFS shared folders or NFS exports on the destination. For more information about adding a file storage resource to My Resources, see “Understanding the Storage Resources view” on page 67 and “Adding storage resources” on page 80.

NOTEStorageX does not support using Phased Migration policies to migrate from nested NFS exports. If you select an export in the Select Items to Migrate window in the New Phased Migration Policy Wizard, then select a second export that is nested within the first export, StorageX will not include that second nested export on the subsequent Create Destination Exports window.

TABLE 24 Phased Migration policy sources and destinations

Source Destination

A CIFS shared folder or folder under a CIFS shared folder

A CIFS shared folder or folder under a CIFS shared folder

An NFS export or folder under an NFS export An NFS export or folder under an NFS export

StorageX Administrator’s Guide 251

Page 270: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Phased Migration policies5

If you use a DFS namespace or automount map files, you can specify as a migration option that you want StorageX to automatically update DFS namespaces or automount map files to reference file data stored in a new location in the Final Phase of the policy run. For more information, see “How StorageX manages data access in CIFS environments with DFS namespaces” on page 242 and “How StorageX manages data access in NFS environments with automount map files” on page 245.

StorageX currently only supports specifying VNXe file storage resources as sources and destinations in Phased Migration policies under the following conditions:

• The Phased Migration policies that include VNXe file storage resources as sources or destinations are created using the New Phased Migration Policy Wizard in the Data Movement view.

• You specify the full UNC path to the VNXe sources and destinations, including the share and any subfolders as appropriate.

StorageX does not support VNXe file storage resources as sources or destinations in Phased Migration policies created by Migration Projects in the Migration Projects view. You also cannot add VNXe file storage resources to the My Resources folder in the Storage Resources view and have StorageX manage the resource.

Once you have created a Phased Migration policy, you can either use the wizard to create additional Phased Migration policies or you can copy an existing Phased Migration policy and then modify it as needed. For more information about copying existing Phased Migration policies, see “Copying existing Phased Migration policies” on page 257.

To create a new Phased Migration policy

1. In the StorageX Console, click the Data Movement tab.

2. In the tree pane, right-click the folder where you want to create the new policy and select Phased Migration Policy.

3. Review the welcome message, and then click Next.

4. If you want to migrate data from a specific CIFS shared folder or NFS export to a destination shared folder or export, complete the following steps:

a. Select Migrate source and destination shared folders or exports.

b. In the Source field, type the UNC path for the shared folder or export with the file data you want to migrate, or click Browse to browse to and select the source path.

If you want the Phased Migration policy to update automount map files in the Final Phase of the policy, ensure that the path you specify as your source in this field exactly matches the string you use to specify the source in the automount map file. If the string used to specify the source in the Phased Migration policy does not exactly match the string used in the automount map file, the Phased Migration policy will not be able to update the automount map file correctly in the Final Phase of the policy.

For example, assume that you specify the source in the Phased Migration policy as FullyQualifiedDomainName:/path. However, assume that the source in the automount map file is IPAddress:/path. In this scenario, the Phased Migration policy will not be able to update the automount map file correctly. However, if you specify the source in the Phased Migration policy as IPAddress:/path and the source in the automount map file is IPAddress:/path, the Phased Migration policy will be able to update the automount map file correctly in the Final Phase.

252 StorageX Administrator’s Guide

Page 271: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Phased Migration policies 5

For more information about how StorageX can manage data access in NFS environments with automount map files, see “How StorageX manages data access in NFS environments with automount map files” on page 245.

c. In the Destination field, type the UNC path for the shared folder or export to which you want the data to be migrated, or click Browse to browse to and select the path.

If you specified a CIFS shared folder or NFS export on a file storage resource in the Source field, you must specify an existing CIFS shared folder or NFS export on the destination file storage resource. The CIFS shared folder or NFS export you specify must already exist on the destination. If the CIFS shared folder or NFS export does not already exist on the destination, you can create it in the Storage Resources view. For more information, see “Creating CIFS shared folders” on page 140 and “Creating NFS exports” on page 145.

5. If you want to migrate data from multiple CIFS shared folders or NFS exports located on a specific storage resource to a destination storage resource, complete the following steps:

a. Select Discover shares and exports to migrate from source resource.

b. In the Source field, type the UNC path for the storage resource with the file data you want to migrate, or click Browse to browse to and select the source path.

If you want the Phased Migration policy to update automount map files in the Final Phase of the policy, ensure that the path you specify as your source in this field exactly matches the string you use to specify the source in the automount map file. If the string used to specify the source in the Phased Migration policy does not exactly match the string used in the automount map file, the Phased Migration policy will not be able to update the automount map file correctly in the Final Phase of the policy.

For example, assume that you specify the source in the Phased Migration policy as FullyQualifiedDomainName:/path. However, assume that the source in the automount map file is IPAddress:/path. In this scenario, the Phased Migration policy will not be able to update the automount map file correctly. However, if you specify the source in the Phased Migration policy as IPAddress:/path and the source in the automount map file is IPAddress:/path, the Phased Migration policy will be able to update the automount map file correctly in the Final Phase.

For more information about how StorageX can manage data access in NFS environments with automount map files, see “How StorageX manages data access in NFS environments with automount map files” on page 245.

c. In the Destination field, type the UNC path for the storage resource to which you want the data to be migrated, or click Browse to browse to and select the path.

d. If you want to migrate only the CIFS shared folders on the file storage resource that are referenced by a DFS namespace, click Only migrate shares referenced by a DFS namespace.

e. If you want to migrate specific CIFS shared folders on the file storage resource, click Migrate selected shares. If you also want to include hidden shares, select the Include hidden shares check box.

f. If you want to migrate specific NFS exports on the file storage resource, click Migrate selected exports.

For more information about each option, click the Help button on the dialog box.

6. If you want to import a list of source and destination shared folders, exports, or resources to migrate, complete the following steps:

StorageX Administrator’s Guide 253

Page 272: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Phased Migration policies5

a. Select Import source and destination pairs from file.

b. In the Import File field, type the UNC path for the Phased Migration policy import file, or click Browse to browse to and select the import file. For more information about creating a Phased Migration policy import file, see “Creating Phased Migration policy import files” on page 258.

7. Click Next.

8. On the Policy Name and Description dialog box, specify the unique name you want to use to identify the policy and a word or phrase that describes the policy.

9. Click Next.

10. On the Specify Template dialog box, select a template from the list of available templates. The policy inherits base settings from the template, but you can make changes later if necessary. For more information, see “Modifying Phased Migration policy properties” on page 279.

11. Click Next.

12. If you specified a file storage resource on the Specify Migration Type and Resources dialog box, complete the following steps:

a. In the Select Items to Migrate dialog box, ensure the check box is selected for each source you want to migrate, and cleared for each source you do not want to migrate.

b. If you want to change a destination path, select the destination path and then click Edit Path or type directly in the Destination Path field. You can edit the destination path for multiple sources in one operation by multi-selecting the sources with the destination path you want to change, and then clicking Edit Path.

c. If you want StorageX to warn you if the destination already contains files or folders, select the Warn if destination already contains files or folders check box.

d. Click Next.

13. If the CIFS shared folder or NFS export of the destination path for a source path does not exist on the destination file storage resource, the Create Destination Shares or Create Destination Exports dialog box displays.

This dialog box lists destination CIFS shared folders or NFS exports that currently do not exist on the destination file storage resource and must be created on the destination file storage resource before you can use the policy to migrate file data. StorageX displays a red x symbol in front of the suggested local path name for each destination CIFS shared folder or NFS export that needs to be created.

Review the list of destination CIFS shared folders or NFS exports which need to be created under Destination Share or Destination Export, as well as the local path displayed for each destination share in the Local Path field.

The Destination Shares Status or Destination Exports Status field below the list of destination CIFS shared folders or NFS exports displays the total number of destination CIFS shared folders or NFS exports that need to be created. For example, if you specified that you want to create 20 CIFS shared folders on the destination file storage resource, but only 16 of the 20 shared folders on the destination file storage resource currently exist, 16 of 20 Destination Items Verified displays.

254 StorageX Administrator’s Guide

Page 273: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Phased Migration policies 5

If you want to create a destination CIFS shared folder or NFS export on the destination file storage resource using the displayed local path, select the local path, and then click Create Destination Share or Create Destination Export as appropriate. You can also create multiple destination CIFS shared folders or NFS exports in one operation by multi-selecting all of the CIFS shared folders or NFS exports you want to create, and then clicking Create Destination Share or Create Destination Export as appropriate.

NOTEIf you have not added the destination file storage resource to the My Resources folder in the Storage Resources view, StorageX will not be able to create CIFS shared folders or NFS exports on the destination. The file storage resource that is the destination where you want to create CIFS shared folders or NFS exports must be added to the My Resources folder in the Storage Resources view.

If you want to change the local path before you create the destination CIFS shared folder or NFS export, select the local path and then click Edit Path or type directly in the Local Path field to edit the local path. Then click Create Destination Share or Create Destination Export as appropriate. You can edit the suggested local path for multiple CIFS shared folders or NFS exports in one operation by multi-selecting the CIFS shares or NFS exports with the suggested local path you want to change, and then clicking Edit Path.

StorageX immediately creates destination CIFS shared folders or NFS exports on the destination file storage resource when you click Create Destination Share or Create Destination Export. When finished, click Next.

14. If a source or destination path in the new policy is the same as a source or destination path in an existing Phased Migration policy, the Duplicate Migration Paths Detected dialog box displays.

Review the information provided that shows the existing Phased Migration policies with the same source or destination path as the new Phased Migration policy you are creating. When you have finished your review and you are ready to continue, click Next.

In particular, pay special attention to any existing Phased Migration policies that have the same destination as the new Phased Migration policy you are creating. Typically it is not a good idea to have multiple policies with the same destination. When you create Phased Migration policies with different sources but the same destination, files can be overwritten and data can be lost.

For example, assume you have a file called 2013 Financial Data.xls stored in the 2013 Financial Data folder on FileStorageResource-01. You create a Phased Migration policy to migrate the 2013 Financial Data folder to a folder called 2013 Financial Data on FileStorageResource-02. Next assume you have a file called 2013 Financial Data.xls stored in the 2013 Financial Data folder on FileStorageResource-03, and you create a second Phased Migration policy to migrate the 2013 Financial Data folder on this resource to the same destination, the 2013 Financial Data folder on FileStorageResource-02. When the first policy runs, the 2013 Financial Data.xls file is migrated from FileStorageResource-01 to FileStorageResource-02. When the second policy runs, the 2013 Financial Data.xls file is migrated from FileStorageResource-03 to FileStorageResource-02, and it overwrites the previous version of the file migrated previously from FileStorageResource-01.

StorageX Administrator’s Guide 255

Page 274: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Phased Migration policies5

Also ensure that you carefully review policies that have the same source and destination path of the Phased Migration policy you are creating if you have selected the Delete orphaned files and folders on the destination option on the General Options tab on any of the policies with duplicate paths. When you create Phased Migration policies with different sources but the same destination and the Delete orphaned files and folders on the destination option is selected, files can be deleted and data can be lost.

For example, assume once again you have a file called 2013 Financial Data.xls stored in the 2013 Financial Data folder on FileStorageResource-01. You create a Phased Migration policy to migrate the 2013 Financial Data folder to a folder called 2013 Financial Data on FileStorageResource-02. Next assume you have a folder called 2013 Financial Data folder on FileStorageResource-03. This folder does not contain the 2013 Financial Data.xls file. You then create a second policy to migrate the 2013 Financial Data folder on this resource to the same destination, the 2013 Financial Data folder on FileStorageResource-02. When the first policy runs, the 2013 Financial Data.xls file is migrated from FileStorageResource-01 to FileStorageResource-02. When the second policy runs, the policy detects that the 2013 Financial Data.xls file is on FileStorageResource-02, since it was migrated from migrated from FileStorageResource-01. However, because the second policy has the Delete orphaned files and folders on the destination option selected, when the second policy detects the 2013 Financial Data.xls file on the destination but not on the source, the second policy deletes the 2013 Financial Data.xls file on the destination.

15. If file data is already stored in a specified destination, the Verify Destination Paths Are Empty dialog box displays, and the destination path that already contains files or folders displays with a warning symbol.

When you create a Phased Migration policy with a destination that already contains file data, files can be overwritten and data can be lost. Verify whether it is acceptable to migrate file data into a destination that already contains file data. Clear the check box for items you do not want to migrate, or edit the destination path by typing directly into the Destination Path field as needed, and then click Next.

16. In the New Migration Policy Summary dialog box, verify the settings you specified for the new Phased Migration policy, and then click Finish.

StorageX creates one or more new Phased Migration policies, one for each source and destination pair you specified in the New Phased Migration Policy Wizard. For example, if the source file storage resource had 20 sources that you wanted to migrate to 20 destinations on a destination file storage resource, StorageX creates 20 new Phased Migration policies, one policy for each source and destination pairing.

New Phased Migration policies display in the left tree pane on the Data Movement tab under the Phased Migration template used when creating the new Phased Migration policy. If you created the Phased Migration policy by right-clicking the My Policies folder and then clicking New > Phased Migration Policy, the new Phased Migration policy displays under both the Phased Migration template used when creating the new Phased Migration policy, as well as under the My Policies folder.

After you create the new Phased Migration policy, verify the replication options and migration options specified for the policy as needed. For more information, see the following topics:

• “Configuring replication options for Phased Migration policies” on page 279.

• “Specifying migration options for Phased Migration policies” on page 280.

After verifying replication and migration options, you can choose to run the policy immediately or you can schedule the policy. For more information, see the following topics:

256 StorageX Administrator’s Guide

Page 275: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Phased Migration policies 5

• “Running Phased Migration policies immediately” on page 262

• “Scheduling Phased Migration policies” on page 263

Copying existing Phased Migration policiesUse the New Phased Migration Policy Wizard to create your first Phased Migration policy, or generate Phased Migration policies by executing Migration Project designs or running Archival Migration policies that have the Automatically generate Migration policies for migration candidates option selected on the Task Options tab for an Archival Migration policy.

Once you have created a Phased Migration policy, you can either use the wizard to create additional policies or you can copy an existing Phased Migration policy and then modify it as needed to create a new Phased Migration policy.

This topic explains how to copy an existing Phased Migration policy.

For more information about using the New Phased Migration Policy Wizard to create Phased Migration policies, see “Creating new Phased Migration policies” on page 251. For more information about generating Phased Migration policies when executing Migration Project designs, see “Executing Migration Project designs” on page 363. For more information about generating Phased Migration policies when running Archival Migration policies, see “Understanding Archival Migration policies” on page 233.

To copy an existing Phased Migration policy

1. If the you created the Phased Migration policy in the Data Movement view or an Archival Migration policy generated the policy, in the StorageX Console, click the Data Movement tab.

2. If StorageX generated the Phased Migration policy when you executed a Migration Project design, in the StorageX Console, click the Migration Projects tab.

3. In the left tree pane, browse to and right-click the Phased Migration policy you want to copy, and then click Copy.

4. Browse to and select a different custom folder or a template, and then click Paste.

NOTEYou cannot copy and paste a policy into the same folder as the original folder.

StorageX displays the new policy in the tree pane with the default name Copy of MigrationPolicyName, where MigrationPolicyName is the name of the original policy.

5. In the left tree pane, right-click the new Phased Migration policy and click Properties.

6. In the Name and Description fields, type a unique name and description for the new Phased Migration policy.

7. In the left pane of the Migration Properties dialog box, click each tab, review the current properties in the right pane, and modify properties as needed.

8. Click OK.

StorageX Administrator’s Guide 257

Page 276: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Phased Migration policies5

Creating Phased Migration policy import filesInstead of creating Phased Migration policies to migrate data between two shares, exports, or resources, you can automatically create Phased Migration policies for up to 50 source and destination shares or exports using a policy import file.

To import Phased Migration policy sources and destinations, create a CSV-format file using the following format for each source/destination pair:

Name,Description,Source,Destination,Destination Local Path (Optional)

Where Name is the name of the new Phased Migration policy, Description is a description for the new policy, Source is the share or export on the source resource, Destination is the share or export on the destination resource, and Destination Local Path is the local path for the shared folder or export on the destination file system. Destination Local Path is only necessary if the share or export does not already exist on the destination resource.

For example:

CIFS Policy1,Migrate CIFS resource,\\server1.domain\shareA,\\server2.domain\shareACIFS Policy2,Migrate Windows server,\\server1.domain\shareB,\\server2.domain\shareB,C:\shares\Folder\shareBNFS Policy1,Migrate NFS resource,server3.domain:/vol/volA,server4.domain:/vol/volA

After you create the policy import file, launch the New Phased Migration Policy Wizard, click the Import source and destination pairs from file option and browse to the import file to create a Phased Migration policy for each source and destination pair.

Configuring Phased Migration policies to use native replicationWhen you create a Phased Migration policy, StorageX uses the universal data engine to migrate data from the source resource to the target resource by default. However, you can also configure StorageX to use a native tool to migrate data from the source to the target.

StorageX currently only supports using the NDMP protocol and the isi_vol_copy tool to migrate data outside of the universal data engine. You can configure StorageX to use NDMP and isi_vol_copy to migrate from a NetApp Data ONTAP 8 7-Mode resource or a NetApp Data ONTAP 7 resource to an EMC Isilon resource. In some environments, replication from NetApp resources to EMC Isilon resources using isi_vol_copy can be significantly faster than replication using the StorageX universal data engine.

To migrate data using native replication, create a Phased Migration policy with a share on the NetApp resource as the source and a share on the EMC Isilon resource as the destination, then configure the new policy to use NDMP instead of the universal data engine.

Before migrating data using NDMP, ensure you review the planning considerations and requirements provided here:

• “General data transfer planning considerations” on page 239

• “NDMP-specific data transfer requirements and configuration” on page 246

We recommend you also review the OneFS Migration Tools Guide provided by EMC, available at https://community.emc.com/docs/DOC-36563, prior to configuring your Phased Migration policies to use isi_vol_copy for replication.

258 StorageX Administrator’s Guide

Page 277: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Phased Migration policies 5

NOTEIf you do not configure both the source and destination resources properly, StorageX may encounter issues.

To configure a Phased Migration policy to use native replication

1. In the StorageX Console, create a new Phased Migration policy with a share on a Data ONTAP resource as the source and a share on an EMC Isilon resource as the destination.

1. In the left tree pane, click the Storage Resources tab.

2. Browse to and right-click the Data ONTAP resource you specified as the source for the Phased Migration policy, and then click Properties.

3. Click the NDMP Options tab.

4. Select Use Network Data Management Protocol for replication, when applicable.

5. Specify the user name and password you want the EMC Isilon resource to use to communicate with the Data ONTAP resource.

6. If you want StorageX to automatically attempt to discover the password for the specified Data ONTAP user account the EMC Isilon resource will use to communicate, click Discover password.

NOTEStorageX can only discover passwords for user accounts on the Data ONTAP resource that have been assigned the login-ndmp capability. NetApp recommends assigning the built-in backup role to a group to which the user account belongs. For more information about the login-ndmp capability, see the article “What NDMP security is” on the NetApp Support site at https://library.netapp.com/ecmdocs/ECMP1368865/html/GUID-CB35AA4C-0904-49D3-B88D-60F4509F8BED.html.

7. If you want to use a specific non-default port to connect to the NDMP service, click Use this specific port and specify the port number.

You must configure the ports you want NDMP replication to use on both the source resource and the destination resource. The source resource and the destination resource cannot use the same specific port for NDMP replication.

8. Click OK when finished.

9. Browse to and right-click the EMC Isilon resource you specified as the destination for the Phased Migration policy, and then click Properties.

10. Click the NDMP Options tab.

11. Select Use Network Data Management Protocol for replication, when applicable.

12. If you want the source resource to use a specific port to connect to the EMC Isilon resource, click Use this port for replication and specify the port number.

If you want NDMP replication to use a specific port on the destination EMC Isilon resource, ensure you first configure that port on the resource itself, using the OneFS user interface. Then, in the Properties for the EMC Isilon resource, click NDMP Options, select Use this specific port, and specify the port you configured the resource to use through OneFS.

StorageX Administrator’s Guide 259

Page 278: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Validating Phased Migration policy settings5

NOTEIf you select the Use the default port to connect to the NDMP service option on the source resource, ensure you do not configure the destination resource to use the port 0. Selecting 0 in the Use this specific port field forces isi_vol_copy to use the default NDMP port, which is already in use on the source resource. Specify a different port both in the Use this specific port field and in OneFS or select Use any port for replication, instead.

13. Click OK.

14. In the left tree pane, click the Data Movement tab.

15. Browse to and right-click the Phased Migration policy you want to configure, and then click Properties.

16. Click the Replication Type tab.

17. Click Use NDMP for Replication Type.

18. Click OK.

In the Summary pane, Replication Method is now Network Data Management Protocol (isi_vol_copy), instead of StorageX Universal Data Engine. The next time the configured Phased Migration policy runs, StorageX will use the NDMP protocol and isi_vol_copy tool for the migration.

ATTENTIONIf you configure a Phased Migration policy to use NDMP and the isi_vol_copy tool and run the policy, StorageX cannot correctly display statistics for the Phased Migration policy run. StorageX uses universal data engines to gather statistical information on policy runs, and using NDMP and isi_vol_copy for migration goes outside of the universal data engine. Therefore, StorageX displays a value of 0 for most statistics in the Policy Status area and in the manifest. The only statistics StorageX can provide for Phased Migration policies using NDMP are Files Copied and Bytes Copied, and those statistics themselves are unreliable and may not be correct. In some situations, StorageX may display a value of 0 when a small number of files or bytes were successfully copied.

Validating Phased Migration policy settingsOnce you create a new Phased Migration policy, you can validate that the settings and resources you specified for the policy will function correctly during a policy run by using the Simulate Replication (No Data Copy) option in the General Settings > Replication Type tab of the policy Properties dialog box.

This option allows you to perform a dry run of a Phased Migration policy without actually replicating any data from the source to the destination. When you run a policy with Simulate Replication selected, StorageX:

• Checks that the selected universal data engine can access both the source and the destination.

• Provides statistics on the data that would be moved during a real policy run, including the number of files, the number of folders, and the overall size in bytes.

• Enables you to see if your filtering options are configured correctly, including the Copy files setting in the policy General Options, any filters in the policy Replication Filters, and any criteria specified in the Differential Replication settings.

260 StorageX Administrator’s Guide

Page 279: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Validating Phased Migration policy settings 5

With the information from the simulated replication run, you can then modify your policy configuration as necessary before disabling the Simulate Replication option and performing the first real replication.

NOTES:

• The Simulate Replication option is only available for Phased Migration policies. You cannot enable this option for Phased Migration templates, Migration Project templates, Disaster Recovery policies, or Replication policies.

• This option requires the StorageX universal data engine. You cannot use the Simulate Replication option when using the NDMP protocol or SnapMirror to migrate data. If you select the Use NDMP for Replication Type option, the Simulate Replication option is automatically disabled.

• StorageX cannot validate access on a file or folder level, because the simulation process does not open the individual files and folders. This option only checks that the universal data engine can access each resource as a whole, both source and destination.

• Because of the above limitation, StorageX cannot determine if files are locked or in use on the source when you enable the Simulate Replication option and run the policy.

• In addition, when you run a simulation, StorageX cannot determine if the destination grants “write” permissions to the universal data engine, if the destination has space available for replication from the source, or if the destination is read-only.

• If you want to run a simulation on a schedule, you can enable the Simulate Replication option and then configure the settings in the Migration Schedule tab of the policy Properties dialog box. Ensure you modify the policy schedule if necessary after the simulation run is complete.

• Running Phased Migration policies with the Simulate Replication option enabled does not count against your license in terms of data migrated, if applicable. However, you must have a valid StorageX license to be able to use this functionality.

• StorageX cannot use Phased Migration policy runs with the Simulate Replication option enabled for estimating the optimum cutover window for the policy.

To enable and perform a simulated replication run for a Phased Migration policy

1. If you created the Phased Migration policy in the Data Movement view or if an Archival Migration policy generated the policy, in the StorageX Console, click the Data Movement tab.

2. If StorageX generated the Phased Migration policy when you executed a Migration Project design, in the StorageX Console, click the Migration Projects tab.

3. In the left tree pane, browse to and right-click the Phased Migration policy you want to validate, then click Properties.

4. Click the General Settings > Replication Type tab.

5. Select Simulate Replication (No Data Copy).

6. Click Apply.

7. Click each tab and configure the appropriate settings as necessary, and then click OK.

For more information about the settings on each tab, click the Help button on the dialog box.

8. In the Summary pane, verify that the Next Configured Action is Simulate Replication. This indicates that the Simulate Replication option is enabled for the policy.

StorageX Administrator’s Guide 261

Page 280: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Running Phased Migration policies immediately5

9. In the left tree pane, right-click the policy and select Run.

10. After the replication simulation run finishes, review the statistics displayed in the Policy Status area.

NOTEBecause no actual replication has taken place during the simulation run, the value of the Copy Rate per Second column in the Policy Status area is N/A. Also, while the Bytes Copied column may display data after a simulation run, no data is copied when the Simulate Replication option is enabled.

11. In the Policy Status area, click the View Details link in the Event Details column.

12. Review the information provided in the Operation Details dialog box, then click Close.

13. In the left tree pane, right-click the policy and select Properties.

14. Address any configuration issues discovered during the simulation run. For more information about the settings on each tab, click the Help button on the dialog box.

15. When finished making changes to policy settings, click the General Settings > Replication Type tab.

16. Clear Simulate Replication (No Data Copy).

17. Click OK.

18. In the Summary pane, verify that the Next Configured Action is Initial Phase (Perform a baseline copy).

After you finish validating the policy settings and disabling the Simulate Replication option, when you run the Phased Migration policy, StorageX will perform the full data migration.

Running Phased Migration policies immediatelyYou can wait for a Phased Migration policy to run on the schedule specified for the policy on the Migration Schedule tab, or you can choose to run the policy immediately.

This topic explains how to run Phased Migration policies immediately.

For more information about scheduling Phased Migration policies, see “Scheduling Phased Migration policies” on page 263.

For more information about using the New Phased Migration Policy Wizard to create Phased Migration policies, see “Creating new Phased Migration policies” on page 251. For more information about generating Phased Migration policies when executing Migration Project designs, see “Executing Migration Project designs” on page 363. For more information about generating Phased Migration policies when running Archival Migration policies, see “Understanding Archival Migration policies” on page 233.

NOTEIf VNX OE for File or OneFS file storage resources are specified as destinations in Phased Migration policies generated by StorageX when executing a Migration Project design, ensure you configure the schedule for each of these policies to never advance to the Final Phase automatically by selecting the Never advance automatically; policy will remain in the Incremental Phase until advanced manually option on the Incremental Phase tab for the policy. As a general rule, ensure you run

262 StorageX Administrator’s Guide

Page 281: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Scheduling Phased Migration policies 5

Migration Project Phased Migration policies manually one at a time when the destination specified in the Destination Path field on the Migration Paths tab is a VNX OE for File or OneFS file storage resource. For more information about Migration Project designs, see “Understanding Migration Project designs” on page 326 and “Creating Migration Project designs” on page 339.

To run a Phased Migration policy immediately

1. If you created the Phased Migration policy in the Data Movement view or if an Archival Migration policy generated the policy, in the StorageX Console, click the Data Movement tab.

2. If StorageX generated the Phased Migration policy when you executed a Migration Project design, in the StorageX Console, click the Migration Projects tab.

3. In the left tree pane, browse to and select the Phased Migration policy you want to run, and then in the right pane, review the policy summary information.

4. In the left tree pane, right-click the policy and then click Properties.

5. Click each tab and verify that the policy is configured with the appropriate settings, and then click OK.

For more information about the settings on each tab, click the Help button on the dialog box.

6. In the left tree pane, right-click the Phased Migration policy and then click Run.

7. If the Run option is not available, this means that the policy is currently running or the policy was run previously. To restart the policy again, click Policy Actions, and then select the appropriate policy action to restart the policy. For more information about restarting a policy, see “Restarting Phased Migration policies” on page 269.

After you run Phased Migration policies, verify that the policies completed successfully. For more information, see “Verifying Phased Migration policies completed successfully” on page 271.

Scheduling Phased Migration policiesThe Phased Migration template associated with a Phased Migration policy includes base settings that determine when the policy runs by default. However, you can override these settings and configure a one-time or recurring schedule for Phased Migration policies as needed.

You can also use the Cutover Estimation tab of the Control Panel view to estimate whether your policy will fit within the specified window for the cutover. For more information about the cutover planning, see “Planning for storage resource cutover” on page 265.

When scheduling Phased Migration policies, consider the following examples:

Example: One time run from start to finish

For this example, assume that your plan is to copy all of the file data from the source to destination in a single pass. All of the file data is ready to be copied, users are no longer accessing the source file data, and cut over can happen immediately. In this scenario, you can configure the Phased Migration policy to use your cutover date and time as the policy schedule. You can then run the policy one time, from start to finish, by performing the following steps:

1. On the Migration Schedule tab, ensure the Use migration schedule check box is selected and specify 8:00 p.m. as the schedule.

2. On the Initial Phase tab, clear the Perform a baseline copy check box.

StorageX Administrator’s Guide 263

Page 282: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Scheduling Phased Migration policies5

3. On the Incremental Phase tab, clear the Copy the data check box to skip the Incremental Phase.

At 8:00 p.m., the policy will start. The policy will quickly run through the Initial Phase without copying any data, skip the Incremental Phase, and then run the Final Phase using the cutover options you specified on the Final Phase tab.

Example: Multiple incremental runs, then manually advance to Final Phase and cutover

For this example, assume you have users who may still be accessing the source file data. In this scenario, you plan to perform a series of incremental policy runs over time in order to ensure all file data is copied as appropriate from the source to the destination. You don’t want to run the Final Phase and cut over until you are sure that 95% or more of the file data has been copied from the source to the destination. In this scenario, you can configure the Phased Migration policy to perform multiple runs to copy the file data over time by performing the following steps:

1. On the Migration Schedule tab, ensure the Use migration schedule check box is selected and specify 8:00 p.m. every day as the schedule.

2. On the Initial Phase tab, specify whether or not you want to perform a baseline copy.

3. On the Incremental Phase tab, ensure the Copy the data check box is selected and the Never advance automatically; policy will remain in the Incremental Phase until advanced manually option is selected.

At 8:00 p.m. every day, the policy will start running and copying file data from the source to the destination. You check the progress of the copy operation every few days. When you see that the policy has copied 95% of the file data from the source to the destination, manually specify that you want to advance the policy to the Final Phase after the policy’s current Incremental Phase run completes by selecting the After policy’s current Incremental Phase run completes, advance the policy according to the Migration Schedule option on the Incremental Phase tab and specifying 11:00 p.m. on a certain date on the Migration Schedule tab for the next policy run. After you make these changes, the next time the policy runs at 11:00 p.m. it advances to the Final Phase for cutover.

You could also choose to advance the policy to the Final Phase at any time by running the policy immediately. For more information about running Phased Migration policies immediately, see “Running Phased Migration policies immediately” on page 262.

Example: Multiple incremental runs, then automatically advance to Final Phase and cutover

For this example, assume that this example is similar to the previous example. You have users who may still be accessing the source file data, and you want to perform a series of incremental policy runs over time in order to ensure all file data is copied as appropriate from the source to the destination. However, in this example, you have a specific cutover date, October 31st, 2013, and you want to simply specify the cutover date and have the policy advance to the Final Phase automatically on this date. In this scenario, you can configure the Phased Migration policy to perform multiple runs to copy the file data over time by performing the following steps:

1. On the Migration Schedule tab, ensure the Use migration schedule check box is selected and specify 8:00 p.m. every day as the schedule.

2. On the Initial Phase tab, specify whether or not you want to perform a baseline copy.

3. On the Incremental Phase tab, ensure the Copy the data check box is selected and the End the Incremental Phase and advance the policy according to the Migration Schedule after the following date and time option is selected. Then specify October 31st, 2013 at 12:00 a.m. as the date on which you want the policy to advance to the Final Phase.

264 StorageX Administrator’s Guide

Page 283: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Planning for storage resource cutover 5

At 8:00 p.m. every day, the policy will start running and copying file data from the source to the destination. At 8:00 p.m. on October 31st, which is the next time the policy runs after the October 31st, 2013 at 12:00 a.m. cutover date you specified, the policy will automatically advance to the Final Phase and cutover.

For more information about running Phased Migration policies immediately, see “Running Phased Migration policies immediately” on page 262.

For more information about using the New Phased Migration Policy Wizard to create Phased Migration policies, see “Creating new Phased Migration policies” on page 251. For more information about generating Phased Migration policies when executing Migration Project designs, see “Executing Migration Project designs” on page 363. For more information about generating Phased Migration policies when running Archival Migration policies, see “Understanding Archival Migration policies” on page 233.

NOTEIf VNX OE for File or OneFS file storage resources are specified as destinations in Phased Migration policies generated by StorageX when executing a Migration Project design, ensure you configure the schedule for each of these policies to never advance to the Final Phase automatically by selecting the Never advance automatically; policy will remain in the Incremental Phase until advanced manually option on the Incremental Phase tab for the policy. As a general rule, ensure you run Migration Project Phased Migration policies manually one at a time when the destination specified in the Destination Path field on the Migration Paths tab is a VNX OE for File or OneFS file storage resource. For more information about Migration Project designs, see “Understanding Migration Project designs” on page 326 and “Creating Migration Project designs” on page 339.

To schedule a Phased Migration policy

1. If you created the Phased Migration policy in the Data Movement view or if an Archival Migration policy generated the policy, in the StorageX Console, click the Data Movement tab.

2. If StorageX generated the Phased Migration policy when you executed a Migration Project design, in the StorageX Console, click the Migration Projects tab.

3. In the left tree pane, browse to and right-click the Phased Migration policy you want to schedule, and then click Properties.

4. Click the Migration Schedule tab.

5. Select the Use migration schedule check box.

6. If you want to create a new schedule, click New and configure a new schedule.

7. If you want to modify an existing schedule, select the schedule from the list and modify it as needed.

8. If you want to delete a schedule, select the schedule from the list and click Delete.

9. Click OK.

Planning for storage resource cutoverAfter you create one or more Phased Migration policies, you can use the Cutover Estimation tab of the Control Panel view to determine when might be the best time window in which to cut over from your source resources to your destination resources.

StorageX Administrator’s Guide 265

Page 284: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Planning for storage resource cutover5

NOTEThe Cutover Estimation tab provides only an estimate, based upon previous policy runs and available universal data engines. The cutover window suggested by a specific cutover plan should be viewed as a recommendation, not as a requirement.

To accurately estimate when to cut over from your source resources to your destination resources, first create a cutover plan. The cutover plan allows you to visualize how the Phased Migration policies in your environment fit into your overall schedule and to move policies around in the schedule as necessary for the actual cutover.

When you create a cutover plan, you specify one or more Phased Migration policies to include in the plan. StorageX then uses past incremental runs of those policies to estimate how long you can expect the policies to take when running the pre-cutover replication task in the final phase.

StorageX also automatically determines which data engine or data engine group will run each policy included in the plan. The application distributes policies across available data engines, depending on how many policy jobs each data engine can run at one time.

NOTEStorageX recommends including policies in a cutover plan that have completed at least three incremental policy runs successfully. StorageX averages the duration of those three policy runs to determine how long a policy could run at cutover. If you include a policy that has completed fewer than three incremental runs, StorageX may not be able to accurately estimate the cutover window for that policy. StorageX does not include baseline copy policy runs in the calculated average.

For more detailed information about cutover planning and estimation, see the following topics:

• “Creating a cutover plan” on page 266

• “Reviewing and modifying a cutover plan” on page 267

Creating a cutover planAfter you have created at least one Phased Migration policy for which you want to plan the cutover window, create a cutover plan.

NOTEEach cutover plan must include a minimum of one Phased Migration policy and one source storage resource.

To create a new cutover plan

1. In the StorageX Console, click the Data Movement tab.

2. Ensure you have created at least one Phased Migration policy to include in the cutover plan.

3. In the left tree, click the Control Panel tab.

4. In the Control Panel view, click the Cutover Estimation tab.

5. Click New.

6. On the Basic Settings tab, specify a name and description for the new cutover plan.

7. Specify the date and time you want to use for the start of the cutover window for the new cutover plan.

266 StorageX Administrator’s Guide

Page 285: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Planning for storage resource cutover 5

8. Specify the date and time you want to use for the end of the cutover window for the new cutover plan.

NOTEYou must specify the cutover window start and end date and/or time for a cutover plan.

9. Click the Cutover Source Devices tab, then select the storage resources you want to use as policy sources for the cutover plan.

10. If you want to add a new source storage resource to the list, click Add Device and follow the steps in the Add File Storage Resource Wizard.

11. Click the Related Policies tab, then select one or more Phased Migration policies to include in the new cutover plan.

12. If you want to view all Phased Migration policies that use the previously specified storage resources, including policies already used by another cutover plan, click Show migration policies that are already assigned to another cutover plan.

13. If you want to configure advanced settings for the cutover plan, click the Advanced tab and configure settings as necessary for your environment. For more information about each option, click the Help button on the dialog box.

14. Click OK. StorageX analyzes the specified Phased Migration policies and displays the estimated cutover window in the right pane of the Console.

Reviewing and modifying a cutover planWhen StorageX finishes analyzing a particular cutover plan, you should review the cutover window and the status provided.

In the right pane of the Console, StorageX displays each universal data engine or data engine group used by the Phased Migration policies associated with the cutover plan and each policy individually. The specified cutover window is delineated by two red lines on the Cutover Estimation view

StorageX displays the status of the cutover plan in the status indicator at the top right corner. You can click the status indicator for more information or click a specific policy in the cutover plan to see detailed information about that policy.

The following are possible options for the status of a cutover plan:

Some of the policies in the cutover plan do not have a replication duration estimate.StorageX uses information about previous runs of a Phased Migration policy to estimate how long a particular policy may run during a cutover window. We recommend only including policies that have completed a minimum of three incremental policy runs successfully.

If you include a policy that has completed fewer than three incremental runs, StorageX may not be able to accurately estimate the cutover window for that policy. StorageX does not include baseline copy policy runs in the calculated average.

Some of the policies do not fit in the cutover window.This status indicates that not all policies associated with the cutover plan will run in the specified cutover window. Policies that StorageX estimates will not fit in the cutover window are marked in red. You may need to modify the cutover window, move policies to a different universal data engine, or remove policies from the cutover plan.

StorageX Administrator’s Guide 267

Page 286: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Planning for storage resource cutover5

Some of the data engines in the cutover plan also belong to a group that is also included in the cutover plan.This status indicates that policies are assigned both to specific data engines and to one or more data engine groups of which the data engines are also members. In this situation, StorageX uses the specific data engines first, assigning policies to those data engines based on the number of jobs each data engine has available. If the data engines that belong to the data engine group are assigned policies, the data engine group may not have any remaining availability to run policies.

Some of the data engine groups in the cutover plan will not have enough capacity to run the allocated policies because other policies are assigned to specific data engines that belong to the data engine group.This status indicates that policies are assigned both to specific data engines and to one or more data engine groups of which the data engines are also members, and the data engine groups do not have sufficient availability to run assigned policies.

As configured, the cutover plan should complete within the specified cutover window.This status indicates that StorageX estimates that the specified policies should be able to complete successfully within the cutover window.

NOTEThe status indicator does not display all potential issues related to a cutover plan. StorageX only displays the most severe problem found for that cutover plan during the analysis.

If StorageX returns an error, you may need to modify the cutover plan to address the issue, either to add or remove policies from the cutover plan, add or remove sources from the plan, modify included policies, or change the cutover window.

To review and modify a cutover plan or associated policies

1. In the StorageX Console, click the Control Panel tab.

2. In the Control Panel view, click the Cutover Estimation tab.

3. If the cutover plan you want to review is not already displayed, click Open, select the cutover plan, and click Open again.

4. If you want to modify the cutover plan, complete the following steps:

a. Click Configure.

b. Modify the cutover window, add or remove sources, add or remove policies, or configured advanced cutover plan settings, as necessary to resolve issues with your cutover plan.

c. Click OK.

5. If you want to modify a Phased Migration policy included in the cutover plan, complete the following steps:

a. Right-click the policy and select Open.

b. Modify the migration path, universal data engine selection, or migration schedule for the policy, as necessary to resolve issues with your cutover plan.

c. Click OK.

6. If you want to move a Phased Migration policy to a different universal data engine, click the policy you want to move, drag the policy to the new data engine, and drop the policy on the data engine.

268 StorageX Administrator’s Guide

Page 287: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Canceling Phased Migration policies 5

7. If you want to remove a Phased Migration policy from the cutover plan, complete the following steps:

a. Right-click the policy and select Remove.

b. Click Yes to confirm.

8. When you modify the cutover plan configuration or any associated policies, StorageX automatically re-analyzes the modified cutover plan.

Canceling Phased Migration policiesYou can view running Phased Migration policies on the Tasks tab. The Tasks tab displays at the bottom of the StorageX Console.

If you start to run a Phased Migration policy and need to stop it before the policy completes, you can cancel the policy and restart it later.

NOTEIf you cancel a Phased Migration policy, the policy will not automatically run again the next time the policy is scheduled to run. You must manually go to the policy, right-click the policy, and then select the appropriate policy action from the Policy Actions menu to restart the policy run. For more information about restarting a Phased Migration policy, see “Restarting Phased Migration policies” on page 269

To cancel a Phased Migration policy

1. If you created the Phased Migration policy in the Data Movement view or if an Archival Migration policy generated the policy, in the StorageX Console, click the Data Movement tab.

2. If StorageX generated the Phased Migration policy when you executed a Migration Project design, in the StorageX Console, click the Migration Projects tab.

3. If you want to cancel the Phased Migration policy while viewing the running Phased Migration policy on the Tasks tab, right-click the running Phased Migration policy, and then click Cancel.

4. If you want to cancel the running Phased Migration policy from the tree view, in the left tree pane, right-click the running Phased Migration policy you want to cancel, and then click Cancel.

Restarting Phased Migration policiesIf you cancel a Phased Migration policy before the policy completes, you can restart the policy later.

When you restart a Phased Migration policy, StorageX continues the policy run from the point at which it was canceled. The policy run can be continued safely because any changes to that StorageX has made to files were made to the files in their new destination location, and not to the files in the original source location.

This topic explains how to restart a Phased Migration policy. For more information about canceling a Phased Migration policy, see “Canceling Phased Migration policies” on page 269.

StorageX Administrator’s Guide 269

Page 288: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Restarting Phased Migration policies5

To restart a Phased Migration policy

1. If you created the Phased Migration policy in the Data Movement view or if an Archival Migration policy generated the policy, in the StorageX Console, click the Data Movement tab.

2. If StorageX generated the Phased Migration policy when you executed a Migration Project design, in the StorageX Console, click the Migration Projects tab.

3. In the left tree pane, browse to and select the Phased Migration policy you want to restart.

4. If you want to see how much of the policy completed previously before you restart it, in the center pane, review the information in the Status and Policy Status areas. For more information about the information provided in these areas, see “Verifying Phased Migration policies completed successfully” on page 271.

5. If the Phased Migration policy stopped because of an error, review the policy manifest for the last run of the policy to obtain detailed information about the error and then address the error. For more information about policy manifests and reviewing policy manifests, see “Verifying Phased Migration policies completed successfully” on page 271.

6. Restart the policy by completing the following steps:

a. In the left tree pane, right-click the Phased Migration policy and then click Policy Actions.

NOTEIf StorageX displays one or more of the policy actions as unavailable, this means that the policy has already executed the action successfully. For example, if the first action for a Phased Migration policy is to perform a baseline copy in the Initial Phase and the policy performs this action successfully, the Reset policy to the first action the next time the policy runs action displays as unavailable. If all policy action options display as unavailable, this means that the policy has already run successfully.

b. If you want to restart the Phased Migration policy from the beginning the next time the policy runs, select Reset policy to the first action the next time the policy runs.

c. If the Phased Migration policy stopped at some point during the Initial Phase, Incremental Phase, or Final Phase and you want to try running the policy again by retrying the last action the next time the policy runs, select Set policy to retry the last action the next time the policy runs.

d. If the Phased Migration policy stopped at some point during the Initial Phase, Incremental Phase, or Final Phase and you want to try running the policy again without trying the last action the next time the policy runs, select Advance policy to the next action the next time the policy runs.

NOTEIf the Do not advance if the data copy operation completed with errors option is configured for the Phased Migration policy, and then you right-click the policy and select Policy Actions > Advance policy to the next action the next time the policy runs, the Advance policy option overrides the previously configured Do not advance option.

270 StorageX Administrator’s Guide

Page 289: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying Phased Migration policies completed successfully 5

Verifying Phased Migration policies completed successfullyOnce you run a Phased Migration policy, you can view policy status information and the policy manifest to verify that the policy completed successfully. The policy manifest provides detailed information about the last run of the policy.

You can also use information in the Alerts and Events views to verify whether a policy completed successfully and to troubleshoot issues. The Events view is a complete historical listing of events. StorageX appends new events to the list in the Events view every time you run a policy. The Alerts view provides information for only the latest run of a policy. Every time you run a policy, StorageX deletes the alerts from the previous run.

You can export policy manifests and alert and event details and save them as reports in *.tsv format. This information can be useful not only for auditing purposes, but also for regulatory compliance purposes.

When you verify whether a Phased Migration policy completed successfully, ensure you check to see if StorageX encountered any locked files during the policy run. StorageX cannot copy files that are locked on the source to the destination.

You can see if StorageX encountered any locked files during the policy run by selecting the policy in the left tree pane, and then in the right pane, in the Policy Status area, reviewing the information displayed in the Files Failed column. The Files Failed column shows the number of files that StorageX was not able to copy from the source and the destination. The most common reason for StorageX failing to copy a file is that the file was locked because it was in use by a user during the policy run.

If you want to be able to see exactly which files failed, you can view this information in the policy manifest if you select the Only list files that encounter errors option in the Event details field on the General Options tab for a Phased Migration policy.

If you want to see a spreadsheet of all errors in the manifest for one or more policies, you can export the consolidated manifest errors for your policies in .tsv format from the My Policies window in the Console by right-clicking the policy and selecting Consolidate Manifest Errors. This allows you to quickly view and organize all the errors your policies encountered while running.

If you used a batch file in a Phased Migration policy and the policy did not complete successfully, ensure you met requirements for using batch files. For more information, see “Using batch files with Data Movement policies” on page 315.

To verify a Phased Migration policy completed successfully

1. If you created the Phased Migration policy in the Data Movement view or if an Archival Migration policy generated the policy, in the StorageX Console, click the Data Movement tab.

2. If StorageX generated the Phased Migration policy when you executed a Migration Project design, in the StorageX Console, click the Migration Projects tab.

3. In the left tree pane, select the Phased Migration policy you want to verify.

4. In the center pane, review the following information in the Status area:

• Status - Displays summary status information for the overall Phased Migration policy.

If the policy is still in progress, In Progress displays.

If the policy has not yet been run, or if the policy has run previously, but the policy will run again in the future, Scheduled displays.

StorageX Administrator’s Guide 271

Page 290: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying Phased Migration policies completed successfully5

If user action is required before the policy can continue, User action required displays.

This status displays for a Phased Migration policy when you specified on the Initial Phase, Incremental Phase, or Final Phase tab for the policy that you wanted to pause the policy run when an error occurs by selecting the Only on error option in the Pause after this step field.

This status also displays if you specified on the Initial Phase, Incremental Phase, or Final Phase tab for the policy that you always want to pause the policy run after a particular action occurs, such as performing a baseline copy. When you select the Always option in the Pause after this step field, the policy run will not continue until you manually advance the policy.

If the policy stopped due to an error, address the error and then either retry the last action or continue with the next action. To see the cause of the error, select the policy in the left tree pane, and then in the center pane, in the Policy Status area, click the View Details link in the Event Details column. When you click the View Details link, StorageX displays the manifest for the policy run. The manifest for the policy run provides additional details about the policy run. After you have addressed the error, you can choose to either retry the last action or continue with the next action. To retry the last action, right-click the policy and then select Policy Actions > Set policy to retry the last action the next time the policy runs. To continue with the next action, right-click the policy and then select Policy Actions > Advance policy to the next action the next time the policy is run.

If the policy run stopped because you specified that you wanted to pause the policy after a particular action occurred, such as performing a baseline copy, when you are ready to continue the policy run, right-click the policy and then select Policy Actions > Advance policy to the next action the next time the policy is run.

NOTEIf the Do not advance if the data copy operation completed with errors option is configured for the Phased Migration policy, and then you right-click the policy and select Policy Actions > Advance policy to the next action the next time the policy runs, the Advance policy option overrides the previously configured Do not advance option.

If you or someone else canceled the policy, Canceled displays. When you are ready to continue the policy run, right-click the policy, select Policy Actions, and then restart the policy by selecting the appropriate action.

If the policy encountered an internal error, Invalid Parameters displays. This status rarely, if ever, displays, and indicates an internal inconsistency within StorageX. If this status displays, contact Data Dynamics, Inc. Technical Support.

If the policy has completed, Completed is displayed.

If the policy has never run, Unknown is displayed. Once you run the policy, this field is updated to display the current policy status.

• Last Action - Displays the last action performed by the policy. StorageX updates this field with information about the last policy action as policy actions complete.

If the policy is currently running, Unknown displays. StorageX updates this field with information about the last policy action as policy actions complete.

If you specified on the Initial Phase tab for a Phased Migration policy that you wanted to run a pre-migration batch file, and the last action the policy performed was running the pre-migration batch file, Run pre-Migration batch file displays.

272 StorageX Administrator’s Guide

Page 291: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying Phased Migration policies completed successfully 5

If you specified on the Initial Phase tab for a Phased Migration policy that you wanted to perform a base line copy of the data during the Initial Phase, and the last action the policy performed was performing a baseline copy of the data, Perform a baseline copy displays.

If you specified on the Incremental Phase tab for a Phased Migration policy that you wanted to copy the data during the Incremental Phase, and the last action the policy performed was copying the data, Copy the data in Incremental Phase displays.

If StorageX has completed the Incremental Phase and is currently evaluating whether the policy should advance to the final phase, Evaluate conditions for advancement to the Final Phase displays.

If you specified on the Final Phase tab for a Phased Migration policy that you wanted to update DFS namespaces or automount map files in the Final Phase, and the last action the policy performed was updating DFS namespaces or automount map files, Update DFS namespace or automount maps displays.

If you specified on the Final Phase tab for a Phased Migration policy that you wanted to prevent user connections during final copy for sources that are shares, and the last action the policy performed was preventing user connections during the final copy, Prevent user connections during final copy displays.

If you specified on the Final Phase tab for a Phased Migration policy that you wanted to do a final replication, and the last action the policy performed was performing the final replication, Do final replication displays.

If you specified on the Final Phase tab for a Phased Migration policy that you wanted to stop sharing the source after the final replication, and the last action the policy performed was stop sharing the source, Stop sharing source displays.

If you specified on the Final Phase tab for a Phased Migration policy that you wanted to run a post-migration batch file, and the last action the policy performed was running the batch file, Run post-Migration batch file displays.

If the Phased Migration policy was generated by a Migration Project and StorageX is running a pre-migration check to see if items like credentials are configured correctly so StorageX can access the source and destination, Pre-migration check displays.

If the Phased Migration policy was generated by a Migration Project and StorageX is creating shares or exports on the destination with the same settings as the shares or exports on the source, Sharing data on destination displays. StorageX creates shares and exports on the destination with the same settings as the shares and exports on the source at the beginning of the Final Phase when running Phased Migration policies created by a Migration Project.

If the Phased Migration policy was generated by a Migration Project and StorageX is performing final operations at the end of the policy run such as creating quotas on the destination that have the same settings as quotas on the source, Post-migration operations displays.

• Last Action Result - Displays the result of the last action.

If the policy is currently running, Unknown displays. StorageX updates this field with information about the last policy action as policy actions complete.

If the last action completed successfully, Completed successfully displays.

StorageX Administrator’s Guide 273

Page 292: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying Phased Migration policies completed successfully5

If the last action completed with warnings, Completed with warnings displays. To see the warnings, as well as additional information about the cause of the warnings, select the policy in the left tree pane, and then in the center pane, in the Policy Status area, click the View Details link in the Event Details column. When you click the View Details link, StorageX displays the manifest for the policy run. The manifest for the policy run provides additional details about the policy run, including information about the cause any warnings.

If the last action completed with errors, Completed with errors displays. To see the errors, as well as additional information about the cause of the errors, select the policy in the left tree pane, and then in the center pane, in the Policy Status area, click the View Details link in the Event Details column. When you click the View Details link, StorageX displays the manifest for the policy run. The manifest for the policy run provides additional details about the policy run, including information about the cause any errors.

After you address the errors, you can choose to either retry the last action or continue with the next action. To retry the last action, right-click the policy in the left tree pane and then select Policy Actions > Set policy to retry the last action the next time the policy runs. To continue with the next action, right-click the policy in the left tree pane and then select Policy Actions > Advance policy to the next action the next time the policy is run.

If the last action was the canceling of the policy, Canceled displays. When you are ready to restart the policy, you can choose to either retry the last action or continue with the next action. To retry the last action, right-click the policy in the left tree pane and then select Policy Actions > Set policy to retry the last action the next time the policy runs. To continue with the next action, right-click the policy in the left tree pane and then select Policy Actions > Advance policy to the next action the next time the policy is run.

NOTEIf the Do not advance if the data copy operation completed with errors option is configured for the Phased Migration policy, and then you right-click the policy and select Policy Actions > Advance policy to the next action the next time the policy runs, the Advance policy option overrides the previously configured Do not advance option.

If the last action was canceled because a time window you specified for the policy on the Migration Schedule tab for the policy expired, Canceled (time window expired) displays.

If the last action could not be completed for some unknown reason, Unknown displays. This status rarely, if ever displays, and may indicate an unhandled exception. If this status displays, contact Data Dynamics, Inc. Technical Support.

If the last action failed, Failed displays. This status rarely, if ever displays. If this status displays, to try and see the cause of the failure, as well as additional information about the failure, select the policy in the left tree pane, and then in the center pane, in the Policy Status area, click the View Details link in the Event Details column. When you click the View Details link, StorageX displays the manifest for the policy run. The manifest for the policy run provides additional details about the policy run, and may include additional information about the cause of the failure. After you review the information in the policy manifest regarding the failure, if you still need additional assistance, contact Data Dynamics, Inc. Technical Support.

• Last Replication Result - Displays the result of the last replication.

If the policy has not replicated data previously, None displays.

If the last replication completed successfully, Completed successfully displays.

274 StorageX Administrator’s Guide

Page 293: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying Phased Migration policies completed successfully 5

If the last replication completed with warnings, Completed with warnings displays. To see the warnings, as well as additional information about the cause of the warnings, select the policy in the left tree pane, and then in the center pane, in the Policy Status area, click the View Details link in the Event Details column. When you click the View Details link, StorageX displays the manifest for the policy run. The manifest for the policy run provides additional details about the policy run, including information about the cause of any warnings.

If the last replication completed with errors, Completed with errors displays. To see the errors, as well as additional information about the cause of the errors, select the policy in the left tree pane, and then in the center pane, in the Policy Status area, click the View Details link in the Event Details column. When you click the View Details link, StorageX displays the manifest for the policy run. The manifest for the policy run provides additional details about the policy run, including information about the cause of any errors.

After you address the errors, you can choose to either retry the last action or continue with the next action. To retry the last action, right-click the policy in the left tree pane and then select Policy Actions > Set policy to retry the last action the next time the policy runs. To continue with the next action, right-click the policy in the left tree pane and then select Policy Actions > Advance policy to the next action the next time the policy is run.

If the last replication was canceled, Canceled displays. When you are ready to restart the policy, you can choose to either retry the last action or continue with the next action. To retry the last action, right-click the policy in the left tree pane and then select Policy Actions > Set policy to retry the last action the next time the policy runs. To continue with the next action, right-click the policy in the left tree pane and then select Policy Actions > Advance policy to the next action the next time the policy is run.

NOTEIf the Do not advance if the data copy operation completed with errors option is configured for the Phased Migration policy, and then you right-click the policy and select Policy Actions > Advance policy to the next action the next time the policy runs, the Advance policy option overrides the previously configured Do not advance option.

If the last replication is still in progress, In Progress displays.

5. In the center pane, in the Policy Status area, you can optionally review the last 30 runs of the policy, including the following information:

• Completion State - Displays the completion state for the last run of the policy.

If the run of the policy is still in progress, In Progress displays.

If the run of the policy completed successfully, Completed successfully displays.

If the last run of the policy completed with warnings, Completed with warnings displays. To see the warnings, as well as additional information about the cause of the warnings, select the policy in the left tree pane, and then in the center pane, in the Policy Status area, click the View Details link in the Event Details column. When you click the View Details link, StorageX displays the manifest for the policy run. The manifest for the policy run provides additional details about the policy run, including information about the cause any warnings.

StorageX Administrator’s Guide 275

Page 294: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying Phased Migration policies completed successfully5

If the last run of the policy completed with errors, Completed with errors displays. To see the errors, as well as additional information about the cause of the errors, select the policy in the left tree pane, and then in the center pane, in the Policy Status area, click the View Details link in the Event Details column. When you click the View Details link, StorageX displays the manifest for the policy run. The manifest for the policy run provides additional details about the policy run, including information about the cause any errors.

After you address the errors, you can choose to either retry the last action or continue with the next action. To retry the last action, right-click the policy in the left tree pane and then select Policy Actions > Set policy to retry the last action the next time the policy runs. To continue with the next action, right-click the policy in the left tree pane and then select Policy Actions > Advance policy to the next action the next time the policy is run.

If the last run of the policy was canceled, Canceled displays. When you are ready to restart the policy, you can choose to either retry the last action or continue with the next action. To retry the last action, right-click the policy in the left tree pane and then select Policy Actions > Set policy to retry the last action the next time the policy runs. To continue with the next action, right-click the policy in the left tree pane and then select Policy Actions > Advance policy to the next action the next time the policy is run.

NOTEIf the Do not advance if the data copy operation completed with errors option is configured for the Phased Migration policy, and then you right-click the policy and select Policy Actions > Advance policy to the next action the next time the policy runs, the Advance policy option overrides the previously configured Do not advance option.

If the last run of the policy stopped unexpectedly because of an issue outside of StorageX, Unknown displays. This status indicates that due to a major external issue like a database failure, unexpected reboot, or power outage, StorageX was unable to send the final status of the policy run to the database. We recommend that you re-run the policy by right-clicking the policy in the left tree pane and selecting Run, to ensure that migration completes successfully.

• Source - Displays the path for the source specified for the policy.

• Destination - Displays the path for the destination specified for the policy.

• Files Copied - Displays the number of files copied during the policy run.

• Bytes Copied - Displays the number of bytes copied during the policy run.

• Files Security Copied - Displays the number of files where file attributes were copied during the policy run. This column does not display the number of files where file data was copied.

• Files in Sync - Displays the number of files in sync between the source and destination during the policy run.

• Bytes in Sync - Displays the number of bytes in sync between the source and destination during the policy run.

• Files Deleted - Displays the number of files deleted during a policy run. A number displays in this field only if you selected the Delete orphaned files and folders on the destination setting on the General Options tab for a Phased Migration policy.

• Bytes Deleted - Displays the number of bytes deleted during the policy run. A number displays in this field only if you selected the Delete orphaned files and folders on the destination setting on the General Options tab for a Phased Migration policy.

276 StorageX Administrator’s Guide

Page 295: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying Phased Migration policies completed successfully 5

• Files Failed - Displays the number of files that StorageX was not able to copy from the source and the destination. The most common reason for StorageX failing to copy a file is that the file was locked because it was in use by a user during the policy run. If you want to be able to see exactly which files failed, you can view this information in the policy manifest if you selected the Only list files that encounter errors option in the Event details field on the General Options tab for a Phased Migration policy.

• Data Engine - Displays the name of the computer that hosts the StorageX universal data engine that performed the policy run.

• Event Details - Displays a View Details link to a policy manifest that provides additional detailed information about the policy run. When you click the View Details link and open up the policy manifest, you can see detailed information about the policy run, including number of files and folders copied, number of files and folders in sync, number of files and folders deleted, number of files failed, and more.

If you want to save the detailed information in the policy manifest to a .tsv report, on the Operation Details dialog box, click Export. In the Specify Report Options dialog box, you can specify a file name and the location where you want to save the report. For more information, click the Help button on the dialog box.

• Started - Displays the date and time the policy run started.

• Stopped - Displays the date and time the policy run ended.

• Queued - Displays the time the policy was queued for the universal data engine to run.

6. If you want to see all of the events generated during a policy run, click the Events view to see events associated with the execution of the policy.

7. If you want to view all the details for a particular event, complete the following steps:

a. Double-click the event in the Events view to open the Event Viewer dialog box.

b. Click Details to view event details.

c. If you want to save the event details to a report, in the Event Details dialog box, click Export. In the Specify Report Options dialog box, you can specify a file name and the location where you want to save the report. For more information, click the Help button on the dialog box.

8. If you want to check for any errors or warnings generated during a policy run, click the Alerts view.

9. If you want to view all the details for a particular alert, complete the following steps:

a. Double-click the alert in the Alerts view to open the Alert Details dialog box.

b. If you want to save the alert details to a report, in the Alert Details dialog box, click Export. In the Specify Report Options dialog box, you can specify a file name and the location where you want to save the report. For more information, click the Help button on the dialog box.

10. If you want to export all errors in the manifest for one or more policies as a .tsv file, complete the following steps:

a. Ensure the policy or policies are copied into the My Policies folder.

b. In the left tree pane, click My Policies.

c. Select one or more policies and right-click Consolidate Manifest Errors. Use the Ctrl or Shift keys to select multiple policies.

StorageX Administrator’s Guide 277

Page 296: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Phased Migration policies5

d. Specify a file name and location and click OK.

e. If you want to open the consolidated manifest error file, click Open. You may need to specify a program to use when opening the file.

f. If you want to go directly to the folder where StorageX exported the consolidated file, click Open Folder.

g. Click Close.

h. In the .tsv file, view and sort the consolidated errors as necessary.

11. If the policy stopped with errors, you can resume running the policy after you have addressed the errors. In the tree pane, right-click the Phased Migration policy and click Policy Actions > Retry the last action now or Continue the next action now. For more information, see “Restarting Phased Migration policies” on page 269.

Managing Phased Migration policiesThis section explains how to manage Phased Migration policies. For more information about creating Phased Migration policies, see “Creating Phased Migration policies” on page 250.

The following topics provide more information about managing Phased Migration policies:

• “Modifying Phased Migration policy properties” on page 279

• “Configuring replication options for Phased Migration policies” on page 279

• “Specifying migration options for Phased Migration policies” on page 280

• “Working with policy file and folder inclusion and exclusion filters” on page 280

• “Running batch files with Phased Migration policies” on page 286

• “Assigning universal data engines or universal data engine groups to Phased Migration policies” on page 288

• “Processing security identifiers (SIDs) in a Phased Migration policy” on page 289

• “Changing the template specified for a Phased Migration policy” on page 290.

• “Viewing and managing default settings for Phased Migration policies” on page 291.

• “Renaming Phased Migration policies” on page 291

• “Creating custom folders for Data Movement Phased Migration policies” on page 292

• “Viewing Phased Migration policies scheduled to run in the future” on page 292

• “Deleting Phased Migration policies” on page 293

278 StorageX Administrator’s Guide

Page 297: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Phased Migration policies 5

Modifying Phased Migration policy propertiesAfter you create a Phased Migration policy, you can modify its properties or specify additional properties before you run the policy. Once you have run the policy, you cannot change the specified source or destination path for the policy. However, if the policy is set to run on a recurring schedule, you can make other changes to the policy that will be effective the next time the policy runs.

To modify the properties of a Phased Migration policy

1. If you created the Phased Migration policy in the Data Movement view or if an Archival Migration policy generated the policy, in the StorageX Console, click the Data Movement tab.

2. If StorageX generated the Phased Migration policy when you executed a Migration Project design, in the StorageX Console, click the Migration Projects tab.

3. In the left tree pane, right-click a Phased Migration policy and then click Properties.

4. Click the tab for the properties that you want to update, and then specify options. as appropriate. For more information about each option, click the Help button on the dialog box.

5. Click OK.

Configuring replication options for Phased Migration policiesYou can configure several replication options for Phased Migration policies.

Replication options allow you to specify how you want to replicate, or copy, data from the source to the destination. For example, you can specify which folders and files you want to replicate, the universal data engine you want to use to copy data, and other options, such as whether you want to use differential replication, how you want to replicate security descriptors for files, and how you want to replicate file attributes.

To configure replication options for a Phased Migration policy

1. If you created the Phased Migration policy in the Data Movement view or if an Archival Migration policy generated the policy, in the StorageX Console, click the Data Movement tab.

2. If StorageX generated the Phased Migration policy when you executed a Migration Project design, in the StorageX Console, click the Migration Projects tab.

3. In the left tree pane, browse to and right-click the policy, and then click Properties.

4. In the left pane, under Replication Options, specify the replication options you want to use on each of the following tabs:

• General Options

• Replication Filters

• Universal Data Engine Selection

• Differential Replication

• Replication Scripting

• CIFS Security Replication

• CIFS Attribute Replication

• NFS Security Replication

StorageX Administrator’s Guide 279

Page 298: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Phased Migration policies5

For more information about the options available on each tab, click the Help button on the dialog box.

5. Click OK.

Specifying migration options for Phased Migration policiesYou can configure several migration options for Phased Migration policies. Migration options allow you to specify the schedule you want to use for the migration, as well as what actions you want the policy to perform in the Initial, Incremental, and Final phases of the migration.

If you have implemented DFS namespaces or automount map files in your environment, migration options also allow you to specify whether or not you want the policy to update these items in the Final phase of the migration.

To specify migration options

1. If you created the Phased Migration policy in the Data Movement view or if an Archival Migration policy generated the policy, in the StorageX Console, click the Data Movement tab.

2. If StorageX generated the Phased Migration policy when you executed a Migration Project design, in the StorageX Console, click the Migration Projects tab.

3. In the left tree pane, browse to and right-click a Phased Migration policy, and click Properties.

4. In the left pane, under Migration Options, specify the migration options you want to use on each of the following tabs:

• Initial Phase

• Incremental Phase

• Final Phase

• DFS Namespaces

• Automounts

• Migration Schedule

For more information about how to use the options available on each tab, click the Help button on the dialog box.

5. Click OK.

Working with policy file and folder inclusion and exclusion filtersStorageX allows you to configure file and folder inclusion and exclusion filters for Phased Migration policies. You configure inclusion and exclusion filters on the Replication Filters tab for a Phased Migration policy.

This section explains how file and folder inclusion and exclusion filters for Phased Migration policies work. This section also provides examples of inclusion and exclusion filter formats and explains how to specify file and folder inclusion and exclusion filters for Phased Migration policies.

This section includes the following topics:

• “Understanding Phased Migration policy inclusion filters” on page 281

• “Examples of valid inclusion filters for Phased Migration policies” on page 282

• “Understanding Phased Migration policy exclusion filters” on page 283

280 StorageX Administrator’s Guide

Page 299: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Phased Migration policies 5

• “Examples of valid exclusion filters for Phased Migration policies” on page 284

• “Specifying file and folder inclusion and exclusion filters for Phased Migration polices” on page 285

For more information about Phased Migration policies, see “Understanding Phased Migration policies” on page 230 and “Creating Phased Migration policies” on page 250.

Understanding Phased Migration policy inclusion filters

By default, StorageX includes all files and folders on the source in the migration. When you specify an inclusion filter, you are specifying that you want to include only a subset of the files and folders on the source in the migration. If you do not specify an inclusion filter, by default StorageX uses *.

When you create inclusion filters on the Replication Filters tab for Phased Migration policies, remember the following points:

• StorageX processes exclusion filters before inclusion filters. Files or folders matching an exclusion filter are not processed further and cannot be included by a subsequent inclusion filter.

• Folder inclusion filters are search expressions composed of folder names or folder paths that you can use to include any folders matching the specified inclusion criteria.

• Folder inclusion filters should use the root-level path you want StorageX to migrate. For example, if you want to migrate the source /vol/vol1/qtree and want to include the subfolder /vol/vol1/qtree/F1, the folder inclusion filter would be /F1.

• File inclusion filters are search expressions composed of file names or extensions that you can use to include files matching the specified inclusion criteria. If you want to include all files in a directory, use a folder or path inclusion filter, instead.

• Inclusion filters are additive. If you create multiple filters for the same policy, only files or folders matching all filters will be included.

• You can use DOS wildcards alone or in concert with a character string to include files or folders of similar name or type.

• To match a string of characters of any length, including an empty string, type an asterisk (*). For example, s*d finds sad, sLKJLKJHd, and sd.

• To match any single character in the search text, use a question mark (?). For example, s?t finds set and sit, but not Saturday.

• Inclusion filters are case-sensitive when they list directories and files on NFS file storage resources.

• You must delimit multiple folder or file inclusion filter parameters with double quotes, or click Expand to specify multiple files, file types, or folders.

• When you select the Include subfolders setting in the General Options tab of a Phased Migration policy and you specify file inclusion filters, StorageX traverses subfolders for files to include in the destination. StorageX always traverses subfolders to the destination even when they are empty.

• When you select the Delete orphaned files and folders on the destination setting on the General Options tab for a Phased Migration policy, the inclusion filters affect how StorageX handles orphan files on the destination. StorageX deletes orphan files on the destination that match inclusion filters.

StorageX Administrator’s Guide 281

Page 300: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Phased Migration policies5

Examples of valid inclusion filters for Phased Migration policies

The following table provides examples of valid inclusion filters for Phased Migration policies and descriptions for each filter.

NOTEThe following list only presents examples of possible valid filters a user could create. This list is not meant to represent all possible options for using various DOS wildcards in a filter.

TABLE 25 Examples of valid file and folder inclusion filters for Phased Migration policies

Format Applied to Description

* Files or folders When used specifically as a folder inclusion parameter, includes only folders (no files) of the specified parent. When used as a file inclusion parameter, includes all files and all folders.

*.* Files Includes all files contained within the specified parent and their associated child folders.

\ (CIFS)/ (NFS)

Folders When used as a folder inclusion parameter, includes all folders and files contained within the specified parent.

\* (CIFS)/* (NFS)

Files or folders When used as a folder inclusion parameter, includes all folders. When used as a file inclusion parameter, includes all files and related folders.

\*.* (CIFS)/*.* (NFS)

Files When used as a file inclusion parameter, includes all files contained in the parent.

*.tmp Files Includes all files with a .tmp file extension.

listing Files or folders Includes files or folders named listing.

listing.txt Files Includes files named listing.txt.

listing???.txt Files Includes all text files that begin with the string listing followed by any three characters and end with .txt.

listing*.txt Files Includes all text files with names that start with the literal character string listing and end with .txt.

\listing (CIFS)/listing (NFS)

Folders This example traverses the directory tree and includes folders named listing.By prepending the slash character to the folder name, only folders named listing that reside directly under the root folder are included. The following example is not included:<root>\test\listing

listing\ or \listing\ (CIFS)listing/ or /listing/ (NFS)

Folders This example traverses the directory tree and includes subfolders of the listing folder.

282 StorageX Administrator’s Guide

Page 301: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Phased Migration policies 5

Understanding Phased Migration policy exclusion filters

When you create exclusion filters on the Replication Filters tab for Phased Migration policies, remember the following points:

• StorageX processes exclusion filters before inclusion filters. Files or folders matching an exclusion filter are not processed further and cannot be included by a subsequent inclusion filter.

• Folder exclusion filters are search expressions composed of folder names or folder paths that you can use to exclude any folders matching the specified exclusion criteria.

• Folder exclusion filters should use the root-level path you want StorageX to migrate. For example, if you want to migrate the source /vol/vol1/qtree and want to exclude the subfolder /vol/vol1/qtree/F1, the folder exclusion filter would be /F1.

• File exclusion filters are search expressions composed of file names or extensions that you can use to exclude files matching the specified exclusion criteria. If you want to exclude all files in a directory, use a folder or path exclusion filter, instead.

• Exclusion filters are additive. If you create multiple filters for the same policy, only files or folders matching all filters will be excluded.

• You can use DOS wildcards alone or in concert with a character string to exclude files or folders of similar name or type.

• To match a string of characters of any length, including an empty string, type an asterisk (*). For example, s*d finds sad, sLKJLKJHd, and sd.

• To match any single character in the search text, use a question mark (?). For example, s?t finds set and sit, but not Saturday.

• To exclude a subfolder and its contents, the trailing backward slash (\) or forward slash (/) is optional. StorageX excludes the subfolder and its contents whether or not the trailing backward slash or forward slash is present.

• Exclusion filters are case-sensitive when they list directories and files on NFS computers.

• You must delimit multiple folder or file exclusion filter parameters with double quotes, or click Expand to specify multiple files, file types, or folders.

• When you select the Include subfolders option in the General Options tab of a Phased Migration policy and you specify file exclusion filters, StorageX traverses subfolders for files to exclude from the destination. StorageX always transfers subfolders to the destination even when they are empty.

*\listing (CIFS)*/listing (NFS)

Folders Includes subfolders named listing.

*\listing\file.txt (CIFS)*/listing/file.txt(NFS)

Files Includes files named file.txt located in a subfolder named listing.

TABLE 25 Examples of valid file and folder inclusion filters for Phased Migration policies

Format Applied to Description

StorageX Administrator’s Guide 283

Page 302: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Phased Migration policies5

• When you select the Delete orphaned files and folders on the destination setting on the General Options tab for a Phased Migration policy, the exclusion filters affect how StorageX handles orphan files on the destination. StorageX does not delete orphan files on the destination that match the exclusion filter, but does delete orphan files that do not match the exclusion filter.

Examples of valid exclusion filters for Phased Migration policies

The following table provides examples of valid file and folder exclusion filters and descriptions for each filter.

NOTEThe following list only presents examples of possible valid filters a user could create. This list is not meant to represent all possible options for using various DOS wildcards in a filter.

TABLE 26 Examples of valid file and folder exclusion filters for Phased Migration policies

Format Applied to Description

* Files or folders When used specifically as a folder exclusion parameter, excludes all files and folders. When used specifically as a file exclusion parameter, folders are still included, but all files contained in those folders are excluded.

*.* Files Excludes all files contained within the specified parent and their associated child folders.

\ (CIFS)/ (NFS)

Folders When used as a directory exclusion parameter, excludes all files and folders contained within the specified parent and child folders.

\* (CIFS)

/* (NFS)

Files or folders When used as a folder exclusion parameter, excludes all files and

all folders. When used as a file exclusion parameter, excludes all

files.

\*.* (CIFS)/*.* (NFS)

Files When used as a file exclusion parameter, excludes all files contained in the parent.

*.tmp Files Excludes all files with a .tmp file extension.

listing Files or folders Excludes files or folders named listing.

listing.txt Files Excludes files named listing.txt.

listing???.txt Files Excludes all text files that begin with the string listing followed by any three characters and end with .txt.

listing*.txt Files Excludes all text files with names that start with the literal character string listing and end with .txt.

\listing (CIFS)/listing (NFS)

Folders This example traverses the directory tree and excludes folders named listing.By prepending the slash character to the folder name, only folders named listing that reside directly under the root folder are excluded. The following example is not excluded:<root>\test\listing

284 StorageX Administrator’s Guide

Page 303: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Phased Migration policies 5

Specifying file and folder inclusion and exclusion filters for Phased Migration polices

You can create file and folder inclusion and exclusion filters for Phased Migration policies on the Replication Filters tab for a Phased Migration policy.

File and folder inclusion and exclusion filters for Phased Migration policies allow you to specify which folders and files you want to exclude from or include in the migration.

This topic explains how to specify file and folder inclusion and exclusion filters for Phased Migration policies. For more information about inclusion and exclusion filters, see the following topics:

• “Understanding Phased Migration policy inclusion filters” on page 281

• “Examples of valid inclusion filters for Phased Migration policies” on page 282

• “Understanding Phased Migration policy exclusion filters” on page 283

• “Examples of valid exclusion filters for Phased Migration policies” on page 284

To specify file and folder inclusion and exclusion filters for Phased Migration policies

1. If you created the Phased Migration policy in the Data Movement view or if an Archival Migration policy generated the policy, in the StorageX Console, click the Data Movement tab.

2. If StorageX generated the Phased Migration policy when you executed a Migration Project design, in the StorageX Console, click the Migration Projects tab.

3. In the left tree pane, browse to and right-click the Phased Migration policy where you want to specify file or folder inclusion or exclusion filters, and then click Properties.

4. Click the Replication Filters tab.

NOTEIf your source is a Windows file storage resource, ensure you do not specify a junction point as an exclusion or inclusion. For more information about junction points on Windows file storage resources, click the Help button on the dialog box.

5. If you want to exclude folders from replication, in the Paths field, specify folder exclusions by typing folder exclusion filters. Type a folder exclusion filter relative to the root, or source file storage resource. Filters can be relative paths or absolute paths, and filters can include wild card characters. When you specify folder exclusions, the folders you specify are excluded from migration.

listing\ or \listing\ (CIFS)listing/ or /listing/ (NFS)

Folders This example traverses the directory tree and excludes subfolders of the listing folder.

*\listing (CIFS)*/listing (NFS)

Folders Excludes subfolders named listing.

*\listing\file.txt (CIFS)*/listing/file.txt(NFS)

Files Excludes files named file.txt located in a subfolder named listing.

TABLE 26 Examples of valid file and folder exclusion filters for Phased Migration policies

Format Applied to Description

StorageX Administrator’s Guide 285

Page 304: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Phased Migration policies5

If you want to specify multiple filters, click the folder icon and then type each additional filter on its own line. For more information about specifying folder exclusions, see “Examples of valid exclusion filters for Phased Migration policies” on page 284.

6. If you want to exclude files from replication, in the Files field, specify file exclusions by typing file exclusion filters. Type a file exclusion filter relative to the root, or source file storage resource. Filters can be relative paths or absolute paths, and filters can include wild card characters. When you specify file exclusions, the files you specify are excluded from migration.

If you want to specify multiple filters, click the folder icon and then type each additional filter on its own line. For more information about specifying file exclusions, see “Examples of valid exclusion filters for Phased Migration policies” on page 284.

NOTEIf you select the replication option Delete orphaned files and folders on the destination on the General Options tab for a Phased Migration policy that contains an exclusion filter, StorageX does not copy files that match the exclusion filter and StorageX does not delete files on the destination that match the exclusion filter. For more information, click the Help button on the dialog box.

7. If you want to include folders in the replication, in the Paths field, specify folder inclusions by typing folder inclusion filters. Type a folder inclusion filter relative to the root, or source file storage resource. Filters can be relative paths or absolute paths, and filters can include wild card characters. When you specify folder inclusions, only the folders you specify are included in the migration.

If you want to specify multiple filters, click the folder icon and then type each additional filter on its own line. For more information about specifying folder inclusions, see “Examples of valid inclusion filters for Phased Migration policies” on page 282.

8. If you want to include files in the replication, in the Files field, specify file inclusions by typing file inclusion filters. Type a file inclusion filter relative to the root, or source file storage resource. Filters can be relative paths or absolute paths, and filters can include wild card characters. When you specify file inclusions, only the files you specify are included in the migration.

If you want to specify multiple filters, click the folder icon and then type each additional filter on its own line. For more information about specifying file inclusions, see “Examples of valid inclusion filters for Phased Migration policies” on page 282.

9. Click OK.

Running batch files with Phased Migration policiesIf you know how to write scripts and create batch files, you can specify that you want to run batch files during the following periods of a Phased Migration policy run:

• Before or after replication by selecting the appropriate option on the Replication Scripting tab for a Phased Migration template or policy

• In the Initial Phase by selecting the appropriate option on the Initial Phase tab for a Phased Migration template or policy

• In the Final Phase by selecting the appropriate option on the Final Phase tab for a Phased Migration template or policy

286 StorageX Administrator’s Guide

Page 305: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Phased Migration policies 5

For more information about using batch files with Phased Migration policies, including requirements for using batch files, see “Using batch files with Data Movement policies” on page 315.

To run batch files with a Phased Migration policy

1. If you created the Phased Migration policy in the Data Movement view or if an Archival Migration policy generated the policy, in the StorageX Console, click the Data Movement tab.

2. If StorageX generated the Phased Migration policy when you executed a Migration Project design, in the StorageX Console, click the Migration Projects tab.

3. In the left tree pane, browse to and right-click the Phased Migration policy where you want to run a batch file, and then click Properties.

4. If you want to run a batch file before or after replication, complete the following steps:

a. Click the Replication Scripting tab.

b. If you want to run a batch file before replication, select the Run batch file before replication check box.

c. If you want to run a batch file after scanning replication, select the Run batch file after replication check box.

NOTEIf you run a Phased Migration policy with batch files configured to run before or after replication but the replication job cannot run, StorageX still runs any replication scripting batch files configured. For example, if you run a policy with a post-replication batch file, and StorageX cannot find a valid universal data engine, StorageX runs the post-replication batch file even though the replication did not complete.

d. Type the UNC path or a local path to the batch file or click Browse to browse to and select the batch file.

If you specify a UNC path, the StorageX server service account must have Read permissions to the folder where the batch file is stored as well as Read permissions to the batch file itself.

If you specify a local path, the StorageX server service account must have Read permissions to the folder where the batch file is stored, the batch file must be stored in a local path on the StorageX server computer, and the StorageX server service account must have Read permissions to the batch file itself.

e. Click Apply.

5. If you want to run a batch file in the Initial Phase of a Phased Migration policy, complete the following steps:

a. Click the Initial Phase tab.

b. Select the Run batch file check box.

c. Type the UNC path or a local path to the batch file or click Browse to browse to and select the batch file.

If you specify a UNC path, the StorageX server service account must have Read permissions to the folder where the batch file is stored as well as Read permissions to the batch file itself.

StorageX Administrator’s Guide 287

Page 306: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Phased Migration policies5

If you specify a local path, the StorageX server service account must have Read permissions to the folder where the batch file is stored, the batch file must be stored in a local path on the StorageX server computer, and the StorageX server service account must have Read permissions to the batch file itself.

d. In the Pause after this step field, specify whether you want to always pause the policy after running the batch file or if you only want to pause the policy after running the batch file if there are errors.

e. Click Apply.

6. If you want to run a batch file in the Final Phase of a Phased Migration policy, complete the following steps:

a. Click the Final Phase tab.

b. Select the Run batch file check box.

c. Type the UNC path or a local path to the batch file or click Browse to browse to and select the batch file.

If you specify a UNC path, the StorageX server service account must have Read permissions to the folder where the batch file is stored as well as Read permissions to the batch file itself.

If you specify a local path, the StorageX server service account must have Read permissions to the folder where the batch file is stored, the batch file must be stored in a local path on the StorageX server computer, and the StorageX server service account must have Read permissions to the batch file itself.

d. In the Pause after this step field, specify whether you want to always pause the policy after running the batch file or if you only want to pause the policy after running the batch file if there are errors.

e. Click OK.

Assigning universal data engines or universal data engine groups to Phased Migration policiesYou can use universal data engine groups with Phased Migration policies to specify which universal data engine or universal data engine group you want to transfer file data. Use universal data engine groups if you want to distribute file data transfer workloads or increase the performance and availability of universal data engines when transferring data.

For more information about universal data engines and creating and managing universal data engine groups, see “Understanding StorageX universal data engines” on page 9 and “Creating and managing universal data engine groups” on page 130.

To assign a universal data engine or universal data engine group to a Phased Migration policy

1. If you created the Phased Migration policy in the Data Movement view or if an Archival Migration policy generated the policy, in the StorageX Console, click the Data Movement tab.

2. If StorageX generated the Phased Migration policy when you executed a Migration Project design, in the StorageX Console, click the Migration Projects tab.

3. In the left tree pane, browse to and right-click the Phased Migration policy where you want to assign a universal data engine or universal data engine group, and then click Properties.

288 StorageX Administrator’s Guide

Page 307: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Phased Migration policies 5

4. Click the Universal Data Engine Selection tab.

5. Specify the universal data engine or universal data engine group you want the policy to use to transfer file data by selecting the appropriate option. For more information about each option, click the Help button on the dialog box.

6. Click OK.

Processing security identifiers (SIDs) in a Phased Migration policyYou can configure your Phased Migration policies to automatically map SIDs from the source to the destination using one or more SID mapping rules. You can replace any SID in a CIFS security descriptor with any other SID and even translate SIDs across domains. SID mapping rules are configured in a SID map file for each universal data engine.

To configure SID mapping rules

1. Create a SID map file. A SID map is a text file with one SID mapping rule per line. StorageX provides a template SID map for you to get started, located in the Examples\Templates subfolder of the installation folder. For example, C:\Program Files\Data Dynamics\StorageX\Examples\Templates.

Each line in the text file must be a different SID mapping rule in the following format: [SrcSID]:[DstSID] where SrcSID and DstSID are SIDs in string form.

Example

[S-1-5-21-122983-421665-67978-1000]:[S-1-5-21-333614-246723-113026-1106]

NOTEFor each line in the SID map, anything after the closing ‘]’ is ignored. You can use this space to add comments.

2. If you want to remove SIDs on the destination, leave DstSID empty for the SID mapping rule.

Example

[S-1-5-21-122983-421665-67978-1000]:[]

NOTEOwner and group SIDs cannot be removed. If you configure the mapping rule to remove an owner or group SID, it will instead be replaced with the SID for local administrators group.

3. Name the SID map file StorageXSidMap.txt and copy it to the following folder on the universal data engine assigned to your Phased Migration policy: C:\ProgramData\Data Dynamics\StorageX\ReplicationAgent\

NOTETo ensure consistent results, you must copy the same SID map file to each universal data engine in a data engine group.

4. Restart the universal data engine service.

5. If you want to use the SID map defined above when running a Phased Migration policy, click the Use SID mapping rules defined on the universal data engine check box in the CIFS Security Replication tab in your Phased Migration policy’s properties dialog box.

StorageX Administrator’s Guide 289

Page 308: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Phased Migration policies5

Changing the template specified for a Phased Migration policyThe default settings for each Phased Migration policy in the Data Movement view are defined by the Phased Migration template specified either when you created the Phased Migration policy or when an Archival Migration policy generated the Phased Migration policy. However, you can change the Phased Migration template specified for a Phased Migration policy in the Data Movement view at any time.

When you change the template specified for a Phased Migration policy in the Data Movement view, the Phased Migration policy inherits settings from the new template. The Phased Migration policy no longer inherits settings from the previous template. However, you can still override template settings in the policy itself.

The default settings for each Phased Migration policy in the Migration Projects view are defined by the settings specified in the Migration Project Phased Migration template in the Migration Projects view. There is only one Phase Migration template, the Migration Project Phased Migration template, in the Migration Projects view. You cannot change the template specified for Phased Migration policies in the Migration Projects view to a different template. When you change the settings specified in the Migration Project Phased Migration template, any existing Phased Migration policies in the Migration Project view inherit the updated settings from the template. However, you can still override template settings in the policy itself.

For more information about templates, see “Understanding Phased Migration and Archival Migration templates” on page 229 and “Understanding Migration Project Phased Migration templates” on page 328.

To change the template specified for a Phased Migration policy

1. In the StorageX Console, click the Data Movement tab.

2. If you want to view or change the Phased Migration template used by StorageX for Phased Migration policies generated from an Archival Migration policy, complete the following steps:

a. In the left tree pane, browse to and right-click the Archival Migration policy that generated the Phased Migration policy, and then click Properties.

b. Click the Migration Template tab.

c. Review the current Phased Migration template specified, and if appropriate, select a different Phased Migration template from the list.

d. Click OK.

3. If you want to view or change the Phased Migration template associated with a specific Phased Migration policy, complete the following steps:

a. In the tree pane, browse to and right-click a Phased Migration policy, and then click Properties.

b. In the left pane, under Template Options, click Manage template inheritance.

c. Review the current Phased Migration template specified, and if appropriate, select a different Phased Migration template from the list.

d. Click OK.

290 StorageX Administrator’s Guide

Page 309: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Phased Migration policies 5

Viewing and managing default settings for Phased Migration policiesIf you are working in the Data Movement view, the base options defined for a Phased Migration policy are based on the Phased Migration template specified either when you created the Phased Migration policy or when an Archival Migration policy generated the Phased Migration policy.

If you are working in the Migration Projects view, the base options defined for a Phased Migration policy are based on the options specified in the Migration Project Phased Migration template at the time when StorageX executed the Migration Project design and generated Phased Migration policies.

Although you cannot manage default settings for Phased Migration policies in the Migration Projects view, you can manage default settings for Phased Migration policies in the Data Movement view.

In the Data Movement view, you can view which Phased Migration options were changed from the defaults specified in the template associated with the policy. You can also reset all settings in the policy back to the default template settings. For more information about templates, see “Understanding Phased Migration and Archival Migration templates” on page 229 and “Understanding Migration Project Phased Migration templates” on page 328.

To view and manage default settings for Phased Migration policies

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and right-click a Phased Migration policy, and then click Properties.

3. In the left pane, under Template Options, click Highlight settings that differ from the defaults to view which settings have been changed in the policy. If any default settings have been changed, the name of the affected dialog box in the left pane and the changed fields in that dialog box are displayed in bold font.

4. If you want to remove the highlighting, in the left pane, under Template Options, click Remove highlighting from changed settings.

5. If you want to reset all settings in the policy back to the default template settings, in the left pane, under Template Options, click Reset settings to their defaults.

6. Click OK.

Renaming Phased Migration policiesYou can rename Phased Migration policies any time. For example, you might need to rename your Phased Migration policies to conform to new corporate standards. Renaming a Phased Migration policy does not affect the policy in any other way.

In addition to using naming standards for your Phased Migration policies, you can group them into folders to organize them. For more information, see “Creating custom folders for Data Movement Phased Migration policies” on page 292.

To rename a Phased Migration policy

1. If you created the Phased Migration policy in the Data Movement view or if an Archival Migration policy generated the policy, in the StorageX Console, click the Data Movement tab.

2. If StorageX generated the Phased Migration policy when you executed a Migration Project design, in the StorageX Console, click the Migration Projects tab.

StorageX Administrator’s Guide 291

Page 310: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Phased Migration policies5

3. In the left tree pane, browse to and right-click a Phased Migration policy, and then click Rename.

4. Type a new name for the policy and press the Enter key.

Creating custom folders for Data Movement Phased Migration policiesYou can create custom folders to help you organize Phased Migration policies. However, the method you can use to organize your Phased Migration policies varies based on whether you are working in the Data Movement view or in the Migration Projects view.

If you are working in the Data Movement view, in the left tree pane, each Phased Migration policy displays under its associated template, regardless of the folder structure you use to organize your policies. If you created the Phased Migration policy by right-clicking the My Policies folder and then clicking New > Phased Migration Policy, the new Phased Migration policy displays under both the Phased Migration template used when creating the new Phased Migration policy, as well as under the My Policies folder.

In the Data Movement view, you can create custom folders at any time under My Policies to help you logically organize your Phased Migration policies as needed, and then cut and paste Phased Migration policies into appropriate folders as needed. Organizing Phased Migration policies in custom folders does not affect the policies in any other way.

If you are working in the Migration Projects view, you must create custom folders for Migration Project Phased Migration policies in the Migration Projects view. You then specify the custom folder that you want to store Phased Migration policies in when you execute the Migration Project design. For more information about creating custom folders in the Migration Projects view, see “Creating custom folders for Migration Project Phased Migration policies” on page 362.

To create custom folders for Data Movement Phased Migration policies

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, right-click My Policies and click New > Folder.

3. Type a name for the Phased Migration policy folder and press Enter.

4. Repeat step 2 and step 3 to create additional folders.

5. Copy and paste Phased Migration policies into the Phased Migration policy folders you created.

Viewing Phased Migration policies scheduled to run in the futureYou can view Phased Migration policies that are scheduled to run in the future on the Schedules tab.

Viewing Phased Migration policies that are scheduled to run in the future can help you understand what file data migration tasks will be occurring in the future.

It can also help you identify appropriate maintenance windows for the StorageX server computer as needed. For example, it can be helpful to know what Phased Migration policies are scheduled to run in the future if you need to temporarily take the StorageX server computer offline to apply patches or to perform other maintenance activities on the computer.

292 StorageX Administrator’s Guide

Page 311: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Phased Migration policies 5

To view Phased Migration policies scheduled to run in the future

1. In the StorageX Console, click the Schedules tab.

2. Specify a date range to view in the From and To fields, and then click Go.

3. In the Description column, review the list of scheduled tasks and look for items with the following description:

Running Migration Policy PhasedMigrationPolicyName, where PhasedMigrationPolicyName is the name of a Phased Migration policy.

4. If you want to prevent a Phased Migration policy scheduled to run in the future from running, complete the following steps:

a. Note the name of each Phased Migration policy you want to prevent from running in the future displayed on the Schedules tab.

b. If the Phased Migration policy was created in the Data Movement view or if an Archival Migration policy generated the policy, click the Data Movement tab.

c. If StorageX generated the Phased Migration policy when executing a Migration Project design, in the StorageX Console, click the Migration Projects tab.

d. In the left tree pane, browse to the Phased Migration policy you want to prevent from running in the future.

e. Right-click the Phased Migration policy, and then click Properties.

f. On the Migration Schedule tab, clear the Use migration schedule check box.

g. Click OK.

For more information about viewing Archival Migration policies that are scheduled to run in the future, see “Viewing Archival Migration policies scheduled to run in the future” on page 312.

Deleting Phased Migration policiesYou can delete a Phased Migration policy if you no longer want to use the policy in your environment. To actually delete a policy, you must delete it from under its template in the left tree pane. Removing a policy from the My Policies folder in the left tree pane does not actually delete the policy.

When you delete a Phased Migration policy, StorageX also deletes any alerts, events, tasks, or details associated with the policy. If you want to retain any information about a Phased Migration policy run, ensure you export the information in the policy manifest before deleting the policy. For more information about exporting detailed policy manifest information, see “Verifying Phased Migration policies completed successfully” on page 271.

NOTEIf you delete a Phased Migration policy while that policy is running, and the policy was generated by a Migration Project design that uses SnapMirror replication, you must manually quiesce and delete the SnapMirror on both the source and destination resources and delete the partially-migrated volume on the destination resource. For more information about deleting SnapMirrors, see “Deleting SnapMirrors from StorageX for Data ONTAP file storage resources” on page 157. For more information about using SnapMirror replication for Migration Project designs, see “Understanding using SnapMirror replication for Migration Projects” on page 330.

StorageX Administrator’s Guide 293

Page 312: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Archival Migration policies5

To delete a Phased Migration policy

1. If you created the Phased Migration policy in the Data Movement view or if an Archival Migration policy generated the policy, in the StorageX Console, click the Data Movement tab.

2. If StorageX generated the Phased Migration policy when you executed a Migration Project design, in the StorageX Console, click the Migration Projects tab.

3. In the left tree pane, locate the policy you want to delete under the template with which it is associated.

4. Right-click the policy and click Delete.

5. Click Yes.

Creating Archival Migration policiesCreate Archival Migration policies to scan resources and generate Phased Migration policies you can run, or a list of migration candidates you can review. You configure the Archival Migration policy with the criteria you want to use to select folders to migrate.

If you use DFS namespaces or automount map files, when you migrate sources, StorageX automatically updates the DFS namespace or automount map files to reference the data at the new location. For more information, see “How StorageX manages data access in CIFS environments with DFS namespaces” on page 242 and “How StorageX manages data access in NFS environments with automount map files” on page 245.

The first time you create an Archival Migration policy, use the New Archival Migration Policy Wizard. Once you have created Archival Migration policies, you can either use the Wizard or copy existing policies and modify them as needed. For more information, see “Creating new Archival Migration policies” on page 294 and “Copying an existing Archival Migration policy” on page 296.

In an Archival Migration policy, you can have multiple source and destination pairs. Each source must be either a physical path or, if you have implement DFS namespaces in your environment, a source can be a physical path or a DFS link with a single link target. The destination must be a physical path.

In StorageX, a physical path is a path directly to the file storage resource. For example, a physical path is the UNC path \\FileStorageResource\ShareName, where FileStorageResource is the actual name of the file storage resource. If the file storage resource is a virtual file storage resource, or if the file storage resource has its own virtualization layer, the physical path is the UNC path to the resource.

Creating new Archival Migration policiesUse the New Archival Migration Policy Wizard to create your first Archival Migration policy. Once you have created a policy, you can either use the wizard to create additional Archival Migration policies or you can copy an existing Archival Migration policy and then modify it as needed. For more information, see “Copying an existing Archival Migration policy” on page 296.

To create a new Archival Migration policy

1. In the StorageX Console, click the Data Movement tab.

2. If you know which Archival Migration template you want to use for the policy, in the left tree pane, browse to and right-click the template, and then click New > Archival Migration Policy.

294 StorageX Administrator’s Guide

Page 313: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Archival Migration policies 5

3. If you do not know which Archival Migration template you want to use for the policy, in the tree pane, right-click My Policies and click New > Archival Migration Policy.

4. Review the welcome message, and then click Next.

5. Specify a unique name and description to identify the policy. The name is displayed in the tree pane under My Policies and under the name of the template you specify for the policy.

6. Click Next.

7. If you did not already specify an Archival Migration template for the policy, select a template from the list of available templates. The policy inherits base settings from the template, but you can make changes later if necessary.

8. Click Next.

9. Specify whether you want to use scan paths and migration criteria or a batch file to generate Phased Migration policies. For more information about using batch files with Archival Migration policies, see “Running batch files with Archival Migration policies” on page 308.

10. Click Next.

11. If you are using scan paths and migration criteria to generate Phased Migration policies, type the UNC path of the source and destination, or click Browse to browse to and select the path.

The source search path must be either a physical path or a DFS link with a single link target. The destination must by a physical path.

In StorageX, a physical path is a path directly to the file storage resource. For example, a physical path is the UNC path \\FileStorageResource\ShareName, where FileStorageResource is the actual name of the file storage resource. If the file storage resource is a virtual file storage resource, or if the file storage resource has its own virtualization layer, the physical path is the UNC path to the resource.

If you have not implemented DFS namespaces in your environment, specify a physical path as the source search path.

If you have implemented DFS namespaces in your environment, specify either a physical path or a DFS link with a single link target as your source search path.

NOTEYou can only specify a DFS link with a single link target as a scan path in an Archival Migration policy. If you specify a DFS link with more then one link target as a scan path in an Archival Migration policy, the Archival Migration policy ignores the DFS link with multiple targets. The Archival Migration policy does not evaluate DFS links with multiple targets when they are specified as a search path or attempt to identify any migration candidates for a DFS link with multiple targets.

12. Click Next.

13. If you are using a batch file to generate Phased Migration policies, type the UNC path or a local path to the batch file or click Browse to browse to and select the batch file.

If you specify a UNC path, the StorageX server service account must have Read permissions to the folder where the batch file is stored as well as Read permissions to the batch file itself.

If you specify a local path, the StorageX server service account must have Read permissions to the folder where the batch file is stored, the batch file must be stored in a local path on the StorageX server computer, and the StorageX server service account must have Read permissions to the batch file itself.

StorageX Administrator’s Guide 295

Page 314: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Running Archival Migration policies immediately5

Running a batch file instead of using migration criteria bypasses the scanning process and automatically creates Phased Migration policies.

For more information about using batch files, see “Using batch files with Data Movement policies” on page 315 and “Running batch files with Archival Migration policies” on page 308.

14. Click Next.

15. On the New Archival Migration Policy Summary dialog box, verify the settings you specified for the new Archival Migration policy, and then click Finish.

Once you have created the new Archival Migration policy, you can specify additional properties and actions for the policy. For more information, see “Managing Archival Migration policies” on page 301. You can also run the policy as needed or on a schedule you configure. For more information, see “Immediately scanning for folders to migrate” on page 302 and “Scheduling scanning for folders to migrate” on page 302.

Copying an existing Archival Migration policyUse the New Archival Migration Policy Wizard to create your first Archival Migration policy. For more information, see “Creating new Archival Migration policies” on page 294. Once you have created a policy, you can either use the wizard or you can copy an existing Archival Migration policy and then modify it as needed to create a new Archival Migration policy.

To copy an existing Archival Migration policy

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and right-click the Archival Migration policy you want to copy and then click Copy.

3. Browse to the location where you want to paste the Archival Migration policy, and then click Paste.

StorageX displays the new policy in the tree pane with the default name Copy of ArchivalMigrationPolicyName, where ArchivalMigrationPolicyName is the name of the original policy.

4. In the left tree pane, right-click the new Archival Migration policy and click Properties.

5. In the Name and Description fields, type a new name and description for the Archival Migration policy.

6. In the left pane of the Migration Properties dialog box, click each tab, review the current properties in the right pane, and modify other policy settings as needed.

7. Click OK.

Once you have created a new Archival Migration policy, you can run the policy and specify additional settings and actions for the policy. For more information, see “Managing Archival Migration policies” on page 301.

Running Archival Migration policies immediatelyOnce you have created an Archival Migration policy, you can wait for the policy to run on the default schedule specified for the policy on the Policy Scan Schedule tab, or you can choose to run the policy immediately.

296 StorageX Administrator’s Guide

Page 315: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Scheduling Archival Migration policies 5

This topic explains how to run Archival Migration policies immediately.

For more information about scheduling Archival Migration policies, see “Scheduling Archival Migration policies” on page 297. For more information about using the New Archival Migration Policy Wizard to create Archival Migration policies, see “Creating new Archival Migration policies” on page 294.

To run an Archival Migration policy immediately

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and select the Archival Migration policy you want to run, and then in the right pane, review the policy summary information.

3. In the left tree pane, right-click the policy and then click Properties.

4. Click each tab and verify that the policy is configured with the appropriate settings, and then click OK.

For more information about the settings on each tab, click the Help button on the dialog box.

5. In the left tree pane, right-click the Archival Migration policy and then click Run.

6. If the Run option is not available, this means that the policy was run previously. To restart the policy again, click Policy Actions, and then select the appropriate policy action to restart the policy. For more information about restarting a policy, see “Restarting Archival Migration policies” on page 298.

After you run Archival Migration policies, verify that the policies completed successfully. For more information, see “Verifying Archival Migration policies completed successfully” on page 299.

Scheduling Archival Migration policiesThe Archival Migration template associated with an Archival Migration policy includes base settings that determine when the policy runs by default. However, you can override these settings and configure a one-time or recurring schedule as needed to meet your requirements. You can also run an Archival Migration policy immediately.

This topic explains how to schedule Archival Migration policies.

For more information about running Archival Migration policies immediately, see “Running Archival Migration policies immediately” on page 296.

For more information about using the New Archival Migration Policy Wizard to create Archival Migration policies, see “Creating new Archival Migration policies” on page 294.

To schedule an Archival Migration policy

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and select the Archival Migration policy you want to schedule, and then click Properties.

3. Click the Policy Scan Schedule tab.

4. Select the Use policy scan schedule check box.

5. If you want to create a new schedule, click New and configure a new schedule.

StorageX Administrator’s Guide 297

Page 316: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Canceling Archival Migration policies5

6. If you want to modify an existing schedule, select the schedule from the list and modify it as needed.

7. If you want to delete a schedule, select the schedule from the list and click Delete.

8. Click OK.

Canceling Archival Migration policiesYou can view running Archival Migration policies on the Tasks tab. The Tasks tab displays at the bottom of the StorageX Console.

If you start to run an Archival Migration policy and need to stop it before the policy completes, you can cancel the policy and restart it later.

To cancel an Archival Migration policy

1. In the StorageX Console, click the Data Movement tab.

2. If you want to cancel the Archival Migration policy while viewing the running Archival Migration policy on the Tasks tab, right-click the running Archival Migration policy, and then click Cancel.

3. If you want to cancel the running Archival Migration policy from the tree view, in the left tree pane, right-click the running Archival Migration policy you want to cancel, and then click Cancel.

For more information about restarting a canceled Archival Migration policy, see “Restarting Archival Migration policies” on page 298.

Restarting Archival Migration policiesIf you cancel an Archival Migration policy before the policy completes, you can restart the policy later.

When you restart an Archival Migration policy, StorageX continues the policy run from the point at which it was canceled.

This topic explains how to restart an Archival Migration policy. For more information about canceling an Archival Migration policy, see “Canceling Archival Migration policies” on page 298.

To restart an Archival Migration policy

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and select the Archival Migration policy you want to restart.

3. If you want to see how much of the policy completed previously before you restart it, in the center pane, review the information in the Status and Migration Candidates areas. For more information about the information provided in these areas, see “Verifying Archival Migration policies completed successfully” on page 299.

You can also obtain more information about the Archival Migration policy run by viewing the policy manifest associated with the policy run in the Alerts or Events tab in the StorageX Console.

298 StorageX Administrator’s Guide

Page 317: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying Archival Migration policies completed successfully 5

If you want to view information about any alerts StorageX generated when the policy ran, on the Alerts tab, double-click each alert associated with the Archival Migration policy run to view alert details in the policy manifest.

If you want to view information about any events StorageX generated when the policy ran, on the Events tab, double-click each event associated with the Archival Migration policy run, and then click Details to view event details about the policy run in the policy manifest.

4. If the Archival Migration policy stopped because of an error, on the Alerts or Events tab, double-click the alert or event generated during the last run of the policy to obtain detailed information about the error and then address the error. The alert and event details provided in the policy manifest for an alert or event provides detailed information about any problems with specific scan paths, such as if there was a problem scanning the path or if access to the path was denied.

Alert and event details can also help you obtain the following additional information about any errors:

• If the policy uses a batch file to identify migration candidates, you can see if there were any problems running the batch file. For example, you can see if the policy was unable to run the script, if StorageX cannot find the output file for the script, if the results in the output file are malformed, or if there are invalid source and destination paths in the results in the output file.

• If the source is a DFS link, you can see additional details about any issues with the DFS link, such as whether StorageX was able to enumerate the DFS link, if the DFS link has more than on DFS link target, if the DFS link target points to another DFS link, or if the DFS server is no longer running.

You can see whether StorageX was able to enumerate the DFS link target, or if the DFS link target refers to either a file storage resource that StorageX cannot communicate with or the path specified in the DFS link target no longer exists.

You an also see if the DFS link target already refers to the scan destination. If the DFS link target already points to the scan destination, this means that a previous Archival Migration policy run already identified the DFS link as a migration candidate and a Phased Migration policy has already moved the data to the scan destination.

5. Restart the policy by right-clicking the Archival Migration policy and then clicking Run.

Verifying Archival Migration policies completed successfullyOnce you run an Archival Migration policy, you can view policy status information and the policy manifest to verify that the Archival Migration policy completed successfully. The policy manifest provides detailed information about the last run of the Archival Migration policy.

Policy manifest information in the Alerts and Events views can help you verify whether a policy completed successfully and troubleshoot issues. The Events view is a complete historical listing of events. StorageX appends new events to the list in the Events view every time you run a policy. The Alerts view provides information for only the latest run of a policy. Every time you run a policy, StorageX deletes the alerts from the previous run.

You can export policy manifests and alert and event details and save them as reports in *.tsv format. This information can be useful not only for auditing purposes, but also for regulatory compliance purposes.

StorageX Administrator’s Guide 299

Page 318: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying Archival Migration policies completed successfully5

If you used a batch file in an Archival Migration policy and the policy did not complete successfully, ensure you met requirements for using batch files. For more information, see “Using batch files with Data Movement policies” on page 315.

To verify an Archival Migration policy completed successfully

1. Open the StorageX Console.

2. Click the Data Movement tab.

3. In the left tree pane, browse to and select the Archival Migration policy you want to verify.

4. In the center pane, review the following information in the Status area:

If the policy has never been run before, Unknown status displays.

If the policy is still in progress, In Progress displays.

If the policy completed successfully, Completed successfully displays.

If the policy completed with errors, Completed with errors displays. Address the cause of the error and then restart the policy. To see the cause of the error, click the Alerts tab and then double-click the error message to open the policy manifest. The policy manifest provides additional details about the cause of the error.

If the policy completed with warnings, Completed with warnings displays. Address the cause of the warning and then restart the policy. To see the cause of the warning, click the Alerts tab and then double-click the warning message to open the policy manifest. The policy manifest provides additional details about the cause of the warning.

If the policy was canceled, Canceled displays. To restart the policy, right-click the policy and then click Run.

If you specified that you wanted to use a batch file before an Archival Migration policy scan on the General Options tab or if you specified that you wanted to use a batch file to identify folders for migration on the Policy Creation Criteria tab and one of the following issues occurs, Invalid configuration displays:

• The batch file you specified is missing or not accessible.

• One of the parameters specified in batch files is the location of the output file, and StorageX is unable to find the output file.

• The format of the output file is not correct. StorageX requires an output file in XML format, but the output file is not in XML format or the XML is malformed.

• Content is missing from the output file. For example, the output file specifies a source, but does not specify a corresponding destination.

5. If you want to see all of the events generated during a policy run, click the Events view to see events associated with the execution of the policy.

6. If you want to view all the details for a particular event, complete the following steps:

a. Double-click the event in the Events view to open the Event Viewer dialog box.

b. Click Details to view event details.

c. If you want to save the event details to a report, in the Event Details dialog box, click Export. In the Specify Report Options dialog box, you can specify a file name and the location where you want to save the report. For more information, click the Help button on the dialog box.

300 StorageX Administrator’s Guide

Page 319: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Archival Migration policies 5

7. If you want to check for any errors or warnings generated during a policy run, click the Alerts view.

8. If you want to view all the details for a particular alert, complete the following steps:

a. Double-click the alert in the Alerts view to open the Alert Details dialog box.

b. If you want to save the alert details to a report, in the Alert Details dialog box, click Export. In the Specify Report Options dialog box, you can specify a file name and the location where you want to save the report. For more information, click the Help button on the dialog box.

9. If the policy completed successfully and you specified that you did not want the policy to automatically generate Phased Migration policies for migration candidates, you can see the list of migration candidates identified by the policy in the center pane in the Migration Candidates area.

NOTEArchival Migration policies generate Phased Migration policies for migration candidates when the Automatically generate Migration policies for migration candidates check box on the Task Options tab for the policy is selected. If this check box is cleared, the Archival Migration policy only identifies a list of migration candidates. You can then choose which migration candidates you want to create Phased Migration policies for by selecting a migration candidate and then clicking Create Policy.

If you do not see all of the migration candidates you expected, click the Alerts tab and view the policy manifest. The policy manifest provides additional details about why folders were included or excluded as migration candidates.

10. If the policy completed successfully and you specified that you wanted the policy to automatically generate Phased Migration policies for migration candidates, you will not see any migration candidates displayed in the Migration Candidates area. However, you can see a list of the Phased Migration policies the Archival Migration policy generated by clicking on the Alerts tab and viewing the policy manifest. The policy manifest provides additional details about each Phased Migration policy the Archival Migration policy generated.

Archival Migration policies generate Phased Migration policies for migration candidates when the Automatically generate Migration policies for migration candidates check box on the Task Options tab for the policy is selected.

Managing Archival Migration policiesThis section explains how to manage Archival Migration policies. For more information about creating Archival Migration policies, see “Creating Archival Migration policies” on page 294.

The following topics provide more information about managing Archival Migration policies:

• “Modifying Archival Migration policy properties” on page 302

• “Immediately scanning for folders to migrate” on page 302

• “Scheduling scanning for folders to migrate” on page 302

• “Viewing and managing migration candidates” on page 303

• “Specifying migration criteria for Archival Migration policies” on page 304

• “Specifying folder exclusion and inclusion filters for Archival Migration policies” on page 305

StorageX Administrator’s Guide 301

Page 320: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Archival Migration policies5

• “Creating batch files for Archival Migration policies” on page 306

• “Running batch files with Archival Migration policies” on page 308

• “Specifying post-scanning options for Archival Migration policies” on page 310

• “Managing Archival Migration template inheritance” on page 311

• “Managing default settings in Archival Migration policies” on page 311

• “Renaming Archival Migration policies” on page 312

• “Organizing Archival Migration policies” on page 312

• “Viewing Archival Migration policies scheduled to run in the future” on page 312

• “Deleting Archival Migration policies” on page 313

Modifying Archival Migration policy propertiesYou can modify the properties of an Archival Migration policy at any time to meet your requirements.

To modify the properties of an Archival Migration policy

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, right-click an Archival Migration policy and click Properties.

3. In the left pane, click the tab for the item that you want to modify, and then specify new settings in the right pane. For more information about each setting, click the Help button on the dialog box.

4. Click OK.

Immediately scanning for folders to migrateOnce you have set up an Archival Migration policy, you can set a schedule for the policy to run, or you can immediately scan for folders that match the migration criteria of the policy. For more information about scheduling Archival Migration policy scans, see “Scheduling scanning for folders to migrate” on page 302. By default, the Archival Migration policy displays a list of Phased Migration policies.

To scan for data immediately

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and right-click an Archival Migration policy, and then click Run.

You can view results of the scanning operation in the Alerts and Events views. For more information, see “Scheduling scanning for folders to migrate” on page 302.

After the scan completes, you can view a list of migration candidates when by clicking the Archival Migration policy in the left tree pane and then view the list of migration candidates displayed in the center pane under Migration Candidates.

Scheduling scanning for folders to migrateYou can schedule Archival Migration policies to automatically scan for folders that match specified criteria and display a list of migration candidates when scanning completes.

302 StorageX Administrator’s Guide

Page 321: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Archival Migration policies 5

NOTEEven if you configure a schedule for an Archival Migration policy, you can choose to override the schedule and run the policy scan immediately. For more information, see “Immediately scanning for folders to migrate” on page 302.

To schedule scanning for folders to migrate

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and right-click the Archival Migration policy for which you want to schedule scanning, and then click Properties.

3. In the left pane, click the Policy Scan Schedule tab.

4. Select the Use policy scan schedule check box.

5. If you want to create a new schedule, click New and configure a new schedule.

6. If you want to modify an existing schedule, select the schedule from the list and modify it as needed.

7. If you want to delete a schedule, select the schedule from the list and click Delete.

8. Click OK.

If the Archival Migration policy does not find any migration candidates when it scans folders, running the policy does not affect the contents of the folders.

Viewing and managing migration candidatesIf you selected the Archival Migration policy option to generate migration candidates, when the Archival Migration policy runs, the policy processes the scan paths you specified in the policy and generates a list of migration candidates that you can view and manage. For example, you can view the source and destination of a migration candidate, as well as other properties of the candidate. The display of some properties depends on policy options you selected, such as size and size on disk.

Each time an Archival Migration policy runs, it identifies a list of migration candidates. For example, assume you run an Archival Migration policy on Monday, and the Archival Migration policy generates a list of migration candidates. Next, assume you run the same Archival Migration policy again on Wednesday. When the Archival Migration policy runs again on Wednesday, the Archival Migration policy clears out the list of migration candidates from Monday, and then generates a new list of migration candidates based on the latest run of the policy on Wednesday.

After an Archival Migration policy runs, you can specify whether you want to exclude a migration candidate from the list of migration candidates. You can also specify that you want to create a Phased Migration policy for a migration candidate.

If you want to exclude a migration candidate identified by an Archival Migration policy from the list of migration candidates, select the migration candidate you want to exclude and then click Exclude. Once you exclude a migration candidate identified by an Archival Migration policy, if the Archival Migration policy runs again, the Archival Migration policy will recognize that you previously excluded the migration candidate. The migration candidate you excluded will continue to be excluded as a migration candidate during subsequent policy runs and will not display on the list of migration candidates generated during subsequent policy runs.

StorageX Administrator’s Guide 303

Page 322: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Archival Migration policies5

If you create a Phased Migration policy for a migration candidate identified by an Archival Migration policy, the next time the Archival Migration policy runs, the Archival Migration policy will recognize that a Phased Migration policy already exists for the migration candidate. Migration candidates that already have Phased Migration policies created for them are automatically excluded as migration candidates during subsequent runs of the policy and StorageX does not display those candidates on the list of migration candidates generated during subsequent runs of the policy.

If you delete a Phased Migration policy that you created for a migration candidate, the next time the Archival Migration policy runs, it will identify that a Phased Migration policy no longer exists for the migration candidate. Since the migration candidate no longer has a Phased Migration policy associated with it, the migration candidate will once again display on the list of migration candidates during subsequent policy runs.

If you do not want to view and manage a list of migration candidates, you can configure Archival Migration policies to generate Phased Migration policies for migration candidates automatically. For more information, see “Specifying post-scanning options for Archival Migration policies” on page 310.

To view and manage migration candidates

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and select an Archival Migration policy. The list of migration candidates displays in the center pane under Migration Candidates.

3. If you want to create a Phased Migration policy for one or more migration candidates, in the center pane under Migration Candidates, select the appropriate migration candidates and then click Create Policy.

StorageX creates Phased Migration policies for the migration candidates. The Phased Migration policies for migration candidates display in the left tree pane under the Phased Migration template associated with the Archival Migration policy.

4. If you want to exclude a migration candidate from migration, in the content pane under Migration Candidates, select a migration candidate and then click Exclude.

Specifying migration criteria for Archival Migration policiesArchival Migration policies allow you to specify migration criteria that determine whether a folder should be migrated. You can configure the criteria provided by StorageX, or you can specify your own criteria. You can migrate all folders found or search for folders that match the criteria you specify.

To specify migration criteria for an Archival Migration policy

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and right-click the Archival Migration policy for which you want to specify migration criteria, and then click Properties.

3. In the left pane, click the Migration Criteria tab.

304 StorageX Administrator’s Guide

Page 323: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Archival Migration policies 5

4. If you want to migrate all of the folders found in the specified source path, click Always migrate folders. This option enables you to migrate folders without using migration criteria. StorageX calculates the folder size or size on disk and displays this data for each folder. Calculating this data might take time, depending on the size of the folder. Network traffic is generated as StorageX gathers the information.

5. If you want to search for and migrate folders that match criteria you specify, click Migrate a folder when it meets any of the selected conditions. When you specify multiple items, the items are connected with “OR” Boolean logic. You can migrate folders using one or more of the following options:

• % or more of its files have not been accessed within the past - Migrate folders when a specified percentage of the files in the folders have not been accessed within a specified time.

• % or more of its files have not been modified within the past - Migrate folders when a specified percentage of the files in the folders have not been modified within a specified time.

• % or more of its files have not been created within the past - Migrate folders when a specified percentage of the files in the folders have not been created within a specified time.

• The folder is more than [x] old- Migrate folders that have reached a specified age.

• The folder size or size on disk is greater than [x] MB - Migrate folders whose size or size on disk is greater than a specified size.

• The folder contains more than [x] files - Migrate folders that contain more than a specified number of files.

• The folder is confirmed for migration by the following batch file - Migrate a folder based on the criteria in the specified batch file.

For more information about batch files, see “Using batch files with Data Movement policies” on page 315 and “Running batch files with Archival Migration policies” on page 308.

6. Click Apply.

Specifying folder exclusion and inclusion filters for Archival Migration policiesYou can create folder inclusion and exclusion filters on the General Options tab of an Archival Migration policy to specify which folders you want to explicitly include or exclude from the paths that an Archival Migration policy scans.

Folder inclusion filters do not follow the same filters as exclusions.

If a folder meets an exclusion filter and is excluded, then the Archival Migration policy ignores everything underneath the folder.

If a folder does not meet an inclusion filter, the Archival Migration policy will still go into the folder to see if any subfolders meet the inclusion criteria.

Archival Migration policies process exclusion filters first, and then they process inclusion filters.

Inclusion and exclusion filters increase processing time and may impact performance.

StorageX Administrator’s Guide 305

Page 324: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Archival Migration policies5

After a migration candidate displays in the exclusion list, you cannot include it as a candidate by adding it to an inclusion list. You must first remove the candidate from the exclusion list. For more information about managing migration candidates, see “Viewing and managing migration candidates” on page 303.

The following table provides a list of valid folder exclusion and inclusion filters for Archival Migration policies and includes an explanation for each filter.

To specify folder exclusion and inclusion filters for Archival Migration policies

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and right-click the Archival Migration policy where you want to create folder exclusion and inclusion filters, and then click Properties.

3. In the left pane, click the General Options tab.

4. If you want to exclude folders from scanning, in the Exclude field, type folder exclusion filters delimited by double quotes, or click Expand to specify multiple folder exclusion filters. The folder exclusion filters can include DOS wild card characters such as asterisks (*) or question marks (?).

5. If you want to include folders in the scan, in the Include field, type folder inclusion filters delimited by double quotes, or click Expand to specify multiple folder inclusion filters. The folder exclusion filters can include DOS wild card characters such as asterisks (*) or question marks (?).

6. Click OK.

Creating batch files for Archival Migration policiesThe following topics provide additional information you can use to create batch files to use with Archival Migration policies:

• “PreScan sample Archival Migration policy script” on page 307

• “Criteria sample Archival Migration policy script” on page 307

• “MigrationCreation sample Archival Migration policy script” on page 308

TABLE 27 Valid folder exclusion and inclusion filters for Archival Migration policies

Item filter Description

1 * Match everything

2 *exp* Match any path containing the string “exp”

3 Listing??? Match folders whose name begins with “Listing” followed by three characters

4 G* Match folders whose name begins with “G”

5 “G*” “L*” Match folders whose name begins with “G” and folders whose name begins with “L”

6 \\server\directory\folder (CIFS)server:/root/directory (NFS)

Include/exclude absolute path

306 StorageX Administrator’s Guide

Page 325: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Archival Migration policies 5

PreScan sample Archival Migration policy script

The PreScan sample Archival Migration policy script is an example of the type of script you can specify on the General Options tab for an Archival Migration policy or an Archival Migration policy template. You specify that you want to run a batch file before you run an Archival Migration policy scan by selecting the Run batch file before scan check box.

When you specify that you want to run a batch file before an Archival Migration policy scan, StorageX performs the following actions:

1. StorageX uses the source and destination pairs specified in the output file from the batch file as the list of scan paths.

2. StorageX evaluates the combined list of scan paths against the migration criteria you specified on the Migration Criteria tab.

3. After StorageX completes its evaluation, StorageX performs one of the following actions:

• If you selected the Automatically generate Migration policies for migration candidates option on the Task Options tab, StorageX automatically creates a Phased Migration policy for each migration candidate.

• If you cleared the Automatically generate Migration policies for migration candidates option on the Task Options tab, StorageX displays a list of migration candidates in the center pane under Migration Candidates when you select an Archival Migration policy. You can then manually create a Phase Migration policy for each migration candidate by selecting the candidate and then clicking Create Policy.

StorageX provides a sample PreScan script and batch files you can view and modify in the \StorageX\Examples\Scripts\Archival folder on the computer where you installed the StorageX server.

Argument

1. Policy name

2. Local path to a file to which the script can output a list of scan paths. The local path is an absolute path to a file in the system temp directory.

3. First user argument

Exit codes

Criteria sample Archival Migration policy script

The Criteria sample Archival Migration policy script is an example of the type of script you can specify on the Migration Criteria tab for an Archival Migration policy or an Archival Migration policy template.

You specify that you want to run a batch file to confirm folders for migration by selecting the The folder is confirmed for migration by the following batch file check box.

When you specify that you want to use a batch file to confirm folders for migration, as StorageX evaluates the source and destination pairs to identify migration candidates, StorageX uses the criteria you specified on the Migration Criteria tab, including the criteria specified in this batch file, when evaluating and identifying migration candidates.

0 Success

All others Error

StorageX Administrator’s Guide 307

Page 326: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Archival Migration policies5

Argument

1. Policy name

2. UNC path to evaluate for CIFS; fully qualified UNIX path to evaluate for NFS

3. First user argument

Exit codes

MigrationCreation sample Archival Migration policy script

The MigrationCreation sample Archival Migration policy script is an example of the type of script you can specify on the Policy Creation Criteria tab for an Archival Migration policy when you specify that you want to use a batch file to identify folders for migration.

The MigrationCreation sample Archival Migration policy script is also an example of the type of script you can specify when you are creating a new Archival Migration policy and you specify that you want to use a batch file to identify folders for migration on the Select Policy Generator dialog box in the New Archival Migration Policy Wizard.

When you specify that you want to use a batch file to identify folders for migration, StorageX uses the source and destination pairs you specify in the output file from the batch file to create Phased Migration policies for each source and destination pair when your run the Archival Migration policy.

StorageX provides a sample MigrationCreation script and batch file you can view and modify in the \StorageX\Examples\Scripts\Archival folder on the computer where you installed the StorageX server.

Argument

1. Policy name

2. Local path to a file to which the script can output a list of a list of source and destination pairs for which Phased Migration policies should be created. The local path is relative to the StorageX server that runs the script

3. First user argument

Exit codes

Running batch files with Archival Migration policiesIf you know how to write scripts and create batch files, with Archival Migration policies you can specify that you want to run batch files by specifying a batch file on the following tabs:

• General Options tab - Allows you to specify that you want to run a batch file before or after a scan. For more information about creating a batch file to run before a scan, see “PreScan sample Archival Migration policy script” on page 307.

0 Match (Success)

1 Not a Match (Success)

All others Error

0 Success

All others Error

308 StorageX Administrator’s Guide

Page 327: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Archival Migration policies 5

• Migration Criteria tab - Allows you to specify that you want to use a batch file to confirm folders for migration. For more information about creating a batch file to confirm folders for migration, see “Criteria sample Archival Migration policy script” on page 307.

• Policy Creation Criteria tab - Allows you to specify that you want to use a batch file to identify folders for migration instead of using scan paths and migration criteria to identify folders for migration. For more information about creating a batch file to identify folders for migration instead of scan paths and migration criteria, see “MigrationCreation sample Archival Migration policy script” on page 308.

For more information about using batch files with Archival Migration policies, including requirements for using batch files, see “Using batch files with Data Movement policies” on page 315.

To run batch files with an Archival Migration policy

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and right-click the Archival Migration policy where you want to specify the batch file, and then click Properties.

3. If you want to run a batch file before or after an Archival Migration policy scan, complete the following steps:

a. Click the General Options tab.

b. If you want to run a batch file before scanning, select the Run batch file before scan check box, and then type the UNC path or a local path to the batch file or click Browse to browse to and select the batch file. For more information, click the Help button on the dialog box.

c. If you want to run a batch file after scanning completes, select the Run batch file after scan check box, and then type the UNC path or a local path to the batch file or click Browse to browse to and select the batch file. For more information, click the Help button on the dialog box.

d. Click OK.

4. If you want to run a batch file to confirm folders for migration, complete the following steps:

a. Click the Migration Criteria tab.

b. Select the The folder is confirmed for migration for the following batch file check box.

c. Type the UNC path or a local path to the batch file or click the ellipsis button (...) to browse to and select the batch file. For more information, click the Help button on the dialog box.

d. Click OK.

5. If you want to use a batch file to identify folders for migration instead of using scan paths and migration criteria to identify folders for migration, complete the following steps:

a. Click the Policy Creation Criteria tab.

b. Select Use a batch file.

c. Type the UNC path or a local path to the batch file or click Browse to browse to and select the batch file. For more information, click the Help button on the dialog box.

d. Click OK.

StorageX Administrator’s Guide 309

Page 328: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Archival Migration policies5

Specifying post-scanning options for Archival Migration policiesYou can specify options that determine how the Archival Migration policy handles the results of its scan. You can choose to automatically create Phased Migration policies after scanning completes, run those policies, and then either save or delete those policies when they have completed. Or, you can choose to view a generated list of migration candidates and select appropriate candidates for migration.

To specify post-scanning options

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and right-click the Archival Migration policy for which you want to specify post-scanning options, and then click Properties.

3. In the left pane, click the Task Options tab.

4. If you want to automatically create Phased Migration policies after scanning is complete, select the Automatically generate Migration policies for migration candidates check box.

5. If you want to view a list of migration candidates after a scan completes, clear the Automatically generate Migration policies for migration candidates check box. You can then manually create Phased Migration policies for all candidates or selected candidates.

6. If you want to delete Phased Migration policies after they complete, select the Automatically delete completed Migration policies check box.

7. If you want to keep a record of completed Phased Migration policies, clear the Automatically delete completed Migration policies check box. StorageX provides a visual indicator when a policy completes successfully.

8. If you want to only migrate folders referenced by a DFS namespace, select the Only migrate data referenced by a DFS namespace check box.

Select this check box if you only want to identify and migrate folders that meet your migration criteria and are targets of DFS links in a DFS namespace.

Only select this check box if you specified a physical path as your source path in the Source field on the Choose Source/Destination Dialog box when you created the Archival Migration policy, or if you specified a physical path as your source path on the Policy Creation Criteria tab of the Archival Migration policy. Do not select this check box if you specified a DFS link with a single link target as your source search path.

In StorageX, a physical path is a path directly to the file storage resource. For example, a physical path is the UNC path \\FileStorageResource\ShareName, where FileStorageResource is the actual name of the file storage resource. If the file storage resource is a virtual file storage resource, or if the file storage resource has its own virtualization layer, the physical path is the UNC path to the resource.

If you select this option, when the Archival Migration policy does a scan to identify migration candidates, the Archival Migration policy only identifies folders as migration candidates if the folders are targets of DFS links in a DFS namespace managed by StorageX.

For more information, see “Understanding Archival Migration policies” on page 233.

9. Click OK.

10. If you want to run a scan immediately, in the left tree pane, right-click the Archival Migration policy, and then click Run.

310 StorageX Administrator’s Guide

Page 329: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Archival Migration policies 5

StorageX creates Phased Migration policies for the migration candidates. The Phased Migration policies created from Archival Migration policies display under the Phased Migration template associated with the Archival Migration template when StorageX created the policies.

You can also run the policy according to a schedule you have configured. For more information, see “Scheduling scanning for folders to migrate” on page 302. Depending on the post-scanning options you selected, when the policy scan completes, you can view and manage the list of migration candidates or Phased Migration policies. For more information, see “Viewing and managing migration candidates” on page 303.

Managing Archival Migration template inheritanceThe base default settings for each Archival Migration policy are defined by the template you selected when you created the policy. However, you can change the template from which an Archival Migration policy inherits settings. For more information about templates, see “Understanding Phased Migration and Archival Migration templates” on page 229.

To manage template inheritance for an Archival Migration policy

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and right-click the Archival Migration policy, and then click Properties.

3. If you want to view or change the Archival Migration template associated with the policy, complete the following steps:

a. In the left pane, under Template Options, click Manage template inheritance.

b. Review the current Archival Migration template and, if appropriate, select a different template from the drop-down list.

c. Click OK.

4. If you want to view or change the Phased Migration template for Phased Migration policies generated from the Archival Migration policy, complete the following steps:

a. In the left pane, under General Settings, click the Migration Template tab.

b. Review the current Phased Migration template specified, and if appropriate, select a different Phased Migration template from the list.

c. Click OK.

Managing default settings in Archival Migration policiesThe base default settings for an Archival Migration policy are defined by the Archival Migration template you selected for the policy, but you can change those settings in the policy. You can view which settings have been changed from their defaults. You can also reset all settings in the policy back to the default template settings. For more information about templates, see “Understanding Phased Migration and Archival Migration templates” on page 229.

To view and manage default settings

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and right-click an Archival Migration policy, and then click Properties.

StorageX Administrator’s Guide 311

Page 330: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Archival Migration policies5

3. In the left pane, under Template Options, click Highlight settings that differ from the defaults to view which settings have been changed in the policy. If any default settings have been changed, the name of the affected dialog box in the left pane and the changed fields in that dialog box are displayed in bold font.

4. If you want to remove the highlighting, in the left pane, under Template Options, click Remove highlighting from changed settings.

5. If you want to reset all settings in the policy back to the default template settings, in the left pane, under Template Options, click Reset settings to their defaults.

6. Click OK.

Renaming Archival Migration policiesYou can rename Archival Migration policies any time. For example, you might need to rename your Archival Migration policies to conform to new corporate standards. Renaming the policy does not affect it in any other way.

To rename an Archival Migration policy

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and right-click an Archival Migration policy, and then click Rename.

3. Type a new name for the policy and then press the Enter key.

Organizing Archival Migration policiesYou can use folders to organize your Archival Migration policies into logical groupings in the StorageX Console.

To organize your Archival Migration policies into folders

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, browse to and right-click My Policies, and then click New > Folder.

3. Type a name for the Archival Migration policy folder and press Enter.

4. Drag and drop Archival Migration policies into the folder you created.

Viewing Archival Migration policies scheduled to run in the futureYou can view Archival Migration policies that are scheduled to run in the future on the Schedules tab.

Viewing Archival Migration policies that are scheduled to run in the future can help you understand what file data migration tasks will be occurring in the future.

It can also help you identify appropriate maintenance windows for the StorageX server computer as needed. For example, it can be helpful to know what Archival Migration policies are scheduled to run in the future if you need to temporarily take the StorageX server computer offline to apply patches or to perform other maintenance activities on the computer.

312 StorageX Administrator’s Guide

Page 331: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Configuring email notification options for Data Movement policies and templates 5

To view Archival Migration policies scheduled to run in the future

1. In the StorageX Console, click the Data Movement tab.

2. Click the Schedules tab.

3. Specify a date range to view in the From and To fields, and then click Go.

4. In the Description column, review the list of scheduled tasks and look for items with the following description:

Scanning task for Archival Migration policy ArchivalMigrationPolicyName, where ArchivalMigrationPolicyName is the name of an Archival Migration policy.

5. If you want to prevent an Archival Migration policy scheduled to run in the future from running, complete the following steps:

a. Note the name of each Archival Migration policy you want to prevent from running in the future displayed on the Schedules tab.

b. In the left tree pane, browse to the Archival Migration policy you want to prevent from running in the future.

c. Right-click the Archival Migration policy, and then click Properties.

d. On the Policy Scan Schedule tab, clear the Use policy scan schedule check box.

e. Click OK.

Deleting Archival Migration policiesYou can delete an Archival Migration policy when you no longer want to run the policy. If a migration task is in progress when you delete an Archival Migration policy, the migration task runs until it completes.

NOTEDeleting a policy from the list of policies under My Policies does not actually delete the policy. The My Policies folder is only an organizational tool.

To delete an Archival Migration policy

1. In the StorageX Console, click the Data Movement tab.

2. In the left tree pane, locate the Archival Migration policy under its template.

3. Right-click the policy, and then click Delete.

4. Click Yes.

Configuring email notification options for Data Movement policies and templates

You can configure a Phased Migration or Archival policy or policy template to automatically notify one or more users each time the policy runs. You can set a policy to send email notifications when the policy is canceled, when the policy completes successfully, when the policy completes with warnings, or when the policy completes with errors, as necessary.

StorageX Administrator’s Guide 313

Page 332: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Bypassing path validation for Data Movement policies5

StorageX sends Data Movement policy email notifications either using an existing notification profile or a new notification profile created specifically for the policy.

To configure Data Movement policy email notification options

1. If you created a Data Movement policy or policy template in the Data Movement view, or if an Archival Migration policy generated a Phased Migration policy, in the StorageX Console, click the Data Movement tab.

2. If StorageX generated a Phased Migration policy when you executed a Migration Project design, in the StorageX Console, click the Migration Projects tab.

3. In the left tree pane, browse to and right-click a Data Movement policy or policy template, and click Properties.

4. In the left pane, click Email Notification Settings.

5. If you want to use an existing notification profile, click the Select an existing notification profile or create a new profile list and select the profile you want to use, then click Email is enabled for the selected notification profile.

6. If you want to create a new notification profile for the policy or policy template, complete the following steps:

a. Click the Select an existing notification profile or create a new profile list.

b. Click New.

c. Specify the SMTP settings you want to use for the new profile. For more information about the SMTP settings, click the Help button on the dialog box.

d. Specify the message settings you want to use for the new profile. For more information about the message settings, click the Help button on the dialog box.

e. Click Send Test Message to verify the profile settings are correct.

f. If you want to use the new notification profile for all notifications, click Enable all usage of this notification.

g. Click OK.

7. Click one or more criteria you want StorageX to use when sending email notifications. For more information about the possible notification criteria, click the Help button on the dialog box.

8. Click OK.

Bypassing path validation for Data Movement policiesBy default, when you create a new Data Movement policy, the StorageX server attempts to access all destination CIFS shared folders or NFS exports. When the server cannot access a shared folder or export path, the New Phased Migration Policy Wizard does not allow you to finish creating the policy.

If you configure StorageX to bypass policy validation, you can create a Data Movement policy, even when the StorageX server cannot access the CIFS share or NFS export.

This may be necessary in some environments, as when the StorageX server cannot access an NFS export, but the StorageX universal data engine has permission for the export.

314 StorageX Administrator’s Guide

Page 333: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using batch files with Data Movement policies 5

NOTEThis setting affects all Data Movement policies. If you select the Do not validate CIFS shared folder or NFS export paths for Data Movement policies check box, StorageX bypasses validation for all Data Movement policies created on the StorageX server.

To configure StorageX to bypass path validation for Data Movement policies

1. Click File > Options.

2. Click the Policy Validation Options tab.

3. If you want StorageX to not validate shared folder or export paths when creating a Data Movement policy, select Do not validate CIFS shared folder or NFS export paths for Data Movement policies.

4. Click OK.

Using batch files with Data Movement policiesIf you know how to write scripts and create batch files, you can use batch files with Phased Migration and Archival Migration Data Movement policies.

The following topics provide more information about using batch files with Phased Migration and Archival Migration policies:

• “Using batch files with Phased Migration policies” on page 315

• “Using batch files with Archival Migration policies” on page 316

• “Phased Migration and Archival Migration batch file requirements” on page 317

Using batch files with Phased Migration policiesFor Phased Migration templates and Phased Migration policies, you can specify that you want to run batch files by specifying a batch file on the following tabs:

• Replication Scripting tab - Allows you to specify that you want to run a batch file before or after replication.

• Initial Phase tab - Allows you to specify that you want to run a batch file as the first action that occurs in the Initial Phase of a policy run.

• Final Phase tab - Allows you to specify that you want to run a batch file as the final action that occurs in the Final Phase of a policy run.

Depending on when you run the batch file, StorageX passes certain parameters that you can use in your scripting. StorageX returns one set of parameters when you run a batch file before replication or in the Initial Phase of a policy run, and a second, larger set of parameters when you run a batch file after replication or as the final action in the Final Phase of a policy run.

TABLE 28 StorageX parameters returned for pre-run batch files

Parameter Name Parameter Description

[Empty string] StorageX returns a null-value string for the first parameter.

Source Path StorageX returns the full path of the Phased Migration policy source.

StorageX Administrator’s Guide 315

Page 334: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using batch files with Data Movement policies5

For more information about batch file requirements for Phased Migration policies, see “Phased Migration and Archival Migration batch file requirements” on page 317. For more information about running batch files, see “Running batch files with Phased Migration policies” on page 286.

Using batch files with Archival Migration policiesFor Archival Migration templates and Archival Migration policies, you can specify that you want to run batch files by specifying a batch file on the following tabs:

• General Options tab - Allows you to specify that you want to run a batch file before or after a scan. For more information about creating a batch file to run before a scan, see “PreScan sample Archival Migration policy script” on page 307.

Destination Path StorageX returns the full path of the Phased Migration policy destination.

Current Migration Phase StorageX returns the name of the phase during which the batch file is run. The value returned will be Initial, Incremental, or Final, depending on the phase.

TABLE 29 StorageX parameters returned for post-run batch files

Parameter Name Parameter Description

[Empty string] StorageX returns a null-value string for the first parameter.

Source Path StorageX returns the full path of the Phased Migration policy source.

Destination Path StorageX returns the full path of the Phased Migration policy destination.

Policy Run Duration (Timespan) StorageX returns the amount of time it took the policy to run, in seconds. This policy duration includes not only copying of files, but also other policy actions associated with the policy run, such as deploying universal data engines to the source or destination as needed, hiding shares and exports, deleting shares and exports, and updating DFS namespaces and automount map files as specified for the policy.

Finish State StorageX returns the status of the policy run.

Files Copied StorageX returns the number of files copied from the source to the destination during the policy run.

Bytes Copied StorageX returns the number of bytes copied from the source to the destination during the policy run.

Files In Sync StorageX returns the number of files that were already in sync between the source and the destination and were not copied during the last policy run.

Bytes In Sync StorageX returns the number of bytes that were already in sync between the source and destination and were not copied during the policy run.

Files Deleted StorageX returns the number of files deleted during the policy run.

Bytes Deleted StorageX returns the number of bytes deleted during the policy run.

Files Excluded StorageX returns the number of files that were excluded from the last policy run.

Bytes Excluded StorageX returns the number of bytes that were excluded from the last policy run.

Current Migration Phase StorageX returns the name of the phase during which the batch file is run. The value returned will be Initial, Incremental, or Final, depending on the phase.

TABLE 28 StorageX parameters returned for pre-run batch files

Parameter Name Parameter Description

316 StorageX Administrator’s Guide

Page 335: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using batch files with Data Movement policies 5

• Migration Criteria tab - Allows you to specify that you want to use a batch file to confirm folders for migration. For more information about creating a batch file to confirm folders for migration, see “Criteria sample Archival Migration policy script” on page 307.

• Policy Creation Criteria tab - Allows you to specify that you want to use a batch file to identify folders for migration instead of using scan paths and migration criteria to identify folders for migration. For more information about creating a batch file to identify folders for migration instead of scan paths and migration criteria, see “MigrationCreation sample Archival Migration policy script” on page 308.

Phased Migration and Archival Migration batch file requirementsBefore you specify a batch file for a Phased Migration or Archival Migration policy, review the following requirements to ensure the batch file produces the desired results and the policy completes successfully.

• If the path to the batch file contains spaces, the path must be wrapped in quotation marks.

• If you browse to the batch file location, StorageX automatically enters the quotation marks.

• If you enter the path to the batch file manually, you must enter the quotation marks.

• StorageX does not validate the path to the batch file you specify. It is your responsibility to ensure that the path is accurate and accessible to the StorageX server that runs the batch file.

• Batch files run with their working folder set to the folder containing the batch file when they are specified by a local path, such as c:\bats\myfile.bat. When the batch file is referenced by a UNC path, its working folder is the system32 folder of the StorageX server that runs the batch file.

• Any file StorageX runs must be a batch file. It is possible to have a top-level batch file run other tools, such as jscript files or other executables.

• The arguments StorageX passes to the batch file may be slightly different than expected. It can be very helpful to have your batch file log into a text file when the batch file runs, along with the arguments it receives.

For more information about arguments StorageX uses when running Archival Migration policy batch files, see the following topics:

• “PreScan sample Archival Migration policy script” on page 307

• “Criteria sample Archival Migration policy script” on page 307

• “MigrationCreation sample Archival Migration policy script” on page 308

• Multiple copies of a batch file might run simultaneously if tasks are running at the same time.

• StorageX uses the exit value of the batch file to assess whether the batch file succeeded or failed. Batch files must set the return value correctly to signal either success or failure.

If you are using batch files with Archival Migration policies, the exit code is not just a success or failure values. For more information about exit codes used for Archival Migration policies, see

• If your batch file is not producing the desired results, you can insert different exit codes throughout the batch file to determine where exactly the batch file is exiting. You can also insert logging statements showing progress through the script to trace execution.

StorageX Administrator’s Guide 317

Page 336: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using batch files with Data Movement policies5

• Batch files must not prompt for user input, since there is no console available to display a prompt at run time. Batch files that prompt for input may cause StorageX to stop responding because the policy executing the batch file will hang indefinitely. This is true for any prompt, whether in an error path or in a normal execution path in the batch file.

• The Alert Details and Event Details dialog boxes may truncate output from user-written batch files that return more than about 80 characters to Stdout. If you need to output more than 80 characters from a batch file, ensure the batch file is written to store the information in a disk file for subsequent reference.

• Test your scripts and batch files to verify that they are functioning as expected before you use them in policies. Specify small test directories for the source and destination and configure the scripts to write diagnostic output to a text file for review. After the scripts function correctly in the test configuration, you can configure them for use in actual policies, and you can reduce the amount of diagnostic information logged by the scripts to match the requirements of your environment.

For more information about using batch files with Phased Migration policies, see “Running batch files with Phased Migration policies” on page 286. For more information about using batch files with Archival Migration policies, see “Running batch files with Archival Migration policies” on page 308.

318 StorageX Administrator’s Guide

Page 337: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX Administrator’s Guide

Chapter

6

Creating and Managing Migration Projects

This section provides information about Migration Projects. It explains what Migration Projects are, how to create Migration Projects and Migration Project designs, and how to execute Migration Projects and generate Phased Migration policies to use to migrate file data.

In this chapter•Checklist: Migrating data using Migration Projects. . . . . . . . . . . . . . . . . . . 320

•Understanding Migration Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

•Migration Project operating system requirements . . . . . . . . . . . . . . . . . . . 332

•Identifying Migration Project sources, destinations, and credentials . . . . 332

•Creating Migration Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

•Adding sources and destinations to Migration Projects . . . . . . . . . . . . . . . 334

•Understanding Migration Project views . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

•Generating Data ONTAP SnapMirror reports . . . . . . . . . . . . . . . . . . . . . . . . 338

•Creating Migration Project designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

•Editing and specifying advanced options for Migration Project designs . . 353

•Exporting Migration Project designs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

•Validating Migration Project designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

•Understanding Migration Project design validation rules. . . . . . . . . . . . . . 356

•Deploying universal data engines for migrations using the NFS protocol. 361

•Modifying Migration Project Phased Migration template properties . . . . . 362

•Creating custom folders for Migration Project Phased Migration policies 362

•Executing Migration Project designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

•Viewing and modifying Migration Project Phased Migration policies . . . . 365

•Rolling back when a Migration Project design execution fails . . . . . . . . . . 366

•Managing Migration Projects and Migration Project designs. . . . . . . . . . . 369

319

Page 338: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Checklist: Migrating data using Migration Projects6

Checklist: Migrating data using Migration ProjectsUse the following checklist to help you migrate data using Migration Projects:

TABLE 30 Checklist: Migrating data using Migration Projects

Task

1 Ensure you understand Migration Project source and destination requirements and how the following items work:• Migration Projects. For more information, see “Understanding Migration Projects” on page 321.• Migration Project operating system requirements. For more information, see “Migration Project

operating system requirements” on page 332.• Migration Project sources and destinations. For more information, see “Understanding Migration

Project sources and destinations” on page 323.• Migration Project designs. For more information, see “Understanding Migration Project designs”

on page 326.• Migration Project Phased Migration templates. For more information, see “Understanding

Migration Project Phased Migration templates” on page 328.• Phased Migration policies generated using settings specified in Migration Project designs and the

Migration Project Phased Migration template. For more information, see “Understanding Migration Project Phased Migration policies” on page 328.

2 Identify source and destination file storage resources and credentials for the Migration Project. Verify that the sources and destinations have been added to StorageX and that they display correctly in the My Resources folder in the Storage Resources view. For more information, see “Identifying Migration Project sources, destinations, and credentials” on page 332.

3 If you want to include VNX OE for File file storage resources as sources or destinations in Migration Projects, configure SSH for VNX OE for File file storage resources. For more information, see “Configuring StorageX to Use SSH Shell Credentials” on page 433.

4 Create the Migration Project. For more information, see “Creating Migration Projects” on page 333.

5 Add sources and destinations to the Migration Project. For more information, see “Adding sources and destinations to Migration Projects” on page 334.

6 Review Migration Project summary information and source and destination file storage resource summary and detailed information. For more information, see the following topics:• “Using Migration Project Summary views” on page 335• “Using Migration Project Source and Destination Summary views” on page 336• “Using Migration Project Source and Destination Detail views” on page 337

7 If you added Data ONTAP file storage resources to you Migration Project, generate a SnapMirror report and review SnapMirror relationships as needed. For more information, see “Generating Data ONTAP SnapMirror reports” on page 338.

8 Design the Migration Project. For more information, see “Creating Migration Project designs” on page 339.

9 Validate the Migration Project design. For more information, see “Validating Migration Project designs” on page 354 and “Understanding Migration Project design validation rules” on page 356.

10 If you will be migrating file data using the NFS protocol, ensure you deploy the universal data engines that you want to use to migrate file data using the NFS protocol before you execute the Migration Project design. For more information, see “Deploying universal data engines for migrations using the NFS protocol” on page 361.

11 View Migration Project Phased Migration template properties and modify properties as needed. For more information, see “Modifying Migration Project Phased Migration template properties” on page 362.

320 StorageX Administrator’s Guide

Page 339: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Projects 6

Understanding Migration ProjectsMigration Projects support migrating file data to and from Data ONTAP, VNX OE for File, and OneFS file storage resources.

Migration Projects help you automate the creation, or provisioning, of target items on the destination file storage resources, including items such as volumes, qtrees and tree quotas, CIFS shared folders, and NFS exports. Migration Projects also help you automate the creation of Phased Migration policies that you can then use to migrate file data from CIFS shared folders or NFS exports on sources to appropriate new locations on destination file storage resources.

If you want to migrate file data stored in specific sets of CIFS shared folders or NFS exports, or if you want to migrate file data stored on Windows or Linux file storage resources, create and run Phased Migration policies. For more information about creating Phased Migration policies, see “Creating Phased Migration policies” on page 250.

Migration Projects can be as simple as creating a single Migration Project that moves data from one volume on an older Data ONTAP file storage resource to a new volume on a newer Data ONTAP file storage resource. Migration Projects can also be more complex. Consider the following examples:

• As a part of a technology refresh cycle, you need to move file data stored in volumes and qtrees on several older Data ONTAP file storage resources to newer Data ONTAP file storage resources.

• As a part of a technology refresh cycle, you need to move file data stored in volumes and qtrees on several older Data ONTAP file storage resources to newer VNX OE for File or OneFS file storage resources.

• Due to a corporate merger, you need to move file data stored on multiple VNX OE for File file storage resources owned by one business unit over to one or more Data ONTAP file storage resources owned by a different business unit.

12 If you will have multiple Migration Project designs, create custom folders for policies based on your designs as needed. For more information, see “Creating custom folders for Migration Project Phased Migration policies” on page 362.

13 Execute the Migration Project design. For more information, see “Executing Migration Project designs” on page 363.

14 View the Phased Migration policies generated when you executed the Migration Project design and modify polices as needed. For more information, see “Viewing and modifying Migration Project Phased Migration policies” on page 365.

15 Run the Phased Migration policies for the project. You can run the policies immediately or schedule the policies. For more information, see “Running Phased Migration policies immediately” on page 262 and “Scheduling Phased Migration policies” on page 263.

16 Verify that the Phased Migration policies completed successfully. For more information, see “Verifying Phased Migration policies completed successfully” on page 271.

17 Review Migration Project reports and Phased Migration policy reports as needed to help you better understand the current state of your Migration Project and the Phased Migration policies generated for Migration Projects. For more information, see “Understanding Migration Project Reports” on page 420, “Understanding Phased Migration Policy reports” on page 421, and “Viewing reports” on page 426.

TABLE 30 Checklist: Migrating data using Migration Projects

Task

StorageX Administrator’s Guide 321

Page 340: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Projects6

Based on source and destination mappings you specify in the Migration Project, StorageX automatically creates, or provisions the following items on destination file storage resources as appropriate:

• If the destination is a Data ONTAP file storage resource, StorageX creates volumes and qtrees as appropriate on destination

• If the destination is a VNX OE for File file storage resource, StorageX creates file systems and tree quotas as appropriate on the destination

• If the destination is a OneFS file storage resource, StorageX creates folders under the /ifs folder and OneFS SmartQuotas as appropriate on the destination

Migration Projects also automatically generate Phased Migration policies for you to use to migrate file data from the sources to the destinations included in the project. After StorageX generates Phased Migration policies based on the settings you specified in the Migration Project, you can view and modify the policies as needed. You can then choose to run the Phased Migration policies immediately or schedule the policies.

After you run the Phased Migration policies generated by a Migration Project, you can verify that the file data was migrated successfully by viewing information in the Status area for the policy. If there was an issue when the policy ran, you can view detailed information about the issue in the policy manifest and in the Alerts and Events view. Once you address any issues that occurred during the policy run, you can re-run the policies as needed until the file data is successfully migrated.

You can also use Migration Project reports to help you better understand the state of your Migration Projects and the Phased Migration policies generated for Migration Projects.

Migration Projects consist of the following items:

Source and destination file storage resources for the migrationYou can have one or more sources and one or more destinations in a Migration Project. You can also create Migration Projects that include a mixture of Data ONTAP, VNX OE for File, and OneFS file storage resources in the same or in different Migration Projects. For more information, see “Migration Project operating system requirements” on page 332 and “Understanding Migration Project sources and destinations” on page 323.

Migration Project designsMigration Project designs allow you to design, model, and validate Migration Projects before StorageX creates, or provisions items on destination file storage resources and generates the individual Phased Migration policies used to perform the actual file data migration. For more information, see “Understanding Migration Project designs” on page 326.

Migration Project Phased Migration templatesMigration Project Phased Migration templates provide default settings that StorageX uses as a base when generating Phased Migration policies for a Migration Project. For more information, see “Understanding Migration Project Phased Migration templates” on page 328.

Phased Migration policiesPhased Migration policies are created by StorageX based on the settings specified in the Migration Project Phased Migration template and the Migration Project design. You can run the Phased Migration policies created for a Migration Project immediately or schedule the policies. For more information, see “Understanding Migration Project Phased Migration policies” on page 328.

322 StorageX Administrator’s Guide

Page 341: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Projects 6

Migration Project reportsMigration Project reports provide information about Phased Migration policies associated with Migration Projects and Migration Project designs. For example, you can view reports that provide summary information for Migration Projects and Migration Project designs, as well as reports that provide detailed information about all of the Phased Migration policies associated with each Migration Project in StorageX. For more information about Migration Project reports, see “Understanding Migration Project Reports” on page 420 and “Viewing reports” on page 426.

Understanding Migration Project sources and destinationsEach Migration Project consists of one or more sources and one or more destinations. In a Migration Project, a source can be one of the following items:

TABLE 31 Migration Project sources and destinations

Platform Source Destination

Data ONTAP Entire Data ONTAP file storage resource, including all volumes on the resource

• An aggregate on a Data ONTAP file storage resource

• A storage pool on a VNX OE for File file storage resource

• The /ifs folder on a OneFS file storage resource

NOTE: StorageX does not support migrating FlexGroups using Migration Projects. To migrate FlexGroup data, use a Phased Migration policy.

One or more volumes on a Data ONTAP file storage resource

• An aggregate on a Data ONTAP file storage resource

• A storage pool on a VNX OE for File file storage resource

• The /ifs folder on a OneFS file storage resource

One or more qtrees on a Data ONTAP file storage resource

• A volume on a Data ONTAP file storage resource

• The VNX OE for File file system on a VNX OE for File file storage resource

• The /ifs folder on a OneFS file storage resource

• If you are creating an Advanced Migration Project design and transforming qtrees to a different type of item, you can specify a Data ONTAP aggregate or a VNX OE for File storage pool as a destination. For more information, see “Creating Migration Project designs” on page 339 and “Creating Advanced Migration Project designs” on page 349.

StorageX Administrator’s Guide 323

Page 342: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Projects6

VNX OE for File Entire VNX OE for File file storage resource, including all volumes on the resource

• An aggregate on a Data ONTAP file storage resource

• A storage pool on a VNX OE for File file storage resource

• The /ifs folder on a OneFS file storage resource

The VNX OE for File file system on a VNX OE for File file storage resource

• An aggregate on a Data ONTAP file storage resource

• A storage pool on a VNX OE for File file storage resource

• The /ifs folder on a OneFS file storage resource

One or more volumes on a VNX OE for File file storage resource

• An aggregate on a Data ONTAP file storage resource

• A storage pool on a VNX OE for File file storage resource

• The /ifs folder on a OneFS file storage resource

One or more tree quotas on a VNX OE for File file storage resource

• A volume on a Data ONTAP file storage resource

• A storage pool on a VNX OE for File file storage resource

• The /ifs folder on a OneFS file storage resource

• If you are creating an Advanced Migration Project design and transforming qtrees to a different type of item, you can specify a Data ONTAP aggregate or a VNX OE for File storage pool as a destination. For more information, see “Creating Migration Project designs” on page 339 and “Creating Advanced Migration Project designs” on page 349.

OneFS One or more folders under the /ifs folder on a OneFS file storage resource

• A volume on a Data ONTAP file storage resource

• A storage pool on a VNX OE for File file storage resource

• The /ifs folder on a OneFS file storage resource

NOTE: StorageX does not support migrating SmartLock directories. Ensure that all source folders included in your Migration Project are not SmartLock directories.

Windows Windows file storage resources are currently not supported as sources or destinations in Migration Projects. However, you can use Phased Migration policies to migrate data stored in CIFS shared folders on Windows file storage resources. For more information, see “Understanding Phased Migration policies” on page 230.

Linux Linux file storage resources are currently not supported as sources or destinations in Migration Projects. However, you can use Phased Migration policies to migrate data stored in NFS exports on Linux file storage resources. For more information, see “Understanding Phased Migration policies” on page 230.

TABLE 31 Migration Project sources and destinations

Platform Source Destination

324 StorageX Administrator’s Guide

Page 343: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Projects 6

There is no limit to the number of source and destinations you can include in a Migration Project.

After you add sources and destinations to Migration Projects, when you design the Migration Project you match each source with a destination. For more information about designing Migration Projects, see “Understanding Migration Project designs” on page 326 and “Creating Migration Project designs” on page 339.

If your source contains CIFS shared folders, StorageX will clone the CIFS shared folders on the source to the destination. However, StorageX clones security settings for only domain groups, domain users, and local built-in accounts on the source to the destination, such as the local Admin account. StorageX does not clone share security settings for local users or groups from the source to the destination. As a result, a best practice is to verify that any CIFS shared folders that are sources in Phased Migration policies created from Migration Project designs do not have any local users, local groups, or unresolved SIDs specified in the CIFS shared folder permissions on the source.

Consider the following points:

• If your source is a CIFS shared folder and your destination is on a Data ONTAP 8.2 Cluster Mode, Data ONTAP 8.3 Cluster Mode, ONTAP 9, or ONTAP 9.1 file storage resource, when you run a Phased Migration policy created from a Migration Project design, StorageX performs the following actions:

• If there are local groups or local users and domain groups and domain users in the in the CIFS shared folder permissions on the source, when you run a Phased Migration policy created from a Migration Project design, StorageX creates the CIFS shared folder on the destination. StorageX strips out the CIFS shared folder permissions for the local groups and local users, but StorageX does migrate the CIFS shared folder permissions for the domain groups and domain users.

• If there are only local groups or local users in the CIFS shared folder permissions on the source, when you run a Phased Migration policy created from a Migration Project design, StorageX creates the CIFS shared folder on the destination. However, StorageX does not migrate the security settings for the local groups or local users. Because the CIFS shared folder created on the destination is a CIFS shared folder that has no security settings, the Data ONTAP operating system by default adds the Everyone group to the share permissions and gives the Everyone group Full permissions.

• If there are any users with unresolved SIDs in the CIFS shared folder permissions on the source, when you run a Phased Migration policy created from a Migration Project design, StorageX creates the CIFS shared folder on the destination. However, StorageX does not migrate the unresolved SIDs. Because the CIFS shared folder created on the destination is a CIFS shared folder that has no security settings, the Data ONTAP operating system by default adds the Everyone group to the share permissions and gives the Everyone group Full permissions.

• If your source is a CIFS shared folder and your destination is on a Data ONTAP 7.3.2 or later file storage resource or a Data ONTAP 8.0.2 or later 7- Mode file storage resource, when you run a Phased Migration policy created from a Migration Project design, StorageX performs the following actions:

• If there are local groups or local users in the CIFS shared folder permissions on the source, when you run a Phased Migration policy created from a Migration Project design, StorageX creates the CIFS shared folder on the destination, and then migrates the local groups and local user permissions to the destination. However, the local groups or local users display as unresolved SIDs on the destination.

StorageX Administrator’s Guide 325

Page 344: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Projects6

• If there are any users with unresolved SIDs in the CIFS shared folder permissions on the source, when you run a Phased Migration policy created from a Migration Project design, StorageX creates the CIFS shared folder on the destination. StorageX then migrates any unresolved SIDs from the source to the destination.

• If your source is a CIFS shared folder and your destination is on a VNX OE for File file storage resource, when you run a Phased Migration policy created from a Migration Project design, if there are local users, local groups, or any users with unresolved SIDs in the CIFS shared folder permissions on source, StorageX will not create the CIFS shared folders on the destination, and StorageX displays an error when the policy runs in the Final Phase.

• If your source is a CIFS shared folder and your destination is a OneFS file storage resource, when you run a Phased Migration policy created from a Migration Project design, StorageX performs the following actions:

• If there are local groups or local users in the CIFS shared folder permissions on the source, when you run a Phased Migration policy created from a Migration Project design, StorageX creates the CIFS shared folder on the destination, and then migrates the local groups and local user permissions to the destination. However, the local groups or local users display as unresolved SIDs on the destination.

• If there are any users with unresolved SIDs in the CIFS shared folder permissions on the source, when you run a Phased Migration policy created from a Migration Project design, StorageX creates the CIFS shared folder on the destination. StorageX then migrates any unresolved SIDs from the source to the destination.

If your source is a compressed NTFS file system and your destination is a VNX OE for File file system, the VNX OE for File file system must have deduplication enabled and set to Deep. For more information, see the EMC VNX Deduplication and Compression white paper, available at http://www.emc.com/collateral/hardware/white-papers/h8198-vnx-deduplication-compression-wp.pdf.

Understanding Migration Project designsAfter creating a Migration Project and adding sources and destinations to the project, create one or more Migration Project designs using the sources and destinations. Migration Project designs specify the source and destination mappings and settings you want to use for file storage resources included in the Migration Project. When you create a Migration Project design, you specify the sources and destinations you want to include in the design.

StorageX takes the information you specify in a Migration Project design and uses this information to perform the following actions:

• Create, or provision, items on destination file storage resources as appropriate when you execute the design, including the creation of the following items on destination file storage resources:

• Data ONTAP volumes and qtrees

• VNX OE for File file systems and tree quotas

• OneFS folders

• Generate Phased Migration policies that you can then use to migrate file data from the sources to the destinations you specified in the Migration Project design based on the source and destination mappings you specified in the Migration Project design.

326 StorageX Administrator’s Guide

Page 345: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Projects 6

When you create Migration Project designs, you can create the following types of designs:

Like-to-Like Migration Project designsCreate Like-to-Like Migration Project designs when you want to create destination items on destination file storage resources that are similar to the source items on the source file storage resources. Consider the following examples:

• Your source is a Data ONTAP file storage resource and you want to perform the following tasks:

• Migrate file data from Data ONTAP volumes to volumes on aggregates on new Data ONTAP file storage resources, to file systems in storage pools on VNX OE for File file storage resources, or to the /ifs folder on OneFS file storage resources.

• Migrate file data from Data ONTAP qtrees to volumes on Data ONTAP file storage resources, to file systems on VNX OE for File file storage resources, or to the /ifs folder on OneFS file storage resources.

• Your source is a VNX OE for File file storage resource and you want to perform the following tasks:

• Migrate file data from VNX OE for File file systems to volumes on aggregates on Data ONTAP file storage resources, to file systems on VNX OE for File file storage resources, or to the /ifs folder on OneFS file storage resources.

• Migrate file data in tree quotas on VNX OE for File file storage resources to qtrees on volumes on Data ONTAP file storage resources, to file systems on VNX OE for File file storage resources, or to the /ifs folder on OneFS file storage resources.

• Your source is a OneFS file storage resource and you want to perform the following tasks:

• Migrate folders under the /ifs folder on OneFS file storage resources to volumes on aggregates on Data ONTAP file storage resources, to file systems in storage pools on VNX OE for File file storage resources, or to the /ifs folder on new OneFS file storage resources.

• Migrate folders under the /ifs folder on OneFS file storage resources to qtrees on volumes on Data ONTAP file storage resources.

For more information about creating Like-to-Like Migration Project designs, see “Creating Like-to-Like Migration Project designs” on page 342.

Advanced Migration Project designsCreate Advanced Migration Project designs when you want to transform the way you store your file data and create items on destination file storage resources that are different from the source items on the source file storage resource. Consider the following examples:

• You want to transform a qtree on a source Data ONTAP file storage resource to a volume on a destination Data ONTAP file storage resource.

• You want to transform a qtree on a source Data ONTAP file storage resource to a file system on a destination VNX OE for File file storage resource or to a folder or subfolder under the /ifs folder on a destination OneFS file storage resource.

• You want to transform a tree quota on a source VNX OE for File file storage resource to a volume on a destination Data ONTAP file storage resource or to a folder or subfolder under the /ifs folder on a destination OneFS file storage resource

• You want to transform a tree quota on a source VNX OE for File file storage resource to a file system on a destination VNX OE for File.

StorageX Administrator’s Guide 327

Page 346: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Projects6

For more information about creating Advanced Migration Project designs, see “Creating Advanced Migration Project designs” on page 349.

The number of Migration Project designs you create for a Migration Project can vary based on the types of destination file storage resources included in your Migration Project.

For more information about creating Migration Project designs, see “Creating Migration Project designs” on page 339.

Understanding Migration Project Phased Migration templatesWhen you create a Migration Project design, StorageX automatically associates the Migration Project design with the Migration Project Phased Migration template available in the Migration Projects view.

The Migration Project Phased Migration template in the Migration Project view contains common settings and options StorageX uses as a base when executing the Migration Project design and generating Migration Project Phased Migration policies for the project.

Although each Migration Project Phased Migration policy StorageX creates in the Migration Project view for a Migration Project is based on the Migration Project Phased Migration template, the template exists separately from the Migration Project Phased Migration policies. Since the Migration Project Phased Migration template is separate from the policies, you can create and maintain the Migration Project Phased Migration policies separately from the Migration Project Phased Migration template.

For example, if you want to change the default policy settings StorageX uses when generating Phased Migration policies for a Migration Project, you can update the settings in the Migration Project Phased Migration template. Then, the next time you execute a Migration Project design and StorageX generates Phased Migration policies based on the Migration Project design and the Migration Project Phased Migration template, the Migration Project Phased Migration policies you create will automatically include the new default settings. The new policy settings you specify will also be inherited by any existing Migration Project Phased Migration policies you may have already created in the Migration Projects view.

Like non-project Phased Migration policies, Phased Migration policies created as part of an Archival Migration Project also copy file and directory attributes and permissions.

NOTEPhased Migration policies do not copy the offline attribute (FILE_ATTRIBUTE_OFFLINE) when copying file or directory attributes during the migration process, because the file or directory is online by default after migration. If you want to configure the migrated file or directory to be offline, you must use a third-party tool to set the offline attribute after the migration process finishes.

For more information, see “Modifying Migration Project Phased Migration template properties” on page 362.

Understanding Migration Project Phased Migration policiesMigration Project Phased Migration policies are the policies StorageX automatically generates when executing a Migration Project design. You use the Phased Migration policies to migrate file data. You can run the policies immediately or schedule the policies.

328 StorageX Administrator’s Guide

Page 347: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Projects 6

Phased Migration policies generated in the Migration Projects view are very similar to the Phased Migration policies you create in the Data Movement view. However, Phased Migration policies generated in the Migration Projects view are different from the Phased Migration policies you create in the Data Movement view in the following ways:

• Phased Migration policies generated as a part of a Migration Project display in the Migration Projects view. Phased Migration projects you create manually to migrate file data stored in sources CIFS shared folders or NFS exports to destination CIFS shared folders or NFS exports display in the Data Movement view.

Phased Migration policies generated by Migration Projects display when you click the Migration Projects tab. You can view the individual policies in the Migration Projects > My Policies folder or in a custom folder under Migration Projects if you created and then specified a custom folder for the policies when you executed the Migration Project design.

Phased Migration policies you create in the Data Movement view display when you click the Data Movement tab. You can view the individual Phased Migration policies in the Data Movement view under the template each policy uses. If you created the Phased Migration policy by right-clicking the My Policies folder and then clicking New > Phased Migration Policy, the new Phased Migration policy displays under both the Phased Migration template used when creating the new Phased Migration policy, as well as under the My Policies folder.

• Phased Migration policies generated by Migration Projects in the Migration Projects view use a slightly different Phased Migration template than the Phased Migration policies available in the Data Movement view. The Stop sharing the source option is not available on the Final Phase tab of the Phased Migration template used as a base when generating Phased Migration policies for a Migration Project. This option is available on the Final Phase tab for Phased Migration templates used to create Phased Migration policies in the Data Movement view.

• Phased Migration policies in the Migration Projects view have slightly different options available on the Final Phase tab and on the Migration Paths tab.

• The Stop sharing the source option is not available on the Final Phase tab for Phased Migration policies generated by Migration Projects. This option is available on the Final Phase tab for Phased Migration policies created in the Data Movement view. This is because typically in Migration Projects whole volumes are moved, and then the entire source file storage resource is taken offline and decommissioned.

• The Original Path and Destination Path fields are read-only on the Migration Paths tab for Phased Migration policies generated by Migration Projects. This option is available on the Migration Paths tab for Phased Migration policies created in the Data Movement view. This is because for Migration Projects, StorageX creates the source and destination paths for the policy when it executes the Migration Project.

• The process used to create destination CIFS shared folders or NFS exports varies based on whether the Phased Migration policy was created when you executed a Migration Project design in the Migration Projects view or whether you created the Phased Migration policy using the New Phased Migration Policy Wizard in the Data Movement view.

• In the Migration Projects view, Phased Migration policies create destination CIFS shared folders or NFS exports during the Final Phase of the policy run.

• In the Data Movement view, destination CIFS shared folders or NFS exports are handled as follows:

If you specify a CIFS shared folder or NFS export as your source in a Phased Migration policy you create using the New Phased Migration Policy Wizard in the Data Movement view, the destination CIFS shared folders or NFS exports must exist on the destination in order for you to create the policy.

StorageX Administrator’s Guide 329

Page 348: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Projects6

If you specify an entire file storage resource as your source in a Phased Migration policy you create using the New Phased Migration Policy Wizard in the Data Movement view, if the destination CIFS shared folders or NFS exports do not exist, StorageX can create the destination CIFS shared folders or NFS exports for you as you create the policy.

For more information about creating Phased Migration policies in the Data Movement view, see “Creating new Phased Migration policies” on page 251.

• If you have user quotas on source file storage resources, Phased Migration policies in the Migration Projects view create the appropriate corresponding user quota item on the destination as the last step in the Final Phase of the Phased Migration policy. For example, if you have Data ONTAP qtrees with quotas, VNX OE for File tree quotas, or OneFS SmartQuotas on the source, Phased Migration policies create the appropriate quota items, such as a Data ONTAP qtrees with quotas, VNX OE for File tree quotas, or OneFS SmartQuotas on the destination in the Final Phase.

Phased Migration policies created in the Data Movement view do not have this capability.

When Phased Migration policies in the Migration Project view run in the Final Phase, StorageX copies user quota information from the source to the destination.

StorageX maintains quota settings for domain users and groups when creating the quota settings on the destination. However, StorageX does not maintain quota settings for local users and groups. You must manually configure quota settings for local users and groups on the destination.

In addition, the quotas StorageX creates on the destination are not turned on by default. You must turn on the quotas using a native Data ONTAP, VNX OE for File, or OneFS tool. For more information about enabling quotas on the destination after the Phased Migration policy completes, see the Data ONTAP, VNX OE for File, or OneFS documentation.

• If you are using StorageX with DFS namespaces or automount map files, Phased Migration policies in the Migration Projects view can automatically update DFS namespaces and automount map files as a part of the Final Phase of the policy if you select the Update automounts or update DFS namespaces using the following method option on the Final Phase tab for the policy. However, the process used to update the DFS namespaces and automount map files varies based on whether the policy is a Phased Migration policy in the Data Movement view or a Phased Migration policy in the Migration Projects view.

• If the Phased Migration policy is in the Data Movement view, after the Phased Migration policy runs, StorageX updates the DFS namespace if a DFS link points to the source CIFS shared folder or a child folder under the source CIFS shared folder.

• If the Phased Migration policy is in the Migration Projects view, StorageX does not look at the source when updating the DFS namespace. StorageX instead enumerates all of the CIFS shared folders on the destination and then updates the DFS namespace for all of the shares on the destination.

Understanding using SnapMirror replication for Migration ProjectsBy default, any Phased Migration policies StorageX automatically generated for a Migration Project design use the StorageX universal data engine to copy data from any source resource to the corresponding destination resource.

330 StorageX Administrator’s Guide

Page 349: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Projects 6

However, you can also configure StorageX to use SnapMirror replication to migrate data from the source to the destination of a Migration Project when the resources meet certain requirements. You can only use SnapMirror replication for Migration Project designs if the source is one of the following:

• Data ONTAP 7 file storage resource

• Data ONTAP 8 7-Mode file storage resource

Any destination for SnapMirror replication must be a Data ONTAP 8.2 Cluster Mode, Data ONTAP 8.3 Cluster Mode, ONTAP 9, or ONTAP 9.1 file storage resource. If both the source and destination are valid, StorageX allows you to use SnapMirror replication for any Phased Migration policies generated by the Migration Project.

In addition to the source and destination requirements, you must create an intercluster interface for the destination resource cluster before you can use SnapMirror replication to copy data to the cluster. If a valid intercluster interface already exists, you do not need to create a new interface. For more information about creating intercluster interfaces, see “Configuring intercluster interfaces for NetApp Cluster Mode file storage resources” on page 116

You can configure both Like-to-Like and Advanced Migration Project designs to use SnapMirror replication instead of the universal data engine. Select the Use SnapMirror option in the Migration Project Design Wizard or the Use Snapmirror option in the Migration Project Design Advanced Options dialog box, as appropriate.

For more information about creating Migration Project designs, see “Creating Migration Project designs” on page 339.

NOTES:

• If you quiesce a SnapMirror currently being used to transfer data, you must manually resume the data transfer. StorageX does not automatically restart SnapMirror data transfers when the SnapMirror is quiesced. In addition, any policy currently using the SnapMirror to transfer data will not correctly display the number of bytes copied in the manifest.

• If you delete a Phased Migration policy generated by a Migration Project design while that policy is running, and the design uses SnapMirror replication, you must manually quiesce and delete the SnapMirror on both the source and destination resources and delete the partially-migrated volume on the destination resource. For more information about deleting SnapMirrors, see “Deleting SnapMirrors from StorageX for Data ONTAP file storage resources” on page 157. For more information about using SnapMirror replication for Migration Project designs, see “Understanding using SnapMirror replication for Migration Projects” on page 330.

• If you use SnapMirror replication for a Migration Project design, when the design execution is completed, the Phased Migration policy automatically clones existing exports from the source Data ONTAP 7 or 7-Mode resource to the Data ONTAP 8 Cluster Mode destination resource. The policy also creates new export policies on the Cluster Mode destination resource for the cloned exports. StorageX performs this action as part of the Final Phase of the policy.

• StorageX can only clone volume exports to Data ONTAP 8.2 Cluster Mode resources and volume and qtree exports to Data ONTAP 8.3 Cluster Mode, ONTAP 9, or ONTAP 9.1 resources. StorageX cannot clone folder exports.

StorageX Administrator’s Guide 331

Page 350: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Migration Project operating system requirements6

Migration Project operating system requirementsFile storage resources included in Migration Projects must be running one of the following operating system versions:

Identifying Migration Project sources, destinations, and credentialsA s you identify the source and destination file storage resources you want to include in a Migration Project, complete the following steps:

1. Identify source and destination file storage resources that store the file data you want to migrate.

2. Verify that each source and destination file storage resource meets Migration Project operating system requirements. For more information, see “Migration Project operating system requirements” on page 332.

3. Obtain the following information for each file storage resource included in the project:

TABLE 32 Migration Project operating system requirements

Operating System Versions

Data ONTAP 7G • 7.3.1 V-Series• 7.3.2 or later NetApp Storage Systems

Data ONTAP 8 • 8.0.2 7-Mode• 8.0.3 7-Mode• 8.0.4 7-Mode• 8.0.5 7-Mode• 8.1 7-Mode• 8.1.1 7-Mode• 8.1.2 7-Mode• 8.2 Cluster Mode• 8.2 7-Mode• 8.3 Cluster Mode

NOTEStorageX does not support using FlexCache volumes as sources for Migration Projects.

ONTAP 9 • 9.0• 9.1

NOTEStorageX does not support using FlexGroups as sources or destinations for Migration Projects.

VNX OE for File • 7.1.47• 8.1

OneFS • 7.0.X• 7.1.X• 7.2.X• 8.0

332 StorageX Administrator’s Guide

Page 351: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Migration Projects 6

• IP address, NetBIOS name, or fully qualified domain name for each file storage resource

• Credentials for StorageX to use to communicate with the file storage resources. For more information about credentials, see “Adding the StorageX server service account to file storage resources” on page 71, “Configuring default credentials for file storage resources” on page 76, and “Configuring credentials for specific storage resources” on page 103.

4. Verify that each file storage resource you want to include in the Migration Project is configured correctly in the domain. For more information, see “Verifying file storage resource DNS configuration” on page 71.

5. Verify that each file storage resource you want to add to a Migration Project has been added to the My Resources folder in the Storage Resources view and displays correctly. For more information, see “Understanding the Storage Resources view” on page 67, “Adding storage resources” on page 80, and “Verifying storage resources” on page 117.

6. If a source or destination file storage resource does not currently display in the My Resources folder, add it. You can add file storage resources to the My Resources folder one at a time, or you can add multiple file storage resources at once by creating and importing a file storage resource import list. For more information about adding file storage resources to the My Resources folder, see “Adding storage resources” on page 80.

7. If you want to include VNX OE for File file storage resources as sources or VNX OE for File or OneFS file storage resources as destinations in Migration Projects, configure SSH for those file storage resources. For more information, see “Configuring StorageX to Use SSH Shell Credentials” on page 433.

8. If you will be migrating CIFS shared folders from source to destination file storage resources, verify that any CIFS shared folders on source file storage resources do not have any local users, local groups, or unresolved SIDs specified in the CIFS shared folder permissions on the source. For more information about how StorageX migrates security settings for CIFS shared folder with local users, local groups, or unresolved SIDs, see “Understanding Migration Project sources and destinations” on page 323.

Once all of the source and destination file storage resources that you want to include in the Migration Project display in the My Resources folder in the Storage Resources view, create the Migration Project. For more information, see “Creating Migration Projects” on page 333.

Creating Migration ProjectsCreate Migration Projects after you have identified the source and destination file storage resources you want to include in the project and verified that each source and destination has been added to StorageX for management and displays correctly in the My Resources folder in the Storage Resources view. For more information, see “Identifying Migration Project sources, destinations, and credentials” on page 332.

To create a Migration Project

1. In the StorageX Console, click the Migration Projects tab.

2. In the center pane, click Create Migration Projects.

3. In the Name field, type a unique name for the Migration Project.

4. In the Description field, type a description for the Migration Project.

5. In the Project Owner field, type the name of the Migration Project owner.

StorageX Administrator’s Guide 333

Page 352: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Adding sources and destinations to Migration Projects6

6. In the Project Start field, select a start date for the Migration Project, and in the Project End field, select an end date for the Migration Project.

NOTEThe dates specified in the Project Start and Project End fields are reference dates for you to use only to help you plan and manage Migration Projects. These dates are not used to by StorageX to execute the Migration Project or run any Phased Migration policies generated by the Migration Project. For more information about running Phased Migration policies generated by Migration Projects, see “Running Phased Migration policies immediately” on page 262 and “Scheduling Phased Migration policies” on page 263.

7. Click OK.

Adding sources and destinations to Migration ProjectsAfter creating a Migration Project, add source and destination file storage resources to the project.

NOTEFor more information about creating a Migration Project, see “Creating Migration Projects” on page 333.

To add sources and destinations to a Migration Project

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane, expand the folder for the Migration Project where you want to add source or destination file storage resources, and then complete the following steps:

NOTEBefore you can add a file storage resource to a Migration Project, the file storage resource must be managed by StorageX and display in the My Resources folder in the Storage Resources view. For more information about adding file storage resources to StorageX, see “Adding storage resources” on page 80.

a. If you want to add a source file storage resource to the Migration Project, right-click the Sources folder, and then click Add resources.

b. If you want to add a destination file storage resource to the Migration Project, right-click the Destinations folder, and then click Add resources.

c. In the Select Machines dialog box, select the file storage resource you want to add, and then click Open.

3. If you added Data ONTAP Vserver or SVM file storage resources to the Migration Project and you want to generate SnapMirror reports to help you identify SnapMirror relationships, ensure you include both the Vserver or SVM as well as the Vserver or SVM hosting resource to the Migration Project.

If you do not add both the Vserver or SVM as well as the Vserver or SVM hosting resource to the Migration Project, SnapMirror relationships for Vservers and SVMs will not be included in SnapMirror reports. For more information, see “Generating Data ONTAP SnapMirror reports” on page 338.

334 StorageX Administrator’s Guide

Page 353: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Project views 6

After adding source and destination file storage resources to a Migration Project, you can see summary and detailed information for file storage resources by clicking on the storage resource in the center pane. For more information, see “Understanding Migration Project views” on page 335.

Understanding Migration Project viewsMigration Project views help you plan your migration. StorageX provides the following Migration Project views:

• Migration Project Summary view. For more information, see “Using Migration Project Summary views” on page 335.

• Migration Project Source and Destination Summary view. For more information, see “Using Migration Project Source and Destination Summary views” on page 336.

• Migration Project Source and Destination Details view. For more information, see “Using Migration Project Source and Destination Detail views” on page 337.

Using Migration Project Summary viewsYou can view summary information for each Migration Project you create. Viewing summary information for a Migration Project helps you and others understand the nature and scope of the Migration Project.

Before you can view summary information for a Migration Project, you must create a Migration Project and add source and destination file storage resources to the project. For more information, see “Creating Migration Projects” on page 333 and “Adding sources and destinations to Migration Projects” on page 334.

To view Migration Project summary information

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane, under Migration Projects, browse to and then select a Migration Project.

3. Review the following information in the center pane:

General area

Displays general information about the Migration Project specified during project creation, such as the project name, description, project owner, and project start and end times.

Details area

Provides a Sources field and a Destinations field that display the list of source and destination file storage resources you added to the project.

4. In the center pane, in the Sources field, click a source, or in the Destinations field, click a destination. The results pane displays summary information for the selected file storage resource, such as total shares, hidden shares, domain information, IP addresses, platform information, and more.

5. If you have added multiple sources or destinations to the Migration Project, in the center pane under Sources or Destinations, select two or more file storage resources. The results pane displays aggregated information for the selected file storage resources using the following rules:

StorageX Administrator’s Guide 335

Page 354: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Project views6

• If StorageX can aggregate the properties for the selected file storage resources, StorageX displays the information. For example, if the file storage resources all belong to the same domain, StorageX displays the aggregated domain information in the Domain Name field when you select multiple file storage resources.

• If StorageX can add up the properties for the selected file storage resources, StorageX displays the information. For example, since StorageX can add up the total number of CIFS shared folders across file storage resources, StorageX displays the total number of CIFS shared folders in the Total shares field when you select multiple file storage resources.

• If StorageX cannot aggregate the properties for the selected file storage resources, StorageX does not display the information. For example, since aggregating IP addresses for file storage resources is not meaningful, StorageX does not display IP address aggregate information when you select multiple file storage resources.

6. If you expand the folders of the Migration Project folder in the left tree pane, the following subfolders display in the tree:

Sources

Click the Sources folder to display a list of source file storage resources for the Migration Project underneath the Sources folder in the tree view.

Destinations

Click the Destinations folder to display a list of destination file storage resources for the Migration Project.

Designs

Click the Designs folder to display a list of designs created for the Migration Project.

NOTEWhen you first create a Migration Project, the Sources, Destinations, and Designs folders are empty. Once you add sources and destinations to the project and create a one or more Migration Project designs, items display in the appropriate subfolders. For more information, see “Adding sources and destinations to Migration Projects” on page 334 and “Creating Migration Project designs” on page 339.

Using Migration Project Source and Destination Summary viewsAfter adding a file storage resource to a Migration Project as either a source or destination, when you click on the Sources or Destinations folder under the Migration Project in the left tree pane, you can view summary information about the source and destination file storage resources you have added to the project.

To view Migration Project source and destination summary information

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane under Migration Projects, browse to the Migration Project and then select either the Sources or Destinations folder.

3. In the center pane, in the Sources field, click a source, or in the Destinations field, click a destination. The results pane displays summary information for the selected file storage resource, such as total shares, hidden shares, domain information, IP addresses, platform information, and more.

336 StorageX Administrator’s Guide

Page 355: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Project views 6

4. If you have added multiple sources or destinations to the Migration Project, in the center pane under Sources or Destinations, select two or more file storage resources. The results pane displays aggregated information for the selected file storage resources using the following rules:

• If StorageX can aggregate the properties for the selected file storage resources, StorageX displays the information. For example, if the file storage resources all belong to the same domain, StorageX displays the aggregated domain information in the Domain Name field when you select multiple file storage resources.

• If StorageX can add up the properties for the selected file storage resources, StorageX displays the information. For example, since StorageX can add up the total number of CIFS shared folders across file storage resources, StorageX displays the total number of CIFS shared folders in the Total shares field when you select multiple file storage resources.

• If StorageX cannot aggregate the properties for the selected storage resources, StorageX does not display the information. For example, since aggregating IP addresses for file storage resources is not meaningful, StorageX does not display IP address aggregate information when you select multiple file storage resources.

Using Migration Project Source and Destination Detail viewsYou can view detailed information about source and destination file storage resources in a Migration Project after you add the file storage resources to the project. Viewing detailed information about sources and destinations in a Migration Project helps you better plan and understand your Migration Project.

To view source and destination details

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane under Migration Projects, browse to and then expand the folder for a Migration Project.

3. If you want to view detailed information for a source, expand the Sources folder and then click on the file storage resource.

4. If you want to view detailed information for a destination, expand the Destinations folder and then click on the file storage resource.

After you select a specific file storage resource listed in the left tree pane under the Sources or Destinations folder for a Migration Project, the following detailed information displays in the center pane:

CIFS Shares

Displays a list of CIFS shares on the file storage resource. When you select a specific CIFS shared folder in the center pane, in the results pane you can see information such as the number of current connections, the file system type, whether the shared folder is hidden, the local path to the shared folder, and more.

NFS Exports

Displays a list of NFS exports on the file storage resource. When you select a specific NFS export in the center pane, in the results pane you can see information about the file system permissions for the export.

Volumes

StorageX Administrator’s Guide 337

Page 356: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Generating Data ONTAP SnapMirror reports6

Displays a list of volumes on the file storage resource. When you select a specific volume in the center pane, in the results pane you can see information such as the number of CIFS shared folders or NFS exports on the volume, current connections, whether the share is hidden, and more. You can also see general information about the volume, such as aggregate information, number of disks, quota information, and amount of used space versus free space.

5. If you select multiple CIFS shared folders, NFS exports, or volumes for a storage resource in the center pane, StorageX displays aggregated or summarized information about the selected items using the following rules:

• If StorageX can aggregate the properties of the selected items, StorageX displays the aggregated information. For example, if the selected items are CIFS shared folders that all use NTFS as their file system, StorageX displays the aggregated file system information in the File System field when you select multiple storage resources.

• If StorageX can add up the properties for the selected items, StorageX displays the sum of the information. For example, since StorageX can add up the total number of current connections for CIFS shared folders, StorageX displays the total number of current connections in the Current Connections field when you select multiple storage resources.

• If StorageX cannot aggregate or add up the properties for the selected storage resources, StorageX does not display the information. For example, since aggregating the local path for CIFS shared folders isn’t meaningful, StorageX does not display local path information when you select multiple CIFS shared folders.

When you select one or more storage resources in the center pane, you can also specify if you want to view detailed information using categories or alphabetically by using the following options:

Categorized Results

Click the Categorized button to display storage resource details by category. For example, for CIFS shared folders and volumes, you can see detailed information organized into CIFS Resources, General information, NFS Resources, SnapMirror and SnapShot details and Storage Statistics categories. For NFS exports, you can see detailed information organized into a General category.

Alphabetical Results

Click the Alphabetical button to display storage resource details alphabetically without using categories.

Generating Data ONTAP SnapMirror reportsIf you have Data ONTAP file storage resources in a Migration Project, after you add Data ONTAP file storage resource sources to the Migration Project, you can generate SnapMirror reports.

SnapMirror reports allow you to identify any SnapMirror relationships that may exist between one or more of the source Data ONTAP file storage resources included in your Migration Project and other Data ONTAP file storage resources in your environment.

You can use SnapMirror reports in the following ways:

• To help ensure that you understand any SnapMirror relationships on your sources

• To help you determine if you have additional file storage resources that should be added to the Migration Project

338 StorageX Administrator’s Guide

Page 357: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Migration Project designs 6

• To help you reestablish SnapMirror relationship as needed after a migration.

SnapMirror reports use a tab-separated value (.tsv) file format. The .tsv file format is a simple file format that is widely supported across different computer programs and platforms.

If you have included Data ONTAP Vservers or SVMs in the Migration Project and you want to generate SnapMirror reports, ensure you have added both the Vserver or SVM as well as the Vserver or SVM hosting resource to the Migration Project. If you do not include both the Vserver or SVM as well as the Vserver or SVM hosting resource to the Migration Project, SnapMirror relationships for Vservers and SVMs will not be included in the report. For more information, see “Adding sources and destinations to Migration Projects” on page 334.

If you want to include schedule information for a specific SnapMirror in a SnapMirror report, ensure you have added the Data ONTAP resource that is the destination of the SnapMirror relationship both to My Resources and to the Migration Project. StorageX can only retrieve SnapMirror schedule information from the SnapMirror destination resource.

To generate a SnapMirror report

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane under Migration Projects, browse to and then right-click the Migration Project for which you want to generate a SnapMirror report.

3. Click Generate SnapMirror Report.

4. In the File name field, type a name for the SnapMirror report you want to generate.

5. In the File location field, type the UNC path for the location where you want to save the SnapMirror report or click Browse to browse to and select the folder where you want to save the report. The user account you use to run the StorageX Console must have permissions to write to the folder you specify.

6. Click OK.

7. When Download Completed displays in the StorageX Download dialog box, click Open to open the .tsv file that contains the SnapMirror report using Microsoft Excel or any other application that supports the .tsv file format.

Creating Migration Project designsYou can create one or more Migration Project designs for a Migration Project.

Before you can create a Migration Project design, you must create a Migration Project and add source and destination file storage resources to the project. For more information, see “Understanding Migration Project designs” on page 326, “Creating Migration Projects” on page 333, and “Adding sources and destinations to Migration Projects” on page 334.

When you create Migration Project designs, you can create the following types of Migration Project designs:

Like-to-Like Migration Project designsCreate Like-to-Like Migration Project designs when you want to create destination items on destination file storage resources that are similar to the source items on the source file storage resources. For more information about Like-to-Like Migration Project designs, see “Understanding Migration Project designs” on page 326. For more information about creating Migration Project designs, see “Creating Like-to-Like Migration Project designs” on page 342.

StorageX Administrator’s Guide 339

Page 358: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Migration Project designs6

Advanced Migration Project designsCreate Advanced Migration Project designs when you want to transform the way you store your file data and create items on destination file storage resources that are different from the source items on the source file storage resource. For more information about Advanced Migration Project designs, see “Understanding Migration Project designs” on page 326. For more information about creating Advanced Migration Project designs, see “Creating Advanced Migration Project designs” on page 349.

ATTENTIONEnsure that you review Migration Project design planning considerations before creating Migration Project designs. For more information, see “Migration Project design planning considerations” on page 340

Migration Project design planning considerationsWhen you create Migration Project designs, ensure you take the following points into consideration:

• Do not create Migration Project designs with overlapping sources.

Since you can create multiple Migration Project designs for a Migration Project, ensure you do not create designs with overlapping sources. If you have overlapping sources in different Migration Project designs, this can result in the same file data in more than one destination. If you do have overlapping sources within a single Migration Project design, StorageX can detect this and display a warning. However, StorageX cannot detect and warn when you have overlapping sources across multiple Migration Project designs. StorageX can only detect if a destination volume mapped to a source has already been created on the destination file storage resource and prompt you to change the name of the destination volume. This capability does not prevent you from having duplicate copies of file data if you have overlapping sources in different Migration Project designs.

• Do not mix security styles or CIFS access-checking policy styles in Migration Project designs. Consider the following points:

• If you have Data ONTAP file storage resources in your Migration Project with volumes and qtrees that have different security styles, create different Migration Project designs so you can group items that use the same security style together. With this approach, you can specify the appropriate protocol for StorageX to use (CIFS or NFS) when executing the Migration Project design and generating the Phased Migration policies that StorageX will use to migrate the file data.

For example, assume that you have Data ONTAP file storage resources as sources in your Migration Project. Next assume that the volumes and qtrees on the Data ONTAP source file storage resources included in your migration project use a mixture of NTFS and UNIX security styles.

In this scenario, create two Migration Project designs for your Migration Project. In your first Migration Project design, include all of the Data ONTAP volumes and qtrees with NTFS as their security style in one design. When you execute this design, specify that you want to use the CIFS protocol to copy the data.

In your second Migration Project design, include all of the Data ONTAP volumes and qtrees with UNIX as their security style in the design. When you execute the second design, specify that you want to use the NFS protocol to copy the data.

340 StorageX Administrator’s Guide

Page 359: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Migration Project designs 6

You can see the security style used by Data ONTAP volumes in the Migration Projects view when you select a file storage resource in the Sources folder in the left tree pane, and then select a volume in the center pane. When you select a volume in the center pane, the security style used by the volume displays in the right pane in the Security Style field.

You can also see the security style used for a Data ONTAP volume in the New Migration Project Design Wizard on the Specify Sources dialog box when creating a Like-to-Like Migration Project design or in the Select Sources for New Design dialog box when creating an Advanced Migration Project design. When you select a volume in one of these dialog boxes, the security style used by the volume displays in the right pane in the Security Style field.

You can see the security style used by a qtree in the New Migration Project Design Wizard on the Specify Sources dialog box when creating a Like-to-Like Migration Project design or in the Select Sources for New Design dialog box when creating an Advanced Migration Project design. When you select a qtree on the Specify Sources dialog box, the security style used by the qtree displays in the right pane in the Security Style field.

You can also filter by security style in the Specify Sources dialog box when creating a Like-to-Like Migration Project design or in the Select Sources for New Design dialog box when creating an Advanced Migration Project design by right-clicking a volume or qtree and then selecting the appropriate filtering option. For more information about filtering by security style when creating Migration Project designs, see “Creating Like-to-Like Migration Project designs” on page 342 and “Creating Advanced Migration Project designs” on page 349.

• If you have a VNX OE for File destination in a Migration Project and you will be creating a large number of file systems and tree quotas on the VNX OE for File destination, ensure you allow sufficient time for StorageX to execute the design and create the file systems and tree quotas on the destination.

• As a general rule, try not to include too many source and destination mappings in each Migration Project design. Limiting the number of source and destination mappings in Migration Project designs makes it easier to manage the designs. Limiting the number of source and destination mappings also makes it easier to roll back if a Migration Project design execution fails. For more information about rolling back a failed Migration Project design execution, see “Rolling back when a Migration Project design execution fails” on page 366.

• If you want to migrate a volume allocated to a Data ONTAP vFiler as a part of your Migration Project, first ensure that you have included the vFiler as a source in the Migration Project. When you specify the vFiler as a source in your Migration Project, you can then specify the vFiler as a source in your Migration Project design, as well as specify a destination for the volume allocated to the vFiler in your Migration Project. If you select the Data ONTAP file storage resource that hosts the volume allocated to the vFiler instead of the vFiler itself, you will not be able to view or select the volume allocated to the vFiler as a source when you specifying sources in the Migration Project design.

StorageX Administrator’s Guide 341

Page 360: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Migration Project designs6

Creating Like-to-Like Migration Project designsCreate Like-to-Like Migration Project designs when you want to create destination items on destination file storage resources that are identical to the source items on the source file storage resources. For example, create Like-to-Like Migration Project designs when you want to perform the following types of migrations:

• Your source is a Data ONTAP file storage resource and you want to perform the following tasks:

• Migrate file data from Data ONTAP volumes to volumes on aggregates on new Data ONTAP file storage resources, to volumes in storage pools on VNX OE for File file storage resources, or to the /ifs folder on OneFS file storage resources.

• Migrate file data from Data ONTAP qtrees to volumes on Data ONTAP file storage resources, to file systems on VNX OE for File file storage resources, or to the /ifs folder on OneFS file storage resources.

• Your source is a VNX OE for File file storage resource and you want to perform the following tasks:

• Migrate file data from VNX OE for File file systems to volumes on aggregates on Data ONTAP file storage resources, or to the /ifs folder on OneFS file storage resources.

• Migrate file data in tree quotas on VNX OE for File file storage resources to qtrees on volumes on Data ONTAP file storage resources or to the /ifs folder on OneFS file storage resources.

• Your source is a OneFS file storage resource and you want to perform the following tasks:

• Migrate folders under the /ifs folder on OneFS file storage resources to volumes on aggregates on Data ONTAP file storage resources, to file systems in storage pools on VNX OE for File file storage resources, or to the /ifs folder on new OneFS file storage resources.

• Migrate folders under the /ifs folder on OneFS file storage resources to qtrees on volumes on Data ONTAP file storage resources.

Before you can create a Migration Project design, you must create a Migration Project and add source and destination file storage resources to the project. For more information, see “Understanding Migration Project designs” on page 326, “Creating Migration Projects” on page 333, and “Adding sources and destinations to Migration Projects” on page 334. Also ensure that you review Migration Project design planning considerations before creating Migration Project designs. For more information, see “Migration Project design planning considerations” on page 340.

To create a Like-to-Like Migration Project design

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane, expand Migration Projects > Projects > MigrationProjectName, where MigrationProjectName is the name of your Migration Project, and then click Designs.

3. In the center pane, click Create Like-to-Like Migration Project Design.

4. Review the welcome message, and then click Next.

5. Type a unique name and a description for the Migration Project design, and then click Next.

6. Select the source file storage resources you want to include in the design by selecting the source items you want to migrate.

For example, you can select the following types of items:

342 StorageX Administrator’s Guide

Page 361: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Migration Project designs 6

• One or more volumes on a Data ONTAP or VNX OE for File file storage resource

• One or more qtrees on a Data ONTAP file storage resource

• A VNX OE for File file system or one or more tree quotas on a VNX OE for File file storage resource

• One or more folders under the /ifs folder on a OneFS file storage resource

If you have sources that use the NTFS, Unix, or Mixed security styles, create separate designs for each security style. For example, for sources that have some volumes that use the NTFS security style and other volumes that use the Unix security style, create two separate Migration Project designs, where the first design is for items that use the NTFS security style, and the second design is for items that use the Unix security style.

For more information, see “Migration Project design planning considerations” on page 340.

As you create your design, you can apply filters to your sources to help you better understand the different types of security styles that may be in use on the source items you have included in your design. However, when you apply these filters, it is important that you understand that you are not actually filtering items out of your design. You are only using filters to help you view and analyze your source items. If you see when you apply filters that there are items on the source that you do not want to include in your design, ensure you clear the check box in front of these items.

For example, assume you have source Data ONTAP file storage resources where some volumes and qtrees use the NTFS security style and other volumes and qtrees use the Unix security style. In this scenario, first create a Migration Project design that includes only the items that use the NTFS security style by completing the following steps:

a. If you want to include only the volumes on a file storage resource that use the NTFS security style in your design and you do not want to include any qtrees in the design, click the plus (+) symbol in front of the file storage resource to display the volumes. Then right-click the file storage resource, and click Filter by Security Style > Show Only Volumes with NTFS security style. Then right-click each volume and click Select only the volume but not the underneath Qtrees. When you click Select only the volume but not the underneath Qtrees, the check box in front of the volume is selected, and the check boxes in front of each qtree are not selected. Only the volume is then included in the design.

b. If you want to include only the qtrees on the file storage resource that use the NTFS security style in your design and you do not want to include any volumes in the design, right-click the file storage resource, and then click Filter by Security Style > Qtrees Filter > Show Only Qtrees with NTFS security style. Then select the check box in front of each qtree to include the qtree in your Migration Project design. Only the qtrees that you select are included in the design.

c. If you want to include both the volumes and qtrees on a file storage resource that use the NTFS security style in your design, right-click the file storage resource, and then click Filter by Security Style > Show Only Volumes with NTFS security style to view only the volumes on the file storage resource that use the NTFS security style. Then right-click the file storage resource again and then click Filter by Security Style > QTrees Filter > Show Only Qtrees with NTFS security style. Then select the check box in front of each volume and qtree you want to include in your Migration Project design. Only the volumes and qtrees you select will be included in the design.

Then create a second Migration Project design that includes only the items that use the Unix security style.

7. Click Next.

StorageX Administrator’s Guide 343

Page 362: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Migration Project designs6

8. On the Specify Destinations dialog box, under Source, select your source.

9. If your source is a volume on a Data ONTAP file storage resource, specify a destination by completing the following steps:

a. Click Browse, and then browse to and select the location on the destination file storage resource where you want StorageX to create the appropriate destination item.

b. If the destination is another Data ONTAP file storage resource, in the Container field, select the aggregate on the destination Data ONTAP file storage resource where you want StorageX to create the destination volume for the file data migration.

c. If the destination is a VNX OE for File file storage resource, in the Container field, select the storage pool on the destination VNX OE for File file storage resource where you want StorageX to create the destination volume for the file data migration.

d. If the destination is a OneFS file storage resource, select the destination OneFS file storage resource where you want StorageX to create the destination folder for the file data migration.

e. If the destination is a OneFS file storage resource, specify the path on the destination you want to use when migrating. By default, the path is /ifs/volume, where volume is the name of the volume on the source. To configure a path other than the default, click Destination Path and specify the path you want to use. For example, you could change the default root path to /ifs/data, in which case the full path would be /ifs/data/volume.

f. If the destination is a OneFS file storage resource and you want to use the same destination path setting for all valid resources, click Apply these settings to all valid sources.

g. If you want to use the same destination for all of your sources, after you have specified your first source and destination mapping, click Apply this destination to all sources to apply this mapping to all of the sources and destinations in the project.

h. If the destination is an aggregate on a Data ONTAP file storage resource or a storage pool on a VNX OE for File file storage resource and you want to change the additional percentage specified for the total volume size, click Increase the destination volume by the following percentage, and then adjust the percentage up or down. By default, StorageX specifies a 20% as the additional percentage specified for the total volume size.

i. If the destination is an aggregate on a Data ONTAP file storage resource or a storage pool on a VNX OE for File file storage resource and you want to use the same percentage you specified on all of destination volumes in the Migration Project, click Apply this setting to all volume sources.

j. If the destination is an aggregate on a Data ONTAP file storage resource and you want to create a destination volume using a specific snapshot reserve, space guarantee, or volume size, click Use the following settings, and then specify the appropriate setting for each option. For more information about the options available for each setting, click the Help button on the dialog box.

k. If the destination is a storage pool on a VNX OE for File file storage resource and you want to create a destination volume using a specific space guarantee or volume size, click Use the following settings, and then specify the appropriate setting for each option.

NOTEThe Snapshot Reserved % option does not apply to VNX OE for File file storage resources.

344 StorageX Administrator’s Guide

Page 363: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Migration Project designs 6

l. If the source is a Data ONTAP 7 file storage resource or Data ONTAP 8 7-Mode file storage resource, the destination is a Data ONTAP 8.2 Cluster Mode, Data ONTAP 8.3 Cluster Mode, ONTAP 9, or ONTAP 9.1 file storage resource, and you want to use SnapMirror for replication instead of the StorageX universal data engine, click Use SnapMirror.

NOTEYou can only configure StorageX to use SnapMirror to replicate data from a source to a destination if the source is a Data ONTAP 7 or Data ONTAP 8 7-Mode file storage resource and the destination is a Data ONTAP 8.2 Cluster Mode, Data ONTAP 8.3 Cluster Mode, ONTAP 9, or ONTAP 9.1 file storage resource. For other resource types in Migration Projects, you must use the StorageX universal data engine.

m. If you have multiple Data ONTAP 7 or Data ONTAP 8 7-Mode sources and Data ONTAP 8.2 Cluster Mode, Data ONTAP 8.3 Cluster Mode, ONTAP 9, or ONTAP 9.1 destinations, and you want to use SnapMirror for replication instead of the StorageX universal data engine for all applicable sources and destinations, click Apply this setting to all valid volume pairs.

For more information about the options available for each setting, click the Help button on the dialog box.

10. If the source is a qtree on a Data ONTAP file storage resource, complete the following steps:

a. Click Browse, and then browse to and select the location on the destination file storage resource where you want StorageX to create the appropriate destination item.

b. If the destination is another Data ONTAP file storage resource, browse to and select the volume on the destination Data ONTAP file storage resource where you want StorageX to create the destination qtree for the file data migration.

c. If the destination is a VNX OE for File file storage resource, browse to and select the VNX OE for File file system on the VNX OE for File file storage resource where you want StorageX to create the destination tree quota for the file data migration.

d. If the destination is a OneFS file storage resource, select the destination OneFS file storage resource where you want StorageX to create the destination folder for the file data migration.

e. If the destination is a OneFS file storage resource, specify the path on the destination you want to use when migrating. By default, the path is /ifs/volume, where volume is the name of the volume on the source. To configure a path other than the default, click Destination Path and specify the path you want to use. For example, you could change the default root path to /ifs/data, in which case the full path would be /ifs/data/volume.

f. If the destination is a OneFS file storage resource and you want to use the same destination path setting for all valid resources, click Apply these settings to all valid sources.

g. If you want to use the same destination for all of your sources, after you have specified your first source and destination mapping, click Apply this destination to all sources to apply this mapping to all of the sources and destinations in the project.

11. If your source is a volume on a VNX OE for File file storage resource, specify a destination by completing the following steps:

StorageX Administrator’s Guide 345

Page 364: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Migration Project designs6

a. Click Browse, and then browse to and select the location on the destination file storage resource where you want StorageX to create the appropriate destination item.

b. If the destination is a Data ONTAP file storage resource, in the Container field, select the aggregate on the Data ONTAP file storage resource where you want StorageX to create the destination volume for the file data migration.

c. If the destination is a OneFS file storage resource, select the destination OneFS file storage resource where you want StorageX to create the destination folder for the file data migration.

d. If the destination is a OneFS file storage resource, specify the path on the destination you want to use when migrating. By default, the path is /ifs/volume, where volume is the name of the volume on the source. To configure a path other than the default, click Destination Path and specify the path you want to use. For example, you could change the default root path to /ifs/data, in which case the full path would be /ifs/data/volume.

e. If the destination is a OneFS file storage resource and you want to use the same destination path setting for all valid resources, click Apply these settings to all valid sources.

f. If you want to use the same destination and container settings for all of the source and destination mappings in the project, after you have specified your first source and destination mapping and container settings, click Apply this destination to all sources to apply the settings to all the source and destination mappings in the project.

g. If your destination is an aggregate on a Data ONTAP file storage resource or a storage pool on a VNX OE for File file storage resource and you want to change the additional percentage specified for the total volume size, click Increase the destination volume by the following percentage, and then adjust the percentage up or down. By default, StorageX specifies a 20% as the additional percentage specified for the total volume size.

h. If your destination is an aggregate on a Data ONTAP file storage resource and you want to use the same percentage you specified on all of destination volumes in the Migration Project, click Apply this setting to all volume sources.

i. If your destination is an aggregate on a Data ONTAP file storage resource and you want to create a destination volume using a specific snapshot reserve, space guarantee, or volume size, click Use the following settings, and then specify the appropriate setting for each option. For more information about the options available for each setting, click the Help button on the dialog box.

12. If your source is a tree quota on a VNX OE for File file storage resource, complete the following steps:

a. Click Browse, and then browse to and select the location on the destination file storage resource where you want StorageX to create the appropriate destination item.

b. If the destination is another Data ONTAP file storage resource, select the volume on the destination Data ONTAP file storage resource where you want StorageX to create the destination qtree for the file data migration.

c. If the destination is a OneFS file storage resource, select the /ifs folder on a destination OneFS file storage resource where you want StorageX to create the destination folder for the file data migration.

346 StorageX Administrator’s Guide

Page 365: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Migration Project designs 6

d. If the destination is a OneFS file storage resource, specify the path on the destination you want to use when migrating. By default, the path is /ifs/volume, where volume is the name of the volume on the source. To configure a path other than the default, click Destination Path and specify the path you want to use. For example, you could change the default root path to /ifs/data, in which case the full path would be /ifs/data/volume.

e. If the destination is a OneFS file storage resource and you want to use the same destination path setting for all valid resources, click Apply these settings to all valid sources.

f. If you want to use the same destination for all of your sources, after you have specified your first source and destination mapping, click Apply this destination to all sources to apply this mapping to all of the sources and destinations in the project.

13. If your source is a folder on a OneFS file storage resource, specify a destination by completing the following steps:

a. Click Browse, and then browse to and select the location on the destination file storage resource where you want StorageX to create the appropriate destination item.

b. If the destination is another OneFS file storage resource, select the destination OneFS file storage resource where you want StorageX to create the destination folder for the file data migration. By default, the path is /ifs/folder, where folder is the name of the subfolder on the source. To configure a path other than the default, click Destination Path and specify the path you want to use. For example, you could change the default root path to /ifs/data, in which case the full path would be /ifs/data/folder.

c. If the destination is another OneFS file storage resource and you want to use the same destination path setting for all valid resources, click Apply these settings to all valid sources.

d. If the destination is a Data ONTAP file storage resource, in the Container field, select the aggregate on the destination Data ONTAP file storage resource where you want StorageX to create the destination volume for the file data migration. By default, the name of the destination volume will be the same as the name of the specified folder on the source OneFS file storage resource.

e. If the destination is a Data ONTAP file storage resource, and you select a volume on the destination resource, StorageX will migrate the folder into a qtree under that volume.

f. If the destination is a VNX OE for File file storage resource, in the Container field, select the storage pool on the destination VNX OE for File file storage resource where you want StorageX to create the destination volume for the file data migration. By default, the name of the destination volume will be the same as the name of the specified folder on the source OneFS file storage resource.

g. If you want to use the same destination for all of your sources, after you have specified your first source and destination mapping, click Apply this destination to all sources to apply this mapping to all of the sources and destinations in the project.

h. If the destination is an aggregate on a Data ONTAP file storage resource or a storage pool on a VNX OE for File file storage resource and you want to change the additional percentage specified for the total volume size, click Increase the destination volume by the following percentage, and then adjust the percentage up or down. By default, StorageX specifies a 20% as the additional percentage specified for the total volume size.

StorageX Administrator’s Guide 347

Page 366: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Migration Project designs6

i. If the destination is an aggregate on a Data ONTAP file storage resource or a storage pool on a VNX OE for File file storage resource and you want to use the same percentage you specified on all of destination volumes in the Migration Project, click Apply this setting to all volume sources.

j. If the destination is an aggregate on a Data ONTAP file storage resource and you want to create a destination volume using a specific snapshot reserve, space guarantee, or volume size, click Use the following settings, and then specify the appropriate setting for each option. For more information about the options available for each setting, click the Help button on the dialog box.

k. If the destination is a storage pool on a VNX OE for File file storage resource and you want to create a destination volume using a specific space guarantee or volume size, click Use the following settings, and then specify the appropriate setting for each option.

NOTEThe Snapshot Reserved % option does not apply to VNX OE for File file storage resources.

14. Click Migration Mode and select the protocol you want StorageX to use to copy the data from the source to the destination.

If you want to use the CIFS protocol to copy the data, select Using CIFS from the drop-down box.

If you want to use the NFS protocol to copy the data, select Using NFS from the drop-down box.

If you want to use the same protocol for all valid sources and destinations, click Apply this setting to all pairs.

The protocol you specify will be used to copy data across all sources and destinations included in the Migration Project. For more information about each option, click the Help button on the dialog box.

15. Click Next.

16. Review your Migration Project design, and then click Finish.

The Migration Project design displays under Designs folder under the Migration Project in the left tree pane. Click the Migration Project design and review the details of your design in the center pane.

When you review your Migration Project design, in the General area you can see the name and description you specified for your design, as well as the design state and the validation result.

When you first create a Migration Project design, the Design State field displays a value of In Design. After you validate your design, this is updated to Validated, and after you execute your design, the Design State field updates to Executed.

When you first create a Migration Project design, the Validate Result field displays and shows the number of validated source and destination pairs. For example, assume you create a Migration project design with 20 source and destination pairs. When you first create the Migration Project design, the Design State displays as In Design, and the Validation Result displays as Validated 0 of 20. After you validate the Migration Project design, the Design State displays as Validated, and the Validation Results displays as Validated 15 of 20. This means that five of your source and destination pairs have one or more problems. You can see the warnings or errors associated with each of the five source and destination pairs that did not pass validation in the Details area.

348 StorageX Administrator’s Guide

Page 367: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Migration Project designs 6

In the Details area, you can see additional details about the sources and destinations included in your Migration Project design, as well as filter on both source and destination storage resources. By default, file storage resources are grouped by source. If you expand a source, in the Description field you can see a description of the source, as well as its destination mapping and any migration settings you specified during the migration design, such as an additional percentage for volume size on the destination.

The Message field is blank when you first create a Migration Project design, but after you validate the design, it displays a validation message for the selected source and destination pair. If the rules StorageX uses to validate a Migration Project design detect a problem with the design, StorageX displays information about which rule was broken.

The Category field is also blank when you first create a Migration Project, but after you validate the design, if the rules StorageX uses to validate a Migration Project design detect a problem with the design, the Category field displays the category of the rule that was broken.

After you create a Migration Project design, you can then perform the following actions:

• Export the design. For more information, see “Exporting Migration Project designs” on page 354.

• Validate the design. For more information, see “Validating Migration Project designs” on page 354.

Creating Advanced Migration Project designsCreate an Advanced Migration Project design when you want to transform your file data while migrating file data from sources to destinations. For example, create Advanced Migration Project designs for the following scenarios:

• You want to transform a qtree on a source Data ONTAP file storage resource to a volume on a destination Data ONTAP file storage resource.

• You want to transform a qtree on a source Data ONTAP file storage resource to a file system on a destination VNX OE for File file storage resource or to a folder under the /ifs folder on a destination OneFS file storage resource.

• You want to transform a tree quota on a source VNX OE for File file storage resource to a volume on a destination Data ONTAP file storage resource or to a folder under the /ifs folder on a destination OneFS file storage resource

• You want to transform a tree quota on a source VNX OE for File file storage resource to a file system on a destination VNX OE for File.

Before you can create a Migration Project design, you must create a Migration Project and add source and destination file storage resources to the project. For more information, see “Understanding Migration Project designs” on page 326, “Creating Migration Projects” on page 333, and “Adding sources and destinations to Migration Projects” on page 334. Also ensure that you review Migration Project design planning considerations before creating Migration Project designs. For more information, see “Migration Project design planning considerations” on page 340.

To create an Advanced Migration Project design

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane, expand Migration Projects > Projects > MigrationProjectName, where MigrationProjectName is the name of your Migration Project, and then click Designs.

StorageX Administrator’s Guide 349

Page 368: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Migration Project designs6

3. In the center pane, click Create Advanced Migration Project Design.

4. Select the source file storage resources you want to include in the design by selecting the source items you want to migrate.

If you have sources that use the NTFS, Unix, or Mixed security styles, create separate designs for each security style. For example, for sources that have some volumes that use the NTFS security style and other volumes that use the Unix security style, create two separate Migration Project designs, where the first design is for items that use the NTFS security style, and the second design is for items that use the Unix security style.

If you have VNX OE for File file storage resources in your Migration Project with file systems that have different CIFS access-checking policy styles, create different Migration Project designs so you can group items that use the same CIFS access-checking policy styles together.

For more information, see “Migration Project design planning considerations” on page 340.

As you create your design, you can apply filters to your sources to help you better understand the different types of security styles that may be in use on the source items you have included in your design. However, when you apply these filters, it is important that you understand that you are not actually filtering items out of your design. You are only using filters to help you view and analyze your source items. If you see when you apply filters that there are items on the source that you do not want to include in your design, ensure you clear the check box in front of these items.

For example, assume you have source Data ONTAP file storage resources where some volumes and qtrees use the NTFS security style and other volumes and qtrees use the Unix security style. In this scenario, first create a Migration Project design that includes only the items that use the NTFS security style by completing the following steps:

a. If you want to include only the volumes on a file storage resource that use the NTFS security style in your design and you do not want to include any qtrees in the design, click the plus (+) symbol in front of the file storage resource to display the volumes. Then right-click the file storage resource, and click Filter by Security Style > Show Only Volumes with NTFS security style. Then right-click each volume and click Select only the volume but not the underneath Qtrees. When you click Select only the volume but not the underneath Qtrees, the check box in front of the volume is selected, and the check boxes in front of each qtree are not selected. Only the volume is then included in the design.

b. If you want to include only the qtrees on the file storage resource that use the NTFS security style in your design and you do not want to include any volumes in the design, right-click the file storage resource, and then click Filter by Security Style > Qtrees Filter > Show Only Qtrees with NTFS security style. Then select the check box in front of each qtree to include the qtree in your Migration Project design. Only the qtrees that you select are included in the design.

c. If you want to include both the volumes and qtrees on a file storage resource that use the NTFS security style in your design, right-click the file storage resource, and then click Filter by Security Style > Show Only Volumes with NTFS security style to view only the volumes on the file storage resource that use the NTFS security style. Then right-click the file storage resource again and then click Filter by Security Style > QTrees Filter > Show Only Qtrees with NTFS security style. Then select the check box in front of each volume and qtree you want to include in your Migration Project design. Only the volumes and qtrees you select will be included in the design.

Then create a second Migration Project design that includes only the items that use the Unix security style.

350 StorageX Administrator’s Guide

Page 369: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Migration Project designs 6

Now assume that you have source VNX OE for File file storage resources where some file systems have NT as their CIFS access-checking policy style and other file systems have UNIX as their CIFS access-checking policy style. In this scenario, first create a Migration Project design that includes only the file systems that use NT as their CIFS access-checking policy style by completing the following steps:

a. If you want to include only the file systems on a file storage resource that use the NT access-checking policy style in your design, right-click the file storage resource, and then click Show Only File Systems with NT Access Checking Policy. Then right-click each file system and click Select only the File System but not the underneath Tree Quotas. When you click Select only the File System but not the underneath Tree Quotas, the check box in front of the file system is selected, and the check boxes in front of each tree quota are not selected. Only the file system is then included in the design.

b. If you want to include only the tree quotas on the file storage resource that use the NT access-checking policy style in your design and you do not want to include any file systems in the design, right-click the file storage resource, and then click Show Only File Systems with NT Access Checking Policy. Then right-click each file system and click Select all the underneath Tree Quotas only. Then select the check box in front of each tree quota to include the tree quota in your Migration Project design. Only the tree quotas that you select are included in the design.

c. If you want to include both the file systems and tree quotas on a file storage resource that use the NT access-checking policy style in your design, right-click the file storage resource, and then click Show Only File Systems with NT Access Checking Policy to view only the file systems on the file storage resource that use the NT access-checking policy style. Then right-click the file storage resource again. Click Select only the File System but not the underneath Tree Quotas, and then select the check box in front of each file system and tree quota you want to include in your Migration Project design. Only the file systems and tree quotas you select will be included in the design.

Then create a second Migration Project design that includes only the items that use the Unix access-checking policy style.

5. Click OK.

6. In the Design Name field, specify a name for the Migration Project design, and in the Design Description field, specify a description for the Migration Project design.

7. Review the information displayed in each of the columns. For more information about the information displayed in each of the columns, click the Help button on the dialog box.

8. Specify missing information for any columns that display in red. Columns that display in red must be completed before you can close the dialog box. Columns that display in gray do not apply to the selected destination.

9. Freeze or unfreeze the source columns as needed by clicking Freeze/Unfreeze Source Columns.

10. Sort columns, add or remove columns, and group by columns by right-clicking in a column heading and then selecting the appropriate option.

11. If you want to apply filters to the grid, right-click in a column heading, click Filter Editor, specify the filter you want to use, and then click OK. After you create your filter, StorageX applies the filter and displays information in the grid based on your filter settings. Your current filter settings display in the bottom grid.

StorageX Administrator’s Guide 351

Page 370: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Migration Project designs6

12. If you want to search across settings, complete the following steps:

a. Right-click in a column heading, and then click Show Find Panel.

b. Type your search string into the search field, and then click Find.

13. If you want to export your Migration Project design to a Microsoft Excel file, a CSV file, or a PDF file, click Export and then save your Migration Project design. For more information about exporting Migration Project designs, see “Exporting Migration Project designs” on page 354.

14. When you are done working with your design, click OK.

15. If you have applied a filter to the grid, StorageX will display a message informing you that a filter is currently applied to the grid.

If you want to include all items included in the Migration Project design, including items that may not currently display in the grid because of applied filters, click Yes.

If you want to include only the items currently displayed in the grid in the Migration Project design, and you do not want to include other items that are included in the design but that StorageX currently does not display in the grid because of applied filters, click No.

The Migration Project design displays under Designs folder under the Migration Project in the left tree pane. Click the Migration Project design and review the details of your design in the center pane.

When you review your Migration Project design, in the General area you can see the name and description you specified for your design, as well as the design state and the validation result.

When you first create a Migration Project design, the Design State field displays a value of In Design. After you validate your design, this is updated to Validated, and after you execute your design, the Design State field updates to Executed.

When you first create a Migration Project design, the Validate Result field displays and shows the number of validated source and destination pairs. For example, assume you create a Migration project design with 20 source and destination pairs. When you first create the Migration Project design, the Design State displays as In Design, and the Validation Result displays as Validated 0 of 20. After you validate the Migration Project design, the Design State displays as Validated, and the Validation Results displays as Validated 15 of 20. This means that five of your source and destination pairs have one or more problems. You can see the warnings or errors associated with each of the five source and destination pairs that did not pass validation in the Details area.

In the Details area, you can see additional details about the sources and destinations included in your Migration Project design, as well as filter on both source and destination storage resources. By default, file storage resources are grouped by source. If you expand a source, in the Description field you can see a description of the source, as well as its destination mapping and any migration settings you specified during the migration design, such as an additional percentage for volume size on the destination.

The Message field is blank when you first create a Migration Project design, but after you validate the design, it displays a validation message for the selected source and destination pair. If the rules StorageX uses to validate a Migration Project design detect a problem with the design, StorageX displays information about which rule was broken.

The Category field is also blank when you first create a Migration Project, but after you validate the design, if the rules StorageX uses to validate a Migration Project design detect a problem with the design, the Category field displays the category of the rule that was broken.

After you create a Migration Project design, you can then perform the following actions:

352 StorageX Administrator’s Guide

Page 371: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Editing and specifying advanced options for Migration Project designs 6

• Export the design. For more information, see “Exporting Migration Project designs” on page 354.

• Validate the design. For more information, see “Validating Migration Project designs” on page 354.

Editing and specifying advanced options for Migration Project designsAfter you create a Migration Project design, you can edit and specify advanced options for an existing Migration Project design.

For example, you can edit or specify advanced options for an existing Migration Project design when you want to change or update some of the settings specified for the design based on your review of the design.

NOTEYou can only edit or specify advanced options for an existing Migration Project design if you have not yet executed the Migration Project design. You cannot edit or specify advanced options for an existing Migration Project design once you execute the design. For more information about executing an existing Migration Project design, see “Executing Migration Project designs” on page 363.

This topic explains how to edit or specify advanced options for Migration Project designs. For more information about creating Migration Project designs, see “Creating Migration Project designs” on page 339.

To edit or specify advanced options for an existing Migration Project design

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane, browse to and then select the Migration Project design where you want to edit options or specify advanced options.

3. In the center pane, click Advanced Options.

4. Review and modify the information displayed in each of the columns as needed based on your requirements. For more information about the information displayed in each of the columns, click the Help button on the dialog box.

5. Specify missing information for any columns that display in red. Columns that display in red must be completed before you can close the dialog box. Columns that display in gray do not apply to the selected destination.

6. Freeze or unfreeze the source columns as needed by clicking Freeze/Unfreeze Source Columns.

7. Sort columns, add or remove columns, and group by columns by right-clicking in a column heading and then selecting the appropriate option.

8. If you want to apply filters to the grid, right-click in a column heading, click Filter Editor, specify the filter you want to use, and then click OK. After you create your filter, StorageX applies the filter and displays information in the grid based on your filter settings. Your current filter settings display in the bottom grid.

9. If you want to search across settings, complete the following steps:

a. Right-click in a column heading, and then click Show Find Panel.

b. Type your search string into the search field, and then click Find.

StorageX Administrator’s Guide 353

Page 372: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Exporting Migration Project designs6

10. If you want to export your Migration Project design to a Microsoft Excel file, a CSV file, or a PDF file, click Export and then save your Migration Project design. For more information about exporting Migration Project designs, see “Exporting Migration Project designs” on page 354.

11. Click OK.

Exporting Migration Project designsYou can export an existing Migration Project design as an Excel-format file (.xls or .xlsx), a comma-delimited text file (.csv), or an Adobe PDF file (.pdf). Export an existing Migration Project design when you want to have an offline copy that others can use to review and verify or approve the source to destination mappings and settings in the design.

You can also export a Migration Project design when you want to save a copy of the Migration Project design outside of StorageX for reporting or archival purposes.

You can export a Migration Project design after you create a Migration Project design but before you validate the design. You can also export a Migration Project design after you validate the design but before you execute the design, as well as after you execute the design.

To export a Migration Project design

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane, browse to and then select the Migration Project design where you want to specify advanced options.

3. In the center pane, click Advanced Options.

4. Click Export.

5. Browse to the folder where you want to save the Migration Project design.

6. In the File name field, specify a name for the Migration Project design you want to export.

7. In the Save as type field, select the format in which you want to export the design.

8. Click Save.

Validating Migration Project designsAfter creating a Migration Project design, validate the design. You must validate your Migration Project design before you can execute your Migration Project design.

When StorageX validates a Migration Project design, StorageX takes the settings specified for the design, builds a model of the migration, and then runs a set of predefined rules against the model.

For example, StorageX looks at each source and destination mapping specified in a Migration Project and checks for items such as name conflicts, whether destination file storage resources have enough available space, and more. StorageX then displays a status for each source and destination mapping using the following values:

NoneDisplays when StorageX has not yet validated the source and destination mapping.

354 StorageX Administrator’s Guide

Page 373: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Validating Migration Project designs 6

ErrorDisplays when StorageX detects an error with the source and destination mapping. For example, a status of Error displays if StorageX detects that there is not enough available space on the destination Data ONTAP aggregate or VNX OE for File storage pool, or if there is a name conflict on a destination volume.

WarningDisplays when StorageX detects an issue with the source and destination mapping. For example, a status of Warning displays if the space guarantee specified for a source is None, or thin provisioning, but the space guarantee specified for the destination is Volume, or thick provisioning.

Green check boxDisplays when StorageX has validated the source and destination mapping and no issues were detected.

For some issues, StorageX displays not only information about the issue, but also allows you to resolve the issue right from within StorageX. However, for other issues, StorageX can display information about the issue and how to resolve it, but you cannot resolve the issue from within StorageX.

Consider the following examples:

• If StorageX detects a name conflict for a source and destination mapping, StorageX displays a message with information about the conflict and provides an Edit button you can use to rename the destination as appropriate.

• If StorageX detects an issue where the size of the source on a Data ONTAP or VNX OE for File file storage resource is larger than the amount of space available on the destination Data ONTAP aggregate, or VNX OE for File storage pool, or OneFS /ifs folder, StorageX displays a message telling you that the aggregate, storage pool, or /ifs folder specified does not have enough disk space. However, in order to actually resolve the issue you must connect directly to the destination Data ONTAP, VNX OE for File, or OneFS file storage resource and add disks using a native tool. For example, if you need to add disks to a Data ONTAP aggregate, you must use a Data ONTAP tool such as NetApp OnCommand System Manager. Use EMC Unisphere to add disks for VNX OE for File file storage resources, and Open FS to add disks for OneFS file storage resources. After adding the new disks, validate the design again to confirm that you addressed the issue.

This topic explains how to validate a Migration Project design. For more information about Migration Project design validation rules, see “Understanding Migration Project design validation rules” on page 356.

To validate a Migration Project design

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane, expand Migration Projects > Projects > MigrationProjectName > Designs > MigrationProjectDesign, where MigrationProjectName is the name of your Migration Project, and MigrationProjectDesign is the name of your Migration Project design.

3. Right-click the Migration Project design, and then click Validate Design.

StorageX Administrator’s Guide 355

Page 374: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Project design validation rules6

After you validate your design, complete the following tasks:

• Review any warnings or errors generated during the validation process and address any warnings or errors as appropriate. For more information about validation rules and validation errors and warnings. see “Understanding Migration Project design validation rules” on page 356.

• If you will be migrating file data using the NFS protocol and Phased Migration policies generated by Migration Projects, ensure you deploy the universal data engines that you want to use to migrate the file data using the NFS protocol before you execute the Migration Project design.

• Review and modify Migration Project Phased Migration template properties as needed. The Migration Project will use the base settings specified in the Migration Project Phased Migration template when executing the Migration Project and generating Phased Migration policies based on the template and Migration Project design settings. For more information, see “Modifying Migration Project Phased Migration template properties” on page 362.

• Create custom folders for the Phased Migration policies generated by the Migration Project as needed. For more information, see “Creating custom folders for Migration Project Phased Migration policies” on page 362.

• Execute the Migration Project design and generate Phase Migration policies. For more information, see “Executing Migration Project designs” on page 363.

Understanding Migration Project design validation rulesAfter you create a Migration Project design, validate your Migration Project design. You must validate your Migration Project design before you can execute your design. When you validate a Migration Project design, StorageX uses validation rules to determine if there are any problems or issues with your design.

This topic explains the validation rules StorageX uses when validating a Migration Project design. For more information about creating Migration Project designs, see “Creating Migration Project designs” on page 339. For more information about validating Migration Project designs, see “Validating Migration Project designs” on page 354.

StorageX uses the following validation rules when validating a Migration Project design:

TABLE 33 Migration Project design validation rules

Type Category Platform Specific

Message How to Resolve

Warning Volume No The source volume is a thin provisioning volume but you are creating a thick provisioning volume on the destination.

Change the space guarantee style specified by clicking the Edit button next to the warning and then specifying a different space guarantee style. You can also choose to continue without changing the style.

Warning Volume No The source volume is a thick provisioning volume but you are creating a thin provisioning volume on the destination.

Change the space guarantee style specified by clicking the Edit button next to the warning and then specifying a different space guarantee style. You can also choose to continue without changing the style.

356 StorageX Administrator’s Guide

Page 375: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Project design validation rules 6

Warning Volume Data ONTAP

You are trying to create a non-SnapLocked destination on a destination where SnapLock is enabled.

Change the policy destination to a non-SnapLock enabled volume by clicking the Edit button next to the warning and then specifying a different destination. You can also choose to continue without changing the destination.

Warning Volume No The volume size specified can potentially exceed the available size of the aggregate.

Specify a destination with additional capacity by editing the Migration Project design. For more information, see “Editing and specifying advanced options for Migration Project designs” on page 353.You can also choose to continue without changing the destination.

Warning Volume Data ONTAP

The language code on the Vserver or SVM on the destination does not match the language code on the source volume.

Specify a destination with an appropriate language code by editing the Migration Project design. For more information, see “Editing and specifying advanced options for Migration Project designs” on page 353. You can also choose to continue without changing the language code specified.

Warning Volume No The volume total size should not exceed 16TB.

Specify a new size for the Data ONTAP volume or VNX OE for File file system by clicking the Edit button next to the warning and then specifying a new size. You can also choose to continue without changing the volume size.

Warning Qtree Data ONTAP

You are trying to create a qtree with the UNIX security style on a destination volume with the NTFS security style.

Change the security style specified by clicking the Edit button next to the warning and then specifying a different security style. You can also choose to continue without changing the security style.

Warning Volume Data ONTAP

You are trying to create a volume with deduplication enabled on a destination that is not deduplication-capable.

Specify a new destination with an appropriate deduplication type by clicking the Edit button next to the warning and then specifying a different destination. You can also choose to continue without changing the destination.

Warning Volume Data ONTAP

Deduplication is enabled on the volume. You need to manually set up the deduplication settings on the destination after the migration is completed.

After the migration is completed, enable deduplication on the destination resource.

NOTE: If you create a design that uses SnapMirror to migrate from a source where the Enable Storage Efficiency option was previously set and removed, StorageX returns this warning. StorageX does not display this warning for designs that do not use SnapMirror, regardless of whether the Enable Storage Efficiency option was previously set.

TABLE 33 Migration Project design validation rules

Type Category Platform Specific

Message How to Resolve

StorageX Administrator’s Guide 357

Page 376: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Project design validation rules6

Warning Share No CIFS share 'ShareName' with local path 'LocalPath' is already shared under CIFS share 'ShareName' with local path 'LocalPath'.

This warning indicates that you have two or more overlapping sources in the Migration Project design. Overlapping sources can result in duplicate copies of file data. Verify that you want to include overlapping sources in your design. You can also choose to continue without changing the source share. For more information, see “Migration Project design planning considerations” on page 340.

Error Volume Data ONTAP

The specified mount path does not exist on the destination, or the specified mount path cannot be used as a mount path.

Specify a different mount path by clicking the Edit button next to the error and then specifying a different Data ONTAP volume.

Error Volume No The volume name is already in use.

Specify a new name for the destination Data ONTAP volume or VNX OE for File file system by clicking the Edit button next to the error and then specifying a different name.

Error Share No The CIFS share name 'ShareName' is already in use.

Specify a new name for the destination share by clicking the Edit button next to the error and then specifying a different name.

Error Volume No The volume size must be less than the available size of the aggregate.

Specify a different Data ONTAP volume or VNX OE for File file system size by clicking the Edit button next to the error and then specifying a different volume size.

Error Volume No The volume must be online. Manually place the Data ONTAP volume or VNX OE for File file system online using a native tool such as NetApp OnCommand System Manager for Data ONTAP file storage resources or EMC Unisphere for VNX OE for File file storage resources.

Error Qtree Data ONTAP

The qtree name is already in use. Specify a new name for the qtree by clicking the Edit button next to the error and then specifying a new qtree name.

Error Volume No The volume total size must be less than the available storage size on the destination.

Specify a different Data ONTAP volume or VNX OE for File file system size by clicking the Edit button next to the error and then specifying a different size.

Error Volume No An aggregate that contains the volume does not exist.

Specify a different aggregate by clicking the Edit button next to the error and then specifying a different aggregate.

Error Qtree Data ONTAP

You are trying to create a qtree with the NTFS security style on a destination volume with the UNIX security style.

Specify a different security style by clicking the Edit button next to the error and then specifying a different security style.

TABLE 33 Migration Project design validation rules

Type Category Platform Specific

Message How to Resolve

358 StorageX Administrator’s Guide

Page 377: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Project design validation rules 6

Error Volume No Another volume is already mounted at ‘MountPath’.

If the Migration Project design is a Like-to-Like Migration Project design, specify a different mount path by clicking the Edit button next to the error and then specifying a different Data ONTAP volume or VNX OE for File file system name.If the Migration Project design is an Advanced Migration Project design, in the General area, click Advanced Options and then specify a different mount path in the Dst Mount Path column.

Error Volume Data ONTAP

You are trying to create a SnapLocked destination on a destination where SnapLock is not enabled.

Change the destination to a volume with SnapLock enabled by editing the Migration Project design. For more information, see “Editing and specifying advanced options for Migration Project designs” on page 353.

Error Export No The NFS export name 'ExportName' is already in use.

Manually change export name using a native tool such as NetApp OnCommand System Manager for Data ONTAP file storage resources, EMC Unisphere for VNX OE for File for File file storage resources, or One FS for OneFS file storage resources.

Error Qtree /Tree Quota

Data ONTAP

The destination volume is read-only.  Please select a different destination or break the SnapMirror related to this volume.

If you want to select a different destination volume, select a different destination by editing the Migration Project design. For more information about editing a Migration Project design, see “Editing and specifying advanced options for Migration Project designs” on page 353.If the destination Data ONTAP volume is a volume that is a destination in an active SnapMirror relationship and you are consolidating file data from different sources, you can choose to break the SnapMirror relationship before continuing. For more information about breaking a SnapMirror relationship, see “Breaking SnapMirror relationships on Data ONTAP file storage resources” on page 156.

Error Volume No The available volume size must be larger than the current data size on the volume.

Specify a different Data ONTAP volume or VNX OE for File file system size by clicking the Edit button next to the error and then specifying a different size.

Error Volume No The volume total size must be at least 20MB.

Specify a different Data ONTAP volume or VNX OE for File file system size by clicking the Edit button next to the error and then specifying a different size.

TABLE 33 Migration Project design validation rules

Type Category Platform Specific

Message How to Resolve

StorageX Administrator’s Guide 359

Page 378: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Migration Project design validation rules6

Error Volume Data ONTAP

The language code of the source volume is undefined. Please resolve the issue and then retry the design.

Manually resolve the undefined language code on the source volume by specifying a new language code using a native tool such as NetApp OnCommand System Manager for Data ONTAP file storage resources.

Error Volume No The volume total size must be larger than the current data size on the volume.

Specify a different Data ONTAP volume or VNX OE for File file system size by clicking the Edit button next to the error and then specifying a different size.

Error Qtree/Tree Quota

No The destination volume is not mounted. Please mount the volume and validate the design again.

Manually mount the Data ONTAP volume using a native tool such as NetApp OnCommand System Manager for Data ONTAP file storage resources or manually mount the VNX OE for File file system using a native tool such as EMC Unisphere for VNX OE for File file storage resources.

Error API No Unable to connect to the destination file storage resource using the platform API. This may be due to incorrect credentials, or because platform API access is not enabled. Please resolve the issue and then retry the design.

This error occurs when StorageX can contact the file storage resource but cannot not communicate with the file storage resource using the platform API. Verify that platform API access is configured correctly for the file storage resource. For more information about configuring platform API access, see “Configuring platform API access for file storage resources” on page 72.

Error Device No Unable to contact the destination file storage resource. This may be due to network connectivity or DNS issue, or because the file storage resource is offline. Please resolve the issue and then retry the design.

This error occurs when StorageX can contact the file storage resource, but cannot not communicate with the file storage resource using the platform API. Verify that platform API access is configured correctly for the file storage resource. For more information about configuring platform API access, see “Configuring platform API access for file storage resources” on page 72.

Error API OneFS Unable to get storage information for the destination location. This may be due to a network connectivity issue, or due to an interruption in platform API access. Please resolve the issue and then retry the design

This is an intermittent error that can occur when there is an access interruption to the OneFS file storage resource.

Error Tree Quota

VNX OE for File

The tree quota path specified already exists.

Specify a different name by clicking the Edit button next to the error and then specifying a different name.

Error Folder OneFS Another source is also set to migrate data to the same destination location.

Specify a different destination location by clicking the Edit button next to the error and then specifying a different destination location.

TABLE 33 Migration Project design validation rules

Type Category Platform Specific

Message How to Resolve

360 StorageX Administrator’s Guide

Page 379: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Deploying universal data engines for migrations using the NFS protocol 6

Deploying universal data engines for migrations using the NFS protocol

If you will be migrating file data using the NFS protocol and Phased Migration policies generated by Migration Projects, ensure you deploy the universal data engines that you want to use to migrate the file data using the NFS protocol before you execute the Migration Project design.

ATTENTIONIf you do not deploy the universal data engines you want to use to migrate file data using the NFS protocol before you execute the Migration Project design, StorageX will not have appropriate permissions on the destination and the Phased Migration policies created by the Migration Project will not be able to migrate the data.

If you deploy the universal data engines and specify appropriate universal data engine settings on the Universal Data Engine Selection tab of the Phased Migration template associated with the Migration Project, when you execute the policy, StorageX will have appropriate permissions to perform the data migration.

First deploy the universal data engines that you want to use for migrating file data using the NFS protocol. Also configure universal data engine groups as needed. For performance reasons, a best practice is to use a Linux data engine when transferring file data using the NFS protocol. However, you can also use the Windows data engine installed by default on the StorageX server computer to transfer file data using the NFS protocol if needed. For more information, see “Understanding StorageX universal data engines” on page 9, “Installing and configuring Linux data engines” on page 35, and “Creating and managing universal data engine groups” on page 130.

After you deploy the universal data engines, on the Migration Project Phased Migration template specify the universal data engine or universal data engine group you want to use to migrate the data using the NFS protocol on the Universal Data Engine Selection tab. For more information about viewing and modifying settings specified in the Migration Project Phased Migration template, see “Modifying Migration Project Phased Migration template properties” on page 362.

After you execute the Migration Project and generate Phased Migration policies for the Migration Project, you can make any additional modifications to universal data engines assigned to individual Phased Migration policies as needed. Make the adjustments on the Universal Data Engine Selection tab for each policy before you run the policy. For more information, see “Viewing and modifying Migration Project Phased Migration policies” on page 365.

Error Folder OneFS The destination location already exists on the destination file storage resource.

Change the destination path by clicking the Edit button next to the error and then specifying a different destination location.

Error Folder OneFS The parent folder for the destination location does not exist.

Change the destination path by clicking the Edit button next to the error and then specifying a different destination location.

Error Volume Data ONTAP

The name cannot contain spaces.

Change the volume name by clicking the Edit button next to the error and then specifying a different volume name.

TABLE 33 Migration Project design validation rules

Type Category Platform Specific

Message How to Resolve

StorageX Administrator’s Guide 361

Page 380: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Modifying Migration Project Phased Migration template properties6

Modifying Migration Project Phased Migration template propertiesReview and modify Migration Project Phased Migration template properties after you have created and validated your Migration Project design but before you execute the design.

By default, StorageX provides a Migration Project Phased Migration template that StorageX uses when generating Phased Migration policies based on settings specified in both the Migration Project design as well as the Migration Project Phased Migration template.

Review the Migration Project Phased Migrate template properties and modify any properties as needed before you execute your Migration Project design and generate Phased Migration policies for the project.

To view and modify Migration Project Phased Migration template properties

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane, expand Migration Projects > Projects > MigrationProjectName > Designs > MigrationProjectDesign, where MigrationProjectName is the name of your Migration Project, and MigrationProjectDesign is the name of your Migration Project design.

3. Right-click the Migration Project design, and then click Phased Migration Template Properties.

4. Review the settings on each tab and make any modifications to the Phased Migration template properties as needed. For more information about the options available on each of the Phased Migration template tabs, click the Help button on the dialog box.

In particular, consider reviewing the options in the Migration Options area. For example, on the Initial Phase tab, specify if you would like to run a batch file or perform a baseline copy during the Initial Phase of the policy run. On the Incremental Phase tab, specify conditions for advancing to the Incremental Phase as appropriate. On the Final Phase tab, if you are using a DFS namespace or automount map files, specify whether you would like StorageX to update the DFS namespace or the automount map files during the Final Phase of the policy run.

5. When you are finished reviewing and modifying Phased Migration template properties as needed, click OK.

After you review and modify the Phased Migration template properties as needed, complete the following tasks:

• Create custom folders for the Phased Migration policies generated by the Migration Project design as needed. For more information, see “Creating custom folders for Migration Project Phased Migration policies” on page 362.

• Execute the Migration Project design and generate Phased Migration policies for the Migration Project. For more information, see “Executing Migration Project designs” on page 363.

Creating custom folders for Migration Project Phased Migration policies

When you execute a Migration Project design, StorageX automatically generates Phased Migration policies for the project based on the settings specified in the Migration Project design and the Migration Project Phased Migration template.

362 StorageX Administrator’s Guide

Page 381: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Executing Migration Project designs 6

By default, StorageX places the Phased Migration policies generated by a Migration Project design in the Migration Projects > My Policies folder.

However, you can create additional custom folders under Migration Projects > My Policies and store polices created using specific Migration Project designs in project-specific folders.

For example, if you have multiple Migration Project designs for one or more Migration Projects, consider creating custom folders to help you better organize and manage the Phased Migration policies StorageX creates when executing each Migration Project design.

To create a custom folder for Migration Project Phased Migration policies

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane, expand Migration Projects > My Policies.

3. Right-click My Policies, and then click Folder.

4. Type a name for the folder.

After you create any custom folders needed for Phased Migration policies that will be generated by a Migration Project design, execute the Migration Project design to generate the Phased Migration policies. For more information, see “Executing Migration Project designs” on page 363.

Executing Migration Project designsAfter creating and designing the Migration Project and validating your Migration Project design, execute the Migration Project design.

StorageX performs the following actions when executing a Migration Project design:

• Creates destinations on file storage resources as appropriate.

If the destination is a Data ONTAP file storage resource, StorageX creates destination volumes and qtrees as needed on the destination.

If the destination is a VNX OE for File file storage resource, StorageX creates destination file systems and tree quotas as needed on the destination.

If the destination is a OneFS file storage resource, StorageX creates destination folders and subfolders under the /ifs folder as needed.

• If the source and destination use the CIFS protocol, StorageX creates a hidden share on the source and destination. StorageX uses this hidden share to copy data, and then removes this hidden share when the migration completes.

• If the source and destination use the NFS protocol, StorageX creates an export on the source and destination. StorageX uses this export to copy data.

When sources and destinations use the NFS protocol, StorageX creates the path for the export, but does not remove the export when the migration completes. After the migration completes, if you want to hide the local path used by the export, remove the export.

StorageX Administrator’s Guide 363

Page 382: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Executing Migration Project designs6

• Generates Phased Migration policies for migrating file data from the sources to the destinations specified in the design

NOTEExecuting the Migration Project design does not actually move file data. To move file data, you must run each Phased Migration policy created for the Migration Project. Executing the Migration Project design also does not create the destination CIFS shared folders or NFS exports. StorageX creates destination CIFS shared folders and NFS exports in the Final Phase of a Phased Migration policy. If you are using StorageX with a DFS namespace or automount map files, executing the Migration Project design also does not update the DFS namespace or automount map files. StorageX updates the DFS namespace or automount map files as needed based on the properties specified in the Phased Migration policy in the Final Phase of the Phased Migration policy. For more information, see “Understanding Migration Project Phased Migration policies” on page 328, “Running Phased Migration policies immediately” on page 262 and “Scheduling Phased Migration policies” on page 263.

To execute a Migration Project design

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane, expand Migration Projects > Projects > MigrationProjectName > Designs > MigrationProjectDesign, where MigrationProjectName is the name of your Migration Project, and MigrationProjectDesign is the name of the Migration Project design you want to execute.

3. Right-click the Migration Project design folder, and then click Execute Design.

4. In the Folder field, browse to and select the folder where you want to store the Phased Migration policies created by the Migration Project.

StorageX provides a single folder by default called My Policies that you can use to store Phased Migration policies generated by Migration Project designs. You can also create custom folders to store policies in as needed to help you organize policies. However, you need to create these custom folders prior to executing your Migration Project design if you want to specify a custom folder for policies when you execute the design. For more information, see “Creating custom folders for Migration Project Phased Migration policies” on page 362.

If you specify that you want the Phased Migration policies generated by the Migration Project design stored in the default My Policies folder, you can later create custom folders and drag and drop the policies into custom folders as needed.

5. Click OK.

StorageX generates Phased Migration policies based on the Migration Project design and the Migration Project Phased Migration template. You can see the policies generated in the right pane when you select a Migration Project design in the Migration Projects tree.

After executing the Migration Project design and creating Phased Migration policies, view and modify the policies as needed, then run the policies.

NOTEIf VNX OE for File or OneFS file storage resources are specified as destinations in Phased Migration policies generated by StorageX when executing a Migration Project design, ensure you configure the schedule for each of these policies to never advance to the Final Phase automatically by selecting the Never advance automatically; policy will remain in the Incremental Phase until advanced manually option on the Incremental Phase tab for the policy. As a general rule, ensure you run

364 StorageX Administrator’s Guide

Page 383: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Viewing and modifying Migration Project Phased Migration policies 6

Migration Project Phased Migration policies manually one at a time when the destination specified in the Destination Path field on the Migration Paths tab is a VNX OE for File or OneFS file storage resource. For more information about Migration Project designs, see “Understanding Migration Project designs” on page 326 and “Creating Migration Project designs” on page 339.

For more information, see “Viewing and modifying Migration Project Phased Migration policies” on page 365, “Running Phased Migration policies immediately” on page 262, and “Scheduling Phased Migration policies” on page 263.

Viewing and modifying Migration Project Phased Migration policiesYou can view and modify the Phased Migration policies generated when StorageX executes a Migration Project design before you run the policies.

This topic explains how to view and modify Phased Migration policies generated by a Migration Project design. For more information about creating a Migration Project design, see “Creating Migration Project designs” on page 339.

NOTEIf VNX OE for File or OneFS file storage resources are specified as destinations in Phased Migration policies generated by StorageX when executing a Migration Project design, ensure you configure the schedule for each of these policies to never advance to the Final Phase automatically by selecting the Never advance automatically; policy will remain in the Incremental Phase until advanced manually option on the Incremental Phase tab for the policy. As a general rule, ensure you run Migration Project Phased Migration policies manually one at a time when the destination specified in the Destination Path field on the Migration Paths tab is a VNX OE for File or OneFS file storage resource. For more information about Migration Project designs, see “Understanding Migration Project designs” on page 326 and “Creating Migration Project designs” on page 339.

To view and modify Migration Project Migration policies

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane, expand Migration Projects > My Policies.

3. If the policy is stored in the My Policies folder, select the policy.

4. If the policy is stored in a custom folder, browse to the custom folder where the policy is stored and then select the policy. For more information about custom folders, see “Creating custom folders for Migration Project Phased Migration policies” on page 362.

5. In the center pane, review the summary information for the policy.

The General area displays the Migration Project design the policy was generated from, as well as the name and description of the Phased Migration policies that StorageX generated when executing the Migration Project design. You can change the name and the description for the policy by clicking on the appropriate link.

The Status area displays status information for the policy. For example, if there was a problem when the policy ran that you need to address, the following fields display with the following information:

• The Status field displays a value of User action required.

StorageX Administrator’s Guide 365

Page 384: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Rolling back when a Migration Project design execution fails6

• The Last Action field displays information about the last action that occurred when the policy ran, such as Perform a baseline copy, and the Last Action Result field displays a value such as Failed.

• The Last Replication Result field displays a value such as Completed with errors.

The Configuration area displays the source and destination paths on the source and destination storage resources. Click on the path link to open Windows Explorer and visually verify the contents in the source and destination.

The Schedule area allows you to specify a schedule for the policy by clicking on the link. When you click on the link, the Migration Schedule dialog box displays, and you can specify a schedule for running the Phased Migration policy. For more information about each option on the Migration Schedule dialog box, click the Help button on the dialog box. For more information about scheduling a policy, see “Scheduling Phased Migration policies” on page 263.

The Policy Status area displays information about the last 30 runs of the policy

6. In the left tree pane, right-click the policy, and then click Properties to review and modify the Phased Migration policy properties as needed. For more information about specific policy properties, click the Help button available on each tab of the dialog box.

Consider the following examples:

• If you have a large environment, you may want to distribute the data movement workload. For example, if you have 15 different destination file storage resources, you can specify that the policy use multiple universal data engines to perform the data movement. To distribute the data movement workload across universal data engines, right-click the policy and then click Properties. In the Replication Options area, click Universal Data Engine Selection, and then specify appropriate universal data engine options.

• If you want to specify a schedule for running the policy, right-click the policy and then click Properties. In the Migration Options area, click Migration Schedule, and then specify a schedule for the policy.

After you review the Phased Migration policies generated by the Migration Project and make adjustments to policy settings as needed, run the Phased Migration policies and verify they completed successfully. For more information about running Phased Migration policies, see the following topics:

• “Running Phased Migration policies immediately” on page 262

• “Scheduling Phased Migration policies” on page 263

For more information about verifying Phased Migration policies, see “Verifying Phased Migration policies completed successfully” on page 271.

Rolling back when a Migration Project design execution failsIn some circumstances, a Migration Project design may fail during execution.

The most common reason for a Migration Project design to fail during execution is a network interruption. However, there may also be other unexpected issues that occur.

When you execute a Migration Project design, StorageX creates a Phased Migration policy for each source and destination pairing and creates destination items on destination file storage resources as appropriate. For more information about the actions StorageX performs when executing a Migration Project design, see “Executing Migration Project designs” on page 363.

366 StorageX Administrator’s Guide

Page 385: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Rolling back when a Migration Project design execution fails 6

If a Migration Project design fails during execution, identify which Phased Migration policies and items on the destination StorageX failed to create in the Migration Projects view. You can do this by selecting the failed Migration Project design and then comparing differences between the number of Phased Migration policies generated and the number of source and destination pairings included in the Migration Project design.

Once you understand which items StorageX failed to create when executing the Migration Project design and how many of these items there are, you can determine which rollback approach is appropriate for your specific circumstances. Typically the steps you take to roll back a Migration Project design execution failure differ based on whether a small number or a large number of items failed during design execution.

If only a small number of items failed during Migration Project design execution, note the items that failed during execution, address the reason for the execution failure, such as addressing any network interruptions that may have caused the failure, and then create a new Migration Project design for only the items that failed.

This approach typically works best when only one or a small number of items failed during execution. For example, assume you execute a Migration Project design with a Data ONTAP file storage resource as one of your destinations. StorageX creates 19 out of 20 volumes on the destination and 19 out of 20 Phased Migration policies. In this scenario, note which Phased Migration policy and which volume on which destination StorageX could not create. Then create a new Migration Project design that includes only the source and destination pairing for the Phased Migration policy and volume creation failure.

If a large number of items failed during Migration Project design execution, note the items that were created successfully during execution, delete the items that were successfully created during execution, and delete the Migration Project design. Next address the reason for the execution failure, such as addressing any network interruptions that may have caused the failure. Then create a new Migration Project design, validate the new design, and then execute the new design to create the appropriate policies and items on the destination to use when migrating data.

This approach typically works best when a large number of items failed during execution. For example, if you execute a Migration Project design and StorageX creates only 20 out of 100 volumes on the destination, note which items StorageX created on the destination, as well as any Phased Migration policies that StorageX created. Delete these items, address the underlying cause of the failure, and delete the failed Migration Project design. Then create a new Migration Project design, validate the new design, and then execute the new Migration Project design.

To roll back when a Migration Project fails during execution

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane under Migration Projects, browse to and select Migration Project design that failed.

3. Determine if only a small number of items failed during Migration Project design execution or if a large number of items failed during Migration Project design execution by completing the following steps:

a. In the center pane, under Details, count up the total number of source and destination pairings included in the Migration Project design.

b. In the left tree pane, under the My Policies folder or a custom folder you created under My Policies, count up the total number of Phased Migration policies that StorageX created when executing the Migration Project design.

StorageX Administrator’s Guide 367

Page 386: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Rolling back when a Migration Project design execution fails6

c. Identify the difference between the number of source and destination pairings in the Migration Project design and the number Phased Migration policies created during design execution.

The difference between the number of source and destination pairings and the number of Phased Migration policies created indicates whether a small number or a large number of items failed during Migration Project design execution.

4. If you see that StorageX failed to create only a small number of Phased Migration policies during design execution, complete the following steps:

a. Identify the source and destination pair that is missing a corresponding Phased Migration policy.

b. Connect to the destination file storage resource for each source and destination pair.

c. Delete any items on the destination file storage resource StorageX may have created when the Migration Project design executed.

Ensure you delete destination items such Data ONTAP volumes and qtrees, VNX OE for File volumes and tree quotas, and OneFS destination folders.

Also ensure you delete any hidden shares or exports StorageX may have created on the destination. StorageX creates these hidden shares or exports on the destination and then uses these items when migrating data using Phased Migration policies.

d. Address the reason for the execution failure, such as addressing any network interruptions that may have caused the failure.

e. Create a new Migration Project design that contains only the source and destination pairings that failed when the original Migration Project design executed.

For more information about creating a new Migration Project design, see “Creating Migration Project designs” on page 339.

f. Execute the new Migration Project design to create the items that failed previously.

For more information about executing a Migration Project design, see “Executing Migration Project designs” on page 363.

After the new Migration Project design executes successfully and creates the required items on the destination and the appropriate Phased Migration policies, you can use the new items and Phased Migration policies to migrate file data. For more information about running Phased Migration policies and migrating file data, see “Running Phased Migration policies immediately” on page 262 and “Scheduling Phased Migration policies” on page 263.

5. If you see that StorageX failed to create a large number of Phased Migration policies during design execution, complete the following steps:

a. Identify the source and destination pairs for each Phased Migration policy that StorageX created when executing the design.

b. Connect to each destination file storage resource for each source and destination pair.

c. Delete any items on the destination file storage resource StorageX may have created when the Migration Project design executed.

Ensure you delete destination items such Data ONTAP volumes and qtrees, VNX OE for File volumes and tree quotas, and OneFS destination folders.

368 StorageX Administrator’s Guide

Page 387: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Migration Projects and Migration Project designs 6

Also ensure you delete any hidden shares or exports StorageX may have created on the destination. StorageX creates these hidden shares or exports on the destination and then uses these items when migrating data using Phased Migration policies.

d. Delete all of the Phased Migration policies StorageX created during design execution.

For more information about deleting Phased Migration policies, see “Deleting Phased Migration policies” on page 293.

e. Delete the Migration Project design that failed during execution.

For more information about deleting Migration Project designs, see “Deleting Migration Project designs” on page 371.

f. Fix the issue that caused the execution of the design to fail. For example, if network connectivity issues caused the Migration Project design execution to fail, address these issues.

g. Create a new Migration Project design that includes the appropriate source and destination pairings, validate the design, and then execute the design again. For more information, see “Creating Migration Project designs” on page 339, “Validating Migration Project designs” on page 354, and “Executing Migration Project designs” on page 363.

Managing Migration Projects and Migration Project designsThis section explains how to manage Migration Projects and Migration Project designs.

The following topics provide more information about managing Migration Projects and Migration Project designs:

• “Modifying Migration Project properties” on page 369

• “Renaming Migration Projects” on page 370

• “Deleting Migration Projects” on page 370

• “Deleting Migration Project designs” on page 371

For more information about understanding and creating Migration Projects and Migration Project designs, see the following topics:

• “Understanding Migration Projects” on page 321 and “Creating Migration Projects” on page 333

• “Understanding Migration Project designs” on page 326 and “Creating Migration Project designs” on page 339

Modifying Migration Project propertiesAfter you create a Migration Project, you can modify project settings, including the Migration Project name, description, project owner, and project start and end dates.

To modify Migration Project properties

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane, right-click the Migration Project for which you want to modify properties, and then click Properties.

StorageX Administrator’s Guide 369

Page 388: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Migration Projects and Migration Project designs6

3. Modify the Migration Project name, description, project owner, and project start and end dates as needed, and then click OK. For more information about each item, click the Help button on the dialog box.

For more information about creating a Migration Project, see “Creating Migration Projects” on page 333. For more information about deleting a Migration Project, see “Deleting Migration Projects” on page 370.

Renaming Migration ProjectsYou can rename a Migration Project at any time. For example, if you have created several Migration Projects, you might need to rename your Migration Projects to clarify the purpose of each Migration Project. Renaming a Migration project does not affect the project in any other way.

To rename a Migration Project

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane, right-click the Migration Project that you want to rename, and then click Rename.

3. Type a new name for the Migration Project, and then press the Enter key.

For more information about creating a Migration Project, see “Creating Migration Projects” on page 333. For more information about modifying other properties of a Migration Project, see “Modifying Migration Project properties” on page 369.

Deleting Migration ProjectsYou can delete a Migration Project if you no longer want to use the Migration Project.

Before you delete a Migration Project, ensure you delete any Phased Migration policies StorageX created for the Migration Project. StorageX generates Phased Migration policies for a Migration Project when you execute a Migration Project design. You must delete any Phased Migration policies created for the Migration Project before you can delete the Migration Project.

For more information about deleting Phased Migration policies, see “Deleting Phased Migration policies” on page 293.

To delete a Migration Project

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane, right-click the Migration Project that you want to delete, and then click Delete.

3. Click Yes to confirm that you want to delete the Migration Project.

StorageX deletes the Migration Project, as well as any Migration Project designs associated with the Migration Project.

For more information about creating a Migration Project, see “Creating Migration Projects” on page 333. For more information about creating Migration Project designs and executing Migration Project designs, see “Creating Migration Project designs” on page 339 and “Executing Migration Project designs” on page 363.

370 StorageX Administrator’s Guide

Page 389: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Migration Projects and Migration Project designs 6

Deleting Migration Project designsYou can delete a Migration Project design when you no longer want to use the Migration Project design.

If you have executed the Migration Project design that you want to delete, you must first delete any Phased Migration policies created when you executed the design before you can delete the design. For more information about deleting Phased Migration policies, see “Deleting Phased Migration policies” on page 293.

If you have not executed the Migration Project design that you want to delete, the Migration Project design has not generated any Phased Migration Projects. In this scenario, you can simply delete the design.

To delete a Migration Project design

1. In the StorageX Console, click the Migration Projects tab.

2. In the left tree pane, browse to and then right-click the Migration Project design that you want to delete, and then click Delete.

3. Click Yes to confirm that you want to delete the Migration Project design.

StorageX deletes the Migration Project design.

For more information about creating a Migration Project design, see “Creating Migration Project designs” on page 339.

StorageX Administrator’s Guide 371

Page 390: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Migration Projects and Migration Project designs6

372 StorageX Administrator’s Guide

Page 391: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX Administrator’s Guide

Chapter

7n

Creating and Managing Disaster Recovery and ReplicatioPolicies

This section provides information to help you plan and configure Disaster Recovery and Replication policies in your StorageX environment. This section explains what Disaster Recovery and Replication policies are, how to create them, and how to manage them.

In this chapter•Checklist: Creating and managing Disaster Recovery and Replication policies 374

•Understanding Disaster Recovery policies . . . . . . . . . . . . . . . . . . . . . . . . . 374

•Understanding replication and replication topology . . . . . . . . . . . . . . . . . . 376

•Understanding Disaster Recovery policy failover . . . . . . . . . . . . . . . . . . . . 377

•Disaster Recovery policy planning considerations . . . . . . . . . . . . . . . . . . . 380

•Creating Disaster Recovery policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381

•Scheduling Disaster Recovery policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384

•Manually failing over Disaster Recovery policies . . . . . . . . . . . . . . . . . . . . 385

•Manually failing back Disaster Recovery policies . . . . . . . . . . . . . . . . . . . . 391

•Verifying Disaster Recovery policies completed successfully . . . . . . . . . . 386

•Resynchronizing SnapMirrors for Disaster Recovery failback . . . . . . . . . . 392

•Managing Disaster Recovery policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

•Understanding Disaster Recovery discovery . . . . . . . . . . . . . . . . . . . . . . . . 396

•Understanding Replication policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

•Replication policy planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . 400

•Creating Replication policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401

•Running Replication immediately. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

•Scheduling Replication policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

•Verifying Replication policies completed successfully . . . . . . . . . . . . . . . . 403

•Managing Replication policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407

•Using batch files with Disaster Recovery or Replication policies. . . . . . . . 410

373

Page 392: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Checklist: Creating and managing Disaster Recovery and Replication policies7

Checklist: Creating and managing Disaster Recovery and Replication policies

Use the following checklist to help you ensure business continuity using Disaster Recovery policies:

Understanding Disaster Recovery policiesDisaster Recovery policies allow you to easily set up and manage your disaster recovery plan, in the event that your servers or data centers experience a failure.

StorageX provides three types of Disaster Recovery monitoring using Disaster Recovery policies:

• CIFS-based resource monitoring

• NetApp-based resource monitoring

• DFS namespace link monitoring

All of these types of monitoring provide business continuity for CIFS client computers using DFS. Like Phased Migration policies, Disaster Recovery policies and Replication policies also copy file and directory attributes and permissions.

NOTES:

• You cannot use Disaster Recovery policies to monitor NFS servers.

• Disaster Recovery policies and Replication policies do not copy the offline attribute (FILE_ATTRIBUTE_OFFLINE) when copying file or directory attributes during the replication process, because the file or directory is online by default after replication. If you want to configure the replicated file or directory to be offline, you must use a third-party tool to set the offline attribute after the replication process finishes.

Before configuring Disaster Recovery policies for your environment, ensure you examine your environment and plan for your specific needs. For more information about Disaster Recovery policy planning, see “Disaster Recovery policy planning considerations” on page 380.

TABLE 34 Checklist: Creating and managing Disaster Recovery and Replication policies

Task

1 If you want to use a DFS namespace with Disaster Recovery and Replication policies, create a DFS namespace or add an existing DFS namespace to StorageX. For more information, see “Creating and Managing DFS Namespaces” on page 159.

2 Ensure you understand how Disaster Recovery and Replication policies work. For more information, see “Understanding Disaster Recovery policies” on page 374 and “Understanding Replication policies” on page 399.

3 Review Disaster Recovery and Replication policy planning considerations. For more information, see “Disaster Recovery policy planning considerations” on page 380 and “Replication policy planning considerations” on page 400.

4 Create new Disaster Recovery and Replication policies as needed. For more information, see “Creating Disaster Recovery policies” on page 381 and “Creating Replication policies” on page 401.

5 Modify your policies and specify additional properties and actions as needed to ensure the appropriate resources are monitored and replicated in the event of a failure. For more information, see “Managing Disaster Recovery policies” on page 392 and “Managing Replication policies” on page 407.

374 StorageX Administrator’s Guide

Page 393: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Disaster Recovery policies 7

The following topics provide more information about understanding Disaster Recovery policies:

• “Understanding Disaster Recovery policy functionality” on page 375

• “CIFS-based resource monitoring” on page 375

• “NetApp-based resource monitoring” on page 376

• “DFS namespace link monitoring” on page 376

Understanding Disaster Recovery policy functionalityEach Disaster Recovery policy includes multiple functions: health monitoring; discovery; and replication.

Health Monitoring

When you use a Disaster Recovery policy to monitor the health of your resources, StorageX regularly checks that the storage resources and links the policy monitors are available and accessible, and if a resource or link cannot be accessed, automatically fails over to the specified secondary resources or links. For more information about failover functionality, see “Understanding Disaster Recovery policy failover” on page 377.

Discovery

Using Disaster Recovery policies, StorageX looks for changes to your monitored DFS namespaces and NetApp resources and notifies you when changes occur. Complex environments can change frequently, and multiple users may be modifying or adding links or qtrees. StorageX automatically tracks those modifications or additions and allows you to quickly add new links or qtrees to be monitored to your Disaster Recovery policy. For more information about link and qtree discovery, see “Understanding Disaster Recovery discovery” on page 396.

Replication

In order for a Disaster Recovery plan to work properly, the data on your primary and secondary storage resources must be in sync. When you configure a Disaster Recovery policy, StorageX replicates data from the primary resource to the secondary resource. For more information about replication, see “Understanding replication and replication topology” on page 376.

CIFS-based resource monitoringCIFS-based resource Disaster Recovery monitoring enables you to make data on servers participating in your namespace highly available. Use this monitoring type when you want to ensure data on a primary server is highly available. When a failure of the primary server is detected, StorageX automatically fails over all links in the Disaster Recovery policy to a secondary server.

• This type of monitoring enables you to configure a server as a disaster recovery backup for a primary server.

• You can monitor for new links targeting the primary server to add to the policy and to replicate data to a secondary server.

StorageX Administrator’s Guide 375

Page 394: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding replication and replication topology7

NOTEYou can create Namespace Availability policies to make the logical structure of the namespace highly available. For more information, see “Synchronizing DFS namespaces” on page 216.

NetApp-based resource monitoringNetApp-based resource Disaster Recovery monitoring enables you to make data on Data ONTAP-based file storage resources participating in your namespace highly available.

• This type of monitoring allows you to set up a file storage resource or nearline storage device as a disaster recovery backup for one or more primary file storage resources.

• You can also leverage SnapMirror® replication to replicate data to a standby volume or qtree. When a failure on the primary file storage resource is detected, an automatic failover to the standby file storage resource is initiated.

NOTEStorageX does not support using Disaster Recovery policies to monitor storage resources running Data ONTAP Cluster Mode.

DFS namespace link monitoringDFS namespace link Disaster Recovery monitoring enables you to detect a failure and automatically fail over DFS links to a replicated file storage resource. You can use this policy type when data is scattered among multiple servers, or if you want more flexibility, as it enables you to control how monitoring and failover occur.

• One of the most significant advantages of this type of monitoring is the ability to designate a cascading failover path. A typical scenario is one in which you designate critical data to fail over first to a local edge device, and then to a remote central device. This ensures high availability of the data whether there is a local server failure or an entire site outage. Failover takes place without changing login scripts or network configuration.

• Links contained in the Disaster Recovery policy must have at least two replicated targets and might contain multiple offline targets.

Understanding replication and replication topologyIn StorageX, Disaster Recovery and Replication policies copy data from one CIFS storage resource to another or from one NFS storage resource to another (Replication policies only).This process is called replication. You can replicate data from either a physical location on a server or a DFS namespace link that has physical paths as its link targets. The Disaster Recovery or Replication policy then copies data from that source to one or more target paths, which must also be physical paths or DFS links with targets that have physical paths.

In a Disaster Recovery policy, data is replicated from the primary server, target, or qtree to all configured secondary resources. You cannot configure how replication occurs for a Disaster Recovery policy.

When you create a Replication policy, the policy automatically creates a replication topology that distributes data from the data source to the specified targets in your environment. The replication topology is a graphical representation of how the Replication policy distributes data.

376 StorageX Administrator’s Guide

Page 395: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Disaster Recovery policy failover 7

By default, data is distributed from the source target to each destination target. However, you can modify the replication topology to distribute data in a way that better fits your environment.

For example, you can configure the replication topology to copy data to a series of targets in sequence, creating a cascaded topology. If you have three targets for a particular data source, the policy automatically configures the source to replicate data to Targets 1, 2, and 3 all at the same time.

You can delete the linkages from the source to Targets 2 and 3 and add a new linkage between Targets 1 and 2 and another between Targets 2 and 3. The Replication policy then replicates data sequentially from the source to Target 1, then from Target 1 to Target 2, and then from Target 2 to Target 3.

For more information about configuring replication topology, see “Modifying the replication topology” on page 407.

Understanding Disaster Recovery policy failoverThe primary function of a Disaster Recovery policy in StorageX is to provide as close to continuous access to data as possible. In the event of a disaster, StorageX shortens the restore window from hours or days to minutes without requiring client reconfiguration or network rerouting.

StorageX offers several options that you can use to execute failover for link targets that are members of a Disaster Recovery policy. The following example illustrates the failover options that you can select when you configure a policy.

Example

For this example, assume that you have a Disaster Recovery policy named Houston DR policy with two links, Link1 and Link4, and each link has two targets. The targets for Link1 are:

• \\mara\FolderA• \\ARGOS\FolderAThe targets for Link4 are:

• \\mara\FolderD• \\ARGOS\FolderDThe primary target of both links is online.

Now assume that the Link1 target \\mara\FolderA becomes unavailable. In this situation, StorageX would take the following actions, depending on your failover configuration:

• If you selected only Automatically failover in the policy, Link1 would fail over to \\Argos\FolderA, and Link4 would continue to have \\mara\FolderD as the online target.

• If you selected Automatically failover and Failover all links in the policy, Link1 would fail over to \\ARGOS\FolderA and Link4 would fail over to \\ARGOS\FolderD.

• If you selected Automatically failover and Failover all links in the policy and specified that you wanted to monitor only Link1, Link1 would fail over to \\ARGOS\FolderA, and Link4 would fail over to \\ARGOS\FolderD. However, if you selected the option to monitor only Link4, failover would not be initiated. This option is useful when all the link targets are contained in a single resource. If only one link is monitored, the level of resources used in monitoring is reduced.

The following topics provide more information about understanding Disaster Recovery failover:

• “Disaster Recovery failover options” on page 378

StorageX Administrator’s Guide 377

Page 396: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Disaster Recovery policy failover7

• “Understanding failover topology” on page 379

• “Understanding failover in NetApp-based resource monitoring” on page 379

Disaster Recovery failover optionsDisaster Recovery policies provide the following failover options:

Automatically failoverAutomatically make a secondary resource or target the primary resource or target when the initial primary resource or target is not available. StorageX performs automatic failover in the order in which targets are arranged in the failover topology.

For example, if the first target in the topology becomes unavailable, the link fails over to the second target in the topology. If a given secondary target cannot be activated, StorageX tries to activate the next secondary target, in the order configured in the failover topology. When you set up automatic failover for a monitored link, you must also set up the failover topology for all link targets. For more information, see “Understanding failover topology” on page 379.

Failover all links in case of failoverAutomatically switch to the standby target of all the links in the policy when any active target that is a member of the policy is not available.

NOTEThis option is not available for Disaster Recovery policies that monitor NetApp resources.

Run user decision script to determine the health of the resources.When the Disaster Recovery policy runs, automatically run a user decision script to monitor the health of your resources and links and determine whether the policy needs to make a secondary resource or target the new primary resource or target.

For more information about using batch files and user decision scripts with Disaster Recovery policies, see “Using batch files with Disaster Recovery or Replication policies” on page 410.

Break third party replication when failing overAutomatically stop any third-party replication processes when StorageX detects a failure. For example, you can configure StorageX to stop NetApp SnapMirror replication in the event of a failure.

NOTEThis option is not available for Disaster Recovery policies that monitor DFS links or non-NetApp storage resources.

Monitor a Master LinkAutomatically make a secondary target the primary target when a specific master link is not available.

In some environments, you may not need to actively monitor every link using a Disaster Recovery policy. Instead, you can configure one of your monitored DFS links to act as the master link for the policy. StorageX monitors the master link for the Disaster Recovery policy, and if that link fails, StorageX automatically fails over all links monitored by the policy.

378 StorageX Administrator’s Guide

Page 397: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Disaster Recovery policy failover 7

For example, if you have a Disaster Recovery policy monitoring multiple links on a single server, you do not need to check every single link to determine whether the server is active or has failed. You can configure a link pointing to your C$ share on the server as the master link for the policy, and if the server stops working, StorageX knows to fail over all the links monitored by that policy, since the host computer is no longer available.

If you create a Disaster Recovery policy to monitor a CIFS-based storage resource, StorageX automatically monitors the resource using a master link. In this case, the master link is the first link added to the policy.

For more information about using master links, “Configuring Disaster Recovery policies to monitor master links” on page 395.

NOTEThis option is not available for Disaster Recovery policies that monitor NetApp resources.

Understanding failover topologyWhen you create a Disaster Recovery policy, StorageX sets up a failover topology for the targets of the links monitored by the policy. The failover topology is a graphical representation of the sequence in which a Disaster Recovery policy fails over the monitored links.

StorageX creates a default failover topology for each monitored link in the Disaster Recovery policy, which fails over automatically to the next link target listed in the Summary view. However, you can configure the topology to follow a different sequence.

For example, if you have a series of four link targets for a particular link, and Targets 1, 3, and 4 are all located in the same region, you may not want the policy to automatically fail over to Target 2, which is in a different region. You can modify the default topology to fail over from Target 1 to Target 3 and then to Target 4, skipping Target 2 entirely.

NOTES:

• You cannot create a linkage from a link target back to the link itself.

• You also cannot create a failover topology that diverges into multiple endpoints. Each topology must be linear, failing over from one target to the next target in the topology.

For more information about configuring failover topology, see “Modifying the failover topology for a monitored link” on page 392.

Understanding failover in NetApp-based resource monitoringYou can easily set up SnapMirror replication from one or more file storage resources to another file storage resource or nearline storage device.

A NetApp-based Disaster Recovery policy can monitor for new resources on the source file storage resource. You select the new resources that will be added to the policy and you mirror the new resources to the destination file storage resource.

The policy can also monitor for the availability of a primary link target on the source file storage resource and automatically fail over the link to the standby target on the destination file storage resource when the primary target is not available.

StorageX Administrator’s Guide 379

Page 398: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Disaster Recovery policy planning considerations7

Disaster Recovery policy planning considerationsReview the following planning considerations before you create and implement Disaster Recovery policies in your environment:

• Carefully plan where each StorageX component (links, servers, and universal data engines) should be deployed. If the StorageX server becomes unavailable, neither failover nor data synchronization can be performed. User access to the primary storage target is not affected.

• The StorageX server communicates with the DFS namespace to initiate a failover.

• The StorageX server communicates directly with the storage targets to initiate data synchronization.

NOTEThe StorageX console does not have to be running for Disaster Recovery policies to function.

• If a DFS namespace served by a single system is used and becomes unavailable, failover cannot be performed, and users can access only the primary storage target until their referral times out. Adding additional servers to host copies of the namespace provides fault tolerance. To create copies of the namespace, you can create DFS namespace servers in the case of domain-based namespaces, or you can set up Namespace Availability policies to synchronize the logical structure of two or more stand-alone namespaces. An alternate approach for creating a highly available namespace is to host a stand-alone namespace on a Windows cluster server. For more information about DFS namespaces, refer to “Creating and Managing DFS Namespaces” on page 159.

• DFS namespaces containing links participating in Disaster Recovery policies can also be members of Namespace Availability policies. In this configuration, as with Disaster Recovery policies containing links from replicated domain-based namespaces, it is recommended that you configure the Disaster Recovery policies for manual failover rather than for automatic failover if the links target read/write data rather than read-only data. For more information about using Namespace Availability policies, see “Synchronizing DFS namespaces” on page 216.

• When you add a link to a Disaster Recovery policy using SnapMirror replication, the link should have only two targets. Ensure one target is the source and the other target is the destination of the SnapMirror.

• If you want to use a SnapMirror created outside of StorageX for a Disaster Recovery policy, ensure you initialize the SnapMirror before creating the policy. For detailed information on initializing a SnapMirror outside of StorageX, see “Initializing a SnapMirror destination,” in the Data ONTAP® Data Protection Online Backup and Recovery Guide For 7-Mode, available on the NetApp Support web site at https://library.netapp.com/ecmdocs/ECMP1196991/html/GUID-6816A0E6-951B-49F1-AF26-71CD381FB428.html.

• When planning replication, consider the available time you have to complete the operation and how much data you have to replicate. Adjust your replication schedule as necessary and consider expanding your universal data engine infrastructure to make replication faster.

• It is not recommended that you enable real-time virus scanning on file storage resources because replication throughput can be severely reduced.

• The benefits of differential replication are realized on slower links rather than on a LAN. Computational costs outweigh the benefits of differential replication on a LAN.

• When configuring replication, you should not configure overlapping source and destination directory hierarchies. This can result in unintended duplication of files.

380 StorageX Administrator’s Guide

Page 399: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Disaster Recovery policies 7

• When configuring replication options, carefully consider how much event detail you need. If you gather information about all files, it affects performance. As a compromise between performance and the need for feedback, it is recommended that you gather information only when an error is encountered.

• When transferring data between NTFS source and destination, consider inherited permissions and how they will affect permissions on the source and destination. If the source and destination inherit different permission settings from their parents, the result will be different file permissions between the source and destination.

• It is not recommended that you perform full backups during a replication operation because backups can change archive attribute settings and trigger massive differences between source and destination.

• There is a replication time delay between primary and secondary contents. If a primary target becomes unavailable, there is no guarantee that all the contents of the primary target are replicated to the standby targets.

Account requirements for Disaster Recovery policiesThe account used by the StorageX server must have permission to make modifications to the DFS namespace containing the links in the Disaster Recovery policy. If the account lacks these permissions, StorageX cannot control the online/offline state of the link targets. For more information about permission requirements, “StorageX server service account requirements” on page 16.

Requirements for Disaster Recovery policy linksBefore you add links to a Disaster Recovery policy, review the following requirements:

• The account used by the StorageX server must have permission to make modifications to the DFS namespace containing the link or links in the Disaster Recovery policy. If the account lacks this permission, StorageX cannot control the online/offline state of the link targets.

• You should add only links that have shared folders as their targets to Disaster Recovery policies. Due to universal data engine location and DFS referral considerations, it is not recommended that you add links to Disaster Recovery policies that have a DFS namespace or another link as their target.

• Each link that you add to a Disaster Recovery policy that targets CIFS data should have at least two targets.

• When you add a link to a Disaster Recovery policy using SnapMirror replication, the link should have only two targets. Make sure that one target is the source and the other target is the destination of the SnapMirror.

Creating Disaster Recovery policiesUse the Disaster Recovery Policy Wizard to create Disaster Recovery policies. You provide a name for a new policy, select the monitoring type, specify the primary storage resource, specify the secondary storage resource, and add links. A policy can contain multiple links with replicated targets, logical folders, and DFS namespaces.

NOTES:

StorageX Administrator’s Guide 381

Page 400: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Disaster Recovery policies7

• Namespaces containing links participating in Disaster Recovery policies can also be members of Namespace Availability policies. For more information about Namespace Availability policies, see “Synchronizing DFS namespaces” on page 216.

• Once you add a DFS link to a Disaster Recovery policy, you cannot modify the link, including adding additional link targets. Ensure you add a backup link target before you monitor a link using a Disaster Recovery policy.

To create a new Disaster Recovery policy

1. In the StorageX Console, click the Disaster Recovery tab.

2. Right-click My Policies and click New Disaster Recovery Policy to open the Disaster Recovery Policy Wizard.

3. Review the welcome message, and then click Next.

4. On the Policy Name and Description dialog box, complete the following steps:

a. In the Name field, type a unique name to identify the policy. The name is displayed in the tree pane under My Policies, in alphabetical order by default.

b. In the Description field, type a word or phrase that describes the policy.

c. Click Next.

5. If you want to monitor your CIFS-based storage resources, complete the following steps:

a. On the Select Monitoring Type dialog box, select Monitor the availability of storage resources.

b. Click Next.

c. On the Specify Primary Storage Resource dialog box, type the UNC path or the machine name for the CIFS resource you want to use as your primary storage resource or click the ellipsis (...) button to browse to and select the resource.

d. Click Next.

e. If you specified a NetApp resource but want to monitor CIFS resources, on the Configure Monitoring dialog box, click Monitor CIFS Resources.

f. On the Specify Secondary Storage Resource dialog box, type the UNC path or the machine name for the CIFS resource you want to use as your secondary storage resource or click the ellipsis (...) button to browse to and select the resource.

g. Click Next.

6. If you want to monitor your NetApp-based storage resources using SnapMirror, complete the following steps:

a. On the Select Monitoring Type dialog box, select Monitor the availability of storage resources.

b. Click Next.

c. On the Specify Primary Storage Resource dialog box, type the UNC path or the machine name for the NetApp resource you want to use as your primary storage resource or click the ellipsis (...) button to browse to and select the resource.

d. Click Next.

382 StorageX Administrator’s Guide

Page 401: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Disaster Recovery policies 7

a. On the Configure Monitoring dialog box, select Monitor NetApp Resources.

b. On the Select NetApp Resources dialog box, click the Add icon to browse to and select the NetApp volume or qtree you want to monitor.

c. Click Next.

d. On the Configure NetApp SnapMirror dialog box, select a SnapMirror to use as the destination and then click Next.

e. If you want to create a new SnapMirror, select Create New SnapMirror, click Next, and complete the steps in the Create SnapMirror dialog box. For more information about creating SnapMirrors, see “Creating SnapMirrors on Data ONTAP file storage resources” on page 153.

7. If you only want to monitor your DFS link targets, complete the following steps:

a. On the Select Monitoring Type dialog box, select Monitor the availability of targets of DFS links.

b. Click Next.

8. On the Select DFS Links dialog box, type the UNC path to a DFS link you want to monitor or click the Add icon to browse to and select the DFS link.

NOTEYou can monitor multiple DFS links with a single Disaster Recovery policy. However, you cannot manage the same DFS link with multiple Disaster Recovery policies. You can only select DFS links contained in a namespace that you have added to My Namespaces.

9. If you only want to monitor DFS links and you want to configure the failover topology for a link, complete the following steps:

a. Select the link and click Configure Link Topology.

b. If you want to delete an existing linkage, right-click the linkage and select Delete, then click Yes to confirm.

c. If you want to create a new linkage, right-click the canvas and select New Linkage, select the source DFS link, then select the destination DFS link.

NOTEYou cannot create a linkage from the destination link back to the source link.

d. When finished, click OK.

10. Click Next.

11. If you only want to monitor DFS links and you did not configure a failover topology as in step 9, click Yes to confirm.

12. On the Disaster Recovery Policy Summary dialog box, verify the settings you specified for the new Disaster Recovery policy, and then click Finish.

13. If you want to start monitoring, right-click the new policy and select Start Monitoring Now.

14. In the Summary pane, verify that the policy started monitoring correctly.

StorageX Administrator’s Guide 383

Page 402: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Scheduling Disaster Recovery policies7

NOTEIf the Summary pane displays the message “Link does not have backup target(s).” for one or more of your monitored DFS links, you must remove the link from the policy, add a new target to the link, then add the link back to the policy. For more information about removing a DFS link from a policy, see “Removing DFS links from Disaster Recovery policies” on page 396. For more information about adding DFS links to a policy, see “Adding DFS links to Disaster Recovery policies” on page 393.

Scheduling Disaster Recovery policiesBy default, when you create a Disaster Recovery policy, the Disaster Recovery Policy Wizard automatically configures the policy to run on a scheduled basis. The new policy includes three separate schedules:

• Discovery Schedule

• Health Monitoring Schedule

• Replication Schedule

If you want to modify or disable any of the default schedules, you can change the schedule settings in the Disaster Recovery policy properties.

NOTESettings on the Replication Schedule tab of the Properties window are not available for Disaster Recovery policies monitoring NetApp-based storage resources.

To schedule a Disaster Recovery policy

1. In the StorageX Console, click the Disaster Recovery tab.

2. In the left tree pane, browse to and right-click the Disaster Recovery policy you want to schedule, and then click Properties.

3. If you want to modify or disable the default Discovery Schedule, complete the following steps:

a. Click the Discovery Schedule tab.

b. If you want to disable the Discovery Schedule, clear Use a schedule to discover new resources for this policy.

c. If you want to create a new schedule, click New and configure a new schedule.

d. If you want to use or modify an existing schedule, select the schedule from the list and modify it as needed.

e. If you want to delete a schedule, select the schedule from the list and click Delete.

4. If you want to modify or disable the default Health Monitoring Schedule, complete the following steps:

a. Click the Health Monitoring Schedule tab.

b. If you want to disable the Health Monitoring Schedule, clear Use a schedule to monitor health for this policy.

c. If you want to create a new schedule, click New and configure a new schedule.

384 StorageX Administrator’s Guide

Page 403: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Manually failing over Disaster Recovery policies 7

d. If you want to use or modify an existing schedule, select the schedule from the list and modify it as needed.

e. If you want to delete a schedule, select the schedule from the list and click Delete.

5. If you want to modify or disable the default Replication Schedule, complete the following steps:

a. Click the Replication Schedule tab.

b. If you want to disable the Replication Schedule, clear Use a schedule to replicate data for this policy.

c. If you want to create a new schedule, click New and configure a new schedule.

d. If you want to use or modify an existing schedule, select the schedule from the list and modify it as needed.

e. If you want to delete a schedule, select the schedule from the list and click Delete.

6. Click OK.

Manually failing over Disaster Recovery policiesIf a failure occurs in your environment, and you need StorageX to fail over your primary target to the secondary target, you can manually set your Disaster Recovery policy to fail over, which then causes the primary target to fail over to the secondary. This may be necessary if the failure occurs in between the specified Health Monitoring Schedule interval, when StorageX has not yet detected the failure automatically.

NOTEWhen you start to manually fail over a Disaster Recovery policy, you cannot cancel the failover process.

To manually fail over a Disaster Recovery policy

1. In the StorageX Console, click the Disaster Recovery tab.

2. In the left tree pane, browse to and right-click the Disaster Recovery policy you want to fail over, and then click Failover all links.

3. If the primary target is still active, and you need to replicate files to the secondary target, complete the following steps:

a. Click Replicate.

b. After the replication process finishes, right-click the policy again and click Failover all links.

4. If you have replicated all files and are ready to fail over, click Change.

5. In the Summary pane, verify that the policy failed over all resources and links correctly.

StorageX Administrator’s Guide 385

Page 404: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying Disaster Recovery policies completed successfully7

Verifying Disaster Recovery policies completed successfullyAfter StorageX automatically fails over one or more targets or you manually fail over or fail back one or more targets using a Disaster Recovery policy, you can view policy status information and the policy manifest to verify that the policy completed successfully. The policy manifest provides detailed information about the last run of the policy.

You can also use information in the Alerts and Events views to verify whether a policy completed successfully and to troubleshoot issues. The Events view is a complete historical listing of events. StorageX appends new events to the list in the Events view every time you run a policy. The Alerts view provides information for only the latest run of a policy. Every time you run a policy, StorageX deletes the alerts from the previous run.

You can export policy manifests and alert and event details and save them as reports in *.tsv format. This information can be useful not only for auditing purposes, but also for regulatory compliance purposes.

When you verify whether a Disaster Recovery policy completed successfully, ensure you check to see if StorageX encountered any locked files during the policy run. StorageX cannot replicate files that are locked on the primary resource to the secondary resource.

You can see if StorageX encountered any locked files during replication by selecting the policy in the left tree pane, and then in the right pane, in the Replication Summary area, reviewing the information displayed in the Files Failed column. The Files Failed column shows the number of files that StorageX was not able to copy from the source and the destination. The most common reason for StorageX failing to copy a file is that the file was locked because it was in use by a user during replication. If you want to be able to see exactly which files failed, you can view this information in the policy manifest if you select the Only list files that encounter errors option in the Event details field on the General Options tab for a Disaster Recovery policy.

If you used a batch file in a Disaster Recovery policy and the policy did not complete successfully, ensure you met requirements for using batch files. For more information, see “Using batch files with Disaster Recovery or Replication policies” on page 410.

To verify a Disaster Recovery policy completed successfully

1. In the StorageX Console, click the Disaster Recovery tab.

2. In the left tree pane, select the Disaster Recovery policy you want to verify.

3. In the center pane, review the following information in the Monitoring Summary area:

• Last monitoring status - Displays summary status information for the most recent run of the Disaster Recovery policy health monitoring task.

If the policy has not yet been run, Not run displays.

If the policy completed successfully, Completed successfully is displayed.

If the policy successfully failed over all monitored resources and links, Resource(s)/Link(s) have failed over displays.

If the policy could not automatically fail over one or more monitored resources or links, Resource(s)/Link(s) need manual failover displays. To complete the policy run, you must manually fail over any resources or links that remain in their initial state. For more information about manually failing over your primary target, see “Manually failing over Disaster Recovery policies” on page 385.

If you or someone else canceled the policy, Canceled displays.

386 StorageX Administrator’s Guide

Page 405: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying Disaster Recovery policies completed successfully 7

If the policy ran but encountered an error with a user decision script, Error code returned from user decision script or Fail to run user decision script displays. Verify the user decision script specified in the Failover Scripting tab of the policy Properties is correct. For more information about configuring user decision scripts for Disaster Recovery policies, see “Using batch files with Disaster Recovery or Replication policies” on page 410.

If the policy completed with errors or warnings, Completed with errors or Completed with warnings displays. Address the issue causing the error or warning and then retry running the policy. To see the cause of the error or warning, select the policy in the left tree pane, and then in the center pane, in the Monitoring Summary area, click View Monitoring Details. When you click View Monitoring Details, StorageX displays the manifest for the health monitoring task. The manifest provides additional details about the policy monitoring run.

After you have addressed the error or warning, you can restart monitoring manually or wait until the next scheduled health monitoring task, as configured in the policy Properties. To restart monitoring manually, right-click the policy and then select Start Monitoring Now.

If the policy is still in progress, In progress displays.

If the last run of the policy stopped unexpectedly because of an issue outside of StorageX, Unknown displays. This status indicates that due to a major external issue like a database failure, unexpected reboot, or power outage, StorageX was unable to send the final status of the policy run to the database. We recommend that you re-run the policy by right-clicking the policy in the left tree pane and selecting Start Monitoring Now.

• Monitoring Status - Displays the status of each link monitored by the policy.

If the link is in an unfailed-over, normal state and has at least one backup target, Link is in normal state displays.

If the link is in an unfailed-over, normal state but does not have any backup targets, Link does not have backup target(s) displays. StorageX cannot fail over links that do not have backup targets. To correctly configure the DFS link, remove the link from the policy, add a secondary link target, re-add the link to the policy, right-click the policy, and then select Start Monitoring Now.

If the policy successfully failed over the monitored link, Link is failed over displays.

If the policy could not automatically fail over the monitored link, Link requires manual failover displays. To complete the policy run, you must manually fail over the link. For more information about manually failing over the primary target of a DFS link, see “Manually failing over Disaster Recovery policies” on page 385.

If the policy encountered an issue with the monitored link during the policy run, Link is in a bad state and requires manual operation on the link targets displays. This indicates that StorageX encountered a problem with the DFS server itself. For example, StorageX may not be able to retrieve information on the DFS link from the DFS server due to a permission issue with that server, or the link targets for the DFS link were modified outside of StorageX.

When you see this status, you must manually resolve the issue with the DFS server before StorageX can successfully monitor or fail over the DFS link. After you have addressed the issue, you can restart monitoring manually or wait until the next scheduled health monitoring task, as configured in the policy Properties. To restart monitoring manually, right-click the policy and then select Start Monitoring Now.

StorageX Administrator’s Guide 387

Page 406: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying Disaster Recovery policies completed successfully7

If the policy that monitors the link is currently running, Link is in an unknown state displays. StorageX updates this field with information about the monitored link as policy actions complete.

4. Review the following information in the Replication Summary area:

• Last Replication Status - Displays summary status information for the most recent run of the Disaster Recovery policy.

If the policy has not replicated data previously, Not run displays.

If the last policy run completed successfully, Completed successfully displays.

If the last policy run completed with errors or warnings, Completed with errors or Completed with warnings displays. Address the issue causing the error or warning and then retry the policy. To see the cause of the error or warning, select the policy in the left tree pane, and then in the center pane, in the Replication Summary area, click the Last Replication Status status. When you click the status, StorageX displays the manifest for the policy. The manifest provides additional details about the policy run. In the tree displayed in the left pane of the manifest, expand Replication and any sub-nodes in the tree to see the specific error or warning encountered.

After you have addressed the error or warning, you can restart the policy manually or wait until the next scheduled run, as configured in the policy Properties. To restart the Replication policy manually, right-click the policy and then select Start Replication Now.

If the last policy run was canceled, Canceled displays.

If StorageX could not complete all replication tasks in the policy, Incomplete replication to all intended targets displays. This indicates that at least one replication task completed successfully, and at least one replication task completed with errors. This issue may be caused by a particular file being used by an end user while the replication task is running.

Address the issue causing the replication error and then retry the policy. To view any errors or warnings for the policy run, select the policy in the left tree pane, and then in the center pane, in the Replication Summary area, click the Last Replication Status status. When you click the status, StorageX displays the manifest for the policy. In the tree displayed in the left pane of the manifest, expand Replication and any sub-nodes in the tree to see any errors or warnings encountered.

After you have addressed the issue, you can restart the policy manually or wait until the next scheduled run, as configured in the policy Properties. To restart the Replication policy manually, right-click the policy and then select Start Replication Now.

If the last policy run is still in progress, In Progress displays.

If the last policy run stopped unexpectedly because of an issue outside of StorageX, Unknown displays. This status indicates that due to a major external issue like a database failure, unexpected reboot, or power outage, StorageX was unable to send the final status of the policy run to the database. We recommend that you re-run the policy by right-clicking the policy in the left tree pane and selecting Start Replication Now.

5. In the center pane, in the Replication Summary area, you can optionally review the last 30 replication tasks, including the following information:

• Completion State - Displays the replication status for each resource monitored by the policy.

If the policy has not replicated data previously for the resource, Not Run displays.

388 StorageX Administrator’s Guide

Page 407: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying Disaster Recovery policies completed successfully 7

If the last replication completed successfully for the resource, Completed Successfully displays.

If the last replication completed with errors or warnings for the resource, Completed With Errors or Completed With Warnings displays. Address the issue causing the error or warning and then retry the replication task. To see the cause of the error or warning for the resource, select the policy in the left tree pane, and then in the center pane, in the Replication Summary area, click the View Details link in the Event Details column that applies to the resource that has an issue. When you click the View Details link, StorageX displays the manifest for the policy run and the replicated resource.

After you have addressed the error or warning, you can restart replication manually or wait until the next scheduled replication task, as configured in the policy Properties. To restart replication manually, right-click the policy and then select Start Replication Now.

If the last replication was canceled for the resource, Canceled displays.

If the last replication is still in progress for the resource, In Progress displays.

If the last replication for the resource stopped unexpectedly because of an issue outside of StorageX, Unknown displays. This status indicates that due to a major external issue like a database failure, unexpected reboot, or power outage, StorageX was unable to send the final status of the replication task to the database. We recommend that you re-run replication by right-clicking the policy in the left tree pane and selecting Start Replication Now.

• Source - Displays the path for the source specified for the policy.

• Destination - Displays the path for the destination specified for the policy.

• Files Copied - Displays the number of files copied during replication.

• Bytes Copied - Displays the number of bytes copied during replication.

• Files Security Copied - Displays the number of files where file attributes were copied during replication. This column does not display the number of files where file data was copied.

• Files in Sync - Displays the number of files in sync between the source and destination during replication.

• Bytes in Sync - Displays the number of bytes in sync between the source and destination during replication.

• Files Deleted - Displays the number of files deleted during replication. A number displays in this field only if you selected the Delete orphaned files and folders on the destination setting on the General Options tab for a Disaster Recovery policy.

• Bytes Deleted - Displays the number of bytes deleted during replication. A number displays in this field only if you selected the Delete orphaned files and folders on the destination setting on the General Options tab for a Disaster Recovery policy.

• Files Failed - Displays the number of files that StorageX was not able to copy from the source and the destination. The most common reason for StorageX failing to copy a file is that the file was locked because it was in use by a user during the policy run. If you want to be able to see exactly which files failed, you can view this information in the policy manifest if you selected the Only list files that encounter errors option in the Event details field on the General Options tab for a Disaster Recovery policy.

• Data Engine - Displays the name of the computer that hosts the StorageX universal data engine that performed the replication.

StorageX Administrator’s Guide 389

Page 408: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying Disaster Recovery policies completed successfully7

• Event Details - Displays a View Details link to a policy manifest that provides additional detailed information about the replication task. When you click the View Details link and open up the policy manifest, you can see detailed information about the replication task, including number of files and folders copied, number of files and folders in sync, number of files and folders deleted, number of files failed, and more.

If you want to save the detailed information in the policy manifest to a .tsv report, on the Operation Details dialog box, click Export. In the Specify Report Options dialog box, you can specify a file name and the location where you want to save the report. For more information, click the Help button on the dialog box.

• Started - Displays the date and time the replication task started.

• Stopped - Displays the date and time the replication task ended.

• Queued - Displays the time the replication task was queued for the universal data engine to run.

6. Review the following information in the Discovered Candidates area:

• Last Discovery Run - Displays the state of the last discovery task run and the time the run occurred.

If the discovery task is still in progress, In progress displays.

If the discovery task has not yet been run, Not run displays.

If the discovery task completed successfully, Completed successfully is displayed.

If the discovery task found new DFS links to monitor, New item(s) are found displays. You can then add discovered DFS links to the Disaster Recovery policy or exclude discovered links from the Discovered Candidates list. For more information about discovering new links to monitor, see “Understanding Disaster Recovery discovery” on page 396.

If you or someone else canceled the discovery task, Canceled displays.

If the discovery task completed with errors or warnings, Completed with errors or Completed with warnings displays. Address the issue causing the error or warning and then retry running the discovery task. To see the cause of the error or warning, select the policy in the left tree pane, and then in the center pane, in the Discovered Candidates area, click the Last Discovery Run status. StorageX displays the manifest for the discovery task run. The manifest for the policy run provides additional details about the policy monitoring.

After you have addressed the error or warning, you can manually discover new DFS links or wait until the next scheduled discovery task, as configured in the policy Properties. To manually discover new DFS links to monitor, right-click the policy and then select Discover new resources.

If the discovery task stopped unexpectedly because of an issue outside of StorageX, Unknown displays. This status indicates that due to a major external issue like a database failure, unexpected reboot, or power outage, StorageX was unable to send the final status of the discovery task to the database. We recommend that you re-run discovery by right-clicking the policy in the left tree pane and selecting Discover new resources.

7. If you want to see all of the events generated during Disaster Recovery monitoring, discovery, replication, or failover, click the Events view to see events associated with the execution of the policy.

8. If you want to view all the details for a particular event, complete the following steps:

390 StorageX Administrator’s Guide

Page 409: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Manually failing back Disaster Recovery policies 7

a. Double-click the event in the Events view to open the Event Viewer dialog box.

b. Click Details to view event details.

c. If you want to save the event details to a report, in the Event Details dialog box, click Export. In the Specify Report Options dialog box, you can specify a file name and the location where you want to save the report. For more information, click the Help button on the dialog box.

9. If you want to check for any errors or warnings generated during Disaster Recovery monitoring, discovery, replication, or failover, click the Alerts view.

10. If you want to view all the details for a particular alert, complete the following steps:

a. Double-click the alert in the Alerts view to open the Alert Details dialog box.

b. If you want to save the alert details to a report, in the Alert Details dialog box, click Export. In the Specify Report Options dialog box, you can specify a file name and the location where you want to save the report. For more information, click the Help button on the dialog box.

Manually failing back Disaster Recovery policiesAfter a failure in your environment has been resolved, you may need to fail back from your secondary target to the primary. You can use the Disaster Recovery feature to fail back your resources and links to their original state.

You can manually fail back a single link, selected links, or all links in a Disaster Recovery policy. StorageX fails back links from the active target to the target above the active target, in the order in which the targets are arranged in the link.

To manually fail back links in a Disaster Recovery policy

1. In the StorageX Console, click the Disaster Recovery tab.

2. If you want to manually fail back a single link in a Disaster Recovery policy, complete the following steps:

a. In the left tree pane, click the Disaster Recovery policy. The Summary tab for the policy appears in the content pane.

b. Under These are the DFS links managed by this policy, right-click a link and click Failback.

3. If you want to manually fail back all links in a Disaster Recovery policy, in the left tree pane, browse to and right-click the Disaster Recovery policy you want to fail back to its original state, and then click Failback all links.

4. If the secondary target is still active, and you need to replicate files to the primary target, complete the following steps:

a. Click Replicate.

b. After the replication process finishes, right-click the policy again and click Failback all links.

5. If you have replicated all files and are ready to fail back, click Change.

6. In the Summary pane, verify that the policy failed back correctly to all primary targets.

StorageX Administrator’s Guide 391

Page 410: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Resynchronizing SnapMirrors for Disaster Recovery failback7

Resynchronizing SnapMirrors for Disaster Recovery failbackWhen a failover breaks the SnapMirror and redirects users to the alternate target, you need to update the repaired source and re-establish the original configuration of the SnapMirror.

For detailed information on resynchronizing SnapMirrors after a failover, see “Retrieving data for disaster recovery: A special use of snapmirror resync,” in the Data ONTAP® Data Protection Online Backup and Recovery Guide For 7-Mode, available on the NetApp Support web site at https://library.netapp.com/ecmdocs/ECMP1113957/html/GUID-FBF3CE88-BB13-43A6-B01F-A194F9F10798.html.

Managing Disaster Recovery policiesThis section explains how to manage Disaster Recovery policies. For more information about creating Disaster Recovery policies, see “Creating Disaster Recovery policies” on page 381.

The following topics provide more information about managing Disaster Recovery policies:

• “Modifying Disaster Recovery policy properties” on page 392

• “Modifying the failover topology for a monitored link” on page 392

• “Adding DFS links to Disaster Recovery policies” on page 393

• “Configuring email notification options for Disaster Recovery policies” on page 394

• “Configuring Disaster Recovery policies to monitor master links” on page 395

• “Removing DFS links from Disaster Recovery policies” on page 396

• “Deleting Disaster Recovery policies” on page 396

Modifying Disaster Recovery policy propertiesAfter you create a Disaster Recovery policy, you can modify its properties or specify additional properties before you run the policy. Once you have run the policy, you cannot change the specified source or destination path for the policy. However, if the policy is set to run on a recurring schedule, you can make other changes to the policy that will be effective the next time the policy runs.

To modify the properties of a Disaster Recovery policy

1. In the StorageX Console, click the Disaster Recovery tab.

2. In the left tree pane, right-click a Disaster Recovery policy and then click Properties.

3. Click the tab for the properties that you want to update, and then specify options. as appropriate. For more information about each option, click the Help button on the dialog box.

4. When finished, click OK.

Modifying the failover topology for a monitored linkWhen you create a Disaster Recovery policy, the Disaster Recovery Policy Wizard automatically configures the failover topology for your monitored links unless you specifically configure the topology for each link.

For more information about failover topology, see “Understanding failover topology” on page 379.

392 StorageX Administrator’s Guide

Page 411: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Disaster Recovery policies 7

NOTES:

• You can only modify the failover topology for a Disaster Recovery policy that monitors DFS links. There is no failover topology for policies that monitor CIFS- or NetApp-based storage resources.

• You cannot create a linkage from a link target back to the link itself.

• You also cannot create a failover topology that diverges into multiple endpoints. Each topology must be linear, failing over from one target to the next target in the topology.

To modify the failover topology for a monitored link

1. In the StorageX Console, click the Disaster Recovery tab.

2. In the left tree pane, select the Disaster Recovery policy that monitors the link. The Summary tab for the policy appears in the content pane.

3. Under These are the DFS links managed by this policy, right-click the link for which you want to modify the failover topology and click Edit Failover Topology.

4. If you want to delete an existing linkage, right-click the linkage and select Delete, then click Yes to confirm.

5. If you want to create a new linkage, right-click the canvas and select New Linkage, select the source DFS link, then select the destination DFS link.

6. When finished, click OK.

7. If you want to set the primary link target to Online, click Yes to confirm.

8. If you do not yet want to set the primary link target to Online, click No.

Adding DFS links to Disaster Recovery policiesOnce you have created a Disaster Recovery policy, you can manually add DFS links to the policy. You can add multiple links to a policy by dragging the selected links to the policy. Before you add links to the policy, ensure you have reviewed the requirements for links in Disaster Recovery policies. For more information, see “Requirements for Disaster Recovery policy links” on page 381.

By default, StorageX creates a failover topology for each Disaster Recovery policy, which fails over automatically to the next link target listed in the Summary view. You can configure the failover topology to follow a different sequence. For more information about failover topologies, see “Understanding failover topology” on page 379. For more information about modifying a failover topology, see “Modifying the failover topology for a monitored link” on page 392.

To add DFS links to a Disaster Recovery policy

1. In the StorageX Console, click the Disaster Recovery tab.

2. If you want to add links from the policy, in the left tree pane, right-click a Disaster Recovery policy and then click Add Links to open the Add DFS Links to Disaster Recovery Policy Wizard.

3. If you want to add links from the My Namespaces folder, in the left tree pane, right-click one or more links to add and then click Add to policy to open the Add DFS Links to Disaster Recovery Policy Wizard.

StorageX Administrator’s Guide 393

Page 412: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Disaster Recovery policies7

NOTEWhen adding links from My Namespaces, you can select a maximum of 2000 links at one time.

4. Review the welcome message, and then click Next.

5. On the Select DFS Links dialog box, type the UNC path to a DFS link you want to monitor or click the Add icon to browse to and select the DFS link.

NOTEYou can monitor multiple DFS links with a single Disaster Recovery policy. However, you cannot manage the same DFS link with multiple Disaster Recovery policies. You can only select DFS links contained in a namespace that you have added to My Namespaces.

6. If you want to configure the failover topology for the new link, complete the following steps:

a. Select the link and click Configure Link Topology.

b. If you want to delete an existing linkage, right-click the linkage and select Delete, then click Yes to confirm.

c. If you want to create a new linkage, right-click the canvas and select New Linkage, select the source DFS link, then select the destination DFS link.

NOTEYou cannot create a linkage from the destination link back to the source link.

d. When finished, click OK.

7. Click Next.

8. If you want to use the default failover topology for links monitored by the policy, click Yes to confirm.

9. On the Add DFS Links to Disaster Recovery Policy Summary dialog box, verify the DFS links you want to add to the specified Disaster Recovery policy, and then click Finish.

Configuring email notification options for Disaster Recovery policiesYou can configure a Disaster Recovery policy to automatically notify one or more users each time the policy runs, each time the discovery task runs, and each time the health check runs. You can set a policy to send email notifications when the policy is canceled, when the policy completes successfully, when new DFS namespace items are found, or when resources or links have failed over, among other criteria.

StorageX sends Disaster Recovery policy email notifications either using an existing notification profile or a new notification profile created specifically for the policy.

To configure Disaster Recovery policy email notification options

1. In the StorageX Console, click the Disaster Recovery tab.

2. In the left tree pane, browse to and right-click a Disaster Recovery policy, and click Properties.

3. If you want to configure discovery notification settings, in the left pane, click Discovery Notification Settings.

394 StorageX Administrator’s Guide

Page 413: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Disaster Recovery policies 7

4. If you want to configure health monitoring notification settings, in the left pane, click Health Notification Settings.

5. If you want to configure replication notification settings, in the left pane, click Replication Notification Settings.

6. If you want to use an existing notification profile, click the Select an existing notification profile or create a new profile list and select the profile you want to use, then click Email is enabled for the selected notification profile.

7. If you want to create a new notification profile for the policy, complete the following steps:

a. Click the Select an existing notification profile or create a new profile list.

b. Click New.

c. Specify the SMTP settings you want to use for the new profile. For more information about the SMTP settings, click the Help button on the dialog box.

d. Specify the message settings you want to use for the new profile. For more information about the message settings, click the Help button on the dialog box.

e. Click Send Test Message to verify the profile settings are correct.

f. If you want to use the new notification profile for all notifications, click Enable all usage of this notification.

g. Click OK.

8. Click one or more criteria you want StorageX to use when sending email notifications. For more information about the possible notification criteria, click the Help button on the dialog box.

9. If you want to configure another notification setting for the same policy, repeat step 3 through step 8.

10. When finished click OK.

Configuring Disaster Recovery policies to monitor master linksIf you do not need to monitor every link using a Disaster Recovery policy, you can configure a monitored DFS link to be the master link for the policy. StorageX monitors the DFS link, and when that link cannot be contacted, the Disaster Recovery policy automatically fails over all links monitored by the policy.

For more information about using a master link in a Disaster Recovery policy, see “Understanding Disaster Recovery policy failover” on page 377.

NOTEMaster link monitoring does not apply to Disaster Recovery policies monitoring NetApp-based storage resources.

To configure a Disaster Recovery policy to monitor a master link

1. In the StorageX Console, click the Disaster Recovery tab.

2. In the left tree pane, right-click the Disaster Recovery policy you want to configure and then click Properties.

3. Click the Policy Options tab.

StorageX Administrator’s Guide 395

Page 414: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Disaster Recovery discovery7

4. Select the Monitor a Master Link check box.

5. Click the Monitor this master link drop-down menu and select the link you want to use as the master link.

NOTEIf you select the Monitor a Master Link option, you must select a master link to monitor.

6. Click OK.

Removing DFS links from Disaster Recovery policiesIf you no longer want to monitor a DFS link using a Disaster Recovery policy, you can remove that link from the policy.

NOTES:

• If you need to modify a DFS link, it may also be necessary to temporarily remove a link from a Disaster Recovery policy.

• You cannot remove a link from a Disaster Recovery policy that is designated as the master link for that policy. To remove a master link, first select a different link to be the master link for the policy or disable the Monitor a Master Link option in the policy properties.

To remove a DFS link from a Disaster Recovery policy

1. In the StorageX Console, click the Disaster Recovery tab.

2. In the left tree pane, select the Disaster Recovery policy you want to modify.

3. In the Summary pane, right-click the DFS link you want to remove and click Remove from Policy.

4. Click Yes to confirm.

Deleting Disaster Recovery policiesIf you no longer need a Disaster Recovery policy, you can delete the policy in the StorageX Console.

To delete a Disaster Recovery policy

1. In the StorageX Console, click the Disaster Recovery tab.

2. In the left tree pane, right-click the Disaster Recovery policy you want to delete and click Delete.

3. Click Yes to confirm.

Understanding Disaster Recovery discoveryIn addition to adding specific links and qtrees to your Disaster Recovery policies, you can configure your policies to automatically discover links and qtrees to monitor in your environment.

396 StorageX Administrator’s Guide

Page 415: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Disaster Recovery discovery 7

You must select the Enable Discovery option on each Disaster Recovery policy in order to discover new links and qtrees. If you try to discover resources without first enabling discovery, StorageX cannot find any new links.

After you enable discovery, you must add one or more DFS namespace paths to search for new links or qtrees. If you do not add at least one search path, StorageX does not display any discovered links or qtrees in the Discovered Candidates list.

For more information about creating Disaster Recovery policies, see “Creating Disaster Recovery policies” on page 381.

The following topics provide more information about configuring and modifying discovery settings for your Disaster Recovery policies:

• “Adding DFS search paths to Disaster Recovery policies” on page 397

• “Manually discovering new links and qtrees” on page 398

• “Adding discovered links or qtrees to Disaster Recovery policies” on page 398

Adding DFS search paths to Disaster Recovery policiesYou can configure an existing Disaster Recovery policy to search additional DFS paths when discovering new links and qtrees to monitor.

To add DFS search paths to a Disaster Recovery policy

1. In the StorageX Console, click the Disaster Recovery tab.

2. If you want to add one or more search paths directly to a policy, complete the following steps:

a. In the left tree pane, expand My Policies, right-click the policy for which you want to discover new links or qtrees to monitor, and then click Properties.

b. Click the DFS Namespaces tab.

c. If you have not previously enabled discovery for the policy, click the Enable Discovery check box.

NOTEYou must click this check box to enable StorageX to discover new links for this policy. If you do not click the check box, the discovery process cannot find any new resources.

d. In the Discover links under the following DFS namespace paths field, type the UNC path to a DFS namespace path you want to add to the policy for discovery or click the Add icon to browse to and select the DFS namespace path.

e. Click OK.

3. If you want to add a search path from the My Namespaces folder, complete the following steps:

a. In the left tree pane, expand My Namespaces, right-click a namespace you want to add to the discovery process for a policy, and then click Add to policy discovery to open the Add DFS Search Paths to Disaster Recovery Policy Wizard.

b. Review the welcome message, and then click Next.

c. On the Specify Policy dialog box, select the existing Disaster Recovery policy to which you want to add the DFS search path, and then click Next.

StorageX Administrator’s Guide 397

Page 416: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Disaster Recovery discovery7

d. On the Add DFS Search Paths to Disaster Recovery Policy Summary dialog box, verify the DFS search paths you want to add to the specified Disaster Recovery policy, and then click Finish.

Manually discovering new links and qtreesIf you do not want to wait for a Disaster Recovery policy to automatically discover new links and qtrees, you can force StorageX to immediately discover new links and qtrees using the policy’s discovery rules.

NOTES:

• You must click this check box to enable StorageX to discover new links for this policy. If you do not click the check box, the discovery process cannot find any new resources.

• Before forcing StorageX to discover new resources, refresh the DFS namespaces listed in the My Namespaces folder.

To manually discover new links or qtrees using a Disaster Recovery policy

1. In the StorageX Console, click the Disaster Recovery tab.

2. Right-click My Namespaces and click Refresh.

3. In the left tree pane, expand My Policies, right-click the policy for which you want to discover new links or qtrees to monitor, and then click Properties.

4. Right-click the policy and then click Discover new resources.

Adding discovered links or qtrees to Disaster Recovery policiesIf a Disaster Recovery policy discovers new links or qtrees, you can add those resources to the policy. StorageX displays any discovered links or qtrees in the center pane, under Discovered Candidates.

To add discovered links or qtrees to a Disaster Recovery policy

1. In the StorageX Console, click the Disaster Recovery tab.

2. In the left tree pane, expand My Policies and select the Disaster Recovery policy to which you want to add discovered links or qtrees.

3. In the Summary pane, navigate to Discovered Candidates.

4. If you want to exclude new links or qtrees from the policy, right-click one or more discovered candidates and then click Exclude.

5. If you want to add new links to the policy, complete the following steps:

a. Right-click one or more links and then click Add to policy to open the Add DFS Links to Disaster Recovery Policy Wizard.

NOTEWhen adding links from Discovered Candidates, you can select a maximum of 2000 links at one time.

b. Review the welcome message, and then click Next.

398 StorageX Administrator’s Guide

Page 417: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding Replication policies 7

c. On the Select DFS Links dialog box, select the DFS links you want to add to the policy.

NOTEYou can monitor multiple DFS links with a single Disaster Recovery policy. However, you cannot manage the same DFS link with multiple Disaster Recovery policies. You can only select DFS links contained in a namespace that you have added to My Namespaces.

d. Click Next.

e. On the Add DFS Links to Disaster Recovery Policy Summary dialog box, verify the DFS links you want to add to the specified Disaster Recovery policy, and then click Finish.

6. If you want to add new qtrees to the policy, complete the following steps:

a. Right-click one or more qtrees and then click Add to policy to open the Add Candidates to Disaster Recovery Policy Wizard.

b. Review the welcome message, and then click Next.

c. On the Configure NetApp SnapMirror dialog box, select a SnapMirror to use as the destination and then click Next.

d. If you want to create a new SnapMirror, select Create New SnapMirror, click Next, and complete the steps in the Create SnapMirror dialog box. For more information about creating SnapMirrors, see “Creating SnapMirrors on Data ONTAP file storage resources” on page 153.

e. Click Next.

f. On the Add Candidates to Disaster Recovery Policy Summary dialog box, verify the qtrees you want to add to the specified Disaster Recovery policy, and then click Finish.

Understanding Replication policiesReplication policies enable you to replicate CIFS or NFS data across a network, synchronizing data between two storage resources. Status information is provided about replication operations performed using the StorageX universal data engine. Replication policies replicate data in the same way that Disaster Recovery policies do, but do not monitor, fail over, or fail back resources.

You can easily and effectively manage Replication policies for storage resources:

• Status information about replication operations - Status information is provided about replication operations performed using a StorageX universal data engine.

• Allows horizontal scaling and load balancing - StorageX provides you with tools to replicate data in a single operation. These tools give you coordinated management of the logical and physical aspects of storage.

Like Phased Migration policies, Replication policies also copy file and directory attributes and permissions.

For more information about replication and replication topology, see “Understanding replication and replication topology” on page 376.

StorageX Administrator’s Guide 399

Page 418: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Replication policy planning considerations7

NOTEReplication policies do not copy the offline attribute (FILE_ATTRIBUTE_OFFLINE) when copying file or directory attributes during the replication process, because the file or directory is online by default after replication. If you want to configure the replicated file or directory to be offline, you must use a third-party tool to set the offline attribute after the replication process finishes.

Replication policy planning considerationsYou can choose the optimal replication mechanism for your configuration, whether it is the StorageX universal data engine for heterogeneous environments or another mechanism for homogeneous environments. StorageX enables you to configure replication at the folder level.

StorageX uses file-to-file copy to synchronize data across a network. Review the following planning considerations before configuring Replication policies in your environment:

• When planning replication, consider the available time you have to complete the operation and how much data you have to replicate. Adjust your replication schedule as necessary and consider expanding your universal data engine infrastructure to make replication faster.

• It is not recommended that you enable real-time virus scanning on file storage resources because replication throughput can be severely reduced.

• The benefits of differential replication are realized on slower links rather than on a LAN. Computational costs outweigh the benefits of differential replication on a LAN.

• When configuring replication, you should not configure overlapping source and destination directory hierarchies. Otherwise, unintended repeated duplication of files can result and can interfere with StorageX replication.

• When configuring replication options, carefully consider how much event detail you need. If you gather information about all files, it affects performance. As a compromise between performance and the need for feedback, it is recommended that you gather information only when an error is encountered.

• When transferring data between a source and a destination, consider inherited permissions and how they will affect permissions on the source and destination. If the source and destination are inheriting different permission settings from their parents, the result will be different file permissions between the source and destination.

• It is not recommended that you perform full backups during a replication operation because backups can change archive attribute settings and trigger massive differences between source and destination.

• A Replication policy synchronizes from its source to a number of read-only copies.

• There is a replication time delay between primary and secondary contents. If a primary target becomes unavailable, there is no guarantee that all the contents of the primary target are replicated to the standby targets.

• The StorageX console does not have to be running for Replication policies to function.

The following topics provide more information about planning for Replication policies:

• “Replication policy requirements” on page 401

• “Understanding unsupported file types for replication” on page 401

400 StorageX Administrator’s Guide

Page 419: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Replication policies 7

Replication policy requirementsReview the following requirements for Replication policies in StorageX:

• A policy can contain either a CIFS source and CIFS destinations or an NFS source and NFS destinations.

• Once you create a Replication policy for a CIFS or NFS source and destination(s), you cannot modify the policy to use a different protocol. For example, you cannot create a Replication policy with a CIFS source and three CIFS destinations, then go to the policy Properties window and change the source to an NFS source and the targets to NFS destinations. You must create a new Replication policy, instead.

• CIFS physical paths must be UNC paths. For example: \\<computer>\<share>• You can only add DFS links with targets that are physical paths. You cannot add a link that has

a DFS namespace or another link as its target.

• Links that are already members of Disaster Recovery policies cannot be members of a Replication policy because Disaster Recovery policies also replicate data. Multiple policies replicating data to the same link can cause a data integrity conflict.

Understanding unsupported file types for replicationWhile StorageX can replicate most types of files from a source to a destination, there are some specific file types that StorageX ignores during the replication process.

StorageX does not support replicating the following types of files:

• Encrypted files

• Reparse points

• CIFS symbolic links

NOTEStorageX does support replicating NFS symbolic links.

• Snapshot folders

• System volume information

• Local users

• Recycle Bin

Creating Replication policiesUse the Replication Policy Wizard to create Replication policies. You provide a name for a new policy, specify the source path, specify one or more target paths, and configure the replication topology.

Before you configure Replication policies, ensure you have reviewed the policy requirements and planning considerations. For more information about Replication policy requirements and planning, see “Replication policy planning considerations” on page 400 and “Replication policy requirements” on page 401.

StorageX Administrator’s Guide 401

Page 420: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating Replication policies7

To create a new Replication policy

1. In the StorageX Console, click the Disaster Recovery tab.

2. Right-click My Policies and click New Replication Policy to open the Replication Policy Wizard.

3. Review the welcome message, and then click Next.

4. On the Policy Name and Description dialog box, complete the following steps:

a. In the Name field, type a unique name to identify the policy. The name is displayed in the tree pane under My Policies, in alphabetical order by default.

b. In the Description field, type a word or phrase that describes the policy.

c. Click Next.

5. On the Specify Replication Source Path dialog box, type the path to the resource you want to use as the source for replication or click the ellipsis (...) button to browse to and select the resource.

NOTEYou can specify a path to either a physical CIFS or NFS resource or a DFS namespace link with one or more targets that are physical paths.

6. Click Next.

7. On the Specify Replication Target Paths dialog box, click the Add icon and then type the UNC or NFS path to one or more targets to which you want to replicate data or click the ellipsis button (...) to browse to and select the target paths you want to use.

8. If you want to configure the replication topology for your environment, complete the following steps:

a. Click Config Replication Topology.

b. If you want to delete an existing linkage, right-click the linkage and select Delete, then click Yes to confirm.

c. If you want to create a new linkage, right-click the canvas and select New Linkage, select the source, then select the target.

NOTEYou cannot create a linkage from the target back to the source.

d. When finished, click OK.

9. Click Next.

10. If you want to use the default replication topology the policy, click Yes to confirm.

11. On the Replication Policy Summary dialog box, verify the settings you specified for the new Replication policy, and then click Finish.

12. If you want to start the replication process, right-click the new policy and select Start Replication Now.

13. In the Summary pane, verify that the policy started the replication process correctly.

402 StorageX Administrator’s Guide

Page 421: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Running Replication immediately 7

Running Replication immediatelyOnce you have created a Disaster Recovery or Replication policy, you can wait for the policy to run on the default schedule specified for the policy on the Replication Schedule tab, or you can choose to run the replication process for the policy immediately.

If you want to run replication immediately for a policy, click the Disaster Recovery tab, right-click the Disaster Recovery or Replication policy for which you want to run replication, then click Start Replication Now. Click the Alerts tab to verify that the replication process finished successfully.

For more information about scheduling Disaster Recovery policies, see “Scheduling Disaster Recovery policies” on page 384. For more information about scheduling Replication policies, see “Scheduling Replication policies” on page 403.

For more information about creating new Disaster Recovery policies, see “Creating Disaster Recovery policies” on page 381. For more information about creating new Replication policies, see “Creating Replication policies” on page 401.

Scheduling Replication policiesWhen you create a Replication policy, the Replication Policy Wizard automatically configures the policy to replicate data on a scheduled basis. If you want to modify or disable the replication schedule, you can change the schedule settings in the policy properties.

To schedule a Replication policy

1. In the StorageX Console, click the Disaster Recovery tab.

2. In the left tree pane, browse to and right-click the Replication policy you want to schedule, and then click Properties.

3. Click the Replication Schedule tab.

4. If you want to disable the Replication Schedule, clear Use a schedule to replicate data for this policy.

5. If you want to create a new schedule, click New and configure a new schedule.

6. If you want to use or modify an existing schedule, select the schedule from the list and modify it as needed.

7. If you want to delete a schedule, select the schedule from the list and click Delete.

8. Click OK.

Verifying Replication policies completed successfullyAfter StorageX automatically replicates data from a primary resource to a target using a Replication policy, you can view policy status information and the policy manifest to verify that the policy completed successfully. The policy manifest provides detailed information about the last run of the policy.

StorageX Administrator’s Guide 403

Page 422: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying Replication policies completed successfully7

You can also use information in the Alerts and Events views to verify whether a policy completed successfully and to troubleshoot issues. The Events view is a complete historical listing of events. StorageX appends new events to the list in the Events view every time you run a policy. The Alerts view provides information for only the latest run of a policy. Every time you run a policy, StorageX deletes the alerts from the previous run.

You can export policy manifests and alert and event details and save them as reports in *.tsv format. This information can be useful not only for auditing purposes, but also for regulatory compliance purposes.

When you verify whether a Replication policy completed successfully, ensure you check to see if StorageX encountered any locked files during the policy run. StorageX cannot replicate files that are locked on the primary resource to the target resource.

You can see if StorageX encountered any locked files during replication by selecting the policy in the left tree pane, and then in the right pane, in the Replication Summary area, reviewing the information displayed in the Files Failed column. The Files Failed column shows the number of files that StorageX was not able to copy from the source and the destination. The most common reason for StorageX failing to copy a file is that the file was locked because it was in use by a user during replication. If you want to be able to see exactly which files failed, you can view this information in the policy manifest if you select the Only list files that encounter errors option in the Event details field on the General Options tab for a Replication policy.

If you used a batch file in a Replication policy and the policy did not complete successfully, ensure you met requirements for using batch files. For more information, see “Using batch files with Disaster Recovery or Replication policies” on page 410.

To verify a Replication policy completed successfully

1. In the StorageX Console, click the Disaster Recovery tab.

2. In the left tree pane, select the Replication policy you want to verify.

3. Review the following information in the Replication Summary area:

• Last Replication Status - Displays summary status information for the most recent run of the replication task.

If the policy has not replicated data previously, Not run displays.

If the last replication completed successfully, Completed successfully displays.

If the last replication completed with errors or warnings, Completed with errors or Completed with warnings displays. Address the issue causing the error or warning and then retry the replication task. To see the cause of the error or warning, select the policy in the left tree pane, and then in the center pane, in the Replication Summary area, click the Last Replication Status status. When you click the status, StorageX displays the manifest for the replication task. The manifest provides additional details about the replication task run. In the tree displayed in the left pane of the manifest, expand Replication and any sub-nodes in the tree to see the specific error or warning encountered.

After you have addressed the error or warning, you can restart replication manually or wait until the next scheduled replication task, as configured in the policy Properties. To restart replication manually, right-click the policy and then select Start Replication Now.

If the last replication was canceled, Canceled displays.

404 StorageX Administrator’s Guide

Page 423: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying Replication policies completed successfully 7

If StorageX could not complete all replication tasks in the policy, Incomplete replication to all intended targets displays. This indicates that at least one replication task completed successfully, and at least one replication task completed with errors. This issue may be caused by a particular file being used by an end user while the replication task is running.

Address the issue causing the replication error and then retry the replication task. To view any errors or warnings for the replication task run, select the policy in the left tree pane, and then in the center pane, in the Replication Summary area, click the Last Replication Status status. When you click the status, StorageX displays the manifest for the replication task. In the tree displayed in the left pane of the manifest, expand Replication and any sub-nodes in the tree to see any errors or warnings encountered.

After you have addressed the issue, you can restart replication manually or wait until the next scheduled replication task, as configured in the policy Properties. To restart replication manually, right-click the policy and then select Start Replication Now.

If the last replication is still in progress, In Progress displays.

If the last replication stopped unexpectedly because of an issue outside of StorageX, Unknown displays. This status indicates that due to a major external issue like a database failure, unexpected reboot, or power outage, StorageX was unable to send the final status of the replication task to the database. We recommend that you re-run replication by right-clicking the policy in the left tree pane and selecting Start Replication Now.

4. In the center pane, in the Replication Summary area, you can optionally review the last 30 replication tasks, including the following information:

• Completion State - Displays the replication status for each resource monitored by the policy.

If the policy has not replicated data previously for the resource, Not Run displays.

If the last replication completed successfully for the resource, Completed Successfully displays.

If the last replication completed with errors or warnings for the resource, Completed With Errors or Completed With Warnings displays. Address the issue causing the error or warning and then retry the replication task. To see the cause of the error or warning for the resource, select the policy in the left tree pane, and then in the center pane, in the Replication Summary area, click the View Details link in the Event Details column that applies to the resource that has an issue. When you click the View Details link, StorageX displays the manifest for the policy run and the replicated resource.

After you have addressed the error or warning, you can restart replication manually or wait until the next scheduled replication task, as configured in the policy Properties. To restart replication manually, right-click the policy and then select Start Replication Now.

If the last replication was canceled for the resource, Canceled displays.

If the last replication is still in progress for the resource, In Progress displays.

If the last replication for the resource stopped unexpectedly because of an issue outside of StorageX, Unknown displays. This status indicates that due to a major external issue like a database failure, unexpected reboot, or power outage, StorageX was unable to send the final status of the replication task to the database. We recommend that you re-run replication by right-clicking the policy in the left tree pane and selecting Start Replication Now.

• Source - Displays the path for the source specified for the policy.

StorageX Administrator’s Guide 405

Page 424: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Verifying Replication policies completed successfully7

• Destination - Displays the path for the destination specified for the policy.

• Files Copied - Displays the number of files copied during replication.

• Bytes Copied - Displays the number of bytes copied during replication.

• Files Security Copied - Displays the number of files where file attributes were copied during replication. This column does not display the number of files where file data was copied.

• Files in Sync - Displays the number of files in sync between the source and destination during replication.

• Bytes in Sync - Displays the number of bytes in sync between the source and destination during replication.

• Files Deleted - Displays the number of files deleted during replication. A number displays in this field only if you selected the Delete orphaned files and folders on the destination setting on the General Options tab for a Replication policy.

• Bytes Deleted - Displays the number of bytes deleted during replication. A number displays in this field only if you selected the Delete orphaned files and folders on the destination setting on the General Options tab for a Replication policy.

• Files Failed - Displays the number of files that StorageX was not able to copy from the source and the destination. The most common reason for StorageX failing to copy a file is that the file was locked because it was in use by a user during the policy run. If you want to be able to see exactly which files failed, you can view this information in the policy manifest if you selected the Only list files that encounter errors option in the Event details field on the General Options tab for a Replication policy.

• Data Engine - Displays the name of the computer that hosts the StorageX universal data engine that performed the replication.

• Event Details - Displays a View Details link to a policy manifest that provides additional detailed information about the replication task. When you click the View Details link and open up the policy manifest, you can see detailed information about the replication task, including number of files and folders copied, number of files and folders in sync, number of files and folders deleted, number of files failed, and more.

If you want to save the detailed information in the policy manifest to a .tsv report, on the Operation Details dialog box, click Export. In the Specify Report Options dialog box, you can specify a file name and the location where you want to save the report. For more information, click the Help button on the dialog box.

• Started - Displays the date and time the replication task started.

• Stopped - Displays the date and time the replication task ended.

• Queued - Displays the time the replication task was queued for the universal data engine to run.

5. If you want to see all of the events generated during replication, click the Events view to see events associated with the execution of the policy.

6. If you want to view all the details for a particular event, complete the following steps:

a. Double-click the event in the Events view to open the Event Viewer dialog box.

b. Click Details to view event details.

c. If you want to save the event details to a report, in the Event Details dialog box, click Export. In the Specify Report Options dialog box, you can specify a file name and the location where you want to save the report. For more information, click the Help button on the dialog box.

406 StorageX Administrator’s Guide

Page 425: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Replication policies 7

7. If you want to check for any errors or warnings generated during replication, click the Alerts view.

8. If you want to view all the details for a particular alert, complete the following steps:

a. Double-click the alert in the Alerts view to open the Alert Details dialog box.

b. If you want to save the alert details to a report, in the Alert Details dialog box, click Export. In the Specify Report Options dialog box, you can specify a file name and the location where you want to save the report. For more information, click the Help button on the dialog box.

Managing Replication policiesThis section explains how to manage Replication policies. For more information about creating Replication policies, see “Creating Replication policies” on page 401.

The following topics provide more information about managing Replication policies:

• “Modifying Replication policy properties” on page 407

• “Modifying the replication topology” on page 407

• “Adding targets to Replication policies” on page 408

• “Removing targets from Replication policies” on page 409

• “Configuring email notification options for Replication policies” on page 409

• “Deleting Replication policies” on page 410

Modifying Replication policy propertiesAfter you create a Replication policy, you can modify its properties or specify additional properties.

NOTEIf you add, remove, or modify any targets of a Replication policy, StorageX resets the replication topology of the policy to its default. For more information about replication topology, see “Understanding replication and replication topology” on page 376.

To modify the properties of a Replication policy

1. In the StorageX Console, click the Disaster Recovery tab.

2. In the left tree pane, right-click a Replication policy and then click Properties.

3. Click the tab for the properties that you want to update, and then specify options. as appropriate. For more information about each option, click the Help button on the dialog box.

4. When finished, click OK.

Modifying the replication topologyAfter you create a Replication policy, you can reconfigure the replication topology for the policy to move data more effectively to specific targets. For example, you can modify the replication topology to group targets that are geographically close together.

StorageX Administrator’s Guide 407

Page 426: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Replication policies7

To modify the replication topology for a policy

1. In the StorageX Console, click the Disaster Recovery tab.

2. In the left tree pane, select the Replication policy you want to modify.

3. In the Replication Summary area of the center pane, click Modify Topology.

4. If you want to delete an existing linkage, right-click the linkage and select Delete, then click Yes to confirm.

5. If you want to create a new linkage, right-click the canvas and select New Linkage, select the source, then select the target.

NOTEYou cannot create a linkage from the target back to the source.

6. When finished, click OK.

Adding targets to Replication policiesOnce you have created a Replication policy, you can add new targets for replication. Before you add links to the policy, ensure you have reviewed the requirements for Replication policies. For more information, see “Replication policy requirements” on page 401.

NOTEIf you add, remove, or modify any targets of a Replication policy, StorageX resets the replication topology of the policy to its default. For more information about replication topology, see “Understanding replication and replication topology” on page 376.

To add targets to a Replication policy

1. In the StorageX Console, click the Disaster Recovery tab.

2. In the left tree pane, right-click the Replication policy you want to modify and then click Properties.

3. Click the Replication Paths tab.

4. Click the Add icon.

5. Type the path to the target you want to add to the policy or click the ellipsis (...) button to browse to and select the target.

6. Click OK.

7. If you want to reconfigure the replication topology, click Yes, then complete the following steps:

a. If you want to delete an existing linkage, right-click the linkage and select Delete, then click Yes to confirm.

b. If you want to create a new linkage, right-click the canvas and select New Linkage, select the source, then select the target.

NOTEYou cannot create a linkage from the target back to the source.

c. Click OK when finished.

408 StorageX Administrator’s Guide

Page 427: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Managing Replication policies 7

8. If you want to use the default replication topology, click No.

Removing targets from Replication policiesIf you no longer want to replicate to a particular target using a Replication policy, you can remove that target from the policy.

NOTEIf you add, remove, or modify any targets of a Replication policy, StorageX resets the replication topology of the policy to its default. For more information about replication topology, see “Understanding replication and replication topology” on page 376.

To remove a target from a Replication policy

1. In the StorageX Console, click the Disaster Recovery tab.

2. In the left tree pane, right-click the Replication policy you want to modify and then click Properties.

3. Click the Replication Paths tab.

4. Select the target you want to remove and then click the Remove icon.

5. Click OK.

6. If you want to reconfigure the replication topology, click Yes, then complete the following steps:

a. If you want to delete an existing linkage, right-click the linkage and select Delete, then click Yes to confirm.

b. If you want to create a new linkage, right-click the canvas and select New Linkage, select the source, then select the target.

NOTEYou cannot create a linkage from the target back to the source.

c. Click OK when finished.

7. If you want to use the default replication topology, click No.

Configuring email notification options for Replication policiesYou can configure a Replication policy to automatically notify one or more users each time the policy runs. You can set a policy to send email notifications when the policy is canceled, when the policy completes successfully, or when replication was incomplete, among other criteria.

StorageX sends Replication policy email notifications either using an existing notification profile or a new notification profile created specifically for the policy.

To configure Replication policy email notification options

1. In the StorageX Console, click the Disaster Recovery tab.

2. In the left tree pane, browse to and right-click a Replication policy, and click Properties.

3. In the left pane, click Email Notification Settings.

StorageX Administrator’s Guide 409

Page 428: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using batch files with Disaster Recovery or Replication policies7

4. If you want to use an existing notification profile, click the Select an existing notification profile or create a new profile list and select the profile you want to use, then click Email is enabled for the selected notification profile.

5. If you want to create a new notification profile for the policy, complete the following steps:

a. Click the Select an existing notification profile or create a new profile list.

b. Click New.

c. Specify the SMTP settings you want to use for the new profile. For more information about the SMTP settings, click the Help button on the dialog box.

d. Specify the message settings you want to use for the new profile. For more information about the message settings, click the Help button on the dialog box.

e. Click Send Test Message to verify the profile settings are correct.

f. If you want to use the new notification profile for all notifications, click Enable all usage of this notification.

g. Click OK.

6. Click one or more criteria you want StorageX to use when sending email notifications. For more information about the possible notification criteria, click the Help button on the dialog box.

7. Click OK.

Deleting Replication policiesIf you no longer need a Replication policy, you can delete the policy in the StorageX Console.

To delete a Replication policy

1. In the StorageX Console, click the Disaster Recovery tab.

2. In the left tree pane, right-click the Replication policy you want to delete and click Delete.

3. Click Yes to confirm.

Using batch files with Disaster Recovery or Replication policiesIf you know how to write scripts and create batch files, you can use batch files with Disaster Recovery and Replication policies.

The following topics provide more information about using batch files with Disaster Recovery and Replication policies:

• “Using batch files with Disaster Recovery policies” on page 411

• “Using batch files with Replication policies” on page 411

• “Disaster Recovery and Replication batch file requirements” on page 411

• “Creating batch files for Disaster Recovery policies” on page 413

• “Running batch files with Disaster Recovery and Replication policies” on page 417

410 StorageX Administrator’s Guide

Page 429: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using batch files with Disaster Recovery or Replication policies 7

Using batch files with Disaster Recovery policiesFor a Disaster Recovery policy, you can specify that you want to run batch files by specifying a batch file on the following tabs in the Properties window of the policy:

• Failover Scripting tab - Allows you to specify that you want to run a batch file before or after failover and failback

NOTEIf you configure a Disaster Recovery policy to run a batch file before or after failover, StorageX also runs the batch file before or after failback.

• Policy Options tab - Allows you to specify that you want to run a user decision script to determine the health of your monitored resources

• Replication Scripting tab - Allows you to specify that you want to run a batch file before or after replication.

For more information about batch file requirements for Disaster Recovery and Replication policies, see “Disaster Recovery and Replication batch file requirements” on page 411.

For more information about creating batch files for Disaster Recovery policies, see “Creating batch files for Disaster Recovery policies” on page 413. For more information about running batch files, see “Running batch files with Disaster Recovery and Replication policies” on page 417.

Using batch files with Replication policiesFor a Replication policy, you can specify that you want to run batch files by specifying a batch file on the following tabs in the Properties window of the policy:

• Replication Scripting tab - Allows you to specify that you want to run a batch file before or after replication.

For information about using batch files before or after replication, see “Running batch files with Phased Migration policies” on page 286.

For more information about batch file requirements for Disaster Recovery and Replication policies, see “Disaster Recovery and Replication batch file requirements” on page 411.

For more information about running batch files, see “Running batch files with Disaster Recovery and Replication policies” on page 417.

Disaster Recovery and Replication batch file requirementsBefore you specify a batch file for a Disaster Recovery or Replication policy, review the following requirements to ensure the batch file produces the desired results and the policy completes successfully.

• If the path to the batch file contains spaces, the path must be wrapped in quotation marks.

• If you browse to the batch file location, StorageX automatically enters the quotation marks.

• If you enter the path to the batch file manually, you must enter the quotation marks.

• StorageX does not validate the path to the batch file you specify. It is your responsibility to ensure that the path is accurate and accessible to the StorageX server that runs the batch file.

StorageX Administrator’s Guide 411

Page 430: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using batch files with Disaster Recovery or Replication policies7

• Batch files run with their working folder set to the folder containing the batch file when they are specified by a local path, such as c:\bats\myfile.bat. When the batch file is referenced by a UNC path, its working folder is the system32 folder of the StorageX server that runs the batch file.

• Any file StorageX runs must be a batch file. It is possible to have a top-level batch file run other tools, such as jscript files or other executables.

• The arguments StorageX passes to the batch file may be slightly different than expected. It can be very helpful to have your batch file log into a text file when the batch file runs, along with the arguments it receives.

For more information about arguments StorageX uses when running Disaster Recovery policy batch files, see the following topics:

“Pre-failover batch file for Disaster Recovery policy monitoring DFS links” on page 413

“Pre-failover batch file for Disaster Recovery policy monitoring NetApp resources” on page 414

“Post-failover batch file for Disaster Recovery policy monitoring DFS links” on page 414

“Post-failover batch file for Disaster Recovery policy monitoring NetApp resources” on page 415

“User decision script for Disaster Recovery policy monitoring DFS links” on page 416

“User decision script for Disaster Recovery policy monitoring NetApp resources” on page 416

• Multiple copies of a batch file might run simultaneously if tasks are running at the same time.

• StorageX uses the exit value of the batch file to assess whether the batch file succeeded or failed. Batch files must set the return value correctly to signal either success or failure.

• If your batch file is not producing the desired results, you can insert different exit codes throughout the batch file to determine where exactly the batch file is exiting. You can also insert logging statements showing progress through the script to trace execution.

• Batch files must not prompt for user input, since there is no console available to display a prompt at run time. Batch files that prompt for input may cause StorageX to stop responding because the policy executing the batch file will hang indefinitely. This is true for any prompt, whether in an error path or in a normal execution path in the batch file.

• The Alert Details and Event Details dialog boxes may truncate output from user-written batch files that return more than about 80 characters to Stdout. If you need to output more than 80 characters from a batch file, ensure the batch file is written to store the information in a disk file for subsequent reference.

• Test your scripts and batch files to verify that they are functioning as expected before you use them in policies. Specify small test directories for the source and destination and configure the scripts to write diagnostic output to a text file for review. After the scripts function correctly in the test configuration, you can configure them for use in actual policies, and you can reduce the amount of diagnostic information logged by the scripts to match the requirements of your environment.

For more information about creating batch files for use with Disaster Recovery policies, see “Creating batch files for Disaster Recovery policies” on page 413.

For more information about using batch files with Disaster Recovery and Replication policies, see “Running batch files with Disaster Recovery and Replication policies” on page 417.

412 StorageX Administrator’s Guide

Page 431: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using batch files with Disaster Recovery or Replication policies 7

Creating batch files for Disaster Recovery policiesThe following topics provide additional information you can use when creating batch files or user decision scripts to use with Disaster Recovery policies.

For information about using batch files before or after replication, either for Disaster Recovery, Replication, or Phased Migration policies, see “Running batch files with Phased Migration policies” on page 286.

NOTEYou should only use batch files or user decision scripts in StorageX if you know how to write scripts and work with batch files.

• “Pre-failover batch file for Disaster Recovery policy monitoring DFS links” on page 413

• “Pre-failover batch file for Disaster Recovery policy monitoring NetApp resources” on page 414

• “Post-failover batch file for Disaster Recovery policy monitoring DFS links” on page 414

• “Post-failover batch file for Disaster Recovery policy monitoring NetApp resources” on page 415

• “User decision script for Disaster Recovery policy monitoring DFS links” on page 416

• “User decision script for Disaster Recovery policy monitoring NetApp resources” on page 416

Pre-failover batch file for Disaster Recovery policy monitoring DFS links

When you create a Disaster Recovery policy to monitor one or more DFS links, you can configure the policy to run a batch file before failover or failback. To specify that you want to use a batch file for the policy, click the Failover Scripting tab and then select the Run batch file before failover or failback check box. The policy runs the batch file once for each link failed over or failed back.

NOTEIf you configure a Disaster Recovery policy to run a batch file before or after failover, StorageX also runs the batch file before or after failback.

Use the following arguments and exit codes to create a batch file to use for this option.

Arguments

1. Policy name

2. (not used)

3. UNC path of the link being failed over

4. Invocation type (/failover or /failback)

5. First user argument

StorageX Administrator’s Guide 413

Page 432: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using batch files with Disaster Recovery or Replication policies7

Exit codes

Pre-failover batch file for Disaster Recovery policy monitoring NetApp resources

When you create a Disaster Recovery policy to monitor one or more NetApp resources, you can configure the policy to run a batch file before failover or failback. To specify that you want to use a batch file for the policy, click the Failover Scripting tab and then select the Run batch file before failover or failback check box. The policy runs the batch file once for each NetApp resource failed over or failed back.

NOTEIf you configure a Disaster Recovery policy to run a batch file before or after failover, StorageX also runs the batch file before or after failback.

Use the following arguments and exit codes to create a batch file to use for this option.

Arguments

1. Policy name

2. NetApp Filer/cluster name

3. NetApp Vserver or SVM name (if monitoring a NetApp cluster)

4. NetApp volume name

5. NetApp qtree name (if monitoring a NetApp qtree)

6. Invocation type (/failover or /failback)

7. First user argument

Exit codes

Post-failover batch file for Disaster Recovery policy monitoring DFS links

When you create a Disaster Recovery policy to monitor one or more DFS links, you can configure the policy to run a batch file after failover or failback. To specify that you want to use a batch file for the policy, click the Failover Scripting tab and then select the Run batch file after failover or failback check box. The policy runs the batch file once for each link failed over or failed back.

NOTEIf you configure a Disaster Recovery policy to run a batch file before or after failover, StorageX also runs the batch file before or after failback.

Use the following arguments and exit codes to create a batch file to use for this option.

0 Success

All others Error

0 Success

All others Error

414 StorageX Administrator’s Guide

Page 433: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using batch files with Disaster Recovery or Replication policies 7

Arguments

1. Policy name

2. New Online targets (in comma-separated list)

3. UNC path of the link being failed over or failed back

4. Invocation type (/failover or /failback)

5. First user argument

Exit codes

Post-failover batch file for Disaster Recovery policy monitoring NetApp resources

When you create a Disaster Recovery policy to monitor one or more NetApp resources, you can configure the policy to run a batch file after failover or failback. To specify that you want to use a batch file for the policy, click the Failover Scripting tab and then select the Run batch file after failover or failback check box. The policy runs the batch file once for each NetApp resource failed over or failed back.

NOTEIf you configure a Disaster Recovery policy to run a batch file before or after failover, StorageX also runs the batch file before or after failback.

Use the following arguments and exit codes to create a batch file to use for this option.

Arguments

1. Policy name

2. NetApp Filer/cluster name

3. NetApp Vserver or SVM name (if monitoring a NetApp cluster)

4. NetApp volume name

5. NetApp qtree name (if monitoring a NetApp qtree)

6. Invocation type (/failover or /failback)

7. First user argument

0 Success

All others Error

StorageX Administrator’s Guide 415

Page 434: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using batch files with Disaster Recovery or Replication policies7

Exit codes

User decision script for Disaster Recovery policy monitoring DFS links

When you create a Disaster Recovery policy to monitor one or more DFS links, you can configure the policy to run a user decision script to check the health of your monitored links. To specify that you want to use a user decision script for the policy, click the Policy Options tab and then select the Run user decision script to determine the health of the resources check box. The policy runs the batch file once for each monitored link.

NOTEIf you run this type of user decision script for a Disaster Recovery policy that monitors both CIFS-based storage resources and links or that uses a master link, the policy only runs the script one time, for the configured master link.

Use the following arguments and exit codes to create a user decision script to use for this option.

Arguments

1. Policy name

2. UNC path of the monitored link

3. Online targets (in comma-separated list)

4. Offline targets (in comma-separated list)

5. First user argument

Exit codes

User decision script for Disaster Recovery policy monitoring NetApp resources

When you create a Disaster Recovery policy to monitor one or more NetApp resources, you can configure the policy to run a user decision script to check the health of your monitored resources. To specify that you want to use a user decision script for the policy, click the Policy Options tab and then select the Run user decision script to determine the health of the resources check box. The policy runs the batch file once for each monitored NetApp resource.

Use the following arguments and exit codes to create a user decision script to use for this option.

Arguments

1. Policy name

2. NetApp Filer/cluster name

3. NetApp Vserver or SVM name (if monitoring a NetApp cluster)

4. NetApp volume name

5. NetApp qtree name (if monitoring a NetApp qtree)

0 Success

All others Error

0 Success

All others Error

416 StorageX Administrator’s Guide

Page 435: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using batch files with Disaster Recovery or Replication policies 7

6. First user argument

Exit codes

Running batch files with Disaster Recovery and Replication policiesIf you know how to write scripts and create batch files, you can specify that you want to run batch files during Disaster Recovery or Replication policy run.

For more information about using batch files with Disaster Recovery policies, see “Using batch files with Disaster Recovery policies” on page 411. For more information about using batch files with Replication policies, see “Using batch files with Replication policies” on page 411.

For more information about creating batch files for use with Disaster Recovery policies, see “Creating batch files for Disaster Recovery policies” on page 413.

To run batch files with a Disaster Recovery or Replication policy

1. In the left tree pane, browse to and right-click the Disaster Recovery or Replication policy where you want to run a batch file, and then click Properties.

2. If you want to run a batch file before or after failover and failback, or on manual failover and failback, for a Disaster Recovery policy, complete the following steps:

a. Click the Failover Scripting tab.

b. If you want to run a batch file before a link is failed over, select Run batch file before failover or failback. For example, if ten links must be failed over, the batch file runs ten times, once before each link fails over. You can specify the batch file either as the UNC path to a file accessible on your network or as a local path to a file residing on the server computer where monitoring is taking place. Type the path of a batch file or click the ellipsis (...) button to browse to and select a batch file on your network.

c. If you selected Run batch file before failover or failback and you want to run the specified batch file every time you perform a manual failover or failback, select Also run batch on manual failover or failback.

d. If you want to run a batch file after a link is failed over, select Run batch file after failover or failback. For example, if ten links are failed over, the batch file runs ten times, once after each link fails over. You can specify the batch file either as the UNC path to a file accessible on your network or as a local path to a file residing on the server computer where monitoring is taking place. Type the path of a batch file or click the ellipsis (...) button to browse to and select a batch file on your network.

e. If you selected Run batch file after failover or failback and you want to run the specified batch file every time you perform a manual failover or failback, select Also run batch on manual failover or failback.

f. Click Apply.

3. If you want to run a batch file before or after replication, complete the following steps:

0 Success

All others Error

StorageX Administrator’s Guide 417

Page 436: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using batch files with Disaster Recovery or Replication policies7

a. Click the Replication Scripting tab.

b. If you want to run a batch file before a replication operation, select the Run batch file before replication check box.

c. If you want to run a batch file after a replication operation, select the Run batch file after replication check box.

NOTEIf you run a Disaster Recovery or Replication policy with batch files configured to run before or after replication, but the replication job cannot run, StorageX still runs any replication scripting batch files configured. For example, if you run a policy with a post-replication batch file, and StorageX cannot find a valid universal data engine, StorageX runs the post-replication batch file even though the replication did not complete.

d. Type the UNC path or a local path to the batch file or click the ellipsis (...) button to browse to and select the batch file on your network.

If you specify a UNC path, the StorageX server service account must have Read permissions to the folder where the batch file is stored as well as Read permissions to the batch file itself.

If you specify a local path, the StorageX server service account must have Read permissions to the folder where the batch file is stored, the batch file must be stored in a local path on the StorageX server computer, and the StorageX server service account must have Read permissions to the batch file itself.

e. Click Apply.

4. If you want to run a user decision script to check the health of your resources when the policy runs, complete the following steps:

a. Click the Policy Options tab.

b. Select the Run user decision script to determine the health of the resource check box.

c. Type the UNC path or a local path to the batch file or click the ellipsis (...) button to browse to and select the batch file on your network.

If you specify a UNC path, the StorageX server service account must have Read permissions to the folder where the batch file is stored as well as Read permissions to the batch file itself.

If you specify a local path, the StorageX server service account must have Read permissions to the folder where the batch file is stored, the batch file must be stored in a local path on the StorageX server computer, and the StorageX server service account must have Read permissions to the batch file itself.

d. Click Apply.

5. Click OK.

418 StorageX Administrator’s Guide

Page 437: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX Administrator’s Guide

Chapter

8

Working with Reports

This section explains how to create and use StorageX reports. StorageX reports can help you better understand your file storage resource environment and how you are using StorageX policies and Migration Projects to migrate and manage your file data.

In this chapter•Understanding reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419

•Creating reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

•Viewing reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

•Customizing displayed reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

•Searching for items in reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430

•Exporting reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431

•Comparing different versions of a Resource Baseline report . . . . . . . . . . 431

Understanding reportsStorageX allows you to create the following report types, and also provides prepackaged example reports for each report type that you can customize:

• Universal Data Engine reports. For more information, see “Understanding Universal Data Engine reports” on page 420.

• Disaster Recovery reports. For more information, see “Understanding Disaster Recovery reports” on page 420.

• Migration Project reports. For more information, see “Understanding Migration Project Reports” on page 420.

• Namespace Policy reports. For more information, see “Understanding Namespace Policy reports” on page 421.

• Phased Migration Policy reports. For more information, see “Understanding Phased Migration Policy reports” on page 421.

• Storage resource reports. For more information, see “Understanding Storage Resource reports” on page 422.

419

Page 438: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding reports8

Understanding Universal Data Engine reportsStorageX universal data engine reports provide information about universal data engine utilization over the past 30 days.

StorageX provides the following report types relating to universal data engines:

Universal Data Engine Utilization for the Last 30 Days reportDisplays information about universal data engine utilization over the past 30 days and helps you discover and understand which universal data engines are actively running policies.

Universal Data Engine Utilization Daily Trend for the Last 30 Days reportDisplays information about universal data engine utilization trends day by day over the past 30 days.

For a detailed explanation of each column included in the report, click the Help button in the upper-right corner of the report when viewing the report.

Understanding Disaster Recovery reportsDisaster Recovery reports provide information about what occurred during the last run of your Replication policies or in all runs of your Replication policies. Disaster Recovery reports include information about policies created in the Disaster Recovery view.

StorageX provides the following Disaster Recovery reports:

Replication Policy All Runs reportDisplays information about every run of every Replication policy run in StorageX, regardless of which policy the run is associated with. For example, if you have five universal data engines in your StorageX environment, you can use this report to view a list of all the policy runs associated with each specific universal data engine by sorting on the Data Engine column. Use this report to see things like how long each policy run is taking, how much file data has been replicated during each policy run, and policy run trends over time.

Replication Policy Last Run reportDisplays information about the last run of every Replication policy in StorageX. For example, you can use this report to quickly see which policies have not yet run, which policies have completed, and which policies are scheduled. You can also use this report to get a general idea of how close policy runs are to completion. You can view additional details about each policy run associated with a policy by clicking the plus (+) sign in front of the policy name.

For more information about viewing Disaster Recovery reports, see “Viewing reports” on page 426. For a detailed explanation of each column included in a report, click the Help button in the upper-right corner of the report when viewing the report.

Understanding Migration Project ReportsStorageX Migration Project reports provide information about Phased Migration policies associated with Migration Projects and Migration Project designs.

StorageX provides the following Migration Project reports:

420 StorageX Administrator’s Guide

Page 439: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding reports 8

Migration Project Policies reportDisplays information about all of the Phased Migration policies associated with each Migration Project in StorageX. For example, you can use this report to see how many files were copied from the source to the destination during the last policy run, the number of files StorageX was unable to copy during the last policy run, the file copy rate during the last policy run, and more.

Migration Project Summary reportDisplays summary information for Migration Projects and Migration Project designs. For example, you can use this report to see the number of Migration Project designs created for each Migration Project, as well as the state of each design (In Design, Validated, or Executed). You can also see the number of sources and destinations included in each design, the number of policies generated for a design if the design has been executed, and the number of policies in each design that are configured to run on a schedule versus the number of policies configured to be run manually.

For more information about viewing Migration Project reports, see “Viewing reports” on page 426. For a detailed explanation of each column included in a report, click the Help button in the upper-right corner of the report when viewing the report.

Understanding Namespace Policy reportsNamespace Policy reports provide information about Namespace Availability and Namespace Backup policies run in your environment, as well as information about synchronized and backed-up namespaces.

StorageX provides the following Namespace Policy reports:

Availability Policy Last Run reportDisplays information about the last run of every Namespace Availability policy in StorageX. For example, you can use this report to quickly see which policies have completed, which target namespaces were synchronized, and which target namespaces could not be synchronized. You can also use this report to get a general idea of how close policy runs and projects are to completion.

Backup Policy Last Run reportDisplays information about the last run of every Namespace Backup policy in StorageX. For example, you can use this report to quickly see which policies have completed, which namespaces were backed up, and which namespaces could not be backed up. You can also use this report to get a general idea of how close policy runs and projects are to completion.

For more information about viewing Namespace Policy reports, see “Viewing reports” on page 426. For a detailed explanation of each column included in a report, click the Help button in the upper-right corner of the report when viewing the report.

Understanding Phased Migration Policy reportsPhased Migration Policy reports provide information about what occurred during the last run of your Phased Migration policies or in all runs of your Phased Migration policies. Phased Migration Policy reports include information about policies created in the Data Movement view, as well as Phased Migration project policies created when you execute Migration Project designs in the Migration Projects view.

StorageX Administrator’s Guide 421

Page 440: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding reports8

StorageX provides the following Phased Migration Policy reports:

Phased Migration Policy All Runs reportDisplays information about every run of every Phased Migration policy run in StorageX, regardless of which policy the run is associated with. For example, if you have five universal data engines in your StorageX environment, you can use this report to view a list of all the policy runs associated with each specific universal data engine by sorting on the Data Engine column. Use this report to see things like how long each policy run is taking, how much file data has been migrated during each policy run, and policy run trends over time.

Phased Migration Policy Last Run reportDisplays information about the last run of every Phased Migration policy in StorageX. For example, you can use this report to quickly see which policies have not yet run, which policies have completed, which policies are scheduled, and which policies are waiting for user input. You can also use this report to get a general idea of how close policy runs and projects are to completion. You can view additional details about each policy run associated with a policy by clicking the plus (+) sign in front of the policy name.

For more information about viewing Phased Migration Policy reports, see “Viewing reports” on page 426. For a detailed explanation of each column included in a report, click the Help button in the upper-right corner of the report when viewing the report.

Understanding Storage Resource reportsStorage Resource reports provide information about CIFS shared folders and NFS exports on file storage resources, as well as summary information about file storage resources. You can specify which storage resources you want to include in the reports. For example, you can specify that you want to include all of the files storage resources managed by StorageX in the report, or you can specify that you want to include only a certain subset of file storage resources managed by StorageX in the report.

NOTETo use the Storage Resource reports, you must click Select Resources and then specify which resources you want to include in the report. If you do not select at least one resource to include, the report will remain blank.

StorageX provides the following Storage Resource reports:

CIFS Resource Connections reportDisplays information about current connections to a selected set of CIFS storage resources, including the user names used for each connection, the number of open files, the duration of the connection, and more.

Exports reportDisplays information about NFS exports on file storage resources, including export names, the name of the volume or file system that hosts the export, and export permissions.

Namespace Health Check reportRuns health checks against specified DFS namespaces and displays information about the current state of those namespaces, including whether all link targets are enabled, whether anonymous access is restricted, whether the DFS service is running, and more.

422 StorageX Administrator’s Guide

Page 441: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating reports 8

Namespace Link Summary reportDisplays summary information about namespace links managed by StorageX, including link names and paths, namespaces, enabled or disabled targets, namespace types, and more.

Namespace Target Summary reportDisplays summary information about namespace targets managed by StorageX, including namespaces, namespace paths, server paths, referral status, priority, and more.

NFS Resource Connections reportDisplays information about current connections to a selected set of NFS storage resources, including the name of the each storage resource, the path on each resource to the NFS exports, and more.

Resource Baseline reportDisplays detailed baseline information about selected file storage resources managed by StorageX, including DNS configuration information, management accounts, volume and filesystem statistics, quotas, and more.

For information about comparing two versions of a particular Resource Baseline report, see “Comparing different versions of a Resource Baseline report” on page 431.

Shares reportDisplays information about CIFS shared folders on file storage resources, including share names, share properties, the type of file system that hosts the shared folder, and the name of the volume or file system where the CIFS shared folder resides.

Storage Resource Summary reportDisplays summary information about file storage resources managed by StorageX, including file storage resource names, IP addresses, the total number of shares and exports on resources, platform information, status information, and more.

For more information about viewing Storage Resource reports, see “Viewing reports” on page 426. For a detailed explanation of each column included in a report, click the Help button in the upper-right corner of the report when viewing the report.

Creating reportsYou can create custom StorageX reports on the Reporting tab, using the Report Creation Wizard to configure the particular type of report you want and the resources you want to include in the report.

For more information about the different types of reports StorageX provides, see “Understanding reports” on page 419.

To create a new report

1. In the StorageX Console, click the Reporting tab.

2. In the left tree pane right-click Reports or a specific subfolder where you want to create a report and select New Report to open the Report Creation Wizard.

3. Review the welcome message, and then click Next.

4. Specify a name and description for the new report, and then click Next.

StorageX Administrator’s Guide 423

Page 442: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating reports8

5. Select the type of report you want to create, and then click Next.

6. If the report type includes one or more file storage resources, complete the following steps:

a. In the Select Devices window, select the file storage resources you want to include.

b. If you want to include a file storage resource that is not already listed, click Add Device and follow the steps in the Add File Storage Resource Wizard to add a new storage resource.

c. Click Next.

7. If the report type includes one or more namespaces, complete the following steps:

a. In the Select Namespaces window, select the namespaces you want to include.

b. If you want to include a namespace that is not already listed, click Add Namespace, type the DFS namespace path of the DFS namespace you want to add or click Browse to browse to and select the DFS namespace you want to add, and then click OK. StorageX adds the namespace to the Select Namespace window and selects the new namespace by default.

c. Click Next.

8. If the report type includes one or more health checks, complete the following steps:

a. In the Health Checks window, clear any health checks you do not want to run on the resources included in the report. All health checks are selected by default.

b. If you want StorageX to display a Warning when a health check fails instead of the default Error, click the error level for the health check and select Warning.

c. Click Next.

9. If the report type is Resource Baseline report, complete the following steps:

a. In the Resource Baseline Report Information window, select any storage resource baseline information you want to include in the report for the specified resources. All data points are cleared by default.

b. If you want to collect information on all resource baseline data points, click Select All.

c. Click Next.

10. If the report type is a Replication report, complete the following steps:

a. In the Specify Policies window, select any policy you want to include in the report. All policies are cleared by default.

b. Click Next.

11. If you want StorageX to automatically run the new report on a schedule, complete the following steps:

a. In the Specify Report Schedule dialog box, select Use schedule.

NOTEThis option is selected by default.

b. Select an existing schedule to use or click New to define a new schedule.

c. In the Schedule Task field, specify whether you want to run the report only once, or on a per minute, hourly, daily, or weekly basis.

d. Specify a start time for the schedule you want to use.

424 StorageX Administrator’s Guide

Page 443: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Creating reports 8

e. Specify how frequently you want the report to run, depending on the Schedule Task setting.

f. If you want to configure an end date for the report, click Advanced, specify an end date, and then click OK.

g. If you want to configure a one-time, daily, or weekly scheduled report to repeat, click Advanced, specify how frequently you want the report to repeat, and then click OK.

h. Click Next.

12. If you want to configure StorageX to save a completed report to a specific location each time the report runs, complete the following steps:

a. In the Output File Name field, type the name you want to use when saving the completed report.

NOTEYou can click Macros and use the provided macro options to automatically insert the report name, the report folder, or a date/time stamp in the Output Folder or Output File Name field each time StorageX saves the completed report. For example, you could use the macros to automatically include a date/time stamp each time you save a scheduled report and avoid overwriting an existing saved report.

There is a 260 character limit for the combined fully qualified file name and directory name of a report. Ensure that when you configure your macro options the information automatically inserted does not cause the report name to exceed 260 characters.

b. In the Output File Format field, select the file format in which you want to save the completed report. You can select either XLSX or CSV format.

c. Select the Save report to folder check box.

NOTEIf you configure StorageX to automatically run a report on a schedule, you must also configure StorageX to email the completed report or save the completed report to a specified location.

d. In the Output Folder field, type the path to the folder where you want to save the completed report or click Browse to browse to and select the folder where you want to save the report.

13. If you want to configure StorageX to email a completed report to one or more recipients each time the report runs, complete the following steps:

a. In the Output File Name field, type the name you want to use when sending the completed report.

NOTEYou can click Macros and use the provided macro options to automatically insert the report name, the report folder, or a date/time stamp in the Output Folder or Output File Name field each time StorageX sends the completed report. For example, you could use the macros to automatically include a date/time stamp each time you send a scheduled report.

StorageX Administrator’s Guide 425

Page 444: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Viewing reports8

There is a 260 character limit for the combined fully qualified file name and directory name of a report. Ensure that when you configure your macro options the information automatically inserted does not cause the report name to exceed 260 characters.

b. Select the Send email when report is complete check box.

c. If you want to use an existing email notification profile, select the profile from the Select an existing notification profile or create a new profile list.

d. If you want to create a new email notification profile, click New, then specify the profile name, SMTP settings, and message settings you want to use. Click Send Test Message to verify StorageX can send the message correctly, then click OK. For more information about the SMTP settings available for a notification profile, click the Help button on the dialog box.

e. Select the Email is enabled for the selected notification profile check box.

NOTEIf you configure StorageX to automatically run a report on a schedule, you must also configure StorageX to email the completed report or save the completed report to a specified location.

f. In the Subject field, specify the text you want to include in the “Subject” field of the email message.

NOTEYou can click Macros and use the provided macro options to automatically insert the report name, the report folder, or a date/time stamp in the “Subject” field each time StorageX emails the report.

g. If you want to attach the completed report to the email message, select the Attach Report to Email check box.

h. Click Next.

14. Review the summary information, and then click Finish.

15. Click the new report in the tree pane and make any customizations to the report. For more information about customizing reports, see “Customizing displayed reports” on page 427.

Viewing reportsYou can view reports created in StorageX on the Reporting tab.

For more information about creating reports, see “Creating reports” on page 423.

To view a report

1. In the StorageX Console, click the Reporting tab.

2. In the left tree pane, browse to and then select the report you want to view.

426 StorageX Administrator’s Guide

Page 445: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Customizing displayed reports 8

3. In the center pane, review the data displayed, and customize the view as needed to meet your reporting requirements. For example, by right-clicking in a header, you can sort items in ascending or descending order, add or remove columns, add filters, and more. For more information, see “Customizing displayed reports” on page 427.

NOTEThe StorageX Console automatically saves any changes you make to a displayed report and displays that report in the same way the next time you select it. If you want to revert your customizations to the displayed report, click the Reset grid configuration icon.

4. If you want to view the last saved report, click the folder that contains the report in the left pane, then click on the link in the Last Saved Scheduled Report column in the right pane.

5. If you want to export the report, click the Save icon. For more information about exporting reports, see “Exporting reports” on page 431.

Customizing displayed reportsYou can customize how StorageX displays reports. For more information about customizing displayed reports, see the following topics:

• “Adding, removing, reordering, and resizing report columns” on page 427

• “Sorting data in reports” on page 428

• “Grouping and ungrouping data in reports” on page 428

• “Filtering records in reports” on page 429

Adding, removing, reordering, and resizing report columnsYou can customize reports by adding, removing, reordering, and resizing report columns.

For more information about reports, see “Understanding reports” on page 419. For more information about viewing reports, see “Viewing reports” on page 426.

To add, remove, reorder, or resize report columns

1. In the StorageX Console, click the Reporting tab.

2. In the left tree pane, browse to and then select a report.

3. If you want to add a hidden column to the report, complete the following steps:

a. Right-click a column header, and then click Column Chooser.

b. Double-click a column displayed in the report Customization dialog box to add the column to the report.

4. If you want to remove, or hide, a column from a report, right-click the column header you want to remove, and then click Remove This Column.

5. If you want to reorder columns in a report, drag and drop the column header to a new position in the report.

6. If you want to resize a column, drag the right edge of the column to the right to make the column larger, or to the left to make the column smaller.

StorageX Administrator’s Guide 427

Page 446: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Customizing displayed reports8

7. If you want to change a specific column width so that it displays its contents compactly in their entirety, compete one of the following actions:

• Double-click the right edge of the column header.

• Right-click the column header, and then click Best Fit.

8. If you want to change the width of all columns so that they display their contents in the best possible way, right-click the header of any column and then click Best Fit (all columns).

Sorting data in reportsYou can sort data in report columns. This topic explains how to sort data in columns.

For more information about reports, see “Understanding reports” on page 419. For more information about viewing reports, see “Viewing reports” on page 426.

To sort data in reports:

1. In the StorageX Console, click the Reporting tab.

2. In the left tree pane, browse to and then select a report.

3. If you want to sort records by column values and replace existing sort conditions that are applied to the current column or other columns, click the target column’s header until an Up or Down arrow displays within the header. The Up arrow indicates ascending sort order. The Down arrow indicates descending sort order.

4. If you want to sort records by column values while preserving existing sort conditions, perform one of the following actions:

• Click a column header while holding the SHIFT key down, until an Up or Down arrow displays within the header.

• Right-click a column header and then click Sort Ascending or Sort Descending.

5. If you want to remove sorting by a column, right-click the column header and then click Clear Sorting.

Grouping and ungrouping data in reportsYou can group data in report. This topic explains how to group data in reports.

For more information about reports, see “Understanding reports” on page 419. For more information about viewing reports, see “Viewing reports” on page 426.

To group data in reports:

1. In the StorageX Console, click the Reporting tab.

2. In the left tree pane, browse to and then select a report.

3. If you want to group data by a specific column, perform one of the following actions:

• Drag a column header to the group panel. The group panel is the panel immediately above the column headers.

• Right-click a column header and then click Group By This Column.

4. If you want to ungroup data grouped by a grouping column, perform one of the following actions:

428 StorageX Administrator’s Guide

Page 447: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Customizing displayed reports 8

• Drag a column header from the group panel back to the column header area. The group panel is the panel immediately above the column headers.

• Right-click a grouping column’s header in the group panel and then click UnGroup.

5. If you want to remove grouping by all columns, right-click the group panel, and then click Clear Grouping.

6. If you want to change group order, move the column header in the group panel to another position in the grouping panel.

7. If you want to hide the group panel, right-click the group panel and then click Hide Group By Box.

8. If the group panel is currently hidden and you want to display it, right-click a column header and then click Show Group By Box.

Filtering records in reportsFilter conditions specify what data to select from a data source and display in a report grid.

A typical simple filter condition consists of three parts: the column/field name, operator and value(s).

You can use simple filters and filter reports to view only records that contain a specific value in a specific column. You can also build more complex filters that use multiple conditions.

For more information about reports, see “Understanding reports” on page 419. For more information about viewing reports, see “Viewing reports” on page 426.

To filter for records that contain a specific value is a specific column:

1. In the StorageX Console, click the Reporting tab.

2. In the left tree pane, browse to and then select a report.

3. If you want to use filter drop-down lists to quickly create simple filters, complete the following steps:

a. Click the filter icon in the right corner of the column.

b. If a filter is already applied to the column, the filter drop-down list displays only the values that match the current filter criteria. If you want to list all values, and not just the values that match the current filter criteria, press the SHIFT key while opening the filter drop-down.

c. Select the filter value you want to use from the drop-down list.

The filter drop-down list closes immediately and displays the records that contain the specified value in the specified column.

d. If the filter drop-down list provides check boxes to the left of the filter values, you can select multiple values at the same time. After selecting the filter values you want to use, click OK to close the drop-down list and apply the filter.

4. If you want to build a more complex filter that uses multiple conditions, complete the following steps:

StorageX Administrator’s Guide 429

Page 448: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Searching for items in reports8

a. Right-click a column header, and then click Filter Editor.

b. To filter against a column, click the link that displays the column name. This displays a list of available columns. Select the column you want to filter against.

c. Select an operator by clicking the condition’s operator link to display the support comparison operators and then select an appropriate operator. The comparison operator lists displays only those operators that are supported by the current column’s data type.

d. Click the value box and enter an appropriate value.

e. Click OK or Apply to filter data using the created filter condition.

f. If you want to add additional filter conditions, click the green button next to And to create and specify additional filter conditions.

5. If you want to edit an existing filter, click the Edit Filter button in the lower-right corner of the report grid.

6. If you want to remove a filter, clear the check box in front of the filter in the lower-left corner of the report grid.

7. If you want to delete a filter, click the Delete icon in front of the filter in the lower-left corner of the report grid.

8. If you want to filter data on the fly by typing text within a row and having a filter condition automatically created based on the filter entered, type in the automatic filtering row that displays at the top of the report grid, just under the column headers.

StorageX does not display the automatic filtering row by default, but you can display the automatic filtering row by completing the following steps:

a. Right-click a column header.

b. Click Show Auto Filter Row.

c. Type text in the row to begin creating a filter condition.

9. If the automatic filtering row displays at the top or the report grid but you want to hide it, right-click a column header and then click Hide Auto Filter Row.

Searching for items in reportsYou can search for data in reports. This section explains how to search for data in reports.

For more information about reports, see “Understanding reports” on page 419. For more information about viewing reports, see “Viewing reports” on page 426.

To search for data in reports:

1. In the StorageX Console, click the Reporting tab.

2. In the left tree pane, browse to and then select a report.

3. Click the Search icon.

4. Type the text you want to search on in the text field, and then click Find.

5. If the Find panel displays but you want to hide it, right-click a column header, and then click Hide Find Panel.

430 StorageX Administrator’s Guide

Page 449: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Exporting reports 8

Exporting reportsYou can export StorageX reports to files in .xlsx, .xls, or .csv format.

For more information about StorageX reports, see “Understanding reports” on page 419 and “Viewing reports” on page 426.

NOTES:

• You can only export Namespace Health Check reports in .csv format.

• You can only export Resource Baseline reports in .xlsx format.

To export a report

1. In the StorageX Console, click the Reporting tab.

2. In the left tree pane, browse to and then select the report you want to export.

3. In the center pane, review the data displayed and customize the view as needed to meet your reporting requirements. For example, by right-clicking in a header, you can sort items in ascending or descending order, add or remove columns, add filters, and more. For more information, see “Customizing displayed reports” on page 427.

4. Click the Save icon.

5. Browse to the location where you want to export the report.

6. Type a file name for the report, specify the file format for the report (.xlsx, .xls, or .csv), and then click Save.

Comparing different versions of a Resource Baseline reportAfter you create a Resource Baseline report and run the report at least two times, you can compare one version of the report, the baseline, to a different version of the report.

This allows you to see how your environment has changed over time. For example, you can run a Resource Baseline report one week with the DNS Configuration and CIFS Share Properties information types selected, re-run the report the next week, and then compare the two versions of the report to see if DNS settings have been modified or there have been changes to any CIFS shares on the selected resources over the course of the week.

For more information about Resource Baseline reports, see “Understanding Storage Resource reports” on page 422. For more information about creating reports, see “Creating reports” on page 423. For more information about viewing reports, see “Viewing reports” on page 426.

To compare two versions of a Resource Baseline report

1. In the StorageX Console, click the Reporting tab.

2. In the left tree pane, browse to and then select the Resource Baseline report you want to compare.

3. When the report finishes loading, click the Compare report against previous version icon.

4. Select the report version you want to use as the baseline and click Set as Baseline.

StorageX Administrator’s Guide 431

Page 450: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Comparing different versions of a Resource Baseline report8

NOTEThe baseline report version of a given Resource Baseline Report is displayed in blue, and the value displayed in the Is Baseline? column is Yes.

5. Select the two versions of the report you want to compare and click Compare.

NOTEYou can compare any two versions of the same report, even if neither version is the baseline.

In the Report Comparison Results dialog box, review the displayed information. If data is different between the compared versions of the report, the dialog box displays the information type area that includes the data.

6. When finished reviewing the data, click Close.

432 StorageX Administrator’s Guide

Page 451: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX Administrator’s Guide

Appendix

A

Configuring StorageX to Use SSH Shell Credentials

StorageX uses the SSH protocol and SSH shell credentials to perform the following tasks:

• On VNX OE for File file storage resources, when migrating file data between VNX OE for File sources and destinations using Migration Projects in the Migration Projects view.

• On Linux file storage resources, when creating and cloning NFS exports in the Storage Resources view, and when cloning NFS exports as needed when creating Phased Migration policies in the Data Movement view.

• When updating automount map files stored on NFS clients as needed when running Phased Migration policies in the Data Movement or Migration Projects views.

This appendix explains how to configure SSH shell credentials for StorageX to use in these scenarios. You can either use a user name and password for SSH authentication or generate and use an SSH public/private key pair.

For information about specifying SSH credentials, see “Configuring default SSH shell credentials” on page 79 and “Configuring SSH shell credentials for specific file storage resources” on page 107.

NOTEYou do not need to configure SSH shell credentials for StorageX to use if you only want to view NFS exports on file storage resources or migrate file data stored in NFS exports on source to destination file storage resources. You only need to configure SSH shell credentials for StorageX to use if you want to migrate file data on VNX OE for File file storage resources using Migration Projects, if you want to create or clone NFS exports on Linux file storage resources, or if you want StorageX update automount map files stored on NFS clients when running Phased Migration policies.

In this appendix•Understanding SSH requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434

•Checklist: Configuring SSH shell credentials for StorageX . . . . . . . . . . . . . 435

•Generating an SSH public/private key pair . . . . . . . . . . . . . . . . . . . . . . . . . 435

•Copying public keys to Linux and VNX OE for File file storage resources and NFS clients 437

•Using SSH shell credentials with StorageX . . . . . . . . . . . . . . . . . . . . . . . . . 437

•Converting PuTTY-generated SSH private keys to OpenSSH-format private keys 438

433

Page 452: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding SSH requirementsA

Understanding SSH requirementsBefore you configure StorageX to use the SSH protocol and SSH shell credentials when migrating file data between VNX OE for File sources and destinations using Migration Projects, when creating and cloning NFS exports on Linux file storage resources, or when updating automount map files on NFS clients when running Phased Migration policies, ensure that the Linux file storage resources and NFS clients that StorageX manages meet the following requirements:

• VNX OE for File file storage resources, Linux file storage resources, and NFS clients that StorageX communicates with must be running an SSH server that conforms to the standards of the SSH protocol. SSH V2 or later must be enabled on the file storage resource. There are many SSH server versions that you can choose to use. Ensure you choose a version that conforms to SSH protocol standards and supports SSH V2 or later.

• VNX OE for File file storage resources, Linux file storage resources, and NFS clients that StorageX communicates with using SSH must be configured using an SSH public/private key file. You can use an existing SSH public/private key pair, or you can generate a new SSH public/private key pair using an SSH tool. For more information about generating an SSH public/private key pair, see “Generating an SSH public/private key pair” on page 435.

• If you want to use StorageX to manage VNX OE for File file storage resources, all managed VNX resources must use the built-in nasadmin account.

• If you want to use StorageX to manage Linux file storage resources, StorageX must be able to log in as root on the file storage resource in order to modify exports and AllowRootLogin for sshd must be enabled on the Linux file storage resource.

If you have disabled AllowRootLogin for sshd, StorageX will not be able to perform required commands. In order to use StorageX, allow StorageX to log in as root.

If security policies prevent you from allowing StorageX to log in as root, you can use one of the following options as a workaround:

• Turn off the password prompt for sudo commands via SSH. If you use this approach, ensure you set up an account that will not prompt for a sudo password when sudo is invoked.

• Allow StorageX to log in as root, but restrict StorageX access to the following files and commands:

TABLE 1 Commands and files use by StorageX on Linux file storage resources

Commands Files

echomkdirexportfsgrepdfcutmvcatypcatmake (the make command was deprecated in StorageX 7.0)

/etc/exports/dev/null/tmp/nvIntermediateFile

If you want to modify automounts, the path and name of the automount file. This path and name is specific to your environment.

434 StorageX Administrator’s Guide

Page 453: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Checklist: Configuring SSH shell credentials for StorageX A

Checklist: Configuring SSH shell credentials for StorageXThis topic provides a checklist you can use to help you configure SSH shell credentials for StorageX to use when performing the following tasks:

• On VNX OE for File file storage resources, when migrating file data between VNX OE for File sources and destinations using Migration Projects in the Migration Projects view.

• On Linux file storage resources, when creating and cloning NFS exports in the Storage Resources view, and when cloning NFS exports as needed when creating Phased Migration policies in the Data Movement view.

• When updating automount map files stored on NFS clients as needed when running Phased Migration policies in the Data Movement or Migration Projects views.

NOTEStorageX does not currently support using SSH to communicate with Data ONTAP vFilers, Vservers, or SVMs or EMC Isilon access zones.

Generating an SSH public/private key pairStorageX communicates securely with VNX OE for File file storage resources, Linux file storage resources, and NFS clients using an SSH public/private key pair when performing the following tasks:

• On VNX OE for File file storage resources, when migrating file data between VNX OE for File sources and destinations using Migration Projects in the Migration Projects view.

• On Linux file storage resources, when creating and cloning NFS exports in the Storage Resources view, and when cloning NFS exports as needed when creating Phased Migration policies in the Data Movement view.

TABLE 2

Task

1 Install and configure an SSH server on each VNX OE for File file storage resource, Linux file storage resource, and NFS client as needed and ensure the SSH V2 or later protocol is enabled.

2 If you want StorageX to use an SSH private key to communicate with your storage resources, identify the SSH public/private key pair that you want StorageX to use as needed to communicate with VNX OE for File file storage resources, Linux file storage resources, and NFS clients. You can use an existing SSH public/private key pair, as long as the existing private key is in an OpenSSH-compatible format, or you can generate a new SSH public/private key pair using an SSH tool. For more information about generating a new SSH public/private key pair, see “Generating an SSH public/private key pair” on page 435.

3 If you want StorageX to use an SSH private key to communicate with your storage resources, copy the public key to each VNX OE for File file storage resource, Linux file storage resource, and NFS client as needed. For more information, see “Copying public keys to Linux and VNX OE for File file storage resources and NFS clients” on page 437.

4 Configure StorageX to use either a user name and password or a SSH private key, including the passphrase, if applicable. For more information, see “Configuring default SSH shell credentials” on page 79. If you want to configure only specific storage resources to use a user name and password or SSH private key, modify the SSH settings for each resource. For more information, see “Configuring SSH shell credentials for specific file storage resources” on page 107.

StorageX Administrator’s Guide 435

Page 454: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Generating an SSH public/private key pairA

• When updating automount map files stored on NFS clients as needed when running Phased Migration policies in the Data Movement or Migration Projects views.

StorageX requires that any SSH public/private key pair used with the product be in an OpenSSH-compatible format. You can use any SSH client or tool you prefer to generate a key pair, as long as the keys use the OpenSSH format.

If you want to generate a new SSH public/private key pair to use with StorageX, you can generate the SSH public/private key pair on the StorageX server computer or you can generate the public/private key pair on any other computer where an SSH client is installed, and then either store the private key in a location accessible by the StorageX server and all storage resources, or copy the private key to the StorageX server computer and all storage resources.

If you already have an SSH public/private key pair that you want to use with StorageX, you can use your existing key pair, as long as the existing private key is in an OpenSSH-compatible format.

NOTES:

• If you want to use a configured user name and password for SSH authentication, you do not need to generate a public/private key pair. For more information about specifying SSH credentials, see “Configuring default SSH shell credentials” on page 79.

• If you previously generated an SSH public/private key pair using PuTTY, you must use the PuTTY Key Generator tool to export the private key as an OpenSSH key. For more information about converting an existing PuTTY-generated private key, see “Converting PuTTY-generated SSH private keys to OpenSSH-format private keys” on page 438.

The following web pages provide more information about OpenSSH and Windows SSH clients:

• http://www.openssh.com/

• http://www.putty.org/

• http://sshwindows.sourceforge.net/

Keep all keys in one directory and provide a meaningful name for the new key, such as private_sshV2_1024_key. Remember where this file is saved and the name of the file, because you will have to provide this information to StorageX when you configure StorageX to use SSH to communicate with VNX OE for File file storage resources, Linux file storage resources, and NFS clients as needed. For more information, see “Using SSH shell credentials with StorageX” on page 437.

After you generate the public/private key pair, copy the public key to each VNX OE for File file storage resource that you want to include as a source or destination in a Migration Project, to each Linux file storage resource where you want StorageX to create or clone NFS exports, and to each NFS client where you want StorageX to update and manage automount map files. For more information, see “Copying public keys to Linux and VNX OE for File file storage resources and NFS clients” on page 437.

436 StorageX Administrator’s Guide

Page 455: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Copying public keys to Linux and VNX OE for File file storage resources and NFS clients A

Copying public keys to Linux and VNX OE for File file storage resources and NFS clients

After you generate a public/private key pair or identify an existing public/private key pair you want StorageX to use, copy the public key to each VNX OE for File file storage resource, Linux file storage resource, and NFS client as needed where you want to perform the following tasks:

• On VNX OE for File file storage resources, when migrating file data between VNX OE for File sources and destinations using Migration Projects in the Migration Projects view.

• On Linux file storage resources, when creating and cloning NFS exports in the Storage Resources view, and when cloning NFS exports as needed when creating Phased Migration policies in the Data Movement view.

• When updating automount map files stored on NFS clients as needed when running Phased Migration policies in the Data Movement or Migration Projects views.

Copy the public key into the authorized_keys file on each VNX OE for File file storage resource, Linux file storage resource, and NFS client.

Typically the authorized_keys file is located under a .ssh folder under the user logging in. However, the authorized_keys file may be in a different location based on the type of device and how SSH is configured in your environment.

When you paste the public key into the authorized_keys file, make sure that the public key appears in one line. The key should not be separated by line breaks.

Also make sure that the following directories have the appropriate permissions:

Check the sshd configuration on the resource to verify that public key authentication is enabled. For example, on Red Hat Enterprise Linux 6, the configuration file is in /etc/ssh/sshd_config.

If you changed the sshd configuration to enable public key authentication, restart the SSH daemon.

For more information about how to set up SSH, see the documentation for your VNX OE for File file storage resources, Linux file storage resources, and NFS clients.

Using SSH shell credentials with StorageXStorageX uses the SSH protocol and SSH shell credentials to perform the following tasks:

• On VNX OE for File file storage resources, when migrating file data between VNX OE for File sources and destinations using Migration Projects in the Migration Projects view.

• On Linux file storage resources, when creating and cloning NFS exports in the Storage Resources view, and when cloning NFS exports as needed when creating Phased Migration policies in the Data Movement view.

TABLE 3 Directory permissions

Directory Permissions

home 700 or 755

.ssh 700

authorized_keys 700 or 755

StorageX Administrator’s Guide 437

Page 456: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Converting PuTTY-generated SSH private keys to OpenSSH-format private keysA

• When updating automount map files stored on NFS clients as needed when running Phased Migration policies in the Data Movement or Migration Projects views.

After you configure StorageX to use SSH as needed, you can configure StorageX to use SSH shell commands in the following ways:

• You can configure default SSH shell credentials for StorageX to use to communicate with VNX OE for File file storage resources, Linux file storage resources, and NFS clients as a system option. The default SSH shell credentials are then used to communicate with new VNX OE for File file storage resources, Linux file storage resources, and NFS clients when you add them to the My Resources folder in the Storage Resources view. For more information, see “Configuring default SSH shell credentials” on page 79.

• You can configure specific SSH shell credentials for a specific VNX OE for File file storage resource, Linux file storage resource, or NFS client after you add the resource to the My Resources folder in the Storage Resources view. When you specify specific SSH shell credentials for a specific VNX OE for File file storage resource, Linux file storage resource, or NFS client, the specific SSH shell credentials specified for the VNX OE for File file storage resource, Linux file storage resource, or NFS client override the default SSH shell credentials specified for the system. For more information, see “Configuring SSH shell credentials for specific file storage resources” on page 107.

Converting PuTTY-generated SSH private keys to OpenSSH-format private keys

If you previously used a SSH private key with StorageX that was created using PuTTY, when you upgrade to StorageX 7.8, you must use the PuTTY Key Generator to convert your existing private key to OpenSSH format.

NOTEYou can also create a new public/private key pair using the OpenSSH format.

To convert a PuTTY-generated SSH private key pair to OpenSSH format

1. On a computer where you have the PuTTY SSH client installed, start a command prompt and type the path of the puttygen.exe file. By default, this file is located in the \Program Files\PuTTY folder.

NOTEIf you no longer have the PuTTY client installed, you can obtain a copy of PuTTY from the following Web site: http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html.

2. Press Enter. The PuTTY Key Generator dialog box displays.

3. Click Conversions > Import key, then browse to and select the PuTTY-generated private key you want to convert.

4. If you specified a passphrase for the private key, enter the passphrase and click OK.

5. Click Conversions > Export OpenSSH key.

6. Browse to the location where you want to save the OpenSSH-format private key, specify the name you want to use, and click Save.

438 StorageX Administrator’s Guide

Page 457: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Converting PuTTY-generated SSH private keys to OpenSSH-format private keys A

Keep all keys in one directory, such as the \Program Files\putty installation folder. Provide a meaningful name for the key, such as private_sshV2_1024_key. Remember where this file is saved and the name of the file, because you will have to provide this information to StorageX when you configure StorageX to use SSH to communicate with VNX OE for File file storage resources, Linux file storage resources, and NFS clients as needed.

If you generated the private key on a computer other than the StorageX server computer, ensure you either store the private key in a location accessible by the StorageX server and all storage resources, or copy the private key to the StorageX server computer and all storage resources.

7. Close the PuTTY Key Generator application, then close the command prompt.

8. Configure your StorageX options to use the converted private key. For more information, see “Configuring default SSH shell credentials” on page 79.

StorageX Administrator’s Guide 439

Page 458: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Converting PuTTY-generated SSH private keys to OpenSSH-format private keysA

440 StorageX Administrator’s Guide

Page 459: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX Administrator’s Guide

Appendix

B

Troubleshooting StorageX

This appendix provides detailed information about common problems you might encounter when using StorageX and explains how to resolve or work around those issues.

We recommend you consult this appendix before calling Data Dynamics, Inc. Support. For information about contacting Data Dynamics, Inc. Support, see “Contacting Support” on page ii.

For more information on troubleshooting StorageX, search the Knowledge Base on the Data Dynamics Technical Support Portal at http://www.datdynsupport.com/.

In this appendix•“Initial troubleshooting” on page 441

•“Resolving basic issues” on page 443

•“Troubleshooting known issues” on page 447

•“Understanding StorageX error messages and error codes” on page 454

Initial troubleshootingWhile each issue is different, we recommend taking some simple first steps when troubleshooting a problem with StorageX. These first steps can reduce the time it takes to resolve an issue and aid the Data Dynamics, Inc. Support staff if you decide to escalate the issue.

For more information about initial StorageX troubleshooting steps, see the following topics:

• “Running the Support Site Kit” on page 441

• “Using LogViewer to view StorageX log files” on page 442

Running the Support Site KitBefore going any further, use the Support Site Kit provided with StorageX to gather all relevant logs for the issue you are experiencing:

• If you have an issue related to migration, run the Support Site Kit on the universal data engine being used for the migration process.

• If you have an issue related to storage resources, run the Support Site Kit on the StorageX Console and StorageX server.

By default, the StorageX setup program installs the SupportSiteKit.exe file in the following directory on the StorageX server:

\Program Files\Data Dynamics\StorageX\Tools\SupportSiteKit

You can also download the Support Site Kit from the Data Dynamics Support Portal at http://www.datdynsupport.com/.

441

Page 460: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Initial troubleshootingB

The Support Site Kit automatically gathers all StorageX application logs and basic information about your environment, saving that information to a .zip file on your desktop.

To use the Support Site Kit to collect StorageX log files

1. Connect to the computer where you want to run the Support Site Kit.

2. If you want to collect logs for the StorageX universal data engine, ensure you copy the Support Site Kit to the universal data engine computer. You cannot run the Support Site Kit on a remote computer.

3. Open a command prompt and navigate to the folder where the Support Site Kit is installed. For example, C:\ProgramData\Data Dynamics\StorageX\Tools\SupportSiteKit.

4. Enter the SupportSiteKit.exe command.

5. In the StorageX Support Site Kit Wizard, review the introductory text and click Next.

6. Specify the folder where you want to save the .zip file with all collected logs and information and click Next. By default, the Support Site Kit saves the file to the desktop of the current computer.

7. Specify which types of data you want to collect and click Next. We recommend collecting all available data.

8. Review the StorageX Support Site Kit Summary dialog box and click Finish.

When the Support Site Kit finishes running, you can use the gathered data to resolve your issue or provide the .zip file to the Data Dynamics Support team.

Using LogViewer to view StorageX log filesIf you need to troubleshoot an issue on a specific StorageX component, including a StorageX server or universal data engine, you may want to access StorageX log files directly, without using the Support Site Kit.

To directly access StorageX log files

1. Connect to the StorageX server.

2. Open a command prompt and navigate to the folder where StorageX is installed. For example, C:\Program Files\Data Dynamics\StorageX\.

3. Open the Tools folder, then open the LogViewer folder.

4. Double-click the LogViewerX application.

5. Click the Open Application Log File(s) icon.

6. If you want to view the logs for the StorageX server, select StorageXServer.

7. If you want to view the logs for a StorageX Windows data engine, select StorageXReplicationAgent.

8. If you want to view the logs for the StorageX Console, select MC.

9. If you want to select multiple types of logs, use the Ctrl or Shift keys to select multiple items in the Application list.

10. If you want to color-code log items by severity level, complete the following steps:

442 StorageX Administrator’s Guide

Page 461: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Resolving basic issues B

a. Click View > Options.

b. Select Enable severity level highlighting.

c. Click OK.

11. When you have finished viewing the logs, click the Close icon.

Resolving basic issuesThis section walks you through basic issues that can arise in your StorageX environment and helps you configure your environment and the product to resolve those issues.

This section includes the following subsections:

• “Troubleshooting installation issues” on page 443

• “Troubleshooting licensing and permissions issues” on page 444

• “Troubleshooting storage resource issues” on page 444

• “Troubleshooting Phased Migration issues” on page 445

• “Troubleshooting Migration Project issues” on page 445

• “Troubleshooting post-migration issues” on page 446

Troubleshooting installation issuesThis section displays basic issues users may encounter when installing StorageX.

When installing StorageX, did you copy the setup program to a location on the installation computer? We do not recommend running the setup program remotely.

No. Uninstall StorageX and reinstall using a local copy of the setup program.

Did you install StorageX using the same account that you used to install the SQL Server database instance?

No. Ensure the StorageX installation account has the DVBCreator role assigned in SQL Server, then re-run the setup program.

Is Microsoft .NET Framework 4.6.2 installed on all StorageX servers and StorageX Console computers?

No. Install .NET Framework 4.6.2 on all StorageX servers and StorageX Console computers, then re-run the setup program. For more information about .NET Framework requirements, see “StorageX server computer requirements” on page 14 and “StorageX Console computer requirements” on page 17.

Is JavaScript enabled on the StorageX installation computer?No. Can you enable JavaScript on the StorageX installation computer?

• Yes. Enable JavaScript on the StorageX installation computer, then re-run the setup program.

• No. In the installation package, navigate to the StorageX Setup.msi file, right-click the file, and select Install.

StorageX Administrator’s Guide 443

Page 462: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Resolving basic issuesB

Troubleshooting licensing and permissions issuesThis section displays basic issues users may encounter with regard to StorageX licensing and permissions.

Can you access all views in the StorageX Console?No. You may not have a valid StorageX license key installed and verified. Ensure that you add a valid license key, complete the License Configuration Wizard, and then verify the new license key, if applicable. Evaluation licenses do not need to be verified.

Are you using the correct user account and password for the StorageX service account?No. If you are not using the correct user account and password for the StorageX service account, open the Services Administrative Tool, right-click the StorageX Server service, and select Properties. In the Properties window, click the Log On tab, specify the correct account information, and then click OK.

Is the StorageX service account a member of the Domain Admins group?No. If the StorageX service account is not a member of the Domain Admins group, the service account must be a member of the local Administrators group on all StorageX components and storage resources.

Troubleshooting storage resource issuesThis section displays basic issues users may encounter with regard to adding storage resources in the StorageX Console.

Do all storage resources managed by StorageX pass all resource health checks?No. Verify that the information provided for each resource managed by StorageX is correct.

Is the name of the resource correct?No. In the tree pane on the Storage Resources view, right-click the resource name and select Remove from folder. Then re-add the resource to StorageX using the correct name.

Is the platform type set correctly?No. In the tree pane on the Storage Resources view, right-click the resource name and select Properties. Specify the correct platform type for the resource and click OK.

Is the resource path in the correct format?No. In the tree pane on the Storage Resources view, right-click the resource name and select Properties. Specify the correct path for the resource and click OK.

Can you ping the resource from the StorageX server?No. Is DNS configured correctly on the StorageX server?

• No. Verify DNS settings for the StorageX server so that the server can successfully retrieve information from resources in your environment.

Is the resource located behind a firewall configured to refuse ICMP messages?Yes. Try to remotely manage the computer from the StorageX server.

444 StorageX Administrator’s Guide

Page 463: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Resolving basic issues B

Did you specify the correct SSH credentials (if applicable)?No. In the tree pane on the Storage Resources view, right-click the resource name and select Properties. Specify the SSH credentials you want StorageX to use when communicating with the resource and click OK.

Are the correct ports open on the StorageX server and the resource?No. Configure the ports on both the StorageX server and the specific resource.

Troubleshooting Phased Migration issuesThis section displays basic issues users may encounter when running Phased Migration policies.

Is the specified source path in the correct format in the migration policy?No. In the tree pane on the Data Movement view, right-click the policy name and select Properties. In the Properties window, click Migration Paths, then type or browse to the correct source path.

Is the specified destination path in the correct format in the migration policy?No. In the tree pane on the Data Movement view, right-click the policy name and select Properties. In the Properties window, click Migration Paths, then type or browse to the correct destination path.

Does the migration destination have sufficient space to store the files to be migrated?No. In the tree pane on the Data Movement view, right-click the policy name and select Properties. In the Properties window, click Migration Paths, then type or browse to a destination resource with sufficient space to complete the migration.

Are you using the isi_vol_copy functionality built into StorageX?Yes. Is NDMP properly configured on your NAS device?

• No. Ensure you enable NDMP on both the source and the destination resources.

Did you specify the correct SSH credentials (if applicable)?No. In the tree pane on the Storage Resources view, right-click the resource name and select Properties. Specify the SSH credentials you want StorageX to use when communicating with the resource and click OK.

Troubleshooting Migration Project issuesThis section displays basic issues users may encounter when working with Migration Projects.

Did StorageX successfully validate the Migration Project design?No. Look at any validation errors displayed in the StorageX Console, address any issues in the design, and re-validate the design.

Did StorageX successfully execute the Migration Project design?No. Look at any execution errors displayed in the StorageX Console, address any issues in the design, re-validate the design, and execute the design again.

StorageX Administrator’s Guide 445

Page 464: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Resolving basic issuesB

Troubleshooting post-migration issuesThis section displays basic issues users may encounter after running Phased Migration policies or Migration Projects.

Did StorageX display an Error or Warning icon for the policy?Yes. In the Policy Status window of the center pane, scroll right until you see the Event Details column. Click View Details. In the manifest, drill down to get information on the cause of the Error or Warning.

NOTENot all Warnings indicate that the migration failed.

Did the migration policy complete successfully?No. Look in the manifest for details on the failed migration policy run.

In the manifest, does the error say that access is denied?Yes. Ensure your StorageX service account and universal data engine have permissions to write to the specific shares and exports.

Did the policy exceed its limit?Yes. Re-run the policy or modify the time limit within the policy Properties.

Did another user cancel the policy?Yes. Re-run the policy.

Did StorageX successfully migrate all data, with no files missing?No. Did you configure file exclusion filters in your policy?

• Yes. Disable or modify the filter in the policy Properties and re-run the policy.

No. Did StorageX display an error regarding file or folder name length?

• Yes. Refer to the documentation for the specific storage resource platform to determine if the file or folder name exceeds the limit.

Did StorageX successfully copy security from the source to the destination?No. Call Data Dynamics Technical Support.

Did StorageX identify any files as locked files?Yes. Locked files are files that are currently in use. Re-run the policy when the locked files are no longer being used.

Did StorageX successfully create all folders for migrated shares or export?No. Does the policy have root client for the StorageX server and universal data engine, and does the StorageX service account have root permissions?

446 StorageX Administrator’s Guide

Page 465: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Troubleshooting known issues B

Troubleshooting known issuesThis section lists known issues with StorageX and with the different types of storage resources StorageX can manage, as well as solutions or workarounds for those issues.

This section includes the following subsections:

• “Troubleshooting known storage resource management issues” on page 447

• “Troubleshooting known Migration Project issues” on page 449

• “Troubleshooting known Phased Migration issues” on page 451

• “Troubleshooting known reporting issues” on page 453

Troubleshooting known storage resource management issuesThis section displays known issues and solutions or workarounds related to storage resources.

This section includes the following issues:

• “StorageX does not properly display current restart mode setting for NetApp SnapMirrors” on page 447

• “Local groups must be added using NetApp OnCommand on Data ONTAP 8.2.1 and earlier Vservers” on page 447

• “Cannot specify security style or oplocks settings when creating qtrees on Data ONTAP vFiler file storage resources” on page 448

• “StorageX does not properly display folders under EMC VNX vServers” on page 448

StorageX does not properly display current restart mode setting for NetApp SnapMirrors

If you view the properties of a NetApp SnapMirror in the Storage Resources view and change the Restart mode setting on the Options and Schedule tab, then re-open the properties window, StorageX does not display the updated Restart mode setting. This error occurs because StorageX cannot correctly display the current restart mode of a SnapMirror. However, StorageX does correctly set the restart mode.

Local groups must be added using NetApp OnCommand on Data ONTAP 8.2.1 and earlier Vservers

If you use a Data ONTAP 8.2.1 or earlier CIFS share as the destination for a migration, Disaster Recovery, or Replication policy, the policy may fail with the error message “The remote procedure call failed.” This error occurs when the Create local groups on the destination if not found option is enabled, because the StorageX universal data engine cannot create missing local groups on the Vserver. This is caused by a limitation in Data ONTAP.

To work around this issue, either disable the Create local groups on the destination if not found option or use the NetApp OnCommand console to create the local group on the Vserver and then re-run the policy.

StorageX Administrator’s Guide 447

Page 466: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Troubleshooting known issuesB

Cannot specify security style or oplocks settings when creating qtrees on Data ONTAP vFiler file storage resources

When you use StorageX to create qtrees on volumes Data ONTAP file storage resources, typically you can specify a security style for the qtree, as well as specify if you want to enable or disable oplocks settings. However, if you are creating a qtree on a volume that is owned by a Data ONTAP vFiler in the Storage Resources view, you cannot specify a security style or oplocks setting on the qtree. New qtrees created on volumes owned by vFilers inherit the security style and oplocks setting from the volume.

In addition, if you plan to use StorageX Migration Projects with Data ONTAP vFilers as destinations, consider the following scenarios:

• If you are moving a volume from a source Data ONTAP file storage resource to a volume on a destination Data ONTAP vFiler, when you execute the Migration Project design, StorageX creates the qtree on a volume on the destination vFiler, and the qtree on the destination inherits the security style and oplocks setting from the destination volume.

• If you are moving a VNX OE for File File System from a source VNX OE for File file storage resource to a volume on a destination Data ONTAP vFiler, when you execute the Migration Project design, StorageX creates the qtree on a volume on the destination vFiler, and the qtree inherits the security style and oplocks setting from the destination volume.

• If you are moving a Data ONTAP qtree or VNX OE for File tree quota from a Data ONTAP or VNX OE for File file storage resources to a volume on a destination Data ONTAP vFiler file storage resource, StorageX creates the qtree on a volume on the destination vFiler, and the qtree inherits the security style and oplocks setting from the destination volume.

If you plan to use StorageX Migration Projects with Data ONTAP vFilers as destinations, after you execute the Migration Project design, ensure you verify the security style and oplocks settings on the destination qtrees before you migrate file data to the destinations using Migration Project Phased Migration policies.

If you want to change the qtree security style or oplocks settings on the destination, connect to the vFiler file storage resource directly and change the settings. For more information, see the Data ONTAP CLI command documentation.

StorageX does not properly display folders under EMC VNX vServers

In EMC VNX environments with dual control stations installed, when you add an EMC VNX server and its hosted vServers to your storage resources using the management alias IP address or name of the server, StorageX cannot properly display the file system folders under the Volumes folders for one or more of the vServers.

This issue occurs when slot_1 is configured as the primary control station. To resolve this issue, you must log into the EMC VNX server and manually fail over from the slot_1 primary control station to the slot_0 control station.

To fail over from the slot_1 control station to the slot_0 control station, complete the following steps:

1. Log into the EMC VNX control station. When you successfully log in, the user interface displays a message showing which control station slot is currently the primary control station.

2. If you need to determine which control station slot is the primary, enter the following command:

/nas/sbin/getreason

448 StorageX Administrator’s Guide

Page 467: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Troubleshooting known issues B

3. Enter the su command and provide the password necessary for root access.

4. Enter the following command to start the failover process:

/nasmcd/sbin/cs_standby -failover

5. When the user interface asks if you want to reboot the system, enter yes.

6. To confirm the control station has failed over successfully, enter the following command:

/nas/sbin/getreason

The user interface should display the primary control station as having switched to slot_0.

7. Log out of the control station.

For more information about failing over EMC VNX control stations, see the following article on the EMC VNX Product Community site:

https://community.emc.com/docs/DOC-45561

Troubleshooting known Migration Project issuesThis section displays known issues and solutions or workarounds related to Migration Projects.

This section includes the following issues:

• “Migration Project policies cannot detect existing folder on destination Data ONTAP 8.3 Vserver” on page 449

• “StorageX cannot copy the NetApp “maxdirsize” volume option with Migration Projects” on page 450

• “Migration Project designs fail when migrating to multiple Vservers on the same cluster” on page 450

• “User and group quotas on Data ONTAP sources are not migrated to VNX OE for File destinations” on page 450

• “Migration Project design execution fails if the destination is a VNX OE for File Virtual Data Mover, an object on the source has the same name as an item on the destination, and the item on the destination with the same name is not visible to the destination VDM” on page 450

• “Export cloning fails when VNX is the destination, and the VNX server has a large number of NFS exports” on page 451

Migration Project policies cannot detect existing folder on destination Data ONTAP 8.3 Vserver

If you create a Migration Project design that uses a Data ONTAP 8.3 Vserver as the destination, and the Vserver contains a folder with the same name as the source, when you execute the design, the export creation process may fail with the following error in the Sharing data on destination node of the manifest:

Failed to create or determine if a junction exists within volume "VOLUMENAME". Error occurred with the remaining junction path of "DESTPATH" for the given path of "SOURCEPATH" Reason: Junction create failed (21).

StorageX cannot determine if a folder already exists on the destination. To work around this issue, you must manually create the junction path, then re-run the Migration Project policy.

StorageX Administrator’s Guide 449

Page 468: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Troubleshooting known issuesB

StorageX cannot copy the NetApp “maxdirsize” volume option with Migration Projects

If you create a Migration Project design that uses Data ONTAP resources as both source and destination, StorageX does not copy the NetApp volume option maxdirsize from the source to the destination.

This limitation occurs because NetApp optimizes this option for each specific version of Data ONTAP and does not allow you to copy the option value from one volume to another. For more information about configuring this volume option, contact NetApp technical support.

NOTES:

• If you use SnapMirror replication for a Migration Project policy, the SnapMirror functionality duplicates the source maxdirsize volume option on the destination.

• This limitation only applies to Migration Projects where the source is a volume. This limitation does not apply to Migration Projects where the source is a qtree.

Migration Project designs fail when migrating to multiple Vservers on the same cluster

If you create a Migration Project design that uses as destination resources two Vservers or SVMs hosted on the same cluster and aggregate, and the aggregate does not have enough space to store the migrated data more than once, StorageX successfully validates the design and displays no errors. However, when you execute the design, the design fails to execute with an error that there is not enough space available to create the new volume on the destination.

When creating a Migration Project design with multiple Vservers or SVMs as destination resources, you must ensure that there is sufficient space on the destination host resource to migrate data for all specified destination Vservers or SVMs.

User and group quotas on Data ONTAP sources are not migrated to VNX OE for File destinations

StorageX does not support the migration of local user and group quotas or domain user and group quotas from source Data ONTAP file storage resources to destination VNX OE for File file storage resources.

Migration Project design execution fails if the destination is a VNX OE for File Virtual Data Mover, an object on the source has the same name as an item on the destination, and the item on the destination with the same name is not visible to the destination VDM

If your destination is a VNX OE for File Virtual Data Mover (VDM) and you have an object on your source, such as a Data ONTAP volume or VNX OE for File File System, with the same name as a VNX OE for File File System on your destination, and the VNX OE for File File System with the same name is not visible to the destination VDM, when you validate the Migration Project design, the design validates successfully. However, when you execute the Migration Project design, the design execution fails and a This name already exists error message displays.

450 StorageX Administrator’s Guide

Page 469: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Troubleshooting known issues B

To avoid this issue, ensure that source object names do not already exist on destination VNX OE for File VDM destinations when you create Migration Project designs.

Export cloning fails when VNX is the destination, and the VNX server has a large number of NFS exports

When you execute a Migration Project design, and the destination of the migration project is a VNX server with a large number of NFS exports, the export creation phase may fail with the following error in the Sharing data on destination node of the manifest:

Failed sharing resources '<export name>': Failed to create NFS export on destination machine.

A VNX server has an upper limit on the buffer size it will use when responding to a mount request to enumerate the NFS exports on the server. Because of this limit, the VNX server may not return information for all NFS exports. This happens when the amount of data required to list all exports is greater than the maximum buffer size configured for the VNX server. In testing StorageX with the default VNX configuration, the VNX returned information for approximately 3,000 exports even though it had 8,000 exports configured (the exact number returned will vary based on the lengths of the export paths).

Because the VNX server does not return all NFS exports, the StorageX server attempts to create an export that already exists, resulting in the error listed above.

The fix to this issue is to increase the upper limit of the buffer size used by the VNX server when it responds to a mount request to enumerate its NFS exports. In the EMC VNX Series Release 7.1 Parameters Guide for VNX for File document, the upper limit is documented as being controlled by the mount facility parameter tcpResponseLimit. The default value is 262144, but it can be increased up to 1048576. The needed size depends on the number of NFS exports (and their corresponding path lengths) defined on the VNX server. See the VNX documentation for more details.

Troubleshooting known Phased Migration issuesThis section displays known issues and solutions or workarounds related to Phased Migration policies.

This section includes the following issues:

• “Access denied error when migrating NetApp qtrees” on page 452

• “Phased Migration replication option to clear the Archive attribute for files on the destination does not properly clear the attribute” on page 452

• “Phased Migration policies return error when migrating files or folders with local security descriptors between Data ONTAP 7-Mode and Data ONTAP 8.3” on page 452

• “Phased Migration policies fail when migrating data to destination resources with paths longer than the character limit allowed on the resource” on page 452

• “StorageX may display the error: Unable to contact VNX device 'VNXFileStorageResourceName': The remote server returned an error: (503) Server Unavailable under the following conditions” on page 453

StorageX Administrator’s Guide 451

Page 470: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Troubleshooting known issuesB

Access denied error when migrating NetApp qtrees

If you run a Phased Migration policy to move data from one volume to another and the destination volume does not have enough available space and has automatic growth disabled, the NetApp device closes all active share connections for that volume and you will see an "Access denied" error in the StorageX UI even if your account credentials are correct.

To work around this issue, ensure that the size of the volume is sufficient to complete the data migration.

Phased Migration replication option to clear the Archive attribute for files on the destination does not properly clear the attribute

If you create a Phased Migration policy and the destination storage resource contains files that have the Archive attribute set, when you select the Attribute setting on destination > Clear option for Archive attributes in the CIFS Attribute Replication tab, StorageX does not consistently clear the Archive attribute.

Phased Migration policies return error when migrating files or folders with local security descriptors between Data ONTAP 7-Mode and Data ONTAP 8.3

If you add a local group to the Security properties of a file or folder located on a NetApp Data ONTAP 7-Mode file storage resource and then run a Phased Migration policy to migrate from the 7-Mode file storage resource to a Data ONTAP 8.3 CIFS Vserver that does not have the same local group, StorageX returns the following error in the manifest:

A device attached to the system is not functioning.

This error occurs because of a NetApp Data ONTAP 8.3 issue, where NetApp Data ONTAP 8.3 Vservers cannot correctly process local security descriptors.

To work around this issue, right-click the Phased Migration policy and select Properties, click Replication Options > CIFS Security Replication, clear the Process local trustees in security descriptor option, click OK, and then re-run the policy.

Phased Migration policies fail when migrating data to destination resources with paths longer than the character limit allowed on the resource

If you run a Phased Migration policy where the destination file storage resource path is longer than the character limit allowed on the resource, the policy fails with a “The filename or extension is too long.” error message. This issue occurs both when the folders in the specified path already exist and when one or more folders are created during the migration process.

Before creating and running Phased Migration policies, ensure the destination path is shorter than the number of characters allowed on the resource. For information about storage resource character limits for a particular resource, see the documentation for the device.

452 StorageX Administrator’s Guide

Page 471: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Troubleshooting known issues B

StorageX may display the error: Unable to contact VNX device 'VNXFileStorageResourceName': The remote server returned an error: (503) Server Unavailable under the following conditions

If you install the StorageX server on a Windows computer that does not have sufficient processing power or memory and you then try to run several hundred Phased Migration policies at the same time and that all have VNX OE for File file storage resources as destinations. In this scenario, when the Phased Migration policies run and try to clone a shared folders from the source to the destination the 'VNXFileStorageResourceName': The remote server returned an error: (503) Server Unavailable error message displays.

If you have installed the StorageX server on a computer with sufficient processing power and memory but there are other storage applications connecting to the VNX OE for File file storage resources that are consuming lots of connections to the VNX OE for File file storage resource. In this scenario, when the Phased Migration policies run and try to clone a shared folders from the source to the destination the 'VNXFileStorageResourceName': The remote server returned an error: (503) Server Unavailable error message displays

This issue is caused by a limitation in the EMC VNX API. By design, VNX file storage resources have a maximum of 16 connections. This 16 connection limit is designed to prevent denial of service attacks.

If you are running the StorageX server on a Windows computer without sufficient processing power or memory, you can resolve this issue by installing the StorageX server on a newer computer with more processing power and memory. For more information about StorageX server computer requirements, see the StorageX Administrator’s Guide.

If you are running the StorageX server on a Windows computer with sufficient processing power or memory but other storage applications are consuming the connections, you can resolve this issue by stopping the other storage applications that are consuming connections when you are running a large number Phased Migration policies all at the same time.

Troubleshooting known reporting issuesThis section displays known issues and solutions or workarounds related to reporting.

This section includes the following issues:

• “Storage Resource Reports do not list the correct number of NFS exports for a VNX server when it has a large number of NFS exports” on page 453

Storage Resource Reports do not list the correct number of NFS exports for a VNX server when it has a large number of NFS exports

When you view a report that lists NFS exports for a VNX server (e.g., the Exports report or the Storage Resource Summary report), the number of NFS exports listed in the report may be less than the number of exports configured on the VNX server if the VNX server has a large number of NFS exports.

StorageX Administrator’s Guide 453

Page 472: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding StorageX error messages and error codesB

A VNX server has an upper limit on the buffer size it will use when responding to a mount request to enumerate the NFS exports on the server. Because of this limit, the VNX server may not return information for all NFS exports. This happens when the amount of data required to list all exports is greater than the maximum buffer size configured for the VNX server. In testing StorageX with the default VNX configuration, the VNX returned information for approximately 3,000 exports even though it had 8,000 exports configured (the exact number returned will vary based on the lengths of the export paths).

Because the VNX server does not return all NFS exports, the StorageX reports that include information about NFS exports do not show the correct number of NFS exports for the VNX server.

The fix to this issue is to increase the upper limit of the buffer size used by the VNX server when it responds to a mount request to enumerate its NFS exports. In the EMC VNX Series Release 7.1 Parameters Guide for VNX for File document, the upper limit is documented as being controlled by the mount facility parameter tcpResponseLimit. The default value is 262144, but it can be increased up to 1048576. The needed size depends on the number of NFS exports (and their corresponding path lengths) defined on the VNX server. See the VNX documentation for more details.

Understanding StorageX error messages and error codesThe following table displays a number of error messages and error codes you may encounter when using StorageX, as well as possible causes and recommendations for resolving the issue behind each error message.

NOTEThis table is not meant to be comprehensive, but is instead a sample of error messages and codes that a user is likely to see.

Error Message Displayed (if applicable)

Error Code (if applicable)

Possible Cause/Meaning Suggested Resolution/Remediation

Access is denied. NV_E_ACCESSDENIED

This message indicates that StorageX could not access the specified storage resource.

This message could be triggered by a number of access-related issues, depending on the context in which it is displayed.Ensure that the StorageX service account has sufficient permissions to access the resource, and that all API and SSH credentials required are correct, then retry the action.

The data engine has been paused and is not accepting new jobs.

NV_E_AGENT_PAUSED

This message indicates that the StorageX universal data engine used to run the policy has been paused.

In the StorageX Console, click the Control Panel view, then find the paused universal data engine in the list of data engines. Right-click the paused data engine and select Resume.

454 StorageX Administrator’s Guide

Page 473: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding StorageX error messages and error codes B

An attempt was made to create an NFS directory which already exists.

NV_E_NFS_DIRECTORY_EXISTS

This message indicates that the policy specified a new NFS path that already exists on the destination storage resource.

Either change the destination of the policy to use a different path on the NFS storage resource that does not already exist or remove the existing NFS export from the destination.

Cannot create a file when that file already exists.

This message indicates that StorageX was unable to create a new file at the specified location.

This message could be triggered by a number of access-related issues, depending on the context in which it is displayed.Ensure that the StorageX service account has sufficient permissions to access the resource, and that all API and SSH credentials required are correct, then retry the action.

Corrupt data NV_E_CORRUPT_DATA

This message indicates that data stored for internal use by the StorageX application has become corrupted.

This message could be an indication of a hard disk failure, where data stored in the StorageX database has been corrupted, or it could indicate operating system-level corruption in the Windows registry.Please contact your local network administrator to determine if a problem has occurred with any of the servers on which StorageX components are installed.

A device attached to the system is not functioning correctly.

This message may indicate that StorageX was unable to migrate one or more files because those files have an invalid SID.

Examine any files StorageX could not migrate and determine whether the files have valid SIDs.

Error trying to read from or write to a file.

NV_E_FILECREATE

This message indicates that StorageX does not have sufficient permissions to read from or write to a file on the source or destination resource.

Ensure the StorageX service account has permissions on both the source and destination and retry the action.

Error trying to write to a file.

NV_E_FILEWRITE

This message indicates that StorageX does not have sufficient permissions to write to a file on the source or destination resource.

Ensure the StorageX service account has permissions on both the source and destination and retry the action.

The evaluation license has expired.

NV_LICENSE_KEY_EXPIRED

This message indicates that the specified StorageX Evaluation License has expired.

Please contact the Data Dynamics Sales team to request a valid license.

Error Message Displayed (if applicable)

Error Code (if applicable)

Possible Cause/Meaning Suggested Resolution/Remediation

StorageX Administrator’s Guide 455

Page 474: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding StorageX error messages and error codesB

The file or directory is encrypted. The request is not supported.

NV_E_FILE_ENCRYPTED

This message indicates that the specified file or folder is encrypted and cannot be migrated.

StorageX does not support migrating encrypted files or folders.Please contact Data Dynamics Technical Support for more information.

The filename, directory name, or volume label syntax is incorrect.

This message indicates that StorageX was unable to perform the action on the specified file, directory, or volume because the name of that resource used an invalid syntax.

Verify that the name of the file, directory, or volume uses the correct format and that there were no errors made when entering the path, then retry the action.

Generic ONC-RPC error. NV_E_ONCRPC_ERROR

This message indicates that StorageX encountered issues when trying to communicate with an NFS server.

This message could be triggered by any of several NFS-related issues, some of which may be transient. Retry the action that caused the message to initially be displayed.If the message persists, contact Data Dynamics Technical Support.

Incorrect function This message indicates that StorageX attempted to perform an action that is not supported on the destination resource.

Ensure that the destination resource platform allows the action you want StorageX to perform and retry the action if necessary.

Insufficient access granted to complete the NFS operation.

NV_E_NFS_ACCESS

This message indicates that StorageX does not have sufficient permissions on the NFS storage resource.

Ensure that the StorageX service account has sufficient permissions on the storage resource, as outlined in the StorageX Administrator's Guide, and retry the action.

Insufficient access granted to complete the NFS read-file operation.

NV_E_NFS_FILE_ACCESS

This message indicates that StorageX does not have sufficient permissions to read files from the source NFS storage resource.

Ensure that the StorageX service account has sufficient permissions on the source storage resource, as outlined in the StorageX Administrator's Guide, and retry the action.

Invalid Format NV_E_INVALID_FORMAT

This message indicates either that there are issues with a SID mapping file or that you specified an invalid path when using FileInsight.

Verify that all entries in the specified SID mapping file are valid or ensure that you are using the correct path when running FileInsight.

The network name could not be resolved.

NV_E_NAME_RESOLUTION

This message indicates that the network name specified for the storage resource could not be resolved. The name may be invalid, or there may be a connection issue between the StorageX universal data engine and the resource.

In the storage resources Properties window, verify that the storage resource network name is valid.

Error Message Displayed (if applicable)

Error Code (if applicable)

Possible Cause/Meaning Suggested Resolution/Remediation

456 StorageX Administrator’s Guide

Page 475: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding StorageX error messages and error codes B

The network resource was not found.

NV_E_NOTFOUND

This message indicates that StorageX was attempted to access a resource that does not exist in the specified location.

This message could be triggered by a number of access-related issues, depending on the context in which it is displayed.Ensure that the StorageX service account has sufficient permissions to access the resource, and that all API and SSH credentials required are correct, then retry the action.

NFS Server is not started.

NV_E_ONCRPC_PROGRAM_UNAVAILABLE

This message indicates that the NFS service on the destination NFS resource is not currently running.

On the destination NFS resource, verify that the NFS service is running. If the service is not running, log in to the destination resource as root, start the NFS service, and rerun the policy.

No input parameters were selected for the report.

NV_E_NO_INPUT

This message indicates that StorageX could not display the specified report, because no parameters were provided for the report.

Verify the configuration for the report and confirm that all necessary parameters and options have been provided. When finished, refresh the report.

Not enough quota is available to process the command

This message indicates that there may be insufficient memory available on the StorageX server to complete the current action.

If StorageX displays this message, close other applications running on the StorageX server and retry the action.If the action still cannot be completed, increase the size of the server paging file in the Control Panel > System > Virtual Memory.

Error Message Displayed (if applicable)

Error Code (if applicable)

Possible Cause/Meaning Suggested Resolution/Remediation

StorageX Administrator’s Guide 457

Page 476: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding StorageX error messages and error codesB

The operation is not supported.

NV_E_UNSUPPORTED

This is a generic message and can indicate a number of different issues:• The StorageX server and

universal data engine are running different versions of the product, and StorageX attempts to make a remote procedure call.

• StorageX tries to copy NFS data to a destination resource that does not support symbolic links.

• StorageX is copying CIFS security and encounters an unknown SID type.

• StorageX encounters unrecognized replication options while migrating. For example, if a StorageX server with a later version of the product sends a replication task to an older universal data engine, and a new replication option was added in the later version.

Ensure your StorageX server and all universal data engines are running the same version of the product.If migrating NFS data, verify the configuration of your destination resource and then retry.If copying CIFS security, verify that all SID types on the source are valid and then retry.

Operation completed with errors.

NV_E_COMPLETED_WITH_ERRORS

This message indicates that the current policy completed with warnings.

In the Policy Status area, click View Details in the Event Details column to view the policy manifest. Examine the manifest to determine what errors the policy returned, address any issues, and rerun the policy.

Operation completed with warnings.

NV_E_COMPLETED_WITH_WARNINGS

This message indicates that the current policy completed with warnings.

In the Policy Status area, click View Details in the Event Details column to view the policy manifest. Examine the manifest to determine what warnings the policy returned, address any issues, and rerun the policy, if necessary.

The operation was canceled.

NV_CANCELED This message indicates that the current migration was canceled by a user.

If StorageX displays this message, a user canceled the migration either directly or indirectly. For example, this message could be displayed if the StorageX server was rebooted, thereby canceling all currently running policies.If the policy run was not canceled intentionally, rerun the policy.

Error Message Displayed (if applicable)

Error Code (if applicable)

Possible Cause/Meaning Suggested Resolution/Remediation

458 StorageX Administrator’s Guide

Page 477: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding StorageX error messages and error codes B

The operation was canceled.

NV_CANCELED_ON_ERROR

This message indicates that StorageX encountered an error and canceled the migration.

In the Policy Status area, click View Details in the Event Details column to view the policy manifest. Examine the manifest to determine what errors the policy returned and address any issues. Also examine the StorageX and Windows event logs and address any issues, then rerun the policy.

The operation was cancelled because time window has expired.

NV_CANCELED_WINDOW_CLOSED

This message indicates that the current migration was canceled because the policy run exceeded the replication duration specified for the policy.

If StorageX displays this message without encountering any other issues, you may want to consider changing the specified replication duration.Right-click the policy, and in the General Options tab, change the value of the Replication Duration setting, then rerun the policy.

Operation would cause loss of file security.

NV_E_FILE_SECURITY_LOSS

This message indicates that the source resource is in the NTFS format, but the destination resource does not support NTFS.

Right-click the policy, and in the CIFS Security Replication tab, select Allow loss of security information when the destination does not support NTFS security. Click OK, then rerun the policy.

Operation would cause loss of file streams.

NV_E_FILE_STREAM_LOSS

This message indicates that the source resource is in the NTFS format, but the destination resource does not support NTFS.

Right-click the policy, and in the General Options tab, select Allow loss of additional file streams (CIFS only). Click OK, then rerun the policy.

Operation would cause loss of file meta data.

NV_E_FILE_METADATA_LOSS

This message indicates that the source resource is in the NTFS format, but the destination resource does not support NTFS.

Right-click the policy, and in the General Options tab, select Allow loss of additional file streams (CIFS only). Click OK, then rerun the policy.

The process cannot access the file because it is being used by another process.

This message indicates that StorageX was unable to migrate one or more files because those files are locked.

Ensure that all files being migrated are not currently being used or are not otherwise locked, and rerun the policy.

The protocol is not supported.

NV_E_PROTO_UNSUPPORTED

This message indicates that the policy attempted to migrate using a protocol (CIFS or NFS) that is not supported on the destination resource.

Verify that the destination resource is configured correctly in the policy and that the destination resource supports the specified protocol.

Error Message Displayed (if applicable)

Error Code (if applicable)

Possible Cause/Meaning Suggested Resolution/Remediation

StorageX Administrator’s Guide 459

Page 478: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding StorageX error messages and error codesB

Registry error NV_E_REGISTRY

This error indicates that StorageX encountered a problem opening or saving values in the Windows registry.

Ensure that the StorageX service account has full access to the Windows registry on the StorageX server, and that all StorageX registry keys are intact.

Replication failed to copy any of the files.

NV_E_COMPLETED_WITH_CATASTROPHIC_ERRORS

This message indicates that StorageX was unable to replicate any files between the source and destination storage resources, despite having appropriate levels of access on both resources. This may mean that the destination resource has experienced an unexpected failure.

Ensure both the source and destination resources are online and functioning properly and rerun the policy.

A required privilege is not held by the client.

NV_E_SEC_PRIV

This message indicates that the StorageX service account does not have sufficient permissions to manage one or more storage resources.

Ensure the StorageX service account has permissions on all managed resources and retry the action.

A required registry entry was not found.

NV_E_REG_REQUIRED_NOTFOUND

This error indicates that StorageX could not find a required entry in the Windows registry.

Ensure that the StorageX service account has full access to the Windows registry on the StorageX server, and that all StorageX registry keys are intact.

The resource already exists.

NV_E_ALREADY_EXISTS

This message indicates that a user attempted to add or create a storage resource in StorageX that already exists.

Check if the storage resource you want to add is already listed in the Storage Resources view in the StorageX Console.

The share's local path is invalid

NV_E_SHARE_LOCAL_PATH_INVALID

This message indicates that StorageX could not add the specified share because the specified local path for the share was invalid.

Verify that the share can be created in the specified location on the local server and retry the action.

The timeout period was exceeded while waiting to receive a reply to an ONC-RPC call.

NV_E_ONCRPC_TIMED_OUT

This message indicates that StorageX encountered a network interruption while migrating or archiving data.

Ensure that there are no network interruptions in the overall network infrastructure and that there are no disruptions on the destination, then rerun the policy.

Unable to mount an export for NFS operations.

NV_E_NFS_MOUNT_ERROR

This message indicates that StorageX could not mount the specified export.

Examine the StorageX and Windows event logs, address any issues, and rerun the policy, if necessary.

Error Message Displayed (if applicable)

Error Code (if applicable)

Possible Cause/Meaning Suggested Resolution/Remediation

460 StorageX Administrator’s Guide

Page 479: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding StorageX error messages and error codes B

A write operation was attempted on an NFS read-only file system.

NV_E_NFS_READONLY_FILESYSTEM

This message indicates that the destination NFS resource is configured to be read-only, and StorageX cannot write data to the destination.

Either remove the read-only NFS resource as the destination of the policy, or change the configuration of the resource itself to allow the StorageX universal data engine to copy data.

NONE NV_E_FILEPTR This message indicates that StorageX encountered an error when trying to copy an NFS file from the source to the destination.

This issue may be caused by conflicts with an outside file-archival solution running on the source or destination resource.

NONE NV_E_LIBRARY This message indicates that StorageX encountered an error when loading or unloading a DLL required for product functionality.

If you see this error, you may need to reinstall the product in order to resolve the underlying issue. Please contact Data Dynamics Technical Support for more information.

NONE NV_LICENSE_KEY_INVALID

This message may indicate either that the StorageX database has been corrupted or that a user has illegally attempted to modify a StorageX license, thereby invalidating the license.

Please contact Data Dynamics Technical Support for more information.

Error Message Displayed (if applicable)

Error Code (if applicable)

Possible Cause/Meaning Suggested Resolution/Remediation

StorageX Administrator’s Guide 461

Page 480: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Understanding StorageX error messages and error codesB

462 StorageX Administrator’s Guide

Page 481: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX Administrator’s Guide

Appendix

C

Using the StorageX API

While StorageX works with APIs provided for different storage resources, the product also includes its own internal set of APIs, which allow advanced users to interact directly with StorageX functionality outside of the StorageX Console, StorageX Management Portal, or StorageX Retrieval Portal. This enables users to create their own custom integrations into the StorageX environment.

You can run API calls outside of the StorageX user interfaces to create policies, delete policies, get details about policy runs, archive data to object storage resources, get data about your universal data engines, and perform other StorageX functions.

For detailed information about specific API calls, see the StorageX API Guide.

ATTENTIONStorageX API functionality is recommended for use only by advanced users who are knowledgeable about the product.

In this appendix•StorageX API requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463

•Using the StorageX API Web interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464

StorageX API requirementsIn order to use the StorageX API and API Web interfaces, you must ensure that your StorageX environment meets the following requirements:

• StorageX role-based access control (RBAC) must be enabled.

Because the StorageX APIs expose low-level functionality to users outside of the StorageX Console, including some types of functionality that might be restricted for most users of the product, role-based access control must be enabled in your StorageX environment for API usage.

Note that when you enable access control, you must assign roles to any users who you want to be able to work with StorageX, either in the Console, the Management Portal, or Retrieval Portal, or through the API. The only account assigned a role by default is the StorageX service account.

For information about configuring role-based access control, see “Configuring role-based access control” on page 46.

• A Web browser must be installed on a computer with access to the StorageX server.

NOTES:

463

Page 482: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using the StorageX API Web interfacesC

• If you use Microsoft Internet Explorer, ensure you disable Compatibility View in the browser to correctly display the API Web interface. In Internet Explorer, click Tools > Compatibility View settings, clear Display intranet sites in Compatibility View, and click Close.

• If you receive an HTTP Error 400 Bad request message when connecting to the API Web interface using a browser, substitute the IP address of the server for the fully-qualified domain name, which is used by default, and try again to connect to the interface.

• If upgrading from a previous version of StorageX, ensure the MC.exe.config file includes the StorageX server name as the value of the WebServer.Server property on the StorageX server and all StorageX Console computers. For more information about upgrading StorageX and changing configuration properties post-upgrade, see “Upgrading StorageX servers and databases” on page 53 and “Upgrading StorageX Console computers” on page 54.

Using the StorageX API Web interfacesThis section explains how to access the StorageX API Web interfaces, which are automatically installed on the StorageX server when you install the product. These Web interfaces use the Swagger framework to automatically generate information based on the APIs.

Using the API Web interfaces, you can view information about the API calls available for StorageX, run API calls on your StorageX server, and view responses received from API calls run on the server. The Web interfaces display errors if an API call cannot be run successfully, allowing you to resolve issues before using the API call in a script or other integration.

There are different Web interfaces for each set of APIs, located at the following default URLs:

StorageX Migration APIhttps://servername:9454/swagger/ui/index

StorageX Management/Analysis Portal APIhttps://servername:9777/swagger/ui/index

StorageX Metadata Service APIhttps://servername:9462/swagger/ui/index

When you use the API Web interfaces to run an API call, you must have an access token and provide that access token in the Authorization field.

You can use third-party tools like Postman to generate access tokens. For more information about using Postman to generate access tokens, see the following links:

• https://www.getpostman.com/docs/postman/sending_api_requests/authorization

• https://www.codeproject.com/Articles/1090252/Token-Based-Authentication-using-Postman-as-Client

464 StorageX Administrator’s Guide

Page 483: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using the StorageX API Web interfaces C

To use the StorageX API Web interfaces

1. Log onto a computer with access to the StorageX server using an account with sufficient permissions to use the StorageX APIs.

2. Open a Web browser.

3. If you want to access the StorageX Migration API, navigate to the following URL:

https://servername:9454/swagger/ui/index

Where servername is the name of the StorageX server.

NOTEIf the StorageX server is attached to a domain, ensure you specify the full server name, including the domain. For example: https://servername.domain.domain:9454/swagger/ui/index

4. If you want to access the StorageX Management/Analysis API, navigate to the following URL:

https://servername:9777/swagger/ui/index

Where servername is the name of the StorageX server.

NOTEIf the StorageX server is attached to a domain, ensure you specify the full server name, including the domain. For example: https://servername.domain.domain:9777/swagger/ui/index

5. If you want to access the StorageX Metadata Service API, navigate to the following URL:

https://servername:9462/swagger/ui/index

Where servername is the name of the StorageX server.

NOTEIf the StorageX server is attached to a domain, ensure you specify the full server name, including the domain. For example: https://servername.domain.domain:9462/swagger/ui/index

6. If the browser displays a warning, ensure you have installed a trusted certificate and configured StorageX to use that certificate.

7. If you see an “Insecure Connection” warning while using Mozilla Firefox to access the APIs, complete the following steps:

a. In the Web browser, open a new window or tab and enter about:config.

b. If prompted by the browser, click to accept.

c. In the list of preferences, find the security.enterprise_roots.enabled preference.

d. If the preference does not exist, right-click the list, select New > Boolean, specify the name security.enterprise_roots.enabled, and click OK.

e. Double-click the preference to set the value to true.

f. Close the window or tab.

g. Retry the API link.

StorageX Administrator’s Guide 465

Page 484: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using the StorageX API Web interfacesC

8. If you want to view detailed information about a specific API call, click the name of the API call. The browser displays the implementation notes, schema, parameters, and responses for the call.

9. If you want to run a specific API call on your StorageX server, complete the following steps:

a. Click the name of the API call.

b. Specify the values for each parameter used by the API call, as necessary.

c. In the Authorization field, provide the access token used by the API.

d. Click Try it out!.

The Web interface displays the response for the call in the Curl, Request URL, Response Body, Response Code, and Response Headers fields.

e. If you want to use the specific API call outside of StorageX, copy the string displayed in the Curl field for the call and incorporate the Curl code into your own scripts.

10. When finished, close the browser window.

466 StorageX Administrator’s Guide

Page 485: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

StorageX Administrator’s Guide

Appendix

D

Using StorageX for Application Transformation

The StorageX Application Transform API allows application developers to create their own custom integrations into the StorageX environment to transform file data into object storage.

For detailed information about specific API calls, see the StorageX API Guide.

ATTENTIONThe StorageX API functionality is recommended for use only by advanced users who are knowledgeable about the product.

In this appendix•StorageX Application Transformation requirements. . . . . . . . . . . . . . . . . . 467

•Configuring StorageX for Application Transformation. . . . . . . . . . . . . . . . . 467

•Using the API for Application Transformation . . . . . . . . . . . . . . . . . . . . . . . 468

StorageX Application Transformation requirementsIn order to use the StorageX Application Transform API, you must ensure that your StorageX environment meets the following requirements:

• StorageX role-based access control (RBAC) must be enabled.

• A trusted certificate must be installed on the StorageX server, and StorageX must be configured to use the certificate.

Configuring StorageX for Application TransformationThis section provides information about configuring StorageX and your environment to enable use of the Application Transform API, and includes the following topics:

• “Configuring object endpoints and universal data engines for API usage” on page 467

• “Configuring Application Transform Profiles” on page 468

Configuring object endpoints and universal data engines for API usageBefore you can use Application Transform to transfer your file-based application data into object storage, you will first need to add your object endpoints to Storage Resources. For information about adding object storage resources to Storage Resources, see “Adding storage resources” on page 80.

467

Page 486: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using the API for Application TransformationD

You must also deploy StorageX universal data engines in your environment with read and write access permissions to both the source file system and the target object endpoint. For more information on deploying universal data engines, see “Managing universal data engines” on page 123.

Configuring Application Transform ProfilesIn order to use the StorageX Application Transform API, you must provide the name of a valid Application Transform Profile with any Application Transform API call. Different groups of users in your environment have different permissions and access levels, creating difficulty establishing the correct permissions for file storage and object endpoints.

Instead of granting permissions to each application developer account individually, the Application Transform Profile serves as a single account with permissions to an object endpoint that groups of application developers can use at the same time when writing Application Transform API calls.

To create an Application Transform Profile:

1. Open the StorageX Console.

2. In the left tree, click the Control Panel tab.

3. In the Control Panel view, click the Application Transform Profiles tab.

4. Click Add Profile....

5. In the Application Transform Profile Properties window, complete the following steps:

a. In the Name field, type a name for the Application Transform Profile.

b. In the Description field, type a brief description.

c. Select the universal data engine or universal data engine group to use for the Application Transform.

d. Select the object storage endpoint to use for the Application Transform.

e. Click OK.

Once you have saved the Application Transform Profile, you can distribute the profile information to your application developers for them to use as their designated account for running Application Transform API calls.

Using the API for Application TransformationAfter creating one or more Application Transform Profiles, as necessary for your environment, you can create scripts using StorageX Application Transform API calls and run those scripts to transform your application data from file format to object storage.

To use the API to create and run a file-to-object transform job, you must include all required parameters:

• Id

• Link

• JobName

• ProfileName

468 StorageX Administrator’s Guide

Page 487: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using the API for Application Transformation D

• JobItems > ObjectId

• JobItems > FilePath

• BucketName

• KeyingScheme

For detailed information about specific Application Transform API calls, see the StorageX API Guide.

NOTES:

• When you create and run a file-to-object transform job using the API, StorageX does not automatically delete the specified source files.

• If you include duplicate entries in the JobItems parameter list for a transform job, StorageX transforms all specified source files into objects, even those that are duplicated. StorageX does not check for duplicate entries when using the API.

StorageX Administrator’s Guide 469

Page 488: Data Dynamics StorageX Administrator’s Guide · StorageX Administrator’s Guide i ... command names in the narrative portions of this guide are ... Enabling platform API access

Using the API for Application TransformationD

470 StorageX Administrator’s Guide


Top Related