Administrator s Guide. StorageX 7.6

Transcription

1 Administrator s Guide StorageX 7.6 May 2015

2 Copyright 2015 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 102 Teaneck, NJ Tel: Fax: info@datdyn.com 2StorageX Administrator s Guide

3 About This Document This document is a procedural guide written to help storage area network (SAN) 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 formatting The narrative-text formatting conventions that are used in this document are as follows: bold text italic text code text Identifies command names Identifies the names of user-manipulated GUI elements Identifies keywords and operands Identifies text to enter at the GUI or CLI Provides emphasis Identifies variables Identifies paths and Internet addresses Identifies document titles Identifies CLI output Identifies syntax examples 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. NOTE A Note provides a tip, guidance or advice, emphasizes important information, or provides a reference to related information. StorageX Administrator s Guide i

4 ATTENTION An 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: documentation@datdyn.com 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 to support@datdyn.com or go to the Data Dynamics, Inc. Support site at Include the following information in your or support request: Product name, version, and build number NOTE To 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

5 About This Document Documentation conventions i Documentation feedback ii Contacting Support ii Chapter 1 Planning and Installing StorageX In this chapter Checklist: Planning and installing StorageX Understanding the StorageX architecture and components Understanding the StorageX server Understanding the StorageX database Understanding the StorageX Console Understanding StorageX replication agents StorageX requirements StorageX server computer requirements StorageX server service account requirements StorageX Console computer requirements StorageX database computer requirements Replication agent computer requirements Replication agent service account requirements File storage resource requirements Feature-specific requirements Network port requirements StorageX network connectivity and policy processing considerations26 StorageX installation and configuration worksheet Installing StorageX components Installation account requirements Installing the StorageX server and StorageX Console Installing Windows replication agents Installing and configuring Linux replication agents Opening the StorageX Console Working with license keys Understanding StorageX licensing Adding license keys and specifying license notifications Viewing product version and license key information Obtaining license keys Updating license keys Verifying license keys Configuring StorageX access control Understanding role-based access control Understanding StorageX roles Configuring role-based access control Viewing assigned roles StorageX Administrator s Guide iii

6 Configuring StorageX auditing Understanding StorageX auditing Understanding StorageX audit events Configuring auditing settings Viewing StorageX audit events Backing up the StorageX database Stopping and restarting the StorageX server Upgrading StorageX Upgrading StorageX servers and databases Upgrading StorageX Console computers Upgrading StorageX replication agents Uninstalling StorageX Checklist: Uninstalling StorageX components Uninstalling replication agents Removing replication agents from the StorageX database Uninstalling the StorageX server and StorageX Consoles Deleting the StorageX database Deleting StorageX log files, cache files, and remaining program folders Chapter 2 Configuring and Viewing File Storage Resources In this chapter Checklist: Configuring file storage resources and StorageX Understanding the Storage Resources view Understanding the My Resources folder Understanding custom folders in the Storage Resources view 62 Creating custom folders in the Storage Resources view Deleting custom folders in the Storage Resources view Understanding file storage resource validation checks Verifying file storage resource DNS configuration Adding the StorageX server service account to file storage resources64 Configuring platform API access for file storage resources Enabling platform API access on Data ONTAP file storage resources 65 Enabling platform API access on VNX OE for File file storage resources Enabling platform API access on OneFS file storage resources68 Configuring default credentials for file storage resources Configuring default Data ONTAP credentials Configuring default VNX OE for File credentials Configuring default OneFS credentials Configuring default SSH shell credentials Adding file storage resources Adding and configuring file storage resources individually Creating file storage resource import lists Importing lists of file storage resources iv StorageX Administrator s Guide

7 Configuring file storage resources in My Resources Configuring credentials for specific file storage resources Configuring credentials for specific Data ONTAP file storage resources Configuring credentials for specific VNX OE for File file storage resources Configuring credentials for specific OneFS file storage resources93 Configuring SSH shell credentials for specific file storage resources 94 Configuring virtual file storage resources Specifying hosting properties for Data ONTAP vfilers, Vservers, and SVMs Specifying hosting properties for VNX OE for File Data Movers 97 Configuring the SNMP community name for file storage resources98 Configuring NFS credentials Configuring intercluster interfaces for NetApp Cluster Mode file storage resources Verifying file storage resources Specifying replication agent settings on file storage resources..101 Specifying replication agent proxy computers for file storage resources Specifying replication agent data transfer rate limits Viewing file storage resource information Viewing file storage resource properties Refreshing displayed file storage resource information Specifying file storage resource platform type Removing file storage resources from My Resources Exporting file storage resource import lists Managing replication agents Specifying default service account credentials for Windows replication agents Manually deploying Windows replication agents Enabling deployment of Windows replication agents on Windows file storage resources Specifying default replication agent proxy computers Viewing replication agent status Stopping, starting, pausing, and resuming Windows replication agents Changing deployed Windows replication agent service account credentials Creating and managing replication agent groups Changing the replication agent listening port Changing StorageX server service account credentials Working with StorageX events Viewing StorageX events Filtering events StorageX Administrator s Guide v

8 Chapter 3 Chapter 4 Provisioning File Storage Resources In this chapter Understanding provisioning Provisioning operating system requirements Creating and managing CIFS shared folders Understanding the CIFS protocol Creating CIFS shared folders Viewing CIFS shared folder properties Viewing CIFS shared folder contents Cloning CIFS shared folders Creating and managing NFS exports Understanding the NFS protocol Creating NFS exports Viewing NFS export properties Cloning NFS exports Creating and managing Data ONTAP volumes and qtrees Creating volumes on Data ONTAP file storage resources Creating qtrees on Data ONTAP file storage resources Viewing qtree properties on Data ONTAP file storage resources130 Sharing qtrees on Data ONTAP file storage resources Deleting qtrees on Data ONTAP file storage resources Creating and managing Data ONTAP SnapMirrors Understanding SnapMirrors Creating SnapMirrors on Data ONTAP file storage resources.132 Initializing SnapMirrors on Data ONTAP file storage resources133 Quiescing and resuming SnapMirrors on Data ONTAP file storage resources Updating SnapMirrors on Data ONTAP file storage resources134 Interrupting SnapMirror data transfers on Data ONTAP file storage resources Breaking SnapMirror relationships on Data ONTAP file storage resources Resyncing SnapMirrors on Data ONTAP file storage resources135 Deleting SnapMirrors from StorageX for Data ONTAP file storage resources Creating and Managing DFS Namespaces In this chapter Checklist: DFS namespace planning and implementation Understanding DFS namespaces DFS Namespace components How DFS namespaces work Understanding DFS namespace size limits and recommendations 141 Understanding DFS namespace types vi StorageX Administrator s Guide

9 DFS namespace operating system requirements DFS namespace server operating system requirements DFS namespace client computer operating system requirements146 Understanding DFS namespace validation checks Creating and configuring DFS namespaces Domain-based DFS namespace configuration requirements.147 Creating domain-based DFS namespaces Stand-alone DFS namespace configuration requirements Creating stand-alone DFS namespaces Understanding consolidation DFS namespaces Consolidation DFS namespace configuration requirements.153 Creating consolidation DFS namespaces Configuring consolidation DFS namespaces Managing DFS namespaces Viewing DFS namespaces Viewing DFS namespace properties Modifying DFS namespace properties Enabling access-based enumeration for DFS namespaces..159 Delegating management for DFS namespaces Specifying referral settings for DFS namespaces Refreshing DFS namespaces Upgrading DFS namespaces to Windows Server 2008 mode162 Adding DFS namespaces to My Resources Verifying DFS namespaces Removing DFS namespaces from My Resources Deleting DFS namespaces Creating domain-based DFS namespace servers Managing domain-based DFS namespace servers Viewing and modifying domain-based DFS namespace servers167 Enabling and disabling referrals for domain-based DFS namespace servers Overriding referral ordering for domain-based DFS namespace servers Removing domain-based DFS namespace servers Adding DFS links to DFS namespaces StorageX Administrator s Guide vii

10 Managing DFS links Viewing DFS link properties Modifying DFS link properties Specifying referral settings for DFS links Refreshing DFS links Creating folders in DFS namespaces Deleting folders in DFS namespaces Renaming DFS links and DFS namespace folders Converting DFS links to folders Deleting DFS links Viewing DFS link targets Adding additional DFS link targets to DFS links Changing the status of DFS link targets Specifying which users and groups can view specific DFS link targets 184 Enabling or disabling referrals for DFS link targets Overriding referral ordering for DFS link targets Deleting DFS link targets Searching for DFS objects Converting stand-alone namespaces to domain-based namespaces191 Synchronizing DFS namespaces Creating Namespace Availability policies Running Namespace Availability policies immediately Adding or Removing Namespaces in a Namespace Availability policy 196 Scheduling Namespace Availability policies Backing up and restoring DFS namespaces Creating Namespace Backup policies Manually backing up namespaces Browsing namespace backups Restoring namespace backups Chapter 5 Creating and Managing Data Movement Policies In this chapter Checklist: Creating and managing Data Movement policies Understanding Data Movement templates and policies Understanding Phased Migration and Archival Migration templates 205 Understanding Phased Migration policies Understanding Archival Migration policies Data Movement policy protocol requirements viii StorageX Administrator s Guide

11 Data Movement policy planning considerations General data transfer planning considerations CIFS-specific data transfer planning considerations How StorageX manages data access in CIFS environments with DFS namespaces NFS-specific data transfer planning considerations How StorageX manages data access in NFS environments with automount map files NDMP-specific data transfer requirements and configuration221 Distributing file data transfer workloads using replication agent groups Creating and managing templates Creating new templates Copying an existing template Viewing and modifying template properties Renaming templates Deleting templates Creating Phased Migration policies Creating new Phased Migration policies Copying existing Phased Migration policies Configuring Phased Migration policies to use native replication233 Running Phased Migration policies immediately Scheduling Phased Migration policies Canceling Phased Migration policies Restarting Phased Migration policies Verifying Phased Migration policies completed successfully Managing Phased Migration policies Modifying Phased Migration policy properties Configuring replication options for Phased Migration policies247 Specifying migration options for Phased Migration policies..248 Working with policy file and folder inclusion and exclusion filters248 Running batch files with Phased Migration policies Assigning replication agents or replication agent groups to Phased Migration policies Changing the template specified for a Phased Migration policy256 Viewing and managing default settings for Phased Migration policies 257 Renaming Phased Migration policies Creating custom folders for Data Movement Phased Migration policies Viewing Phased Migration policies scheduled to run in the future259 Deleting Phased Migration policies Creating Archival Migration policies Creating new Archival Migration policies Copying an existing Archival Migration policy Running Archival Migration policies immediately Scheduling Archival Migration policies StorageX Administrator s Guide ix

12 Canceling Archival Migration policies Restarting Archival Migration policies Verifying Archival Migration policies completed successfully Managing Archival Migration policies Modifying Archival Migration policy properties Immediately scanning for folders to migrate Scheduling scanning for folders to migrate Viewing and managing migration candidates Specifying migration criteria for Archival Migration policies Specifying folder exclusion and inclusion filters for Archival Migration policies Creating batch files for Archival Migration policies Running batch files with Archival Migration policies Specifying post-scanning options for Archival Migration policies277 Managing Archival Migration template inheritance Managing default settings in Archival Migration policies Renaming Archival Migration policies Organizing Archival Migration policies Viewing Archival Migration policies scheduled to run in the future 279 Deleting Archival Migration policies Using batch files with Phased Migration and Archival Migration policies 280 Using batch files with Phased Migration policies Using batch files with Archival Migration policies Phased Migration and Archival Migration batch file requirements281 Chapter 6 Creating and Managing Migration Projects In this chapter Checklist: Migrating data using Migration Projects Understanding Migration Projects Understanding Migration Project sources and destinations..287 Understanding Migration Project designs Understanding Migration Project Phased Migration templates292 Understanding Migration Project Phased Migration policies.292 Understanding using SnapMirror replication for Migration Projects 294 Migration Project operating system requirements Identifying Migration Project sources, destinations, and credentials296 Creating Migration Projects Adding sources and destinations to Migration Projects Understanding Migration Project views Using Migration Project Summary views Using Migration Project Source and Destination Summary views300 Using Migration Project Source and Destination Detail views 301 Generating Data ONTAP SnapMirror reports x StorageX Administrator s Guide

13 Creating Migration Project designs Migration Project design planning considerations Creating Like-to-Like Migration Project designs Creating Advanced Migration Project designs Editing and specifying advanced options for Migration Project designs 316 Exporting Migration Project designs Validating Migration Project designs Understanding Migration Project design validation rules Deploying replication agents for migrations using the NFS protocol324 Modifying Migration Project Phased Migration template properties325 Creating custom folders for Migration Project Phased Migration policies 326 Executing Migration Project designs Viewing and modifying Migration Project Phased Migration policies328 Rolling back when a Migration Project design execution fails Managing Migration Projects and Migration Project designs Modifying Migration Project properties Renaming Migration Projects Deleting Migration Projects Deleting Migration Project designs Chapter 7 Creating and Managing Disaster Recovery and Replication Policies In this chapter Checklist: Creating and managing Disaster Recovery and Replication policies Understanding Disaster Recovery policies Understanding Disaster Recovery policy functionality CIFS-based resource monitoring NetApp-based resource monitoring DFS namespace link monitoring Understanding replication and replication topology Understanding Disaster Recovery policy failover Disaster Recovery failover options Understanding failover topology Understanding failover in NetApp-based resource monitoring341 Disaster Recovery policy planning considerations Account requirements for Disaster Recovery policies Requirements for Disaster Recovery policy links Creating Disaster Recovery policies Scheduling Disaster Recovery policies Manually failing over Disaster Recovery policies Verifying Disaster Recovery policies completed successfully StorageX Administrator s Guide xi

14 Manually failing back Disaster Recovery policies Resynchronizing SnapMirrors for Disaster Recovery failback Managing Disaster Recovery policies Modifying Disaster Recovery policy properties Modifying the failover topology for a monitored link Adding DFS links to Disaster Recovery policies Configuring Disaster Recovery policies to monitor master links356 Removing DFS links from Disaster Recovery policies Deleting Disaster Recovery policies Understanding Disaster Recovery discovery Adding DFS search paths to Disaster Recovery policies Manually discovering new links and qtrees Adding discovered links or qtrees to Disaster Recovery policies359 Understanding Replication policies Replication policy planning considerations Replication policy requirements Creating Replication policies Running Replication immediately Scheduling Replication policies Verifying Replication policies completed successfully Managing Replication policies Modifying Replication policy properties Modifying the replication topology Adding targets to Replication policies Removing targets from Replication policies Deleting Replication policies Using batch files with Disaster Recovery or Replication policies..370 Using batch files with Disaster Recovery policies Using batch files with Replication policies Disaster Recovery and Replication batch file requirements Creating batch files for Disaster Recovery policies Running batch files with Disaster Recovery and Replication policies 376 Chapter 8 Working with Reports In this chapter Understanding reports Understanding Agent reports Understanding Migration Project Reports Understanding Namespace Policy reports Understanding Phased Migration Policy reports Understanding Storage Resource reports Creating reports Viewing reports xii StorageX Administrator s Guide

15 Customizing reports Adding, removing, reordering, and resizing report columns..384 Sorting data in reports Grouping and ungrouping data in reports Filtering records in reports Searching for items in reports Exporting reports Appendix A Configuring StorageX to Use SSH Shell Credentials In this appendix SSH requirements Checklist: Configuring SSH shell credentials for StorageX Generating an SSH public/private key pair Copying public keys to Linux and VNX OE for File file storage resources and NFS clients Using SSH shell credentials with StorageX Converting PuTTY-generated SSH private keys to OpenSSH-format private keys StorageX Administrator s Guide xiii

16 xiv StorageX Administrator s Guide

17 Planning and Installing StorageX Chapter 1 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. In this chapter Checklist: Planning and installing StorageX Understanding the StorageX architecture and components StorageX requirements StorageX network connectivity and policy processing considerations StorageX installation and configuration worksheet Installing StorageX components Opening the StorageX Console Working with license keys Configuring StorageX access control Configuring StorageX auditing Backing up the StorageX database Stopping and restarting the StorageX server Upgrading StorageX Uninstalling StorageX StorageX Administrator s Guide 1

18 1 Checklist: Planning and installing StorageX Checklist: Planning and installing StorageX Use 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 Identify the computers that will host StorageX components and verify StorageX readiness. For more information, see StorageX installation and configuration worksheet on page Identify the file storage resources that you will manage with StorageX. For more information, see StorageX installation and configuration worksheet on page 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 file storage resources using a DFS namespace Types of client computers used by these users Applications in your environment that access file data on file storage resources that you want to include in the DFS namespace For more information, see Checklist: DFS namespace planning and implementation on page 138 and StorageX installation and configuration worksheet on page Review the existing network connectivity in your file 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 Install StorageX components. For more information, see Installing StorageX components on page Add file storage resources to the My Resources folder in the StorageX Storage Resources view and then configure file storage resources as needed in the Storage Resources view. For more information, see Understanding the Storage Resources view on page 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 policies If 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 389, Configuring default SSH shell credentials on page 71, and Configuring SSH shell credentials for specific file storage resources on page If you have file storage resources on which you do not want to install replication agents, specify replication agent proxy computers for the file storage resources. For more information, see Specifying replication agent proxy computers for file storage resources on page 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 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 StorageX Administrator s Guide

