Data Migrator Administration Guide

Hitachi NAS Platform

Data Migrator Administration GuideRelease 123

MK-92HNAS005-07

No part of this publication may be reproduced or transmitted in any form or by anymeans electronic or mechanical including photocopying and recording or stored in adatabase or retrieval system for any purpose without the express written permission ofHitachi Ltd

Hitachi Ltd reserves the right to make changes to this document at any time withoutnotice and assumes no responsibility for its use This document contains the mostcurrent information available at the time of publication When new or revised informationbecomes available this entire document will be updated and distributed to all registeredusers

Some of the features described in this document might not be currently available Referto the most recent product announcement for information about feature and productavailability or contact Hitachi Data Systems Corporation at httpsportalhdscom

Notice Hitachi Ltd products and services can be ordered only under the terms andconditions of the applicable Hitachi Data Systems Corporation agreements The use ofHitachi Ltd products is governed by the terms of your agreements with Hitachi DataSystems Corporation

2Hitachi NAS Platform Data Migrator Administration Guide

Hitachi Data Systems products and services can be ordered only under the terms andconditions of Hitachi Data Systemsrsquo applicable agreements The use of Hitachi DataSystems products is governed by the terms of your agreements with Hitachi DataSystems

Hitachi is a registered trademark of Hitachi Ltd in the United States and othercountries Hitachi Data Systems is a registered trademark and service mark ofHitachi Ltd in the United States and other countries

Archivas Dynamic Provisioning Essential NAS Platform HiCommand Hi-TrackShadowImage Tagmaserve Tagmasoft Tagmasolve Tagmastore TrueCopyUniversal Star Network and Universal Storage Platform are registered trademarks ofHitachi Data Systems Corporation

AIX AS400 DB2 Domino DS8000 Enterprise Storage Server ESCON FICONFlashCopy IBM Lotus OS390 RS6000 S390 System z9 System z10 Tivoli VMESA zOS z9 zSeries zVM zVSE are registered trademarks and DS6000 MVSand z10 are trademarks of International Business Machines Corporation

All other trademarks service marks and company names in this document orwebsite are properties of their respective owners

Microsoft product screen shots are reprinted with permission from MicrosoftCorporation

This product includes software developed by the OpenSSL Project for use in theOpenSSL Toolkit (httpwwwopensslorg) Some parts of ADC use open source codefrom Network Appliance Inc and Traakan Inc

Part of the software embedded in this product is gSOAP software Portions created bygSOAP are copyright 2001-2009 Robert A Van Engelen Genivia Inc All rightsreserved The software in this product was in part provided by Genivia Inc and anyexpress or implied warranties including but not limited to the implied warranties ofmerchantability and fitness for a particular purpose are disclaimed In no event shallthe author be liable for any direct indirect incidental special exemplary orconsequential damages (including but not limited to procurement of substitutegoods or services loss of use data or profits or business interruption) howevercaused and on any theory of liability whether in contract strict liability or tort(including negligence or otherwise) arising in any way out of the use of this softwareeven if advised of the possibility of such damage

The product described in this guide may be protected by one or more US patentsforeign patents or pending applications

Notice of Export Controls

Export of technical data contained in this document may require an export licensefrom the United States government andor the government of Japan Contact theHitachi Data Systems Legal Department for any export compliance questions

Contents

Preface 8Contacting Hitachi Data Systems8Related Documentation 8

1 Overview of Data Migrator and Data Migrator to Cloud 12Data migration paths14Types of migration targets 14Cross volume links in Data Migrator 15Cross volume link format considerations 17Adding a license key17

2 Hitachi Data Systems Data Migrator 20Configuring Data Migrator21Data Migrator considerations 21Viewing data migration paths24

Configuring Data Migrator paths 25Adding a local WFSHNAS data migration path26About external data migration paths 28

Viewing data migration rules29Adding a data migration rule by template 30Adding a custom WFSHNAS data migration rule34Modifying a data migration rule 35

Viewing data migration policies and schedules36Adding a WFSHNAS data migration policy39

Using Pre-Conditions 42Modifying a data migration policy43About the ndmp-management-ports-set command44Migration schedules 45

Adding a Data Migration schedule45Modifying a schedule47

Data Migration status and reports48

Viewing details of a data migration report49Migration to HCP Systems51

3 Hitachi Data Systems Data Migrator to Cloud 54Configuring Data Migrator to Cloud56

Checking and setting the status of aggregate ports for Data Migrator to Cloud56Ensuring that the route exists when using aggregate ports 57

Ensuring the route exists when using management ports 58Data Migrator to Cloud Configurations 58

Target on the Internet with dedicated aggregate ports58Target on the Internet with shared aggregate ports 59Data Migrator to Cloud with aggregate support with target on LAN 60

About cloud accounts and destinations61Cloud providers 62Establishing credentials for Amazon S362Establishing a Microsoft Azure cloud account 63Adding a cloud account 64Adding a cloud destination 66Viewing cloud accounts and destinations 68Viewing Cloud Account Details69Viewing Cloud Destination Details 70

Viewing data migration paths71Adding a cloud path72

Viewing data migration rules73Adding a data migration rule by template 74Adding a data migration rule for the Data Migrator to Cloud78Modifying a data migration rule 80

Viewing data migration policies and schedules80Adding a cloud data migration policy83

Using Pre-Conditions 84Modifying a data migration policy86Migration schedules 87Adding a Data Migration schedule 88Modifying a schedule 90

Data Migration status and reports91Viewing details of a data migration cloud report92

Cloud data migration and replication considerations93Introduction to HCP no delete feature97HCP no delete functionality 97

4 Overview of Hitachi NAS Universal Migrator 100Overview of Universal Migrator Capacity Based (UMC) license101Universal Migrator Capacity License considerations 101Universal Migrator Capacity event notification101Hitachi NAS Universal Migrator Terms 102Pre-migration considerations for Hitachi NAS Universal Migrator102

Number and layout associations102NFS export on the LNAS used by HNAS 103Exportshares from HNAS103Backup and replication policies disaster recovery103

Virtualization103Migration 104HNAS NDMP file replication and tape backups 105

Setting up LNAS and HNAS for virtualization105Starting virtualization 107Monitoring the association 108Incompatible features 108Performance Limitations 109Upgrade and downgrade considerations 109

Troubleshooting Hitachi NAS Universal Migrator 109Cannot create associations 109Hitachi NAS Universal Migrator associations paused110Virtualization or migration does not complete110

Hitachi NAS Universal Migrator Console Commands111virtualization-license-report CLI command 111virtualization-path-control CLI command111virtualization-path-create CLI command112virtualization-path-delete CLI command113virtualization-path-excluded-directory-add CLI command 114virtualization-path-excluded-directory-delete CLI command114virtualization-path-excluded-directory-list CLI command115virtualization-path-files CLI command116virtualization-path-journal-control CLI command 116virtualization-path-journal-show CLI command118virtualization-path-list CLI command118virtualization-path-modify CLI command119virtualization-path-stats CLI command120

A Creating specific and detailed rules 122Rules syntax 123Keywords124Connectors 127Conditionals127Statement order127

B Configuring management ports for Data Migrator to Cloud130Configuring management ports for Data Migrator to Cloud 134Data Migrator to Cloud Environment Variables 137

Preface

In PDF format this guide provides information about the Data Migratorfeature including how to set up migration policies and schedules

Contacting Hitachi Data Systems

2845 Lafayette StreetSanta Clara California 95050-2627USAhttpsportalhdscomNorth America 1-800-446-0744

Related DocumentationRelease Notes provide the most up-to-date information about the systemincluding new feature summaries upgrade instructions and fixed and knowndefects

Administration Guides

bull System Access Guide (MK-92HNAS014)mdashIn PDF format this guideexplains how to log in to the system provides information about accessingthe NAS servercluster CLI and the SMU CLI and provides informationabout the documentation help and search capabilities available in thesystem

bull Server and Cluster Administration Guide (MK-92HNAS010)mdashIn PDF formatthis guide provides information about administering servers clusters andserver farms Includes information about licensing name spacesupgrading firmware monitoring servers and clusters the backing up andrestoring configurations

bull Storage System User Administration Guide (MK-92HNAS013)mdashIn PDFformat this guide explains user management including the different typesof system administrator their roles and how to create and manage theseusers

bull Network Administration Guide (MK-92HNAS008)mdashIn PDF format thisguide provides information about the servers network usage and explainshow to configure network interfaces IP addressing name and directoryservices

bull File Services Administration Guide (MK-92HNAS006)mdashIn PDF format thisguide explains about file system formats and provides information aboutcreating and managing file systems and enabling and configuring fileservices (file service protocols)

8 PrefaceHitachi NAS Platform Data Migrator Administration Guide

bull Data Migrator Administration Guide (MK-92HNAS005) mdashIn PDF formatthis guide provides information about the Data Migrator feature includinghow to set up migration policies and schedules

bull Storage Subsystem Administration Guide (MK-92HNAS012)mdashIn PDFformat this guide provides information about managing the supportedstorage subsystems (RAID arrays) attached to the servercluster Includesinformation about tiered storage storage pools system drives (SDs) SDgroups and other storage device related configuration and managementfeatures and functions

bull Snapshot Administration Guide (MK-92HNAS011)mdashIn PDF format thisguide provides information about configuring the server to take andmanage snapshots

bull Replication and Disaster Recovery Administration Guide (MK-92HNAS009)mdashIn PDF format this guide provides information about replicating datausing file-based replication and object-based replication providesinformation on setting up replication policies and schedules and usingreplication features for disaster recovery purposes

bull Antivirus Administration Guide (MK-92HNAS004)mdashIn PDF format thisguide describes the supported antivirus engines provides informationabout how to enable them and how to configure the system to use them

bull Backup Administration Guide (MK-92HNAS007)mdashIn PDF format this guideprovides information about configuring the server to work with NDMP andmaking and managing NDMP backups Also includes information aboutHitachi NAS Synchronous Image Backup

bull Command Line Reference Opens in a browser and describes thecommands used to administer the system

Note For a complete list of Hitachi NAS open source software copyrights andlicenses see the System Access Guide

Hardware Referencesbull Hitachi NAS Platform 3080 and 3090 G1 Hardware Reference

(MK-92HNAS016)mdashProvides an overview of the second-generation serverhardware describes how to resolve any problems and replace potentiallyfaulty parts

bull Hitachi NAS Platform 3080 and 3090 G2 Hardware Reference(MK-92HNAS017)mdashProvides an overview of the second-generation serverhardware describes how to resolve any problems and replace potentiallyfaulty parts

bull Hitachi NAS Platform Series 4000 Hardware Reference (MK-92HNAS030)(MK-92HNAS030)mdashProvides an overview of the Hitachi NAS PlatformSeries 4000 server hardware describes how to resolve any problems andhow to replace potentially faulty components

bull Hitachi High-performance NAS Platform (MK-99BA012-13)mdashProvides anoverview of the NAS Platform 3100NAS Platform 3200 server hardware

Preface 9Hitachi NAS Platform Data Migrator Administration Guide

and describes how to resolve any problems and replace potentially faultyparts

Best Practicesbull Hitachi USP-VVSP Best Practice Guide for HNAS Solutions

(MK-92HNAS025)mdashThe HNAS practices outlined in this document describehow to configure the HNAS system to achieve the best results

bull Hitachi Unified Storage VM Best Practices Guide for HNAS Solutions(MK-92HNAS026)mdashThe HNAS system is capable of heavily driving astorage array and disks The HNAS practices outlined in this documentdescribe how to configure the HNAS system to achieve the best results

bull Hitachi NAS Platform Best Practices Guide for NFS with VMware vSphere(MK-92HNAS028)mdashThis document covers VMware best practices specific toHDS HNAS storage

bull Hitachi NAS Platform Deduplication Best Practice (MK-92HNAS031) mdashThisdocument provides best practices and guidelines for using HNASDeduplication

bull Hitachi NAS Platform Best Practices for Tiered File Systems(MK-92HNAS038) mdashThis document describes the Hitachi NAS Platformfeature that automatically and intelligently separates data and metadataonto different Tiers of storage called Tiered File Systems (TFS)

bull Hitachi NAS Platform Data Migrator to Cloud Best Practices Guide(MK-92HNAS045)mdashData Migrator to Cloud allows files hosted on the HNASserver to be transparently migrated to cloud storage providing thebenefits associated with both local and cloud storage

bull Brocade VDX 6730 Switch Configuration for use in an HNAS ClusterConfiguration Guide (MK-92HNAS046)mdashThis document describes how toconfigure a Brocade VDX 6730 switch for use as an ISL (inter-switch link)or an ICC (inter-cluster communication) switch

bull Best Practices for Hitachi NAS Universal Migrator (MK-92HNAS047)mdashTheHitachi NAS Universal Migrator (UM) feature provides customers with aconvenient and minimally disruptive method to migrate from their existingNAS system to the Hitachi NAS Platform The practices andrecommendations outlined in this document describe how to best use thisfeature

bull Hitachi NAS Platform Storage Pool and HDP Best Practices(MK-92HNAS048)mdashThis document details the best practices for configuringand using HNAS storage pools related features and Hitachi DynamicProvisioning (HDP)

bull mdashThis document describes the features of Network File System (NFS)Version 4

bull Hitachi Data Systems SU 12x Network File System (NFS) Version 4Feature Description

bull

1Overview of Data Migrator and Data

Migrator to CloudHitachi NAS Platforms support multiple storage technologies with differentperformance capacity and cost characteristics In order to take full advantageof tiered storage data should be organized using a tiered hierarchy ofimportance and need Data Migrator makes it easier to move data amongdifferent tiers of storage

There are five key reasons to use Data Migrator with the server1 Cost-Efficient Storage Utilization Using Data Migrator newer or

routinely accessed data can be retained on primary storage while olderless-accessed or less performance-critical data is migrated to cost-efficient secondary storage Data that has been migrated to secondarystorage can be moved back to primary storage if it becomes active again

2 Easy Policy-Based Configuration Data Migrator uses logical policiesthat invoke simple building blocks of rules to classify files as available formigration or reverse migration (returning the data from secondarystorage to primary storage) Data Migrator rules and pre-conditions caninclude a files size type access history creation date or owner amongother criteria Files meeting the criteria in the rules and pre-conditionsare migrated (or reverse migrated)

3 Discreet Migration Migrations are handled as automated backgroundtasks with minimal impact on server performance While migrations arein progress all data can continue to be accessed normally

4 Client Transparency Files migrated off primary storage are replacedby a link The link looks and functions identically as the original fileWhen the link is accessed the contents of the associated file areretrieved transparently from their location on secondary storage To theclient workstation they appear indistinguishable During a reversemigration the data is moved from secondary to primary storage and thelink is removed

5 Maximizing Storage Efficiency through Migration ReportsMigration reports are created at the end of each migration cycle Thesereports detail file usage and space consumption patterns revealing

12 Overview of Data Migrator and Data Migrator to CloudHitachi NAS Platform Data Migrator Administration Guide

opportunities to create more aggressive migration policies freeing upmore primary space

Further migration possibilities can be gauged by scheduling Data Migratortest runs where reports can be produced without an actual migration takingplace

Data migration paths

Types of migration targets

Cross volume links in Data Migrator

Cross volume link format considerations

Adding a license key

Overview of Data Migrator and Data Migrator to Cloud 13Hitachi NAS Platform Data Migrator Administration Guide

Data migration pathsBefore any data migration is run the location of the migration target must bedefined by creating a data migration path A data migration path is a longterm relationship between a migration source which can be a file system (forData Migrator and Data Migrator to Cloud) or a virtual volume (for DataMigrator only) and a migration target which may be a local file system a setof file systems a remote location or a list of locations Once a migrationpath has been used it cannot be deleted until files migrated through thatpath have been deleted

The advantages of having this long term relationship between a migrationsource and a target are as follows1 Other system software can stop file systems from being destroyed when

they are actively used by a migration path This avoids migrated filesbecoming inaccessible

2 Where snapshots can be taken on the target (local Data Migrator only)synchronized source and target snapshots can be taken to maintainsnapshot images of migrated files

3 When recovering from tape or replicating a file system that includedmigrated data data which was originally migrated can be placed back onthe migration target

If using virtual volumes individually as migration sources within migrationpaths the file system containing the virtual volumes cannot be used as amigration source itself Currently it is only possible to define one migrationpath for a given migration source

Data Migrator can move data to secondary storage attached directly to thestorage servercluster (a local migration) or to secondary storage attachedto an external server that is not connected to the storage servercluster (aremote migration)

Note Performing a remote migration from one Enterprise Virtual Server(EVS) in a cluster to another EVS in the same cluster is not supported Thereason for this restriction is that it would be dangerous to configure migrationfrom one EVS of a cluster to another EVS on the same cluster The dangerarises because in the case of a failure of the destination (target) EVS thatfailed EVS could fail over to the same node as the migrationrsquos source EVSwhich would cause all the migrated files to become inaccessible

Local migrations provide the benefits described previously and remotemigrations extend the functionality of Data Migrator to allow storage

administrators to free up local storage resources by migrating data to storageattached to a remote NFSv3 server or a Hitachi Content Platform (HCP) Datamay also be migrated to a remote server for a variety of other reasonsincluding archival deduplication or policy-based retention compliance andaccess control As with files migrated locally when a client tries to read a filemigrated to a remote server the file is retrieved and sent to the client sothere is no indication to the client that the file is not in their local file system

Note A single migration path or operation can be made between localtargets or remote targets but not both local and remote targets Remotemigrations are controlled by user defined policies just like the policiescreated for local migrations Only the paths to the secondary storage aredifferent Local migrations have paths to secondary storage that is attachedto the same servercluster that hosts the primary file system while remotemigrations have external paths (the secondary storage is attached to aremote server)

Note A remote migration to a Hitachi Content Platform (HCP) or to a cloudtarget uses the HTTPHTTPS protocol A remote migration to any otherremote server uses the NFS protocol

Cross volume links in Data MigratorData Migrator allows you to move data from primary to secondary storagebased on policies that you define When a file is migrated a cross volume linkis left indicating the new location of the filersquos data A cross volume link is aspecial file on the local file system that points to the file on a remote filesystem The cross volume link stores the migrated filersquos metadata and is usedto construct a handle for the file on the remote file system

When a read request for a migrated file is received the storage server readsthe cross volume link constructs the file handle retrieves the file from thesecondary storage and sends the file to satisfy the read request In this waythe read request is serviced and the client need not be aware that the file isnot actually stored on the local file system

The original cross volume link format (CVL-1) required that the file systemshad to be bound to the same EVS Original cross volume links are supportedby first-generation NAS Platforms as well as the most recent NAS PlatformsEnhanced cross volume links (CVL-2) are supported by NAS Platform Series2000 and NAS Platform Series 3000 as well as NAS Platform 3080 and NASPlatform 3090 CVL-2 is the default Enhanced cross volume links offer thefollowing benefitsbull Remote file systems might be on a storage device attached to a remote

server (not necessarily another NAS Platform) accessible through theNFSv3 protocol This capability called remote migration allows the storage

server to migrate files to a separate storage device such as contentarchival or compliance productsRemote migration to a Hitachi Content Platform (HCP) system issupported through the HTTP or HTTPS (cloud only) protocol for newremote migration paths but pre-existing remote migration paths that werecreated in releases that supported the NFSv3 protocol are still supportedYou cannot however create paths to an HCP system using the NFSv3protocolAccess to files located on the external storage device is a licensed featurerequiring an external volume link (XVL) license and a Data Migratorlicense See the Server and Cluster Administration Guide for informationon adding a license key

bull Local access to migrated file attributes increases performance for getattrlookupreaddir+ requestsFor original cross volume links (CVL-1) some file attributes for a migratedfile are stored on the local file system and some are stored on the remotefile system When an operation requires the attributes of a migrated filethe storage server combines locally stored attribute information withattributes it retrieves from the remote file systemFor enhanced cross volume links (CVL-2) all file attributes for a migratedfile are stored on the local file system When an operation requires theattributes of a migrated file the storage server responds with locallystored attribute information which provides better performanceIn addition local read caching can be used to improve performance whenaccessing migrated files See the Server and Cluster Administration Guidefor information on local read caching

bull Enhanced cross volume links provide improved quota managementWith original cross volume links file length is tracked on the remote filesystem As a result quotas are tracked independently on the local filesystem and on the remote file system By storing attributes on the localfile system enhanced cross volume links make it possible to track quotasentirely on the local file system because file space and file count quotasare managed and calculated using local attributes This simplifies quotamanagement but does not allow storage administrators to set up separatequotas for data based on the datas locationAs a result of differences in how quotas are calculated when using originalcross volume links or enhanced cross volume links mixing of cross volumelink formats is not supported within the same file system By defaultoriginal cross volume links are created for local migrations and enhancedcross volume links are created for all remote (external) migrations butyou can configure the storage server to create only original cross volumelinks Contact Hitachi Data Systems Support Center for more informationabout limiting the creation of cross volume links to the original format

Cross volume link format considerationsWhen choosing which type of cross volume link to use the following areimportant considerationsbull Files migrated to storage devices attached to remote servers (remote

migrations) always use enhanced cross volume linksbull Files migrated locally (to storage attached to the same EVS) can use

original cross volume links or enhanced cross volume links but enhancedcross volume links are used by default

bull If the file system has files that were migrated in previous releases originalcross volume links should be used because original and enhanced crossvolume links cannot be mixed within the same file system You canhowever convert original cross volume links to enhanced cross volumelinks using the cvl-convert command

bull If migrations are being performed on this file system for the first time youshould use enhanced cross volume links

bull When Network Data Management Protocol (NDMP) encounters a crossvolume link to a remote server (an enhanced cross volume link) itincludes the link in the backup stream but does not include the data

bull Original cross volume links use 1 KB of space and enhanced cross volumelinks (CVL-2 links) use 32 KB of space

Adding a license keyAdding a license key can enable services or increase the capabilities of yoursystem To add a license key

Procedure

1 Navigate to Home gt Server Settings gt License Keys

2 Click add

The following table describes the fields on this page

FieldItem Description

Add a License Key

License Key To manually enter the license key enter the license key and then click add

Import License Keys From a File

License Key File

Name

To import a license key from a file click Browse navigate to the file that

contains the license key and then click Import

cancel Closes the page without saving configuration changes

Note After adding a license key if a reboot is required in order to starta serviceprotocol or enable a feature you will be instructed to reboot orrestart the system

You can now either enter the key manually or import it from a filebull To enter the key manually type it in the field then click addbull To Import the key click Choose File navigate to the file select the

key file then click Import

After all the keys have been entered or imported they will be displayedon the License Keys page Follow the instructions to reboot the system(if necessary)

2Hitachi Data Systems Data Migrator

This chapter describes the Data Migrator features and provides instructionson how to add paths rules policies and schedules The topics listed on theleft of this page represent the Data Migrator features and tasks Click thecorresponding link to advance to the selected topic

If you are using the Data Migrator to Cloud refer to Hitachi Data Systems onpage 54

Configuring Data Migrator

Data Migrator considerations

Viewing data migration paths

Viewing data migration rules

Viewing data migration policies and schedules

Data Migration status and reports

Migration to HCP Systems

20 Hitachi Data Systems Data MigratorHitachi NAS Platform Data Migrator Administration Guide

Configuring Data MigratorTo use Data Migrator you must define the followingbull Data migration paths from primary to secondary storage

Data migration paths define the relationship between primary andsecondary storage The primary and secondary storage defined in the datamigration paths must be assigned to the same EVS

bull Data migration rules which define the properties of files that will bemigrated

bull Data migration policies which define rules to apply to specific datamigration paths based on the available free space on the source filesystem or dynamic file volumeFree space is calculated as follows For a file system free space is the amount of unused space allocated to

the file system (before it automatically expands if automatic expansionis enabled for the file system)

For a virtual volume if a quota has been defined free space is theamount of unused space before reaching the usage limit of the quota forthat virtual volume If a quota has not been defined for the virtualvolume free space is the same as the free space for the file system

