EMC DiskXtender for NAS Release 3.1

Transcription

1 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide P/N REV A02 EMC Corporation Corporate Headquarters: Hopkinton, MA

2 Copyright EMC Corporation. All rights reserved. Published January, 2008 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners. 2 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

3 Contents Preface Chapter 1 Chapter 2 Chapter 3 Overview of DiskXtender for NAS How DX-NAS works About DX-NAS architecture and functionality User interface Jobs Alerts and logs Reports Maintenance Backup Using the DX-NAS GUI Logging into DX-NAS About the DX-NAS GUI Menu bar Tabs Action bar Tree display pane Details pane Status bar Alerts window About the status for migrated files About printing Accessing online help Using Help Using the DX-NAS Command Line Interface Logging into the DX-NAS CLI Creating policies in the CLI Command line syntax and usage host source dest policy job sched EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide 3

4 Contents fileattrs report admin Chapter 4 Chapter 5 Chapter 6 Chapter 7 Chapter 8 Appendix A Configuring Policies Creating policies Migration policies Orphan file policies Source scan policies Fine tuning policies Fine tuning with the GUI Fine tuning with the CLI Specifying Match Criteria for Policies Match criteria search methods Match criteria commands Managing the DX-NAS system Monitoring the progress of a running job How to stop a running job DX-NAS properties file Setting the port for DX-NAS Setting the GUI and CLI logout period Enabling job logging File migration status Storage file management Creating source scan policies Running a source scan policy Orphan file management Reports Viewing a migration report Viewing an orphan file report Viewing a primary storage report Backing Up and Restoring DX-NAS Backing up the DX-NAS database Restoring the DX-NAS database Backing up primary and secondary storage Backing up offline stub files About backing up with NFS Relocating DX-NAS Relocating primary storage Relocating the DX-NAS server Relocating data to a new destination Troubleshooting DX-NAS logs Error conditions DX-NAS server is not running EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

5 Contents Network configuration errors Celerra configuration errors NetApp filer issues Small files are not migrated Alerts Appendix B Technical Support Troubleshooting the problem Before contacting EMC Technical details Documenting the problem Reporting a new problem Glossary Index EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide 5

6 Contents 6 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

7 Figures Title Page 1 Migrating Celerra files to secondary storage Migrating NetApp files to secondary storage Migrating files to EMC Centera Migrating files to tertiary storage Celerra restoring files from secondary storage NetApp restoring files from secondary storage Alerts tab in the DX-NAS GUI DiskXtender for NAS Login window DX-NAS GUI main window DX-NAS Server Logs window Save Log dialog box Backup database prompt Audit Trail Wizard Select Report Type list Status bar Filter Alerts Wizard File Attribute Wizard for Microsoft Windows File Attribute Wizard for UNIX/Linux Viewing file status from Windows Explorer Online help icons Relationship of DX-NAS objects in the creation of a job Source and Destination tabs Policies Wizard Readback Method and Match Criteria Four principal elements of a migration policy Policy Wizard Migration policy details page Data Deduplication option EMC Centera migration policy details page Orphan file policy details page Source scan policy details page Preview Job Results windows Preview Job dialog box Jobs in progress details Alerts tab Identifying invalid stub files Backup up database prompt Backup database file (fsmnas.db) and one incremental Stub backup with corresponding secondary storage backup EMC Centera and NetApp require DX-NAS database backup Moving the DX-NAS server from Host 1 to Host File system to file system relocation EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide 7

8 Figures 41 EMC Centera to EMC Centera relocation DX-Windows managed file system to an EMC Centera DXUL FSM-managed file system to an EMC Centera Relocation process flow Export Configuration option EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

9 Tables Title Page 1 Fields on the DX NAS Database Management screen Column definition for the Audit Trail Wizard GUI tabs and their function CLI commands Options for host command Parameters for the source command Parameters for the dest command Parameters for the policy command Parameters for the job command Parameters for the sched command Parameters for the fileattrs command Parameters for the admin command Criteria used to search for files Differences in atime, ctime, mtime, and perm by file system Match criteria options Logical operators Match criteria command examples Primary storage report Secondary storage report Data deduplication report Parameters for the relocate destination utility Errors returned for source host or path issues Errors returned for destination directory issues Common DX-NAS configuration problem EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide 9

10 Tables 10 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

11 Preface As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes. If a product does not function properly or does not function as described in this document, please contact your EMC representative. Audience This document is part of the EMC DiskXtender for NAS (DX-NAS), Release 3.1, documentation set, and is intended for use by trained DX-NAS system administrators. Readers of this document are expected to be familiar with the following topics: EMC Celerra administration EMC Centera administration Celerra FileMover API (formerly known as DHSM) Network Appliance (NetApp) filer administration Solaris, Linux, or Microsoft Windows operating system configuration and management Related documentation Conventions used in this document Related documents include: EMC DiskXtender for NAS Release 3.1 Multiplatform Version Release Notes EMC DiskXtender for NAS Release 3.1 Microsoft Windows Version Installation and Configuration Guide EMC DiskXtender for NAS Release 3.1 UNIX/Linux Version Installation and Configuration Guide EMC DiskXtender for NAS Release 3.1 Theory of Operations EMC DiskXtender for NAS online help EMC AutoStart Module for DiskXtender for NAS Release 3.0 Multiplatform Version Installation Guide Using Celerra FileMover Technical Module EMC uses the following conventions for special notices. Note: A note presents information that is important, but not hazard-related. EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide 11

12 Preface! CAUTION A caution contains information essential to avoid data loss or damage to the system or equipment.! IMPORTANT An important notice contains information essential to operation of the software. Typographical conventions EMC uses the following type style conventions in this document: Normal Used in running (nonprocedural) text for: Names of interface elements (such as names of windows, dialog boxes, buttons, fields, and menus) Names of resources, attributes, pools, Boolean expressions, buttons, DQL statements, keywords, clauses, environment variables, functions, utilities URLs, pathnames, filenames, directory names, computer names, filenames, links, groups, service keys, file systems, notifications Bold Used in running (nonprocedural) text for: Names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, man pages Used in procedures for: Names of interface elements (such as names of windows, dialog boxes, buttons, fields, and menus) What user specifically selects, clicks, presses, or types Italic Used in all text (including procedures) for: Full titles of publications referenced in text Emphasis (for example a new term) Variables Courier Courier bold Used for: System output, such as an error message or script URLs, complete paths, filenames, prompts, and syntax when shown outside of running text Used for: Specific user input (such as commands) Courier italic Used in procedures for: Variables on command line User input variables < > Angle brackets enclose parameter or variable values supplied by the user [ ] Square brackets enclose optional values Vertical bar indicates alternate selections - the bar means or { } Braces indicate content that you must specify (that is, x or y or z)... Ellipses indicate nonessential information omitted from the example Where to get help EMC support, product, and licensing information can be obtained as follows. Product information For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at: 12 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

13 Preface Technical support For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account. Your comments Comments and suggestions about our product documentation are always welcome. To provide feedback: 1. Go to: 2. Click the Feedback link. EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide 13

14 Preface 14 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

15 1 Overview of DiskXtender for NAS This chapter discusses the following topics: How DX-NAS works About DX-NAS architecture and functionality Overview of DiskXtender for NAS 15

16 PS0 PS1 PS2 PS3 PS4 SM B0SM B1 Overview of DiskXtender for NAS How DX-NAS works EMC DiskXtender for NAS (DX-NAS) is a policy engine that migrates files from EMC Celerra storage systems and NetApp filers to secondary storage. When DX-NAS migrates a file, a small file stub is created on the Celerra or NetApp filer. The stub file enables network-attached storage (NAS) clients to continue to access the file in the same location and in the same manner as before. As clients access these file stubs, Celerra can either completely retrieve the migrated file by replacing the file stub with the original file, or access the migrated file on secondary storage and then pass the information through to the client without changing the file stub. (NetApp filers always recall files completely.) NAS clients read and write files to Celerra or NetApp. Independent of this client activity, DX-NAS scans NAS systems for files that should be migrated. These files are identified by policies and match criteria that you create by using either the DX-NAS graphical user interface (GUI) or the DX-NAS command line interface (CLI). When DX-NAS finds a file that needs to be migrated, it moves the file from Celerra or NetApp to secondary storage and leaves a file stub. The stub file contains the location of the file on secondary storage. Figure 1 on page 16 illustrates how the DX-NAS interacts with Celerra to migrate files. NAS clients Celerra 1. Search DX-NAS SB14 SB12 SB6 SB7 SB8 SB9 SB10 SB11 SB15 SB13 2. Read file SB0 SB2 SB4 SB1 SB3 SB5 4. Replace file with Stub file 5. Recall data 3. Write file Secondary storage GEN Figure 1 Migrating Celerra files to secondary storage 16 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

17 PS0 PS1 PS2 PS3 PS4 SM B0SM B1 PS0 PS1 PS2 PS3 PS4 SM B0SM B1 Overview of DiskXtender for NAS Figure 2 on page 17 illustrates how the DX-NAS interacts with NetApp to migrate files. NAS clients NetApp DX-NAS 1. Search 2. Read file 4. Replace file with Stub file 3. Write file 5. Recall data Secondary storage GEN Figure 2 Migrating NetApp files to secondary storage Secondary storage can be Common Internet File System (CIFS) or Network File System (NFS) shares that are accessible by the DX-NAS server. DX-NAS can also migrate files directly to EMC Centera Content Addressed Storage (CAS). Figure 3 on page 17 illustrates migrating files to EMC Centera. NAS clients Celerra or NetApp DX-NAS 1. Search SB14 SB12 SB10 SB12 SB10 SB8 SB15 SB13 SB11 SB13 SB14 SB15 SB11 SB9 2. Read file SB0 SB2 SB4 SB6 SB8 SB0 SB2 SB4 SB6 SB5 SB7 SB9 SB3 SB1 SB1 SB3 SB5 SB7 4. Replace file with Stub file 3. Write file 5. Recall data EMC Centera GEN Figure 3 Migrating files to EMC Centera How DX-NAS works 17

18 PS0 PS1 PS2 PS3 PS4 SM B0SM B1 PS0 PS1 PS2 PS3 PS4 SM B0SM B1 Overview of DiskXtender for NAS Depending on the configuration, DX-NAS can migrate files to tape devices, or tertiary storage. Figure 4 on page 18 illustrates a configuration in which DX-NAS migrates files to secondary storage that is managed by other EMC DiskXtender products such as DiskXtender File System Manager for UNIX/Linux (DX-FSM) or DiskXtender for Windows. NAS Clients Celerra or NetApp DX-NAS SB14 SB14 SB12 SB15 SB15 SB0 SB1 SB2 SB3 SB4 SB5 SB6 SB7 SB13 1. Search SB12 SB10 SB10 SB8 SB13 SB11 SB9 SB0 SB1 SB2 SB3 SB4 SB5 SB6 SB7 SB8 SB9 SB11 2. Read file 4. Replace file with Stub File 3. Write file 5. Recall data Secondary storage CLARiiON ATA Tape/Optical Tertiary storage GEN Figure 4 Migrating files to tertiary storage In some cases DX-NAS is not part of the restore path for migrated files. Celerra retrieves the files directly from secondary storage, or if it is migrating to EMC Centera, the Celerra will go through DX-NAS to recall files. Figure 5 on page 19 illustrates what happens when a NAS client accesses a file stub on the Celerra system. 18 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

19 PS0 PS1 PS2 PS3 PS4 SM B0SM B1 Overview of DiskXtender for NAS (The document Using Celerra FileMover provides more in-depth information about the Celerra FileMover API.) NAS Clients Celerra SB2 SB10 SB12 SB3 SB4 SB5 SB6 SB7 SB8 SB9 SB14 SB15 1. Read Stub file SB11 SB13 FileMover API over HTTP SB0 SB1 Read Read Read DX-NAS DX Windows or FSM-managed Secondary storage Read Secondary storage (shared disk) CLARiiON ATA Tape/Optical EMC Centera Tertiary storage GEN Figure 5 Celerra restoring files from secondary storage How DX-NAS works 19

20 PS0 PS1 PS2 PS3 PS4 SM B0SM B1 Overview of DiskXtender for NAS NetApp, on the other hand, migrates and recalls all data through DX-NAS. Figure 6 on page 20 illustrates what happens when a NAS client accesses a file stub on the NetApp system. NAS Clients NetApp 1. Read Stub file SB0 SB1 SB8 SB10 SB12 SB14 SB9 SB11 SB13 SB15 SB2 SB3 SB4 SB5 SB6 SB7 DX-NAS Read Read DX Windows or FSM-managed Secondary storage Read Secondary storage (shared disk) CLARiiON ATA Tape/Optical EMC Centera Tertiary storage GEN Figure 6 NetApp restoring files from secondary storage Storage space on destination directories The destination directories must have enough storage space to accommodate the migrated files. If you expect more demands for storage capacity for a single destination, you can configure multiple destinations for file migration. Do not migrate files smaller than 50 KB to secondary storage. While there may be many small files on your source, the percentage of total storage that these files represent is usually minimal. Note: To ensure that the destination directory is not approaching maximum capacity, periodically review the Secondary Storage Report from the DX-NAS GUI. About DX-NAS architecture and functionality DX-NAS is installed on a client/server architecture. The client and server software can be installed on Windows, Solaris, or Red Hat Linux platforms. The DX-NAS client uses a TCP/IP connection to the DX-NAS server. The DX-NAS server runs the jobs that move files. 20 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

21 Overview of DiskXtender for NAS The following documentation provides requirements and instructions for installing the DX-NAS client and server software: EMC DiskXtender for NAS Release 3.1 Microsoft Windows Version Installation and Configuration Guide EMC DiskXtender for NAS Release 3.1 UNIX/Linux Version Installation and Configuration Guide EMC DiskXtender for NAS Release 3.1 Multiplatform Version Release Notes User interface The principal configuration tool for DX-NAS is the GUI. From the GUI you can configure and manage migration policies, monitor jobs, view alerts, and view storage reports. A subset of the GUI functionality is provided in the command line interface (CLI). Chapter 2, Using the DX-NAS GUI, and online help provide more information for the DX-NAS GUI. Chapter 3, Using the DX-NAS Command Line Interface, provides more information for the DX-NAS CLI. Jobs DX-NAS uses jobs to migrate files from primary storage to secondary storage. A job consists of the following elements: Source The folder or directory on the Celerra system or NetApp filer where the search engine looks for files to migrate. On Microsoft Windows, a source is specified as a UNC path for example: \\server2\wip On Solaris or Linux, a source is specified as a fully qualified mount point, for example: /Celerra/server2/wip Destination The folder or directory that will hold the migrated files. The DX-NAS server must be able to access the destination in one of the following ways: As a local directory As a UNC path (for CIFS shares on Celerra or NetApp) As a mounted NFS share (for shares on Red Hat Linux and Solaris) As an EMC Centera Policy A description of what files to migrate and how to migrate them. When a policy is created, match criteria is established to identify which files are candidates for migration. This match criteria can be based on a variety of file attributes such as filename, file size, owner, or last modification time. Chapter 5, Specifying Match Criteria for Policies, provides more information on match criteria. After you create jobs you can schedule the DX-NAS server to run the jobs at times that will have the least impact on normal NAS client use. You can create a job from the GUI or the CLI. Online help provides information on creating jobs from the GUI. Chapter 3, Using the DX-NAS Command Line Interface, provides more information on creating jobs from the CLI. About DX-NAS architecture and functionality 21

22 Overview of DiskXtender for NAS Alerts and logs The DX-NAS GUI provides the status of jobs on the Alerts tab as shown in Figure 7 on page 22. Figure 7 Alerts tab in the DX-NAS GUI These alerts are often sufficient to troubleshoot configuration problems with DX-NAS. Appendix A, Troubleshooting, provides more information on what to do for specific alerts. The online help provides more information on managing alerts. Additional information about the operation of DX-NAS is written to the DXNASServerlog_x.log and DXNASLog.log files. If DX-NAS is installed in its default location, the log files can be found in the following locations: On Microsoft Windows, in C:\Program Files\EMC\DXNAS\Server\logs. On Solaris and Linux, /opt/emc/dxnas/server/logs. Appendix A, Troubleshooting, provides more information about DX-NAS logs. Reports The DX-NAS GUI provides historical information about migration activity, deleted orphan files, and storage availability on primary and secondary storage. The following reports are available: Migration Report Shows the number of files migrated and their combined size on a per day or a total-to-date basis. Orphan File Report Shows the number of files deleted on secondary storage that no longer have a valid stub file on primary storage. 22 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

23 Overview of DiskXtender for NAS Primary Storage Report Reports storage used and storage available on source directories. Secondary Storage Report Reports storage used and storage available on destination directories. Data Deduplication Report Reports summary data about the number of files and the amount of storage that has been deduplicated. The report does not provide information about which specific files have been deduplicated. Online help provides more information on reports. Maintenance Common maintenance activities for DX-NAS include the following: Monitor job status The Job tab in the GUI enables you to monitor the status of a running job. Stop a job The Job tab in the GUI enables you to stop a running job. Determine file migration You can use the File Attributes option from the Tools menu to determine whether a source file has been migrated. Note: For a CIFS exported file system, you can also determine if a file has been migrated by using the Windows Explorer. Check primary storage consistency You can create jobs to scan file stubs to determine if the corresponding files located on secondary storage exists and whether they are valid. These jobs are referred to as source scan jobs. Check secondary storage consistency You can create jobs to scan files on specified destination directories to determine if corresponding file stubs on primary storage exist and are valid. These jobs are referred to as orphan file scan jobs. Check the space available on primary and secondary storage You can display primary and secondary storage reports. Online help and Chapter 6, Managing the DX-NAS system, provide more information on maintenance activities. Backup To back up a DX-NAS configuration including the source and destination directories, requires two types of backups: Application Backs up the DX-NAS job configurations and the database of migrated files. (This backup is for DX-NAS components only. No user data is backed up.) Data Backs up the user data on source and destination directories. This enables the recovery of migrated files in the event of data loss. Chapter 7, Backing Up and Restoring DX-NAS, provides more information on backing up DX-NAS. About DX-NAS architecture and functionality 23

24 Overview of DiskXtender for NAS 24 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

25 2 Using the DX-NAS GUI This chapter discusses the following topics: Logging into DX-NAS About the DX-NAS GUI About the status for migrated files About printing Accessing online help Online help provides complete instructions for all functions available from the GUI. Using the DX-NAS GUI 25