19 Understanding the StorageX architecture and components 1 TABLE 1 Task StorageX planning and installing checklist 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 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 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 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 Use StorageX reports as needed to help you better understand your file 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 379. Understanding the StorageX architecture and components StorageX uses a distributed client/server architecture. The StorageX architecture helps you efficiently and centrally manage distributed, heterogeneous file storage resources. The following figure shows StorageX architectural components implemented in a sample file storage environment. StorageX Administrator s Guide 3

20 1 Understanding the StorageX architecture and components The following descriptions provide additional detail about each item in the previous figure: StorageX Console computers The 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 file storage resources you want to manage using StorageX Provision heterogeneous file 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 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. 4 StorageX Administrator s Guide

21 Understanding the StorageX architecture and components 1 StorageX server, database, and replication agent computer The StorageX server communicates with the StorageX database, replication agents, DFS namespace host computers, and the file storage resources in your environment. The StorageX server performs the following tasks: Provides summary information about file storage resources managed by StorageX in your environment Maintains information about your file storage environment and StorageX configuration Runs Phased Migration, Archival Migration, Disaster Recovery, Replication, Namespace Backup, and Namespace Availability policies Validates and executes Migration Projects 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 replication agent on the StorageX server computer. StorageX can then use this replication agent as needed to transfer file data when running policies. Windows and Linux replication agent proxy computers StorageX Windows and Linux replication agent proxy computers are computers on which you deploy or install a replication agent to transfer data from a storage resource. Windows and Linux replication agents transfer file data when StorageX policies run. If you have file storage resources on which you cannot deploy a Windows replication agent or install a Linux replication agent, such as Data ONTAP, VNX OE for File, or OneFS file storage resources, StorageX allows you to deploy the replication agent to a proxy computer. When you deploy a replication agent to a proxy computer, StorageX uses the replication agent on the proxy computer to migrate and replicate file data when running policies. DFS namespace server DFS 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 file storage resources. StorageX enhances and extends DFS namespace technology by allowing you to quickly and easily create and manage new DFS namespaces in your file 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 resources Windows 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 replication agent on the resources. StorageX then uses the Windows replication agent to migrate or replicate file data. For more information, see Understanding standard replication agent usage and data transfer on page 9. StorageX Administrator s Guide 5

22 1 Understanding the StorageX architecture and components You may not always want to deploy a Windows replication agent on a Windows file storage resource. If you have a Windows file storage resource on which you do not want to deploy a Windows replication agent, you can configure policies to use the Windows replication agent installed by default on the StorageX server. You can also choose to have a Windows replication agent installed on a proxy computer migrate or replicate CIFS file data. For more information, see Understanding StorageX replication agent proxy computers on page 9. Linux file storage resources Linux 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 replication agent installed by default on the StorageX server or you can manually install and configure a Linux replication agent on the destination or source Linux file storage resource or on a Linux replication agent proxy computer and use this Linux replication agent to transfer file data. For more information, see Understanding standard replication agent usage and data transfer on page 9. Data ONTAP, VNX OE for File, and OneFS file storage resources Data 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. 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 replication agents onto the Data ONTAP, VNX OE for File, or OneFS file storage resources. Instead, StorageX uses either the replication agent installed by default on the StorageX server computer or replication agents installed on replication agent 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 replication agent installed on a Windows replication agent 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 replication agent installed on a Linux replication agent 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 replication agent installed on a replication agent proxy computer, you specify an appropriate replication agent 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 replication agent 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 computers Client computers using the CIFS or NFS protocol can seamlessly and transparently access highly available CIFS and NFS file data. For additional information about each of the components in the StorageX architecture, see the following sections: Understanding the StorageX server on page 7 Understanding the StorageX database on page 7 6 StorageX Administrator s Guide

23 Understanding the StorageX architecture and components 1 Understanding the StorageX Console on page 7 Understanding StorageX replication agents on page 8 Understanding the StorageX server The StorageX server communicates with the StorageX database, replication agents, and the file storage resources in your environment. The StorageX server performs the following tasks: Maintains information about your file storage environment and configuration Runs Phased Migration, Archival Migration, Disaster Recovery, Replication, Namespace Backup, and Namespace Availability policies NOTE If 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 file 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 13 and Installing the StorageX server and StorageX Console on page 28. Understanding the StorageX database The StorageX database is a Microsoft SQL Server database. The StorageX server uses the StorageX database to store the following information: Configuration information for file storage resources managed by StorageX Configured StorageX replication agents 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 17. Understanding the StorageX Console The StorageX Console is the StorageX user interface and communicates with the StorageX server. Use the StorageX Console to perform the following tasks: Add file storage resources to the StorageX environment Configure and provision file storage resources Create and manage DFS namespaces StorageX Administrator s Guide 7

24 1 Understanding the StorageX architecture and components Create and manage Phased Migration, Archival Migration, Disaster Recovery, Replication, Namespace Availability, and Namespace Backup policies Create and manage Migration Projects Manage the StorageX server Manage StorageX replication agents Multiple StorageX Consoles can connect to the 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 16 and Installing the StorageX server and StorageX Console on page 28. Understanding StorageX replication agents StorageX replication agents transfer file data when StorageX policies run. StorageX provides both Windows and Linux replication agents. Windows replication agents are installed on Windows file storage resources, transfer file data using the CIFS protocol, and are Windows services. Linux replication agents 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, StorageX uses Windows and Linux replication agents installed on replication agent proxy computers as needed to transfer file data stored on these types of file storage resources. For more information about how StorageX uses replications agents, see the following topics: Understanding StorageX replication agent proxy computers on page 9 Understanding standard replication agent usage and data transfer on page 9 Understanding replication agent deployment without differential replication on page 10 Understanding replication agent deployment with differential replication enabled on page 11 Windows replication agent computer requirements on page 20 Linux replication agent computer requirements on page 20 Installing Windows replication agents on page 32 Installing and configuring Linux replication agents on page 33 Managing replication agents on page StorageX Administrator s Guide

25 Understanding the StorageX architecture and components 1 Understanding StorageX replication agent proxy computers StorageX allows you to specify a replication agent proxy computer for file storage resources and StorageX servers as needed. A replication agent proxy computer is a computer other than the source file storage resource, the destination file storage resource, or the StorageX server computer where a StorageX replication agent is installed. StorageX uses replication agents deployed on replication agent proxy computers to transfer data when a replication agent cannot be deployed on the source or destination file storage resource. Configure replication agent proxy computers for file storage resources in the following situations: When you cannot deploy replication agents on destination or source file storage resources, and you do not want to use the replication agent installed on the StorageX server computer to transfer data. For example, you may need to configure replication agent 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 file storage resources and you cannot deploy a replication agent to the destination or source file storage resources. For example, assume you have a StorageX server computer with a replication agent 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 replication agent. In this scenario, install a replication agent on a proxy computer on the same LAN as the source and destination file storage resources. This allows you to use a replication agent on the same LAN as the source and destination file storage resources and avoids transferring data across the WAN when StorageX policies run. Understanding standard replication agent usage and data transfer StorageX uses Windows and Linux replication agents to transfer file data when running StorageX policies. If you have Windows file storage resources as sources or destinations, StorageX can deploy Windows replication agents 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 replication agents 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 replication agent to be deployed to this host check box. For more information, see Enabling deployment of Windows replication agents on Windows file storage resources on page 109. NOTE The Allow replication agent 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. StorageX Administrator s Guide 9

26 1 Understanding the StorageX architecture and components If you have Linux file storage resources as source or destinations, you can manually install a Linux replication agent on either the destination or source file storage resource, or you can specify a Linux replication agent proxy computer for StorageX to use to transfer file data. For more information about manually installing Linux replication agents, see Installing and configuring Linux replication agents on page 33. For more information about specifying replication agent proxy computers for Linux file storage resources, see Specifying replication agent proxy computers for file storage resources on page 101. If you have Data ONTAP, VNX OE for File, or OneFS file storage resources, StorageX cannot deploy Windows replication agents automatically to these file storage resources. You also cannot manually install a Linux replication agent on these types of file storage resources. For these types of file storage resources, you must specify replication agent proxy computers as needed. If you are transferring file data using the CIFS protocol, specify a Windows replication agent proxy computer for the destination or source as needed. If you are transferring file data using the NFS protocol, specify a Linux replication agent proxy computer for the destination or source as needed. Understanding replication agent deployment without differential replication StorageX determines which replication agent to use to transfer file data using the following rules: 1. StorageX first tries to determine if it can use a replication agent installed on the destination file storage resource. The destination file storage resource is the file storage resource where the file data will be transfered. 2. If StorageX can use a replication agent on the destination file storage resource, the replication agent on the destination file storage resource pulls data from the source file storage resource to the destination file storage resource. The source file storage resource is the file storage resource where the file data currently resides. 3. If StorageX cannot use a replication agent on the destination file storage resource, StorageX checks to see if it can use a replication agent on the source file storage resource. 4. If StorageX can use a replication agent on the source file storage resource, the replication agent on the source file storage resource pushes data from the source file storage resource to the destination file storage resource. 5. If StorageX cannot use a replication agent on the source file storage resource, StorageX checks to see if a replication agent proxy computer has been specified for the destination file storage resource. 6. If a replication agent proxy computer has been specified for the destination file storage resource, StorageX uses the replication agent on the replication agent proxy computer specified for the destination file storage resource to pull data from the source file storage resource to the destination file storage resource. 7. If StorageX cannot use a replication agent proxy computer specified for the destination file storage resource, StorageX checks to see if a replication agent proxy computer has been specified for the source file storage resource. 8. If a replication agent proxy computer has been specified for the source file storage resource, StorageX uses the replication agent on the replication agent proxy computer specified for the source file storage resource to pull data from the source file storage resource to the destination file storage resource. 10 StorageX Administrator s Guide

27 Understanding the StorageX architecture and components 1 9. If StorageX cannot use a replication agent on the destination file storage resource, a replication agent on the source file storage resource, a replication agent proxy computer specified for the destination file storage resource, or a replication agent proxy computer specified for the source file storage resource, StorageX uses the replication agent StorageX installs by default on the StorageX server computer to transfer file data. 10. If StorageX can use the replication agent on the StorageX server computer, the replication agent on the StorageX server computer transfers data from the source file storage resource to the destination file storage resource. 11. If StorageX cannot use the replication agent on the StorageX server computer, StorageX checks to see if a replication agent proxy computer has been specified for the StorageX server computer. 12. If a replication agent proxy computer has been specified for the StorageX server computer, StorageX uses the replication agent on the replication agent 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 file storage resources are on a different network segment. In this scenario, you want to use a replication agent proxy computer on the same network segment as your file storage resources. You do not want to use the replication agent on the StorageX server computer to transfer file data. In this scenario, you specify a replication agent proxy computer for the StorageX server computer. When you do this, StorageX will use the replication agent on the replication agent proxy computer you specified for the StorageX server computer to transfer the file data. StorageX will not use the replication agent installed on the StorageX server computer by default to transfer file data. 13. If a replication agent proxy computer has not been specified for the StorageX server computer, the Phased Migration policy fails because a replication agent is not available for StorageX to use to transfer data. This standard process is how StorageX typically uses replication agents to transfer data when you run Phased Migration policies. However, the process StorageX uses to transfer data using replication agents is different when you run Phased Migration policies with differential replication enabled. For more information, see Understanding replication agent deployment with differential replication enabled on page 11. Understanding replication agent 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 replication agents 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, image files, such as.jpg files, and encrypted 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 replication agents to transfer file data. StorageX Administrator s Guide 11

28 1 Understanding the StorageX architecture and components If you specify that you want a Phased Migration policy to replicate data using differential replication, both the source and destination file storage resources must have replication agents installed on them, or you must specify replication agent proxy computers for one or both of the file storage resources. StorageX determines which replication agent to use to transfer file data using the following rules: 1. StorageX first tries to determine if it can use a replication agent installed on the destination file storage resource. The destination file storage resource is the file storage resource where the file data will be transfered. 2. If StorageX can use a replication agent on the destination file storage resource, the replication agent on the destination file storage resource pulls data from the source file storage resource to the destination file storage resource. The source file storage resource is the file storage resource where the file data currently resides. 3. If StorageX cannot use a replication agent on the destination file storage resource, StorageX checks to see if a replication agent proxy computer has been specified for the destination file storage resource. 4. If a replication agent proxy computer has been specified for the destination file storage resource, StorageX uses the replication agent on the replication agent proxy computer specified for the destination file storage resource to pull data from the source file storage resource to the destination file storage resource. 5. If StorageX cannot use a replication agent on either the destination file storage resource or on a replication agent proxy computer specified for the destination file storage resource, StorageX checks to see if it can use a replication agent on the source file storage resource. 6. If StorageX can use a replication agent on the source file storage resource, the replication agent on the source file storage resource pushes data from the source file storage resource to the destination file storage resource. 7. If StorageX cannot use a replication agent on the source file storage resource, StorageX checks to see if a replication agent proxy computer has been specified for the source file storage resource. 8. If a replication agent proxy computer has been specified for the source file storage resource, StorageX uses the replication agent on the replication agent proxy computer specified for the source file storage resource to pull data from the source file storage resource to the destination file storage resource. 9. If StorageX cannot use a replication agent on the destination file storage resource, a replication agent proxy computer specified for the destination file storage resource, a replication agent on the source file storage resource, or a replication agent proxy computer specified for the source file storage resource, StorageX uses the replication agent StorageX installs by default on the StorageX server computer to transfer file data. 10. If StorageX can use the replication agent on the StorageX server computer, the replication agent on the StorageX server computer transfers data from the source file storage resource to the destination file storage resource. 11. If StorageX cannot use the replication agent on the StorageX server computer, StorageX checks to see if a replication agent proxy computer has been specified for the StorageX server computer. 12. If a replication agent proxy computer has been specified for the StorageX server computer, StorageX uses the replication agent on the replication agent proxy computer specified for the StorageX server to transfer data from the source to the destination. 12 StorageX Administrator s Guide

29 StorageX requirements 1 For example, assume that your StorageX server computer is on one network segment, but all of your file storage resources are on a different network segment. In this scenario, you want to use a replication agent proxy computer on the same network segment as your file storage resources. You do not want to use the replication agent on the StorageX server computer to transfer file data. In this scenario, you specify a replication agent proxy computer for the StorageX server computer. When you do this, StorageX will use the replication agent on the replication agent proxy computer you specified for the StorageX server computer to transfer the file data. StorageX will not use the replication agent installed on the StorageX server computer by default to transfer file data. 13. If a replication agent proxy computer has not been specified for the StorageX server computer, the Phased Migration policy fails because a replication agent 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 247. For more information about specifying replication agent proxy computers, see Specifying default replication agent proxy computers on page 109. StorageX requirements This section provides information about requirements for the following components in a StorageX environment: StorageX server computer requirements on page 13 StorageX server service account requirements on page 15 StorageX Console computer requirements on page 16 StorageX database computer requirements on page 17 Replication agent computer requirements on page 19 Replication agent service account requirements on page 21 File storage resource requirements on page 23 Feature-specific requirements on page 24 Network port requirements on page 24 Ensure each component meets the hardware, operating system, software, and configuration requirements for the component before you install it. StorageX server computer requirements Ensure 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: StorageX Administrator s Guide 13

30 1 StorageX requirements 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 7 and StorageX database computer requirements on page 17. The following table lists StorageX server requirements. For more information about the StorageX server, see Understanding the StorageX server on page 7. TABLE 2 Component StorageX server requirements 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 space If 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 16 and StorageX database computer requirements on page 17. Operating System One of the following operating systems with the latest service pack: Microsoft Windows Server 2008 R2 Standard, Enterprise, or Datacenter Edition Microsoft Windows Server 2012 Essentials, Standard, or Datacenter Edition Microsoft Windows Server 2012 R2 Essentials, Standard, or Datacenter Edition 14 StorageX Administrator s Guide

31 StorageX requirements 1 TABLE 2 Component StorageX server requirements Minimum Requirements Additional Software Microsoft.NET Framework 4.5 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. 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, you must install an SSH client on each computer where the StorageX server is installed. 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 389. If you install the StorageX server on a computer running the Microsoft Windows Server 2008 or Microsoft Windows Server 2012 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 2008 R2, 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. StorageX server service account requirements You 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 folder, shares and exports Manage permissions during file data migration Execute backup procedures If you use StorageX for DFS namespace management, management of domain-based DFS namespaces. 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 126. StorageX Administrator s Guide 15