bull Schedules which define when data migration policies are run and files aremigrated

Data Migrator considerationsThe server uses Data Migrator with the following considerationsbull Snapshots and local migrationsmdashIf files are migrated locally (to storage

attached to the same EVS) when snapshots are created on the primaryfile system corresponding snapshots are automatically created on thesecondary file system This preserves snapshot protection on migratedfiles Likewise when a snapshot is deleted on the primary file system thecorresponding snapshot on the secondary file system is automaticallydeletedWhen attempting to access a locally migrated file through a snapshot onprimary storage the server will look for the corresponding snapshot onsecondary storage and retrieve the migrated data from that snapshot Ifthe secondary file system does not contain any snapshots the file contentswill be retrieved from the live file system

bull Snapshots and remote migrationsmdashIf files are migrated to storageattached to a different server (a remote migration) when snapshots arecreated on the primary file system corresponding snapshots are notcreated on the secondary file systemTo preserve snapshot protection on migrated files for remote migrationsyou must ensure that snapshots are taken of the storage attached to the

Hitachi Data Systems Data Migrator 21Hitachi NAS Platform Data Migrator Administration Guide

remote server Snapshots on the secondary file system are not managedused or accessed by the storage serverWhen a snapshot is accessed and the snapshot contains a file system witha cross volume link no special processing of the cross volume link isperformed if the file in the snapshot is equivalent to the live file If the filein the live file system has been modified since the snapshot was taken (if itdiffers from the file in the snapshot) attributes from the file in thesnapshot are returned for getattrlookupreaddir+ requests but an error isreturned for read requests

bull Virtual volumemdashIf files are migrated locally either enhanced crossvolume links or original cross volume links may be used depending on yourconfiguration When files are migrated to a remote server enhanced crossvolume links are always used If enhanced cross volume links are used virtual volumes are not

recreated at all on the secondary storage If original cross volume links are used virtual volumes that are

present on primary storage will be automatically recreated on thesecondary storage when the data is moved during the first scheduledrun of the data migration policy

bull Quota space trackingmdashQuotas are enforced only on the file system orvirtual volume on which they were created When a file is migratedthrough Data Migrator however the contents are moved from one filesystem to another file system or virtual volume which may be on aremote server Cross volume links are used to link the data from itsoriginal location to its new location Quota tracking is different based uponthe type of cross volume link being used When enhanced cross volume links are used and files are

migrated to a file system on a remote server quotas are tracked just asif the file had remained in its original location Quotas are trackedentirely on the local file system because file space and file count quotasare managed and calculated using local attributes This behaviorsimplifies quota management but does not allow storage administratorsto set up separate quotas for data based on the datas location

When original cross volume links are used and files are migratedto another file system or virtual volume on the same serverclusterquotas on primary storage are only effective on files that have not beenmigrated To track space utilization of migrated data quotas must bemanually defined on secondary storage Quota restrictions on virtualvolumes cannot be set until after the policy has been completed

bull Backup restore and replication of migrated filesmdashWhen backing upa migrated file NDMP will backup the entire contents of the file byretrieving it from secondary storage Additionally the backed up file will beidentified as having been a migrated file In this way if the file is restoredto a file system or virtual volume that has been configured as primarystorage in a data migration path the contents of the file will automaticallybe restored to secondary storage leaving a cross volume link on the

primary storage If the restore target is not part of a data migration paththe file will be restored in its entiretyAlternatively the NDMP environment variableNDMP_BLUEARC_EXCLUDE_MIGRATED can be used to prevent migrateddata from being backed up This can also be useful if the effective datamigration policies are configured to migrate non-critical files such as musicand video files from home directories or aged data It can also improvebackup and replication time and isolate the backup data set to includeonly the critical information on primary storageYou can back up a file system that is the target of a data migration This isaccomplished by performing backup of the primary file system andselecting an option to back up only the files that have been migrated tothe secondary file system This functionality is controlled via theNDMP_BLUEARC_INCLUDE_ONLY_MIGRATED NDMP environmentalvariable which does the opposite of theNDMP_BLUEARC_EXCLUDE_MIGRATED See the Backup AdministrationGuide for more informationIt is important to remember that Data Migrator extends the maximumavailable capacity of primary storage by migrating data to secondarystorages This means that the capacity of the backup solution whethertape library or a replication target must also support the new maximumavailable capacity To maintain a reliable backup and recovery systemensure that the capacity of the deployed backup solution is at least equalto the combined capacity of primary and secondary storage Alternativelyuse NDMP_BLUEARC_EXCLUDE_MIGRATED to isolate the backup datasetto only those files that are hosted natively on primary storage

Replication of migrated filesmdashIf a file has been migrated from primarystorage and a replication operation attempts to copy the file NDMP can beset tobull Ignore migrated filesmdashIf set to ignore the replication operation copies

only the files on the primary storage (migrated files are not copied)bull Recreate links to migrated filesmdashIf set to recreate links the replication

operation copies only the details of the cross volume link The crossvolume link is recreated on the destination if the relevant externalmigration data path is in place and the migrated file is accessible

bull Remigrate migrated files (the default)mdashIf set to remigrate thereplication operation copies the file contents but marks the file as havingbeen externally migrated The destination re-migrates to secondarystorage if there is an existing data migration path

bull Unmigrate migrated filesmdashIf set to unmigrate the replication operationcopies all of the files to the primary without remigrating

This functionality is controlled using the NDMP environment variableNDMP_BLUEARC_EXTERNAL_LINKS See the Backup Administration Guide formore informationbull Files with hard linksmdashFiles with hard links are not migrated

bull Migrated file accessmdashFiles that have been migrated should not beaccessed directly by clients on the secondary file system All access tomigrated files should be done through the primary storage server

Procedure

1 Navigate to Home gt Storage Management gt Data Migration Paths

Primary File System The file system from which data will be migrated

Primary Virtual Volume If a virtual volume has been selected as primary storage this

field displays the name of the virtual volume from which data

will be migrated

Secondary Target Type Destination target to which the data will be migrated

Secondary File Systems Displays the secondary file system

EVS The EVS hosting the file system from which data will be

migrated

Status Status of the data migration path The status should always be

OK if otherwise migrated files might be inaccessible

Add WFSHNAS Path Displays the Add WFSHNAS Path page

Add Cloud Path Displays the Add Cloud Path page

delete Deletes the specified migration policy

Policies and Schedules Goes to the Data Migration page

Data Migration Rules Goes to the Data Migration Rules page

Data Migration CloudAccounts

Goes to the Cloud Accounts and Destinations page

Configuring Data Migrator pathsbull Primary storage typically Fibre Channel disk arrays will be the source

for data migrations

Note WORM file systems cannot be specified as a Data Migrator source

bull Secondary storage typically SATA disk arrays will be the target for datamigrations Note that there are two types of paths to secondary storage

Note WORM file systems cannot be specified as a Data Migrator path

Local paths which are paths to secondary storage attached to thesame EVS storage server or cluster Local paths can be added usingthe Web Manager interface

External Paths which are paths to secondary storage that is attachedto a remote server (a NAS Platform or another server using the NFSprotocol or a Hitachi Content Platform using the HTTP protocol)External paths cannot be added using the Web Manager interfaceInstead you must use CLI commands

After Data Migrator has been configured data will be migrated from primaryto secondary storage based on the data migration rules and schedulesfreeing up space and extending the capacity of the primary storage

Caution Dysfunctional backups alert Accessing files directly on secondarystorage might alter access and modification times of the files resulting inunexpected results when performing backups The organizational structure ofmigrated data on secondary storage does not mirror that of primary storage

Caution Lost access to migrated files alert If only the primary or only thesecondary file system is moved to a different EVS access to migrated fileswill be lost If both the primary and the secondary file systems are moved tothe same EVS access to migrated files will be retained When moving filesystems File System Relocation is the recommended method because whenusing File System Relocation if the file system being moved is a member of adata migration path both the data migration source file system and thetarget file system are relocated See the File Services Administration Guidefor more information

Caution Exclusive migration pathing Once a migration path has beenassigned to a virtual volume a subsequent migration path cannot be createdto its hosting file system Also once a migration path has been assigned to a

file system subsequent migration paths cannot be created from virtualvolumes hosted by that file system

Note When defining data migration paths specify a file system or virtualvolume as the primary storage Once a file system is selected as primarystorage that entire file system including all virtual volumes is included as apart of the data migration policy Therefore in order to create individualpolicies for different parts of a file system create virtual volumes and assigneach virtual volume a unique migration path

Adding a local WFSHNAS data migration path

Procedure

2 Click Add WFSHNAS Path

Note WORM file systems cannot be specified in a Data Migrator path

Section ItemField Description

Primary EVSFile

System

The EVS and file system of the primary storage This defines

the source of the data migration path To change the currently

selected EVS and file system click change

Virtual Volume By default data migration policies include the entire file

system To configure migrations on a per virtual volume basis

fill this check box and select the virtual volume to be used as

the primary storage for this data migration path

Secondary Available File systems to which the data will be migrated (the

destination file system) Select the destination file system

from the list The file systems you select should be on

secondary storage

Note When creating a policy for testing purposesselect None (Test Only) Running this policy will thendetermine the outcome of the migration operationwithout actually moving data In most cases youshould specify a single destination file system tocreate a single-target migration path However ifthe amount of data is too large for a single target filesystem you may want to nominate multiple filesystems as targets to create a multi-targetmigration path

For multi-target migration paths you should beaware of the following

bull Data is distributed between the destination filesystems based on the amount of free spaceavailable on those file systems If the destinationfile system is expandable the data distributionalgorithm calculates free space not based on thefile systemrsquos current size but on the maximumsize to which a file system can be expanded

bull Once specified multi-target paths may not bemodified through Web Manager If you need tochange the migration path targets for instance toadd an additional destination file system you mustuse the migration-expand-target commandthrough the CLI

Selected The file systems selected to be the destination of themigration

OK Click to save changes

Cancel Click to cancel and return to the previous page

3 Select the primary file system or virtual volume whose data will bemigrated to a file system in secondary storage Ensure that both theprimary and secondary data belong to the same EVS

4 Verify your settings then click OK to save or cancel to decline

About external data migration pathsExternal data migration paths are not defined through Web Manager InsteadCLI commands are used to specify the path to external secondary storageThese commands arebull migration-add-external-pathbull migration-change-external-pathbull migration-delete-external-pathbull migration-expand-external-path

For information about these commands refer to the Command LineReference or the man page for each command

You should specify a unique external path for each file system being migratedto a remote server

After an external migration path has been defined it will be visible andavailable for selection in the Web Manager Data Migration Paths page

Note Do not define an external migration path from one EVS in a cluster toanother EVS in the same cluster The reason for this restriction is that itwould be dangerous to try to migrate from one EVS of a cluster to another

EVS of the same cluster If the destination (target) EVS fails during themigration it could fail over to the same node as the source EVS which wouldcause all the migrated files to become inaccessible After the externalmigration path has been configured using the CLI all remaining externalmigration management tasks may be performed through Web Managerincluding specifying migration policies rules and schedules

Note When adding external migration paths make sure that the remoteserverrsquos IP address or host name is correct and if using a host name makesure that the host name is resolvable (fully qualified domain names are alsoacceptable)

Viewing data migration rulesThe Data Migration Rules page lists all existing rules and provides forediting or removal of selected rules and creation of new rules Data migrationrules are used in conjunction with data migration paths to form datamigration policies1 Navigate to HomegtStorage ManagementgtData Migration Rules to display

the Data Migration Rules page

ItemField Description

Name The name given when the rule is created It is used to identify the rule when

creating or configuring policies

Type The type of data migration that this rule can be used for

Description A description of the rule to help identify the criteria to be applied

In Use by

Policies

The check box is filled when a rule is being used by one or more policies

details Click for a selected migration rule to display its complete details

add Click to create custom rules that will define the criteria by which the files will be

migrated

remove Click to remove one or more existing rules

Add by Template Click to create simple rules using predefined templates

Policies and

Schedules

Goes to the Data Migration Policies and Schedules page New policies and

schedules can be created there

Data Migration

Cloud Accounts

Goes to the Cloud Accounts and Destinations page New cloud accounts and

destinations can be created there

Data Migration

Paths

Goes to the Data Migration Paths page New paths can be created there

Caution Once created do not change a data migration rule without verifyingthat it is not used by existing policies as such changes might result inunintentional changes to existing policies

See Rules syntax on page 123 for details on syntax keywords connectorsconditionals and statement order

Related references

bull Creating specific and detailed rules on page 122bull Rules syntax on page 123

Adding a data migration rule by templateRules define the properties of files that will be migrated

Procedure

1 To create rules that suit more specific migration needs navigate toHome gt Storage Management gt Data Migration Rules to displaythe Data Migration Rules page and then click Add by Template todisplay the Data Migration Rule Templates page

2 Select a Rule Template then click nextThe following table describes each of the available rule templates

Rule Template Description

By Last Access Migrates all files that have remained inactive (or have been active)

within a certain period of time

By Creation Time Migrates all files created before or after a specific point in time

By File Name Migrates all files with the same name and extension An asterisk

can be used as a wildcard character For examplebull dbfiledb migrates all files with the name dbfile and the

extension dbbull db migrates any file with an extension of db regardless of the

file namebull dbfile migrates all files with the name dbfile and any

extensionbull dbfiledb migrates all files ending with the name dbfile and

the extension dbbull dbfile migrates all files with a name beginning with dbfile

and having any extension

By Path Migrates all files under a particular directory

By User Migrates all files of the specified users

Note This rule does not apply to the Data Migrator toCloud

By File Name and Last

Access

Migrates files of a certain name andor extension (as described

above) that have remained inactive for a certain period of time

By Path and Last Access Migrates all files under a certain directory that have remained

inactive for a certain period of time

3 Enter requested template-specific informationbull If you select By Last Access the Data Migration Rule Last

Access Template page contains the fields described in the followingtable

Name Enter a name for the new rule The rule name can include only

alphanumeric characters hyphens and underscores

Description Enter a description of what the rule does

Include Criteria To specify the maximum period a file can be inactive before being

migrated to a secondary file system1 From the menu select inactive

The menu includes an option for selecting the oppositescenario that is to choose active within to specify files thathave been active within the specified period

2 From the menu select the period (days hours or minutes)3 Enter the threshold quantity period

bull If you select By Creation Time the Data Migration Rule CreationTime Template page contains the fields described in the followingtable

Include Criteria To specify the point in time for the migration rule1 From the first menu select more than or less than2 Enter the threshold number3 From the second menu select month(s) week(s)

day(s) hour(s) or minute(s)

bull If you select By File Name the Data Migration Rule File NameTemplate page contains the fields described in the following table

Case-sensitive

pattern checks

To specify case-sensitive rule checking select this check box

Include Criteria To specify the type of files (based on their file extension) to be

migrated to a secondary file system1 From the menu select include

The menu also has an option for selecting the oppositescenario that is selecting to exclude files not of thespecified type

2 In the all files named field enter the file name andextension More than one file name or extension can benamed in this field separated by commas for instancejpg bmp zip

bull If you select By Path the Data Migration Rule Path Templatepage contains the fields described in the following table

Case-sensitive

pattern checks

Include Criteria To specify the path to the files under a certain directory1 From the menu select include

The menu also has an option for selecting the oppositescenario that is to select exclude to select all files that arenot in the path

2 In the all files in the path field enter the directory filepath

bull If you select By User the Data Migration Rule User NameTemplate page contains the fields described in the following table

Note This option only applies to WFSHNAS and does not apply toData Migrator to Cloud

Type You can only enable the WFSHNAS option This rule does not

apply to cloud options

Case-sensitive

pattern checks

Include Criteria To specify the user names for the owners of the files to be

The menu also has an option for selecting the oppositescenario that is selecting to exclude files from owners otherthat the specified owners

2 In the all files in the path field enter the UNIX or Windowsuser names for the owners of the files you want to migrateMore than one user name can be listed in this field butnames must be separated by commas For instance jjamesmycosmithr mycowsmithWindows user names are specified in the form domainusername and backslashes in user names should not be escaped(double backslashes are not required)

bull If you select By File Name and Last Access the Data MigrationRule Last Access Time and File Name Template page containsthe fields described in the following table

Case-sensitive

pattern checks

To specify case-sensitive rule checking fill this check box

Include Criteria To migrate inactive files from a specified directory to a secondary

file system1 In the All files named field enter the file name extension of

the files to be migrated For example notetxt note ormp3

2 In the All files not accessed within___ field enter thethreshold quantity

3 Select the period from the list You can choose days hoursor minutes

bull If you select By Path and Last Access the Data Migration RuleLast Access Time and Path Template page contains the fieldsdescribed in the following table

Case-sensitive

pattern checks

file system1 In the All files in the Path field enter the directory file path2 In the All files not accessed within___ field enter the

threshold quantity3 Select the period from the list You can choose days hours or

minutes

Adding a custom WFSHNAS data migration ruleUse the Add Data Migration Rule page to name define and add datamigration rules using rule syntax Rules can be built with a series of INCLUDE

and EXCLUDE statements Each of these statements can contain a number ofexpressions specifying the type of files and the conditions under which theywill be migrated

For exampleINCLUDE (ltFILENAME mp3gt AND ltFILE_SIZE_OVER 2GBgt)

Procedure

1 Navigate to Home gt Storage Management gt Data Migration Rulesand then click add to display the Add Data Migration Rule page

The following table describes the fields in this page

Type Click the WFSHNAS or Cloud option as appropriate

Case-sensitive

pattern checks

Rule Definition Insert the syntax for the data migration rule

See Creating specific and detailed rules on page 122 for moreinformation about rule definitions

2 Verify your settings then click OK to save the rule or click cancel todecline

Modifying a data migration rule

Procedure

1 Navigate to Home gt Storage Management gt Data Migration Rules

2 Fill the check box next to the rule to modify and then click detailsThe following table describes the fields on this page

Name Displays the name of the rule

Description The description of the rule Make any changes as appropriate

In Use by

Policies

Displays any associated policies in use for this policy If none are used displays

Not in use

Type Displays the type of rule either Cloud or WFSHNAS

Case-sensitivepatternchecks

Select the check box if the rule checking must be case sensitive

Rule

Definition

Displays the current definition in use Modify if necessary

OK Saves configuration changes and closes the page

3 Make updates as necessary4 Click OK

Viewing data migration policies and schedulesHaving created both data migration paths and data migration rules datamigration policies can now be created Policies assign a rule or set of rules toa specific data migration path They also define the conditions that initiatedata migrations

Procedure

1 To view data migration policies navigate to Home gt StorageManagement gt Data Migration to display a list of policies andschedules

The following tables describe the fields on this page

ItemField for

PoliciesDescription

Name Name of a data migration policy

EVS Primary EVS from which the migration originates

Primary File

System

Files in the primary file system or virtual volume that will be migrated

Secondary File

System

Secondary file system to which all data will be migrated to

Note If the path to the secondary file system is an externalpath the name or IP address of the server hosting the secondaryfile system is also displayed in parentheses The displayed servernameIP address is a link and you can click the link to displaythe full path

Rule Rules that can be triggered in this migration policy

details Displays the details for the selected policy

add Advances to the Add Data Migration Policy page

remove Deletes the selected migration policy

Data MigrationRules

Advances to a page where all the configured data migration rules will be

displayed New rules can be created here as well

ItemField for

PoliciesDescription

Data MigrationCloud Accounts

Advances to the Cloud Accounts and Destinations page

Data MigrationPaths

Displays the configured data migration paths New paths can be created

as well

NDMPConfiguration

Advances to a page where the NDMP can be configured by entering the

username password and NDMP version number

ItemField for Schedules Description

Policy NameSchedule ID Displays the name given to the Data Migration Policy

ServerEVS Displays the primary EVS and server from where the migration is

scheduled to originate

Next Run Displays the month date year and time for the next scheduled

data migration run for this policy

Migration Type Displays the type of data migration that has been scheduled torunbull Migrate files (followed by only once daily or weekly

depending on the selected scheduled type)bull Simulate migration - Generates a one-time report of files that

would be migrated Does not actually migrate filesbull Report migrated files - Generates a one-time report with a

list of previously migrated files This migration type onlyapplies to WFSHNAS and not Data Migrator to Cloud

Last Status Displays the final status of the last run of the data migration

operation

details Displays the current settings for the selected schedule

add Advances to the Add Data Migration Schedule page

Stop Migration(s) Click the Stop Migrations link to stop a selected in-process

migration Only migrations in progress can be stopped

Data Migration Status ampReports

Advances to a page where all the completed migration runs willbe listed in detail

Adding a WFSHNAS data migration policy

Procedure

1 Navigate to Storage Management gt Data Migration and then clickadd under the Policies section to display the Add Data MigrationPolicy page

Item Description

PolicyIdentification

This section allows you to specify a name to identify the migration policy

Name Name for the new data migration policy

Migration Path This section allows you to specify the data migration path to be used by the

migration (or reverse migration) policy

Migrate Data When creating a migration policy this section displays the data migration

source and target informationbull Primary EVSFile System Displays the name of the EVS and file

system for primary storage (the migration source)bull Virtual Volumes If a virtual volume has been selected as primary

storage the virtual volume will be displayedbull Secondary Target Type Displays WFSHNAS to represent the

migration typebull Secondary File System Displays the name of the file system on

secondary storage that will host the migrated data (the migrationtarget)

Reverse Migrate When creating a reverse migration policy this section displays thedestination for the reverse migration (the original data migration sourceand target information) Files that have been migrated from the original

Item Description

source to secondary storage will be returned to this EVS and File Systemwhen the reverse migration policy criteria are met

change Click this button to open the Select a Path page to select a different path

(To create

paths see DataMigrationPaths)

Advances to the Data Migration Paths page which allows you to create

data migration paths

Pre-Conditions This section allows you to specify the rules (the criteria) that the files mustmatchmeet in order to be migrated (or reverse migrated) according to thispolicy

Available WFS

HNAS Rules

Rules with specific threshold limits are displayed here This list of rules

define the set of conditions which trigger the migrationreverse migration

You canbull Add a Pre-condition to the Selected Rules list by selecting it and clicking

the right arrow (gt)bull Remove a rule from the Selected Rules list by selecting it and clicking

the left arrow (lt)

This policy will be run either by a defined schedule or when startedmanually Once the policy is run the threshold specifies when the selectedrules are applied You can specify that the selected rules will be appliedwhen either of the following conditions are metbull When the primary file systems free space falls below X (set the

percentage level for the condition)bull When other conditions are not met These conditions are defined in the

selected rule(s)

After selecting rules and the threshold save the policy by clicking OK

Selected WFS

HNAS Rules

Displays the rules containing the criteriaconditions to be used to determineif a file should be migrated The criteria in the rules are applied when thethreshold (the when condition specified in the Available Rules section) ismet

(To create rules

see DataMigrationRules)

Advances to the Data Migration Rules page which allows you to create

rules

2 Add a descriptive name for the policy The name should make it easy torecognize the purpose of the policy

3 Select a migration path You can specify that the policybull Migrate Data To move the data from the primary file system to the

secondary file system when the criteria defined in the Selected Rulesare met

bull Reverse Migrate To move the data from the secondary file systemback to the primary file system when the criteria defined in theSelected Rules are met

4 Select one of the migration paths you created on the Data MigrationPaths page The path specifies the source and the destination of themigration For abull Migration operation the source is the primary file system and the

destination is the secondary file system

bull Reverse migration operation the source is any secondary file systemand the destination of the revers migration is the primary file system(the original source)When a file is migrated a CVL (cross volume link) or an XVL (externalvolume link) is left in the primary file system to point to the file in thesecondary file system Because the type of link used depends on thedestination of the migration the source of a reverse migration for afile may be

Secondary file system may be Link Type

A file system on the same EVS as the primary

file system

CVL-1

An external secondary file system (a secondary

file system on an external device)

CVL-2

If the currently displayed path is not the one you want this policy to useclick change to display the Select a Path page

Select the path you want the policy to use then click OK