26 Using the DX-NAS GUI Logging into DX-NAS The primary tool for configuring and using DX-NAS is the GUI. A subset of the GUI functionality is provided in the command line interface (CLI), which is documented in Chapter 3, Using the DX-NAS Command Line Interface. To log in to the DX-NAS GUI: 1. Do one of the following to start the DX-NAS program: From the Windows Start menu, select All Programs > EMC DX NAS > DX NAS Client CLI. From Solaris or Linux go to /opt/emc/dxnas/client/bin and type:./runclientgui.bin The DiskXtender for NAS Login window appears as shown in Figure 8 on page 26. Figure 8 DiskXtender for NAS Login window 2. In the Hostname field, type the hostname (or TCP/IP address) where the DX-NAS server runs. 3. In the Username field, type the login username. If you are logging in for the first time, or if you have not created other DX-NAS users, type the username system. 4. In the Password field, type the password for the username. Note: If you do not have the password for the user system, contact EMC Customer Support. 5. Click Login. The DX-NAS GUI starts. 26 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

27 Using the DX-NAS GUI Note: After logging in for the first time, you can click the Admin tab to change the password for the system user. About the DX-NAS GUI The DX-NAS GUI is divided into seven principal areas as shown in Figure 9 on page 27. Figure 9 DX-NAS GUI main window Menu bar From the menu bar, you can: Print the current details pane Exit the DX-NAS GUI Refresh the current view Display file attributes on the Celerra system Set log level View server logs Perform database management Backup the DX-NAS database View the migration audit trail Export configuration About the DX-NAS GUI 27

28 Using the DX-NAS GUI Display GUI version number Display online help Print Exit Refresh View File Attributes Set Log Level When you select File > Print, the GUI prints what is visible on the currently displayed tab. Before printing, resize the GUI windows to limit or expand what is visible. When you select File > Exit, the GUI quits. When you select View > Refresh View, the GUI refreshes the tree display pane and the details pane. This information is refreshed on a regular basis. However, to update what appears before the next refresh interval, select View > Refresh View. Multiple client users can connect to the DX-NAS server. If another user creates an object (for example, a source directory or a rule), it will not appear until the next refresh interval or until you choose to refresh. You can also use the Refresh View operation on the Alerts and Reports tabs to display the most recent alerts and migration information. When you select Tools > File attributes, the File Attributes Wizard appears. To display a file s attributes: 1. In the Filename or Filehandle field of the wizard, type the filename whose attributes you want to display. 2. Click Go. The file attributes display. 3. Click Finish. When you select Tools > Set Log Level, the Log Level Wizard appears. From the Log Level list you can select the level of detail the DX-NAS server writes to the server log file. Generally, the log levels are listed from the least amount of information to the most information: Emergency Report information only when a process becomes unusable. This level returns the least amount of information. Alert Report information when action is required and where lack of action could result in the process becoming unusable. Critical Report conditions that prevent the proper operation of a process. Error Report conditions that cause an operation to fail. Warning Report conditions that warn of impending operation failures. Notice Report normal, but significant, conditions. Informational Report informational messages only. Debug Reports most server activity. This level returns the most amount of information. Note: Selection of one of the more verbose logging levels can cause the log files to grow in size very quickly. Because large log files can adversely affect system performance, run in the Debug, Informational, and Notice modes only long enough to complete troubleshooting or testing. Afterwards, copy the log files to a different location, and reset the logs by starting and stopping the DX-NAS server. 28 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

29 Using the DX-NAS GUI The DX-NAS server writes two log files: DXNASLog.log captures any messages or errors that are written to the default output stream. When troubleshooting, examine this file first. DXNASServerLog_x.log captures any messages or errors generated by the DX-NAS server process. If you installed DX-NAS in the default directory, the server logs are located in the following directories: For Microsoft Windows, in C:\Program Files\EMC\DXNAS\Server\logs. For UNIX or Linux, in /opt/emc/dxnas/server/logs. Resetting DX-NAS logs on Microsoft Windows To reset DX-NAS logs on Microsoft Windows: 1. Log in to the machine where you installed the DX-NAS server. Use the same user account that was used to install DX-NAS. 2. From the Windows Start menu, select All Programs > Administrative Tools > Services. 3. In the Services panel, right-click EMC DX NAS Database and click Stop. The Stop Other Services dialog box indicates that this action also stops EMC DX NAS Server service. Note: To use the Windows command line, type: net stop EMC DX NAS Database 4. Click Yes. The services stop. 5. To make copies of the log files, navigate to the C:\Program Files\EMC\DXNAS\Server\logs folder, and copy DXNASServerLog_x.log and DXNASLog.log to a different location. 6. In the Services panel, right-click EMC DX NAS Server and click Start. Note: To use the Windows command line, type: net start EMC DX NAS Server The logs are now reset. Resetting DX-NAS logs on UNIX or Linux To reset DX-NAS logs on UNIX or Linux: 1. Log in as root on the machine where you installed the DX-NAS server. 2. Go to the bin directory: cd /opt/emc/dxnas/server/bin Note: The default installation directory is /opt/emc/dxnas. 3. Type the following commands:./dxnasserver stop./dxnasdb stop 4. If you want to make copies of the log files, navigate to the /opt/emc/dxnas/server/logs subdirectory, and copy DXNASLog and DXNASServerLog_x.log to a different location. About the DX-NAS GUI 29

30 Using the DX-NAS GUI 5. To restart the processes, type the following commands:./opt/emc/dxnas/server/bin/dxnasdb start./opt/emc/dxnas/server/bin/dxnasserver start The logs are now reset. View Server Logs When you select Tools > View Server Logs, the DX NAS Server Logs window appears as shown in Figure 10 on page 30. Figure 10 DX-NAS Server Logs window If there are multiple pages of log information, you can export the information to a file by clicking Save. The Save Log dialog box appears as shown in Figure 11 on page 30. Figure 11 Save Log dialog box 30 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

31 Using the DX-NAS GUI You can also use a text editor to view the contents of the DXNASLog.log file. Log files can be found in the following locations: For Microsoft Windows, in C:\Program Files\EMC\DXNAS\Server\logs. For UNIX or Linux, in /opt/emc/dxnas/server/logs. Database management Table 1 When you select Tools > Database Mgmt, the DX-NAS Database Management window appears. As shown in Table 1 on page 31, you can use this window to delete old alerts from the database. Fields on the DX NAS Database Management screen Field Name Delete Oldest Delete Older Than Description The specified number of oldest alerts will be deleted from the database. Alerts older than the date entered will be deleted from the database. Manually backing up the DX-NAS database DX-NAS keeps the DX-NAS objects (for example, sources, destinations, and policies) and list of migrated files in a database. Selecting Tools > Backup Database from the menu bar enables you to take a point-in-time snapshot of the database. Figure 12 on page 31 shows the backup database prompt. Figure 12 Backup database prompt Details on how to restore a database backup are provided in Restoring the DX-NAS database on page 100.! CAUTION You should back up the DX-NAS database regularly, especially if you are migrating from NetApp or migrating to EMC Centera. A best practice 3is to backup the database every 24 hours. However, if your migration jobs run less frequently than that, backup the database after each migration job. About the DX-NAS GUI 31

32 Using the DX-NAS GUI View Audit Trail When you select Tools > View Audit Trail, the Audit Trail Wizard appears as shown in Figure 13 on page 32. You can review, export, or delete audited events from this wizard. Figure 13 Audit Trail Wizard You must be logged into the system user account to use the View Audit Trail option. The View Audit Trail option is not available if you are logged into other DX-NAS user accounts. Table 2 on page 32 provides a description for each column in the Audit Trail Wizard. Table 2 Column definition for the Audit Trail Wizard Column Select Date Username Object Action Result Action Message Description Checkbox for selecting one or more actions to delete. Date of the selected action. DX-NAS GUI user that initiated the action. DX-NAS object that was created, deleted or accessed. This includes sources, destinations, policies, and jobs. Result of the action that was initiated. More details about the action result. Click Export on the action bar to export the audit trail table to a comma-separated value format (CSV) file on a locally accessible file system. Only the audit trail information that has not been deleted is exported. 32 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

33 Using the DX-NAS GUI Export Configuration When you select Tools > Export Configuration you can export the complete DX-NAS configuration to a file. This file is used for troubleshooting DX-NAS configurations. It is never re-imported. Tabs Table 3 The DX-NAS GUI provides eight tabs. Table 3 on page 33 lists the tabs and their function. GUI tabs and their function Tab Sources Destinations Policies Jobs Schedules Alerts Reports Admin Function Identify the hosts and directories where DX-NAS should search for files that will be copied and set offline. Identify directories on the secondary storage where the files will be copied to. Specify which files will be copied by defining the match criteria and other parameters. Create jobs that will search for files on the Celerra system, copy them to secondary storage, and then set them offline on the Celerra system. Jobs can also be created to perform the following tasks: To identify and delete orphan files on secondary storage. To identify stubs on primary storage that no longer have valid corresponding files on secondary storage. Schedule the times that jobs will be run. View and acknowledge alerts in the system. View and print reports regarding number of files migrated, the number of orphan files deleted, as well as the amount of storage used and available on primary and secondary storage. Perform the administrative tasks of creating, modifying, and deleting users. Action bar Host and Source buttons The action bar located below the tab names displays buttons that can be used to take action on objects in the tree display panel. Only the buttons that are available for the currently selected tab are displayed. To perform an action for an object: 1. Click the object in the tree display. 2. Click the appropriate available button on the action bar. The Source tab contains the following buttons: Host Create a new source host. Source Create a new source directory. Modify Modify a source. Delete Delete a source. Once a source host has been added, you can create new source directories on that host. About the DX-NAS GUI 33

34 Using the DX-NAS GUI New, Modify, and Delete buttons The Destination, Policies, Schedules, and Admin tabs provide the following three buttons: New Create a new object. Modify Modify an existing object. Delete Delete the object. Note: For each tab, object refers to a specific element. For example, if the Admin tab is selected, object refers to a user. Jobs tab buttons Alerts tab buttons Reports tab buttons The Jobs tab contains the following buttons: New Create a new job. Preview List the files that meet the matching criteria identified in the policy that the job is using. Run Run a job. Files meeting the match criteria are copied to secondary storage. Stop Stop a running job. Modify Modify a job. Delete Delete a job. Help Display help for the Jobs tab buttons. The Alerts tab contains the following buttons: Check All Puts a check mark in every box in the Select column. Filter Limits the number of alerts that are displayed. Export Exports the alerts to a comma-delimited list. Ack Acknowledges alerts. If you check the Select box of an alert, or click Check All, and then click Ack, the selected alerts will no longer appear on the Alerts tab. However, DX-NAS keeps all acknowledged alerts in its database. To view acknowledged alerts click Filter and then from the Status field select Acknowledged. To delete alerts from the database, click Tools > Database Management. Delete Deletes selected alerts. To delete all alerts, click Check All, and then click the Delete. Help Displays help for the Alerts columns on the Alerts tab. The Reports tab contains the following buttons: Custom Allows you to choose the host and the source from which to create the report. Table Displays the report information as a table. Chart Displays the report information as a bar graph. Export Exports the report information to a comma-delimited file. 34 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

35 Using the DX-NAS GUI Help Displays help for the report that is currently selected from the Select Report Type list as shown in Figure 14 on page 35. Figure 14 Select Report Type list Tree display pane The tree display pane of the DX-NAS window provides a tree hierarchy for the objects you create. The tree display pane provides a convenient way to select objects for modification or deletion. Online help provides more information on using the tree display pane. Details pane When you click on an object in the tree display pane, the details of that object are displayed in the details pane. The details can be changed by clicking Modify. Note: Some details of an object cannot be changed. If a detail cannot be changed, it will be grayed out in the dialog box. Status bar The bottom of the DX-NAS window provides a status bar. The status bar shows a summary of critical and warning alerts as illustrated in Figure 15 on page 35. Figure 15 Status bar Alerts window The Alerts windows appears by either selecting the Alerts tab or by clicking the View Alerts button. The Alerts tab and View Alerts button are shown in Figure 16 on page 36. About the DX-NAS GUI 35

36 Using the DX-NAS GUI Setting alert filters If the Alerts tab contains too many alerts, reduce the amount of information by using the Filter Alerts Wizard as shown in Figure 16 on page 36. Figure 16 Filter Alerts Wizard To set an alert filter: 1. From the Alerts tab, click Filter. 2. Select the criteria for each list and select Finish. Online help provides more information on filtering alerts. Clearing alert filters To clear an alert filter. 1. From the Alerts tab, click Filter. 2. Click the Filter Off. 3. Click Finish. The filter has now been cleared. 36 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

37 Using the DX-NAS GUI About the status for migrated files When files are migrated from the Celerra or Net App filer system to secondary storage, the status of the file changes from online to offline. The File Attributes Wizard enables you to select a file on the source system and determine if the file is online or offline. If you migrate files from a file system with a CIFS export, you can determine if the file is offline by using the Windows Explorer. Viewing file status from Windows Explorer on page 39 provides more information on viewing offline files from the Windows Explorer. Viewing file status from the File Attributes Wizard To determine if a file has been migrated to secondary storage: 1. From the menu bar select Tools > File Attributes. 2. From the Source Host list, select the Celerra or NetApp system that contains the file whose attributes you want to query. 3. Click Filename. 4. In the Filename field, type the name of the file (include the full path). For UNIX or Linux, enter the relative path to the computer that runs the DX-NAS server. For Windows, the path must be a full UNC path. You can also browse to the file by clicking Browse and then navigating to the file you want to query. 5. Click Go. About the status for migrated files 37

38 Using the DX-NAS GUI The GUI queries the source system and displays the information, as shown in Figure 17 on page 38 and Figure 18 on page 39. Figure 17 File Attribute Wizard for Microsoft Windows 38 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

39 Using the DX-NAS GUI Figure 18 File Attribute Wizard for UNIX/Linux Note: With UNIX or Linux, the offline path is reported relative to the host where the file resides, not the host where the DX-NAS server is installed. Viewing file status from Windows Explorer From Windows Explorer you can determine if a file on a CIFS share has been migrated to secondary storage. Files that are migrated exhibit the following two characteristics: A small, circular icon overlays the file icon. The Attributes column contains an O. The O indicates that the file is offline. To enable the Attributes column: 1. Right-click the Attributes column heading. 2. Select Attributes. About the status for migrated files 39

40 Using the DX-NAS GUI In Figure 19 on page 40 files that contain the icon overlay and the O attribute, indicate that only the stub file remains on the CIFS share. The content (or data) for the file has been migrated to secondary storage. Figure 19 Viewing file status from Windows Explorer In some instances a caching issue related to the Celerra and Windows system may affect the appearance of migrated files in the Windows Explorer. Although the files have been migrated, the files may not contain a file icon overlay or an O attribute designation in the Attributes column. In the event that the file icons for offline files are missing the circular icon overlay or the O in the Attributes column, use the File Attributes Wizard or the fileattrs command from the DX-NAS CLI to determine the file s status. About printing You can print the contents of the details pane by selecting Print from the File menu. This sends the displayed contents to the default printer of the machine that runs DX-NAS. Note: The print function prints only what is visible on the screen. Before printing, resize the DX-NAS window to limit or expand what is visible. Accessing online help When you choose Help > Help from the menu bar, online help appears starting with the Welcome window. The Help button is available on the action bar for the Jobs, Alerts, and Reports tabs. Clicking the Help button displays context sensitive help for the buttons on these action bars. You can also access online help through the Help buttons at the bottom of various dialog boxes and wizards. Clicking these buttons displays context sensitive help for the current dialog box or wizard. 40 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

41 Using the DX-NAS GUI Using Help In the top left-hand corner of the help screen are three icons that provide three ways to access information in the help. Figure 20 on page 41 highlights the Contents, Index, and Search buttons. Figure 20 Online help icons Contents Browse the table of contents. Index Browse the index. Search Find information by entering a word of phrase. Browse the table of contents Browse the index Perform a search Clicking the Contents icon displays the table of contents pane in the left pane. This is the default display. Clicking an entry in the table of contents displays the related information in the right pane. Clicking the Index icon displays the index in the left pane. Clicking entries in the index displays the related information in the right pane. Typing a word or phrase in the Find text box, searches the index related information. Clicking the Search icon displays the Find field. Type a word or text in the Find text box. If the information is in online help, the results are listed in the left pane. Click on an entry in the left pane to display the related information in the right pane.ì Accessing online help 41

42 Using the DX-NAS GUI 42 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

43 3 Using the DX-NAS Command Line Interface This chapter discusses the following topics. Logging into the DX-NAS CLI Creating policies in the CLI Command line syntax and usage Using the DX-NAS Command Line Interface 43

44 Using the DX-NAS Command Line Interface Logging into the DX-NAS CLI This chapter explains how to use the DX-NAS command line interface (CLI). Like the DX-NAS GUI, you can create DX-NAS objects from the command prompt. To run the CLI: For Windows, select Start > All Programs > EMC DX NAS > DX NAS Client CLI. For UNIX or Linux, type:./opt/emc/dxnas/client/bin/runclientcli.bin When the CLI starts, the following screen output appears: EMC DX NAS Command Line Interface Copyright EMC Corporation Unpublished - All rights reserved Enter DXNAS hostname: To log in to the DX-NAS CLI: 1. Type the hostname (or TCP/IP address) of the machine that runs the DX-NAS server. 2. Type the appropriate login username. If you are logging in for the first time, or if you have not created other users, type system for the username. 3. Type the password for the username. If you do not know the system password, contact EMC Customer Service. Example 1 Screen output for an initial login to the DX-NAS CLI EMC DX NAS Command Line Interface Copyright EMC Corporation Unpublished - All rights reserved Enter DXNAS hostname: lava2062.lss.emc.com Enter username: system Enter password: Enter password: Trying to login. Please wait... You are using an evaluation version license which expires in 30 days. Please use a valid license after the evaluation period. Login successful. Wed Sep 26 08:41:53 MDT 2007 DXNAS Ready> 4. To exit the CLI, type exit or press Ctrl-C at the DXNAS Ready prompt. Note: To obtain help from the CLI, type help at the prompt. 44 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

45 Using the DX-NAS Command Line Interface Creating policies in the CLI Creating a policy in the CLI is similar to creating a policy in the GUI. ( Creating policies on page 70 provides instructions for creating a policy from the DX-NAS GUI). In both cases, you must first create sources and destinations. The source and destination are used with the policy command to create polices. Policies can contain match criteria. Policies are then included in jobs that can be scheduled to run at designated times. To create a policy using the CLI: 1. Use the host command to create a source host. 2. Use the source command to create a source. For the hostname option, use the source host created in step Use the dest command to create a destination 4. Use the policy command to create a policy. For the source and dest options, use the source and destinations in steps 2 and 3. To specify the type of policy, use the -type option: -type mig Creates a migration policy. -type orphan Creates an orphan file policy. -type sourcescan Creates a source scan policy. After the policy is created, include it in a job by using the job command. The job can then be run by using the job command. Creating policies in the CLI 45