32 1 StorageX requirements 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: 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 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 requirements You can install the StorageX Console in the following locations: On the same computer where you install the StorageX server On the desktop computers of the storage administrators responsible for managing file storage resources using StorageX On a desktop computer or server computer convenient to the file storage resources StorageX manages 16 StorageX Administrator s Guide

33 StorageX requirements 1 The following table lists StorageX Console requirements. For more information about the StorageX Console, see Understanding the StorageX Console on page 7. TABLE 3 Component StorageX Console requirements 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 2processor 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 2008 R2 Standard, Enterprise, or Datacenter Edition Microsoft Windows Server 2012 Essentials, Standard, or Datacenter Edition Microsoft Windows Server 2012 R2 Essentials, Standard, or Datacenter Edition Microsoft Windows 7 Pro, Enterprise, or Ultimate Edition Microsoft Windows 8 Pro or Enterprise Edition Microsoft Windows 8.1 Pro or Enterprise Edition Additional Software Microsoft.NET Framework 4.5 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. 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. Typically, you will run the StorageX Console using a user account with permissions to administer file 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 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 requirements The 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. StorageX Administrator s Guide 17

34 1 StorageX requirements 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. You can use either a full version of Microsoft SQL Server or Microsoft SQL Server Express for StorageX product evaluations. A download of Microsoft SQL Server Express 2012 is available from the Microsoft Download Center at If you want to use only the Data Movement features of StorageX, you can also use Microsoft SQL Server Express for StorageX production installations. If you want to use any other StorageX features, including Disaster Recovery, Replication, or Namespace Management, you must use a full version of Microsoft SQL Server for StorageX product installations. The following table lists the detailed database requirements for StorageX. For more information about the StorageX database, see Understanding the StorageX database on page 7. TABLE 4 Component StorageX database requirements Minimum Requirements Hardware 2 GHz or faster processor 4 GB of memory Consult 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 2 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 2 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. 18 StorageX Administrator s Guide

35 StorageX requirements 1 TABLE 4 Component StorageX database requirements Minimum Requirements Additional Software Additional Configuration One of the following versions of Microsoft SQL Server with the latest service pack: Microsoft SQL Server 2008 R2 Express, Standard, Enterprise, or Datacenter Edition Microsoft SQL Server 2012 Express, Standard, Enterprise, or Datacenter Edition Data Dynamics, Inc. provides the following recommendations, depending on how you want to install the product: Data Movement only: You should only use Microsoft SQL Server Express for installations where you do not plan to use Disaster Recovery, Replication, or Namespace Management functionality. 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 Microsoft SQL Server Standard, Enterprise, or Datacenter Edition. 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. Replication agent computer requirements StorageX provides Windows and Linux replication agents. StorageX policies use these Windows and Linux replication agents to transfer file data. This following topics in this section provide replication agent computer requirements for Windows and Linux replication agents: Windows replication agent computer requirements on page 20 Linux replication agent computer requirements on page 20 For more information about StorageX replication agents, replication agent service account requirements, and managing replication agents, see Understanding StorageX replication agents on page 8, Replication agent service account requirements on page 21, and Managing replication agents on page 106. StorageX Administrator s Guide 19

36 1 StorageX requirements Windows replication agent computer requirements The following table lists StorageX Windows replication agent computer requirements. For more information about Windows replication agents, see Understanding StorageX replication agents on page 8. TABLE 5 Windows replication agent 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 2008 R2 Standard, Enterprise, or Datacenter Edition Microsoft Windows Server 2012 Essentials, Standard, or Datacenter Edition Microsoft Windows Server 2012 R2 Essentials, Standard, or Datacenter Edition Microsoft Windows 7 Pro, Enterprise, or Ultimate Edition Microsoft Windows 8 Pro or Enterprise Edition Microsoft Windows 8.1 Pro or Enterprise Edition Additional Configuration The StorageX Windows replication agent 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 replication agent. For information on enabling the Remote Registry service, see the Microsoft TechNet Library. When StorageX automatically deploys Windows replication agents, StorageX uses the ADMIN$ share on the file storage resource where the Windows replication agent is installed. When you manually deploy a replication agent in the Control Panel view, you specify the service account credentials you want the Windows replication agent to use. You can use the same service account for the Windows replication agent that you used for the StorageX server or you can specify different service account credentials for the Windows replication agents you manually deploy. For more information about manually deploying a Windows replication agent, see Changing the replication agent listening port on page 113. Linux replication agent computer requirements You can install a Linux replication agent on a computer running Red Hat Enterprise Linux 6 or Red Hat Enterprise Linux 7. NFS must be installed on the source and destination file storage resources in order for the Linux replication agent to access files across the network. NFS does not have to be installed on the computer where the Linux replication agent is installed. 20 StorageX Administrator s Guide

37 StorageX requirements 1 The following table lists StorageX Linux replication agent computer requirements. For more information about Linux replication agents, see Understanding StorageX replication agents on page 8. TABLE 6 Component Linux replication agent computer requirements 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 6 with the following 32-bit packages installed: glibc.i686 libstdc el6.i686 Red Hat Enterprise Linux 7 with the following 32-bit packages installed: glibc.i686 libstdc el7_0.i686 The Linux replication agent is a 32-bit application and requires 32-bit versions of OS system libraries. These libraries are not installed on Red Hat Enterprise Linux 64-bit by default. You must install these 32-bit libraries on the Linux replication agent computer before you can use the Linux replication agent. Replication agent service account requirements StorageX automatically deploys a Windows replication agent on the computer where you install the StorageX server. When StorageX automatically deploys this replication agent, 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 replication agent. After you install the StorageX server, you can continue to use the same service account and service account credentials for the StorageX server and replication agent, or you can change the service account and service account credentials specified for the replication agent. For more information about changing the default replication agent credentials, see Specifying default service account credentials for Windows replication agents on page 106. If you deploy Windows replication agents 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 replication agents deployed by the server. If you do not update the service account credentials on the deployed replication agents, you cannot perform data transfer and replication tasks using the replication agents. For more information about updating the service account credentials for Windows replication agents, see Changing deployed Windows replication agent service account credentials on page 111. If you change the default replication agent credentials for Windows replication agents, you must also update the credentials of any deployed replication agents that use the default credentials. If you do not change the credentials for the deployed replication agents, you cannot perform data transfer and replication tasks using the replication agents. For more information about changing the default replication agent credentials, see Specifying default service account credentials for Windows replication agents on page 106. StorageX Administrator s Guide 21

38 1 StorageX requirements In addition to the Windows replication agent StorageX automatically deploys on the StorageX server computer and the Windows replication agents StorageX can automatically deploy on Windows file storage resources when transferring data, you can also choose to deploy additional Windows replication agents. However, before you deploy additional replication agents, review service account requirements. For more information, see Windows replication agent service account requirements on page 22. Windows replication agent service account requirements In order for StorageX to deploy a Windows replication agent, the replication agent service account specified for the replication agent must have the following permissions on the Windows computer where StorageX deploys the replication agent: 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, management 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 replication agent service account must have Run as Root permission set on all CIFS shares that are destinations in StorageX policies. If the Windows replication agent 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 replication agent 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 replication agent service account has appropriate permissions to perform storage management tasks on remote computers. You should also ensure that the replication agent service account has the permissions listed in the previous paragraph. If you do not make the replication agent service account a member of the Domain Admins group, complete the following tasks: If you are deploying a replication agent to a Windows computer, ensure the replication agent service account has the following permissions on the computer where the replication agent 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 file storage resources also may require the replication agent service account to be a member of both the local Administrators and Backup Operators groups on the Windows computer where the replication agent is installed. If you are using StorageX to manage CIFS file storage resources, add the replication agent service account to the local Administrators group on every CIFS file storage resource managed by StorageX. 22 StorageX Administrator s Guide

39 StorageX requirements 1 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 replication agent 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. Linux replication agent service account requirements In order for StorageX to manage a Linux replication agent, the StorageX server service account must be able to run as root on the Linux computer where you install the Linux replication agent. File storage resource requirements StorageX 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 389 Configuring default SSH shell credentials on page 71 Configuring SSH shell credentials for specific file storage resources on page 94 SNMP settings. For more information, see Configuring the SNMP community name for file storage resources on page 98. NFS credentials. For more information, see Configuring NFS credentials on page 98. Replication agent proxy computers. For more information, see Specifying replication agent proxy computers for file storage resources on page 101. 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 217 and How StorageX manages data access in NFS environments with automount map files on page 220. StorageX Administrator s Guide 23

40 1 StorageX requirements Feature-specific requirements In 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. TABLE 7 StorageX Feature Feature-specific requirements For more information... Provisioning file storage resources in the Storage Resources view Creating and managing DFS namespaces in the Storage Resources view Migrating file data from source to destination CIFS shared folders or NFS exports in the Data Movement view 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 Configuring your disaster recovery plan and managing Disaster Recovery and Replication policies in the Disaster Recovery 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 118 and Provisioning operating system requirements on page 118. 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 139 and DFS namespace operating system requirements on page 144. 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 204 and Data Movement policy protocol requirements on page 212. We also recommend installing a separate StorageX server when creating and running Data Movement policies. 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 285 and Migration Project operating system requirements on page 296. 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 336 and Understanding Replication policies on page 360. Network port requirements StorageX uses the following TCP ports for communication between its components: The StorageX server listens on TCP ports 9451 and The StorageX replication agent listens on TCP port These ports must be open in any firewalls located between these StorageX components. 24 StorageX Administrator s Guide

41 StorageX requirements 1 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, replication agents, and the file storage resources that host the file data StorageX replicates or migrates. The StorageX server and Linux replication agents 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 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. You can change the listening port specified for a replication agent. However, before you change the listening port of a replication agent, review the list of network ports already in use by Microsoft networking components, DFS, CIFS, NFS, and other file storage resources. For more information about changing the listening ports for replication agents, see Changing the replication agent listening port on page 113. 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 and 9453 StorageX replication agent 9452 Network ports used by DFS The following table lists the network ports used by DFS. TABLE 9 Network ports used by DFS Service Name UDP TCP NetBIOS Datagram Service 138 NetBIOS Session Service 139 LDAP Server Remote Procedure Call (RPC) 135 Server Message Block (SMB) Network ports used by CIFS CIFS uses the following standard Windows networking ports: 138 StorageX Administrator s Guide 25

42 1 StorageX network connectivity and policy processing considerations Network ports used by NFS The following table lists the network ports used by NFS. TABLE 10 Network ports used by NFS Service Name UDP TCP NFS mount daemon (mountd) NFS status daemon (statd,statmon) NFS lock manager (lockd,nlockmgr) NFS quota daemon (quotad,rquotad) 608 StorageX network connectivity and policy processing considerations As 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, replication agents, 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). 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 replication agents. 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. 26 StorageX Administrator s Guide

43 StorageX installation and configuration worksheet 1 StorageX installation and configuration worksheet Use 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 Identify the file storage resources StorageX will manage and verify network connectivity and permissions to install and run the replication agent on the file storage resources. 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 replication agents 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 64. 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. 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. 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. StorageX server computer verified? StorageX database computer verified? StorageX Console computers verified? File storage resource name: Network connectivity and permissions verified? Replication agent proxy computer required? File storage resource name: Network connectivity and permissions verified? Replication agent proxy computer required? File storage resource name: Network connectivity and permissions verified? Replication agent proxy computer required? File storage resource name: Network connectivity and permissions verified? Replication agent proxy computer required? File storage resource name: Network connectivity and permissions verified? Replication agent proxy computer required? File storage resource name: Network connectivity and permissions verified? Replication agent proxy computer required? DFS namespace name: Host computer: DFS namespace name: Host computer: Application name: Application name: Application name: Application name: Computer type: Computer type: Computer type: Computer type: StorageX Administrator s Guide 27

44 1 Installing StorageX components Installing StorageX components This 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 28. StorageX Windows replication agents. For more information, see Installing Windows replication agents on page 32. StorageX Linux replication agents. For more information, see Installing and configuring Linux replication agents on page 33 Installation account requirements When 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 Console You 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 13 and StorageX Console computer requirements on page 16. 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 7 and StorageX database computer requirements on page 17. You can select one of the following component combinations when you install StorageX: StorageX Console and StorageX server Installs both the StorageX server and the StorageX Console on a single computer. StorageX server Installs 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. 28 StorageX Administrator s Guide

45 Installing StorageX components 1 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.5, available at 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: 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. NOTE If 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. StorageX Administrator s Guide 29

46 1 Installing StorageX components NOTE This 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. NOTE Data 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 Click Next. 15. On the StorageX Database dialog box, select or specify a database instance for the StorageX database, and then click Next. NOTE This 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 are using a default instance of Microsoft SQL Server Express installed locally, specify.\sqlexpress. 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. 30 StorageX Administrator s Guide

47 Installing StorageX components 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: NOTE This 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. NOTE 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. 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 StorageX Server dialog box specify the StorageX server that you want the StorageX Console to connect to by completing the following steps: NOTE This 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. 18. 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. NOTE This 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. StorageX Administrator s Guide 31

48 1 Installing StorageX components 19. 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. 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 35 and Adding license keys and specifying license notifications on page 37. b. Click Finish to close the setup program. Installing Windows replication agents StorageX automatically installs a Windows replication agent on the StorageX server computer when you install the StorageX server. You can also enable StorageX to automatically install Windows replication agents on destination or source Windows file storage resources when transferring CIFS data to or from Windows file storage resources when running StorageX policies. For more information about how StorageX automatically deploys Windows replication agents, see Understanding standard replication agent usage and data transfer on page 9. For more information about enabling StorageX to deploy replication agents, see Enabling deployment of Windows replication agents on Windows file storage resources on page 109. You can also manually deploy Windows replication agents in the Control Panel view. For more information about manually deploying Windows replication agents, see Manually deploying Windows replication agents on page 107. NOTE The Remote Registry service must be running on the computer where you want to deploy a Windows replication agent. 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 replication agent 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 replication agent 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 replication agents. In these scenarios, install Windows replication agents on Windows replication agent proxy computers as needed or use the replication agent installed on the StorageX server to migrate the CIFS file data. For more information about replication agent proxy computers, see Understanding StorageX replication agent proxy computers on page StorageX Administrator s Guide

49 Installing StorageX components 1 Installing and configuring Linux replication agents You can use the Windows replication agent 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 replication agents on destination and source Linux file storage resources or you can install and configure a Linux replication agent on a Linux replication agent proxy computer to migrate NFS data. Data Dynamics, Inc. recommends that you install Linux replication agents 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 replication agent on the destination file storage resource, install a Linux replication agent on the source file storage resource. In some cases, you may not be able to install a Linux replication agent 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 replication agent 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 replication agents. In these scenarios, install Linux replication agents on Linux replication agent proxy computers as needed or use the replication agent installed on the StorageX server to migrate the NFS file data. For more information about replication agent proxy computers, see Understanding StorageX replication agent proxy computers on page 9. Before you install a Linux replication agent, ensure the Linux computer where you want to install the Linux replication agent meets system requirements. For more information, see Linux replication agent computer requirements on page 20. To install and configure a Linux replication agent 1. Copy the Linux replication agent RPM file from the following folder in the StorageX installation package or CD to the Linux computer where you want to install the Linux replication agent: \ReplicationAgents\Linux\storagexra-Version.rpm where Version is the version of the StorageX Linux replication agent you want to install. 2. Connect to the Linux computer where you want to install the Linux replication agent and open a command prompt. 3. Type rpm -i and then the path to the Linux replication agent.rpm file. Then press Enter. For example, if you placed the Linux replication agent in the /tmp folder, type: rpm -i /tmp/storagexra-version.rpm where Version is the version of the StorageX Linux replication agent you want to install. StorageX installs the Linux replication agent in the /usr/local/ura folder. 4. After the Linux replication agent installation completes, configure the Linux replication agent by completing the following steps: a. In the command prompt, type: /etc/init.d/ura configure StorageX Administrator s Guide 33

50 1 Installing StorageX components b. When prompted to enter the TCP port the Linux replication agent should listen on, press Enter to accept the default or specify a TCP port for the replication agent. Ensure that the Linux firewall is configured to allow communication on the TCP port you specify for the Linux replication agent. For more information about replication agent listening ports, see Network ports used by StorageX on page 25 and Changing the replication agent listening port on page 113. c. 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 CPT port you specify for the StorageX server. For more information about StorageX server ports, see Network ports used by StorageX on page 25. d. When prompted, type the fully qualified domain name of the StorageX server the Linux replication agent 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. e. 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 replication agent 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 replication agent by typing the following command at the command prompt: /etc/init.d/ura start If the following error message displays, the required glibc.i686 and libstdc el6.i686 or libstdc el7_0.i bit packages are not installed on the computer: bad ELF interpreter: No such file or directory The Linux replication agent is a 32-bit application and requires 32-bit versions of OS system libraries. These libraries are not installed on Red Hat Enterprise Linux 64-bit by default. You must install these 32-bit libraries on the Linux replication agent computer before you can use the Linux replication agent. If you want to install the required 32-bit packages on Red Hat Enterprise Linux 6, type the following commands: sudo yum install glibc.i686 sudo yum install libstdc el6.i686 If you want to install the required 32-bit packages on Red Hat Enterprise Linux 7, type the following commands: sudo yum install glibc.i686 sudo yum install libstdc el7_0.i686 After you install the 32-bit packages, start the Linux replication agent by typing /etc/init.d/ura start at the command prompt. 34 StorageX Administrator s Guide