Note If you are adding a policy to perform a test migration a validmigration path is required but it may be a real path involving primaryand secondary file systems or a ldquotest-onlyrdquo path in which a secondaryfile system does not exist

5 Select the rules and specify when the rules will be applied Using thePre-conditions section specify the rules that contain the criteria thatmust be met in order to migrate the file Also choose the threshold thattriggers the migration of the file

6 Verify your settings then click OK to save the policy as defined orcancel to return to the Data Migration page

Using Pre-Conditions

When a migration policy is scheduled to run it evaluates the percentage ofavailable free space in the Policyrsquos primary storage Based on this analysisone rule may be triggered to define the data set subject to migrationMigrations of data from primary storage then occurs based on the statementsin the rule that was triggered Only a single rule will be engaged during anyparticular migration operation

When defining pre-conditions Hitachi Data Systems Support Centerrecommends aggressive tiering specifically it may be desirable tomigrate mp3 files and the contents of the directory tmp regardless of theavailable free space Then if free space on primary storage is reduced to lessthan 50 also to migrate all files not accessed within the last sixty daysFinally if available free space is reduced to less than 15 also to migratethe contents of usersrsquo home directories

The following rules illustrate this scenario

Rule Statement

Rule 1 INCLUDE (ltFILENAME mp3gt) OR ltPATH tmp)

INCLUDE (ltINACTIVE_OVER 60gt)

INCLUDE (ltPATH homegt)

Related pre-conditions

bull Rule 3 if free space is less than 15bull Rule 2 if free space is less than 50bull Rule 1 if no other condition applies

When the migration policy is scheduled to run different rules may betriggered based on the available free space on primary storage When amigration policy is engaged only a single rule will be triggered to run

For examplebull If free space is at 80 then Rule 1 will be usedbull If free space is at 40 then Rule 2 will be usedbull If free space is at 10 then Rule 3 will be used

When percentage thresholds are specified they are evaluated based onwhole number percentages This means that if two rules are specified onethat will take effect at 8 of free space and one at 9 of free space if thefile system has 85 free space available then the rule with the 8 pre-condition will apply

Note If the primary storage defined in the migration path is a virtualvolume free space will be based on the limit defined by the virtual volumequota If this quota has not been defined then free space available will bebased on the free space of the file system hosting the virtual volume

Connection Errors

When attempting to add a new migration policy a connection error may beindicated by a message saying Unable to connect to ltIP addressgt or Erroraccessing ltsourcedestinationgt server

The Unable to connect to message means one of the followingbull The server is not currently powered up or is temporarily disconnected from

the network The server must be available and properly connected whencreating a migration policy

bull The NDMP service may be disabled The migration uses the NDMP servicewhich must be enabled when adding or running replications Use the NDMPconfiguration page (or the ndmp-status command) to enable and start theNDMP service

bull The Gigabit Ethernet port providing access to the EVS which hosts the FileSystem is not accessible from the SMU This may be the case if thenetwork is set up with private subnetworks as commonly used with VLANsIn this case the server may have been configured so that SMU access isthrough the management ports instead of the ports set using the ndmp-management-ports-set command

The ldquoError accessing serverrdquo message may occur as a result of restrictingNDMP access using the ndmp-option command The allowip and blockipoptions can be set such that the SMU is not allowed to access the NDMPservices via the standard routes If the NDMP connection restrictions aredefinitely required change the configuration of the server to allow SMUaccess via the management ports using the ndmp-management-ports-setcommand The SMU connections then bypass the allowipblockip checks

Modifying a data migration policy

Procedure

1 Navigate to Home gt Storage Management gt Data Migration2 Select the policy to modify and then click details to display the Modify

Data Migration Policy page

The following table describes the fields

Item Description

Name of the data migration policy

Migration Path The specified data migration path to be used by the migration (or reverse

migration) policy

Pre-Conditions

This section allows you to modify the rules (the criteria) that the files mustmatchmeet in order to be migrated (or reverse migrated) according to thispolicy

Available Rules Rules with specific threshold limits are displayed here This list of rules

the left arrow (lt)