46 Using the DX-NAS Command Line Interface Figure 21 on page 46 illustrates the steps for creating a policy by using the DX-NAS CLI. In each step, you can see the relationship of the particular DX-NAS object. DXNAS Ready>host -c server229.lab.local -type celerra -user dhsm_user -pass dhsm_user -i "Celerra host from CLI" Source Host Configurations: ========================== SourceHost :server229.lab.local Description=Celerra host from CLI FileMover Username=dhsm_user NAS Filer Type=EMC Celerra DART Hostname=server229.lab.local Number of sources=0 DXNAS Ready>source -c "Celerra CIFS Source" -h server229.lab.local -p \\server229.lab.local\wayne_test\win -i "Celerra CIFS source from CLI" Adding source : Celerra CIFS Source Source Configurations: ========================== Source :Celerra CIFS Source Description=Celerra CIFS source from CLI Sourcehost=server229.lab.local Source path=\\server229.lab.local\wayne_test\win DXNAS Ready>dest -c "Windows Dest for Celerra" -type fs -h TP lab.local -p \\TP lab.local\WinStorage -fmp \\TP lab.local\WinStorage -i "Windows Storage for Celerra referencing a connection string." Destination Configurations: ========================== Destination :Windows Dest for Celerra Type=Disk Filesystem Offline directory=\\tp lab.local\winstorage Description=Windows Storage for Celerra referencing a connection string. Destination path=\\tp lab.local\winstorage Host Name=TP lab.local DXNAS Ready>policy -c "Migrate all.mpg to File System" -type mig -s "Celerra CIFS Source" -dest Windows Dest for Celerra" -mode filemover -rb passthrough -rule "-name *.mpg" -dedup off -i "Migrate to Local Disk" Policy Configurations: ========================== Policy :Migrate all.mpg to File System Migration Source=Celerra CIFS Source Match Criteria= Use data deduplication=false Policy Type=Migration Policy Readback Method=Passthrough Description=Migrate to Local Disk Destination=Windows Dest for Celerra Source Host=server229.lab.local Source Path=\\server229.lab.local\wayne_test\Win Find Match Criteria=-type f -name *.mpg Celerra Offline Directory=\\TP lab.local\WinStorage Destination Path=\\TP lab.local\WinStorage DXNAS Ready>job -c "Migrate MPG" -p "Migrate all.mpg to File System" -m 15 -t 0 -i "Job created from CLI" Job Configurations and Running Jobs: ========================== Job :Migrate MPG Migration Source=Celerra CIFS Source Readback Method=Passthrough Destination=Windows Dest for Celerra Time Limit (minutes)=0.0 Find Match Criteria=-type f -name *.mpg Celerra Offline Directory=\\TP lab.local\WinStorage Match Criteria= Policy Type=Migration Policy Use MD5 deduplication=false Policy=Migrate all.mpg to File System Description=Job created from CLI Source Host=server229.lab.local Source Path=\\server229.lab.local\wayne_test\Win Number of Threads=15 Destination Path=\\TP lab.local\WinStorage Figure 21 Relationship of DX-NAS objects in the creation of a job 46 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

47 Using the DX-NAS Command Line Interface Command line syntax and usage The CLI client enables you to log in to the DX-NAS server, and then issue commands. Table 4 on page 47 provides a list of the commands and their descriptions. Table 4 CLI commands Command host on page 47 source on page 49 dest on page 50 policy on page 54 job on page 60 sched on page 62 fileattrs on page 64 report on page 65 admin on page 66 Description Creates a host that identifies the name of a Celerra Data Mover or the name of a server with the files to migrate. Creates a source that identifies the directory where the DX-NAS server should start searching for files. Creates a destination that identifies a host and directory where files will be migrated. Creates a policy that enables you to specify which files will be copied by defining the match criteria. Creates a job that will search for files and then implements the specified policy on files that fit the match criteria. Creates a schedule that determines the times that jobs will run. Lists file attributes for a file that resides on the Celerra host, which indicates whether the file has been migrated offline. Displays migration reports, orphan file reports, and disk usage on sources and destinations. Provides access to the following administrative functionality of DX-NAS: Display DX-NAS version Export configuration Set log level host Use the host command to list, create, update, or delete a host. A host is the name of a Celerra Data Mover or the name of a server where files you want to migrate are located. List Create Update List information about DX-NAS source host. host -l Create a host entry. host -c <hostname> -type <NAShardware> -user <username> -pass <password> [ -domain <domain> ] [ -i <description> ] Update a host entry. host -u <hostname> [ -user <username> -pass <password> ] [ -i <description> ] Command line syntax and usage 47

48 Using the DX-NAS Command Line Interface Delete Table 5 Delete a host entry. host -d <hostname> Table 5 on page 48 lists the parameters and their description for the host command. Options for host command Option Description -l List all defined DX-NAS hosts. -c hostname Create a DX-NAS host. hostname is the name of the Celerra system or the NetApp filer where your source files reside. For a Celerra host that is supporting CIFS shares, specify the domain name for the host: server2.lab.local For a NetApp host or a Celerra host that is supporting NFS shares, specify just the hostname: server2 The value for this field can be either a name or an IP address. However, be consistent in the use of a name or an IP address. If, for example, an IP address is used, you must use the IP address for all references to the host: In the fstab files and share tab files. For UNC path strings. -u hostname Update a DX-NAS host. hostname is the name of an existing host you want to update. -d hostname Delete a DX-NAS host. hostname is the name of the DX-NAS host you want to delete. Note: A host can only be deleted if there are no DX-NAS sources on the host. -type NAShardware -user username -pass password -domain domain (NetApp only) Specify the host hardware. NAShardware will be one the following options: celerra netapp Specify the DX-NAS user who has sufficient privileges to migrate files from this host. For the Celerra, username is the name of a user who has rights to use the FileMover API on this host. This is the user you configured with the server_user command on the Celerra Control Station. For NetApp filers, enter Administrator. (Do not use root or any other user name.) Specify the password for the DX-NAS source user. Enter the host name of the NetApp filer. -i description Provide a description of the host. Example 2 Using the host command DXNAS Ready>host -c server229.lab.local -type celerra -user dhsm_user -pass mypasswd -i "Celerra host from CLI" SourceHost configurations: ========================== SourceHost :server229.lab.local Description=Celerra host from CLI FileMover Username=dhsm_user NAS Filer Type=EMC Celerra DART Hostname=server229.lab.local Number of sources=0 48 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

49 Using the DX-NAS Command Line Interface DXNAS Ready>host -c lava2048 -type netapp -user Administrator -pass test12 -domain lava2048 -i "NetApp host from CLI" Source Host Configurations: ========================== SourceHost :lava2048 Description=NetApp host from CLI Netapp Username=Administrator Netapp Domain=lava2048 NAS Filer Type=Network Appliance ONTAP Hostname=lava2048 Netapp ONTAP Version=NetApp Release 7.2: Mon Jul 31 14:53:25 PDT 2006 Number of sources=0 DXNAS Ready>host -c server229 -type celerra -user dhsm_user -pass dhsm_user -i "NFS Host" SourceHost configurations: ========================== SourceHost :server229 Description=NFS Filesystem FileMover Username=dhsm_user NAS Filer Type=EMC Celerra DART Hostname=server229 Number of sources=0 source Use the source command to list, create, update, or delete a source. A source identifies the directory on the DX-NAS host where the DX-NAS server starts searching for files. List Create Update Delete List information about DX-NAS sources source -l Create a source entry. source -c <sourcename> -h <hostname> -p <path> [ -i <description> ] Update a source entry. source -u <sourcename> [ -p <path> ] [ -i <description> ] Delete a source directory entry. source -d <sourcename> Table 6 on page 49 provides a list of parameters and their description for the source command. Table 6 Parameters for the source command (page 1 of 2) Parameter Description -l List all defined DX-NAS sources. -c sourcename Create a DX-NAS source. sourcename is an arbitrary name that you choose to identify the DX-NAS source. This name can contain a maximum of 32 characters. The newline (0x0a) or / (slash) cannot be used in the name. -u sourcename Update a DX-NAS source. sourcename is the name of an existing source to update. Command line syntax and usage 49

50 Using the DX-NAS Command Line Interface Table 6 Parameters for the source command (page 2 of 2) Parameter Description -d sourcename Delete a DX-NAS source. sourcename is the name of the source to delete. Note: An entry for a source directory can only be deleted if it is not included in a policy. -h hostname Specify the hostname of the DX-NAS host where the source is located. The DX-NAS host was created by the host command or by the DX-NAS GUI. -p path Specify the path to the source directory. This is the location on the DX-NAS host where you want to start searching for files to migrate. For DX-NAS running on Windows, this path is specified as a UNC path with fully qualified domain name. For DX-NAS running on UNIX or Linux, this path is specified relative to the root of the machine where the DX-NAS server in installed. Note: On UNIX or Linux, the DX-NAS machine may use a mount point that is different than the directory name on the Celerra or the directory name on the host where the source files are located. -i description Provide a description of the source directory entry. Example 3 Using the source command with DX-NAS CLI DXNAS Ready>source -c "Celerra CIFS Source" -h server229.lab.local -p \\server229.lab.local\wayne_test\win -i "Celerra CIFS source from CLI" Adding source : Celerra CIFS Source Source configurations: ========================== Source :Celerra CIFS Source Description=Celerra CIFS source from CLI Sourcehost=server229.lab.local Source path=\\server229.lab.local\wayne_test\win DXNAS Ready>source -c "NetApp CIFS Source" -h lava2048 -p \\lava2048\home -i "NetAPP CIFS source from CLI" Adding source : NetApp CIFS Source Source configurations: ========================== Source :NetApp CIFS Source Description=NetAPP CIFS source from CLI Sourcehost=lava2048 Source path=\\lava2048\home DXNAS Ready>source -c "Celerra NFS" -h server229 -p /Celerra229/Unix -i "NFS source from CLI" Adding source : Celerra NFS Source configurations: ========================== Source :Celerra NFS Description=NFS source from CLI Sourcehost=server229 Source path=/celerra229/unix dest Use the dest command to create, update, or delete a destination. A destination identifies a host and a directory to which files will be copied. 50 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

51 Using the DX-NAS Command Line Interface List Create Update Delete List information about all destinations. dest -l Create a destination directory entry. dest -c <destname> -type <filesystemtype> -h <hostname> -p <path> -fmp <fmpath> [ -addr <centera_address> ] [ -profile <centera_proile_path> ] [ -i <description> ] Update a destination entry. dest -u <destname> [ -h <hostname> ] [ -p <path> ] [ -fmp <fmpath> ] [ -addr <centera_address> ] [ -i <description> ] Delete a destination entry. dest -d <destname> [-l] Table 7 on page 51 provides a list of parameters and their description for the source command Table 7 Parameters for the dest command (page 1 of 2) Parameter Description -l List all defined destination entries. -c destname Create a DX-NAS destination. destname is an arbitrary name that you choose to identify the destination entry. This name can contain a maximum of 32 characters. The newline (0x0a) or / (slash) cannot be used in the name. -u destname Update a DX-NAS destination. destname is the name of the existing destination you want to update. -d destname Delete a DX-NAS destination. destname is the name of the destination to delete. Note: An entry for a destination can be deleted only if it is not included in a job. -type filesystemtype -h hostname (for -type fs only) Specify the type of file system the destination resides on. filesystemtype can be one of the following: fs If the destination to migrate to is a CIFS or NFS filesystem. cas If the destination to migrate to is an EMC Centera device. Specify the hostname where the destination directory resides. For Windows, this is the name of the host with a fully qualified domain name. For example, if the destination were on a host named lava2113 in a domain named lab.local you would enter lava2113.lab.local. The value for this field can be either a name or an IP address. Be consistent in the use of a name or IP address. If, for example, an IP address is used, you must use the IP address for all references to the host: In the fstab files and share tab files. For UNC path strings. Command line syntax and usage 51

52 Using the DX-NAS Command Line Interface Table 7 Parameters for the dest command (page 2 of 2) Parameter -p path (for -type fs only) -fmp fmpath -addr centera_address (for -type cas only) -profile centera_profile_path (for -type cas only) Description Specify the path where you want to migrate files. For Windows, specify a UNC path with the fully qualified domain name of the secondary storage host. For example, instead of specifying a destination path such as \\archiveserver\data, specify \\archiveserver.eng.us\data. (This path does not need to be mapped by the machine that runs the DX-NAS server.) For UNIX or Linux, this is the mount point where the DX-NAS server has mounted the secondary storage. This mount point may have a different name than the directory name on the destination host. Specify the FileMover path or offline directory, which is the path to the destination as seen by Celerra. fmpath is the path Celerra will use to restore the files after they have been migrated. This path should resolve to the same location as one of the connection strings on the Celerra system. For Windows, this path is specified as a UNC path. For UNIX or Linux, this path is specified in a format similar to UNC, which is //hostname/dir_name/dirname. If you are migrating from a NetApp source directory use the value "None" Specify the IP address of the EMC Centera you are using as a destination. centera_address is the IP address of one of the access nodes of the EMC Centera system. You can use multiple access nodes by entering a comma-separated list of access nodes. Specify the path to the EMC Centera profile path. centera_profile_path is the path to the PEA file that the DX-NAS server uses to authenticate to the Celerra. -i description Provide a description of the destination entry.! CAUTION To successfully retrieve migrated files, the entries in -p and -fmp must resolve to the same storage location. To ensure that you can retrieve files, migrate a few sample files to a destination and restore them before you start migrating critical data to the destination. Example 4 Using the dest command with DX-NAS CLI DXNAS Ready>dest -c "Windows Dest for Celerra" -type fs -h TP lab.local -p \\TP lab.local\WinStorage -fmp \\TP lab.local\WinStorage -i "Windows Storage for Celerra referencing a connection string." Destination configurations: ========================== Destination :Windows Dest for Celerra Type=Disk Filesystem Offline directory=\\tp lab.local\winstorage Description=Windows Storage for Celerra referencing a connection string. Destination path=\\tp lab.local\winstorage Host Name=TP lab.local 52 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

53 Using the DX-NAS Command Line Interface DXNAS Ready>dest -c "Windows Dest for NetApp" -type fs -h TP lab.local -p \\TP lab.local\WinStorage -fmp "NONE(No Celerra support)" -i "Windows Storage for NetApp not using a connection string" Destination Configurations: ========================== Destination :Windows Dest for NetApp Type=Disk Filesystem Offline directory=none(no Celerra support) Description=Windows Storage for NetApp not using a connection string Destination path=\\tp lab.local\winstorage Host Name=TP lab.local DXNAS Ready>dest -c "CenteraDest for Celerra" -type cas -fmp " -addr profile \\server229.lab.local\wayne_test\centeraaccess.pea -i "Centera Destination from Command Line" Destination Configurations: ========================== Destination :CenteraDest for Celerra Type=Centera CAS Offline directory= Description=Centera Destination from Command Line Connect Address= Centera internal ID=centera5 Centera Profile Path=\\server229.lab.local\wayne_test\CenteraAccess.pea DXNAS Ready>DXNAS Ready>dest -c "CenteraDest for NetApp" -type cas -fmp "NONE(No Celerra support)" -addr profile \\server229.lab.local\wayne_test\centeraaccess.pea -i "Centera Destination from Command Line" Destination :CenteraDest Type=Centera CAS Offline directory=none(no Celerra support) Description=Centera Destination from Command Line Connect Address= Centera internal ID=centera3 Centera Profile Path=\\server229.lab.local\wayne_test\CenteraAccess.pea DXNAS Ready>dest -c "NFS Destination" -type fs -h lava2114 -p /work/sparcstor -fmp //lava2114/work/sparcstor "NFS storage referencing a connection string" Destination configurations: ========================== Destination :NFS Destination Type=Disk Filesystem Offline directory=//lava2114/work/sparcstor Description= Destination path=/work/sparcstor Host Name=lava2114 DXNAS Ready>dest -c "CenteraDest NFS for Celerra" -type cas -fmp " -addr profile /Celerra229/CenteraAccess.pea -i "Centera Destination from Command Line" Destination Configurations: ========================== Destination :CenteraDest NFS for Celerra Type=Centera CAS Offline directory= Description=Centera Destination from Command Line Connect Address= Centera internal ID=centera5 Centera Profile Path=/Celerra229/CenteraAccess.pea Command line syntax and usage 53

54 Using the DX-NAS Command Line Interface policy Use the policy command to create, update, or delete matching criteria. List policy -l Create Create a policy. Create migration policy (file system) policy -c <policyname> -type mig -s <source> -dest <dest> -rb <full/partial/passthrough> -rule <matchstring> -dedup <on/off> (Celerra only) [ -i <description> ] Create migration policy (EMC Centera) policy -c <policyname> -type mig -s <source> -dest <dest> -mode <filemover/symlink> -rb <full/partial/passthrough> -rule <matchstring> -retention <none/default/class/period/infinite> [ -class <retentionclass> ] [ -period <retentionperiod> ] -collision <Default/ON/OFF> -ebt <embeddedblobthreshold> [ -i <description> ] Create orphan policy policy -c <policyname> -type orphan -dest <dest> -dm <immediate/later> [ -dd <delay > ] [ -df <migdate/orphandate> ] [ -i <description> ] Create source scan policy policy -c <policyname> -type sourcescan -s <source> [ -i <description> ] 54 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

55 Using the DX-NAS Command Line Interface Update Delete Update a policy. Update migration policy (file system) policy -u <policyname> -s <source> -dest <dest> -rb <full/partial/passthrough> -rule <matchstring> -dedup <on/off> (Celerra only) [ -i <description> ] Update migration policy (EMC Centera) policy -u <policyname> -s <source> -dest <dest> -rb <full/partial/passthrough> -rule <matchstring> -retention <none/default/class/period/infinite> -class <retentionclass> -period <retentionperiod> -collision <Default/ON/OFF> -ebt <embeddedblobthreshold> [ -i <description> ] Update orphan policy policy -u <policyname> -dest <dest> -dm <immediate/later> -dd <delay > -df <migdate/orphandate> [ -i <description> ] Update source scan policy policy -u <policyname> -s <source> [ -i <description> ] Delete a policy. policy -d <policyname> Command line syntax and usage 55