51 Opening the StorageX Console 1 NOTE If you receive an error when you load the libraries above, use the yum whatprovides command to determine what shared libraries are required. For example: yum whatprovides libstdc++.so.6 7. To verify the Linux replication agent 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 replication agent installed displays in the list of deployed agents by completing the following steps: a. Click the Control Panel tab. b. In the left pane, click Deployed Agents. c. In the center pane, verify that the name of the Linux computer where you installed the Linux replication agent displays in the Host column and that Running displays in the Status column. Opening the StorageX Console Open 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 28 and Installing the StorageX server and StorageX Console on page 28. 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 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. StorageX Administrator s Guide 35

52 1 Working with license keys Working with license keys This section provides information about working with license keys, and includes the following topics: Understanding StorageX licensing on page 36 Adding license keys and specifying license notifications on page 37 Viewing product version and license key information on page 38 Obtaining license keys on page 38 Updating license keys on page 39 Verifying license keys on page 39 Understanding StorageX licensing StorageX license keys allow you to use one or more product features, on a feature-by-feature basis. 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 Namespace Management policies for your environment. In addition, Data Movement licensing may be limited to a specific amount of migrated data, depending on the license. StorageX licenses can include one or more of the following features: Migration Applies to all migration features, including Phased Migration policies, Archival Migration policies, and Migration Projects. Replication Applies to all replication features, including Replication policies. Discovery Applies to all discovery features, including the File Insight tool. Reporting Applies to all reporting features. Disaster Recovery Applies to all disaster recovery features, including Disaster Recovery policies. Namespace Applies to advanced namespace features, including Namespace Availability and Namespace Backup policies. For information about adding license keys to your StorageX installation, see Adding license keys and specifying license notifications on page StorageX Administrator s Guide

53 Working with license keys 1 Adding license keys and specifying license notifications Specify 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 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 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 38. For more information about viewing product version and license key information, see Viewing product version and license key information on page 38. 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 enable notifications for licensing reminders, complete the following steps: a. Select the Enable License Notifications check box. b. 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. After confirming StorageX can send the test message successfully, click Next. 7. Click Finish. StorageX Administrator s Guide 37

54 1 Working with license keys Viewing product version and license key information You can view product version and license key information at any time in the StorageX Console. To view product version and license key 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 38 and Updating license keys on page 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 keys You can purchase new licenses for StorageX or extend your StorageX evaluation period by sending an message to: sales@datdyn.com If you want to purchase new licenses for StorageX, include the following information in your message: Company name Your name, job title, and a phone number where you can be contacted Product name and version you want to purchase If you want to extend your StorageX evaluation period, include the following information in your 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 key information on page StorageX Administrator s Guide

55 Working with license keys 1 For more information about adding license keys, see Adding license keys and specifying license notifications on page 37. For more information about updating license keys, see Updating license keys on page 39. Updating license keys You 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 NOTE If 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 38. 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 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. a. Click OK, and then click Next. b. If you want to enable 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 keys After you obtain, add, or update one or more license keys, you must then verify your new license keys before you can use StorageX functionality. StorageX Administrator s Guide 39

56 1 Configuring StorageX access control To verify a license key 1. Open the StorageX Console. 2. If you are opening the StorageX Console for the first time or with a new, unverified license key, 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. Select the license key you want to verify and click Verify. 5. Copy the verification code provided and send it to your Data Dynamics sales contact. 6. 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. 7. Click OK, and then click Next. 8. Click Next, and then click Finish. Configuring StorageX access control After 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 40 Understanding StorageX roles on page 41 Configuring role-based access control on page 42 Viewing assigned roles on page 43 Understanding role-based access control When 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. 40 StorageX Administrator s Guide

57 Configuring StorageX access control 1 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 43. 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 roles StorageX 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-Only This 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. NOTE When configuring role-based access control for StorageX, we recommend you assign all StorageX Console users the Read-Only role at a minimum. Read and Execute This 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 Execute This 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 41

58 1 Configuring StorageX access control Administrator This 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 control To 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. NOTE If 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. ATTENTION After 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. 42 StorageX Administrator s Guide

59 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 roles If 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 auditing StorageX 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 43 Understanding StorageX audit events on page 43 Configuring auditing settings on page 44 Viewing StorageX audit events on page 45 Understanding StorageX auditing When 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 events StorageX 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 43

60 1 Configuring StorageX auditing 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 settings If 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. NOTE Users 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 StorageX Administrator s Guide

61 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 events Once 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. NOTE Users 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 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 45

62 1 Backing up the StorageX database Backing up the StorageX database The 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 238 and Viewing Phased Migration policies scheduled to run in the future on page 259 Canceling Archival Migration policies on page 264 and Viewing Archival Migration policies scheduled to run in the future on page 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 Full Database Backups (SQL Server), available at For more information about the StorageX database, see Understanding the StorageX database on page 7. Stopping and restarting the StorageX server From 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: 46 StorageX Administrator s Guide

63 Upgrading StorageX 1 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 238 and Restarting Archival Migration policies on page 265. Upgrading StorageX You can quickly and easily upgrade your existing StorageX 7.5 or later installation to a newer version of StorageX using the installation package for the new version of the product. NOTE Users cannot upgrade from StorageX 7.1 or earlier to a newer version of the product. This section provides information about upgrading StorageX, and includes the following topics: Upgrading StorageX servers and databases on page 47 Upgrading StorageX Console computers on page 48 Upgrading StorageX replication agents on page 49 Upgrading StorageX servers and databases When 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. StorageX Administrator s Guide 47

64 1 Upgrading StorageX NOTE When 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. Click Upgrade. 12. When finished, click Finish to close the setup program. Upgrading StorageX Console computers After 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. Once 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. 48 StorageX Administrator s Guide

65 Upgrading StorageX 1 6. On the StorageX Setup Wizard Welcome dialog box, review the welcome message and then click Next. 7. Click Upgrade. 8. When finished, click Finish to close the setup program. 9. 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. NOTE If 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 39. 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. 10. Verify you can access all necessary functionality in the StorageX Console. Upgrading StorageX replication agents When upgrading your StorageX server and database, we recommend you also upgrade any replication agents deployed in your environment. For more information about managing replication agents, see Managing replication agents on page 106. You can only use StorageX to upgrade replication agents deployed on Windows hosts. If you want to upgrade a replication agent installed on a Linux host, you must manually uninstall the replication agent and then install the new replication agent on the Linux computer. For information about uninstalling Linux replication agents, see Uninstalling Linux replication agents on page 52. For information about re-installing Linux replication agents, see Installing and configuring Linux replication agents on page 33. To upgrade Windows replication agents 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 Agents. 4. In the right pane, right-click the replication agent you want to upgrade and select Upgrade. 5. Repeat step 4 for each replication agent in your environment. StorageX Administrator s Guide 49

66 1 Uninstalling StorageX Uninstalling StorageX This section explains how to uninstall StorageX components. It includes the following topics: Checklist: Uninstalling StorageX components on page 50 Uninstalling replication agents on page 50 Removing replication agents from the StorageX database on page 53 Uninstalling the StorageX server and StorageX Consoles on page 54 Deleting the StorageX database on page 54 Deleting StorageX log files, cache files, and remaining program folders on page 54 Checklist: Uninstalling StorageX components Use the following checklist when uninstalling StorageX components. 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 238 and Viewing Phased Migration policies scheduled to run in the future on page 259 Canceling Archival Migration policies on page 264 and Viewing Archival Migration policies scheduled to run in the future on page Uninstall Windows and Linux replication agents. For more information, see Uninstalling replication agents on page Close all StorageX Consoles. 4 Uninstall the StorageX server. For more information, see Uninstalling the StorageX server and StorageX Consoles on page Uninstall all StorageX Consoles. For more information, see Uninstalling the StorageX server and StorageX Consoles on page Delete the StorageX database. For more information, see Deleting the StorageX database on page 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 54. Uninstalling replication agents Uninstall StorageX Windows and Linux replication agents when you no longer want to use the replication agent to migrate file data. For more information about uninstalling replication agents, see the following topics: Uninstalling Windows replication agents using the StorageX Console on page 51 Uninstalling Windows replication agents using Windows Add or Remove Programs on page 51 Uninstalling Linux replication agents on page StorageX Administrator s Guide

67 Uninstalling StorageX 1 Uninstalling Windows replication agents using the StorageX Console You can uninstall Windows replication agents using the StorageX Console. You can also uninstall Windows replication agents using the Windows Add/Remove Programs feature. This topic explains how to uninstall Windows replication agents using the StorageX Console. For more information about uninstalling Windows replication agents using the Windows Add/Remove Programs feature, see Uninstalling Windows replication agents using Windows Add or Remove Programs on page 51. Before you uninstall a Windows replication agent, ensure you stop any policies that use the Windows replication agent to migrate data. Also ensure no policies are scheduled to run using the Windows replication agent in the future. For more information about how to perform these tasks, see the following topics: Canceling Phased Migration policies on page 238 and Viewing Phased Migration policies scheduled to run in the future on page 259 Canceling Archival Migration policies on page 264 and Viewing Archival Migration policies scheduled to run in the future on page 279 To uninstall a Windows replication agent using the StorageX Console 1. In the StorageX Console, click the Control Panel tab. 2. In the left pane, click Deployed Agents. 3. In the center pane, right-click each replication agent you want to uninstall and then click Uninstall. 4. If you want to uninstall the selected StorageX replication agents using the same credentials used to deploy each of the selected agents, click Uninstall using the same credentials that were used to deploy each of the selected agents and then type the credentials. 5. If you want to specify the credentials you want StorageX to use to uninstall the selected StorageX replication agents, click Uninstall the selected agents using the following credentials. Select this option when the credentials used to run the replication agent do not have the security permissions to uninstall the agent. 6. Click OK. 7. Click the Alerts tab to verify that the replication agent was uninstalled successfully. 8. In the Control Panel view, click Refresh to remove the replication agent from the list of deployed agents. Uninstalling Windows replication agents using Windows Add or Remove Programs You can uninstall Windows replication agents using the Windows Add/Remove Programs feature. You can also uninstall Windows replication agents using StorageX Console. This topic explains how to uninstall Windows replication agents using the using the Windows Add/Remove Programs feature. For more information about uninstalling Windows replication agents using the StorageX Console, see Uninstalling Windows replication agents using the StorageX Console on page 51. StorageX Administrator s Guide 51

68 1 Uninstalling StorageX Before you uninstall a Windows replication agent, ensure you stop any policies that use the Windows replication agent to migrate data. Also ensure no policies are scheduled to run using the Windows replication agent in the future. For more information about how to perform these tasks, see the following topics: Canceling Phased Migration policies on page 238 and Viewing Phased Migration policies scheduled to run in the future on page 259 Canceling Archival Migration policies on page 264 and Viewing Archival Migration policies scheduled to run in the future on page 279 The user account used to uninstall the Windows replication agent using the Add/Remove Programs feature must have Administrator permissions on the computer where the Windows replication agent is installed. To uninstall a Windows replication agent using the Windows Add or Remove Programs feature 1. Connect to the computer where the Windows replication agent is installed. 2. In Control Panel, open Add or Remove Programs. 3. Select StorageX Replication Agent, and then click Uninstall. 4. If a confirmation dialog box displays asking if you are sure you want to uninstall the StorageX Replication Agent, click Yes. StorageX uninstalls the Windows replication agent. 5. After the uninstall completes, remove the Windows replication agent from the StorageX database. The uninstalled Windows replication agent will continue to display in the Control Panel view Deployed Agents list until you remove it from the StorageX database. For more information, see Removing replication agents from the StorageX database on page 53. Uninstalling Linux replication agents Uninstall a Linux replication agent when you no longer want to use the Linux replication agent to migrate file data. Before you uninstall a Linux replication agent, ensure you stop any policies that use the Linux replication agent to migrate data. Also ensure no policies are scheduled to run using the Linux replication agent in the future. For more information about how to perform these tasks, see the following topics: Canceling Phased Migration policies on page 238 and Viewing Phased Migration policies scheduled to run in the future on page 259 Canceling Archival Migration policies on page 264 and Viewing Archival Migration policies scheduled to run in the future on page 279 The user account used to uninstall the Linux replication agent must have root access permissions on the computer where the Linux replication agent is installed. To uninstall a Linux replication agent 1. Connect to the Linux file storage resource where the Linux replication agent you want to uninstall is installed. 2. Open a command prompt and sign in as an administrator with root access permissions. 52 StorageX Administrator s Guide

69 Uninstalling StorageX 1 3. Type rpm -e storagexra and then press Enter. StorageX uninstalls the Linus replication agent. If the Linux replication agent is running, StorageX first stops the Linux replication agent and then uninstalls the agent. 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/ura 5. Remove the Linux replication agent from the StorageX database. The uninstalled Linux replication agent will continue to display in the Control Panel view Deployed Agents list until you remove it from the StorageX database. For more information, see Removing replication agents from the StorageX database on page 53. Removing replication agents from the StorageX database Remove, or purge, a replication agent from the StorageX database under the following conditions: You cannot uninstall a replication agent because the computer on which the replication agent was installed no longer exists or was renamed. You uninstalled a Windows replication agent using the Windows Add or Remove Programs feature. For more information, see Uninstalling Windows replication agents using Windows Add or Remove Programs on page 51. You uninstalled a Linux replication agent. For more information, see Uninstalling Linux replication agents on page 52. NOTE You typically do not need to remove, or purge, a replication agent from the StorageX database when you uninstall a Windows replication agent using the StorageX Console. For more information, see Uninstalling Windows replication agents using the StorageX Console on page 51. To remove a replication agent from the StorageX database 1. In the StorageX Console, click the Control Panel tab. 2. In the left pane, click Deployed Agents. 3. In the center pane, right-click the agent you want to remove from the StorageX database and then click Purge. 4. Click Yes to confirm you want to purge the selected agent. The agent is removed from the database and from the list of agents. 5. Click Refresh and confirm that the replication agent is no longer displayed in the list of deployed agents. StorageX Administrator s Guide 53

70 1 Uninstalling StorageX Uninstalling the StorageX server and StorageX Consoles This 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. Deleting the StorageX database After 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 50. 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 Deleting StorageX log files, cache files, and remaining program folders After 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 StorageX Administrator s Guide

71 Uninstalling StorageX 1 To delete StorageX log files, cache files, and remaining program folders 1. Connect to each computer where you installed a StorageX Windows replication agent, 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. NOTE The \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 replication agent 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. NOTE The \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 replication agent 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 55

72 1 Uninstalling StorageX 56 StorageX Administrator s Guide

73 Configuring and Viewing File Storage Resources Chapter 2 This section explains what the Storage Resources view is and how to add file 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 file storage resources in the Storage Resources view. Finally, this section explains how to manage your StorageX infrastructure, including configuring and managing StorageX replication agents. In this chapter Checklist: Configuring file storage resources and StorageX Understanding the Storage Resources view Understanding file storage resource validation checks Verifying file storage resource DNS configuration Adding the StorageX server service account to file storage resources Configuring platform API access for file storage resources Configuring default credentials for file storage resources Adding file storage resources Configuring file storage resources in My Resources Configuring credentials for specific file storage resources Configuring virtual file storage resources Configuring the SNMP community name for file storage resources Configuring NFS credentials Configuring intercluster interfaces for NetApp Cluster Mode file storage resources 99 Verifying file storage resources Specifying replication agent settings on file storage resources Viewing file storage resource information Removing file storage resources from My Resources Exporting file storage resource import lists Managing replication agents Working with StorageX events StorageX Administrator s Guide 57

74 2 Checklist: Configuring file storage resources and StorageX Checklist: Configuring file storage resources and StorageX Use the following checklist to help you configure file storage resources and StorageX: TABLE 13 Task Checklist: Configuring file storage resources and StorageX 1 Ensure you understand the Storage Resources view and how you can organize file storage resources in the Storage Resources view. For more information, see Understanding the Storage Resources view on page If you want to use custom folders to organize your file 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 62 and Creating custom folders in the Storage Resources view on page Verify file storage resource DNS configuration for each Windows, Linux, Data ONTAP, VNX OE for File, and OneFS file storage resource you want to manage using StorageX. Also verify the file storage resource DNS configuration for each file 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 Ensure the StorageX server service account has Administrator or root access permissions on each file storage resource you want to manage with StorageX. For more information, see Adding the StorageX server service account to file storage resources on page 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 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 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 389 Configuring default SSH shell credentials on page 71 Configuring SSH shell credentials for specific file storage resources on page 94 Creating and managing NFS exports on page 124 How StorageX manages data access in NFS environments with automount map files on page 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 60 and Adding file storage resources on page 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 file storage resources on page StorageX Administrator s Guide