This policy will be run either according to a defined schedule or whenstarted manually Once the policy is run the threshold specifies when theselected rules are applied You can specify that the selected rules will beapplied when either of the following conditions are metbull When the primary file systems free space falls below X (set the

selected rule(s)

Selected Rules Displays the rules containing the criteriaconditions to be used to determineif a file should be migrated The criteria in the rules are applied when thethreshold (when condition specified in the Available Rules section) is met

(To create rules

rules

cancel Click to cancel and return to the previous page

About the ndmp-management-ports-set commandThe SMU replication and data migration features use the NDMP service on theNAS server The NDMP service is usually accessed via the IP address of theEVS which hosts the file system this access usually happens through aGigabit Ethernet port In some cases the IP address is within a privatesubnetwork and is not accessible from the SMU When this is the case thendmp-management-ports-set command can be used to request that the SMU

access goes through the management ports and is then relayed to the NDMPservice

The ndmp-management-ports-set command takes two parameters which arethe TCP ports One is used to accept the incoming connection on themanagement port and one is used to pass the requests to the NDMP codeThese must be ports that are not in use by any other service In particularthese ports must not be the standard NDMP service port The port numbers10001 and 10002 usually work and being next to the standard NDMP port10000 can be useful in identifying the port usage

Having set up the NDMP management ports this way all SMU replication anddata migration NDMP accesses will be routed via the management port Notethat the actual data transfer connections involved are between the NASserver EVSs and do not run over the management connections In particulara replication between two NAS servers passes the data over a TCP connectionbetween EVS IP addresses through the Gigabit Ethernet ports Therefore thetwo EVSs must have IP addresses that can communicate with each other

Migration schedulesAfter a data migration policy has been defined it must be scheduled Thedecision on how often to run a policy may be affected by the rules selected inthis policy For examplebull A policy with a single rule to migrate all mp3 files may be scheduled to run

once every monthbull Another policy used to archive a working project directory once the

project is complete may be scheduled as a Once Only Schedulebull Other policies which migrate based on various Pre-conditions and are

triggered on available free space may be scheduled to run every week

When planning migration schedules schedule migrations during off-peaktimes such as evenings and weekends

After a data migration has begun additional data migrations for the samepolicy cannot be started until the current one has completed However it ispossible to start multiple concurrent data migrations if each have its ownpolicy

Adding a Data Migration schedule

Note You must create a migration policy before you can schedule it

Procedure

1 Navigate to Home gt Storage Management gt Data Migration

2 Click add in the Schedule section of the page to display the Add DataMigration Schedule page

Data Migration

Policy

Select a migration policy from the list

Migration Type Choose from the following migration type options

Migrate Files Select this option and then choose only once daily orweekly from the list Selecting the Once Only option causes the policy torun only once at the specified date and time

Simulate Migration Select this option to generate a report of files thatwould be migrated Does not actually migrate files Only run once

Report Migrated Files Select this option to generate a report with a list ofpreviously migrated files Only run once This option only applies to WFSHNAS and does not apply to Data Migrator to Cloud

Date and Time

to Start

Specifies when the policy will run

From the calendar next to the field select the start date for the policysinitial run The selected date appears on the field

Enter the scheduled run time in a 24 hour setting (for example 1159 PMwill be entered as 2359) The current SMU date and time are providedbelow for reference

Duration Type Choose from the following duration typesRun until migration completes indicates that the scheduled policy shouldrun until it has completed

Suspend migration after x HoursMinutes Resume when the nextschedule starts indicates the scheduled policy should be suspended afterthe time specified and resumed at the next scheduled interval Note thatthis option only applies to Data Migrator to Cloud and not to WFSHNAS

3 Verify your settings Then click OK to save or cancel to decline

Modifying a scheduleOnce defined schedules can be easily modified to meet the changingrequirements of data migration policies When modifying a schedule thescheduled date and time as well as the interval in which the schedule willrun can be changed

Procedure

1 Navigate to Home gt Storage Management gt Data Migration2 Under the Schedules section of the page fill the check box next to the

schedule to modify and then click details

Data Modify

Policy

Name of the schedule This is a read-only field

Data Migration

Type

The type of migration WFSHNAS External or Cloud

Migration Type Displays the current optionMigrate files - options arebull only oncebull dailybull weekly

Simulate Migration - Generates a report of files that would be migratedDoes not actually migrate files Only run once

Report Migrated Files - Generates a report with a list of previouslymigrated files Only run once This option applies to WFSHNAS andExternal data migration types and does not apply to Data Migrator toCloud type

Next Run Date and time of next scheduled run

Initial Run Date and time of initial run

Reschedule To change this fill in the check box and enter the new date and time

Duration Type bull Run until job completes indicates that the scheduled policy shouldrun until it has completed

bull Suspend migration after x HoursMinutes Resume when thenext schedule starts indicates the scheduled policy should besuspended after the time specified and resume at the next scheduledinterval Note that this option only applies to the Data Migrator toCloud

3 Make any modifications as necessary4 Click OK

Data Migration status and reportsAfter a data migration policy has completed a cycle it generates a datamigration report that includes details about files migrated including availablefree space before and after the migration Reports of the last five scheduledmigrations are routinely saved the rest are purged If a schedule is deletedso are its reports

Migration reports can be downloaded in CSV format then imported into aspreadsheet and processed saved or printed These reports are useful whenstudying the system access patterns file storage tendencies the efficiency ofrules paths policies and schedules By gauging file and space usagestatistics of Primary and secondary storage Data Migrator reports can beused to refine a rule or pre-condition The more precise and aggressive therule the better Data Migrator serves the storage system

To view a list of existing reports navigate to HomegtStorageManagementgtData Migration Status amp Reports

Item Description

Schedule ID ID number for the completed migration

Server Primary file systems server

EVS Primary file systems EVS

Policy Policy name

Completed Year month day and time when the migration was completed

Files Migrated Number of files that were migrated

Status Migration completion status

details Opens the Data Migration Report page where you can view the details of the

select report

remove Click to remove a selected report

Item Description

Remove All Click to remove all migration reports in the list

Policies and

Schedules

Opens the Policies and Schedules page where you can view add and remove

existing policies and schedules

Viewing details of a data migration reportTo view data migration reports navigate to Home gt Storage Management gtData Migration Status amp Reports and then click details to display the DataMigration Report page

The following table describes the contents of this page

Item Description

Report Summary

Migration Policy Completed migration policy name

Schedule ID Migration schedule ID

Migration Type Type of migration migrate files simulate migration report migrated files

Frequency How often the Policy is scheduled to run

Start Time Date and time when the migration began

End Time Date and time when the migration ended

Duration Duration of migration

ServerEVS EVS on which the Primary and secondary storage reside

Item Description

Rule Used Rule used by the policy

Amount Migrated The migrated amount of data in GB

Files Migrated Quantity of files that were migrated If files have been migrated click this to

view a list of the files that were migrated The list provides details on their

path size and their start and end times

Files Excluded Number of files that should have been migrated but were not For example

files in use at the time of the migration may not be migrated

Primary File System Statistics

Pre-Migration File

System Space Used

File system size snapshot size and the total used space before the

migration

Post-Migration File

System Space Used

File system size snapshot size and the total used space after the migration

File System

Capacity

File systems total capacity

Live File System

Reclaimed

Reclaimed space in the live file system defined as the usable space on the

file system that is the part of the file system not reserved or in use by

snapshots

Total File System

Reclaimed

Reclaimed space in the total file system defined as the entire capacity of the

file system and includes usable space and space that is reserved or in use by

snapshots

Primary Virtual Volume Statistics

Pre-Migration Virtual

Volume Space Used

Details the virtual volumes size and the total space used before the

migration

Post-Migration

Virtual Volume

Space Used

Details the virtual volumes size and the total space used after the migration

Virtual Volume

Reclaimed

Displays the virtual volume space gained due to the migration

Secondary File System Statistics

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Consumed

Space taken up due to the migration

Item Description

Total File System

Consumed

Total space used in the file system by migration

Secondary Virtual Volume Statistics

Volume Space Used

Details the virtual volume size and the total space used before the migration

Post-Migration

Virtual Volume

Space Used

Details the virtual volume size and the total space used after the migration

Virtual Volume

Consumed

Displays the virtual volume space taken up by the migration

The following Actions are availablebull Click View Log to view a log file containing time duration and status

details of the migration A View Log link is available at both the top andbottom of the page

bull Click Download Migration Report to view a report about the completed datamigrations with details on the primary and secondary file systems andvirtual volumes including status space utilization before and after themigration the duration start and end time for the migrationsIncluded in the download are two other important reports one that lists allthe files that were migrated (listgz) and the other that lists all the filesthat were not migrated (failedgz)

Migration to HCP SystemsThe Hitachi NAS Platform supports migration of data to Hitachi ContentPlatform (HCP) for compliance purposes HDDS can be used to generate a listof files to be migrated to HCP This list of files called a migration request fileis placed into a migration control directory (specified as part of the migrationpath for the file system or virtual volume) The migration control directory isperiodically checked by the SMU When a migration request file is found amigration operation is started Upon completion a report file is created in themigration control directory

After a file has been migrated when a network client attempts to change theread-only attribute of a file that has been migrated to HCP that request fails

Note Migration to HCP requires an external volume link (XVL) license and aData Migrator license See the Server and Cluster Administration Guide forinformation on adding license keys

When Data Migrator migrates files to HCP systems the HTTP protocol is usedNote the following

bull The storage server only supports migration to HCP systems via HTTPwithout SSL security

bull The only supported HTTP targets are HCP systems (migration to otherremote servers uses the NFS protocol)

bull The storage server does not support the use of an HTTP proxy to accessthe remote HCP system

bull The storage server reports an HTTP user agent string constructed fromOEMCompany() OEMOS() and BUILD_VERSION_MAJOR_MINOR Theuser agent string from a Hitachi NAS Platform is reported as followsBlueArc BOS XY where X is the software major release build and Y isthe software minor release build For example the user agent string for aHitachi NAS Platform running software release 65 would read BlueArcBOS 65

When migrating files to HCP systems external migration paths must be setup before the migration control file is created and put into the migrationcontrol directory

Reclaimed Space

Reclaimed space is the difference in available space between the start andcompletion of the migration It is not a report of the amount of data migratedfrom the source file system to the target For this information refer toAmount Migrated

It is likely that the file system will be in use by network clients while themigration is in progress As a result the reclaimed space can be substantiallydifferent than the amount migrated The value can even be negative if fileswere added to the source

Once a data migration has completed copies of the files may be preservedon the source file system in snapshots For the space to be fully reclaimed allsnapshots on the source file system that reference the migrated files must bedeleted

Note When a reverse migration takes place space on the primary filesystem is consumed as files are moved from the secondary file system backto the primary file system Space in the secondary file system however isreclaimed

Reversing Migration

The server does include support for automatic policy-based reverse migrationof files as a part of the Data Migrator feature Aside from the policy-basedreverse migration there are two ways you can manually cause migrated filesto be restored to primary storagebull Reverse Migration Through the server CLI Individual files or whole

directory trees can be reverse-migrated through the CLI The files whichare included in the reverse migration can be identified by pattern or by lastaccess time For detailed information on this process run man reverse-migrate at the CLI

bull Reverse Migration From a Network Client A file can be restored froma network client by performing the following sequence of operations From a Windows or Unix client make a copy of the file (using a

temporary file name) on the primary storage This copy of the file willreside fully on primary storage

Delete the original file This will delete the link on primary storage andthe migrated data from secondary storage

Rename the copied file to its original name

iSCSI Logical Units

Mounted iSCSI LUs cannot be migrated regardless what has been defined inthe data migration policy Due to the types of applications typically hosted oniSCSI storage Hitachi Data Systems Support Center does not recommendmigrating iSCSI LUs to secondary storage However if this is desired it canbe accomplished by performing the followingbull Disconnect any iSCSI Initiators with connections to an LU

bull Unmount the iSCSI LU This can be done through the iSCSI Logical UnitProperties page

bull Run the data migration policy to migrate the LU

bull Re-mount the iSCSI LU

bull Reconnect the Initiator to the iSCSI Target

3Hitachi Data Systems Data Migrator to

Cloud

Important It is important to read through this chapter even if you haveexperience with Data Migrator and are new to Data Migrator to Cloud

Data Migrator to Cloud allows files hosted on the server to be moved ormigrated to cloud storage providing the benefits associated with both localand cloud storage This feature makes it seamless to move data betweendifferent tiers of the storage

A storage cloud is a pool of cost-effective elastic persistent storageaccessible through some variant of the HTTPS protocol that providesreasonable access performance for uploading and downloading archived filesCombining Cross-Volume Link (CVL-2) technology in HNAS with cloud storageprovides a near seamless archiving experience

A public cloud is provided by external entities hosting storage at their facilityand paid for on a per-use basis A private cloud is purchased and controlledby the end user Data Migrator to Cloud supports both and you can decidewhich model best suits your business needs In both cases you can accessthe cloud storage directly to view and download data and by accessing thefiles through the HNAS file system In both scenarios data is protected bothin-flight and at-rest regardless of where the physical storage is hosted

Data Migrator to Cloud is similar in look and feel to Data Migrator wherebyyou must configure paths rules policies and schedules for a file systemData Migrator to Cloud also introduces the concepts of an account wherebythe you enter credentials for the cloud target and a destination which is thelocation on the cloud in which the archived files are to be placed

A license is required to use the Data Migrator to Cloud for non-HCP targetsContact your Hitachi Data Systems representative to purchase a license

Configuring Data Migrator to Cloud

54 Hitachi Data Systems Data Migrator to CloudHitachi NAS Platform Data Migrator Administration Guide

Cloud data migration and replication considerations

Introduction to HCP no delete feature

HCP no delete functionality

Hitachi Data Systems Data Migrator to Cloud 55Hitachi NAS Platform Data Migrator Administration Guide

To use Data Migrator to Cloud you must define the followingbull An established network route See the Network Administration Guide for

detailsbull Cloud accountbull Cloud destinationbull Cloud path which defines the relationship between primary storage and to

the cloud destination to which data will be migratedbull Data migration rules which define the properties of files that will be

migratedbull Data migration policies which define rules to apply to specific data

migration paths based on the available free space on the source filesystem Free space is the amount of unused space allocated to the filesystem (before it automatically expands if automatic expansion is enabledfor the file system)

bull Data migration schedules which define when data migration policies arerun

bull Note The HNAS Virtual Secure Servers feature is not compatible withData Migrator to Cloud Although when per-EVS security is enabled anyEVS that is in the global or default EVS security context can still have theirfiles migrated

Note For late-breaking Data Migrator to Cloud information refer to theRelease Notes

Related references

bull Cloud providers on page 62

Checking and setting the status of aggregate ports for Data Migratorto Cloud

In most cases the default configuration of the ports should be sufficient andyou will not need to take any action To check the current data transfer modethat Cloud Gateway is running issue the following CLI command

migration-cloud-service-mode-showbull If this is the first time you are using Data Migrator to Cloud the system

will send data through the aggregate ports with zero copy for the local HCPcloud target

bull If you currently have Data Migrator to Cloud configured and running thedefault will continue to be management ports You have the option to

switch and send data through the aggregate ports If you decide to useaggregate ports you must first ensure that the route exists Once youconfirm that the route exists issue one of the following CLI commands migration-cloud-service-mode-set -a to transfer data through the

aggregate ports migration-cloud-service-mode-set -z to transfer data at a higher

outgoing performance rate through the aggregate ports when HCPtarget servers are local

Important If you are using VLANs you will need to switch back to themanagement ports by issuing the following command

migration-cloud-service-mode -m

For more information on the CLI commands see the Command LineReference

For information on link aggregations and adding aggregations see theNetwork Administration Guide

Ensuring that the route exists when using aggregate portsTo check the existence of a viable route from the EVS hosting the file systemto the cloud server you want to migrate files to

Procedure

1 Open a BALI command prompt window2 Enter ping -I ltsource addressgt lttarget namegt

where ltsource addressgt is one of the IP addresses on the EVSassociated with the file system and lttarget namegt is the HCPnamespace or cloud provider address

3 The verification process is complete when HNAS successfully receivesresponses to the ping messages from the target The following is anexample of a successful ping to check cloud server reachability from anEVS with the response of 0 packet lossmercury15$ ping -I 1921684322 ns01tenant01hcp01usdevbluearccomns01tenant01hcp01usdevbluearccom (10233458) 64 bytes from 10233458 icmp_seq=0 time=1 ms64 bytes from 10233458 icmp_seq=1 time lt1 ms64 bytes from 10233458 icmp_seq=2 time lt1 ms64 bytes from 10233458 icmp_seq=3 time lt1 ms--4 packets transmitted 4 packets received 0 packet lossround-trip minavgmax = 001 msmercury15$

4 If the route does not exist refer to the Network Administration Guide

Related concepts

bull Checking and setting the status of aggregate ports for Data Migrator toCloud on page 56

Ensuring the route exists when using management ports

To check the existence of a viable route from the EVS hosting the file systemto the cloud server you want to migrate files to

Procedure

1 Open a Linux command prompt2 Enter ping lttarget namegt

where lttarget namegt is the HCP namespace or cloud provider address3 If the route does not exist refer to the Network Administration Guide

Data Migrator to Cloud Configurations

Three example aggregate port configurations are presented in this sectionbull Target on the Internet with dedicated aggregate portsbull Target on the Internet with shared aggregate portsbull Data Migrator to Cloud with aggregate support with the target on the LAN

For all targets the server must be able to resolve the hostname using one ofthe management ports Because the target is on the Internet at least one ofthe configured DNS servers must be connected to the Internet

Target on the Internet with dedicated aggregate ports

The server must be able to resolve the hostname using one of themanagement ports Because the target is on the Internet at least one of theconfigured DNS servers must be connected to the Internet

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

5 agg_3

6 agg_4

Target on the Internet with shared aggregate ports

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

5 agg_3

6 agg_4

Data Migrator to Cloud with aggregate support with target on LAN

For this configurationbull The server must be able to resolve the host name on the targetbull Must be able to reach HCP using one of the HNAS management portsbull HCP maintains its own name serverbull The name server with the delegations to the zones configured on the HCP

must be accessible using one of the HNAS management ports

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

About cloud accounts and destinationsTo use Data Migrator to Cloud you must first configure at least one accountthat contains the following informationbull The cloud provider currently either Hitachi Content Platform (HCP) Hitachi

Cloud Services Amazon S3 or Microsoft Azurebull The credentials of a user with readwrite permissions to the targetbull The fully qualified domain name of the HCP namespace or the Hitachi

Cloud Services namespacebull A destination which is a location on the cloud where migrated files will be

stored This destination must exist before using the Data Migrator toCloud The configuration of the destination will fail if the specificdestination cannot be validated

Multiple accounts are supported Also note that multiple file systemmigration policies can use the same account

Related tasks

bull Establishing a Microsoft Azure cloud account on page 63bull Establishing credentials for Amazon S3 on page 62

Cloud providers

Data Migrator to Cloud supports multiple cloud providers The table belowlists each cloud provider and the required information you will need whenadding a cloud account and destination

Provider Server Name User Credentials Server Credentials References

HCP Fully qualified

domain name of

the HCP

namespace for the

account

credentials

User name of the

Data Access Account

The password of the

Data Access Account

with readwrite

permission to the

user account

Hitachi

Cloud

Services

Fully qualified

domain name of

the Hitachi Cloud

Services

namespace for the

account

credentials

User name of the

Data Access Account

The password of the

Data Access Account

with readwrite

permission to the

user account

Amazon

S3

Atuto-populates

with aws-

amazoncom

An IAM account Security Credential

Key

https

consoleawsamazon

comiam

Microsoft

Azure

Auto-populates

with

azuremicrosoftco

m

Name of storage

account

Primary or

Secondary Access

Key

https

azuremicrosoftcom

Establishing credentials for Amazon S3Before adding an Amazon S3 account you must create an Identify andAccess Management (IAM) account and add an access and a secret key Youwill need to provide this information when adding an Amazon cloud accountand destination

Procedure

1 Go to httpsconsoleawsamazoncomiam and log in with your username and password Refer to http docsawsamazoncomIAMlatestUserGuideUsing_SettingUpUserhtmlUsing_CreateUser_consolehttpsconsoleawsamazoncomiam for more information

2 When creating a user enable the Generate an access key for eachuser (this is enabled by default) check box and then click Create togenerate the access and secret keys Refer to httpdocsawsamazoncomIAMlatestUserGuide ManagingCredentialshtmlfor more information

3 Click Download Credentials and then save the access keys to yourlocal machine You will need this information when you create a cloudaccount

4 Click Close to exit5 Highlight and select the newly added IAM user account to open the users

page6 Click Attach User Policy and select Amazon S3 Full Access (you may

have to scroll down the page)7 Click Apply Policy8 When you create an Amazon cloud account provide the access and

secret keys just created

Establishing a Microsoft Azure cloud accountBefore adding an Microsoft Azure account you must create a storage accountand add Primary or Secondary Access Keys You will need to provide thisinformation when adding a Microsoft Azure cloud account and destination

Procedure

1 Go to httpsazuremicrosoftcom and click the Portal link located atthe upper right of the page

2 Log in with your user name and password3 To create new storage account click New located at the bottom left

corner4 Select Dataservices gt Storage gt Quick Create 5 Enter the URL and click locationaffinity group and replication6 Click Create Storage Account7 Select the storage account and click Manage Access Keys to obtain the

Primary Access Key and Secondary Access Key8 When you create an Microsoft Azure cloud account provide the storage

account and primary access or secondary access keys

Adding a cloud account

Procedure

1 Navigate to Home gt Storage Management gt Data Migration CloudAccounts to display the Cloud Accounts and Destination page

2 Under the Cloud Accounts section of the page click add to display theAdd Cloud Account page

Cloud Account Name The name of the cloud account

Provider This field identifies the cloud provider and the interpretation ofremaining fields in the account definition The options includebull Hitachi Content Platformbull Hitachi Cloud Servicesbull Amazon S3bull Microsoft Azurebull Test Provider

Test Provider is an option that allows you to determine the outcome ofthe migration operation without actually moving data

Server Name bull For Amazon S3 the server name is awsamazoncom and isautomatically inserted

bull For Microsoft Azure the server name is azuremicrosoftcom andis automatically inserted

bull For Hitachi Content Platform and Hitachi Cloud Services theserver name is the fully qualified domain name of the HCPnamespace or HCS namespace for the account credentialsprovided

User Credential bull For Amazon S3 you must have an Identify and AccessManagement (IAM) account

bull For Microsoft Azure you must have an Azure storage accountbull For Hitachi Content Platform and Hitachi Cloud Services this is the

user name of a Data Access Account

Secret Credential bull For Amazon S3 this is the Secret Access Key as described in theUser Credential field

bull For Microsoft Azure this is the primary or secondary keybull For Hitachi Content Platform and Hitachi Cloud Services this is the

password of the Data Access Account that must have the readwrite permission to the user account

3 Enter the details of the account4 Click OK to save the account details

Related tasks

Related references

Adding a cloud destinationA cloud destination associates a namespace directory for HCP or HitachiCloud Services a bucket for Amazon S3 or a container for Microsoft Azurethat is tied to a cloud account

Procedure

2 Under the Cloud Destinations section of the page click add to displaythe Add Cloud Destination page

Cloud Destination

Name

The name of the migration destination location that is tied to a cloud

accountThe name cannot contain spaces or any of the following specialcharacters amprsquoltgt|

Cloud Account

Name

Select from the list of cloud accounts that have been added to the

system

Destination

Location

Files from the cloud are migrated to this location For the cloud provider

this is the bucketsubfolder-list (subfolder-list is optional but should

already exist) For HCP the destination location is either empty or a

folder path This is the location on the cloud to which files are migrated

Encrypted In

Transit

Determines if data is to be encrypted in transit You can change the

existing destination from http to https by manually checking the

Encrypted In Transit checkbox This option applies to HCP destinations

only By default the checkbox is disabled and you must enable the

checkbox in order for the encryption of data during transit to take effect

If the HCP destination is outside your companys firewall be sure to

encrypt in transit

Note The checkbox is disabled if the destinations referencedaccount is an HCP account All other cloud providers are alwaysencrypted in transit

Note Data is automatically encrypted at rest when it arrivesto the destination

Viewing cloud accounts and destinations

Procedure

1 Navigate to Home gt Storage Management gt Data Migration CloudAccounts to display the Cloud Accounts and Destinations page

The following tables describe the fields and columns in this page

ItemField for Cloud

AccountsDescription

Provider Hitachi Content Platform Hitachi Cloud Services Amazon S3

Microsoft Azure or Test Provider

Server Name bull For Hitachi Content Platform and Hitachi Cloud Servicesthe server name is the fully qualified domain name of theHCP namespace

bull For Amazon S3 the server name is awsamazoncombull For Microsoft Azure the server name is

azuremicrosoftcom

User Credential bull For Hitachi Content Platform and Hitachi Cloud Servicesthis is the user name of a Data Access Account

bull For Amazon S3 this is the Access Keybull For Microsoft Azure this is the name of the storage

account

details Displays the details of the selected cloud account settings

add Advances to the Add Cloud Account page where you can

create a new cloud account

ItemField for Cloud

AccountsDescription

remove Deletes one or more selected data migration cloud accounts

Policies and Schedules Click to view existing policies and schedules New policies and

schedules can be created here as well

Data Migration Rules Click to view existing data migration rules New rules can be

created here as well

Data Migration Paths Click to view existing data migration paths New paths can be

ItemField for Cloud

DestinationDescription

Destination Name The name of the cloud destination

Account Name One of the previously configured cloud accounts selectedfrom a list

Destination Location Files from the cloud are migrated to this location For the

cloud provider this is the bucketsubfolder-list For HCP the

destination location is either empty or a folder path This is

the location on the cloud to which files are migrated

Encrypted In Transit Displays Yes if Encrypted in Transmit is enabled for the cloud

destination and No if it not enabled

details Click to view the details of the cloud destination settings

add Advances to the Add Cloud Destination page where you canadd a new data migration cloud destination

remove Deletes the selected data migration cloud destination

Viewing Cloud Account Details

Procedure

1 Navigate to Home gt Storage Management gt Cloud Accounts andDestinations

2 In the Cloud Accounts section of the page select the account to view andthen click Details to open the Cloud Account Details page

Cloud Account

Name

The name of the cloud account

Provider Hitachi Content Platform Amazon S3 or Test Provider

Server Name The name of the serverbull For Hitachi Content Platform and Hitachi Cloud Services the server

name is the URI of the name spacebull For Amazon S3 the server name is awsamazoncombull For Microsoft Azure the server name is azuremicrosoftcom

User Credential For Hitachi Content Platform and Hitachi Cloud Services this is the user

name of a Data Access Account For Amazon S3 this is the access key and

for Microsoft Azure this is the primary key

Secret

Credential

The secret credential shown with asterisks

Viewing Cloud Destination Details

Procedure

1 Navigate to Home gt Storage Management gt Cloud Accounts andDestinations gt Cloud Destination Details

2 In the Cloud Destinations section of the page select the destinationname to view and then click Details to open the Cloud DestinationDetails page

Cloud

Destination

Name

The name of the cloud destination

Cloud Account

Name

One of the previously configured cloud accounts selected from a list

Destination

Location

The location on the cloud to which files will be migrated Files from the

cloud are migrated to this location For the cloud provider this is the

bucketsubfolder-list (subfolder-list is optional) For HCP and Hitachi Cloud

Services the destination location is either empty or a folder path

Procedure

will be migrated

migrated

Adding a cloud path

Procedure

1 Navigate to the Home gt Storage Management gt Data MigrationPaths to display the Data Migration Path page

2 Click Add Cloud Path to display the Add Cloud Path page

Note A file system can only have one cloud target

Primary EVSFile

System

EVS and file system on primary storage This defines thesource for the data migration path Click change to selectanother EVS or file system

Secondary Available Cloud destination to which data will be migrated Select the

destination from the list

Note If you are creating a destination for testingpurposes you must first set up a test cloud accountusing Test Provider

Selected Displays the selected cloud destination

OK Click to save and exit

cancel Click to exit without saving changes

3 To change the currently selected EVS and file system click change4 Select the cloud destination to which data will be migrated and move the

selection to the Selected column You can only select one clouddestination

5 Click OK

In Use by

Policies

migrated

Policies and

Schedules

Data Migration

Cloud Accounts

Data Migration

Paths

Related references

Procedure

extension

bull dbfiledb migrates all files ending with the name dbfile andthe extension db

bull dbfile migrates all files with a name beginning with dbfileand having any extension

Access

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

minutes

Adding a data migration rule for the Data Migrator to CloudThis page can be used to name define add and modify Data Migration Rulesusing rule syntax Rules can be built with a series of INCLUDE and EXCLUDEstatements Each of these statements can contain a number of expressionsspecifying the type of files and the conditions under which they will bemigrated

For example

INCLUDE (ltFILENAME mp3gt AND ltFILE_SIZE_OVER 2GBgt)

Procedure

1 Navigate to Home gt Storage Management gt Data Migration Rulesto display the Data Migration Rules page and then click add

Type Click the appropriate option either WFSHNAS or Cloud

Case-sensitive

pattern checks

For Data Migrator to Cloud only note that files that are 4096 bytes orless will not be migrated

Related references

bull Creating specific and detailed rules on page 122

Procedure

1 Navigate to Home gt Storage Management gt Data Migration Rules2 Fill the check box next to the rule to modify and then click details

In Use by

Policies

Not in use

Rule

Definition

Procedure

ItemField for

PoliciesDescription

Primary File

System

Secondary File

System

Data MigrationRules

ItemField for

PoliciesDescription

Data MigrationPaths

as well

NDMPConfiguration

operation

Adding a cloud data migration policy

Procedure

Item Description

system for primary storage (the migration source)bull Virtual VolumeVirtual volumes do not apply to the Data Migrator to

Cloudbull Secondary Target Type Displays Cloud to represent the migration

type

Item Description

bull Secondary File System Displays the name of the file system onsecondary storage that will host the migrated data (the migrationtarget)

Reverse Migrate This option does not apply for cloud destinations

(To create

Pre-Conditions This section allows you to specify the rules (the criteria) that the files mustmatchmeet in order to be migrated or reverse migrated (reverse migrationis for Data Migrator only not Data Migrator to Cloud) by this policy

Available Cloud

Rules

the left arrow (lt)

percentage level for this condition)bull When other conditions are not met These conditions are defined in the

selected rule(s)

Selected Cloud

Rules

Displays the rules containing the criteriaconditions to be used to determine

if a file should be migrated The criteria in the rules are applied when the

threshold (the when condition specified in the Available Rules section) is

met

(To create rules

rules

When a migration policy is scheduled to run it evaluates the percentage ofavailable free space in the Policyrsquos primary storage Based on this analysisone rule may be triggered to define the data set subject to migrationMigrations of data from primary storage then occurs based on the statements

in the rule that was triggered Only a single rule will be engaged during anyparticular migration operation

Rule Statement

bull Rule 3 if free space is less than 15bull Rule 2 if free space is less than 50

bull Rule 1 if no other condition applies

For examplebull If free space is at 80 then Rule 1 will be used

bull If free space is at 40 then Rule 2 will be used

Note If the primary storage defined in the migration path is a virtualvolume free space will be based on the limit defined by the virtual volumequota If a virtual volume quota has not been defined then free spaceavailable will be based on the free space of the file system hosting the virtualvolume

Connection Errors

Procedure

Item Description

migration) policy

Item Description

Pre-Conditions

the left arrow (lt)

selected rule(s)

(To create rules

rules

Procedure

Data Migration

Policy

Date and Time

to Start

Procedure

Data Modify

Policy

Data Migration

Type

Item Description

Policy Policy name

select report

Item Description

Policies and

Schedules

Viewing details of a data migration cloud reportTo view data migration reports navigate to HomegtStorageManagementgtData Migration Status amp Reports and then click details todisplay the Data Migration Report page

Item Description

Report Summary

Item Description

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Reclaimed

snapshots

Total File System

Reclaimed

snapshots

Cloud data migration and replication considerationsThe following lists important data migration and replication considerations

Amazon and file-based replication

You may choose to deploy a replicated environment to protect primary andarchived data against site-wide failures When using HNAS file replication inconjunction with HCP replication special configuration is required The specialconfiguration depends on the scenario in which HNAS and HCP replication isarchitected

Note In order to take advantage of the new enhancements to HCP as atarget you will need to recall all the data and then re-setup your schedulespolicies and so forth using the new Data Migrator to Cloud

Consider the following three scenarios when using HNAS Data Migrator toCloud to HCP along with HNAS file replication and HCP replication

Scenario 1 Illustrates replicating file systems between HNAS clusters both of which point to asingle HCP system presumably hosted elsewhere however it is possible that theprimary HNAS system and HCP system are in the same location

Caution In this scenario both HNAS clustersentities map to the sameHCP system With HNAS file replication it is possible to access thesecondary file system(s) at any time It is strongly recommended to keepthe destination file system syslocked to avoid unintentional deletion of dataon the HCP system

Scenario 2 Illustrates replicating file systems between HNAS clusters where each cluster pointsto a local HCP system The HCP systems replicate migrated data and also perform aDNS failover so that the secondary HCP maintains the same name resolution as theprimary system

Note In this scenario HCP uses a DNS failover capability Due to theway the HCP failover functionality operations the secondary HNAS will alsopoint to the primary HCP With HNAS file replication it is possible to accessthe secondary file system(s) at any time It is strongly recommended tokeep the destination file system syslocked to avoid unintentional deletion ofdata on the HCP system

Scenario 3 Illustrates replicating file systems between HNAS clusters where each cluster pointsto a local HCP system The HCP systems replicate migrated data and maintain theirown unique name resolution

Scenario 3

For scenario 3 the cloud account must be configured as follows1 Create a dummy namespace on the secondary HCP system with the

same namespace and tenant name as the primary system The HCPsystem and the domain will then be different

2 Create a namespace data access user with read-write permissions on thedummy namespace

3 Configure a cloud account to this namespace which will confirm theread-write permissions

4 Remove the namespace and then configure replication in HCP to create areplica namespace on the secondary system Because a replica is read-only until a failover the read-write permissions check performed by thecloud account creation command will fail unless this dummy is created

Scenario 1 and 2

For scenarios 1 and 2 the cloud account creation command must specify thenamespace and data access account of the primary HCP system

All Scenarios

For all scenarios the cloud destination must be configured as follows1 The destination path and UUID must be the same at the secondary and

the primary because the stub contents will be replicated between clustersand the stub contains the path UUID of the destination If the path andUUID changes between clusters Data Migrator to Cloud cannot locatemigrated files after a failover

2 Identify the UUID of the cloud destination object in the primary filesystem This can be performed using the BOS CLI with the followingcommandbull migration-cloud-destination-list ltdestination-namegt

Destination ID is the UUID of this destination Path at destination is the path

3 On the secondary file system configure the cloud destination objectusing the BOS CLI (not the SMU) specifying the UUID with the -u optionFor examplebull migration-cloud-destination-create ltdestination_namegt -a

ltaccount_namegt -p ltpath at destinationgt -t yes -u ltUUID(obtained above)

bull The -p option should specify the path that was created at the primarybull The -u option is the UUID of the destination at the primary

Cloud Objects (paths rules and so forth)

All other cloud objects (Data Migration paths rules policies and schedules)are configured the same as in a non-replicated environmentbull Data migration paths are not copied by file-based replication As with Data

Migrator the XVLs will work correctly only if the cloud path exists on the

replication target The path must be created prior to the start ofreplication

bull Data Migrator policies and schedules are not copied with file-basedreplication You must manually re-create them on the replication target tosupport continuing migration to the cloud

bull For the cloud you must create the replication rule (navigate to Home gtData Protection gt File Replication Rules) using the values below instead ofthe default settings This ensures that replication copies the migration linksand allows access to the migrated data Make sure the replication rule iscorrectly specified in the replication policy Migrated File Remigration = Enabled External Migration Links = Re-create link

See the Replication and Disaster Recovery Administration Guide formore information

Finally to preserve bandwidth when replicating data between HNAS systemsinstruct HNAS file replication to only migrate the stubs and not the actualdata which will be replicated by HCP itself To do this perform the followingstepsbull When creating a file system replication rule set the External Migration

Links setting to re-create links On the BOS CLI run the followingcommands evssel ltevs number of the file systemgt migration-recreate-links-mode always-recreate-links

Multi-site HCP and file-based replicationbull The same considerations as described in the Amazon and file-based

replication apply to multi-site HCP and file-based replicationbull The replication of the migrated data HCP -gt HCP must be performed by

HCP It is recommended that the server name and credentials be the samefor both the source and the target If this is not possible it can be done atthe cloud account and destination level

The path as replicated will point to the original cloud destination and can beredefined if a different destination is desired Data migration to the cloud willnot begin until after disaster recovery occurs

Caution If both the source and destination point to the same HCP thedestination file system should be syslocked to prevent unintentional deletionof data

Object-based replicationbull Move cloud accounts destinations and rules to the replication target using

Clone Server Settings From the SMU navigate to Home gt Server Settingsgt Clone Server Settings See the Server and Cluster Administration Guidefor more information

bull Object-based replication does not currently support copying XVLs and re-inflates them by copying back the data from the migration target and thentransferring everything to the replication target Therefore care needs tobe taken that the replication target has sufficient space to contain both theun-migrated and migrated data

Note If the environment xvl-auth-recall-on-read is set to true anObject Replication will trigger a recall of migrated files on the source filesystem

bull Cloud policies schedules and paths are copied by object-based replicationas part of the file system Therefore after replication it is possible to re-migrate data back to the cloud

Conclusion

Other configurations may be possible If your environment differs from thescenarios described above contact your Hitachi Data Systems representativeor your Global Solutions and Services representative

Introduction to HCP no delete featureThe HCP no delete feature adds an extra level of data protection bydelaying deletion of archived data on HCP even if the primary XVL is deletedIn HNAS version 121 and higher the HCP no delete feature sets a retentionon the object for a user-defined interval in the future after which thedisposition service will eventually delete it

If an XVL is accidently deleted that represents a file that has been uploadedto HCP by Data Migrator to Cloud and no instance of the XVL exists in anHNAS file system snapshot HCP retains the object in its namespace for auser-defined period of time rather than issuing the purge If the accidentaldeletion is recognized in time the file can be retrieved manually from HCPback to the HNAS file system The decision whether to purge or retain a fileupon deletion of the XVL depends on the presence of a retention class in theHCP namespace After the retention period expires the HCP dispositionservice will automatically clean up these files from the namespace

Create a retention class on HCP for the target namespace HNAS sets theretention to the specified offset instead of deleting the object

Note This is not the default retention setting Default retention settingdeletes the object after a certain interval The HCP no delete feature sets aretention value on HNAS in the place of deleting the object

When the retention class is created and an XVL is deleted on HNAS (or lastsnapshot ages out) Data Migrator to Cloud will set the retention value on theobject on HCP You have that period to retrieve file from HCP if deletion wasaccidental The next figure gives an example of the retention timeframe

The HCP Disposition service periodically runs to delete files for which theretention period has expired so that they do not remain permanently on HCP

The HCP log will show disposition running and how many files it purged

4Overview of Hitachi NAS Universal

MigratorThe Hitachi NAS Universal Migrator allows data to be migrated from filesystems on pre-existing third-party NAS systems to HNAS systems Clientscan continue to access and use the data while the migration is in progressThis means that data stored on a third-party NAS system is immediatelyavailable for access via an HNAS system File systems from the third-partyNAS system can be actively used with HNAS as the frontend while the datamigration is in progress The Universal Migrator provides fast migration oflarge amounts of data while also allowing the use of the data duringmigration with minimal down time (compared to previous types of NASmigration)

It does this in two stages or phases The first virtualization stage discoversdata on the LNAS source and creates objects on the HNAS file system Thesecond migration stage copies the user data from the original file system sothat at the end all data is wholly contained on the HNAS file system At thatpoint the original NAS can be disconnected

Overview of Universal Migrator Capacity Based (UMC) license

Universal Migrator Capacity License considerations

Universal Migrator Capacity event notification

Hitachi NAS Universal Migrator Terms

Pre-migration considerations for Hitachi NAS Universal Migrator

Setting up LNAS and HNAS for virtualization

Troubleshooting Hitachi NAS Universal Migrator

Hitachi NAS Universal Migrator Console Commands

100 Overview of Hitachi NAS Universal MigratorHitachi NAS Platform Data Migrator Administration Guide

Overview of Universal Migrator Capacity Based (UMC)license

Before you can use Universal Migrator the Universal Migrator Capacity (UCM)license must be installed If you do not have a license key contact yourHitachi Data Systems representative

The Universal Migrator Capacity licensebull Is based on total capacity in TBs for all virtualized file systems across the

clusterbull Is fixed at the discovery phase of each associationbull Periodically checks the total licensed capacity against the recorded size of

all the virtualized associations Once the initial virtualization ofassociations has completed the only reason for a change in the actuallicensable capacity would be The addition of new associations (increase)

The removal of existing associations (decrease) The conversion of a virtualized association to a migration association

(decrease)

Universal Migrator Capacity License considerationsbull License capacity is based on total capacity in TBs for all virtualized file

systems across the clusterbull For license purposes the capacity of each association is fixed at the

discovery phasebull If the limit is reached or exceeded warning messages will be generated

periodically and further associations will be blockedbull The following command lists each virtualization path along with the

number of bytes that path has virtualized The paths are grouped by filesystem Virtualization paths that are in migration mode will report avirtualization usage of 0 virtualization-license-report

Universal Migrator Capacity event notificationYou will receive an event notification when virtualization exceeds thefollowing thresholdsbull 9220 is an informational event notification when virtualization exceeds 80

percent of the license allowancebull 9221 is a warning event notification when virtualization exceeds 95

percent of the license allowance

Overview of Hitachi NAS Universal Migrator 101Hitachi NAS Platform Data Migrator Administration Guide

bull 9222 is a severe event notification when virtualization exceeds 100percent of the license allowance

Hitachi NAS Universal Migrator TermsRefer to the following list of terms used for the Hitachi NAS UniversalMigratorbull Association ndash The configured connection between a mount point on the

LNAS and a directory in a file system on the HNAS An association is alsoreferred to as a virtualization path

bull Excluded directories ndash The user-defined list of directories that will not becreated on the virtualized HNAS file system

bull HNAS ndash The HDS NAS system that will hold the data after migrationbull IngestedFile ndash An object (directory or file) in the HNAS file system that is

in the process of being virtualized or migrated As such it contains extrametadata (compared to a regular filedirectory) but incomplete or absentuser data In some ways (principally user data readwrite access) anIngestedFile can be thought of as behaving similarly to an XVL The extrametadata is necessary for two reasons1 To keep track of the current virtualizationmigration state of the file2 To maintain a link to the LNAS version of the file

bull LNAS ndash The pre-existing legacy NAS system that holds the data to bemigrated

bull Migration ndash The process of bringing user data for an object from the LNASto the HNAS

bull Regular filedirectory ndash The normal type of object (a file or directory) inthe HNAS WFS file system

bull Virtualization ndash The process of discovering an object on the LNAS andcreating an IngestedFile to represent the LNAS object in the HNAS filesystem

bull XVL ndash External cross volume link

Pre-migration considerations for Hitachi NAS UniversalMigrator

This section describes the pre-migration considerations for Hitachi NASUniversal Migrator

Number and layout associationsThe HNAS Universal Migrator is designed to deal with multiple associationsper HNAS file system concurrently however due to fundamental file systemlimitations the simplest management is attained by configuring only oneassociation per HNAS file system mapped to a directory in the root of the filesystem

NFS export on the LNAS used by HNASThe export from the LNAS should have the following options set rw syncno_subtree_check no_root_squash These options allow the HNAS to fullycontrol the data and metadata of the files and directories The export mustalso be configured to only allow access to the HNAS as if other clients areable to access the data with rw and no_root_squash then the HNASs viewof the data will not be consistent and it will lose track of what has beenvirtualized or migrated This could result in data loss

Note If you are restricting the LNAS access on a per-IP basis on the exportinclude all IP addresses that an EVS can utilize

The export should only contain real (not virtual) file systems Examples ofvirtual file systems are directories such as dev or proc on a Linux serveror snapshot on a NAS device It may be difficult or impossible toexclude snapshot or similar via the LNAS configuration In this case thedirectory should be excluded at the HNAS using the virtualization-path-excluded-directory- commands The HNAS file system uses its storageresources in different ways to the LNAS therefore you cannot depend on thespace being used being identical on each Furthermore during the process ofvirtualization and migration the HNAS file system needs to use extra storagespace to track the state of the processing

The following arrangements on the LNAS should be avoided as they will leadto unpredictable behavior1 Nesting or overlapping exports on the LNAS used for associations2 Hard links across multiple LNAS exports

Exportshares from HNASIt is recommended not to set no_root_squash in NFS exports in HNAS Thisprevents accidental modification of the file system objects that track thestate of the association

Backup and replication policies disaster recoveryThis section describes backup and replication policies and disaster recovery

Virtualization

During virtualization the LNAS is the canonical store of the data To ensurethat there is no loss of data if the live file system is damaged it is necessaryfor backupsreplicationssnapshots to be configured on the LNAS Systemadministrators should ensure that they have sufficient backupssnapshots ofthe LNAS data set before connecting the HNAS

While it is not necessary to have backups or replications configured for theHNAS during virtualization (because they would not contain any data thatwas not recoverable through the LNAS backup) it is recommended toconfigure these when the association is created This reduces the risk offorgetting to start (or not knowing when to start) them when migrationbegins It also allows time to be sure that everything is working correctlyIncremental backupsreplication schedules started in the virtualization phasewill pick up data added during the migration phase When replicating duringthe virtualization phase a message will appear in the replication log statingthat ingested files are excluded from this operation This is normal

In the event that recovery from a backup is required during the virtualizationphase the simplest course of action is listed below1 Prevent client access2 Delete the association then remove all of the filesdirectories it created

from HNAS If the association was in the root of an HNAS file system itis recommended that you format the file system after deleting theassociation Use virtualization-delete-path --force command

3 Recover the LNAS from backup4 Recreate the association5 Start the virtualization6 Allow client access

Migration

During migration some data is on HNAS only while other data is on theLNAS only This makes backupsreplications and subsequent recovery morecomplicated and depends on the replicationbackup mechanism that is used

Ideally the replicationbackup of data on the HNAS and LNAS would besynchronized such that the data contained in the pair of backups isguaranteed to be consistent A consistent set could be guaranteed by thefollowing method

1 Prevent client access to the data2 Pause the migration by issuing the virtualization-path-control --

pause command3 Wait for activity to stop by issuing the virtualization-path-list

command and wait until the counts displayed in the list stop changing4 Take snapshots of the LNAS and HNAS and start the backupreplications

of these snapshots5 Allow client access

This method can however be undesirable because you must prevent clientaccess A more acceptable alternative is to have time synchronized snapshotsof the HNAS and LNAS to use for the replicationbackups This runs the riskof having inconsistencies between the LNAS and HNAS You could mitigate

this by pausing the background processes andor ensuring the backups aredone at a quiet time for client access

HNAS NDMP file replication and tape backups

Because object-based backup is incompatible with virtualization file basedreplication must be used The recovery of data from the HNAS backupfollowing damage to the live HNAS file system has to encompass a manualmerge of the LNAS and HNAS data This is necessary because although theIngestedFiles contained in the backup are preserved the associatedmetadata is lost because it does not form part of the NDMP backup Theresult is that although the user data of migrated files and the directorystructure that contained them will recover intact the connection of thisdirectory structure to the LNAS is not easily remade

The sequence to recover if NDMP replications or backups are used is asfollows

Procedure

1 Prevent client access2 Delete the association (if it has not been lost in the file system damage)3 Recover HNAS data to a location other than that which will be used for

the association4 If necessary recover LNAS data5 Recreate the association and allow virtualization to complete6 There are now two sets of files those recovered from the LNAS and

virtualized and those that were previously migrated and have beenrecovered to a separate location Depending on the volumetype of filesthat are in the latter set and how many renamesmoves havehappened you can do either of the followinga Examine the files manually and copy the migrated files into the

virtualized directory structure file by file depending on some case-specific judgment

b Use an automated method (rsyncrobocopy) to move the migratedfiles into the virtualized directory structure

7 Allow client access

Setting up LNAS and HNAS for virtualizationBefore using the Hitachi NAS Universal Migrator you must prepare thesystems by associating the HNAS to the LNAS The following steps describethis process Note that your preparation must use the device names and IPaddresses of your actual system

Assuming a legacy NAS device with hostname LNAS at IP address19216811 exporting a directory existing_data_dir as existing_export

using NFSv3 The LNAS is configured such that a sub directory snapshotexists in the root of existing_data_dir to allow browsing of snapshot data

Procedure

1 Create a file system lthnasfsgt using storage appropriate to contain thedata set to be migrated from the LNAS

2 Create NFS exports to the file system and any other HNAS configurationas necessary The directory on the HNAS file system that will be the rootof the association must be emptyIf you want to create exports within the root of the association uncheckthe Create path if does not exist checkbox on the SMU If you use theCLI use the nfs-export add command with the -i and -d(DONTCREATE) options for example nfs-export add -i -dsource_rootdata1 FS1 source_rootdata1 This will ensure the rootof the association remains empty until the virtualization starts

3 Add a new IP address to the LNAS which the HNAS will use for themigration (assuming the LNASs existing IP address will move to theHNAS when it is introduced into the environment)

4 Create the association ltassoc1gt at the HNAS console using thefollowing commands

virtualization-path-create -t lthnasfsgt -n ltassoc1gt -s nfslnasexisting_export

This can be modified if necessary using the following command

virtualization-path-modify

Note This command cannot be used after issuing virtualization-path-control -t lthnasfsgt -n ltassoc1gt --start

When the association has been created virtualization-path-list willshow Seen Dirs as 1 which is the root of the LNAS export

5 Add the snapshot directory to the list of excluded directories for theassociation

virtualization-path-excluded-directory-add -t lthnasfsgt -nltassoc1gt -d snapshot

Again this can be changed (virtualization-path-excluded-directory-list virtualization-path-excluded-directory-delete)up to the point that virtualization-path-control -t hnasfs -nassoc1 --start is used

6 Prevent any further client access to the LNAS by renaming or otherwisechanging the export Ensure that existing export NFSv3 export isconfigured on the LNAS in such a way as to meet the suggested best

practices At this point all other methods for clients to directly connect tothe LNAS should be disabled (for example CIFS shares)

7 If necessary transfer IP addresses from the LNAS to the HNAS (apartfrom the one created in step 4)

Starting virtualizationWhen starting virtualization you have two options You canbull Stop at the end of the virtualization phase and do not migrate any databull Automatically start migrating data once virtualization is complete

Procedure

1 Start the virtualizationa If you want to stop at the end of the virtualization phase and not

automatically migrate any data use the following commandvirtualization-path-control -t hnasfs -n assoc1 --start

Wait for the virtualization to complete This has the benefit that atany time the HNAS can be removed and you can revert back to usingthe LNAS without having to reconstruct the data The disadvantage ofthis is that the file system performance (seen by clients) will besignificantly degraded while in virtualization mode

b To start the data migration use the command virtualization-path-control -t hnasfs -n assoc1 --migrate immediately afterusing virtualization-path-control -t hnasfs -n assoc1 --start The advantage is that the client access (for files) willautomatically transition out of the poorly performing virtualizationmode as soon as possible It should be noted however that until theassociation is deleted and all objects are converted into TitanFileobjects (that is identical to objects that were only ever created on theHNAS outside of an association) the performance will not match thatof a normal HNAS WFS file system This is because it is only at thispoint that the requests by clients against the objects can becompletely served in hardware This has the disadvantage that if youwish to revert back to using the LNAS on its own you would have tomanually recombine the data that is held on the HNAS with that onthe LNAS

2 Once the virtualization has been started it is possible for clients toaccess the data on the LNAS via the HNAS This would normally beachieved by creating NFS exports andor CIFS shares for hnasfs in sucha way as to make the data available at the same location the clients werepreviously accessing lnasexisting_data_export This also requireschanging the configuration that is external to the HNAS for exampleDNS records andor client mount points

3 Monitor progress of the virtualizationmigration

4 Use virtualization-path-list -t hnasfs to display information aboutthe association including the counts of objects in various states

5 Events related to the association are raised in the event log Forexample

Information The virtualization path to filesystem hnasfsassociation name assoc1 from URI nfslnasexisting_data_export has been createdInformation The status of the virtualization path tofilesystem hnasfs association name assoc1 has beenmodified Virtualization has startedInformation The virtualization phase of filesystem hnasfsassociation name assoc1 completedInformation The status of the virtualization path tofilesystem hnasfs association name assoc1 has beenmodified Migration has startedInformation The migration phase of filesystem hnasfsassociation name assoc1 completedInformation The virtualization path to filesystem hnasfsassociation name assoc1 has been deleted

6 If you chose not to automatically proceed with virtualization you canissue virtualization-path-control -t hnasfs -n assoc1 --migrateat any time either before or after virtualization has completed Thisprevents any further client access to LNAS You must first ensure thatexisting_export NFSv3 export is correctly configured on the LNAS

7 Once migration has completed you need to delete the associationvirtualization-path-delete -t hnasfs -n assoc1

Monitoring the associationThe virtualization-path-list command can be used to display the stateof associations This includes a count of the file system objects in theassociation that are in various states While this provides a good overview ofthe progress of the association it may occasionally be unclear especiallywhen the association has been paused and restarted or when connection tothe LNAS has momentarily been lost and the HNAS is automaticallyrecovering Events are recorded in the event log when associations arecreated or deleted and when the virtualization and migration phasescomplete

Incompatible featuresIt is not possible to successfully object replicate a file system containingassociations

Performance LimitationsOnce migration is complete the performance when accessing data in thetarget file-system is that of a normal HNAS file system

During the virtualization phase the performance is governed by a number offactors including the capability of the LNAS and the network connection toit In addition the HNAS has to track the state of the objects in theassociation and send all modifying and IO operations to the LNAS The resultof this is that performance compared to a normal HNAS file system issignificantly degraded This is particularly the case when many (severalhundred) parallel client operations are made on the virtualized data at theexact same time If the desired use case of the feature is likely to include thistype of load it may be prudent to postpone widespread client access untilafter virtualization is complete and migration is well underway

Upgrade and downgrade considerationsAny associations should be removed using the virtualization-path-deletecommandbull If in virtualization mode the association can be deletedbull If part way through migration it is best to wait until migration completes

and then delete the association Data will be recovered onto the HNASrather than being in two different places

Troubleshooting Hitachi NAS Universal MigratorThis section provides common problems and solutions

Cannot create associationsCannot create associates as the remote server is inaccessible For example

mercury2n3(HNAS-4100)$ virtualization-path-create -t HNASfs -ndemo_assoc -s nfsmercuryc5LNASCreate virtualization path failed The remote server isinaccessibleAdditional information NFS Status RemoteTimeout[virtualization-path-create took 30 s]bull Try with IP address rather than hostname andor check the DNS settings

of your networkbull Use remote-nfs-exports on the HNAS console to show what exports are

available to the HNAS from the LNAS

Hitachi NAS Universal Migrator associations pausedWhen using virtualization-path-control on page 111 the pause completessuccessfully but the counts shown by virtualization-path-list on page 118are still seen to change

This is because it is necessary to complete processing the objects that arecurrently being operated on before stopping work If a directory is beingvirtualized that contains many entries this may take some 10s of seconds

Virtualization or migration does not complete

Procedure

1 Check virtualization-path-list CLI command on page 118 to see if thereare any failed files

Note The virtualization-path-files command could take some timeto complete

2 Check the event log The migration may not have completed due toinsufficient space on HNAS in which case it will pause and there will beno failed files

3 If step 1 shows failed files identify the problematic files with virtualization-path-files CLI command on page 116a Inspect the files on the LNAS to ensure that they are correct in that

file systemb Use remote-nfs-errors to gain insight as to why they may have failedc virtualization-path-files --list-failed may just show (that

is root)4 Fix problems if they are not obvious then the following strategies

should allow you to continuea For failed files during virtualization move the failing file out of the

exported directory on the LNAS Manually copy it over to the HNASb For failed files during migration remove the failing file from the HNAS

Manually copy the LNAS version of the file over to the HNAS5 Once you think that you have fixed the problems use virtualization-path-

files CLI command on page 116 to retry the failed filesIt is recommended that if it is only virtualization that has failed andmigration has not been started it may be simplest to delete thevirtualization path and start again - all data is still contained on the LNASat this point

Hitachi NAS Universal Migrator Console CommandsNote The contents below are automatically included from the online manpages which is why it is formatted in the manner displayed

virtualization-license-report CLI commandLists the amount of data currently virtualized by all virtualization paths

Options

--json|-j

Produce the output in JSON format

virtualization-path-control CLI commandOptions

-t -target ltfs labelgt

Target file system

-n --name ltassociation namegt

Name of association

-s --start

Indicates that virtualization of data from the virtualization source is to bestarted

-m --migrate

Indicates that migration of data from the virtualization source is to bestarted

-p --pause

Indicates that background processing of files from the virtualization source isto be paused

-r --resume

Indicates that background processing of files from the virtualization source isto be resumed

EXAMPLES

virtualization-path-control -t fs1 -n assoc1 --pause

Suspends background processing of files for the virtualization path forasociation assoc1 on file system fs1

virtualization-path-control -t fs1 -n assoc1 --migrate

Starts migration for the virtualization path for association assoc1 on filesystem fs1

APPLIES TO

EVS

virtualization-path-create CLI commandThis command creates a virtualization path association between a remoteNFS export source and a local file system vivol or directory target

To ensure data can be managed correctly between the Legacy NAS and theHNAS it is recommended that the mount on the Legacy NAS is exported withrw sync no_subtree_check no_root_squash It is also advised that due tono_root_squash the mount is available only to the HNAS

Options

--characterset ltlatin1|utf8|defaultgt

Character set of the legacy NAS source The default is utf8

--port ltportgt

NFS port of the legacy NAS source

--mountport ltmountportgt

Mount port of the legacy NAS source

-t --target ltfs labelgt

Target file system

-v --vivol ltvivolgt

Name of target Virtual Volume (optional)

-d --dir ltdirectorygt

Directory relative to the vivol or the filesystem in which to create theassociation (optional)

Logical name of the association

-s --source ltlegacy NAS path URIgt

Legacy NAS path URI

EXAMPLES

virtualization-path-create --characterset latin1 -t fs1 -n assoc1--force -s nfslegacyexamplecomexample_fs

Creates a virtualization path to file system fs1 from the legacy NAS pathnfslegacyexamplecomexample_fs using character set Latin-1 even if thepath is currently inaccessible

APPLIES TO

EVS

virtualization-path-delete CLI commandThis command deletes a virtualization path association between a remoteNAS NFS export source and a local file system or vivol target

Options

Target file system

-n --name ltassociationgt

Name of the association

--force

Force the source path to be deleted even if that would lead to files becominginaccessible

-c --confirm

Confirm that the deletion is to be carried out without any further prompt

In migration mode a check will be made to see if there are still files awaitingmigration If there are the command will fail unless the --force option hasbeen supplied

In virtualization mode the command will always fail unless the --force optionhas been supplied Note that not only will existing files become inaccessibleit will also not be possible to create new files in the local file system or vivoltarget

The --force option will cause the virtualization path to be removed even ifsome files must still be accessed on the legacy NAS and new files may fail tobe created which will lead to IO errors after the virtualization path has beendeleted

This operation is also irreversible If you delete the association you cannotrecover it and any virtualization progress will be lost

EXAMPLES

virtualization-path-delete -t fs1 -n assoc1

Delete the virtualization path for assoc1 on file system fs1

virtualization-path-delete -t Accounts -n HR --force

Delete the virtualization path for the association named HR on file systemAccounts even if some files must still be accessed on the legacy NAS whichwill lead to IO errors

APPLIES TO

EVS

virtualization-path-excluded-directory-add CLI commandThis command adds an excluded directory to the virtualization pathassociation between a remote NFS export source and a local file system vivolor directory target

This command can be applied while the association has created but thevirtualization has not been started

Options

Target file system

Target association name

Target directory relative to the root of the association to exclude fromvirtualization

EXAMPLES

virtualization-path-excluded-directory-add -t fs1 -n assoc1 -d snapshot

Add an excluded directory snapshot to the association assoc1 to file systemfs1

APPLIES TO

EVS

virtualization-path-excluded-directory-delete CLI commandThis command deletes an entry from the list of directories to be excludedfrom the virtualization path association between a remote NFS export sourceand a local file system vivol or directory target

This command can only be applied once the association has been created butthe virtualization has not yet started

Options

Target file system

EXAMPLES

virtualization-path-excluded-directory-delete -t fs1 -n assoc1 -d snapshot

Deletes the entry snapshot from the excluded directory list for theassociation assoc1 to file system fs1

APPLIES TO

EVS

virtualization-path-excluded-directory-list CLI commandThis command shows a list of the excluded directories registered to thevirtualization path association between a remote NFS export source and alocal file system vivol or directory target

Options

Target file system

EXAMPLES

virtualization-path-excluded-directory-list -t fs1 -n assoc1

Shows a list of excluded directories registered to the association assoc1 forfile system fs1

APPLIES TO

EVS

virtualization-path-files CLI commandThis command lists all files and directories that have failed to virtualizecorrectly It allows these to be retried as well Retries for individual files canalso be achieved by requesting them as normal through an ls command

Options

Target file system

Name of the association to check

-l --list-failed

List the files that the association has failed to correctly process

-r --retry

Trigger the association to try failed files again

-c --convert-file ltfilenamegt

Change the file name supplied to a file system file rather than it being avirtualized file If the file has not been migrated the contents will beundefined

EXAMPLES

virtualization-path-files -t Accounts -n assoc0 --list-failed

Lists the files that failed to virtualize on file system Accounts within assoc0

APPLIES TO

EVS

virtualization-path-journal-control CLI commandThis command manages journal of files deleted from remote server for avirtualization path association

Options

Target file system

-e --journal-enable

Enables a journal for a virtualization path association

-d --journal-disable

Disables a journal for a virtualization path association

-m --email-logs

Sends logs by email

-u --delete-logs

Deletes logs

-r --recipient ltemail-addressgt

Specifies an email address to sends logs

-s --start-date ltYYYY-MM-DDgt

First log date to send by email or to delete (optional) If not provideddefaults to first log file existing

-f --end-date ltYYYY-MM-DDgt

Last log date to send by email or to delete (optional) If not provideddefaults to current date

-c --confirm

Skips interactive confirmation for --delete-logs

EXAMPLES

virtualization-path-journal-control -t fs1 -n assoc1

Provides information about journal state

virtualization-path-journal-control -t fs1 -n assoc1 --journal-enable

Enables journal for the virtualization path for file system fs1

virtualization-path-journal-control -t fs1 -n assoc1 --email-logs--recipient usercompanycom --start-date 2012-09-01 --end-date2012-09-30

Sends log of all deleted files in September for the virtualization path for filesystem fs1

APPLIES TO

EVS

virtualization-path-journal-show CLI commandThis command displays a journal of files deleted from remote server for avirtualization path association

Options

Target file system

First log date to display (optional) If not provided defaults to first log fileexisting

Last log date to display (optional) If not provided defaults to current date

EXAMPLES

virtualization-path-journal-show -t fs1 -n assoc1 --start-date2012-09-01 --end-date 2012-09-30

Displays log of all deleted files in September for the virtualization path for filesystem fs1

APPLIES TO

EVS

virtualization-path-list CLI commandThis command lists all NAS virtualization path associations defined for thespecified file system or for all file systems if the -a or --all option is used

Options

Target file system

-a --all

All file systems

INFORMATION PROVIDED

Source URI Legacy NAS path URI

Association Logical name of the association

Mode Association mode (virtualize only virtualize and migrate paused)

Options Optional parameters to association (for example legacy NAScharacter set)

Status Runtime status of association

Seen Dirs Number of directories found by virtualization process

Processed Dirs Number of directories fully virtualized

Pending Dirs Number of directories pending virtualization (including failed)

Failed Dirs Number of directories which failed virtualization

Seen Files Number of files found by virtualization process

Processed Files Number of files fully migrated

Pending Files Number of files waiting to start or re-start actively migrating

Migrating Files Number of files actively migratingFailed Files Number of files which failed migration

EXAMPLES

virtualization-path-list -t Accounts

Lists the virtualization path on file system Accounts

virtualization-path-list --all

Lists the virtualization path for all file systems

APPLIES TO

EVS

virtualization-path-modify CLI commandThis command changes the source URI associated with a pre-existingvirtualization path that is mapped to a local file system vivol or directorytarget

This command will change the location that data is received from whenscanning for entries to virtualize After virtualization process has startedchanges by virtualization-path-modify command are no longer allowed Tochange the source in such case the virtualization path needs to be deletedand created again

Options

--port ltportgt

-t --target ltfs namegt

The name of the file system containing the association

The name of the association to be modified

-f --force

Force the source URI to be modified even if the new path is not currentlyaccessible

-s --source

Legacy NAS path URI

EXAMPLES

virtualization-path-modify -t fs1 -n assoc1 -s nfslegacyexamplecomexample_fs

Sets nfslegacyexamplecomexample_fs as the new path associated withthe association assoc1 on file system fs1

virtualization-path-modify -t fs1 -n assoc1 --force -s nfslegacyexamplecomexample_fs

Sets nfslegacyexamplecomexample_fs as the new path associated withthe association assoc1 on file system fs1 even if the path is not currentlyaccessible

APPLIES TO

EVS

virtualization-path-stats CLI commandThis command displays statistics associated with NAS virtualization pathsdetailing the amount and time taken by the migration since the statisticswere last reset or start-up whichever is the most recent

Options

Show migration statistics for the target file system

Further narrow statistics to the association

-a --all

Show migration statistics for all associations on the EVS

-w --work

Show work team statistics

-r --reset

Reset statistics

-g --graph

Show a graphical representation of the time taken by the migration

APPLIES TO

EVS

Control via SMU GUI

At the time of writing there is no GUI support for the feature

Formatting file systems

Caution Formatting a file system from the CLI that contains a virtualizationpath will prompt you to delete the virtualization path However if the SMU isused to format a file system that contains a virtualization path there will beno prompt Therefore it is important to remember to delete the virtualizationpath for a file system before formatting through the SMU

ACreating specific and detailed rules

Before building migration rules refer to the following information regardingsyntax keywords connectors conditionals and statement order Thefollowing example provides a three-step process for assembling simple yetspecific and detailed rules1 Start with a simple INCLUDE statement that is specific about what should

be migrated such asINCLUDE (ltPATH Tempgt AND ltFILENAME mp3gt)

2 Refine the INCLUDE statement by adding exceptions to the rule withrestrictive EXCLUDE statements Add these EXCLUDE statements abovethe INCLUDE such asEXCLUDE (ltFILE_SIZE_UNDER 2MBgt)EXCLUDE (ltACTIVE_WITHIN 14gt)

3 The rule should finally appear this wayEXCLUDE (ltFILE_SIZE_UNDER 2MBgt)EXCLUDE (ltACTIVE_WITHIN 14gt)INCLUDE (ltPATH Tempgt AND ltFILENAME mp3gt)

Click on a topic at the left for more information about a specific rule

Rules syntax

Keywords

Connectors

Conditionals

Statement order

122 Creating specific and detailed rulesHitachi NAS Platform Data Migrator Administration Guide

Rules syntaxData migration rules compare a series of INCLUDE and EXCLUDE statementseach qualified by expressions stating the criteria for data migration Thefollowing guidelines govern rule buildingbull At least one INCLUDE or EXCLUDE Each rule must contain at least one

INCLUDE or EXCLUDE statement Rules consisting only of EXCLUDEstatements imply that everything on primary storage should be migratedexcept what has been specifically excluded

Note If a rule contains only INCLUDE statements all items not specifiedby the INCLUDE statements are excluded

bull Wildcards The asterisk () can be used as a wildcard character to qualifyPATH and FILENAME values When used in a PATH value ldquordquo is only treated as a wildcard if it

appears at the end of a value for example ltPATH tmpgt In a FILENAME value a single ldquordquo can appear either at the beginning or

the end of the value Multiple instances of the wildcard character are not supported and

additional instances in a value definition will be treated as literalcharacters

bull Bracketed keywordvalue pairs Expressions identifying migrationcriteria should be enclosed in brackets All criteria contain a keyworddefining the condition for data migration followed by a single value of alist of values for example ltFILENAME docgt

bull Evaluation of statement sequence When using multiple INCLUDE orEXCLUDE statements they are evaluated using top-down ordering

bull Grouping criteria within statements Parentheses are used to groupthe criteria in INCLUDE and EXCLUDE statements for example INCLUDE(ltPATH Tempgt)

bull Number of INCLUDE or EXCLUDE statements per line When usingmultiple INCLUDE or EXCLUDE statements in a rule each INCLUDE orEXCLUDE statement must be placed on its own line (multiple INCLUDEandor EXCLUDE statements may not be put on the same line)

bull Separating multiple listed values When defining multiple values in aFILENAME list use a comma to separate values for example INCLUDE(ltFILENAME mp3wavwmvgt)

bull Characters requiring escaping the following characters need to beescaped with a backslash () when used as a part of PATH or FILENAMEvalues (backslash) gt (greater than) and (comma) for exampleINCLUDE (ltFILENAME abgt OR ltPATH tmpgtabgt)

Creating specific and detailed rules 123Hitachi NAS Platform Data Migrator Administration Guide

Note Backslashes used when specifying a domain and user name shouldnot be escaped (double backslashes are not required when specifyingdomain_nameuser_name)

bull Forward slash () reserved as a path separator The forward slash ()is used as a path separator as such it must not be used in a FILENAMElist

bull Evaluation of absent PATH If a PATH element is not specified in astatement the statement will apply to the entire file system or virtualvolume defined in the data migration path

bull Quotation mark usage Quotation marks (ldquo) are not allowed around aFILENAME or PATH list

KeywordsThe following table describes the keywords and their related values that canbe used to build rule statements Each keyword can be defined in the rulewith an INCLUDE or EXCLUDE statement to indicate how the keyword valuesare to be applied

Keyword Value(s)

FILENAME Names and types of files contained in the rule Separate multiple names bycommas FILENAME values may start or end with a ldquordquo wildcard characterto indicate all files startingfinishing with specific characters

Usage

FILENAME will often be used with an INCLUDE statement to ensure thatnon-essential files are migrated to secondary storage It can also be usedwith an EXCLUDE statement to prevent specific important data sets frombeing migrated

For example

ltFILENAME mp3txtfilename filenamegt

PATH Specifies literal paths to which a rule applies Values must be full pathsstarting with a forward slash () Separate multiple paths by commasPATH values may end with a ldquordquo wildcard character to indicate allsubdirectories under the specified pathUsage

When used in an INCLUDE statement PATH specifies directories tomigrate This is useful when migrating less-critical directories such as tempor home directories When used in an EXCLUDE statement directories canbe excluded from migration leaving all the files within on primary storage

For example

ltPATH temphomeotherdirgt

USERNAME Specifies user names to which a rule applies Values must be validWindows or UNIX user names Separate multiple names by commas

Keyword Value(s)

Usage

When used in an INCLUDE statement USERNAME specifies the user nameof file owners whose files are to be migrated This is useful when migratingfiles owned by a particular user When used in an EXCLUDE statementusers can be excluded from migration leaving all the files owned by thespecified user(s) on primary storage

Windows user names are specified in the form domainusername

Note Backslashes in user names should not be escaped (doublebackslashes are not required) For example

jjames mycosmithr mycowsmith

FILE_SIZE_OVER Identifies a subset of files in a rule with sizes crossing an upper thresholdThe threshold value is appended to the keyword and defined by thethreshold size in B KB MB or GB

Usage

This will likely be used with INCLUDE statements to ensure files of verylarge sizes are migrated to secondary storage

For example

ltFILE_SIZE_OVER 4GBgt

FILE_SIZE_UNDER Identifies a subset of files in a rule with sizes crossing a lower thresholdThe threshold value is appended to the keyword and is defined by thethreshold size in B KB MB or GB

Usage

This will usually be used in an EXCLUDE statement to ensure that verysmall files are not migrated en masse Migrating small files that take uplittle space provides minimal value in extending the efficiency of primarystorage

For example

ltFILE_SIZE_UNDER 10KBgt

OLDER_THAN Identifies files that were created more than a specified number of days inthe past (files older than x days) The value appended to the keyworddefines the minimum age (number of days) of a file before the rule isapplied to that file

Usage

Used primarily in INCLUDE statements to ensure that older files aremigrated

For example

ltOLDER_THAN 28gt

NEWER_THAN Identifies files that were created less than a specified number of days inthe past (files newer than x days) The value appended to the keyworddefines the maximum age (number of days) of a file before the rule isapplied to that file

Keyword Value(s)

Usage

Used primarily in EXCLUDE statements to ensure that newer files are notmigrated

For example

ltNEWER_THAN 14gt

INACTIVE_OVER Identifies files that have not been accessed within a specific number ofdays A filersquos last access time is updated whenever the file is read ormodified The value is appended to the keyword and defines the number ofdays of inactivity

Usage

Used primarily in INCLUDE statements to ensure that older less frequentlyused files are migrated

For example

ltINACTIVE_OVER 21gt

ACTIVE_WITHIN Identifies files accessed within a specific number of previous days A filersquoslast access time is updated whenever the file is read or modified The valueis appended to the keyword and defines the number of days within whichthe activity has occurred

Usage

Used primarily in EXCLUDE statements to prevent actively used files frombeing migrated

For example

ltACTIVE_WITHIN 30gt

UNCHANGED_OVER Identifies files not modified within a specific number of previous days Afilersquos modification time is updated whenever the filersquos contents have beenchanged The value is appended to the keyword and defines the number ofdays of inactivity

Usage

For example

ltUNCHANGED_OVER 14gt

CHANGED_SINCE Identifies files modified within a specific number of previous days A filersquoslast access time is updated whenever the filersquos contents have beenchanged The value is appended to the keyword and defines the number ofdays of inactivity

Usage

For example

ltCHANGED_SINCE 7gt

ConnectorsStatements can combine multiple criteria as followsbull AND indicates that both statements must be satisfied For example in the

statementINCLUDE (ltFILENAME mp3gt AND ltFILE_SIZE_OVER 5GBgt)both conditions must be true in order for the statement to be true

bull OR indicates that only one statement needs to be satisfied For examplefor the same statement replacing AND with ORINCLUDE (ltFILENAME mp3gt OR ltFILE_SIZE_OVER 5GBgt)only one condition needs to be true for the statement to be true

While AND requires both conditions to be true OR only requires that eithercondition to be true

ConditionalsThe following table shows a set of rules with explanations The syntax caneasily be broken down into cause and effect statements identified by IF andTHEN connectors

Rule Description

INCLUDE (ltFILENAME docgt) IF the file is a doc file THEN include it formigration

EXCLUDE (ltPATH mydirgt) IF the path is the mydir directory THEN excludeit from migration

INCLUDE (ltFILENAME prjgt ANDltFILE_SIZE_OVER 4GBgt)

IF the file is a prj file AND the prj file is over4 GB in size THEN include it for migration

INCLUDE (ltPATH unimportantgt) IF the path is the unimportant directory THENinclude it for migration

EXCLUDE (ltFILE_SIZE_OVER 100GBgt) INCLUDE(ltFILE_SIZE_OVER 12GBgt)

IF files are larger than 12 GB but smaller than100 GB in size THEN include them formigration

Statement orderStatement order is critical Statements are evaluated top-down starting withthe first statement defined Therefore as the following examples illustratebest practice usually specifies EXCLUDE statements at the top of the rule

Rule scenario A

INCLUDE (ltPATH Tempgt AND ltFILENAME mp3gt)EXCLUDE (ltACTIVE_WITHIN 14gt)EXCLUDE (ltFILE_SIZE_UNDER 2MBgt)

The above rule is interpreted asbull IF path name includes Temp AND file name is mp3 THEN MIGRATEbull IF file is active less than 14 days AND less than 2 MB in size THEN

EXCLUDE

In scenario A all the mp3 files under Temp will be migrated based on thefirst INCLUDE statement Statements 2 and 3 are disregarded since they areevaluated after the more inclusive INCLUDE statement that has alreadyadded what rules 2 and 3 are trying to exclude

Rule scenario B

If the same rules were ordered differently

EXCLUDE (ltFILE_SIZE_UNDER 2MBgt)EXCLUDE (ltACTIVE_WITHIN 14gt)INCLUDE (ltPATH Tempgt AND ltFILENAME mp3gt)

The above rule is interpreted asbull IF file is less than 2 MB in size OR active less than 14 days THEN

EXCLUDEbull IF path name includes Temp AND file name is mp3 THEN MIGRATE

In this scenario only mp3 files greater than 2 MB in size that have beeninactive for greater than 14 days will be migrated

BConfiguring management ports for Data

Migrator to CloudIt is recommended that you use the aggregate ports instead of themanagement ports The use of aggregate ports transfers data at a higheroutgoing performance rate However if you plan to use the managementports for cloud targets you must define the followingbull DNSbull Networking

Note The HNAS Virtual Secure Servers feature is not compatible with DataMigrator to Cloud

Before using Data Migrator to Cloud you must ensure that themanagements ports are properly configured

Data Migrator to Cloud connects to the cloud through one of the managementports on the HNAS system and not through the aggregate ports that are usedfor NFS or CIFS access Because of this you must configure the eth0 or eth1network interface card with an IP address netmask and gateway that isroutable to the cloud targetbull If the cloud target is Hitachi Content Platform a route must exist to the

namespace that will be configured as part of the cloud accountbull If the cloud target is Amazon S3 a route must exist to https

s3amazonawscom

In an HNAS clustered environment usually one network interface card isconfigured for the cluster interconnect (eth1) and the other (eth0) is notconfigured In general the cluster interconnect is a private network amongthe cluster nodes and it is expected that the cloud traffic will be sent througheth0 For example eth1 can be used for the cluster interconnect and eth0 forthe cluster node IP as illustrated in the graphic

130 Configuring management ports for Data Migrator to CloudHitachi NAS Platform Data Migrator Administration Guide

Hitachi Global Solutions and Services recommends the following networkconfiguration for cloud traffic

Figure B-1 Single node network configuration

Figure B-2 Clustered HNAS network configuration

The first figure displays a single HNAS node network configuration and thesecond a clustered HNAS network configuration Each HNAS node requirestwo IP addressesbull One cluster node IP address on eth0 and eth1bull One Admin EVS IP address on eth1

Configuring management ports for Data Migrator to Cloud 131Hitachi NAS Platform Data Migrator Administration Guide

This IP will failover between the nodes as needed so it is not importantwhich node it is configured on

The following tables show examples of an IP address configuration

Single Node

Interface IP

SMU eth0 172101011

HNAS Cluster Node IP eth0 172101013

HNAS Admin EVS IP eth0 172101015

Cluster

Interface IP

SMU eth0 172101011

HHNASAS Admin EVS IP eth0 172101015

HNAS 2 Cluster Node IP eth0 172101016

Note The SMU does not require redundant network connectivity All IPsconfigured on eth1 and eth0 of the HNAS node(s) should be on the samesubnet

To configure a cluster node IP addresses on a management port issue thefollowing commands on the HNAS CLI

ipaddr [-r] [-p ltportgt] [-I ltaddrgt -m ltmaskgt] [-c | --confirm]

For example to add the address 19216853116 to eth1 with netmask2552552480 issue the following CLI command

ipaddr -p eth1 -I 19216843116 -m 2552552480

HNAS requires DNS in order to resolve the cloud target To configure DNSthe HNAS CLI dnsserver command can be used

dnsserver add ltserver1gt ltserver2gt hellip

For example the following command assigns DNS servers 1921684510 and1921684511

dnsserver add 1921684510 1921684511

Make sure to configure a default route for the eth0 and eth1 interfaces Thiscan be done with the HNAS CLI route command

route add gateway -g ltaddrgt

For example the following command assigns default gateway 192168431

route add gateway -g 192168431

Note When the cloud target is HCP Global Solutions and Servicesrecommends the HCP and HNAS eth0 and eth1 interfaces reside on the samesubnet

These commands must be run once before configuring the cloud objects suchas account and destination and these settings are persistent across anyreboot of the HNAS system To modify or delete these settings consult theman pages for the ipaddr and route commands

Note Using the ipaddr and route commands will not modify otheraddresses and routes already configured on the management interfaces

Tip To verify your routing and DNS configuration the HNAS CLI ping andhost commands can used

Configuring management ports for Data Migrator to Cloud

Data Migrator to Cloud Environment Variables

Configuring management ports for Data Migrator to CloudIt is recommended that you use the aggregate ports instead of themanagement ports The use of aggregate ports transfers data at a higheroutgoing performance rate However if you plan to use the managementports for cloud targets you must define the followingbull DNSbull Networking

s3amazonawscom

Single Node

Interface IP

SMU eth0 172101011

Cluster

Interface IP

SMU eth0 172101011

ipaddr -p eth1 -I 19216843116 -m 2552552480

dnsserver add 1921684510 1921684511

These commands must be run once before configuring the cloud objects suchas account and destination and these settings are persistent across any

reboot of the HNAS system To modify or delete these settings consult theman pages for the ipaddr and route commands

Data Migrator to Cloud Environment VariablesData Migrator to Cloud provides two settings to control when migrated filesare recalled from a cloud target When using HCP as a cloud target the filesresiding on HCP cannot be modified and can only be deleted It is desirable tohave the ability to modify migrated files When enabled HNAS will recall thefile to the local HNAS file system when it is modified The file can then bemigrated back to HCP when the data migrator policy next runs and it meetsthe migration criteria defined in the data migrator policy

Currently HNAS may not be able to recall all files that are being modifiedthis may result in an error This is application dependent Applications knownto work are Microsoft Office applications To provide better support for recallon write HNAS has another variable xvl-auto-recall-on-read and whenenabled this setting will recall all files when read Because the file willalready reside locally on HNAS all modifications will occur successfully

Note These variables are global cluster-wide settings Global Solutions andServices recommends that these variables are not enabled when existingnon-cloud HCP configurations are in use with other file systems

Important When xvl-auto-recall-on-read is enabled replications willrecall all migrated files

To enable recall on write set the environment variable xvl-auto-recall-on-modify through the HNAS CLI to true

For example

set xvl-auto-recall-on-modify true

To enable recall on read set the environment variable xvl-auto-recall-on-read through the HNAS CLI to true

For example

set xvl-auto-recall-on-read true

Both of these variables take effect immediately

Hitachi NAS Platform Data Migrator Administration Guide

Hitachi Data Systems

Corporate Headquarters2845 Lafayette StreetSanta Clara California 95050-2639USAwwwhdscom

Regional Contact Information

Americas+1 408 970 1000infohdscom

Europe Middle East and Africa+44 (0) 1753 618000infoemeahdscom

Asia Pacific+852 3189 7900hdsmarketingapachdscom

MK-92HNAS005-07

Contents
Preface
- Contacting Hitachi Data Systems
- Related Documentation
- - Overview of Data Migrator and Data Migrator to Cloud
  - - Data migration paths
    - Types of migration targets
    - Cross volume links in Data Migrator
    - Cross volume link format considerations
    - Adding a license key
    - - Hitachi Data Systems Data Migrator
      - Configuring Data Migrator
        
        
        
        Configuring Data Migrator paths
        
        
        About external data migration paths
        
        
        Adding a data migration rule by template
        
        Adding a custom WFSHNAS data migration rule
        
        
        
        
        
        About the ndmp-management-ports-set command
        
        Migration schedules
        
        
        Viewing details of a data migration report
        
        
        Hitachi Data Systems Data Migrator to Cloud
        
        
        Checking and setting the status of aggregate ports for Data Migrator to Cloud
        
        Ensuring that the route exists when using aggregate ports
        
        
        About cloud accounts and destinations
        
        Cloud providers
        
        Establishing credentials for Amazon S3
        
        Establishing a Microsoft Azure cloud account
        
        
        Adding a cloud destination
        
        
        
        
        
        Adding a cloud path
        
        
        
        Adding a data migration rule for the Data Migrator to Cloud
        
        
        
        
        
        Migration schedules
        
        
        Modifying a schedule
        
        
        Viewing details of a data migration cloud report
        
        
        
        
        Overview of Hitachi NAS Universal Migrator
        
        
        
        
        
        
        Number and layout associations
        
        NFS export on the LNAS used by HNAS
        
        Exportshares from HNAS
        
        Backup and replication policies disaster recovery
        
        
        Starting virtualization
        
        Monitoring the association
        
        Incompatible features
        
        Performance Limitations
        
        Upgrade and downgrade considerations
        
        
        Cannot create associations
        
        Hitachi NAS Universal Migrator associations paused
        
        
        
        virtualization-license-report CLI command
        
        virtualization-path-control CLI command
        
        virtualization-path-create CLI command
        
        virtualization-path-delete CLI command
        
        virtualization-path-excluded-directory-add CLI command
        
        virtualization-path-excluded-directory-delete CLI command
        
        virtualization-path-excluded-directory-list CLI command
        
        virtualization-path-files CLI command
        
        virtualization-path-journal-control CLI command
        
        virtualization-path-journal-show CLI command
        
        virtualization-path-list CLI command
        
        virtualization-path-modify CLI command
        
        virtualization-path-stats CLI command
        
        Creating specific and detailed rules
        
        Rules syntax
        
        Keywords
        
        Connectors
        
        Conditionals
        
        Statement order

Page 2: Data Migrator Administration Guide

No part of this publication may be reproduced or transmitted in any form or by anymeans electronic or mechanical including photocopying and recording or stored in adatabase or retrieval system for any purpose without the express written permission ofHitachi Ltd

Hitachi Ltd reserves the right to make changes to this document at any time withoutnotice and assumes no responsibility for its use This document contains the mostcurrent information available at the time of publication When new or revised informationbecomes available this entire document will be updated and distributed to all registeredusers

Some of the features described in this document might not be currently available Referto the most recent product announcement for information about feature and productavailability or contact Hitachi Data Systems Corporation at httpsportalhdscom

Notice Hitachi Ltd products and services can be ordered only under the terms andconditions of the applicable Hitachi Data Systems Corporation agreements The use ofHitachi Ltd products is governed by the terms of your agreements with Hitachi DataSystems Corporation

Contents

Preface

bull

Procedure

2 Click add

Add a License Key

License Key File

Name

Procedure

will be migrated

migrated

for data migrations

Procedure

Primary EVSFile

System

secondary storage

In Use by

Policies

migrated

Policies and

Schedules

Data Migration

Cloud Accounts

Data Migration

Paths

Related references

Procedure

Access

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

minutes

Procedure

Case-sensitive

pattern checks

Procedure

In Use by

Policies

Not in use

Rule

Definition

Procedure

ItemField for

PoliciesDescription

Primary File

System

Secondary File

System

Data MigrationRules

ItemField for

PoliciesDescription

Data MigrationPaths

as well

NDMPConfiguration

operation

Procedure

Item Description

(To create

Available WFS

HNAS Rules

the left arrow (lt)

selected rule(s)

Selected WFS

HNAS Rules

(To create rules

rules

file system

CVL-1

CVL-2

Rule Statement

Connection Errors

Procedure

Item Description

migration) policy

Pre-Conditions

the left arrow (lt)

selected rule(s)

(To create rules

rules

Procedure

Data Migration

Policy

Date and Time

to Start

Procedure

Data Modify

Policy

Data Migration

Type

Item Description

Policy Policy name

select report

Item Description

Policies and

Schedules

Item Description

Report Summary

Item Description

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Reclaimed

snapshots

Total File System

Reclaimed

snapshots

Volume Space Used

migration

Post-Migration

Virtual Volume

Space Used

Virtual Volume

Reclaimed

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Consumed

Item Description

Total File System

Consumed

Volume Space Used

Post-Migration

Virtual Volume

Space Used

Virtual Volume

Consumed

Reclaimed Space

Reversing Migration

iSCSI Logical Units

Cloud

Related references

Procedure

Related concepts

Procedure

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

5 agg_3

6 agg_4

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

5 agg_3

6 agg_4

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

Related tasks

Cloud providers

HCP Fully qualified

domain name of

the HCP

namespace for the

account

credentials

User name of the

Data Access Account

The password of the

Data Access Account

with readwrite

permission to the

user account

Hitachi

Cloud

Services

Fully qualified

domain name of

the Hitachi Cloud

Services

namespace for the

account

credentials

User name of the

Data Access Account

The password of the

Data Access Account

with readwrite

permission to the

user account

Amazon

S3

Atuto-populates

with aws-

amazoncom

Key

https

consoleawsamazon

comiam

Microsoft

Azure

Auto-populates

with

azuremicrosoftco

m

Name of storage

account

Primary or

Secondary Access

Key

https

azuremicrosoftcom

Procedure

Related tasks

Related references

Procedure

Cloud Destination

Name

Cloud Account

Name

system

Destination

Location

Encrypted In

Transit

encrypt in transit

Procedure

ItemField for Cloud

AccountsDescription

azuremicrosoftcom

account

ItemField for Cloud

AccountsDescription

ItemField for Cloud

Procedure

Cloud Account

Name

Secret

Credential

Procedure

Cloud

Destination

Name

Cloud Account

Name

Destination

Location

Procedure

will be migrated

migrated

Adding a cloud path

Procedure

Primary EVSFile

System

5 Click OK

In Use by

Policies

migrated

Policies and

Schedules

Data Migration

Cloud Accounts

Data Migration

Paths

Related references

Procedure

extension

Access

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

minutes

For example

Procedure

Case-sensitive

pattern checks

Related references

Procedure

In Use by

Policies

Not in use

Rule

Definition

Procedure

ItemField for

PoliciesDescription

Primary File

System

Secondary File

System

Data MigrationRules

ItemField for

PoliciesDescription

Data MigrationPaths

as well

NDMPConfiguration

operation

Procedure

Item Description

type

Item Description

(To create

Available Cloud

Rules

the left arrow (lt)

selected rule(s)

Selected Cloud

Rules

met

(To create rules

rules

Rule Statement

Connection Errors

Procedure

Item Description

migration) policy

Item Description

Pre-Conditions

the left arrow (lt)

selected rule(s)

(To create rules

rules

Procedure

Data Migration

Policy

Date and Time

to Start

Procedure

Data Modify

Policy

Data Migration

Type

Item Description

Policy Policy name

select report

Item Description

Policies and

Schedules

Item Description

Report Summary

Item Description

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Reclaimed

snapshots

Total File System

Reclaimed

snapshots

Scenario 3

Scenario 1 and 2

All Scenarios

Conclusion

(decrease)

Virtualization

Migration

Procedure

Options

--json|-j

Target file system

Name of association

-s --start

-m --migrate

-p --pause

-r --resume

EXAMPLES

APPLIES TO

EVS

Options

--port ltportgt

Target file system

Legacy NAS path URI

EXAMPLES

APPLIES TO

EVS

Options

Target file system

--force

-c --confirm

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-l --list-failed

-r --retry

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-e --journal-enable

-m --email-logs

Sends logs by email

-u --delete-logs

Deletes logs

-c --confirm

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-a --all

All file systems

EXAMPLES

APPLIES TO

EVS

Options

--port ltportgt

-f --force

-s --source

Legacy NAS path URI

EXAMPLES

APPLIES TO

EVS

Options

-a --all

-w --work

-r --reset

Reset statistics

-g --graph

APPLIES TO

EVS

Control via SMU GUI

Rules syntax

Keywords

Connectors

Conditionals

Statement order

Keyword Value(s)

Usage

For example

Keyword Value(s)

Usage

For example

Usage

For example

Usage

For example

ltOLDER_THAN 28gt

Keyword Value(s)

Usage

For example

ltNEWER_THAN 14gt

Usage

For example

Usage

For example

Usage

For example

Usage

For example

ltCHANGED_SINCE 7gt

Rule Description

Rule scenario A

EXCLUDE

Rule scenario B

s3amazonawscom

Single Node

Interface IP

SMU eth0 172101011

Cluster

Interface IP

SMU eth0 172101011

ipaddr -p eth1 -I 19216843116 -m 2552552480

dnsserver add 1921684510 1921684511

s3amazonawscom

Single Node

Interface IP

SMU eth0 172101011

Cluster

Interface IP

SMU eth0 172101011

ipaddr -p eth1 -I 19216843116 -m 2552552480

dnsserver add 1921684510 1921684511

For example

MK-92HNAS005-07

Contents
Preface
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        Migration schedules
        
        
        
        
        
        
        
        
        
        
        Cloud providers
        
        
        
        
        
        
        
        
        
        Adding a cloud path
        
        
        
        
        
        
        
        
        Migration schedules
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        Rules syntax
        
        Keywords
        
        Connectors
        
        Conditionals
        
        Statement order

Page 3: Data Migrator Administration Guide

Contents

Preface

bull

Procedure

2 Click add

Add a License Key

License Key File

Name

Procedure

will be migrated

migrated

for data migrations

Procedure

Primary EVSFile

System

secondary storage

In Use by

Policies

migrated

Policies and

Schedules

Data Migration

Cloud Accounts

Data Migration

Paths

Related references

Procedure

Access

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

minutes

Procedure

Case-sensitive

pattern checks

Procedure

In Use by

Policies

Not in use

Rule

Definition

Procedure

ItemField for

PoliciesDescription

Primary File

System

Secondary File

System

Data MigrationRules

ItemField for

PoliciesDescription

Data MigrationPaths

as well

NDMPConfiguration

operation

Procedure

Item Description

(To create

Available WFS

HNAS Rules

the left arrow (lt)

selected rule(s)

Selected WFS

HNAS Rules

(To create rules

rules

file system

CVL-1

CVL-2

Rule Statement

Connection Errors

Procedure

Item Description

migration) policy

Pre-Conditions

the left arrow (lt)

selected rule(s)

(To create rules

rules

Procedure

Data Migration

Policy

Date and Time

to Start

Procedure

Data Modify

Policy

Data Migration

Type

Item Description

Policy Policy name

select report

Item Description

Policies and

Schedules

Item Description

Report Summary

Item Description

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Reclaimed

snapshots

Total File System

Reclaimed

snapshots

Volume Space Used

migration

Post-Migration

Virtual Volume

Space Used

Virtual Volume

Reclaimed

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Consumed

Item Description

Total File System

Consumed

Volume Space Used

Post-Migration

Virtual Volume

Space Used

Virtual Volume

Consumed

Reclaimed Space

Reversing Migration

iSCSI Logical Units

Cloud

Related references

Procedure

Related concepts

Procedure

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

5 agg_3

6 agg_4

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

5 agg_3

6 agg_4

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

Related tasks

Cloud providers

HCP Fully qualified

domain name of

the HCP

namespace for the

account

credentials

User name of the

Data Access Account

The password of the

Data Access Account

with readwrite

permission to the

user account

Hitachi

Cloud

Services

Fully qualified

domain name of

the Hitachi Cloud

Services

namespace for the

account

credentials

User name of the

Data Access Account

The password of the

Data Access Account

with readwrite

permission to the

user account

Amazon

S3

Atuto-populates

with aws-

amazoncom

Key

https

consoleawsamazon

comiam

Microsoft

Azure

Auto-populates

with

azuremicrosoftco

m

Name of storage

account

Primary or

Secondary Access

Key

https

azuremicrosoftcom

Procedure

Related tasks

Related references

Procedure

Cloud Destination

Name

Cloud Account

Name

system

Destination

Location

Encrypted In

Transit

encrypt in transit

Procedure

ItemField for Cloud

AccountsDescription

azuremicrosoftcom

account

ItemField for Cloud

AccountsDescription

ItemField for Cloud

Procedure

Cloud Account

Name

Secret

Credential

Procedure

Cloud

Destination

Name

Cloud Account

Name

Destination

Location

Procedure

will be migrated

migrated

Adding a cloud path

Procedure

Primary EVSFile

System

5 Click OK

In Use by

Policies

migrated

Policies and

Schedules

Data Migration

Cloud Accounts

Data Migration

Paths

Related references

Procedure

extension

Access

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

minutes

For example

Procedure

Case-sensitive

pattern checks

Related references

Procedure

In Use by

Policies

Not in use

Rule

Definition

Procedure

ItemField for

PoliciesDescription

Primary File

System

Secondary File

System

Data MigrationRules

ItemField for

PoliciesDescription

Data MigrationPaths

as well

NDMPConfiguration

operation

Procedure

Item Description

type

Item Description

(To create

Available Cloud

Rules

the left arrow (lt)

selected rule(s)

Selected Cloud

Rules

met

(To create rules

rules

Rule Statement

Connection Errors

Procedure

Item Description

migration) policy

Item Description

Pre-Conditions

the left arrow (lt)

selected rule(s)

(To create rules

rules

Procedure

Data Migration

Policy

Date and Time

to Start

Procedure

Data Modify

Policy

Data Migration

Type

Item Description

Policy Policy name

select report

Item Description

Policies and

Schedules

Item Description

Report Summary

Item Description

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Reclaimed

snapshots

Total File System

Reclaimed

snapshots

Scenario 3

Scenario 1 and 2

All Scenarios

Conclusion

(decrease)

Virtualization

Migration

Procedure

Options

--json|-j

Target file system

Name of association

-s --start

-m --migrate

-p --pause

-r --resume

EXAMPLES

APPLIES TO

EVS

Options

--port ltportgt

Target file system

Legacy NAS path URI

EXAMPLES

APPLIES TO

EVS

Options

Target file system

--force

-c --confirm

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-l --list-failed

-r --retry

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-e --journal-enable

-m --email-logs

Sends logs by email

-u --delete-logs

Deletes logs

-c --confirm

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-a --all

All file systems

EXAMPLES

APPLIES TO

EVS

Options

--port ltportgt

-f --force

-s --source

Legacy NAS path URI

EXAMPLES

APPLIES TO

EVS

Options

-a --all

-w --work

-r --reset

Reset statistics

-g --graph

APPLIES TO

EVS

Control via SMU GUI

Rules syntax

Keywords

Connectors

Conditionals

Statement order

Keyword Value(s)

Usage

For example

Keyword Value(s)

Usage

For example

Usage

For example

Usage

For example

ltOLDER_THAN 28gt

Keyword Value(s)

Usage

For example

ltNEWER_THAN 14gt

Usage

For example

Usage

For example

Usage

For example

Usage

For example

ltCHANGED_SINCE 7gt

Rule Description

Rule scenario A

EXCLUDE

Rule scenario B

s3amazonawscom

Single Node

Interface IP

SMU eth0 172101011

Cluster

Interface IP

SMU eth0 172101011

ipaddr -p eth1 -I 19216843116 -m 2552552480

dnsserver add 1921684510 1921684511

s3amazonawscom

Single Node

Interface IP

SMU eth0 172101011

Cluster

Interface IP

SMU eth0 172101011

ipaddr -p eth1 -I 19216843116 -m 2552552480

dnsserver add 1921684510 1921684511

For example

MK-92HNAS005-07

Contents
Preface
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        Migration schedules
        
        
        
        
        
        
        
        
        
        
        Cloud providers
        
        
        
        
        
        
        
        
        
        Adding a cloud path
        
        
        
        
        
        
        
        
        Migration schedules
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        Rules syntax
        
        Keywords
        
        Connectors
        
        Conditionals
        
        Statement order

Page 4: Data Migrator Administration Guide

Contents

Preface

bull

Procedure

2 Click add

Add a License Key

License Key File

Name

Procedure

will be migrated

migrated

for data migrations

Procedure

Primary EVSFile

System

secondary storage

In Use by

Policies

migrated

Policies and

Schedules

Data Migration

Cloud Accounts

Data Migration

Paths

Related references

Procedure

Access

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

minutes

Procedure

Case-sensitive

pattern checks

Procedure

In Use by

Policies

Not in use

Rule

Definition

Procedure

ItemField for

PoliciesDescription

Primary File

System

Secondary File

System

Data MigrationRules

ItemField for

PoliciesDescription

Data MigrationPaths

as well

NDMPConfiguration

operation

Procedure

Item Description

(To create

Available WFS

HNAS Rules

the left arrow (lt)

selected rule(s)

Selected WFS

HNAS Rules

(To create rules

rules

file system

CVL-1

CVL-2

Rule Statement

Connection Errors

Procedure

Item Description

migration) policy

Pre-Conditions

the left arrow (lt)

selected rule(s)

(To create rules

rules

Procedure

Data Migration

Policy

Date and Time

to Start

Procedure

Data Modify

Policy

Data Migration

Type

Item Description

Policy Policy name

select report

Item Description

Policies and

Schedules

Item Description

Report Summary

Item Description

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Reclaimed

snapshots

Total File System

Reclaimed

snapshots

Volume Space Used

migration

Post-Migration

Virtual Volume

Space Used

Virtual Volume

Reclaimed

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Consumed

Item Description

Total File System

Consumed

Volume Space Used

Post-Migration

Virtual Volume

Space Used

Virtual Volume

Consumed

Reclaimed Space

Reversing Migration

iSCSI Logical Units

Cloud

Related references

Procedure

Related concepts

Procedure

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

5 agg_3

6 agg_4

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

5 agg_3

6 agg_4

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

Related tasks

Cloud providers

HCP Fully qualified

domain name of

the HCP

namespace for the

account

credentials

User name of the

Data Access Account

The password of the

Data Access Account

with readwrite

permission to the

user account

Hitachi

Cloud

Services

Fully qualified

domain name of

the Hitachi Cloud

Services

namespace for the

account

credentials

User name of the

Data Access Account

The password of the

Data Access Account

with readwrite

permission to the

user account

Amazon

S3

Atuto-populates

with aws-

amazoncom

Key

https

consoleawsamazon

comiam

Microsoft

Azure

Auto-populates

with

azuremicrosoftco

m

Name of storage

account

Primary or

Secondary Access

Key

https

azuremicrosoftcom

Procedure

Related tasks

Related references

Procedure

Cloud Destination

Name

Cloud Account

Name

system

Destination

Location

Encrypted In

Transit

encrypt in transit

Procedure

ItemField for Cloud

AccountsDescription

azuremicrosoftcom

account

ItemField for Cloud

AccountsDescription

ItemField for Cloud

Procedure

Cloud Account

Name

Secret

Credential

Procedure

Cloud

Destination

Name

Cloud Account

Name

Destination

Location

Procedure

will be migrated

migrated

Adding a cloud path

Procedure

Primary EVSFile

System

5 Click OK

In Use by

Policies

migrated

Policies and

Schedules

Data Migration

Cloud Accounts

Data Migration

Paths

Related references

Procedure

extension

Access

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

minutes

For example

Procedure

Case-sensitive

pattern checks

Related references

Procedure

In Use by

Policies

Not in use

Rule

Definition

Procedure

ItemField for

PoliciesDescription

Primary File

System

Secondary File

System

Data MigrationRules

ItemField for

PoliciesDescription

Data MigrationPaths

as well

NDMPConfiguration

operation

Procedure

Item Description

type

Item Description

(To create

Available Cloud

Rules

the left arrow (lt)

selected rule(s)

Selected Cloud

Rules

met

(To create rules

rules

Rule Statement

Connection Errors

Procedure

Item Description

migration) policy

Item Description

Pre-Conditions

the left arrow (lt)

selected rule(s)

(To create rules

rules

Procedure

Data Migration

Policy

Date and Time

to Start

Procedure

Data Modify

Policy

Data Migration

Type

Item Description

Policy Policy name

select report

Item Description

Policies and

Schedules

Item Description

Report Summary

Item Description

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Reclaimed

snapshots

Total File System

Reclaimed

snapshots

Scenario 3

Scenario 1 and 2

All Scenarios

Conclusion

(decrease)

Virtualization

Migration

Procedure

Options

--json|-j

Target file system

Name of association

-s --start

-m --migrate

-p --pause

-r --resume

EXAMPLES

APPLIES TO

EVS

Options

--port ltportgt

Target file system

Legacy NAS path URI

EXAMPLES

APPLIES TO

EVS

Options

Target file system

--force

-c --confirm

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-l --list-failed

-r --retry

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-e --journal-enable

-m --email-logs

Sends logs by email

-u --delete-logs

Deletes logs

-c --confirm

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-a --all

All file systems

EXAMPLES

APPLIES TO

EVS

Options

--port ltportgt

-f --force

-s --source

Legacy NAS path URI

EXAMPLES

APPLIES TO

EVS

Options

-a --all

-w --work

-r --reset

Reset statistics

-g --graph

APPLIES TO

EVS

Control via SMU GUI

Rules syntax

Keywords

Connectors

Conditionals

Statement order

Keyword Value(s)

Usage

For example

Keyword Value(s)

Usage

For example

Usage

For example

Usage

For example

ltOLDER_THAN 28gt

Keyword Value(s)

Usage

For example

ltNEWER_THAN 14gt

Usage

For example

Usage

For example

Usage

For example

Usage

For example

ltCHANGED_SINCE 7gt

Rule Description

Rule scenario A

EXCLUDE

Rule scenario B

s3amazonawscom

Single Node

Interface IP

SMU eth0 172101011

Cluster

Interface IP

SMU eth0 172101011

ipaddr -p eth1 -I 19216843116 -m 2552552480

dnsserver add 1921684510 1921684511

s3amazonawscom

Single Node

Interface IP

SMU eth0 172101011

Cluster

Interface IP

SMU eth0 172101011

ipaddr -p eth1 -I 19216843116 -m 2552552480

dnsserver add 1921684510 1921684511

For example

MK-92HNAS005-07

Contents
Preface
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        Migration schedules
        
        
        
        
        
        
        
        
        
        
        Cloud providers
        
        
        
        
        
        
        
        
        
        Adding a cloud path
        
        
        
        
        
        
        
        
        Migration schedules
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        Rules syntax
        
        Keywords
        
        Connectors
        
        Conditionals
        
        Statement order

Page 5: Data Migrator Administration Guide

Preface

bull

Procedure

2 Click add

Add a License Key

License Key File

Name

Procedure

will be migrated

migrated

for data migrations

Procedure

Primary EVSFile

System

secondary storage

In Use by

Policies

migrated

Policies and

Schedules

Data Migration

Cloud Accounts

Data Migration

Paths

Related references

Procedure

Access

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

minutes

Procedure

Case-sensitive

pattern checks

Procedure

In Use by

Policies

Not in use

Rule

Definition

Procedure

ItemField for

PoliciesDescription

Primary File

System

Secondary File

System

Data MigrationRules

ItemField for

PoliciesDescription

Data MigrationPaths

as well

NDMPConfiguration

operation

Procedure

Item Description

(To create

Available WFS

HNAS Rules

the left arrow (lt)

selected rule(s)

Selected WFS

HNAS Rules

(To create rules

rules

file system

CVL-1

CVL-2

Rule Statement

Connection Errors

Procedure

Item Description

migration) policy

Pre-Conditions

the left arrow (lt)

selected rule(s)

(To create rules

rules

Procedure

Data Migration

Policy

Date and Time

to Start

Procedure

Data Modify

Policy

Data Migration

Type

Item Description

Policy Policy name

select report

Item Description

Policies and

Schedules

Item Description

Report Summary

Item Description

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Reclaimed

snapshots

Total File System

Reclaimed

snapshots

Volume Space Used

migration

Post-Migration

Virtual Volume

Space Used

Virtual Volume

Reclaimed

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Consumed

Item Description

Total File System

Consumed

Volume Space Used

Post-Migration

Virtual Volume

Space Used

Virtual Volume

Consumed

Reclaimed Space

Reversing Migration

iSCSI Logical Units

Cloud

Related references

Procedure

Related concepts

Procedure

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

5 agg_3

6 agg_4

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

5 agg_3

6 agg_4

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

Related tasks

Cloud providers

HCP Fully qualified

domain name of

the HCP

namespace for the

account

credentials

User name of the

Data Access Account

The password of the

Data Access Account

with readwrite

permission to the

user account

Hitachi

Cloud

Services

Fully qualified

domain name of

the Hitachi Cloud

Services

namespace for the

account

credentials

User name of the

Data Access Account

The password of the

Data Access Account

with readwrite

permission to the

user account

Amazon

S3

Atuto-populates

with aws-

amazoncom

Key

https

consoleawsamazon

comiam

Microsoft

Azure

Auto-populates

with

azuremicrosoftco

m

Name of storage

account

Primary or

Secondary Access

Key

https

azuremicrosoftcom

Procedure

Related tasks

Related references

Procedure

Cloud Destination

Name

Cloud Account

Name

system

Destination

Location

Encrypted In

Transit

encrypt in transit

Procedure

ItemField for Cloud

AccountsDescription

azuremicrosoftcom

account

ItemField for Cloud

AccountsDescription

ItemField for Cloud

Procedure

Cloud Account

Name

Secret

Credential

Procedure

Cloud

Destination

Name

Cloud Account

Name

Destination

Location

Procedure

will be migrated

migrated

Adding a cloud path

Procedure

Primary EVSFile

System

5 Click OK

In Use by

Policies

migrated

Policies and

Schedules

Data Migration

Cloud Accounts

Data Migration

Paths

Related references

Procedure

extension

Access

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

minutes

For example

Procedure

Case-sensitive

pattern checks

Related references

Procedure

In Use by

Policies

Not in use

Rule

Definition

Procedure

ItemField for

PoliciesDescription

Primary File

System

Secondary File

System

Data MigrationRules

ItemField for

PoliciesDescription

Data MigrationPaths

as well

NDMPConfiguration

operation

Procedure

Item Description

type

Item Description

(To create

Available Cloud

Rules

the left arrow (lt)

selected rule(s)

Selected Cloud

Rules

met

(To create rules

rules

Rule Statement

Connection Errors

Procedure

Item Description

migration) policy

Item Description

Pre-Conditions

the left arrow (lt)

selected rule(s)

(To create rules

rules

Procedure

Data Migration

Policy

Date and Time

to Start

Procedure

Data Modify

Policy

Data Migration

Type

Item Description

Policy Policy name

select report

Item Description

Policies and

Schedules

Item Description

Report Summary

Item Description

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Reclaimed

snapshots

Total File System

Reclaimed

snapshots

Scenario 3

Scenario 1 and 2

All Scenarios

Conclusion

(decrease)

Virtualization

Migration

Procedure

Options

--json|-j

Target file system

Name of association

-s --start

-m --migrate

-p --pause

-r --resume

EXAMPLES

APPLIES TO

EVS

Options

--port ltportgt

Target file system

Legacy NAS path URI

EXAMPLES

APPLIES TO

EVS

Options

Target file system

--force

-c --confirm

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-l --list-failed

-r --retry

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-e --journal-enable

-m --email-logs

Sends logs by email

-u --delete-logs

Deletes logs

-c --confirm

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-a --all

All file systems

EXAMPLES

APPLIES TO

EVS

Options

--port ltportgt

-f --force

-s --source

Legacy NAS path URI

EXAMPLES

APPLIES TO

EVS

Options

-a --all

-w --work

-r --reset

Reset statistics

-g --graph

APPLIES TO

EVS

Control via SMU GUI

Rules syntax

Keywords

Connectors

Conditionals

Statement order

Keyword Value(s)

Usage

For example

Keyword Value(s)

Usage

For example

Usage

For example

Usage

For example

ltOLDER_THAN 28gt

Keyword Value(s)

Usage

For example

ltNEWER_THAN 14gt

Usage

For example

Usage

For example

Usage

For example

Usage

For example

ltCHANGED_SINCE 7gt

Rule Description

Rule scenario A

EXCLUDE

Rule scenario B

s3amazonawscom

Single Node

Interface IP

SMU eth0 172101011

Cluster

Interface IP

SMU eth0 172101011

ipaddr -p eth1 -I 19216843116 -m 2552552480

dnsserver add 1921684510 1921684511

s3amazonawscom

Single Node

Interface IP

SMU eth0 172101011

Cluster

Interface IP

SMU eth0 172101011

ipaddr -p eth1 -I 19216843116 -m 2552552480

dnsserver add 1921684510 1921684511

For example

MK-92HNAS005-07

Contents
Preface
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        Migration schedules
        
        
        
        
        
        
        
        
        
        
        Cloud providers
        
        
        
        
        
        
        
        
        
        Adding a cloud path
        
        
        
        
        
        
        
        
        Migration schedules
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        Rules syntax
        
        Keywords
        
        Connectors
        
        Conditionals
        
        Statement order

Page 6: Data Migrator Administration Guide

Preface

bull

Procedure

2 Click add

Add a License Key

License Key File

Name

Procedure

will be migrated

migrated

for data migrations

Procedure

Primary EVSFile

System

secondary storage

In Use by

Policies

migrated

Policies and

Schedules

Data Migration

Cloud Accounts

Data Migration

Paths

Related references

Procedure

Access

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

minutes

Procedure

Case-sensitive

pattern checks

Procedure

In Use by

Policies

Not in use

Rule

Definition

Procedure

ItemField for

PoliciesDescription

Primary File

System

Secondary File

System

Data MigrationRules

ItemField for

PoliciesDescription

Data MigrationPaths

as well

NDMPConfiguration

operation

Procedure

Item Description

(To create

Available WFS

HNAS Rules

the left arrow (lt)

selected rule(s)

Selected WFS

HNAS Rules

(To create rules

rules

file system

CVL-1

CVL-2

Rule Statement

Connection Errors

Procedure

Item Description

migration) policy

Pre-Conditions

the left arrow (lt)

selected rule(s)

(To create rules

rules

Procedure

Data Migration

Policy

Date and Time

to Start

Procedure

Data Modify

Policy

Data Migration

Type

Item Description

Policy Policy name

select report

Item Description

Policies and

Schedules

Item Description

Report Summary

Item Description

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Reclaimed

snapshots

Total File System

Reclaimed

snapshots

Volume Space Used

migration

Post-Migration

Virtual Volume

Space Used

Virtual Volume

Reclaimed

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Consumed

Item Description

Total File System

Consumed

Volume Space Used

Post-Migration

Virtual Volume

Space Used

Virtual Volume

Consumed

Reclaimed Space

Reversing Migration

iSCSI Logical Units

Cloud

Related references

Procedure

Related concepts

Procedure

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

5 agg_3

6 agg_4

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

5 agg_3

6 agg_4

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

Related tasks

Cloud providers

HCP Fully qualified

domain name of

the HCP

namespace for the

account

credentials

User name of the

Data Access Account

The password of the

Data Access Account

with readwrite

permission to the

user account

Hitachi

Cloud

Services

Fully qualified

domain name of

the Hitachi Cloud

Services

namespace for the

account

credentials

User name of the

Data Access Account

The password of the

Data Access Account

with readwrite

permission to the

user account

Amazon

S3

Atuto-populates

with aws-

amazoncom

Key

https

consoleawsamazon

comiam

Microsoft

Azure

Auto-populates

with

azuremicrosoftco

m

Name of storage

account

Primary or

Secondary Access

Key

https

azuremicrosoftcom

Procedure

Related tasks

Related references

Procedure

Cloud Destination

Name

Cloud Account

Name

system

Destination

Location

Encrypted In

Transit

encrypt in transit

Procedure

ItemField for Cloud

AccountsDescription

azuremicrosoftcom

account

ItemField for Cloud

AccountsDescription

ItemField for Cloud

Procedure

Cloud Account

Name

Secret

Credential

Procedure

Cloud

Destination

Name

Cloud Account

Name

Destination

Location

Procedure

will be migrated

migrated

Adding a cloud path

Procedure

Primary EVSFile

System

5 Click OK

In Use by

Policies

migrated

Policies and

Schedules

Data Migration

Cloud Accounts

Data Migration

Paths

Related references

Procedure

extension

Access

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

minutes

For example

Procedure

Case-sensitive

pattern checks

Related references

Procedure

In Use by

Policies

Not in use

Rule

Definition

Procedure

ItemField for

PoliciesDescription

Primary File

System

Secondary File

System

Data MigrationRules

ItemField for

PoliciesDescription

Data MigrationPaths

as well

NDMPConfiguration

operation

Procedure

Item Description

type

Item Description

(To create

Available Cloud

Rules

the left arrow (lt)

selected rule(s)

Selected Cloud

Rules

met

(To create rules

rules

Rule Statement

Connection Errors

Procedure

Item Description

migration) policy

Item Description

Pre-Conditions

the left arrow (lt)

selected rule(s)

(To create rules

rules

Procedure

Data Migration

Policy

Date and Time

to Start

Procedure

Data Modify

Policy

Data Migration

Type

Item Description

Policy Policy name

select report

Item Description

Policies and

Schedules

Item Description

Report Summary

Item Description

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Reclaimed

snapshots

Total File System

Reclaimed

snapshots

Scenario 3

Scenario 1 and 2

All Scenarios

Conclusion

(decrease)

Virtualization

Migration

Procedure

Options

--json|-j

Target file system

Name of association

-s --start

-m --migrate

-p --pause

-r --resume

EXAMPLES

APPLIES TO

EVS

Options

--port ltportgt

Target file system

Legacy NAS path URI

EXAMPLES

APPLIES TO

EVS

Options

Target file system

--force

-c --confirm

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-l --list-failed

-r --retry

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-e --journal-enable

-m --email-logs

Sends logs by email

-u --delete-logs

Deletes logs

-c --confirm

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-a --all

All file systems

EXAMPLES

APPLIES TO

EVS

Options

--port ltportgt

-f --force

-s --source

Legacy NAS path URI

EXAMPLES

APPLIES TO

EVS

Options

-a --all

-w --work

-r --reset

Reset statistics

-g --graph

APPLIES TO

EVS

Control via SMU GUI

Rules syntax

Keywords

Connectors

Conditionals

Statement order

Keyword Value(s)

Usage

For example

Keyword Value(s)

Usage

For example

Usage

For example

Usage

For example

ltOLDER_THAN 28gt

Keyword Value(s)

Usage

For example

ltNEWER_THAN 14gt

Usage

For example

Usage

For example

Usage

For example

Usage

For example

ltCHANGED_SINCE 7gt

Rule Description

Rule scenario A

EXCLUDE

Rule scenario B

s3amazonawscom

Single Node

Interface IP

SMU eth0 172101011

Cluster

Interface IP

SMU eth0 172101011

ipaddr -p eth1 -I 19216843116 -m 2552552480

dnsserver add 1921684510 1921684511

s3amazonawscom

Single Node

Interface IP

SMU eth0 172101011

Cluster

Interface IP

SMU eth0 172101011

ipaddr -p eth1 -I 19216843116 -m 2552552480

dnsserver add 1921684510 1921684511

For example

MK-92HNAS005-07

Contents
Preface
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        Migration schedules
        
        
        
        
        
        
        
        
        
        
        Cloud providers
        
        
        
        
        
        
        
        
        
        Adding a cloud path
        
        
        
        
        
        
        
        
        Migration schedules
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        Rules syntax
        
        Keywords
        
        Connectors
        
        Conditionals
        
        Statement order

Page 7: Data Migrator Administration Guide

Preface

bull

Procedure

2 Click add

Add a License Key

License Key File

Name

Procedure

will be migrated

migrated

for data migrations

Procedure

Primary EVSFile

System

secondary storage

In Use by

Policies

migrated

Policies and

Schedules

Data Migration

Cloud Accounts

Data Migration

Paths

Related references

Procedure

Access

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

minutes

Procedure

Case-sensitive

pattern checks

Procedure

In Use by

Policies

Not in use

Rule

Definition

Procedure

ItemField for

PoliciesDescription

Primary File

System

Secondary File

System

Data MigrationRules

ItemField for

PoliciesDescription

Data MigrationPaths

as well

NDMPConfiguration

operation

Procedure

Item Description

(To create

Available WFS

HNAS Rules

the left arrow (lt)

selected rule(s)

Selected WFS

HNAS Rules

(To create rules

rules

file system

CVL-1

CVL-2

Rule Statement

Connection Errors

Procedure

Item Description

migration) policy

Pre-Conditions

the left arrow (lt)

selected rule(s)

(To create rules

rules

Procedure

Data Migration

Policy

Date and Time

to Start

Procedure

Data Modify

Policy

Data Migration

Type

Item Description

Policy Policy name

select report

Item Description

Policies and

Schedules

Item Description

Report Summary

Item Description

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Reclaimed

snapshots

Total File System

Reclaimed

snapshots

Volume Space Used

migration

Post-Migration

Virtual Volume

Space Used

Virtual Volume

Reclaimed

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Consumed

Item Description

Total File System

Consumed

Volume Space Used

Post-Migration

Virtual Volume

Space Used

Virtual Volume

Consumed

Reclaimed Space

Reversing Migration

iSCSI Logical Units

Cloud

Related references

Procedure

Related concepts

Procedure

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

5 agg_3

6 agg_4

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

5 agg_3

6 agg_4

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

Related tasks

Cloud providers

HCP Fully qualified

domain name of

the HCP

namespace for the

account

credentials

User name of the

Data Access Account

The password of the

Data Access Account

with readwrite

permission to the

user account

Hitachi

Cloud

Services

Fully qualified

domain name of

the Hitachi Cloud

Services

namespace for the

account

credentials

User name of the

Data Access Account

The password of the

Data Access Account

with readwrite

permission to the

user account

Amazon

S3

Atuto-populates

with aws-

amazoncom

Key

https

consoleawsamazon

comiam

Microsoft

Azure

Auto-populates

with

azuremicrosoftco

m

Name of storage

account

Primary or

Secondary Access

Key

https

azuremicrosoftcom

Procedure

Related tasks

Related references

Procedure

Cloud Destination

Name

Cloud Account

Name

system

Destination

Location

Encrypted In

Transit

encrypt in transit

Procedure

ItemField for Cloud

AccountsDescription

azuremicrosoftcom

account

ItemField for Cloud

AccountsDescription

ItemField for Cloud

Procedure

Cloud Account

Name

Secret

Credential

Procedure

Cloud

Destination

Name

Cloud Account

Name

Destination

Location

Procedure

will be migrated

migrated

Adding a cloud path

Procedure

Primary EVSFile

System

5 Click OK

In Use by

Policies

migrated

Policies and

Schedules

Data Migration

Cloud Accounts

Data Migration

Paths

Related references

Procedure

extension

Access

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

minutes

For example

Procedure

Case-sensitive

pattern checks

Related references

Procedure

In Use by

Policies

Not in use

Rule

Definition

Procedure

ItemField for

PoliciesDescription

Primary File

System

Secondary File

System

Data MigrationRules

ItemField for

PoliciesDescription

Data MigrationPaths

as well

NDMPConfiguration

operation

Procedure

Item Description

type

Item Description

(To create

Available Cloud

Rules

the left arrow (lt)

selected rule(s)

Selected Cloud

Rules

met

(To create rules

rules

Rule Statement

Connection Errors

Procedure

Item Description

migration) policy

Item Description

Pre-Conditions

the left arrow (lt)

selected rule(s)

(To create rules

rules

Procedure

Data Migration

Policy

Date and Time

to Start

Procedure

Data Modify

Policy

Data Migration

Type

Item Description

Policy Policy name

select report

Item Description

Policies and

Schedules

Item Description

Report Summary

Item Description

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Reclaimed

snapshots

Total File System

Reclaimed

snapshots

Scenario 3

Scenario 1 and 2

All Scenarios

Conclusion

(decrease)

Virtualization

Migration

Procedure

Options

--json|-j

Target file system

Name of association

-s --start

-m --migrate

-p --pause

-r --resume

EXAMPLES

APPLIES TO

EVS

Options

--port ltportgt

Target file system

Legacy NAS path URI

EXAMPLES

APPLIES TO

EVS

Options

Target file system

--force

-c --confirm

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-l --list-failed

-r --retry

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-e --journal-enable

-m --email-logs

Sends logs by email

-u --delete-logs

Deletes logs

-c --confirm

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-a --all

All file systems

EXAMPLES

APPLIES TO

EVS

Options

--port ltportgt

-f --force

-s --source

Legacy NAS path URI

EXAMPLES

APPLIES TO

EVS

Options

-a --all

-w --work

-r --reset

Reset statistics

-g --graph

APPLIES TO

EVS

Control via SMU GUI

Rules syntax

Keywords

Connectors

Conditionals

Statement order

Keyword Value(s)

Usage

For example

Keyword Value(s)

Usage

For example

Usage

For example

Usage

For example

ltOLDER_THAN 28gt

Keyword Value(s)

Usage

For example

ltNEWER_THAN 14gt

Usage

For example

Usage

For example

Usage

For example

Usage

For example

ltCHANGED_SINCE 7gt

Rule Description

Rule scenario A

EXCLUDE

Rule scenario B

s3amazonawscom

Single Node

Interface IP

SMU eth0 172101011

Cluster

Interface IP

SMU eth0 172101011

ipaddr -p eth1 -I 19216843116 -m 2552552480

dnsserver add 1921684510 1921684511

s3amazonawscom

Single Node

Interface IP

SMU eth0 172101011

Cluster

Interface IP

SMU eth0 172101011

ipaddr -p eth1 -I 19216843116 -m 2552552480

dnsserver add 1921684510 1921684511

For example

MK-92HNAS005-07

Contents
Preface
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        Migration schedules
        
        
        
        
        
        
        
        
        
        
        Cloud providers
        
        
        
        
        
        
        
        
        
        Adding a cloud path
        
        
        
        
        
        
        
        
        Migration schedules
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        Rules syntax
        
        Keywords
        
        Connectors
        
        Conditionals
        
        Statement order

Page 8: Data Migrator Administration Guide

Preface

bull

Procedure

2 Click add

Add a License Key

License Key File

Name

Procedure

will be migrated

migrated

for data migrations

Procedure

Primary EVSFile

System

secondary storage

In Use by

Policies

migrated

Policies and

Schedules

Data Migration

Cloud Accounts

Data Migration

Paths

Related references

Procedure

Access

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

minutes

Procedure

Case-sensitive

pattern checks

Procedure

In Use by

Policies

Not in use

Rule

Definition

Procedure

ItemField for

PoliciesDescription

Primary File

System

Secondary File

System

Data MigrationRules

ItemField for

PoliciesDescription

Data MigrationPaths

as well

NDMPConfiguration

operation

Procedure

Item Description

(To create

Available WFS

HNAS Rules

the left arrow (lt)

selected rule(s)

Selected WFS

HNAS Rules

(To create rules

rules

file system

CVL-1

CVL-2

Rule Statement

Connection Errors

Procedure

Item Description

migration) policy

Pre-Conditions

the left arrow (lt)

selected rule(s)

(To create rules

rules

Procedure

Data Migration

Policy

Date and Time

to Start

Procedure

Data Modify

Policy

Data Migration

Type

Item Description

Policy Policy name

select report

Item Description

Policies and

Schedules

Item Description

Report Summary

Item Description

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Reclaimed

snapshots

Total File System

Reclaimed

snapshots

Volume Space Used

migration

Post-Migration

Virtual Volume

Space Used

Virtual Volume

Reclaimed

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Consumed

Item Description

Total File System

Consumed

Volume Space Used

Post-Migration

Virtual Volume

Space Used

Virtual Volume

Consumed

Reclaimed Space

Reversing Migration

iSCSI Logical Units

Cloud

Related references

Procedure

Related concepts

Procedure

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

5 agg_3

6 agg_4

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

5 agg_3

6 agg_4

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

Related tasks

Cloud providers

HCP Fully qualified

domain name of

the HCP

namespace for the

account

credentials

User name of the

Data Access Account

The password of the

Data Access Account

with readwrite

permission to the

user account

Hitachi

Cloud

Services

Fully qualified

domain name of

the Hitachi Cloud

Services

namespace for the

account

credentials

User name of the

Data Access Account

The password of the

Data Access Account

with readwrite

permission to the

user account

Amazon

S3

Atuto-populates

with aws-

amazoncom

Key

https

consoleawsamazon

comiam

Microsoft

Azure

Auto-populates

with

azuremicrosoftco

m

Name of storage

account

Primary or

Secondary Access

Key

https

azuremicrosoftcom

Procedure

Related tasks

Related references

Procedure

Cloud Destination

Name

Cloud Account

Name

system

Destination

Location

Encrypted In

Transit

encrypt in transit

Procedure

ItemField for Cloud

AccountsDescription

azuremicrosoftcom

account

ItemField for Cloud

AccountsDescription

ItemField for Cloud

Procedure

Cloud Account

Name

Secret

Credential

Procedure

Cloud

Destination

Name

Cloud Account

Name

Destination

Location

Procedure

will be migrated

migrated

Adding a cloud path

Procedure

Primary EVSFile

System

5 Click OK

In Use by

Policies

migrated

Policies and

Schedules

Data Migration

Cloud Accounts

Data Migration

Paths

Related references

Procedure

extension

Access

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

minutes

For example

Procedure

Case-sensitive

pattern checks

Related references

Procedure

In Use by

Policies

Not in use

Rule

Definition

Procedure

ItemField for

PoliciesDescription

Primary File

System

Secondary File

System

Data MigrationRules

ItemField for

PoliciesDescription

Data MigrationPaths

as well

NDMPConfiguration

operation

Procedure

Item Description

type

Item Description

(To create

Available Cloud

Rules

the left arrow (lt)

selected rule(s)

Selected Cloud

Rules

met

(To create rules

rules

Rule Statement

Connection Errors

Procedure

Item Description

migration) policy

Item Description

Pre-Conditions

the left arrow (lt)

selected rule(s)

(To create rules

rules

Procedure

Data Migration

Policy

Date and Time

to Start

Procedure

Data Modify

Policy

Data Migration

Type

Item Description

Policy Policy name

select report

Item Description

Policies and

Schedules

Item Description

Report Summary

Item Description

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Reclaimed

snapshots

Total File System

Reclaimed

snapshots

Scenario 3

Scenario 1 and 2

All Scenarios

Conclusion

(decrease)

Virtualization

Migration

Procedure

Options

--json|-j

Target file system

Name of association

-s --start

-m --migrate

-p --pause

-r --resume

EXAMPLES

APPLIES TO

EVS

Options

--port ltportgt

Target file system

Legacy NAS path URI

EXAMPLES

APPLIES TO

EVS

Options

Target file system

--force

-c --confirm

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-l --list-failed

-r --retry

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-e --journal-enable

-m --email-logs

Sends logs by email

-u --delete-logs

Deletes logs

-c --confirm

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-a --all

All file systems

EXAMPLES

APPLIES TO

EVS

Options

--port ltportgt

-f --force

-s --source

Legacy NAS path URI

EXAMPLES

APPLIES TO

EVS

Options

-a --all

-w --work

-r --reset

Reset statistics

-g --graph

APPLIES TO

EVS

Control via SMU GUI

Rules syntax

Keywords

Connectors

Conditionals

Statement order

Keyword Value(s)

Usage

For example

Keyword Value(s)

Usage

For example

Usage

For example

Usage

For example

ltOLDER_THAN 28gt

Keyword Value(s)

Usage

For example

ltNEWER_THAN 14gt

Usage

For example

Usage

For example

Usage

For example

Usage

For example

ltCHANGED_SINCE 7gt

Rule Description

Rule scenario A

EXCLUDE

Rule scenario B

s3amazonawscom

Single Node

Interface IP

SMU eth0 172101011

Cluster

Interface IP

SMU eth0 172101011

ipaddr -p eth1 -I 19216843116 -m 2552552480

dnsserver add 1921684510 1921684511

s3amazonawscom

Single Node

Interface IP

SMU eth0 172101011

Cluster

Interface IP

SMU eth0 172101011

ipaddr -p eth1 -I 19216843116 -m 2552552480

dnsserver add 1921684510 1921684511

For example

MK-92HNAS005-07

Contents
Preface
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        Migration schedules
        
        
        
        
        
        
        
        
        
        
        Cloud providers
        
        
        
        
        
        
        
        
        
        Adding a cloud path
        
        
        
        
        
        
        
        
        Migration schedules
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        Rules syntax
        
        Keywords
        
        Connectors
        
        Conditionals
        
        Statement order

Page 9: Data Migrator Administration Guide

bull

Procedure

2 Click add

Add a License Key

License Key File

Name

Procedure

will be migrated

migrated

for data migrations

Procedure

Primary EVSFile

System

secondary storage

In Use by

Policies

migrated

Policies and

Schedules

Data Migration

Cloud Accounts

Data Migration

Paths

Related references

Procedure

Access

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

minutes

Procedure

Case-sensitive

pattern checks

Procedure

In Use by

Policies

Not in use

Rule

Definition

Procedure

ItemField for

PoliciesDescription

Primary File

System

Secondary File

System

Data MigrationRules

ItemField for

PoliciesDescription

Data MigrationPaths

as well

NDMPConfiguration

operation

Procedure

Item Description

(To create

Available WFS

HNAS Rules

the left arrow (lt)

selected rule(s)

Selected WFS

HNAS Rules

(To create rules

rules

file system

CVL-1

CVL-2

Rule Statement

Connection Errors

Procedure

Item Description

migration) policy

Pre-Conditions

the left arrow (lt)

selected rule(s)

(To create rules

rules

Procedure

Data Migration

Policy

Date and Time

to Start

Procedure

Data Modify

Policy

Data Migration

Type

Item Description

Policy Policy name

select report

Item Description

Policies and

Schedules

Item Description

Report Summary

Item Description

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Reclaimed

snapshots

Total File System

Reclaimed

snapshots

Volume Space Used

migration

Post-Migration

Virtual Volume

Space Used

Virtual Volume

Reclaimed

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Consumed

Item Description

Total File System

Consumed

Volume Space Used

Post-Migration

Virtual Volume

Space Used

Virtual Volume

Consumed

Reclaimed Space

Reversing Migration

iSCSI Logical Units

Cloud

Related references

Procedure

Related concepts

Procedure

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

5 agg_3

6 agg_4

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

5 agg_3

6 agg_4

Item Description

1 HNAS node 1

2 HNAS node 2

3 agg_1

4 agg_2

Related tasks

Cloud providers

HCP Fully qualified

domain name of

the HCP

namespace for the

account

credentials

User name of the

Data Access Account

The password of the

Data Access Account

with readwrite

permission to the

user account

Hitachi

Cloud

Services

Fully qualified

domain name of

the Hitachi Cloud

Services

namespace for the

account

credentials

User name of the

Data Access Account

The password of the

Data Access Account

with readwrite

permission to the

user account

Amazon

S3

Atuto-populates

with aws-

amazoncom

Key

https

consoleawsamazon

comiam

Microsoft

Azure

Auto-populates

with

azuremicrosoftco

m

Name of storage

account

Primary or

Secondary Access

Key

https

azuremicrosoftcom

Procedure

Related tasks

Related references

Procedure

Cloud Destination

Name

Cloud Account

Name

system

Destination

Location

Encrypted In

Transit

encrypt in transit

Procedure

ItemField for Cloud

AccountsDescription

azuremicrosoftcom

account

ItemField for Cloud

AccountsDescription

ItemField for Cloud

Procedure

Cloud Account

Name

Secret

Credential

Procedure

Cloud

Destination

Name

Cloud Account

Name

Destination

Location

Procedure

will be migrated

migrated

Adding a cloud path

Procedure

Primary EVSFile

System

5 Click OK

In Use by

Policies

migrated

Policies and

Schedules

Data Migration

Cloud Accounts

Data Migration

Paths

Related references

Procedure

extension

Access

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

Case-sensitive

pattern checks

minutes

For example

Procedure

Case-sensitive

pattern checks

Related references

Procedure

In Use by

Policies

Not in use

Rule

Definition

Procedure

ItemField for

PoliciesDescription

Primary File

System

Secondary File

System

Data MigrationRules

ItemField for

PoliciesDescription

Data MigrationPaths

as well

NDMPConfiguration

operation

Procedure

Item Description

type

Item Description

(To create

Available Cloud

Rules

the left arrow (lt)

selected rule(s)

Selected Cloud

Rules

met

(To create rules

rules

Rule Statement

Connection Errors

Procedure

Item Description

migration) policy

Item Description

Pre-Conditions

the left arrow (lt)

selected rule(s)

(To create rules

rules

Procedure

Data Migration

Policy

Date and Time

to Start

Procedure

Data Modify

Policy

Data Migration

Type

Item Description

Policy Policy name

select report

Item Description

Policies and

Schedules

Item Description

Report Summary

Item Description

Pre-Migration File

System Space Used

migration

Post-Migration File

System Space Used

File System

Capacity

Live File System

Reclaimed

snapshots

Total File System

Reclaimed

snapshots

Scenario 3

Scenario 1 and 2

All Scenarios

Conclusion

(decrease)

Virtualization

Migration

Procedure

Options

--json|-j

Target file system

Name of association

-s --start

-m --migrate

-p --pause

-r --resume

EXAMPLES

APPLIES TO

EVS

Options

--port ltportgt

Target file system

Legacy NAS path URI

EXAMPLES

APPLIES TO

EVS

Options

Target file system

--force

-c --confirm

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-l --list-failed

-r --retry

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-e --journal-enable

-m --email-logs

Sends logs by email

-u --delete-logs

Deletes logs

-c --confirm

EXAMPLES

APPLIES TO

EVS

Options

Target file system

EXAMPLES

APPLIES TO

EVS

Options

Target file system

-a --all

All file systems

EXAMPLES

APPLIES TO

EVS

Options

--port ltportgt

-f --force

-s --source

Legacy NAS path URI

EXAMPLES

APPLIES TO

EVS

Options

-a --all

-w --work

-r --reset

Reset statistics

-g --graph

APPLIES TO

EVS

Control via SMU GUI

Rules syntax

Keywords

Connectors

Conditionals

Statement order

Keyword Value(s)

Usage

For example

Keyword Value(s)

Usage

For example

Usage

For example

Usage

For example

ltOLDER_THAN 28gt

Keyword Value(s)

Usage

For example

ltNEWER_THAN 14gt

Usage

For example

Usage

For example

Usage

For example

Usage

For example

ltCHANGED_SINCE 7gt

Rule Description

Rule scenario A

EXCLUDE

Rule scenario B

s3amazonawscom

Single Node

Interface IP

SMU eth0 172101011

Cluster

Interface IP

SMU eth0 172101011

ipaddr -p eth1 -I 19216843116 -m 2552552480

dnsserver add 1921684510 1921684511

s3amazonawscom

Single Node

Interface IP

SMU eth0 172101011

Cluster

Interface IP

SMU eth0 172101011

ipaddr -p eth1 -I 19216843116 -m 2552552480

dnsserver add 1921684510 1921684511

For example

MK-92HNAS005-07

Contents
Preface
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        Migration schedules
        
        
        
        
        
        
        
        
        
        
        Cloud providers
        
        
        
        
        
        
        
        
        
        Adding a cloud path
        
        
        
        
        
        
        
        
        Migration schedules
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        Rules syntax
        
        Keywords
        
        Connectors
        
        Conditionals
        
        Statement order

Date post:	24-Dec-2021
Category:	Documents
Upload:	others
View:	11 times
Download:	1 times

Data Migrator Administration Guide

Documents