56 Using the DX-NAS Command Line Interface Table 8 on page 56 provides the parameters and their description for the policy command. Table 8 Parameters for the policy command (page 1 of 3) Parameter Description -l List all defined policies. -c policyname Create a DX-NAS policy. policyname is the name you choose for the policy. This name can contain a maximum of 32 characters. The newline (0x0a) or / (slash) cannot be used in the name. -u policyname Update a DX-NAS policy. policyname is the name of the policy that you want to update. -d policyname Delete a DX-NAS policy. policyname is the name of a policy you have previously created that you want to delete. Note: A policy can only be deleted if it is not included in a job. -type mig/orphan/sourcescan Specify the policy type. mig/orphan/sourcescan is the type of policy you are creating. There are three options: -type mig Creates a migration policy. -type orphan Creates an orphan file management policy. -type sourcescan Creates a source scan policy. -s source Specify the DX-NAS source. source identifies the name of a previously created source. -dest dest -rb full/partial/passthrough Specify the DX-NAS destination. dest identifies the name of a previously created destination. Specify the readback method. full/partial/passthrough is the readback method you want to use when accessing the stub.there are three options: rb full Celerra or NetApp reads the file on secondary storage and replaces the stub in the source directory with the file. If attempts to recall data produce an error related to insufficient space or quotas, the Celerra will attempt to reread the data using the passthrough mode. Note: As a best practice do not use the full readback method with the Celerra. However, if you do use the full readback method, also set the dedup parameter to on. rb partial Celerra reads the file on secondary storage and restores only the parts of the file that are being accessed by the requesting client. There may be performance advantages to using the partial readback method if using EMC Centera as secondary storage. The disadvantage to using the partial readback method is that the file is still considered offline unless the entire file is read. rb passthrough Celerra reads the file on secondary storage and passes the data to the requesting client without affecting the stub. As a best practice, use the passthrough readback method, if possible. On Celerra, the read policy override parameter for the DHSM connection takes precedence over the value set in the policy. Note: When a file that has been migrated by using the passthrough or partial readback method is opened with a "write access" application such as Microsoft PowerPoint or Excel, the file is recalled to the Celerra. 56 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

57 Using the DX-NAS Command Line Interface Table 8 Parameters for the policy command (page 2 of 3) Parameter -rule matchstring -dedup on/off (for Celerra only) -retention none default class period infinite (for EMC Centera only) -class retentionclass (for EMC Centera only) -period retentionperiod (for EMC Centera only) -collision Default/on/off (for EMC Centera only) Description Specify the match string. matchstring is the match criteria for finding files that are candidates for migration. Use the find command syntax. For example, -rule "-name *.mpg" The entire match string is enclosed in double quotes. If specifying a filename with spaces, use single quotes to enclose the filename. Match criteria commands on page 83 provides more information on match criteria. Specify on to enable data deplication. Data deduplication uses a hashing algorithm that computes a hash value for each file that is migrated. This hashing algorithm enables DX-NAS to keep only a single copy of unique files on secondary storage. Data deplication for DX-NAS works as follows: Files that generate a unique hash value are retained on the back-end file system. Files that generate a non-unique hash value are considered duplicates, and are not copied to the back-end system. Specify off to disable data deplication, if enabled. Specify the retention policy you want the EMC Centera to use. none default class period infinite specifies the EMC Centera retention policy. The retention policy on EMC Centera determines how long files are protected before they are allowed to be deleted. After the retention conditions are met or have expired, the files are not deleted. Instead, EMC Centera enables processes to delete them. There are five options: None The files may be deleted from EMC Centera at any time. Default Retention policies will be applied to the files based on the default retention policy that was set on EMC Centera. Class The migrated files will be assigned to the retention class specified in the Retention Class field. All files assigned to a retention class are managed according to the attributes of that retention class. Period The number of days EMC Centera should retain migrated files. Infinite None of the migrated files will be deleted. Specify the retention class to use. retentionclass is the name of the retention class to use for files migrated to EMC Centera. This class needs to be currently configured on EMC Centera. Specify the retention period. retentionperiod is the number of days EMC Centera should retain the files before they can be deleted. Specify whether you want to use collision avoidance on the EMC Centera. Default/on/off is the collision avoidance setting you want to use. If you set collision avoidance to default, then collision avoidance is handled by whatever is set by default on EMC Centera. If you set collision avoidance on, then identical files on Celerra have only one datafile on EMC Centera. That is, the file stubs created on Celerra all resolve to the same EMC C-Clip and blob in EMC Centera. (This overrides the default setting on EMC Centera.) If you set collision avoidance off, then each identical file has a corresponding data file. That is, the file stubs created on Celerra resolve to separate (but identical) C-Clips and blobs on EMC Centera. (This overrides the default setting on EMC Centera.) Command line syntax and usage 57

58 Using the DX-NAS Command Line Interface Table 8 Parameters for the policy command (page 3 of 3) Parameter -ebt embeddedblobthreshold (for EMC Centera only) -dm immediate/later -dd delay -df migdate/orphandate Description Specify the embedded blob threshold you want to use on the EMC Centera. embeddedblobthreshold is the file size threshold (between 0 KB and 100 KB) for blob embedding. EMC Centera has the ability to embed the data of small files (100 KB or less) in the EMC Centera C-Clip. This option lowers the threshold for blob embedding. For example, if you set this value to 50, then only files that are 50 KB or less will be embedded in the C-Clips. All other files are stored as a C-Clip and separate blob. If you set the embedded blob threshold to 0, no blobs are embedded in C-Clips regardless of their size. Specify the delete type for orphan file policies. immediate/later defines the behavior for the orphan delete policy. Specify immediate to delete all orphan files as soon as they are discovered. Specify later to delete orphan files at a later time in accordance with the -dd option. Specify the delete delay for orphan file policies. delay is the number of days to wait before deleting orphan files. Specify the delete from point for orphan file policies. migdate/orphandate is either migdate The date the orphaned file was first migrated. orphandate The date at which the file was determined to be an orphan. -i description Provide a description of the policy. Example 5 Using the policy command to create migration policies DXNAS Ready>policy -c "Migrate MPG" -type mig -s "Src1" -dest "Dest 1" -mode filemover -rb passthrough -rule "-name *.mpg" -dedup on I Migrate MPGs to local disk" Policy :Migrate MPG Celerra Offline Directory=\\TP lab.local\WinStorage Data Deduplication=true Data Deduplication Algorithm=MD5 Description=Migrate MPGs to local disk Destination=Dest 1 Destination Path=\\TP lab.local\WinStorage Find Match Criteria=-type f -name *.mpg Match Criteria= Migration Source=Src1 Policy Type=Migration Policy Readback Method=Passthrough Source Host=server229.lab.local Source Path=\\server229.lab.local\wayne_test\Win DXNAS Ready>policy -c "Migrate all PDFs to Centera" -type mig -s "Celerra CIFS Source" -dest "CenteraDest for Celerra" -mode filemover -rb passthrough -rule "-name *.pdf" -retention none -collision Default -ebt 0 -i "migrate to Centera" Policy :Migrate all PDFs to Centera Migration Source=Celerra CIFS Source Centera Address= Readback Method=Passthrough Destination=CenteraDest for Celerra Find Match Criteria=-type f -name *.pdf Centera Collision Avoidance Policy=Default Celerra Offline Directory= 58 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

59 Using the DX-NAS Command Line Interface Match Criteria= Policy Type=Migration Policy Description=migrate to Centera Centera Retention Policy=No Retention Source Host=server229.lab.local Source Path=\\server229.lab.local\wayne_test\Win Centera Profile=\\server229.lab.local\wayne_test\CenteraAccess.pea Centera Embedded Blob Threshold (KB)=0 Example 6 Using the policy command to create orphan file policies DXNAS Ready>policy -c "Orphan Scan FileSystem" -type orphan -dest "Windows Dest for Celerra" -dm later -dd 30 -df migdate -rule "-name *" -i "find all orphans on FileSystem" Policy Configurations: ========================== Policy :Orphan Scan FileSystem Delete Immediately?=false Policy Type=Orphan File Policy Description=find all orphans on FileSystem Destination=Windows Dest for Celerra Delete Delay From=Migrate date Delete Delay=30 Destination Path=\\TP lab.local\WinStorage DXNAS Ready>policy -c "Orphan Scan Centera" -type orphan -dest "CenteraDest NFS for Celerra" -dm later -dd 30 -df migdate -i "find all orphans on Centera" Policy Configurations: ========================== Policy :Orphan Scan Centera Delete Immediately?=false Centera Address= ?/Celerra229/CenteraAccess.pea Policy Type=Orphan File Policy Description=find all orphans on Centera Destination=CenteraDest NFS for Celerra Delete Delay From=Migrate date Delete Delay=30 Example 7 Using the policy command to create source scan policies DXNAS Ready>policy -c "CIFS Source Scan" -type sourcescan -s "Celerra CIFS Source" -i "Scan CIFS source" Policy Configurations: ========================== Policy :CIFS Source Scan Policy Type=Source Scan Policy Description=Scan CIFS source Source Host=server229.lab.local Source Path=\\server229.lab.local\wayne_test\Win Source=Celerra CIFS Source DXNAS Ready>policy -c "NFS Source Scan" -type sourcescan -s "Celerra NFS" -i "Scan CIFS source" Policy Configurations: ========================== Policy :NFS Source Scan Policy Type=Source Scan Policy Description=Scan CIFS source Source Host=server229 Source Path=/Celerra229/Unix Source=Celerra NFS Command line syntax and usage 59

60 Using the DX-NAS Command Line Interface job Use the job command to list, create, update, delete, preview, or run a job. List List information about all jobs. job -l Create Update Preview Validate Run Create a job. job Update a job. job Preview a job. job Validate a job. job Run a job. job -c <jobname> -p <policy> -m <threads> -t <time_limit> [ -i <description> ] -u <jobname> -p <policy> -m <threads> [ -t <time_limit> ] [ -i <description> ] -e <jobname> -v <jobname> -r <jobname> Delete Delete a job. job -d <jobname> Table 9 on page 60 provides the parameters and their description for the job command. Table 9 Parameters for the job command (page 1 of 2) Parameter Description -l List all defined jobs. -c jobname Create a DX-NAS job. jobname is the name of the job. This name can contain a maximum of 32 characters. The newline (0x0a) or / (slash) cannot be used in the name. -u jobname Update a DX-NAS job. jobname is the name of a job that you want to update. -v jobname Validate the configuration of a job. jobname is the name of a job that you want to validate. -e jobname Preview a DX-NAS job. jobname is the name of a job that you want to preview. Note: DX-NAS can display no more than 10,000 files. -r jobname Run a DX-NAS job. jobname is the name of a job that you want to run. -d jobname Delete a DX-NAS job. jobname is the name of a job that you want to delete. 60 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

61 Using the DX-NAS Command Line Interface Table 9 Parameters for the job command (page 2 of 2) Parameter Description -p policy Specify the policy you want the job to use. policy is the name of a DX-NAS policy that was created by using policy command or the DX-NAS graphical user interface. -m threads Specify the number of threads you want the job to use. threads is the number of migration threads you want to use when you run the job. This value must be between 1 and 75. Note: The more threads you specify the more files you can migrate in a shorter period of time. Specifying more than 14 threads does not significantly impact performance. If using EMC Centera as secondary storage, you can specify 60 threads. -t time_limit Specify the time_limit in minutes you want to allow for the job to run. Once the time limit is reached, no more files will migrate. Files that may be in the process of migrating will complete, but no new migrations will begin. Setting this option to zero means there is no time limit. -i description Provide a description of the job. Example 8 Using the job command DXNAS Ready>job -c "Mig MPG" -p "Migrate all.mpg to File System" -m 15 -t 0 -i "Job created from CLI" Job Configurations and Running Jobs: ========================== Job :Mig MPG Migration Source=Celerra CIFS Source Readback Method=Passthrough Destination=Windows Dest for Celerra Time Limit (minutes)=0.0 Find Match Criteria=-type f -name *.mpg Celerra Offline Directory=\\TP lab.local\WinStorage Match Criteria= Policy Type=Migration Policy Use MD5 deduplication=false Policy=Migrate all.mpg to File System Description=Job created from CLI Source Host=server229.lab.local Source Path=\\server229.lab.local\wayne_test\Win Number of Threads=15 Destination Path=\\TP lab.local\WinStorage DXNAS Ready>job -e "Mig MPG" Job preview results Source File Name :\\server229.lab.local\wayne_test\win\level2\level3\level4\level5\level6\level7 \Level8\Level9\Level10\knowledge_navigator.mpg File Size :61.8 MB Last Modified Date :08/31/06 06:05 PM Source File Name :\\server229.lab.local\wayne_test\win\knowledge_navigator.mpg File Size :61.8 MB Last Modified Date :08/31/06 06:05 PM Total candidate files : 2 Total bytes for candidate files : MB Average bytes for candidate files : 61.8 MB Command line syntax and usage 61

62 Using the DX-NAS Command Line Interface DXNAS Ready>job -v Mtime The job configuration is valid. sched Use the sched command to create, update, or delete a schedule for a job. List Create Update Delete List all schedules. sched -l Create a schedule. sched -c <schedname> -j <jobname> [ -o jobonce ] [ -h jobhold ] -s <schedule(cron)> [ -i <description> ] Update a schedule. sched -u <schedname> -j <jobname> [ -o jobonce ] [ -h jobhold ] -s <schedule(cron)> [ -i <description> ] Delete a schedule. sched -d <schedname> Table 10 on page 62 lists the parameters and their description for the sched command. Table 10 Parameters for the sched command (page 1 of 2) Parameter Description -l List all defined schedules. -c schedname Create a DX-NAS schedule. schedname is the name of the schedule. This name can contain a maximum of 32 characters. The newline (0x0a) or / (slash) cannot be used in the name. -u schedname Update a DX-NAS schedule. schedname is the name of a schedule you want to update. -d schedname Delete a DX-NAS schedule. schedname is the name of a schedule you want to delete. -j jobname Specify the DX-NAS job you want to schedule. jobname is the name of a job that was created using the job command or the DX-NAS GUI. 62 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

63 Using the DX-NAS Command Line Interface Table 10 Parameters for the sched command (page 2 of 2) Parameter Description -o jobonce Specify the jobonce flag: Yes Run the job only once. No Run the job according to the specified schedule. -h jobhold Specify the jobhold flag: Yes Put a hold on the job. A jobhold prevents a scheduled job from running. No Run the job according to the specified schedule -s schedule(cron) Specify the schedule you want the job to use. schedule(cron) is the time when a job runs using the UNIX crontab time format. For the crontab time format, see contab(1) by using the man command on a Solaris or Linux system. The cron entry consists of five elements: Minute Hour Day of the month Month of the year Day of the week The elements are entered sequentially in a string following the order above. For example, to schedule a job to run every Saturday at 8:30 A.M., the cron syntax would be " Note: On Solaris and Linux, even though the DX-NAS scheduler uses cron syntax, the scheduler does not put scheduled jobs in crontab. DX-NAS uses an internal mechanism to schedule jobs. As a best practice: Do not run more than one migration job against any given Celerra at one time. Do not run more than three migration jobs simultaneously on a single DX-NAS server. Example 9 Using the sched command DXNAS Ready>sched -c "Win Scheduled Job" -j "Mig MPG" -s "34 * * * *" -i "run hourly at 34 minutes past the hour" Schedule Configurations: ========================== Schedule :Win Scheduled Job Description=run hourly at 34 minutes past the hour Job hold=false Minutes after the hour=34 Schedule Frequency=Hourly Run on days=all Days Job =Mig MPG Job once=false DXNAS Ready>sched -c "UNIX Scheduled Job" -j "Orphan File Scan" -o yes -s "30 6 * * 1" -i "run the job once on Monday at 6:30 A.M." Schedule Configurations: ========================== Schedule :UNIX Scheduled Job Day of the week=monday Description=run the job once on Monday at 6:30 A.M. Job hold=false Schedule Frequency=Weekly Job =Orphan File Scan Start time=6:30 AM Job once=true Command line syntax and usage 63

64 Using the DX-NAS Command Line Interface fileattrs Use the fileattrs command to determine if a file on a source host has been set offline. You can query files by either filename or file handle. fileattrs-l -h hostname -fn pathname fileattrs-l -h hostname -fh handle Table 11 on page 64 provides the parameters and their descriptions for the fileattrs command. Table 11 Parameters for the fileattrs command Parameter Description -h hostname hostname is the name of the Celerra or NetApp system where the file to query is located. On Windows, this should be specified with a fully qualified domain name. -fn pathname -fh handle pathname is the full path and filename of the file to query. For Windows, this is a UNC path with a fully qualified domain name for the server. (Celerra Only) handle is the Celerra internal file handle for the file to query. File handles look something like this: Example 10 Using the fileattrs command DXNAS Ready>fileattrs -l -h server229.lab.local -fn "\\server229.lab.local\wayne_test\win\moby Dick 1 a.rtf" ========================== File attributes for: \\server229.lab.local\wayne_test\win\moby Dick 1 a.rtf File Status = OFFLINE Offline Path = cifs://tp lab.local/winstorage/server229.lab.local/0/0/0/14/ cde1357ac7 Readback Method = Passthrough ATIME = MTIME = CTIME = File Size = File Handle = ========================== DXNAS Ready>fileattrs -l -h server229.lab.local -fh ========================== File attributes for: File Status = OFFLINE Offline Path = cifs://tp lab.local/winstorage/server229.lab.local/0/0/0/f/ cde06f1d8d Readback Method = Passthrough ATIME = MTIME = CTIME = File Size = File Handle = ========================== DXNAS Ready>fileattrs -l -h server229 -fn /Celerra229/Unix/level2/galaxy.jpg ========================== File attributes for: /Celerra229/Unix/level2/galaxy.jpg File Status = OFFLINE Offline Path = nfs://lava2114/work/sparcstor/server229/0/0/0/24/ cd 9e Readback Method = Full ATIME = EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

65 Using the DX-NAS Command Line Interface MTIME = CTIME = File Size = File Handle = ========================== report Use the report command to report statistics. report -l -type <mig/orphan/source/dest/dedup> The -type parameter designates what type of report to generate. -type mig Generates a Migration Report. -type orphan Generates an Orphan File Report. -type source Generates a Primary Storage Report. -type dest Generates a Secondary Storage Report. -type dedup Generates a Data Deduplication Report. Note: To determine available storage on EMC Centera, contact EMC Customer Service. The report command does not generate information for a Secondary Storage Report for EMC Centera. Reports on page 94 provides more information on DX-NAS reports. Example 11 Using the report command DXNAS Ready>report -l -type mig Report: Date : Hostname :Any Total storage migrated :70.4 MB Total # files migrated :43 Actual storage migrated :2.0 MB Actual # files migrated : DXNAS Ready>report -l -type orphan Report: DXNAS Ready>report -l -type primary Report: Source :Celerra CIFS Source Source Path :\\server229.lab.local\wayne_test\win Total bytes :9.6 GB Bytes free :6.1 GB Percent (%) used : Source :NetApp CIFS Source Source Path :\\lava2048\home\level2 Total bytes :254.6 MB Bytes free :119.9 MB Percent (%) used : Command line syntax and usage 65