75 Checklist: Configuring file storage resources and StorageX 2 TABLE 13 Task Checklist: Configuring file storage resources and StorageX 10 Configure virtual file storage resources, such as Data ONTAP vfilers, Vservers, or SVMs and EMC VNX CIFS/NFS Servers, as needed. For more information, see Configuring virtual file storage resources on page 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 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. 13 Verify that the file storage resources you added display correctly in My Resources. For more information, see Verifying file storage resources on page StorageX uses replication agents to transfer file data when running Phased Migration policies. Specify replication agent settings on file storage resources as appropriate. For more information, see Specifying replication agent settings on file storage resources on page 101. 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 file storage resources from a central management console. For more information, see Viewing file storage resource information on page 103. Manage StorageX replication agents as needed. For more information, see Understanding StorageX replication agents on page 8 and Managing replication agents on page 106. 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 File Storage Resources on page 117. 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 137. 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 197 and Synchronizing DFS namespaces on page 193. 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 203. 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 StorageX Administrator s Guide 59

76 2 Understanding the Storage Resources view Migration Projects. For more information, see Creating and Managing Migration Projects on page 283. 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 335. Understanding the Storage Resources view Use the Storage Resources view to view and manage file storage resources using StorageX. The Storage Resources view provides both built-in and custom folders designed to help you easily view and organize file 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 61 Understanding custom folders in the Storage Resources view on page 62 Creating custom folders in the Storage Resources view on page 63 Deleting custom folders in the Storage Resources view on page StorageX Administrator s Guide

77 Understanding the Storage Resources view 2 Understanding the My Resources folder StorageX provides a built-in My Resources folder in the Storage Resources view. The My Resources folder displays the file storage resources you want to manage using StorageX, as well as the DFS namespaces that you can manage using StorageX. By default, the My Resources folder is empty when you first install StorageX. Add file storage resources to the My Resources folder or a custom folder under the My Resources folder so you can begin managing file storage resources using StorageX. You must add file 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.0 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.0 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 Once you add a file storage resource to the My Resources folder, you can use StorageX to perform the following file 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 119 and Creating and managing NFS exports on page 124. 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 128 and Creating and managing Data ONTAP SnapMirrors on page 131. 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 217 and How StorageX manages data access in NFS environments with automount map files on page 220. Include file 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 283. You can add file storage resources one at a time to My Resources, or you can add multiple file storage resources at once using a file storage resource import list. For more information about adding file storage resources to the My Resources folder, see Adding file storage resources on page 73. StorageX Administrator s Guide 61

78 2 Understanding the Storage Resources view 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 60 and Adding file storage resources on page 73. 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 283 and Adding sources and destinations to Migration Projects on page 298. 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 137 and Adding DFS namespaces to My Resources on page 163. 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 file storage resources. For more information, see Understanding custom folders in the Storage Resources view on page 62 and Creating custom folders in the Storage Resources view on page 63. Understanding custom folders in the Storage Resources view In 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 file storage resources managed by StorageX. For example, you can create custom folders based on company departments, geographic locations, or cost centers. You can also add a file storage resource to more than one custom folder. For example, you can add a file storage resource to more than one custom folder if you want to add a file 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: 62 StorageX Administrator s Guide

79 Understanding file storage resource validation checks 2 Creating custom folders in the Storage Resources view on page 63 Deleting custom folders in the Storage Resources view on page 63 Creating custom folders in the Storage Resources view You can create custom folders in the Storage Resources view to help you logically group and organize the file 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 62 Deleting custom folders in the Storage Resources view on page 63 Deleting custom folders in the Storage Resources view Delete custom folders from the Storage Resources view when you no longer want to use the custom folder to organize file 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 62 Creating custom folders in the Storage Resources view on page 63 Understanding file storage resource validation checks When you add or import a new file storage resource to the My Resources folder in the Storage Resources view, StorageX automatically runs a series of validation checks to determine whether the file storage resource is accessible, is properly configured, and can be managed by StorageX. After StorageX finishes running validation checks on your resources, the File Storage Resources tab of the center pane in the Storage Resources view displays 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 file storage resource. The Failed icon ( ) indicates that StorageX could not validate the resource. StorageX Administrator s Guide 63

80 2 Verifying file storage resource DNS configuration 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, click the File Storage Resources tab in the center pane, then right-click My Resources in the tree view and select Refresh. NOTE Most 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 configuration Before 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 resources The StorageX server service account is an account used by the StorageX server service to communicate with and manage file storage resources. 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, VNX OE for File, or OneFS file storage resource, add the StorageX server service account to each Windows, Data ONTAP, VNX OE for File, or OneFS file storage resource you want to manage using StorageX and ensure the StorageX server service account has Administrator permissions on each resource. 64 StorageX Administrator s Guide

81 Configuring platform API access for file storage resources 2 NOTE If 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 382. 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 15. Configuring platform API access for file storage resources If 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 65 Enabling platform API access on VNX OE for File file storage resources on page 67 Enabling platform API access on OneFS file storage resources on page 68 Enabling platform API access on Data ONTAP file storage resources If 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. If the file storage resource is a Data ONTAP 7.0 file storage resource or a Data ONTAP Mode file storage resource, consider the following points: Typically, new Data ONTAP 7.0 file storage resources and Data ONTAP 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.0 or Data ONTAP 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.0 or Data ONTAP Mode file storage resource, you can specify that you want StorageX to use HTTP or HTTPS to communicate with the resource. StorageX Administrator s Guide 65

82 2 Configuring platform API access for file storage resources 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.0 and 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.0 or Data ONTAP 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.0 or Data ONTAP Mode file storage resources, see the Data ONTAP documentation. If the file storage resource is a Data ONTAP 7.0 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. 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 or Data ONTAP 8.3 Cluster Mode file storage resource, consider the following points: RPC is not supported on Data ONTAP 8.2 or Data ONTAP 8.3 Cluster Mode 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. 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. 66 StorageX Administrator s Guide

83 Configuring platform API access for file storage resources 2 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. There may be firewall policies on Data ONTAP 8.2 or Data ONTAP 8.3 Cluster Mode 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 or Data ONTAP 8.3 Cluster Mode 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.0 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. If you want StorageX to use HTTP or HTTPS to communicate with a Data ONTAP 8.0 Vserver or SVM, ensure that HTTP or HTTPS is configured on the Vserver or SVM hosting resource. Data ONTAP 8.0 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 resources If 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 StorageX Administrator s Guide 67

84 2 Configuring default credentials for file storage resources 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 resources If 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. Configuring default credentials for file storage resources You 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 68. 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 70. Default OneFS credentials for StorageX to use to manage OneFS file storage resources. For more information, see Configuring default OneFS credentials on page 71. 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 71. 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. 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 file storage resources on page 90. Configuring default Data ONTAP credentials StorageX 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. 68 StorageX Administrator s Guide

85 Configuring default credentials for file storage resources 2 For more information about the StorageX server service account, see StorageX server service account requirements on page 15. 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 68. 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 65. If you have Data ONTAP 8.2 or Data ONTAP 8.3 Cluster Mode 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 or Data ONTAP 8.3 in Cluster Mode. For more information, see Configuring credentials for specific Data ONTAP file storage resources on page 91. 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 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. StorageX Administrator s Guide 69

86 2 Configuring default credentials for file storage resources 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. 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 91. Configuring default VNX OE for File credentials StorageX 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 15. 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 70. 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 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 StorageX Administrator s Guide

87 Configuring default credentials for file storage resources 2 Configuring default OneFS credentials StorageX 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. 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 15. 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 93. 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 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 93. 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 389. 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. StorageX Administrator s Guide 71

88 2 Configuring default credentials for file storage resources NOTE If 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: 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. NOTE The 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 389. 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 StorageX Administrator s Guide

89 Adding file storage resources 2 Adding file storage resources In order to manage file storage resources using StorageX, you must add your file 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 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 Data ONTAP file storage resources If you want to manage Data ONTAP 7.0 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.0 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. 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, as well as the EMC VNX hosting resource to My Resources. NOTE StorageX 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 Generic CIFS, NFS, or CIFS/NFS file 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 60 and Adding file storage resources on StorageX Administrator s Guide 73

90 2 Adding file storage resources page 73. 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 283 and Adding sources and destinations to Migration Projects on page 298. You can add file 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 74. 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 79 and Importing lists of file storage resources on page 86. Adding and configuring file storage resources individually Add 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 60 and Adding file storage resources on page 73. 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: Use the Ctrl or Shift keys to select multiple resources to add. 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 79 and Importing lists of file storage resources on page 86. ATTENTION Before 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 StorageX Administrator s Guide

91 Adding file 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. NOTE You 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 64. 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 94. 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. 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 68 and Configuring credentials for specific Data ONTAP file storage resources on page 91. b. If the file storage resource you added is running Data ONTAP 8.2 or Data ONTAP 8.3 in Cluster Mode, click Actions > Set API Credentials and specify an Administrator account and password for StorageX to use to communicate with the resource. StorageX Administrator s Guide 75

92 2 Adding file storage resources Data ONTAP 8.2 or Data ONTAP 8.3 in Cluster Mode does 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 or Data ONTAP 8.3 in Cluster Mode. For more information, see Configuring credentials for specific Data ONTAP file storage resources on page 91. 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 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 96. 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 68 and Configuring credentials for specific Data ONTAP file storage resources on page 91. 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. 76 StorageX Administrator s Guide

93 Adding file storage resources 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 96. 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 68 and Configuring credentials for specific Data ONTAP file storage resources on page 91. 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 70 and Configuring credentials for specific OneFS file storage resources on page 93. 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 94. 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 77

94 2 Adding file storage resources 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 97. 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 70 and Configuring credentials for specific OneFS file storage resources on page 93. 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 94. NOTE If 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 71 and Configuring credentials for specific OneFS file storage resources on page 93. 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 94. c. Click Next. 78 StorageX Administrator s Guide

95 Adding file storage resources 2 d. If you want StorageX to use the default SSH credentials to migrate file data, click OK to confirm. 14. Click Finish. 15. Right-click My Resources and select Refresh. 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 again. 17. If the file storage resource you added is a Windows file storage resource, and you want to allow StorageX to deploy a replication agent to the resource, select the new resource in the Summary pane and click the checkbox in the Allow agent install column. For more information, see Specifying replication agent settings on file storage resources on page 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 file storage resources on page 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 98 and Configuring NFS credentials on page 98. 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 file storage resources in My Resources on page 87. Creating file storage resource import lists You 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 File win-xp-machine.domain.local,windows nt win7-machine.domain.local,windows nt win8-machine.domain.local,windows nt win2k-machine.domain.local,windows nt win2k3-machine.domain.local,windows nt win2k3r2-machine.domain.local,windows nt win2k8-machine.domain.local,windows nt win2k12-machine.domain.local,windows nt netapp-736.domain.local,netapp filer,false,root,passwd netapp-8-7mode.domain.local,netapp filer,false,root,passwd netapp-8-cmode.domain.local,netapp cluster,false,admin,passwd netapp-811-7mode.domain.local,netapp filer,true,root,passwd netapp-811-cmode.domain.local,netapp cluster,false,admin,passwd netapp-vfiler.domain.local,netapp vfiler,false,root,passwd,vfiler01,netapp-736.domain.local StorageX Administrator s Guide 79

96 2 Adding file storage resources netapp-vserver.domain.local,netapp vserver,false,root,passwd,vserver01,netapp-811-cmode.domain.local emc-vnx-host.domain.local,emc vnx,false,nasadmin,nasadmin,false,root,passwd emc-vnx-cifs-vdm.domain.local,emc celerra,false,nasadmin,nasadmin,vdm01,emc-vnx-host.domain.local,true,false,r oot,passwd emc-vnx-nfs-data-mover.domain.local,emc celerra,false,nasadmin,nasadmin,datamover01,emc-vnx-host.domain.local,false, false,root,passwd emc-isilon.domain.local,emc isilon,false,user,passwd linux.domain.local,linux,,,,,,,false,root,passwd To create a file storage resource import list, specify the following information in a.csv file: Name Specify the IP address, NetBIOS name, or fully qualified domain name for each file storage resource you want to add. NOTE If you specify a Data ONTAP vfiler, Vserver, or SVM or a VNX OE for File Data Mover, you do not need to list the individual file storage resources that make up the nodes in the Data ONTAP vfiler, Vserver, or SVM or the VNX OE for File Data Mover. You only need to specify the NetBIOS name or fully qualified domain name for the Data ONTAP vfiler, Vserver, or SVM or the VNX OE for File Data Mover, 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 Naming conventions specified by the Internet Engineering Task Force (IETF) in RFC 953, available at and in RFC1123, available at 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 StorageX Administrator s Guide

97 Adding file storage resources 2 Platform Type Specify 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 Windows NT Linux EMC EMC Celerra EMC VNX EMC Isilon NetApp Filer NetApp Cluster NetApp vfiler NetApp Vserver Generic CIFS Generic NFS Generic CIFS/NFS Value displayed in StorageX Console Microsoft Windows Linux EMC Celerra EMC Celerra EMC VNX EMC Isilon NetApp Filer NetApp Filer NetApp vfiler NetApp vfiler Generic CIFS Generic NFS Generic CIFS/NFS 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 104. Use Default API Credentials If 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 68. API User Name If 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 file storage resources on page 90. StorageX Administrator s Guide 81

98 2 Adding file storage resources API Password If 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 file storage resources on page 90. Virtual Resource Name 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, specify the exact name of the resource that hosts the virtual resource. Consider the following examples: If the file storage resource is a Data ONTAP vfiler, Vserver, or SVM, specify the exact name of the vfiler, Vserver, or SVM. ATTENTION The 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 118. For more information about how StorageX can provision file storage resources as a part of a Migration Project, see Understanding Migration Projects on page 285. 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. ATTENTION The 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 file storage resource information on page 103. For more information about how StorageX can provision file storage resources as a part of a Migration Project, see Understanding Migration Projects on page StorageX Administrator s Guide

99 Adding file storage resources 2 Hosting Resource 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, 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. Is Virtual Data Mover If 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 Credentials If 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 68. SSH User Name If 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 file storage resources on page 90. SSH Password If 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 file storage resources on page 90. SSH Private Key File If 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. StorageX Administrator s Guide 83

100 2 Adding file storage resources NOTE Private 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 394. For more information, see Configuring credentials for specific file storage resources on page 90. NOTE If 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 74. 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.local win7-machine.domain.local win8-machine.domain.local win2k-machine.domain.local win2k3-machine.domain.local win2k3r2-machine.domain.local win2k8-machine.domain.local win2k12-machine.domain.local netapp-736.domain.local netapp-8-7mode.domain.local netapp-8-cmode.domain.local netapp-811-7mode.domain.local netapp-811-cmode.domain.local netapp-vfiler.domain.local netapp-vserver.domain.local emc-vnx-host.domain.local emc-vnx-data_mover.domain.local emc-isilon.domain.local linux.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: win-xp-machine.domain.local,windows nt win7-machine.domain.local,windows nt win8-machine.domain.local,windows nt win2k-machine.domain.local,windows nt win2k3-machine.domain.local,windows nt win2k3r2-machine.domain.local,windows nt win2k8-machine.domain.local,windows nt 84 StorageX Administrator s Guide

101 Adding file storage resources 2 win2k12-machine.domain.local,windows nt netapp-736.domain.local,netapp filer netapp-8-7mode.domain.local,netapp filer netapp-8-cmode.domain.local,netapp cluster netapp-811-7mode.domain.local,netapp filer netapp-811-cmode.domain.local,netapp cluster netapp-vfiler.domain.local,netapp vfiler netapp-vserver.domain.local,netapp vserver emc-vnx_host.domain.local,emc vnx emc-vnx_data_mover.domain.local,emc celerra emc-isilon.domain.local,emc isilon linux.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 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,passwd netapp-8-7mode.domain.local,netapp filer,false,root,passwd netapp-8-cmode.domain.local,netapp cluster,false,admin,passwd netapp-811-7mode.domain.local,netapp filer,true,root,passwd netapp-811-cmode.domain.local,netapp cluster,false,admin,passwd NOTE If 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 68 and Configuring credentials for specific file storage resources on page 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,true netapp-8-7mode.domain.local,netapp filer,true netapp-8-cmode.domain.local,netapp cluster,true netapp-811-7mode.domain.local,netapp filer,true netapp-811-cmode.domain.local,netapp cluster,true netapp-vfiler.domain.local,netapp vfiler,true netapp-vserver.domain.local,netapp vserver,true emc-vnx-host.domain.local,emc vnx,false,nasadmin,nasadmin emc-vnx-cifs-vdm.domain.local,emc celerra,false,nasadmin,nasadmin,vdm01,emc-vnx-host.domain.local,true emc-vnx-nfs-data-mover.domain.local,emc celerra,false,nasadmin,nasadmin,datamover01,emc-vnx-host.domain.local,false StorageX Administrator s Guide 85

102 2 Adding file storage resources emc-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.local netapp-vserver.domain.local,netapp vserver,false,root,passwd,vserver01,netapp-811-cmode.domain.local emc-vnx-host.domain.local,emc vnx,false,nasadmin,nasadmin emc-vnx-cifs-vdm.domain.local,emc celerra,false,nasadmin,nasadmin,vdm01,emc-vnx-host.domain.local,true emc-vnx-nfs-data-mover.domain.local,emc celerra,false,nasadmin,nasadmin,datamover01,emc-vnx-host.domain.local,false emc-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 86. Importing lists of file storage resources After 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 79. ATTENTION Before 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 64. 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. 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. 86 StorageX Administrator s Guide

103 Configuring file storage resources in My Resources 2 NOTE You 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 replication agent to a Windows resource, click Allow Agent 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 Naming conventions specified by the Internet Engineering Task Force (IETF) in RFC 953, available at and in RFC1123, available at 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 Click Finish. Configuring file storage resources in My Resources After you add a file storage resource to the My Resources folder or a custom folder under My Resources in the Storage Resources view, you can modify the file storage resource configuration as needed. Ensure the file storage resource is configured correctly in the domain and the StorageX server service account has been added to the file storage resource and has Administrator or root access permission on the file storage resource before you configure the resource. Typically you verify the file storage 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. For more information, see Verifying StorageX Administrator s Guide 87

104 2 Configuring file storage resources in My Resources file storage resource DNS configuration on page 64, StorageX server service account requirements on page 15, and Adding the StorageX server service account to file storage resources on page 64. To configure a file 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 file storage resource you want to configure. 3. If the file 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 If the file 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 68 and Configuring credentials for specific Data ONTAP file storage resources on page 91. b. If the file 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 96. c. If the file storage resource you added is a Data ONTAP file storage resource running Data ONTAP 8.2 or Data ONTAP 8.3 in Cluster Mode, specify an Administrator account and password for StorageX to use to communicate with the resource. Data ONTAP 8.2 or Data ONTAP 8.3 in 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 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 or Data ONTAP 8.3 in Cluster Mode. For more information, see Configuring credentials for specific Data ONTAP file storage resources on page 91. d. 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 AF26-71CD381FB428.html. 88 StorageX Administrator s Guide

105 Configuring file storage resources in My Resources 2 5. If the file 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 70 and Configuring credentials for specific OneFS file storage resources on page 93. b. If the file 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 96. c. 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, configure specific SSH shell credentials for the resource. For more information, see Configuring SSH shell credentials for specific file storage resources on page If the file storage resource you added is a OneFS file storage resource and 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 71 and Configuring credentials for specific OneFS file storage resources on page If the 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 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 98 and Configuring NFS credentials on page 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 file storage resources on page Specify replication agent settings for the file storage resource as appropriate. For more information, see Specifying replication agent settings on file storage resources on page 101. After you have added the file 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 file storage resources from a central management console. For more information, see Viewing file storage resource information on page 103. Manage StorageX replication agents as needed. For more information, see Understanding StorageX replication agents on page 8 and Managing replication agents on page 106. 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 StorageX Administrator s Guide 89

106 2 Configuring credentials for specific file storage resources create and manage Data ONTAP volumes, qtrees, and SnapMirrors on Data ONTAP file storage resources. For more information, see Provisioning File Storage Resources on page 117. 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 137. 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 203. 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 283. Configuring credentials for specific file storage resources You can configure the following types of credentials for StorageX to use with specific file 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 91. 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 92. 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 93. 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 94. When you configure specific credentials to communicate with specific file storage resources, StorageX uses these specific credentials to communicate with the file 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 StorageX Administrator s Guide

107 Configuring credentials for specific file storage resources 2 Configuring credentials for specific Data ONTAP file storage resources StorageX 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 15. 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 68. 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 65. If you have Data ONTAP 8.2 or Data ONTAP 8.3 Cluster Mode 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 or Data ONTAP 8.3 in Cluster Mode. 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 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 file storage resources on page In the Summary pane, select the Data ONTAP file storage resource for which you want to specify credentials, and click Actions > Set API Credentials. 4. 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. StorageX Administrator s Guide 91

108 2 Configuring credentials for specific file storage resources 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, 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. 6. 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. 7. Click OK. 8. 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 resources StorageX 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. For more information about the StorageX server service account, see StorageX server service account requirements on page 15. 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 StorageX Administrator s Guide

109 Configuring credentials for specific file storage resources 2 NOTE If 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 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 file storage resources on page In the Summary pane, select the VNX OE for File file storage resource for which you want to specify credentials, and click Actions > Set API Credentials. 4. Click Use the following settings. 5. In the Username field, type name the name of a user account with Administrator permissions on the selected VNX OE for File file storage resource. 6. In the Password field, type the password for the user account with Administrator permissions on the VNX OE for File file storage resource. 7. Click OK. 8. Right-click My Resources and select Refresh to verify the specified credentials are correct. Configuring credentials for specific OneFS file storage resources StorageX 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 15. 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 71. 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 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. StorageX Administrator s Guide 93

110 2 Configuring credentials for specific file storage 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 file storage resources on page In the Summary pane, select the OneFS file storage resource for which you want to specify credentials, and click Actions > Set API Credentials. 4. Click Use the following settings. 5. In the Username field, type the name of a user account with root access permissions on the OneFS file storage resource. 6. In the Password field, type the password for the user account. 7. Click OK. 8. 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 resources StorageX 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 389. 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 71. 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. 94 StorageX Administrator s Guide

111 Configuring credentials for specific file storage resources 2 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 file storage resources on page In the Summary pane, 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. 3. 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. 4. 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. 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. NOTE The 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 389. d. 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. 6. In the Summary pane, right-click the file storage resource and select Refresh to verify the specified credentials are correct. StorageX Administrator s Guide 95

112 2 Configuring virtual file storage resources Configuring virtual file storage resources After 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 96 Specifying hosting properties for VNX OE for File Data Movers on page 97 Specifying hosting properties for Data ONTAP vfilers, Vservers, and SVMs If 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 the StorageX, see Adding file storage resources on page 73. 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 68 and Configuring credentials for specific Data ONTAP file storage resources on page 91. 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 file storage resources on page 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. ATTENTION The 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 118. For more information about how StorageX can provision file storage resources as a part of a Migration Project, see Understanding Migration Projects on page StorageX Administrator s Guide

113 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 Movers If 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 file storage resources on page 73. 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 70 and Configuring credentials for specific VNX OE for File file storage resources on page 92. 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 file storage resources on page 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. ATTENTION The 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 file storage resource information on page 103. For more information about how StorageX can provision file storage resources as a part of a Migration Project, see Understanding Migration Projects on page 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 97

114 2 Configuring the SNMP community name for file storage resources ATTENTION If 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. Configuring the SNMP community name for file storage resources StorageX 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 file storage resources on page 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 credentials By default, StorageX Linux replication agents 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. 98 StorageX Administrator s Guide

115 Configuring intercluster interfaces for NetApp Cluster Mode file storage resources 2 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 file storage resources on page 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 replication agent to use when communicating with the file storage resource. 6. In the Default Group ID, specify the group ID you want the Linux replication agent to use when communicating with the file storage resource. 7. Click OK. Configuring intercluster interfaces for NetApp Cluster Mode file storage resources If you want to use the default StorageX replication agent 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 294. For more information about configuring and using NetApp Cluster Mode resources, see the NetApp Support site, 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. 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. StorageX Administrator s Guide 99

116 2 Verifying file storage resources 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 file storage resources on page Right-click the cluster for which you want to configure an intercluster interface, and then click Create Intercluster Interface. NOTE You 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. NOTE You can only select data or intercluster ports. StorageX only displays applicable ports. 9. Click OK. StorageX creates the new intercluster interface. Verifying file storage resources After you add file storage resources to the My Resources folder or a custom folder under My Resources, verify that the file storage resource you added passed all validation checks, and that StorageX displays the new resource correctly under My Resources. For more information about file storage resource validation checks, see Understanding file storage resource validation checks on page 63. To verify file 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. In the center pane, click the File Storage Resources tab. 4. In the list of resources displayed in the center pane, select the file storage resource you want to verify. 5. 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. 100 StorageX Administrator s Guide

117 Specifying replication agent settings on file storage resources 2 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. 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 storage resources, see Configuring platform API access for file storage resources on page 65, Configuring default credentials for file storage resources on page 68, Configuring file storage resources in My Resources on page 87, Configuring credentials for specific file storage resources on page 90, and Configuring virtual file storage resources on page 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. 9. 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 64. Specifying replication agent settings on file storage resources StorageX uses replication agents to move file data. The following topics in this section provide information about how to specify replication agent settings on file storage resources: Specifying replication agent proxy computers for file storage resources on page 101 Specifying replication agent data transfer rate limits on page 103 For more information about replication agents, see the following topics: Understanding StorageX replication agents on page 8 Replication agent computer requirements on page 19 Installing Windows replication agents on page 32 Installing and configuring Linux replication agents on page 33 Managing replication agents on page 106 Specifying replication agent proxy computers for file storage resources A replication agent proxy computer is a proxy computer where you deploy a replication agent. After you deploy a replication agent to a proxy computer, you can then use the replication agent 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 replication agent on the StorageX server computer when you install the StorageX server. By default, StorageX also deploys Windows replication agents 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 replication agents on Linux file storage resources. For more information about deploying Windows replication agents, see StorageX Administrator s Guide 101

118 2 Specifying replication agent settings on file storage resources Installing Windows replication agents on page 32. For more information about manually installing and configuring Linux replication agents, see Installing and configuring Linux replication agents on page 33. However, you may have specific Windows file storage resources on which you do not want StorageX to deploy a Windows replication agent. You may also have Linux file storage resources where you don t want to install a Linux replication agent. 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 replication agent or install a Linux replication agent. In these types of scenarios, you can specify a replication agent proxy computer for the file storage resource. When you specify a replication agent proxy computer for a file storage resource, StorageX uses the replication agent on the specified proxy computer to migrate or replicate data when StorageX runs a policy that affects the file storage resource. To specify a replication agent 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 replication agent 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 file storage resources on page Click the Control Panel tab. 4. In the left pane, click Agent Proxies. 5. In the center pane, click New Proxy. 6. In the Host field, type the fully qualified domain name of the file storage resource for which you want to specify a proxy replication agent 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 replication agent 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 replication agent on the StorageX server computer as the replication agent proxy computer for the file storage resource, click Use default proxy. 9. If you want to use a specific replication agent proxy computer, click Use this specified proxy, and then type the fully qualified domain name of the replication agent proxy computer or click the ellipsis button (...) to browse to and select the proxy computer. 10. If you want to use a replication agent installed on a proxy computer that is a member of a replication agent group, click Use this specified agent group, and then select the agent group from the list. For more information about replication agent groups, see Creating and managing replication agent groups on page Click OK. 102 StorageX Administrator s Guide

119 Viewing file storage resource information 2 Specifying replication agent data transfer rate limits You can specify replication agent data transfer rate limits for Windows and Linux replication agents. Specifying replication agent data transfer rate limits for replication agents is also known as bandwidth throttling. Consider specifying replication agent 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 replication agent data transfer rate limits 1. In the StorageX Console, click the Control Panel tab. 2. In the left pane, click Deployed Agents. 3. In the center pane, right-click a Windows or Linux replication agent 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 replication agent 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 replication agent 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. Viewing file storage resource information You can view property information for each heterogeneous file 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 file storage resources. For more information, see Viewing file storage resource properties on page 103. Refresh displayed file storage resource information. For more information, Refreshing displayed file storage resource information on page 104. Specify file storage resource identity. For more information, see Specifying file storage resource platform type on page 104. Viewing file storage resource properties You can use StorageX to view the properties of file storage resources you have added to the My Resources folder in the Storage Resources view. For more information about adding file storage resources to the My Resources folder in the Storage Resources view, see Adding file storage resources on page 73. StorageX Administrator s Guide 103

120 2 Viewing file storage resource information To view file 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 file 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 file storage resource. The properties dialog box has a series of tabs that display additional information about the selected file storage resource, such as IP address, operating system, and more. For more information about the fields and options on each tab, click the Help button on the tab. Refreshing displayed file storage resource information Refresh file storage resource information when you want to display and verify any recent changes you made to the file storage resource. When you refresh file storage resource information, StorageX updates information about the file storage resource and displays this updated information in the Storage Resources view. To refresh file storage resource information 1. In the StorageX Console, click the Storage Resources tab. 2. If you want to refresh the information displayed for all file 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 file 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 file storage resource, right-click the file storage resource, and then click Refresh. 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 type When 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. 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. 104 StorageX Administrator s Guide

121 Removing file storage resources from My Resources 2 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 file storage resources from My Resources Remove a file 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 file storage resource. If you added the file storage resource to more than one custom folder under My Resources, StorageX only removes the file storage resource from the custom folder you select. StorageX does not remove the file storage resource from any other custom folders. If you added a file storage resource to multiple custom folders, you must remove the file storage resource from each custom folder separately. To remove a file storage resource from My Resources 1. In the StorageX Console, click the Storage Resources tab. 2. In the center pane, select the file storage resource you want to remove. 3. Click the Remove storage resource icon ( ). 4. Click OK to confirm. Exporting file storage resource import lists After you add and configure storage resources in your StorageX environment, you can export your storage resources as a.csv-format file 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. To export a list of file storage resources from My Resources 1. In the StorageX Console, click the Storage Resources tab. 2. Right-click the My Resources folder or a specific subfolder and then click Export file storage resources. 3. Click OK to confirm. 4. Browse to the location where you want to export the list of file 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. StorageX Administrator s Guide 105

122 2 Managing replication agents Managing replication agents This section explains how to manage replication agents. It includes information about how to perform the following tasks: Specify default service account credentials for Windows replication agents. For more information, see Specifying default service account credentials for Windows replication agents on page 106. Manually deploy Windows replication agents. For more information, see Manually deploying Windows replication agents on page 107. Specify default replication agent proxy computers. For more information, see Specifying default replication agent proxy computers on page 109. View replication agent status information. For more information, see Viewing replication agent status on page 110. Stop, start, pause, and resume Windows replication agents. For more information, see Stopping, starting, pausing, and resuming Windows replication agents on page 110. Change Windows replication agent service account credentials. For more information, see Changing deployed Windows replication agent service account credentials on page 111. Create and manage replication agent groups. For more information, see Creating and managing replication agent groups on page 112 Change replication agent listening ports. For more information, see Changing the replication agent listening port on page 113. For more information about replication agents, replication agent computer requirements and service account requirements, and deploying replication agents, see Understanding StorageX replication agents on page 8, Replication agent computer requirements on page 19, Replication agent service account requirements on page 21, Installing Windows replication agents on page 32, and Installing and configuring Linux replication agents on page 33. Specifying default service account credentials for Windows replication agents You can specify default service account credentials for Windows replication agents in the Control Panel view. When you specify default service account credentials for Windows replication agents, all Windows replication agents that StorageX deploys after you specify those default credentials will use the default service account credentials. However, service account credentials for Windows replication agents already deployed by the StorageX server are not affected. For more information about changing the service account credentials for deployed Windows replication agents, see Changing deployed Windows replication agent service account credentials on page 111. To specify default service account credentials for Windows replication agents 1. In the StorageX Console, click the Control Panel tab. 2. In the left pane, click Deployed Agents. 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 replication agents using the following format: 106 StorageX Administrator s Guide

123 Managing replication agents 2 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 replication agent service account requirements. 6. In the Password field, type the password for the service account you want to use for the default replication agent service account. 7. In the Confirm field, type the password again. 8. Click OK. Manually deploying Windows replication agents You can enable StorageX to automatically deploy Windows replication agents to manage data transfers. However, you can also manually Windows deploy replication agents. For example, you may want to manually deploy Windows replication agents under the following conditions: You want to deploy a Windows replication agent to a file storage resource before you run a Phased Migration policy that uses the replication agent on the file storage resource. Deploying the replication agent manually before running the policy allows you to verify that the replication agent was successfully deployed on the file storage resource before the policy runs. You may want to deploy a replication agent to a replication agent proxy computer and verify that the replication agent deployed successfully before configuring Phased Migration policies that use the replication agent on the proxy computer. NOTE The Remote Registry service must be running on the computer where you want to deploy a Windows replication agent. For information on enabling the Remote Registry service, see the Microsoft TechNet Library. Before you manually deploy Windows replication agents, ensure that you select the Allow replication agent to be deployed to this host option on the storage resource. Also ensure that the Windows replication agent service account has appropriate permissions on the computer where you want to deploy the replication agent. For example, the Windows replication service account must have Logon as a Service permissions on the computer where you want to deploy the agent. For more information about replication agent service account requirements, see Replication agent service account requirements on page 21. To manually deploy a Windows replication agent 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 replication agent, and then click Properties. 3. On the Computer Properties tab, select the Allow replication agent 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 Agents. 6. In the center pane, click Deploy. StorageX Administrator s Guide 107