66 Using the DX-NAS Command Line Interface DXNAS Ready>report -l -type secondary Report: Destination :Windows Dest for Celerra Destination Path :\\TP lab.local\WinStorage Total bytes :8.5 GB Bytes free :8.4 GB Percent (%) used : Destination :Windows Dest for NetApp Destination Path :\\TP lab.local\WinStorage Total bytes :8.5 GB Bytes free :8.4 GB Percent (%) used : Destination :CenteraDest Destination Path : ?\\server229.lab.local\wayne_test\wtaylor.pea Total bytes :18.9 TB Bytes free :11.0 TB Percent (%) used : DXNAS Ready>report -l -type dedup Report: Source Host :server229.lab.local Storage Capacity Reclaimed :68.1 MB Instances Eliminated :0 Duplicate Storage % :63 Duplicate File % : admin Use the admin command to determine the version number of DX-NAS, to export configuration, and to set log level. admin -v admin -x <pathname> admin -level <logginglevel> 66 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

67 Using the DX-NAS Command Line Interface Table 12 on page 67 provides the parameters and their descriptions for the fileattrs command. Table 12 Parameters for the admin command Parameter Description -v Displays the version of the DX-NAS server. -x pathname pathname is the full path and filename of the file you want to export the database to. -level logginglevel logginglevel is the level of logging you want the DX-NAS server to use. Logging levels are: Emergency report information only when a process becomes unusable. This is the least verbose logging. Alert report information when action is required and where lack of action could result in the process becoming unusable Critical report conditions that prevent the proper operation of a process Error report conditions which cause an operation to fail Warning report conditions that warn of impending operation failures Notice report normal, but significant, conditions Informational report informational messages only Debug reports most server activity. This is the most verbose logging. Example 12 Using the admin command DXNAS Ready>admin -v EMC Corporation, Hopkinton, Mass. DX NAS Version: 3.1 Build: 1.14 DXNAS Ready>admin -x d:\dxnasdb DXNAS Ready>admin -level Informational Command line syntax and usage 67

68 Using the DX-NAS Command Line Interface 68 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

69 4 Configuring Policies This chapter discusses the following topics: Creating policies Fine tuning policies Configuring Policies 69

70 Configuring Policies Creating policies DX-NAS policies determine what files to migrate and how to migrate them. DX-NAS also uses policies to manage discrepancies between migrated files and their stub files. There are three types of policies: Migration policies identify files to be migrated from primary storage to secondary storage. Orphan file policies identify and delete migrated files on secondary storage that no longer have a valid corresponding stub file on primary storage. Source scan policies identify stub files on primary storage that no longer have valid corresponding files on secondary storage, and ensures consistency between file names and locations on secondary storage with the stub file counterpart on primary storage. Note: Inconsistencies can occurs when files are renamed or stub files are restored from a backup. Policies are created by using either the DX-NAS GUI or the CLI. Creating policies in the CLI on page 45 provides information for creating policies by using the CLI. The migration policy can have the most complexity associated with it while the source scan policy has the least. Migration policies Creating a migration policy consists of defining the following principal elements: 1. The source host and directory that DX-NAS scans. 2. The destination directory on secondary storage where the matching files are copied. The Sources and Destinations tabs shown in Figure 22 on page 70 correspond to elements 1 and 2. Figure 22 Source and Destination tabs 70 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

71 Configuring Policies 3. The readback method (passthrough, partial, full). 4. The match criteria for the scan (for example, *.mpeg). The Readback Method list and Match Criteria panel shown in Figure 23 on page 71 correspond to elements 3 and 4. Figure 23 Policies Wizard Readback Method and Match Criteria Creating policies 71

72 Configuring Policies These four elements are then combined into a policy. Figure 24 on page 72 depicts the four elements of a migration policy: source directory, destination directory, migration mode, and match criteria. Figure 24 Four principal elements of a migration policy To create a migration policy: 1. From the DX-NAS GUI, select the Policies tab. 2. Click New. 72 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

73 Configuring Policies The Policy Wizard appears as shown in Figure 25 on page 73. Figure 25 Policy Wizard 3. Provide the appropriate details on this page. a. Type a name for the policy in the Name text box. b. Type a description for the policy in the Description text box. c. From the Policy Type list, select Migration Policy and then click Next. The migration policy details page appears as shown in Figure 26 on page 73. Figure 26 Migration policy details page Creating policies 73

74 Configuring Policies 4. Provide the appropriate details for the migration policy: a. From the Source list, select the source. b. From the Destination list, select the destination device. Note: An empty Source or Destination list indicates that you have not yet created a source or destination. c. From the Readback Method list, select the appropriate method. Select Passthrough to read or recall a file from secondary storage without affecting the stub file on the Celerra source. The Passthrough readback method pertains only to Celerra source systems. Select Partial to restore only parts of a file from secondary storage. The Partial readback method pertains only to Celerra source systems. Select Full to replace the stub on a Celerra or NetApp source directory when a file is recalled from secondary storage. The Full readback method must be used for NetApp sources. d. Specify the appropriate criteria for Match Criteria and Match String. Online help provides more information for specifying match criteria and strings. e. Click Next. Depending upon the type of back-end storage you selected in step 4, the Policy Wizard displays a specific page. 5. If secondary storage is a Celerra system, the Policy Wizard displays a page that provides the Data Deduplication option as shown in Figure 27 on page 74. Figure 27 Data Deduplication option Click Help to view more information for the Data Deduplication option. To enable data dedplication, select the Data Deduplication checkbox and click Finish. 74 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

75 Configuring Policies 6. If secondary storage is an EMC Centera device, the Policy Wizard displays the Centera migration policy details page as shown in Figure 28 on page 75. Figure 28 EMC Centera migration policy details page Click Help for more information on setting retention. Select the appropriate retention policy details and click Finish. After creating the policy an icon appears under the Migration Policies folder. To use a migration policy requires that you create a job in which you select a specific migration policy. The job can then be scheduled to run at specific times and intervals. Online help provides more information for creating jobs. Orphan file policies Orphan files are files on secondary storage that no longer have valid stub files on primary storage. Files that no longer have corresponding stub files are candidates to consider for deletion. An orphan file policy enables you to specify one of two methods of deletion: The Delete immediately option deletes orphan files as soon as they are found by the job running the orphan file policy. The Delete later option deletes orphan files at a specific time by specifying a date and number of days. To create an orphan file policy: 1. From the DX-NAS GUI, select the Policies tab. 2. Click New. The Policy Wizard appears as shown in Figure 25 on page Provide the appropriate details on this page. a. Type a name for the policy in the Name text box. b. Type a description for the policy in the Description text box. c. From the Policy Type list, select Orphan File Policy and then click Next. Creating policies 75

76 Configuring Policies The orphan policy details page appears as shown in Figure 29 on page 76. Figure 29 Orphan file policy details page 4. Provide the orphan policy details: a. From the Destination list, select the appropriate destination. b. Select a Delete Policy. In Figure 29 on page 76 the Delete later option is selected. This option enables you to specify the number days before orphan files are deleted: 1. Type the number of days in the Delete Delay text box. 2. Select either Orphan date or Migrate date from the days after drop-down list. c. Click Finish. An icon for the orphan file policy appears under the Orphan File Policies folder. Orphan files can also be deleted interactively from the Preview Job Results window in the GUI. Online help provides more information on using this feature. Source scan policies A source scan policy enables you to identify stub files on primary storage that no longer have a corresponding file on secondary storage. To create a source scan policy: 1. From the DX-NAS GUI, select the Policies tab. 2. Click New. The Policy Wizard appears as shown in Figure 25 on page Provide the appropriate details on this page. a. Type a name for the policy in the Name text box. b. Type a description for the policy in the Description text box. c. From the Policy Type list, select Orphan File Policy and then click Next. 76 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

77 Configuring Policies The source scan policy details page appears as shown in Figure 30 on page 77 Figure 30 Source scan policy details page 4. Select a source from the Source list and then click Finish. When a source scan job runs, DX-NAS scans that source specified by the source scan policy. Fine tuning policies After you have established the match criteria for a migration or orphan file policy, you can use the job preview functionality of the DX-NAS GUI or CLI to fine tune the policy. This enables you to see what files fit your match criteria as well as to determine how much data will be migrated. Note: A job preview feature can display up to 10,000 files. Fine tuning with the GUI In the GUI, the results of the Preview option can be displayed on two tabs: Summary File List The Summary tab displays the following information: Total number of files (that are not currently offline) that fit the match criteria. Total number of bytes in all files that fit the match criteria. Average size of matching files. Fine tuning policies 77

78 Configuring Policies Figure 31 on page 78 shows the job results for a migration job. Figure 31 Preview Job Results windows This information can be useful when determining the space requirements for secondary storage. The Preview Job dialog box contains the Summary data only checkbox as shown in Figure 32 on page 78. Figure 32 Preview Job dialog box By clearing the Summary data only check box, the job preview returns a list of files that fit the match criteria. By examining this list, you can determine if the match criteria is returning the expected results. Through an iterative process of setting the match criteria in the policy, and then running a preview of a job that incorporates that policy, you can ensure that the policy finds only the files you want to migrate. Fine tuning with the CLI With the CLI, you can preview jobs by using the -e option of the job command. From the command prompt, type: job -e <jobname> 78 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

79 Configuring Policies Where jobname is the name of the job you want to preview. The CLI displays files that fit the match criteria of the job. Example 13 on page 79 illustrates the job - e command. Example 13 Using the job -e command DXNAS Ready>job -e "Migrate TIF Files" Job preview results Source File Name :\\server227.lab.local\wayne1\win\galaxy.tif File Size :62.92 MB Last Modified Date :10/31/07 11:26 AM Source File Name :\\server227.lab.local\wayne1\win\zdmcwin\pillars.tif File Size :8.022 MB Last Modified Date :10/9/07 11:27 AM Source File Name :\\server227.lab.local\wayne1\win\zdmcwin\globelogo.tif File Size :5.081 MB Last Modified Date :10/19/07 11:17 AM Total candidate files : 3 Total bytes for candidate files : MB Average bytes for candidate files : MB Fine tuning policies 79

80 Configuring Policies 80 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

81 5 Specifying Match Criteria for Policies This chapter discusses the following topics: Match criteria search methods Match criteria commands Specifying Match Criteria for Policies 81