124 2 Managing replication agents 7. In the Host field, type the fully qualified domain name of the computer where you want to deploy the replication agent or click the ellipsis button (...) to browse to and select the computer where you want to deploy the replication agent. 8. If you want to specify a listening port other than 9452 for the replication agent, in the Port field, type the number of the port you want the replication agent to use. By default, StorageX uses port 9452 to communicate with replication agents. If you change the replication agent listening port, make sure that the port you specify allows the StorageX server to communicate through any firewalls with the StorageX Console and replication agents deployed by the StorageX server. 9. If you want to use the default service account credentials specified for replication agent service accounts, click The default user name. For more information about specifying default replication agent credentials, see Specifying default service account credentials for Windows replication agents on page 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: NOTE StorageX stores all the credentials currently specified or previously specified for StorageX server and replication agent 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 replication agent service account, click The credentials specified below, and then complete the following steps: NOTE Before you specify new service account credentials for the replication agent, ensure the new service account you specify meets replication agent service account requirements. For more information about replication agent service account requirements, see Replication agent service account requirements on page 21. a. In the User Name field, type the name of the user account you want to use for the replication agent 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 replication agent service account requirements. a. In the Password field, type the password for the user account you want to use for the replication agent service account. b. In the Confirm field, type the password again. c. Click OK. 12. On the Alerts tab, verify that StorageX deployed the replication agent successfully. 108 StorageX Administrator s Guide

125 Managing replication agents Click Refresh to display the new replication agent. Enabling deployment of Windows replication agents on Windows file storage resources If you have Windows file storage resources specified as sources or destinations in Phased Migration policies, you can configure StorageX to automatically deploy Windows replication agents to destinations or sources when you run Phased Migration policies. To enable StorageX to deploy a Windows replication agent on a storage resource, select the Allow replication agent to be deployed to this host check box on the Computer Properties tab for the Windows file storage resource. To enable StorageX to automatically deploy a Windows replication agent 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 replication agent, and then click Properties. 3. On the Computer Properties tab, select the Allow replication agent to be deployed to this host check box. 4. Click OK. For more information about how StorageX uses replication agents, including Windows replication agents, see Understanding StorageX replication agents on page 8. Specifying default replication agent proxy computers You can specify a default replication agent 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 replication agent proxy computer, StorageX uses the replication agent on the proxy computer to migrate or replicate the appropriate file data. To specify a replication agent proxy computer 1. In the StorageX Console, click the Control Panel tab. 2. In the left pane, click Agent 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 replication agent 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 replication agent deployed on the StorageX server, click Use default proxy. 7. If you want to specify a specific replication agent proxy computer for the file storage resource, click Use this specified proxy, and then type the fully qualified domain name of a replication agent proxy computer or click the ellipsis button (...) to browse to and select a replication agent proxy computer. StorageX Administrator s Guide 109

126 2 Managing replication agents 8. If you want to specify a replication agent group for the file storage resource, click Use this specified agent group and then select a group from the drop-down list. For more information about replication agent groups, see Creating and managing replication agent groups on page Click OK. Viewing replication agent status You can view information about the status, or health, of a replication agent in the Control Panel view. To view the status, or health, of a replication agent 1. In the StorageX Console, click the Control Panel tab. 2. In the left pane, click Deployed Agents. 3. In the center pane, right-click the replication agent 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 replication agent. Stopping, starting, pausing, and resuming Windows replication agents You can stop, start, pause, and resume Windows replication agents in the Control Panel view. If you stop a Windows replication agent when it is transferring data, the data transfer stops. Restarting the replication agent 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. NOTE You cannot stop, start, pause, or resume a Linux replication agent from the Control Panel view. The Stop, Start, Pause, and Resume menu options are only available for Windows replication agents. To start, stop, pause, or resume a Windows replication agent 1. In the StorageX Console, click the Control Panel tab. 2. In the left pane, click Deployed Agents. 3. If you want to stop a Windows replication agent, in the right pane right-click the running replication agent you want to stop, and then complete the following steps: a. Click Stop. b. Click Yes to confirm you want to stop the replication agent. StorageX stops the replication agent and updates the status of the replication agent to Not Running in the Status column. c. Click Refresh to view the updated status of the replication agent. 4. If you want to start a stopped Windows replication agent, in the right pane right-click the replication agent you want to start, and then click Start. StorageX starts the replication agent and updates the status of the replication agent to Running in the Status column. Click Refresh to view the updated status of the replication agent. 110 StorageX Administrator s Guide

127 Managing replication agents 2 5. If you want to pause a running Windows replication agent, in the right pane right-click the replication agent you want to pause, and then click Pause. StorageX pauses the replication agent and updates the status of the replication agent to Paused in the Status column. Click Refresh to view the updated status of the replication agent. 6. If you want to resume a paused Windows replication agent, in the right pane right-click a paused replication agent that you want to resume, and then click Resume. StorageX resumes the replication agent and updates the status of the replication agent to Running in the Status column. Click Refresh to view the updated status of the replication agent. Changing deployed Windows replication agent service account credentials You can the credentials of deployed Windows replication agents in the Control Panel view. Before you change the replication agent service account credentials, review the requirements for Windows replication agent service accounts. For more information, see Windows replication agent service account requirements on page 22. To change deployed Windows replication agent service account credentials 1. In the StorageX Console, click the Control Panel tab. 2. In the left pane, click Deployed Agents. 3. In the center pane, right-click the Windows replication agent that you want to change replication agent service account credentials for, and then click Change Credentials. 4. If you want to use the default service account credentials specified for Windows replication agent service accounts, click The default user name. For more information about specifying default Windows replication agent credentials, see Specifying default service account credentials for Windows replication agents on page 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: NOTE StorageX stores all the credentials currently specified or previously specified for StorageX server and replication agent 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 replication agent service account, click The credentials specified below, and then complete the following steps: NOTE Before you specify new service account credentials for the replication agent, ensure the new service account you specify meets Windows replication agent service account requirements. For more information about Windows replication agent service account requirements, see Windows replication agent service account requirements on page 22. StorageX Administrator s Guide 111

128 2 Managing replication agents a. In the User Name field, type the name of the user account you want to use for the replication agent 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 replication agent service account requirements. b. In the Password field, type the password for the user account you want to use for the replication agent service account. c. In the Confirm field, type the password again. d. Click OK. For more information about replication agents and deploying replication agents, see Understanding StorageX replication agents on page 8 and Installing Windows replication agents on page 32. Creating and managing replication agent groups Use replication agent groups if you want to distribute data transfer workloads or increase the performance and availability of replication agents when transferring data using Phased Migration policies. You can use replication agent groups with Phased Migration policies to specify which replication agent or replication agent group you want to perform data transfer operations. For more information about assigning replication agent groups to policies, see Distributing file data transfer workloads using replication agent groups on page 222. To use replication agent groups, create the replication agent group, add replication agents to the group, and then assign the group to a policy. After you create replication agent groups and associate them with policies, StorageX can perform the following actions: If a computer where a replication agent is installed is not available, StorageX can use a different replication agent 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 replication agents in the group. A replication agent can belong to only one replication agent group. There is no limit to the number of replication agents each replication agent group can contain. To create and manage replication agent groups 1. In the StorageX Console, click the Control Panel tab. 2. In the left pane, click Deployed Agents. 3. If you want to create a replication agent group, complete the following steps: a. In the center pane, right-click a replication agent, and then click Properties. b. In the Group field, select New from the drop-down list. c. In the Group Name field, type a name for the group. d. In the Group Description field, type a description for the group. e. Click OK. StorageX creates the group and assigns the selected replication agent to the group. 112 StorageX Administrator s Guide

129 Changing StorageX server service account credentials 2 f. Click OK again to close the dialog box. 4. If you want to assign a replication agent to an existing replication agent group, complete the following steps: a. In the center pane, right-click a replication agent you want to assign to an existing group, and then click Properties. b. In the Group field, select the group to which you want to assign the replication agent from the drop-down list. c. Click OK. 5. If you want to view replication agents assigned to a replication agent group, in the center pane, click the Group column to sort the list alphabetically by replication agent group. Changing the replication agent listening port By default, StorageX uses the TCP port 9452 as the listening port for replication agents. You can change the replication agent listening port. However, before you change the listening port make sure that the port you specify is open. Also ensure that the replication agent can communicate using the port with the StorageX server. To change a replication agent listening port 1. In the StorageX Console, click the Control Panel tab. 2. In the left pane, click Deployed Agents. 3. In the center pane, right-click the replication agent for which you want to change the listening port, and then click Properties. 4. In the Port field, type the port you want the replication agent to use. 5. Click OK. Changing StorageX server service account credentials Use 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. StorageX Administrator s Guide 113

130 2 Working with StorageX events NOTE If 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 events This section explains how to work with StorageX events. It includes the following topics: Viewing StorageX events on page 114 Filtering events on page 114 Viewing StorageX events StorageX 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. Filtering events By 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. 114 StorageX Administrator s Guide

131 Working with StorageX events 2 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. StorageX Administrator s Guide 115

132 2 Working with StorageX events 116 StorageX Administrator s Guide

133 Provisioning File Storage Resources Chapter 3 This section explains how to provision heterogeneous file storage resources using the Storage Resources view. In this chapter Understanding provisioning Provisioning operating system requirements Creating and managing CIFS shared folders Creating and managing NFS exports Creating and managing Data ONTAP volumes and qtrees Creating and managing Data ONTAP SnapMirrors StorageX Administrator s Guide 117

134 3 Understanding provisioning Understanding provisioning After you add file storage resources to My Resources in the Storage Resources view, you can use StorageX as a central management console to provision heterogeneous file 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 Data ONTAP file storage resources, as well as create and manage SnapMirrors. For more information about using StorageX as a central management console to provision heterogeneous file storage resources, see the following topics: Creating and managing CIFS shared folders on page 119 Creating and managing NFS exports on page 124 Creating and managing Data ONTAP volumes and qtrees on page 128 Creating and managing Data ONTAP SnapMirrors on page 131 Provisioning operating system requirements In order to perform provisioning tasks, file 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 Linux Red Hat Linux 6 Red Hat Linux 7 Data ONTAP 7G V-Series NetApp Storage Systems Data ONTAP Mode Mode Mode Mode Mode Mode Mode 8.2 Cluster Mode Mode 8.3 Cluster Mode 118 StorageX Administrator s Guide

135 Creating and managing CIFS shared folders 3 TABLE 14 Supported operating systems for provisioning tasks Operating System Versions VNX OE for File OneFS Creating and managing CIFS shared folders This section explains how you can create and manage CIFS shared folders on file storage resources manage 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 119 Creating CIFS shared folders on page 119 Viewing CIFS shared folder properties on page 121 Viewing CIFS shared folder contents on page 122 Cloning CIFS shared folders on page 122 For more information about provisioning operating system requirements, see Provisioning operating system requirements on page 118. Understanding the CIFS protocol The 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. Creating CIFS shared folders You 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 15. 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. StorageX Administrator s Guide 119

136 3 Creating and managing CIFS shared folders 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 137. NOTE When 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. NOTE If 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: 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. 120 StorageX Administrator s Guide

137 Creating and managing CIFS shared folders 3 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. Viewing CIFS shared folder properties You 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 15. StorageX Administrator s Guide 121

138 3 Creating and managing CIFS shared folders NOTE StorageX 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 contents You 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 15. 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. Cloning CIFS shared folders You 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: 122 StorageX Administrator s Guide

139 Creating and managing CIFS shared folders 3 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. ATTENTION 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 224. 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. StorageX Administrator s Guide 123

140 3 Creating and managing NFS exports 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 Windows 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 Windows 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. Creating and managing NFS exports This 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 125 Creating NFS exports on page 125 Viewing NFS export properties on page 126 Cloning NFS exports on page 127 For more information about provisioning operating system requirements, see Provisioning operating system requirements on page StorageX Administrator s Guide

141 Creating and managing NFS exports 3 Understanding the NFS protocol The 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 exports You 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. 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 389. NOTE If your environment includes Data ONTAP Vservers or SVMs, you can use StorageX to view exports on Data ONTAP Vservers or SVMs, but you cannot create exports on Data ONTAP Vservers or SVMs using StorageX. 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. StorageX Administrator s Guide 125

142 3 Creating and managing NFS exports NOTE If 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. In the Local path field, specify the local path of an existing folder 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 using the appropriate Linux syntax. 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 Data ONTAP file storage resource, type the local path to an existing folder on the destination 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 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 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 an NFS export on a OneFS file storage resource, type the local path to an existing folder on the destination using the appropriate OneFS syntax. 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 properties You 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 15. 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. 126 StorageX Administrator s Guide

143 Creating and managing NFS exports 3 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 exports You 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. 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 389. ATTENTION When 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 224. 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 Server 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 Server 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. StorageX Administrator s Guide 127

144 3 Creating and managing Data ONTAP volumes and qtrees 6. In the Specify Exports to Duplicate dialog box, complete the following steps: a. In the left column, 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. b. In the Destination column, verify the local path for the destination NFS exports you want to create. If you want to change the local path for a specific destination NFS export, click the destination path and then type in a new local path. c. Click Next. 7. Review the paths for the source and destination NFS exports, and then click Finish to create the exports on the destination. Creating and managing Data ONTAP volumes and qtrees This 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 128 Creating qtrees on Data ONTAP file storage resources on page 129 Viewing qtree properties on Data ONTAP file storage resources on page 130 Sharing qtrees on Data ONTAP file storage resources on page 130 Deleting qtrees on Data ONTAP file storage resources on page 131 For more information about provisioning operating system requirements, see Provisioning operating system requirements on page 118. Creating volumes on Data ONTAP file storage resources If 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 or Data ONTAP 8 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. 128 StorageX Administrator s Guide

145 Creating and managing Data ONTAP volumes and qtrees 3 If you are creating a volume on a Data ONTAP 7.0 or Data ONTAP 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. 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 resources If 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 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. StorageX Administrator s Guide 129

146 3 Creating and managing Data ONTAP volumes and qtrees 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. Viewing qtree properties on Data ONTAP file storage resources You 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 resources You 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: 130 StorageX Administrator s Guide

147 Creating and managing Data ONTAP SnapMirrors 3 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. 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 resources You 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 SnapMirrors This 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 132 Creating SnapMirrors on Data ONTAP file storage resources on page 132 Initializing SnapMirrors on Data ONTAP file storage resources on page 133 Quiescing and resuming SnapMirrors on Data ONTAP file storage resources on page 133 Updating SnapMirrors on Data ONTAP file storage resources on page 134 Interrupting SnapMirror data transfers on Data ONTAP file storage resources on page 134 Breaking SnapMirror relationships on Data ONTAP file storage resources on page 135 Deleting SnapMirrors from StorageX for Data ONTAP file storage resources on page 136 StorageX Administrator s Guide 131

148 3 Creating and managing Data ONTAP SnapMirrors 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 283 and Generating Data ONTAP SnapMirror reports on page 302. For more information about provisioning operating system requirements, see Provisioning operating system requirements on page 118. Understanding SnapMirrors SnapMirror 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 132. Creating SnapMirrors on Data ONTAP file storage resources You 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, available on the NetApp Support web site at If you are creating SnapMirrors on Data ONTAP 8.x file storage resources, ensure you understand the following requirements: In Data ONTAP 8.x, 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.x 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.x 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. 132 StorageX Administrator s Guide

149 Creating and managing Data ONTAP SnapMirrors 3 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. 4. On the Source and Destination tab, specify the destination where you want to create the SnapMirror. NOTE You 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 resources After 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, available on the NetApp Support web site at 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 resources After 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: StorageX Administrator s Guide 133

150 3 Creating and managing Data ONTAP SnapMirrors 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. For detailed information about quiescing and resuming SnapMirrors, see the Data ONTAP Data Protection Online Backup and Recovery Guide, available on the NetApp Support web site at 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 resources By 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. NOTE You 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, available on the NetApp Support web site at 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 resources If a SnapMirror is currently updating or transferring data and you need to stop the transfer process, you can manually interrupt the transfer using StorageX. NOTE You can only interrupt a SnapMirror if the SnapMirror is updating or otherwise transferring data. 134 StorageX Administrator s Guide

151 Creating and managing Data ONTAP SnapMirrors 3 For detailed information about interrupting SnapMirrors, see the Data ONTAP Data Protection Online Backup and Recovery Guide, available on the NetApp Support web site at 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 resources You 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, available on the NetApp Support web site at 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. NOTE 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. 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 resources If 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, available on the NetApp Support web site at StorageX Administrator s Guide 135

152 3 Creating and managing Data ONTAP SnapMirrors 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. Deleting SnapMirrors from StorageX for Data ONTAP file storage resources You can delete existing SnapMirrors from StorageX for Data ONTAP file storage resources. ATTENTION If 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, available on the NetApp Support web site at 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. 136 StorageX Administrator s Guide

153 Creating and Managing DFS Namespaces Chapter 4 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 Understanding DFS namespaces DFS namespace operating system requirements Understanding DFS namespace validation checks Creating and configuring DFS namespaces Managing DFS namespaces Creating domain-based DFS namespace servers Managing domain-based DFS namespace servers Adding DFS links to DFS namespaces Managing DFS links Searching for DFS objects Converting stand-alone namespaces to domain-based namespaces Synchronizing DFS namespaces Backing up and restoring DFS namespaces StorageX Administrator s Guide Rev. A

154 4 Checklist: DFS namespace planning and implementation Checklist: DFS namespace planning and implementation This 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 139. 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 163. TABLE 15 Task Checklist: DFS namespace planning and implementation 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 Review DFS namespace operating system requirements. For more information, see DFS namespace operating system requirements on page 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 147 Stand-alone DFS namespace configuration requirements on page 150 Consolidation DFS namespace configuration requirements on page Create the DFS namespace. For more information about creating a DFS namespace, see the following topics: Creating domain-based DFS namespaces on page 148 Creating stand-alone DFS namespaces on page 150 Creating consolidation DFS namespaces on page 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 Add DFS links to your namespace. For more information, see Adding DFS links to DFS namespaces on page StorageX Administrator s Guide Rev. A

155 Understanding DFS namespaces 4 Understanding DFS namespaces A 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 163. 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 139 How DFS namespaces work on page 140 Understanding DFS namespace size limits and recommendations on page 141 Understanding DFS namespace types on page 142 DFS Namespace components A DFS namespace consists of the following components: DFS namespace folder Shared folder at the top of a DFS namespace topology that stores the logical structure of the DFS namespace. DFS namespace server Server 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 link File 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 target CIFS shared folder or folder under a CIFS shared folder that the DFS link references. StorageX Administrator s Guide Rev. A

156 4 Understanding DFS namespaces How DFS namespaces work You 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 StorageX Administrator s Guide Rev. A

157 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 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 recommendations Before 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 articles provide detailed information for DFS namespaces: Windows Server 2003: Distributed File System: Namespace Scalability and Sizing Questions, Microsoft TechNet ( Windows Server 2008: Choose a Namespace Type, Microsoft TechNet ( StorageX Administrator s Guide Rev. A

158 4 Understanding DFS namespaces Understanding DFS namespace types The 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 142 and Comparing DFS namespace types and modes on page 143. 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 142 and Comparing DFS namespace types and modes on page 143. 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 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 152. 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. 142 StorageX Administrator s Guide Rev. A

159 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 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 162. 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 Characteristic Comparing DFS namespace types and modes 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 \\NetBIOSDomainN ame\namespacena me \\DNSDomainName \NamespaceName \\NetBIOSDomainN ame\namespacena me \\DNSDomainName \NamespaceName \\ServerName\Nam espacename \\ServerName\#Co nsolidatedserverna me or \\ConsolidatedServ ername \\ConsolidatedServ ername 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 Rev. A

160 4 DFS namespace operating system requirements 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 Namespace size recommendations Minimum Active Directory Domain Services forest functional level Minimum Active Directory Domain Services domain functional level Minimum supported namespace servers Support for access-based enumeration (if enabled) Supported methods to ensure namespace availability 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 This means no more than approximately 5,000 folders with targets. Windows 2000 Windows 2000 mixed Windows 2000 Server The namespace can contain more than 5,000 folders with targets; the recommended limit is 50,000 folders with targets Windows Server 2003 Windows Server 2008 Windows Server 2008 The namespace can contain more than 5,000 folders with targets; the recommended limit is 50,000 folders with targets Active Directory Domain Services is not required Active Directory Domain Services is not required Windows 2000 Server No Yes Yes, requires Windows Server 2008 namespace server 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 The namespace can contain more than 5,000 folders with targets; the recommended limit is 50,000 folders with targets Active Directory Domain Services is not required Active Directory Domain Services is not required Windows 2000 Server No Create a consolidated namespace on a failover cluster 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 145 and DFS namespace client computer operating system requirements on page 146. DFS namespace operating system requirements When creating and managing DFS namespaces, ensure you understand operating system requirements for the following DFS components: 144 StorageX Administrator s Guide Rev. A

161 DFS namespace operating system requirements 4 DFS namespace servers. For more information, see DFS namespace server operating system requirements on page 145. DFS client computers. For more information, see DFS namespace client computer operating system requirements on page 146. DFS namespace server operating system requirements A 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 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. 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. StorageX Administrator s Guide Rev. A

162 4 Understanding DFS namespace validation checks DFS namespace client computer operating system requirements Client 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 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 available at 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 Windows XP Professional Windows 2000 Server Windows 2000 Professional Understanding DFS namespace validation checks When 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. 146 StorageX Administrator s Guide Rev. A

163 Creating and configuring DFS namespaces 4 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 namespaces This 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 147 and Creating domain-based DFS namespaces on page 148. Stand-alone DFS namespace configuration requirements on page 150 and Creating stand-alone DFS namespaces on page 150. Consolidation DFS namespace configuration requirements on page 153 and Creating consolidation DFS namespaces on page 153. Domain-based DFS namespace configuration requirements A 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. 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 15. 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 StorageX Administrator s Guide Rev. A

164 4 Creating and configuring DFS namespaces Permissions for DFS Namespaces article, available on the Microsoft TechNet web site at 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 145. For more information about the different types of DFS namespaces, see Understanding DFS namespace types on page 142. For more information about creating domain-based DFS namespaces, see Creating domain-based DFS namespaces on page 148. Creating domain-based DFS namespaces Create 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 147. 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: 148 StorageX Administrator s Guide Rev. A

165 Creating and configuring DFS namespaces 4 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. NOTE Microsoft 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. 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. 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 158. 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 60. StorageX Administrator s Guide Rev. A

166 4 Creating and configuring DFS namespaces Stand-alone DFS namespace configuration requirements A 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 15. 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 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 145. For more information about the different types of DFS namespaces, see Understanding DFS namespace types on page 142. For more information about creating stand-alone DFS namespaces, see Creating stand-alone DFS namespaces on page 150. Creating stand-alone DFS namespaces Create 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 StorageX Administrator s Guide Rev. A

167 Creating and configuring DFS namespaces 4 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: 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. NOTE Data 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. StorageX Administrator s Guide Rev. A

168 4 Creating and configuring DFS namespaces 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 158. 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 60. Understanding consolidation DFS namespaces Consolidation 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. 152 StorageX Administrator s Guide Rev. A

169 Creating and configuring DFS namespaces 4 Consolidation DFS namespace configuration requirements Before 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 , available on the Microsoft web site at 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 153 and Configuring consolidation DFS namespaces on page 155. 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. 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 15. All users in the domain that will access the namespace must have read only permissions on the consolidation DFS namespace. Creating consolidation DFS namespaces Before 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 153. 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 155. StorageX Administrator s Guide Rev. A

170 4 Creating and configuring DFS namespaces Use the following checklist to help you create a consolidation DFS namespace: TABLE 18 Task Checklist: Creating a consolidation DFS namespace 1 Create a consolidation DFS namespace. For more information about creating a consolidation DFS namespace, see Creating consolidation DFS namespaces on page Configure the consolidation DFS namespace. For more information about configuring the consolidation DFS namespace, see Configuring consolidation DFS namespaces on page Move the file data from the old file storage resource to the new file storage resource. 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. 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. 154 StorageX Administrator s Guide Rev. A

171 Creating and configuring DFS namespaces 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 158. 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 60. After you create the consolidation DFS namespace, configure the namespace. For more information, see Configuring consolidation DFS namespaces on page 155. Configuring consolidation DFS namespaces After you create a consolidation DFS namespace, you must configure the namespace. This section explains how to configure a consolidation DFS namespace. For more information about creating a consolidation DFS namespace, see Creating consolidation DFS namespaces on page 153. For more information about consolidation DFS namespace requirements, see Consolidation DFS namespace configuration requirements on page 153. 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. StorageX Administrator s Guide Rev. A

172 4 Creating and configuring DFS namespaces 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. ATTENTION You 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. NOTE If 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. 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: 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 , available on the Microsoft web site at After you create the consolidation DFS namespace, perform the following steps: 156 StorageX Administrator s Guide Rev. A

173 Managing DFS namespaces 4 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 205. 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. 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 175. Managing DFS namespaces This section explains how to manage DFS namespaces. For more information, see the following topics: Viewing DFS namespaces on page 158 Viewing DFS namespace properties on page 158 Modifying DFS namespace properties on page 159 Enabling access-based enumeration for DFS namespaces on page 159 Delegating management for DFS namespaces on page 160 StorageX Administrator s Guide Rev. A

174 4 Managing DFS namespaces Specifying referral settings for DFS namespaces on page 161 Refreshing DFS namespaces on page 162 Upgrading DFS namespaces to Windows Server 2008 mode on page 162 Adding DFS namespaces to My Resources on page 163 Verifying DFS namespaces on page 164 Removing DFS namespaces from My Resources on page 165 Deleting DFS namespaces on page 165 For more information about creating and configuring DFS namespaces, see Creating and configuring DFS namespaces on page 147. Viewing DFS namespaces Use 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 147. Viewing DFS namespace properties You 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 147. 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. 158 StorageX Administrator s Guide Rev. A

175 Managing DFS namespaces 4 Modifying DFS namespace properties You 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 147. 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 197. 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 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. 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 161 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 Click OK. Enabling access-based enumeration for DFS namespaces If 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 184. StorageX Administrator s Guide Rev. A

176 4 Managing DFS namespaces ATTENTION Access-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. 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 184. Delegating management for DFS namespaces You 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. 160 StorageX Administrator s Guide Rev. A

177 Managing DFS namespaces 4 4. Click OK. NOTE If 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. Specifying referral settings for DFS namespaces A 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 174. 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. NOTE For 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 146. StorageX Administrator s Guide Rev. A

178 4 Managing DFS namespaces Refreshing DFS namespaces You 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 142. 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. NOTE Gathering and displaying updated DFS namespace information may take some time if the DFS namespace is large. Upgrading DFS namespaces to Windows Server 2008 mode If 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. 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 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 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. NOTE If 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 StorageX Administrator s Guide Rev. A

179 Managing DFS namespaces 4 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. NOTE You 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 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 Resources Ensure 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 142. 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 165. StorageX Administrator s Guide Rev. A

180 4 Managing DFS namespaces 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 namespaces After 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 146. 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 147 and Modifying DFS namespace properties on page 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. 164 StorageX Administrator s Guide Rev. A

181 Managing DFS namespaces 4 Removing DFS namespaces from My Resources All 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 197. 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. 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 namespaces When 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 197. 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. StorageX Administrator s Guide Rev. A

182 4 Creating domain-based DFS namespace servers 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. Creating domain-based DFS namespace servers You 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 142. 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. 166 StorageX Administrator s Guide Rev. A

183 Managing domain-based DFS namespace servers 4 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 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 167. Managing domain-based DFS namespace servers Domain-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 167 Enabling and disabling referrals for domain-based DFS namespace servers on page 168 Overriding referral ordering for domain-based DFS namespace servers on page 169 Removing domain-based DFS namespace servers on page 170 For more information about creating domain-based DFS namespace servers, see Creating domain-based DFS namespace servers on page 166. Viewing and modifying domain-based DFS namespace servers You 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 166. StorageX Administrator s Guide Rev. A

184 4 Managing domain-based DFS namespace servers 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 168, 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 169 or click the Help button on the dialog box. 7. Click OK. For more information about creating domain-based DFS namespace servers, see Creating domain-based DFS namespace servers on page 166. For more information about managing domain-based DFS namespace servers, see Managing domain-based DFS namespace servers on page 167. Enabling and disabling referrals for domain-based DFS namespace servers You can enable or disable referrals 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 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 166. 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. 168 StorageX Administrator s Guide Rev. A

185 Managing domain-based DFS namespace servers 4 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, Online displays. If the domain-based DFS namespace server is disabled, Offline 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. 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. 7. Click OK. For more information about creating domain-based DFS namespace servers, see Creating domain-based DFS namespace servers on page 166. For more information about managing domain-based DFS namespace servers, see Managing domain-based DFS namespace servers on page 167. Overriding referral ordering for domain-based DFS namespace servers You 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 161. 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. StorageX Administrator s Guide Rev. A

186 4 Adding DFS links to DFS namespaces 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. 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 166. For more information about managing domain-based DFS namespace servers, see Managing domain-based DFS namespace servers on page 167. Removing domain-based DFS namespace servers You 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 166. For more information about viewing and modifying domain-based DFS namespace servers, see Viewing and modifying domain-based DFS namespace servers on page 167. Adding DFS links to DFS namespaces After you create a DFS namespace, add DFS links to the DFS namespace. A DFS link is a file 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. 170 StorageX Administrator s Guide Rev. A

187 Adding DFS links to DFS namespaces 4 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. 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, and 2012 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, or 2012 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 15. 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. NOTE You 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: StorageX Administrator s Guide Rev. A

188 4 Managing DFS links 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. 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 172. Managing DFS links The following topics provide information about managing DFS links: Viewing DFS link properties on page 172 Modifying DFS link properties on page 173 Specifying referral settings for DFS links on page 174 Refreshing DFS links on page 175 Creating folders in DFS namespaces on page 175 Deleting folders in DFS namespaces on page 176 Renaming DFS links and DFS namespace folders on page 178 Converting DFS links to folders on page 178 Deleting DFS links on page 179 Viewing DFS link targets on page 182 Adding additional DFS link targets to DFS links on page 182 Changing the status of DFS link targets on page 183 Specifying which users and groups can view specific DFS link targets on page 184 Enabling or disabling referrals for DFS link targets on page 185 Overriding referral ordering for DFS link targets on page 186 Deleting DFS link targets on page 187 For more information about creating DFS links, see Adding DFS links to DFS namespaces on page 170. Viewing DFS link properties You 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. 172 StorageX Administrator s Guide Rev. A

189 Managing DFS links 4 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. 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 170 and Managing DFS links on page 172. Modifying DFS link properties You 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. StorageX Administrator s Guide Rev. A

190 4 Managing DFS links 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 170 and Managing DFS links on page 172. Specifying referral settings for DFS links A 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 161. 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. 174 StorageX Administrator s Guide Rev. A

191 Managing DFS links 4 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. NOTE For 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 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 links Refreshing 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 170 and Managing DFS links on page 172. Creating folders in DFS namespaces You 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, and 2012 defaults share permissions to read-only. Windows 2000 Server defaults share permissions to allow everyone full access. If you want to create folders to organize DFS links in a DFS namespace on a Windows Server 2003, 2008, or 2012 server StorageX Administrator s Guide Rev. A

192 4 Managing DFS links 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 15. 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 170 and Managing DFS links on page 172. Deleting folders in DFS namespaces Delete 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. 176 StorageX Administrator s Guide Rev. A

193 Managing DFS links 4 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, or 2012 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, or 2012 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 170 and Managing DFS links on page 172. StorageX Administrator s Guide Rev. A

194 4 Managing DFS links Renaming DFS links and DFS namespace folders Rename 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 170 and Managing DFS links on page 172. Converting DFS links to folders In 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. NOTE You 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. 178 StorageX Administrator s Guide Rev. A

195 Managing DFS links 4 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. NOTE If 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 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 170 and Managing DFS links on page 172. Deleting DFS links Delete 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 1 Assume you have a DFS namespace with the structure shown in the following image: StorageX Administrator s Guide Rev. A

196 4 Managing DFS links 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 2 Assume 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: 180 StorageX Administrator s Guide Rev. A

197 Managing DFS links 4 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 170 and Managing DFS links on page 172. StorageX Administrator s Guide Rev. A

198 4 Managing DFS links Viewing DFS link targets A 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 170 and Managing DFS links on page 172. Adding additional DFS link targets to DFS links A 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 170. 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. 182 StorageX Administrator s Guide Rev. A

199 Managing DFS links 4 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. NOTE You 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 targets You 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. StorageX Administrator s Guide Rev. A

200 4 Managing DFS links 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 170 and Managing DFS links on page 172. Specifying which users and groups can view specific DFS link targets If 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 159. 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: 184 StorageX Administrator s Guide Rev. A

201 Managing DFS links 4 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 targets You 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 170 and Adding additional DFS link targets to DFS links on page 182. 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: StorageX Administrator s Guide Rev. A

202 4 Managing DFS links 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 170 and Adding additional DFS link targets to DFS links on page 182. For more information about overriding referral ordering for DFS link targets, see Overriding referral ordering for DFS link targets on page 186. Overriding referral ordering for DFS link targets You 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 174. 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. 186 StorageX Administrator s Guide Rev. A

203 Managing DFS links 4 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 166. For more information about managing domain-based DFS namespace servers, see Managing domain-based DFS namespace servers on page 167. Deleting DFS link targets Delete 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: StorageX Administrator s Guide Rev. A

204 4 Managing DFS links Example 1 Assume 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 2 Assume 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. 188 StorageX Administrator s Guide Rev. A