82 Specifying Match Criteria for Policies Match criteria search methods A policy provides the match criteria to use when DX-NAS searches the files located on the Celerra device or on other source directories. The search mechanism for DX-NAS is based on the UNIX find command. When DX-NAS conducts a search, it uses match criteria to determine what files to assemble for migration. Table 13 on page 82 provides a list of attributes that DX-NAS uses to search for files. Table 13 Criteria used to search for files Attribute name size user Description Search for files of a specific name or extension. Search for files that are at or above a specified size. (If using KB, MB, or GB, note that these values are 1024, , and , respectively. Search for files that belong to a specified user. Note: The user attribute is not supported on CIFS file systems. group Search for files that belong to a specified group. Note: The group attribute is not supported on CIFS file systems. accessed date (atime) change time or create time (ctime) modified date (mtime) file permissions (perm) Search for files based on when they were last accessed. On NFS file systems, you can search for files based on when their attributes changed. On CIFS file systems, you can search for files based on when they were created. Search for files based on when they were modified. Search for file based on their file permissions. Note: The perm attribute is not supported pn CIFS file systems. DX-NAS begins the search in the directory specified as the source directory and searches each of its subdirectories. Every file matching the search criteria is migrated to secondary storage according to the requirements of the migration policy. The atime, ctime, mtime, and perm file attributes might yield different results depending on whether DX-NAS is scanning an NFS file system or a CIFS file system: Table 14 on page 82 provides a description for each of these attributes by file system. Table 14 Differences in atime, ctime, mtime, and perm by file system Attribute NFS file system CIFS file system atime Date and time the file was last accessed. Date and time the file was last accessed. ctime Date and time the attributes of the file were last changed. Date and time the file was created. mtime Date and time the file was last modified. Date and time the file was last modified. perm Standard UNIX permissions. Not supported on CIFS file systems. 82 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

83 Specifying Match Criteria for Policies Match criteria commands Match criteria is the rule or pattern that DX-NAS uses to identify the files you want migrate. Table 15 on page 83 provides match criteria that can be specified for the Match String text box in the Policy Wizard. Table 15 Match criteria options (page 1 of 2) Options -name -size -user Description Full or partial text of the filename, which can include wildcards, for example: "-name *.mpeg" Length of the file in bytes. For example, to find files that are larger than 5 MB, type something similar to the following: "-size> c" To determine file size from the Windows Explorer, right-click the file and select Properties. The correct size of the file is specified in the Properties dialog box. Do not use the size specified in the Size column of the Explorer window. Name of the user who owns the file, for example: "-user zkodai" Note: The -user option is not supported on CIFS file systems. -group Name of the group for the user who created the file, for example: "-group dev" Note: The -group option is not supported on CIFS file systems. -atime Match files based on the last access time. The integer value entered with this option represents "days ago," and the precision is a 24-hour period. Example of access time older than 15 days ago: "-atime +15" Example of an access time of 2 days ago: "-atime 2" Match criteria commands 83

84 Specifying Match Criteria for Policies Table 15 Match criteria options (page 2 of 2) Options Description -ctime For CIFS, match files based on create time. For NFS, match files based on when the attributes of the file were modified. The integer value enter with this option represents "days ago," and the precision is a 24-hour period. Example of a file create time less than 30 days ago on CIFS: "-ctime -30" Example of an file attribute change time of 3 days ago on NFS: "-ctime 3" -mtime -perm Match files based on time modified. The integer value enter with this option represents "days ago," and the precision is a 24-hour period. Example of mtime set to match files that were modified 120 days ago: "-mtime 120" Example of mtime being set to match files that were modified less than 3 days ago. "-mtime -3" Match files based on user or group ownership. Example of perm being set to match files with permissions of 755: "-perm 755" Note: The -perm option is not supported on CIFS file systems. In addition to match criteria, Table 16 on page 84 describes three logical operators that you can use to modify the behavior of the search. Table 16 Logical operators Operator AND OR Description Performs a logical AND on two or more expressions. All match criteria grouped with AND must be true for a file to match. Performs a logical OR on two or more expressions. If a file matches any of the match criteria grouped with OR it will be considered a match.! (NOT) Negates the results of an expression or logical operation. To constrain the behavior of the logical operators, use parentheses to group expressions together. Table 17 on page 84 provides command examples for match criteria. Table 17 Match criteria command examples (page 1 of 2) Command "-name *.mpeg" "-name *.mpeg -o -name *.mpg" Description Find all files with an mpeg extension. Find all files with an mpeg or mpg extension. Note: Place a leading space before -name and the trailing space after *.mpg. "-name *.mpeg -a -size c" Find all files with an mpeg extension that are greater than 1 GB. 84 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

85 Specifying Match Criteria for Policies Table 17 Match criteria command examples (page 2 of 2) Command "-atime +15 -a -size c" "-name *.db -a -mtime +30" "-name *.mpeg -a -size c -a -mtime +30" "( -name *.mpeg -a! -name *current*.mpeg ) -a -size c -a -atime +90" Description Find all files that have not been accessed for 15 days or more and are larger than 500 MB. Find all files with a db extension that were modified 30 or more days ago. Find all files with an mpeg extension that are greater than 100 MB, but that have not been modified for 30 days or more. Find all files with an mpeg extension, except those with "current" in their name that are smaller than 100 MB, and have not been accessed for the last 90 days. Match criteria commands 85

86 Specifying Match Criteria for Policies 86 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

87 6 Managing the DX-NAS system This chapter discusses the following topics: Monitoring the progress of a running job DX-NAS properties file File migration status Storage file management Orphan file management Reports Managing the DX-NAS system 87

88 Managing the DX-NAS system Monitoring the progress of a running job After you start using DX-NAS to migrate jobs, you can monitor the status of jobs, or the status of resources that these jobs are using. Consequently, there is maintenance that you can perform to understand the state of the system or to optimize the use of resources. You can monitor the progress of running jobs from the Jobs tab in the DX-NAS GUI. To display the details for a job that is currently running: 1. Select the Jobs tab. 2. Select the Jobs in progress folder and click the icon for the job. Figure 33 on page 88 shows the details for the Full Migration job. Figure 33 Jobs in progress details The job progress details are updated every three seconds. How to stop a running job To stop a job: 1. Select the Jobs tab. 2. Select the Jobs in progress folder and click the icon for the job that you want to stop. 3. Click Stop. A confirmation dialog box appears. 4. Click Yes. 88 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

89 Managing the DX-NAS system Note: The job continues to run until you click Yes. DX-NAS stops the job, and then returns to the job display. When you click Stop, there might be a delay before the DX-NAS services respond to the stop request. In most cases this delay occurs if a job is performing an extensive search, and it is not finding matches. In this case, the GUI may take a long time to respond. If the GUI stops responding while waiting on a stop request, wait for the job to stop. To continue working with DX-NAS, start another instance of the GUI. DX-NAS properties file You can control certain configuration options by modifying the DX-NAS properties file: Setting the maximum errors allowed per job on page 89. Setting the port for DX-NAS on page 89. Setting the GUI and CLI logout period on page 90. Enabling job logging on page 90. Setting the maximum number of threads on page 90. Setting the high or low watermark for job threads on page 90. Excluding subdirectories from search on page 91. Excluding subdirectories for orphan file jobs on page 91. The properties file is called env.properties and by default, is located in the following directories: On Windows, in C:\Program Files\EMC\DXNAS\Server\properties. On UNIX or Linux, in /opt/emc/dxnas/server/properties and /opt/emc/dxnas/client/properties. Note: A separate env.properties file exists for both the DX-NAS server and client. In most cases, these files are independent of each other. However, if you edit the rmi.ports parameter in one file, you will have to edit it in the other. Setting the maximum errors allowed per job As you run jobs there may be files that do not migrate successfully. By default, if more than 30 errors occur while running a job, the job is aborted. However, you can change this threshold by modifying the max.job.errors value in the env.properties file. For example, to allow 75 errors per job, modify the env.properties file as follows: max.job.errors=75 Setting the port for DX-NAS By default, the DX-NAS uses port for communication between the server and client. If you need to change this port for a security reason or any other reason that DX-NAS properties file 89

90 Managing the DX-NAS system prohibits you from using port 11001, modify the rmi.port value in the env.properties file. For example, to use port for DX-NAS, modify the env.properties file as follows: rmi.port=10001 To implement a modification to the port, you must modify the env.properties file for both the server and client. Setting the GUI and CLI logout period If you are using the DX-NAS GUI or CLI, and there is no mouse or keyboard activity for 60 minutes, the GUI or CLI logs out. You can increase or shorten this logout period by modifying the gui.logout.period value in the env.properties file. For example, to shorten the GUI or CLI logout period to 15 minutes, modify the env.properties file as follows: gui.logout.period=15 Enabling job logging To view details for migration jobs, orphan jobs, and source scan jobs, set the job.logging value to ON. For a migration job, the log file will contain all files migrated during the job. For an orphan job, the log file will contain the names of all orphan files that have been deleted. For EMC Centera, the log file also includes files that are not deleted because of a retention policy, as well as files that are deleted. To enable job logging, modify the env.properties file as follows: job.logging=on Setting the maximum number of threads Multiple jobs that run simultaneously on the DX-NAS server can use a total of 200 threads. (The default maximum number of threads is set to 200.) To augment the throughput for jobs, you can increase the number of job threads by editing global.max.job threads in the env.properties file. The value you specify for global.max.jobthreads, however, is dependent upon how powerful the CPU is and how much memory the system has. Before increasing the value for global.max.jobthreads, make sure you have adequate CPU power and memory. For most DX-NAS installations, the default value of 200 is sufficient. Setting the high or low watermark for job threads Each job that runs uses working threads. Working threads are stored in a waiting queue until they are needed by the process that runs a job. The DX-NAS server includes two parameters in the env.properties file that specify the high and low watermarks for working threads: The waiting.workers.highwatermark parameter specifies the maximum number of working threads that can be in the waiting queue. Once the maximum number of working threads is reached, no more working threads can be added to the waiting queue. 90 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

91 Managing the DX-NAS system The default value for waiting.workers.highwatermark is 200 threads, which is usually sufficient for most DX-NAS installations. The waiting.workers.lowwatermark parameter specifies the minimum number of working threads that are kept in the waiting queue. Once the amount of working threads falls below this value, more working threads are added to the waiting queue. The default value for waiting.workers.lowwatermark is 100 threads, which is usually sufficient for most DX-NAS installations. Excluding subdirectories from search The default migration and source scan behavior for DX-NAS is to search a source folder and all its subdirectories. However, it is possible to exclude subdirectories from the search by entering the directories to exclude as a colon-delimited list on the migrate.exclude.filepath line in the env.properties file. For example, to exclude any directories named archive, modify the env.properties file as follows: migrate.exclude.filepath=.etc:.ckpt:lost+found:archive Excluding subdirectories for orphan file jobs The default orphan file scan behavior for DX-NAS is to search a destination folder and all its subdirectories. However, it is possible to exclude subdirectories from the search by entering the exclude directories as a colon-delimited list on the orphan.exclude.filepath line in the env.properties file. For example, to exclude any directories named.snapshot, modify the env.properties file as follows: orphan.exclude.filepath=.etc:.ckpt:lost+found:.snapshot File migration status To determine if a source file has been migrated, you can perform a file attribute check from the DX-NAS GUI or CLI. A file attribute check enables you to specify a file on the Celerra or NetApp source and determine if that file is online or offline. Viewing offline files from the File Attributes Wizard To determine if a file has been migrated to secondary storage use the File Attributes Wizard. Viewing file status from the File Attributes Wizard on page 37 provides complete details for running the File Attributes Wizard. File migration status 91

92 Managing the DX-NAS system Viewing offline files by using the DX-NAS CLI To determine if a file has been migrated to secondary storage: 1. Log in to the DX-NAS CLI. 2. Type the fileattrs command at the prompt. fileattrs on page 64 provides more information for using this command. Example 14 on page 92 illustrates the information that the fileattrs command returns on Windows. Example 15 on page 92 illustrates the information that the fileattrs command returns on UNIX or Linux. Example 14 File attribute information from the DX-NAS CLI on Windows DXNAS Ready>fileattrs -l -h server229.lab.local -fn "\\server229.lab.local\wayne_test\win\moby Dick 1 a.rtf" ========================== File attributes for: \\server229.lab.local\wayne_test\win\moby Dick 1 a.rtf File Status = OFFLINE Offline Path = cifs://tp lab.local/winstorage/server229.lab.local/0/0/0/14/ cde1357ac7 Readback Method = Passthrough ATIME = MTIME = CTIME = File Size = File Handle = Example 15 File attribute information from the DX-NAS CLI on UNIX or Linux DXNAS Ready>fileattrs -l -h server229 -fn /Celerra229/Unix/level2/galaxy.jpg ========================== File attributes for: /Celerra229/Unix/level2/galaxy.jpg File Status = OFFLINE Offline Path = nfs://lava2114/work/sparcstor/server229/0/0/0/24/ cd 9e Readback Method = Full ATIME = MTIME = CTIME = File Size = File Handle = Storage file management You can create jobs that scan migrated file stubs on specified source directories to determine if the corresponding files on secondary storage exist and are valid. When a file is migrated, a stub is created on primary storage and a corresponding copy of the file is placed on secondary storage. However, over time, stubs and their corresponding files can get out of sync and require maintenance. If a migrated file is moved or removed from secondary storage, the stub on the source becomes invalid. By running a source scan job, you can identify which primary stubs are invalid. 92 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

93 Managing the DX-NAS system Source stubs that are missing a valid secondary storage file are reported on the Alerts tab as errors as shown in Figure 34 on page 93. Figure 34 Alerts tab Identifying invalid stub files Creating source scan policies To create a source scan policy: 1. In the DX-NAS GUI, click the Policies tab. 2. Click New. 3. In the Name field, type a name for the source scan policy. 4. In the Description field, type a description of the source scan policy. 5. From the list box in the Policy Type field, select Source Scan Policy. 6. Click Next. 7. From the Source list, select the source you want to scan. 8. Click Finish. When the source scan policy is created, an icon representing the source scan policy appears in the policies tree under the Source Scan Policies heading. To create a source scan policy by using the CLI, see Creating policies in the CLI on page 45. Storage file management 93

94 Managing the DX-NAS system Running a source scan policy After creating a source scan policy, include it in a job. The method for doing this is exactly the same as including any other policy in a job. Online help explains how to create a job. After the source scan job has been created, you can run it as you would any other job. Note: Job preview is not available for jobs that implement source scan policies. As the job runs it reports any source stubs without valid secondary storage files as errors on the Alerts tab. If the reported filenames are too long to view easily on the screen, export the alerts to a comma-delimited file, and then print or view them from a word processor or spreadsheet application. Orphan file management If something happens to the stub file located on primary storage, for example, the stub file is deleted, the corresponding file located on secondary storage is no longer accessible. A file located on secondary storage that no longer has an associated stub file is called an orphan file. Orphan files are created in the following ways: A file is migrated with the full readback method and then accessed on primary storage. This causes the file to be restored, which replaces the stub in the source directory with the complete file. The file now exists in two places. If the file is migrated a second time, a new version of the file is copied to secondary storage, and the first copy becomes an orphan file. A migrated file has another version that is saved over it (for example, in a restore from backup scenario). In this case the file on secondary storage is no longer a valid copy of the file, and becomes an orphan file. A migrated file is deleted from primary storage. In this case, the file still exists on secondary storage. However, no stub exists to access it. The file on secondary storage becomes an orphan file. To manage orphan files, create an orphan file policy that scans secondary storage for orphan files. Orphan file policies on page 75 provides more information on orphan file policies. Reports The DX-NAS software provides a reporting function that enables you to view details about the DX-NAS system. You can view reports from either the DX-NAS GUI or CLI. Chapter 3, Using the DX-NAS Command Line Interface, provides details on using the report command. Viewing a migration report The migration report provides details about the number of files migrated. By default, the report appears as a bar chart and shows migration activity for the past seven days. To view a migration report: 1. From the DX-NAS GUI, select the Reports tab 2. From the Select Report Type list, select Migration Report. 94 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

95 Managing the DX-NAS system The GUI displays details for the migration report in a bar chart. Online help provides more information about the migration report. Viewing an orphan file report The orphan file report provides details on files deleted by an orphan file job. To view an orphan file report: 1. From the DX-NAS GUI, select the Reports tab. 2. From the Select Report Type list, select Orphan File Report. The GUI displays details for the orphan file report in a bar chart. Online help provides more information about the orphan file report. Viewing a primary storage report Table 18 The primary storage report provides information for the amount of storage used and the amount of storage available on each DX-NAS source. To view a primary storage report: 1. In the DX-NAS GUI, click the Reports tab. 2. From the Select report type list, select Primary Storage Report. The primary storage report appears as a table with five columns. Table 18 on page 95 provides a description of each column. Primary storage report Column Source Description DX-NAS source. This is the name the DX-NAS source object was given when it was created. Source Path For Windows, a UNC path that displays the hostname and file system where the source files are located. For Solaris, the path (on the machine that runs the DX-NAS server) where the source is mounted. Total Bytes Bytes free Percent (%) used Total number of bytes available on the source file system. Number of bytes Celerra is reporting as being free on the file system. Percentage of total available bytes that are in use on the source file system. Viewing a secondary storage report The secondary storage report provides information for the amount of storage used and the amount of storage available on each DX-NAS destination. To view the secondary storage report: 1. In the DX-NAS GUI, click the Reports tab. 2. From the Select report type list, select Secondary Storage Report. The GUI displays the secondary storage report. Reports 95

96 Managing the DX-NAS system The secondary storage report appears as a table with five columns. Table 19 on page 96 provides a description of each column. Table 19 Secondary storage report Column Destination Description DX-NAS destination. This is the name the DX-NAS destination object was given when it was created. Destination Path For Windows, a UNC path that displays the hostname and file system where the destination files are located. For Solaris, the path (on the machine that runs the DX-NAS server) where the destination is mounted. Total Bytes Bytes free Percent (%) used Total number of bytes available on the secondary storage host. Number bytes the secondary storage host is reporting as being free on the volume where the secondary storage directory is located. Percentage of total available bytes that are in use on the volume where the secondary storage directory is located. Viewing a data deduplication report The data deduplication report provides summary data about the number of files and the amount of storage that has been deduplicated. The report does not provide information about which specific files have been deduplicated. To view an data deduplication report: 1. From the DX-NAS GUI, select the Reports tab 2. From the Select Report Type list, select Data Deduplication Report. The GUI displays details for the orphan file report in a bar chart. The data deduplication report appears as a table with five columns. Table 20 on page 96 provides a description of each column. Table 20 Data deduplication report Column Source Host Storage Capacity Reclaimed Instances Eliminated Duplicate Storage % Duplicate File % Description Celerra that is being deduplicated. Amount of primary storage that has been freed by migrating files with data deduplication enabled. Number of duplicate file instances that have been set offline by migrating files with data deduplication enabled. The files have not actually been eliminated, rather they have been set offline and a stub has been left on primary storage. Percentage of migrated storage that is single-instanced data. Percentage of migrated files that were duplicate files. 96 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

97 7 Backing Up and Restoring DX-NAS This chapter discusses the following topics: Backing up the DX-NAS database Restoring the DX-NAS database Backing up primary and secondary storage Backing Up and Restoring DX-NAS 97

98 Backing Up and Restoring DX-NAS Backing up the DX-NAS database DX-NAS keeps its objects (sources, destinations, policies) and list of migrated files in the DX-NAS database. You should back up the DX-NAS database regularly, especially if you are migrating files from a NetApp filer or to EMC Centera. A best practice is to back up the database every 24 hours. However, if migration jobs run less frequently, back up the database after each migration job. DX-NAS provides two methods to back up the DX-NAS database: from the GUI or from the command line. Backing up the database from the GUI The GUI enables you to perform a point-in-time snapshot of the database: 1. From the GUI, select Tools > Backup Database to create a point-in-time snapshot of the database. Figure 35 on page 98 shows the backup database prompt. Figure 35 Backup up database prompt 2. Click Yes. Backups are stored in directories that are named based on a time stamp of when the backup was taken. Depending on the system type, backups are stored in the following directories on the DX-NAS server: For Windows, in C:\Program Files\EMC\DXNAS\Server\database\backup. For UNIX or Linux, in /opt/emc/dxnas/server/database/backup. The Backup Database option creates the backup in the default location. You cannot specify a different location. Also, this type of backup cannot be scheduled. To schedule a database backup you must use the SetupDbBackup script from the command line. Backing up the database from the command line on page 98 provides more information. Backing up the database from the command line Release 3.1 enables you to backup the DX-NAS database from the command line by using the SetupDbBackup script on UNIX/Linux or SetupDbBackup.bat on Microsoft Windows. By using SetupDbBackup you can specify a location to place the database backups and set a time for running backups. The backup script automatically performs both incremental and full backups. Incremental backups are scheduled to run from Sunday through Friday. Full backups are scheduled to run on Saturday. The backup script is located in the following directories: On Windows, in C:\Program Files\EMC\DXNAS\Server\bin. On UNIX or Linux, in /opt/emc/dxnas/server/bin. 98 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

99 Backing Up and Restoring DX-NAS The usage information for SetupDbBackup is: USAGE: SetupDbBackup <backupdir> [time] backupdir where to place database backups. time - time to run backup (format HH:MM, example 21:00) Both incremental and full backups are placed in the directory that you specify with the SetupDbBackup script. The location you specify can be either a local or remote location. On UNIX or Linux you must mount the location before you run the SetupDbBackup script. The time parameter is optional. If you do not specify a time, the backup uses the default time, 21:00 (9:00 P.M.). The time must be specified by using a 24-hour clock format. The script creates a new folder and backup file each time a backup runs. Folder names comprise the current date of the backup, for example, Incremental backup files also comprise the current date of the backup, for example, AA.LOG. Full backups of the database use the actual filename, fsmnas.db. The database backup process persists across a system reboot. Restoring database backups from the command line on page 101 provides instructions for restoring the DX-NAS database. Running SetupDbBackup.bat on Microsoft Windows To run SetupDbBackup.bat: 1. Log in to the DX-NAS server as an administrator. 2. Open the Windows Command Prompt. 3. Change the directory to Program Files\EMC\DXNAS\Server\bin and type: SetupDbBackup.bat backupdir time For example, to back up the DX-NAS database to a remote folder at 10:00 A.M., the command syntax would be: SetupDbBackup.bat \\lava2178.lab.local\transfer\dbbackup 10:00 If you run the backup script on Saturday after 10:00 A.M., a full backup of the DX-NAS database would run the next day (Sunday) at 10:00 A.M. The SetupDbBackup script returns the following screen output if it is set up correctly: Successfully set up incremental backup! Successfully set up full backup! To verify that SetupDbBackup.bat creates the scheduled backups, check the backup directory for backup files. Running SetupDbBackup on UNIX or Linux To run SetupDbBackup: 1. Log in to the DX-NAS server as root. 2. Mount the directory that will contain the backups. 3. Change the directory to /opt/emc/dxnas/server/bin and type:./setupdbbackup backupdir time Backing up the DX-NAS database 99

100 Backing Up and Restoring DX-NAS For example, to back up the DX-NAS database to the dbbackup directory at 5:00 P.M., the command syntax would be:./setupdbbackup /dbbackup 17:00 If you run the backup script on Monday after 5:00 P.M, an incremental backup of the DX-NAS database would run the next day (Tuesday) at 5:00 P.M. To modify the backup schedule or time, you must re-issue the SetupDbBackup command. To verify that SetupDbBackup creates the scheduled backups, check the backup directory for backup files. Restoring the DX-NAS database This section provides instructions for restoring the DX-NAS database from one of the point-in-time backups you made by using the Backup Database option from the GUI or from the backups created by using the SetupDbBackup script. Restoring the DX-NAS database from the GUI on Windows To restore the DX-NAS database on Windows: 1. Log in to the DX-NAS server. (Use the same user account that was used to install DX-NAS.) 2. From the Windows Start menu, select All Programs > Administrative Tools > Services. 3. In the Services panel, right-click EMC DX NAS Database and click Stop. The Stop Other Services dialog box indicates that this action also stops EMC DX NAS Server service. Note: To use the Windows command line, type: net stop EMC DX NAS Database 4. Click Yes. The DX-NAS services stop. 5. Change to the directory that contains the database backups. If you installed DX-NAS in the default location, this location is: C:\Program Files\EMC\DXNAS\Server\database\backup\timestampDir where timestampdir is the name of the directory where the DX-NAS GUI stored the database backup. The following directory is an example of a backup directory: C:\Program Files\EMC\DXNAS\Server\database\backup\ Copy the file fsmnas.db and fsmnas.log files to C:\Program Files\EMC\DXNAS\Server\database. Overwrite the existing database file and log if they exist. 7. In the Services panel, right-click EMC DX NAS Server and click Start. Note: To use the Windows command line, type: net start EMC DX NAS Server 100 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

101 Backing Up and Restoring DX-NAS 8. If you are using a NetApp filer as a source host, run a source scan on every source directory on the NetApp filer host. The DX-NAS database has now been restored. Restoring the DX-NAS database from the GUI on UNIX or Linux To restore the DX-NAS database on UNIX or Linux: 1. Log in as root on the DX-NAS server. 2. Navigate to the bin directory: cd /opt/emc/dxnas/server/bin 3. Stop the DX-NAS server and database processes. Type:./DxnasServer stop./dxnasdb stop 4. Change to the directory that contains the database backups. If you installed DX-NAS in the default location, this location is: /opt/emc/dxnas/server/database/backup/timestampdir where timestampdir is the name of the directory where the DX-NAS GUI stored the database backup. The following directory is an example of a backup directory: /opt/emc/dxnas/server/database/backup/ Copy the fsmnas.db and fsmnas.log files to /opt/emc/dxnas/server/database. 6. Overwrite the existing database file and log if they exist. 7. Restart the DX-NAS processes. Type:./opt/EMC/DXNAS/Server/bin/DxnasDb start./opt/emc/dxnas/server/bin/dxnasserver start 8. If you are using NetApp filer as a source host, run a source scan on every source directory on the NetApp filer host. The DX-NAS database has now been restored. Restoring database backups from the command line If you created full and incremental backups by using the SetupDbBackup script or a SetupDbBackup.bat file you can restore these backups to recover the DX-NAS database. The restore procedure uses the dbsrv9 and dbvalid commands, which are located in the following directories: On Windows, in C:\Program Files\EMC\DXNAS\Server\database\bin. On UNIX or Linux, in /opt/emc/dxnas/server/database/bin. To restore the database, you first apply the full backup of the database, and then apply each incremental log file until the backup is restored to the point in time when the database failure occurred. How to restore a database backup The commands in the following procedure are issued from the Command Prompt on Windows or the operating system prompt on UNIX or Linux. Restoring the DX-NAS database 101

102 Backing Up and Restoring DX-NAS To restore a full database backup and its associated incremental backups: 1. Log into the DX-NAS server. 2. Create a directory for the recovery. 3. Go to the directory that contains the full database backup and incremental log files and copy the fsmnas.db file to the recovery directory that you created in step 2. Figure 36 on page 102 illustrates the backup files as they appear in the backup directory. Figure 36 Backup database file (fsmnas.db) and one incremental 4. Go to the directory that contains the dvsrv9 command: On Windows, go to C:\Program Files\EMC\DXNAS\Server\database\bin. On UNIX or Linux, go to /opt/emc/dxnas/server/database/bin. 5. Apply the backup of fsmnas.db. Type: dbsrv9 recovery_directory -a backup_directory where: recovery_directory is the directory path (created in step 2) that contains a full backup of fsmnas.db. backup_directory is the directory path that contains full backup and incremental log files. A message indicating that recovery is in progress appears in the server window. Monitor the server window for error messages.! IMPORTANT A full backup of the DX-NAS database, which runs on Saturday, creates fsmnas.db in the backup directory. If fsmnas.db is not present in the backup directory, the dbsrv9 command fails. 6. Apply all incremental log files: a. Type: dbsrv9 recovery_directory -a backup_directory where: recovery_directory is the directory path that contains a full backup of fsmnas.db. backup_directory is the directory path that contains full backup and incremental log files. b. Repeat step a for all incremental log files in the backup directory. Up to six incremental log files may be applied. 102 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

103 Backing Up and Restoring DX-NAS How to start the database after a restore operation 7. Apply the log file that corresponds to the time of the database failure: dbsrv9 recovery_directory -a backup_directory where: recovery_directory is the directory path that contains a full backup of fsmnas.db. backup_directory is the directory path that contains full backup and incremental log files. 8. Copy only the database file (fsmnas.db) from recovery directory to the production system. A new log file is automatically created. The DX-NAS database is now restored to a current point-in-time backup. Next, you must start the database. How to start the database after a restore operation on page 103 provides more information. After you restore the DX-NAS database, use the dbsrv9 command to start the database, and the dbvalid command to verify the database s integrity. The dbvalid command also ensures that users can connect to the database. The commands in the following procedure are issued from the Command Prompt on Windows or the operating system prompt on UNIX or Linux. To start and verify the DX-NAS database: 1. Log in to the DX-NAS server. 2. Go to the directory that contains the dvsrv9 command: On Windows, go to C:\Program Files\EMC\DXNAS\Server\database\bin. On UNIX or Linux, go to /opt/emc/dxnas/server/database/bin. 3. Type the following command: dbsrv9 -n DXNASDB_hostname database_directory where: hostname is the hostname of the DX-NAS server. database_directory is the directory path to the recovered production database. 4. To verify the database, type: dbvalid -c "uid=dba;pwd=sql;eng=dxnasdb_hostname;dbn=fsmnas" Where hostname is the hostname of the DX-NAS server. The DX-NAS database is now started and validated. Backing up primary and secondary storage The Celerra or NetApp filer are the primary access point for migrated files. Depending on the type of backup software you use, files located on Celerra can be backed up as full files or as stub files. If your backup software is NDMP-enabled, you might be able to back up only the stubs of migrated files (the full content of the file has been migrated to secondary storage). Software that is NDMP-enabled or Celerra FileMover-aware presents the smallest backup window on the Celerra. However, it creates a more complex backup solution as stub backups need to be coordinated with backups of secondary storage. Backing up primary and secondary storage 103

104 Backing Up and Restoring DX-NAS Backing up offline stub files When you back up the stub files of migrated files, the backup application must be able to detect that the stub files represent offline files. If a file is offline, the backup application backs up the 8 KB stub file without recalling the data portion from secondary storage. However, as shown in Figure 37 on page 104, in most cases you should make sure that the data portions of the stubs on secondary storage are also backed up. Backup media Celerra Secondary storage Backup media Backup Stub file Stub file Data file Data file Restore Stub file Data file Figure 37 Stub backup with corresponding secondary storage backup For configurations that use a NetApp source, you must also back up the DX-NAS database. Figure 38 on page 104 illustrates a backup process that includes backing up the DX-NAS database. DX-NAS DB Backup media NetApp Secondary storage Backup media Backup Stub file Stub file Data file Data file Restore Stub file Now-orphaned data file DX-NAS DB Figure 38 EMC Centera and NetApp require DX-NAS database backup Also, if you are migrating from either NetApp or Celerra to an EMC Centera, you must back up the DX-NAS database at the same time you back up secondary storage. 104 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

105 Backing Up and Restoring DX-NAS! IMPORTANT Do not run any migration jobs while backing up the DX-NAS database or secondary storage. Backing up stub files from primary storage has the following advantages: Shorter backup times as only the 8 KB stubs are backed up (instead of the entire file). Reduced network traffic. However, stub backups have the following disadvantages: Only the stub resides on the backup media. The data portion of the stub that resides on secondary storage must be backed up separately. If orphan file management policies are in use, the stub backup and the secondary storage backup must be kept synchronized Note: Stub-only backups are only available using the CIFS protocol. You can not perform a stub only backup on primary storage file systems that are only exported as NFS. Preparing Celerra for stub backups Forcing a passthrough mode on Celerra To back up just the stubs on a Celerra, enable offline back up on the file system you are backing up. From the Celerra Control Station, type the following command: fs_dhsm -modify filesystem -backup offline where filesystem is the name of the primary storage file system to be backed up as passthrough. With offline back up enabled, backup applications like EMC NetWorker will only back up the stub without recalling data from secondary storage. On Celerra, even if you have migrated files by using the full readback method, it is still possible to back up the stubs in passthrough mode, thus obviating the need to remigrate the files. From the Celerra Control Station, type the following command: fs_dhsm -modify filesystem -backup passthrough where filesystem is the name of primary storage file system to be backed up as passthrough. This command overrides the readback mode that was specified when the file was migrated. About backing up with NFS If your backup software uses NFS, then the complete (full) file is backed up. Performing full file backups is a simple way to ensure data integrity in the DX-NAS system. However, it presents the longest backup window on Celerra. The retrieval of migrated files from secondary storage will impact the time required to perform a full backup. About backing up managed file systems In the case where you are using a managed file system as secondary storage, you might not be backing up data portions of files, but rather managed file system stubs Backing up primary and secondary storage 105

106 Backing Up and Restoring DX-NAS that are linked to data files on tertiary storage. In this case, you will need to understand backup strategies for your managed file system.! CAUTION DX-NAS is not a backup and recovery tool. The data on source file systems managed by DX-NAS must still be backed up if want to be able to recover from disaster situations. 106 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

107 8 Relocating DX-NAS This chapter discusses the following topics: Relocating primary storage Relocating the DX-NAS server Relocating data to a new destination Relocating DX-NAS 107

108 SB8 SB6 SB4 SB2 SB0 PS0 PS1 PS2 PS3 PS4 SMB0 SMB1 SB9 SB7 SB5 SB3 SB1 Relocating DX-NAS Relocating primary storage After installing and configuring DX-NAS you may need to change the location of primary storage. To relocate primary storage: 1. Backup primary storage to tape using NDMP-compliant backup software. 2. Restore files and stubs to new location. 3. Run source scan on primary storage. Your primary storage should be relocated. Note: You cannot relocate stubs from a Celerra source to a NetApp source or vice versa. Relocating the DX-NAS server The simplest move scenario is where the DX-NAS server is the only DX-NAS component on the host as shown in Figure 39 on page 108. It assumes that the DX-NAS server on Host 1 is configured and functional. Celerra Host 1 SB14 SB15 Secondary Storage SB12 SB13 SB10 SB11 DX-NAS Host 2 DX-NAS GEN Figure 39 Moving the DX-NAS server from Host 1 to Host 2 This procedure consists of the following general steps: 1. Install the DX-NAS server on Host Stop the DX-NAS services on Host In the DX-NAS database directory, delete the fsmnas.db and fsmnas.log files on Host Stop the DX-NAS services on Host From the database directory on Host 1, copy the fsmnas.db and fsmnas.log files to the same location on Host Start the DX-NAS services on Host Set the IP address of Host 2 as an authorized user of the FileMover API by using the server_http command on the Celerra Control Station. 8. If you are using NetApp source hosts, run a source scan on each NetApp source directory. 108 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

109 Relocating DX-NAS The DX-NAS server on Host 2 should now be functional. You can now uninstall the DX-NAS server on Host 1. Moving the Windows DX-NAS server To move the DX-NAS server from one Windows host to another: 1. Install the DX-NAS server on the new host. The EMC DiskXtender File System Manager for NAS Release 3.1 Microsoft Windows Installation and Configuration Guide provides instructions. 2. After completing the installation, select Start > Administrative Tools > Services. 3. In the Services panel, right-click EMC DX NAS Database and click Stop. The Stop Other Services dialog appears informing you that stopping the EMC DX NAS Database automatically stops the EMC DX NAS Server service as well. Note: To use the Windows command line, type: net stop EMC DX NAS Database 4. Click Yes. The DX-NAS services stop. 5. From the C:\Program Files\EMC\DXNAS\Server\database directory, delete the fsmnas.db and fsmnas.log files. 6. Log in to the host where the previously configured DX-NAS server that you want to move is located. Log in as the same user that was used to install DX-NAS. 7. Choose Start > Administrative Tools > Services. 8. In the Services panel, right-click EMC DX NAS Database and click Stop. The Stop Other Services dialog appears informing you that stopping the EMC DX NAS Database automatically stops the EMC DX NAS Server service as well. Note: To use the Windows command line, type: net stop EMC DX NAS Database 9. Click Yes. The DX-NAS services stop. 10. Copy fsmnas.db and fsmnas.log files from C:\Program Files\EMC\DXNAS\Server\database to the same location on the new host. 11. Choose Start > Administrative Tools > Services. 12. In the Services panel, right-click EMC DX NAS Server and click Start. Note: To use the windows command line, type: net start EMC DX NAS Server The DX-NAS services start. 13. Log in to the Celerra Control Station as an administrator and type the following command: server_http DMName -append dhsm -hosts IPaddress where DMName is the name of the Data Mover you want to migrate files from. IPadddress is the IP address of your new host. Relocating the DX-NAS server 109

110 Relocating DX-NAS 14. Log out of the Celerra Control Station. You can now log in to the DX-NAS server on the new host. 15. If you are using a NetApp filer as a source, run a source scan job on each source directory on the NetApp host. The DX-NAS server on the new host should now be functional. You can now uninstall the DX-NAS server on the old host. Moving the Solaris or Linux DX-NAS server You can move the DX-NAS server from one UNIX or Linux host to another system of the same type. Note: Do not move the DX-NAS server from a Solaris system to a Linux system or in the reverse order. To move the DX-NAS server from one Solaris or Linux host to another: 1. Install the DX-NAS server on the new host. The EMC DiskXtender for NAS Release 3.1 UNIX/Linux Version Installation and Configuration Guide provides instructions. 2. On the new host create mount points for the Celerra that are identical to the Celerra mount points used on the host you are moving from. The directories you used as sources on the host you are moving from need to exist on the new host. 3. On the new host create mount points for secondary storage that are identical to the secondary storage mount points used on the host you are moving from. The directories you used as destinations on the host you are moving from need to exist on the new host. 4. Log in as root on the new host and type: cd /opt/emc/dxnas/server/bin If you installed the DX-NAS server in a location other than the default location, use that location. 5. Stop the DX-NAS programs. Type:./DxnasServer stop./dxnasdb stop 6. Delete the fsmnas.db and fsmnas.log files. 7. Log in as root on the host where the previously configured DX-NAS server that you want to move is located. 8. Navigate to the following directory: cd /opt/emc/dxnas/server/bin If you installed the DX-NAS server in a location other than the default location, use that location. 9. Stop the DX-NAS programs. Type:./DxnasServer stop./dxnasdb stop 10. Copy the fsmnas.db and fsmnas.log from /opt/emc/dxnas/server/database to the same location on the new host. 110 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

111 Relocating DX-NAS 11. Start the DX-NAS programs../dxnasdb start./dxnasserver start The DX-NAS services start. 12. Log in to the Celerra Control Station as an administrator and type the following command: server_http DMName -append dhsm -hosts IPaddress where DMName is the name of the Data Mover you want to migrate files from. IPAdddress is the IP address of the new host. 13. Log out of the Celerra Control Station. 14. If you are using a NetApp filer as a source, run a source scan job on each source directory on the NetApp host. The DX-NAS server on the new host should now be functional. You can now uninstall the DX-NAS server on the old host. Relocating data to a new destination Starting with release 3.0, DX-NAS provides a utility for relocating back-end data on a DX-NAS destination to a new destination. For example, use the utility for situations such as the following: To replace or upgrade the hardware used as DX-NAS secondary storage. To relocate data managed by DiskXtender for Windows or File System Manager to an EMC Centera system. The utility supports the relocation of data from the following secondary storage types: File system to file system. EMC Centera system to EMC Centera system. DXUL File System Manager (FSM) file system to EMC Centera system. DiskXtender for Windows-managed file system to EMC Centera system. Figure 40 on page 112 illustrates a file system on a local disk relocated to another file system on a remote server. For this type of relocation, you must copy the files from Relocating data to a new destination 111

112 PS0 PS1 PS2 PS3 PS4 SMB0 SMB1 Relocating DX-NAS the old destination to the new destination before you run the relocate destination utility. EMC Celerra DX-NAS source DX-NAS server Relocate destination utility SB10 SB8 SB2 SB3 SB4 SB6 SB11 SB9 SB7 SB5 SB12 SB13 SB14 SB15 Old migration path File system (old destination) SB0 SB1 New migration path Relocation from old destination to new destination. After using the relocate destination utility, DX-NAS migrates files to the new destination. File system (new destination) Remote server GEN Figure 40 File system to file system relocation Figure 41 on page 113 illustrates relocating data from an EMC Centera system to another EMC Centera system. For this type of relocation, you must use CASCopy or 112 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

113 PS0 PS1 PS2 PS3 PS4 SMB0 SMB1 Relocating DX-NAS EMC Centera replication to copy the data from the old destination to the new destination before you run the relocate destination utility. EMC Celerra DX-NAS source DX-NAS server Relocate destination utility SB10 SB8 SB0 SB1 SB6 SB11 SB12 SB13 SB14 SB9 SB15 SB7 Old migration path EMC Centera (old destination) SB4 SB2 SB5 SB3 New migration path After using the relocate destination utility, DX-NAS migrates files to the new EMC Centera destination. Relocation from old destination to new destination. EMC Centera (new destination) GEN Figure 41 EMC Centera to EMC Centera relocation Figure 42 on page 114 illustrates relocating data from a DiskXtender for Windows file system to EMC Centera system. The relocate destination utility copies the files from the DiskXtender for Windows file system to the EMC Centera system as part of the processing. Relocating data to a new destination 113

114 PS0 PS1 PS2 PS3 PS4 SMB0 SMB1 Relocating DX-NAS EMC Celerra DX-NAS source DX-NAS server Relocate destination utility SB6 SB8 SB10 SB12 SB14 SB15 SB7 SB9 SB11 SB13 Old migration path DiskXtender for Windows file system (old destination) SB2 SB4 SB3 SB5 New migration path SB0 SB1 Relocation from DXW file system to an EMC Centera system. After using the relocate destination utility, DX-NAS migrates files directly from the Celerra system to the EMC Centera system. DXW can be removed from the configuration. EMC Centera (new destination) GEN Figure 42 DX-Windows managed file system to an EMC Centera Figure 43 on page 115 illustrates relocating data on a DXUL FSM-managed file system to an EMC Centera system. The relocate destination utility copies the files 114 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

115 PS0 PS1 PS2 PS3 PS4 SMB0 SMB1 Relocating DX-NAS from the DXUL File System Manager file system to the EMC Centera system as part of the processing. EMC Celerra DX-NAS source DX-NAS server Relocate destination utility SB6 SB8 SB10 SB12 SB7 SB9 SB11 SB13 SB14 SB15 Old migration path DXUL FSM managed file system (old destination) SB2 SB4 SB3 SB5 New migration path SB0 SB1 Relocation from old destination to new destination. After using the relocate destination utility, DX-NAS migrates files directly from the Celerra system to the EMC Centera system. DXUL FSM can be removed from the configuration. EMC Centera (new destination) GEN Figure 43 DXUL FSM-managed file system to an EMC Centera Note: You cannot use the utility to move data from an EMC Centera system to a file system. DX-NAS supports this utility in configurations in which the source or primary storage device is a Celerra system. Do not use this utility if the source system is a NetApp filer. The DX-NAS server installation includes the relocate destination utility. For UNIX/Linux platforms, the utility is named RelocateDestination and is installed by default in the /opt/emc/dxnas/server/bin directory. For Microsoft Windows platforms, the utility is named RelocateDestination.bat and is installed by default in the C:\Program Files\EMC\DXNAS\Server\bin directory. The utility, which runs as a client job of the DX-NAS server, also enables you to view statistics for a relocation job, stop a relocation job, and delete a relocation job. The utility enables you to specify processing threads when you run a relocation job. The number of threads corresponds to the number of files that can be relocated in parallel. The number of threads you specify can be used for performance tuning. For example, the more threads you specify, the faster the relocation job runs. However, the DX-NAS server uses more resources for processing. Likewise, using less threads slows the relocation job, but enables resources for processing other jobs. To run the relocate destination utility requires a single parameter: RelocateDestination.bat parameter Relocating data to a new destination 115

116 Relocating DX-NAS Table 21 on page 116 includes a list of values that you can specify for this parameter. Table 21 Parameters for the relocate destination utility Value start stat stop delete Description Starts a relocation job. The utility prompts you for the following information: Old destination New destination Maximum number of threads to use to run the job The number of threads corresponds to the number of files being relocated in parallel. The upper limit is 10 threads. The lower limit is 1 thread. Provides status information for the relocation job. The utility prompts you for the destination source. The stat parameter enables you to: View status information for a job until the job is deleted or the DX-NAS server terminates. Follow the progress of the job and check for its completion. Stops a relocation job currently in progress. The utility prompts you for the destination source, and then issues a stop command. The stop command does not remove job information. You can still use the stat parameter to view status information. Deletes the job statistics from the relocation process. The delete process completes successfully if the job has been stopped or has completed (with errors or successfully). After the delete process finishes, the status information is no longer available for viewing. You can, however, view references to the relocation job in the DXNASLog.log file. How the relocate destination utility works The relocate destination utility determines what files use the old destination, and then verifies that the files have been copied to the new destination. The utility 116 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

117 Relocating DX-NAS updates the Celerra offline information to use files from the new destination. Figure 44 on page 117 illustrates the relocation process flow. Use the find command to determine all candidate files to relocate to the new destination. Determine if candidate files are stored on the old destination. Determine the new destination. Is the relocation from a file system to an EMC Centera system? Yes Copy data to the new EMC Centera destination. No Update the Celerra offline attributes to use the new destination. Update database entries, if necessary. Is the relocation from a file system to file system or EMC Centera to EMC Centera? Yes Verify that the data is on the new destination. GEN Figure 44 Relocation process flow The utility does not physically move the data from the current destination device to the new destination device in two cases: If the relocation is from a file system to a file system. If the relocation from an EMC Centera system to an EMC Centera system. You must, therefore, copy the data from the current destination device to the new destination device. To physically copy data from a file system destination device to the new file system destination device, use the appropriate copy command or backup operation for that particular file system. To physically copy data from an EMC Centera destination to a new EMC Centera destination, use the appropriate method: CASCopy administrative tool Note: For additional help with the CASCopy tool, contact EMC Customer Service. EMC Centera replication Relocating data to a new destination 117

118 Relocating DX-NAS! IMPORTANT You usually do not need the relocate destination utility to relocate data from one EMC Centera system to another. Instead, simply change the configuration information for the EMC Centera system by using the Destination Wizard in the DX-NAS GUI. To relocate data managed by DiskXtender for Windows or DXUL File System Manager software to an EMC Centera system does not require that you first copy the destination data to the EMC Centera system. The relocation process reads data from the current file system destination device and then writes C-Clips to the EMC Centera destination. After all data is relocated from the file system to the EMC Centera system, DiskXtender for Windows or File System Manager can be removed from the DX-NAS configuration. To run the utility requires that you provide the following input: DX-NAS server hostname Username and password The relocate destination utility authenticates the username and password to ensure that the account has adequate permissions to run a relocation job. The utility provides data persistence. For example, if a relocation job terminates before it completes, you can restart the job where it left off. If problems occur during processing, the relocate destination utility writes error messages to the DXNASlog.log file.! IMPORTANT A relocation job can be slow depending on the number of objects being relocated. Prerequisites to running the relocate destination utility Before running the relocate destination utility you must create a migration policy for the new destination. The following resources provide detailed instructions for creating destinations and migration policies: For the DX-NAS GUI, use online help. For the DX-NAS CLI, use the EMC DiskXtender for NAS Release 3.1 Multiplatorm Version Administration Guide. For help with the CASCopy tool or EMC Centera replication, use the appropriate EMC Centera documentation. Perform the following tasks before using the relocate destination utility: 1. Use the DX-NAS GUI or CLI to: a. Create a new destination. b. Create a migration policy for the new destination. c. Create a job for the migration policy. d. Stop migrating files to the old destination. 2. Copy all files from the old destination to the new destination: Use the appropriate copy or backup tool to copy all the files from the old file system to the new file system. 118 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

119 Relocating DX-NAS Use CASCopy to copy all data from the old EMC Centera system to the new EMC Centera system. If EMC Centera replication is configured, then the replica EMC Centera system operates as the new destination. This step is not applicable if the old destination is a file system and the new destination is an EMC Centera system. In this circumstance, the relocate destination utility copies the files from the old file system to the new EMC Centera destination. How to run the relocate destination utility The relocate destination utility provides four options: Start a job. Provide status information on a running job. Stop a running job. Delete a job. This section provides instructions for using the relocate destination utility with each of the four options. Note: Use the delete parameter to remove an existing job before you attempt to run another relocation job. Failing to remove an existing job, results in an error message. Starting a relocation job To start a relocation job: 1. Log in to the machine that runs the DX-NAS server software. For UNIX or Linux, log in as root. For Microsoft Windows, log in as an administrator. 2. Open a terminal window or Windows Command prompt. 3. Navigate to the directory that contains the relocate destination utility. For UNIX or Linux, the default directory is /opt/emc/dxnas/server/bin. For Microsoft Windows, the default directory is C:\Program Files\EMC\DXNAS\Server\bin. 4. Type the following command at the prompt: For UNIX or Linux, type:./relocatedestination start For Microsoft Windows, type: RelocateDestination.bat start Note: You can run only one relocation job at a time for a Celerra source. As the utility runs, it displays prompts that require input. 5. Type the appropriate information for the following prompts: a. For Enter Server Name, type the hostname of the DX-NAS server and press Enter. b. For Enter Username, type the username for the DX-NAS GUI and press Enter. The default username is system. Relocating data to a new destination 119

120 Relocating DX-NAS c. For Password, type the password for the username in step b and press Enter. The default password is system. d. For Choose from the following list, type the number for the Celerra source system and press Enter. e. For Select the Old Destination, type the number for the destination and press Enter. f. For Select the New Destination, type the number for the destination and press Enter. g. For Maximum number of threads to use to run job, type a numeric value and press Enter. The range for number of threads is 1 through 10. Ten threads is the default value. Example 16 on page 120 shows output for the RelocateDestination.bat start command. Example 16 Screen output example for the Relocation.bat start command C:\Program Files\EMC\DXNAS\Server\bin>RelocateDestination.bat start Enter Server Name: lava2238 Enter Username: system Enter Password: Select the Source. Choose from the following list: 1. Celerra CIFS Source 2. Celerra NFS Source Selection? 1 Select the Old Destination. Choose from the following list: 1. Old Destination 2. New Destination Selection? 1 Select the New Destination. Choose from the following list: 1. Old Destination 2. New Destination Selection? 2 Maximum number of threads to use to run job [10]? Relocate Destination job started. Viewing job status To view the status of a relocation job: 1. Repeat steps 1 3 from Starting a relocation job on page Type the following command at the prompt: For UNIX or Linux, type:./relocatedestination stat For Microsoft Windows, type: RelocateDestination.bat stat As the script runs, it displays prompts that require input. 120 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

121 Relocating DX-NAS 3. Type the appropriate information for the following prompts: a. For Enter Server Name, type the hostname of the DX-NAS server and press Enter. b. For Enter Username, type the appropriate username and press Enter. c. For Password, type the appropriate password and press Enter. d. For Choose from the following list, type the number for the Celerra source system and press Enter. Example 17 on page 121 displays statistics for a relocation job that has finished. Example 17 Screen output for the RelocateDestination stat command C:\Program Files\EMC\DXNAS\Server\bin>RelocateDestination.bat start Enter Server Name: lava2238 Enter Username: system Enter Password: Select the Source. Choose from the following list: 1. Celerra CIFS Source 2. Celerra NFS Source Selection? 1 Statistics ================================= Job State: Completed Source name: Celerra CIFs Old Destination Name: Old Destination New Destination Name: New Destination Total Attempts: 154 Total Files Offline: 154 Total Files on Old Destination: 154 Number of successful relocations: 154 Number of relocation failures: 0 Number of files where no access to new back end object: 0 Number of errors getting source attibutes: 0 Number of errors setting offline attributes: 0 Number of data copy errors: 0 Number of bytes copied: 0 The relocate destination utility updates the number of bytes copied only if the files are actually copied by the utility from a file system to EMC Centera destination. Stopping a job To stop a relocation job: 1. Repeat steps 1 3 from Starting a relocation job on page Type the following command at the prompt: For UNIX or Linux, type:./relocatedestination stop For Microsoft Windows, type: RelocateDestination.bat stop As the script runs, it displays prompts that require input. 3. Type the appropriate information for the following prompts: a. For Enter Server Name, type the hostname of the DX-NAS server and press Enter. b. For Enter Username, type the appropriate username and press Enter. Relocating data to a new destination 121

122 Relocating DX-NAS c. For Password, type the appropriate password and press Enter. d. For Choose from the following list, type the number for the Celerra source system and press Enter. Example 18 on page 122 shows output for the RelocateDestination.bat stop command. Example 18 Screen output for the RelocateDestination stop command C:\Program Files\EMC\DXNAS\Server\bin>RelocateDestination.bat start Enter Server Name: lava2238 Enter Username: system Enter Password: Select the Source. Choose from the following list: 1. Celerra CIFS Source 2. Celerra NFS Source Selection? 1 Relocate Destination job stopped, job state still active until job is deleted. Deleting a job Example 19 To delete a relocation job: 1. Repeat steps 1 3 from Starting a relocation job on page Type the following command at the prompt: For UNIX or Linux, type:./relocatedestination delete For Microsoft Windows, type: RelocateDestination.bat delete As the script runs, it displays prompts that require input. 3. Type the appropriate information for the following prompts: a. For Enter Server Name, type the hostname of the DX-NAS server and press Enter. b. For Enter Username, type the appropriate username and press Enter. c. For Password, type the appropriate password and press Enter. d. For Choose from the following list, type the number for the Celerra source system and press Enter. Example 19 on page 122 shows output for the RelocateDestination.bat delete command. Screen output for the RelocateDestination.bat delete command C:\Program Files\EMC\DXNAS\Server\bin>RelocateDestination.bat start Enter Server Name: lava2238 Enter Username: system Enter Password: Select the Source. Choose from the following list: 1. Celerra CIFS Source 2. Celerra NFS Source Selection? 1 Relocate destination job deleted. 122 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

123 Relocating DX-NAS! IMPORTANT Before you run a new relocation job, use the delete parameter to delete all statistics for the previous relocation job. Relocating data to a new destination 123

124 Relocating DX-NAS 124 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

125 A Troubleshooting This appendix discusses the following topics: DX-NAS logs Error conditions NetApp filer issues Alerts Troubleshooting 125

126 Troubleshooting DX-NAS logs DX-NAS reports errors as alerts or as messages in log files. With these alerts or messages you can sometimes correct the problem. DX-NAS uses the following log files: DXNASLog.log captures any messages or errors that are written to the default output stream. In troubleshooting situations, examine this log first. DXNASServerLog_x.log captures any messages or errors generated by the DX-NAS server process. For Windows, the default location for the server logs is in C:\Program Files\EMC\DXNAS\Server\logs. For UNIX or Linux, the default location for the server logs is in, /opt/emc/dxnas/server/logs. Error conditions The following are some common problems with the DX-NAS client interfaces. Problems are identified by symptom. Note: Errors reported by DX-NAS on UNIX or Linux may differ somewhat from errors reported on Windows. DX-NAS server is not running When trying to log in with the DX-NAS GUI or CLI, you may receive the following error message: Console Server is not running This error usually means the DX-NAS server is not running. You can either reboot the host where the DX-NAS server was installed (to see if server will start automatically) or you can start the server manually. Starting the DX-NAS on Microsoft Windows To start the DX-NAS console server manually on Microsoft Windows: 1. Log in to the computer that runs the DX-NAS server. Use the same login account that was used to install DX-NAS. 2. From the Windows Start menu, select All Programs > Administrative Tools > Services. 3. In the Services window, right-click EMC DX NAS Server and click Start. Note: To start the service from the Microsoft Windows command prompt, type: net start EMC DX NAS Server The database and server services start, and you should now be able to log in to the DX-NAS server. 126 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

127 Troubleshooting Starting the DX-NAS on UNIX or Linux To start the DX-NAS console server manually on UNIX or Linux: 1. Log in as root to the computer that runs the DX-NAS server. 2. At the prompt, type the following commands: cd /opt/emc/dxnas/server/database./dxnasdb start./dxnasserver start Note: If you installed the DX-NAS server in a location other than the default location, use that location. The database and server services start, and you should now be able to log in to the DX-NAS server. Network configuration errors In some cases the network configuration can result in DX-NAS errors. For example, the following message indicates a communication problem between the DX-NAS server and the NetApp filer: Filer returned an error of 0xffffffff to probe of connection. This error can occur for any number of reasons including the following: On Linux, Samba may be running on the same machine as the DX-NAS server. Hostname resolution may not be set up correctly on the machine where DX-NAS is installed. No network route between the NetApp filer and the DX-NAS server. Celerra configuration errors In some cases when DX-NAS attempts to connect to the Celerra, you may encounter the following error: Error: please enter valid data forbidden to access data mover the server does not have http access on the data mover This error can be caused by either of the following conditions: You have not entered the server_http command to specify the IP address for the DX-NAS server. Type the following command to add the IP address for the DX-NAS server: server_http <data_mover> -append dhsm -hosts <IP_address> This command grants access to the FileMover by the DX-NAS server. You may have appended the DX-NAS server s IP address, but it may be too far down in the list. Re-create the list by using the following server_http command: server_http <data_mover> -modify dhsm -hosts <newipaddresslist> Make sure the DX-NAS server s IP address is one of the first entries in the list. Error conditions 127

128 Troubleshooting Offline directories list is empty or incomplete When creating a destination, the Destination Wizard provides the Offline Directory list. This list contains valid connection strings on Celerra. If the list is empty, or is missing a connection string, check for the following: There are no Celerra systems identified as source hosts on the Sources tab. Migration of files by using the symbolic-link migration mode might cause this problem. The Celerra system identified on the Sources tab are using DART version 5.3. If Celerra is running DART version 5.3, the connection string is not displayed in the Offline Directory list. Note: DART versions earlier than 5.4 are not supported. The computer identified in the Celerra connection string is either down or does not have a network connection. In this case, the Celerra tries to reestablish communication with the computer for 30 seconds. During the retry process, all requests to Celerra for a list of connections fail. Consequently, the Office Directory list is not updated. The source host identified in the Sources tab might have an incorrect FileMover username or password. To determine this, set the DX-NAS logging level to debug, and try to create the destination again. Inspect the log, and if you see an HTTP 401 error, this probably indicates that the FileMover username or password is incorrect. Online help provides more information on setting the log level. The machine that runs the DX-NAS server might not be in the Celerra access list. To determine this, set the log level to debug, and try to create the destination again. Inspect the log, and if you see an HTTP 403 error, this probably indicates that the computer that runs the DX-NAS server needs to be added to the Celerra s access list. Source host or path issues Table 22 Table 22 on page 128 provides common error messages and descriptions for issues that pertain to the source host or path. Errors returned for source host or path issues Error message HTTP Error 401: Unauthorized failed connect call Cannot access migration root directory getdhsmapiattrs: failed to resolve hostname failed to resolve hostname HTTP Error 403: Forbidden Reason for failure The FileMover username or password might be incorrect. The source hostname might be invalid or has become invalid. The DX-NAS server does not have Hypertext Transfer Protocol (HTTP) access to Celerra. The DiskXtender for NAS Installation and Configuration Guides provides more information on verifying HTTP access to Celerra. The source path for the source directory is incorrect. For Windows the source path is a UNC path such as: \\server\... Where server must match the value specified for the Source Host field. 128 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

129 Troubleshooting Destination directory issues Table 23 Table 23 on page 129 provides common error messages and descriptions for issues that pertain to the destination directory. Errors returned for destination directory issues Error message Failed to create migration directory Failed mkdir Cannot access migration root directory NFS access failed for server Unable to reserve space for migrated file, disk maybe full write failure on dest file Could not validate Migration Root Dir Reason for failure The destination specified might be set as read-only. DX-NAS must have write permissions on the destination directory. The destination directory might be inaccessible. You might get this error if you do not have the destination directory shared correctly on your secondary storage host, or if you lose network access to the destination. The destination directory might be out of disk space. The destination s Destination Path and Offline Directory might not point to the same secondary storage location. On Solaris, the directory names in Destination Path and Offline Directory sometimes will be different, but the mount point of Destination Path should resolve to the same location pointed to by Offline Directory. DX-NAS problems Table 24 Table 24 on page 129 lists common DX-NAS server configuration problems. Common DX-NAS configuration problem Problem description A job fails to run or preview. A job that is running stops unexpectedly. Reason for problem An attempt to run or preview a job can fail because of issues with either the source host or path, or the destination directory. The DX-NAS server may have exceeded its maximum error threshold. Look at the errors being reported in the Alerts tab to determine the cause of the error. If possible, correct the error and restart the jobs. If the error is not critical or serious, you can increase the max.job.error setting in the env.properties file. NetApp filer issues This section contains common issues found if using a NetApp filer as a DX-NAS source. Small files are not migrated If you notice that some files are not being migrated from a NetApp filer, it may be because they are too small. DX-NAS does not migrate files from a NetApp filer that are smaller than 8 KB. NetApp filer issues 129

130 Troubleshooting Changes to NetApp filer username, password, or hostname If the username, password, or hostname changes on the NetApp filer source, you must restart the DX-NAS server On UNIX or Linux: 1. Navigate to the /opt/emc/dxnas/server/bin directory. 2. Type the following commands:./dxnasserver stop./dxnasserver start On Microsoft Windows: 1. Select Start > Settings > Control Panel > Administrative Tools > Services. The Services dialog box appears. 2. Right-click EMC DX NAS Server and click Restart. Alerts By default, alerts that are older than seven days are filtered out of the display. To view alerts older than seven days: 1. Select the Alerts tab and click Filter. 2. In the Filter Alerts Wizard, select the appropriate start and end time, and click Finish. Online help provides more details on using the Filter Alerts Wizard. Fix this condition by setting write permissions on the destination share. 130 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

131 B Technical Support This appendix discusses the following topics: Troubleshooting the problem Before contacting EMC Documenting the problem Reporting a new problem Technical Support 131

132 Technical Support Troubleshooting the problem Please perform the relevant diagnostic steps before you contact EMC Customer Service: 1. Read the documentation carefully. 2. Reconstruct the events leading up to the problem and describe them in writing. 3. Run some test cases to reproduce the problem. If you encounter a problem that requires technical programming or analysis, contact EMC Customer Service. Where to get help on page 12 in the Preface provides contact information. Before contacting EMC Have the following information available before contacting EMC Customer Service: Company name and address Contact name Phone number Existing problem tracking ID, if one was previously assigned for the problem Technical details Provide the following information about the source hosts and about the file systems you are using for source directories and destination directories. Celerra information IP address of the Celerra Control Station. Hostname of the Celerra Control Station. Output of the following command executed on the Celerra Control Station: fs_dshm -connection filesystemname -info where filesystemname is the name of the file system where your source directories are located. Output of the following command executed on the Celerra Control Station: server_http datamovername -info where datamovername is the name of the Data Mover where your source directories are located. Output of the following command executed on the Celerra Control Station: server_export filesystemname -info where filesystemname is the name of the file system where your source or destination directories are located. 132 EMC DiskXtender for NAS Release 3.1 Multiplatform Version Administration Guide

133 Technical Support NetApp information IP address of the NetApp filer. Hostname of the NetApp filer. Output of the following command executed on the NetApp filer command line: exportfs Output of the following command executed on the NetApp filer command line: fpolicy Output of the following command executed on the NetApp filer command line: version DX-NAS server information IP address of the machine that runs the DX-NAS server. Hostname of the machine that runs the DX-NAS server. DX-NAS configuration Understanding the DX-NAS configuration is a critical aspect to troubleshooting problems. The most efficient way to gather this information is to use the Export Configuration option in the DX-NAS GUI. To export the configuration: 1. Select Export Configuration from the Tools menu as shown in Figure 45 on page 133. Figure 45 Export Configuration option The Export Config dialog box appears. 2. Select a directory for the configuration file and click Save. The Select an Option dialog box appears. 3. Click Yes. Before contacting EMC 133