How it Works
Qlogic
Loading...
Data Migration Service
User Manual
162 pgs3.58 Mb0

Qlogic Data Migration Service User Manual

Download
Page 1
Data Migration Service
for HP StorageWorks MPX200
User’s Guide
ISR654606-00 A
Page 2
Data Migration Service for HP StorageWorks MPX200 User’s Guide
Document Revision History
Revision A, November 16, 2009
Changes Sections Affected
Initial release of new user’s guide. All
ii ISR654606-00 A
Page 3
Table of Contents
Preface
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
What’s in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Related Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
License Agreements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Knowledge Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
1 Introduction
Features Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Feature Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Job Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Immediate Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Delayed Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Configure Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Serial Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Data Migration Job Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Array Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Data Migration Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Data Migration Job Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Data Migration Job States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Data Migration Job CLI Commands . . . . . . . . . . . . . . . . . . . . . . 1-7
Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
ISR654606-00 A iii
Page 4
Data Migration Service for HP StorageWorks MPX200 User’s Guide
2 Getting Started
Supported Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Supported Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Direct Attach Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Fabric Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Supported Fibre Channel Fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Supported Storage Arrays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
High Availability and Redundant Configurations . . . . . . . . . . . . . . . . . 2-4
Choosing the Right DMS Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Hardware and Software Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Hardware Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Software Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
3 Using DMS
General Steps for Data Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Setting Array Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Setting Array Properties in the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Setting the Array Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Setting Array Properties in the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Creating a Data Migration Job Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Creating a Data Migration Job Group in the GUI. . . . . . . . . . . . . . . . . 3-6
Creating a Data Migration Job Group in the CLI . . . . . . . . . . . . . . . . . 3-7
Using the Data Migration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Starting the Data Migration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Scheduling an Individual Data Migration Job in the GUI . . . . . . . . . . . 3-8
Scheduling an Individual Data Migration Job in the CLI . . . . . . . . . . . 3-11
Scheduling Data Migration Jobs in Batch Mode . . . . . . . . . . . . . . . . . 3-15
Starting Serial Scheduled Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Viewing the Status of Data Migration Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Viewing Data Job Migration Jobs Status in the GUI . . . . . . . . . . . . . . 3-19
Viewing Data Job Migration Jobs Status in the CLI. . . . . . . . . . . . . . . 3-20
Rescanning Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Viewing Job Details and Controlling Job Actions . . . . . . . . . . . . . . . . . . . . . 3-23
Viewing Job Details and Controlling Job Actions in the GUI . . . . . . . . 3-23
Viewing Job Details and Controlling Job Actions in the CLI . . . . . . . . 3-25
Viewing System and Data Migration Job Logs. . . . . . . . . . . . . . . . . . . . . . . 3-27
Viewing Logs in the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Viewing Logs in the CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
iv ISR654606-00 A
Page 5
Using the Verify Migration Job Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Starting the Verify Migration Job Wizard . . . . . . . . . . . . . . . . . . . . . . . 3-33
Scheduling Verification of Job Options . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Acknowledging a Data Migration Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Removing an Offline Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
4 Data Migration Licenses
Types of Data Migration Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Capacity-based Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Array-based Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Installing a Data Migration License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Installing a Data Migration License Key in the GUI . . . . . . . . . . . . . . . 4-2
Installing a Data Migration License Key in the CLI . . . . . . . . . . . . . . . 4-4
Applying an Array-based License to a Specific Array . . . . . . . . . . . . . . . . . 4-5
Applying an Array-based License to a Specific Array in the GUI . . . . 4-5
Applying an Array-based License to a Specific Array in the CLI . . . . . 4-7
Viewing Data Migration License Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Viewing Data Migration License Usage in the GUI . . . . . . . . . . . . . . . 4-8
Viewing Data Migration License Usage in the CLI . . . . . . . . . . . . . . . 4-9
Data Migration Service for HP StorageWorks MPX200
User’s Guide
5 Command Line Interface
User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
User Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Admin Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Miguser Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
set system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
set features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
set fc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
set array. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
set VPGroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
migration_group add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
migration_group remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
migration_group edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
migration add. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
migration rm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
migration stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
migration start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
migration pause. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
migration resume. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
ISR654606-00 A v
Page 6
Data Migration Service for HP StorageWorks MPX200 User’s Guide
migration acknowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
start_serial_jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
compare_luns add. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
compare_luns rm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
compare_luns stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
compare_luns start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
compare_luns pause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
compare_luns resume. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
compare_luns acknowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
show fc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
show migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
show array. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
show luninfo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
show migration_luninfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
show migration_params . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
show mgmt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43
show memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
show properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45
show migration_usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
show perf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-47
show perf byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
show features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49
show migration_logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
show logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
show luns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52
show targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
show vpgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55
target rescan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
save capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57
array rm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58
array_licensed_port rm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59
readjust_priority. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60
show compare_luns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61
6 Performance
Performance Factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Maximizing Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Optimal Configuration and Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
vi ISR654606-00 A
Page 7
Data Migration Service for HP StorageWorks MPX200
User’s Guide
7 Using the HP MSA2012fc Storage Array
MSA2012fc Array Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Using Array-based Licenses for MSA2012fc Array . . . . . . . . . . . . . . . . . . . 7-1
Workaround for Using a Single Array License for MSA2012fc. . . . . . . . . . . 7-2
8 Restrictions
Reconfiguring LUNs on a Storage Array . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Removing an Array After Completing Data Migration Jobs . . . . . . . . . . . . . 8-1
A Troubleshooting
Glossary
Index
List of Figures
Figure Page
2-1 Single and Dual Blade Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2-2 Single and Dual Blade High Availability Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2-3 Migration Between Dissimilar Vendor SANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
3-1 Setting Array Properties: Target Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3-2 Setting Array Bandwidth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3-3 Migration Schedule Options: Individual Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
3-4 Create Data Migration Job: Individual Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3-5 Data Migration Jobs Options: Individual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
3-6 Migration Schedule Options: Batch Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
3-7 Create Data Migration Job: Batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
3-8 Data Migration Jobs Options: Batch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
3-9 Serial Data Migration Jobs Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
3-10 Active Data Migration Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
3-11 Viewing Migration Job Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
3-12 mpx Log: System Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
3-13 mpx Log: Migration Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
3-14 Verify Migration Job Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
3-15 Verifying Jobs Options Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
4-1 Features Page: License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4-2 New License Key Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4-3 Add License Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4-4 License Array Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4-5 Information Page Showing Array is Licensed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4-6 Data Migration Info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
6-1 Topology Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
ISR654606-00 A vii
Page 8
Data Migration Service for HP StorageWorks MPX200 User’s Guide
List of Tables
Table Page
1-1 Data Migration Job States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
2-1 Migration Rates for Single and Dual Blade Configurations . . . . . . . . . . . . . . . . . . . 2-2
2-2 Migration Rates for Single Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2-3 Supported Storage Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
5-1 CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
A-1 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
viii ISR654606-00 A
Page 9
Preface
Data Migration Service (DMS) is a new block level, offline data migration service introduced in the HP StorageWorks MPX200 Multifunction Router (MPX200) data transport device. The HP StorageWorks mpx Manager software is designed to simplify data migration jobs for minimum downtime, while providing protection against common user errors.
Intended Audience
This guide is intended for end users responsible for administration of data migration services using the HP StorageWorks MPX200 Multifunction Router.
What’s in This Guide
This preface provides a general overview of DMS and the HP StorageWorks mpx Manager software, and covers the intended audience, related materials, document conventions, and contact information for technical support.
The remainder of this guide is organized into the following chapters and appendices:
1 Introduction lists the DMS and HP StorageWorks mpx Manager features at
both a high level and in detail.
2 Getting Started describes the direct attached and fabric configurations,
and lists the supported fabric and array types; provides recommendations for high availability and redundant configurations, guidelines for choosing DMS options, and a few general precautions for DMS usage; describes hardware and software setup; and shows how to switch to switch to DMS mode in both the GUI and CLI.
3 Using DMS provides detailed procedures for using DMS in both the HP
StorageWorks mpx Manager graphical user interface (GUI) mode and the command line interface (CLI) mode.
4 Data Migration Licenses describes the two types of migration licenses and
provides instructions for license key installation.
5 Command Line Interface provides information on using the command line
interface (CLI) for data migration services. It defines the guest account and the user sessions: admin and miguser. In addition, for each command, it provides a description, the required session type, and an example.
ISR654606-00 A ix
Page 10
Preface Related Materials
6 Performance describes the factors affecting DMS performance and offers
suggestions for obtaining maximum performance.
7 Using the HP MSA2012fc Storage Array offers several considerations for
using the HP Modular Storage Array 2012fc (MSA2012fc), including array behavior and licensing concerns.
8 Restrictions details the restrictions that apply to the DMS when
reconfiguring logical unit numbers (LUNs) on a storage array and removing an array after completing data migration jobs.
Appendix A Troubleshooting lists some problems that may occur with DMS
and offers a possible reason or solution for each.
Following the appendix are a glossary of terms and acronyms used, and an index that will help you quickly find the information you need.
Related Materials
For additional information, refer to these related documents from QLogic:
Data Migration Service for HP StorageWorks MX200 Planning Guide
iSR6140 Quick Start Guide
iSR6140 Router Manager User’s Guide
iSR6140 Command Line Interface (CLI) User’s Guide
Documentation Conventions
This guide uses the following documentation conventions:
NOTE: provides additional information.
Text in blue font indicates a hyperlink (jump) to a figure, table, or section in
this guide, and links to Web sites are shown in underlined blue. For example:
Table 1-1 lists the possible data migration job states.
For details, see “Starting Serial Scheduled Jobs” on page 4-23.
For more information, visit www.qlogic.com
Text in bold font indicates user interface elements such as a menu items,
buttons, check boxes, or column headings. For example:
On the Wizards menu, click License an Array.
.
In the Migration Schedule Options dialog box, click Schedule
individual job, and then click OK.
Under Scheduling Type, select Serial Schedule Jobs.
x ISR654606-00 A
Page 11
Preface
License Agreements
Text in Courier font indicates a file name, directory path, or command line
text; and text in Courier Bold font indicates user input. For example:
Please select a Migration Job Id from the list above: 0
miguser start -p migration
Key names and key strokes are indicated with
Press
Press the
Text in italics indicates terms, emphasis, variables, or document titles. For
example:
For a complete listing of license agreements, refer to the QLogic
Software End User License Agreement.
A job group allows better management of data migration jobs.
In the left pane, click mpx MPX200:<IP address>.
CTRL+P.
UP ARROW
License Agreements
Refer to the QLogic Software End User License Agreement for a complete listing of all license agreements affecting this product.
Technical Support
Customers should contact their authorized maintenance provider for technical support of their QLogic switch products. QLogic-direct customers may contact QLogic Technical Support; others will be redirected to their authorized maintenance provider.
key.
UPPERCASE
:
Visit the QLogic support Web site listed in Contact Information for the latest firmware and software updates.
Availability
QLogic Technical Support for products under warranty is available during local standard working hours excluding QLogic Observed Holidays.
Training
QLogic offers training for technical professionals for all iSCSI, InfiniBand, and Fibre Channel products. From the main QLogic Web page at www.qlogic.com click the Education and Resources tab at the top, and then click the Education & Training tab on the left. The QLogic Global Training Portal offers online courses, certification exams, and scheduling of in-person training.
ISR654606-00 A xi
,
Page 12
Preface Technical Support
Technical Certification courses include installation, maintenance and troubleshooting QLogic SAN products. Upon demonstrating knowledge using live equipment, QLogic awards a certificate identifying the student as a Certified Professional. The training professionals at QLogic may be reached by e-mail at
training@qlogic.com
Contact Information
Please feel free to contact your QLogic approved reseller or QLogic Technical Support at any phase of integration for assistance. QLogic Technical Support can be reached by the following methods:
Web http://support.qlogic.com
E-mail support@qlogic.com
Knowledge Database
The QLogic knowledge database is an extensive collection of QLogic product information that you can search for specific solutions. We are constantly adding to the collection of information in our database to provide answers to your most urgent questions. Access the database from the QLogic Support Center:
http://support.qlogic.com
.
.
xii ISR654606-00 A
Page 13
1 Introduction
Data Migration Service (DMS) is a new block level, offline data migration service introduced in the HP StorageWorks MPX200 Multifunction Router (MPX200) data transport device. The HP StorageWorks mpx Manager software is designed to simplify data migration jobs for minimum downtime, while providing protection against common user errors.
This chapter provides a high-level Features Overview, and also details of each of the following features:
“Job Scheduling” on page 1-3 “Data Migration Job Groups” on page 1-4 “Array Properties” on page 1-4 “Protection” on page 1-6 “Data Migration Jobs” on page 1-6 “Logs” on page 1-8 “Users” on page 1-8
Features Overview
The Data Migration Service technology deployed on the MPX200 with the HP StorageWorks MPX200 Multifunction Router software has following features:
Fibre Channel SAN vendor independent: The MPX200 supports
Brocade StorageWorks mpx Manager allows data migration across multi-vendor fabrics.
Heterogeneous array support: HP StorageWorks mpx Manager supports
data migration across heterogeneous arrays (arrays manufactured by different vendors). For a list of the storage array types for which DMS currently provides support, see “Supported Storage Arrays” on page 2-4.
Ease of use: HP StorageWorks mpx Manager is designed to be extremely
simple to use. The graphical user interface (GUI) and command line interface (CLI) provide many wizard-based operations and user-level protection.
ISR654606-00 A 1-1
®
/McDATA®, Cisco®, and QLogic Fibre Channel fabrics. HP
Page 14
1–Introduction Feature Details
Data security and sanity: HP StorageWorks mpx Manager provides
features to classify a storage array as “source only,” making it impossible to write data to that array and thus minimizing the chances of data corruption. It also provides a Verify Migration Job wizard to compare data on the source LUN with that on the destination LUN to indicate that the data copy occurred without any data loss or corruption.
Migration job scheduling: Data migration may be disruptive to
business-critical applications; therefore, minimizing application downtime is very important. DMS provides several job scheduling options, including the Configure Only option, which allows you to complete the time-consuming task of configuring data migration jobs without requiring any downtime. The different I/O size capabilities for migration jobs enables you to tune the storage array’s performance during sequential read/write operations. The Load Balancing option is also very useful when dealing with older-generation, lower-speed arrays (such as 2Gb and 4Gb Fibre Channel) being migrated to higher speed (4Gb and 8Gb Fibre Channel) arrays using higher-speed (4Gb and 8Gb) Fibre Channel switches.
Data migration service logs: DMS logs are maintained separately from the
system logs. DMS logs are designed to help the service professional maintain a full, detailed history of each job performed, and can be submitted as a part of the migration report to the customer.
Logging and troubleshooting: System logs are designed to store a
significant number of details that can be used for debugging and troubleshooting. The save capture command (see “save capture” on
page 5-57) helps to capture the configuration details, system logs, and
MPX200 state at any time, and can be used for troubleshooting if the need arises.
Licensing: DMS licenses provide capacity- (per TB) and array-based
licenses. For more information, see 4 Data Migration Licenses.
Feature Details
This section describes the features of the Data Migration Service. Because the current DMS is an offline-only service, it is assumed that when a data migration job for the specified LUN starts, applications (Microsoft Applications, and other applications that are using the source LUNs for data storage) and server access to the LUN is blocked. You do not need to bring down these applications during the initial setup and configuration of DMS. DMS minimizes the downtime by allowing the complete setup and configuration of data migration jobs (except for immediate scheduling of the jobs) without bringing down the other applications. The application and server must be offline only during the actual data migration.
®
Exchange, Oracle®
1-2 ISR654606-00 A
Page 15
Job Scheduling
HP StorageWorks mpx Manager provides multiple data migration job scheduling options to optimize bandwidth and provide maximum usage of SAN resources. It provides a priority-based serial scheduling feature that enables you to line up migration jobs and execute them in serial or parallel fashion, based on available resources.
You can schedule data migration jobs for execution in the following three ways:
Immediate Schedule (start now) Delayed Schedule (start at a later time within the next 30 days) Serial Schedule (priority-based scheduling)
Immediate Schedule
Use the Immediate Schedule option to schedule a data migration job to instantly start data migration. You must ensure that both the source and destination LUNs are not being accessed by any application when this option is selected.
Delayed Schedule
Use the Delayed Schedule option to schedule a data migration job to start at a later time. When you select this option during configuration of a migration job, you are requested to enter the start time. This allows you to configure a migration job during normal business hours and perform actual data migration during off peak hours, so that the application remains down only for a short period of time and during the off peak hours.
1–Introduction
Feature Details
Configure Only
The Configure Only option enables you to configure migrations jobs without a specified start time. With this option, you must start the migration jobs when system downtime begins. This option is very useful when the exact downtime of the application is not known. Use this option when you need to configure all migration jobs without requiring any application downtime.
Serial Schedule
The Serial Schedule option is designed to provide maximum flexibility for data migration. Even though DMS supports 256 simultaneous migration jobs, typical array performance can be maximized by having only 4 to 8 LUNs under migration. Serial scheduling of the job allows configuration of all 256 jobs at the same time, while having fewer active jobs at a time.
ISR654606-00 A 1-3
Page 16
1–Introduction Feature Details
Serial scheduling allows you to configure migration jobs that can have the same or different priority. If you need to configure a large number of jobs (256, for example), you can configure them in batches such that the first four to eight jobs are scheduled at priority 1, the next four to eight jobs at priority 2, and so on. This scheduling arrangement ensures that when the serial schedule starts, no more than four to eight jobs are running simultaneously, and DMS can provide better performance.
In order to achieve this, serial scheduling requires a job priority for each data migration job. Multiple data migration jobs can have the same priority. Migration jobs with the same priority are run together. Job priority 1 is highest and job priority 255 is lowest. After all the jobs are configured for serial execution, you must schedule this batch of serially-scheduled jobs. The batch can be started immediately or at a later time. The Serial Data Migration Jobs Options dialog box provides an easy way to start or schedule the batch.
After the serial batch starts to run, all jobs having the highest priority are completed before the jobs scheduled at the next priority level start to execute.
Only one serial schedule can be active at any time.
Data Migration Job Groups
The mpx Manager uses the concept of job groups to associate data migration jobs with user-defined groups. A job group allows better management of data migration jobs. You can create a maximum of eight job groups. The mpx Manager also has commands to remove and edit job groups.
The groups can be classified for data migration jobs related to application type or server class. For example, a data migration job related to the Microsoft Exchange application could be part of group named “Exchange,” and a data migration job related to a payroll application could be part of group named “Payroll.” The data migration jobs are tracked separately within each group. You can schedule the data migration of all LUNs related to one application, followed by other applications.
If no group is defined, all jobs are assigned to the default group, Group 0. You cannot delete Group 0.
Array Properties
DMS discovers the Fibre Channel target ports and forms an array when at least one data LUN is presented to the DMS running in the MPX200 from that array. If no data LUN is presented to the MPX200, all array ports are shown in the mpx Manager GUI and CLI as target ports. After the LUNs are presented to the MPX200, a target rescan is required to form an array (see “target rescan” on
page 5-56).
1-4 ISR654606-00 A
Page 17
1–Introduction
Feature Details
DMS classifies the discovered storage array controllers into two categories: targets and arrays. All array controller ports are initially identified as targets by the MPX200. After a single data LUN is detected on the target, DMS forms an entity called an array. A specific LUN seen through multiple Fibre Channel target ports are grouped under a single array.
Configure the array entity created by the DMS for the following attributes:
Symbolic name: Upon forming an array, the HP StorageWorks MPX200
Multifunction Router automatically assigns a symbolic name to an array. QLogic highly recommends that the you assign a more meaningful name to an array because the migration logs identify the source and destination LUNs with the symbolic names of the source and destination arrays.
Array type: DMS requires the classification of each array as either Source,
Destination, or Source+Destination. During the creation of migration jobs,
the Data Migration wizard restricts the assignment of a source LUN only from arrays that have an attribute Source and assignment of a destination LUN only from the arrays with attribute Destination. Use the array attribute Source+Destination only when you need to create copies of a LUN on the same array.
Select the array type attribute None to exclude the storage array from participating in data migration. The MPX200 simultaneously supports both iSCSI connectivity and data migration service. Typically, you would use the “None” attribute when the MPX200 is used to provide only iSCSI connectivity for that storage array.
Array bandwidth: This feature is applied only to a source array. This value
indicates the maximum bandwidth available from the array for a data migration task. The bandwidth is computed over all paths. The MPX200 uses only the user-assigned array bandwidth to migrate the data. This allows other applications and servers using the same source array to continue to perform at an acceptable performance level.
Load Balancing: The MPX200 detects all available multiple active and
passive paths to the LUN. Load balancing balances the load for migration jobs over multiple active paths, thus improving the migration rate. Load balancing should be disabled only in case of trouble performing data migration.
ISR654606-00 A 1-5
Page 18
1–Introduction Feature Details
Protection
DMS provides data protection against some of the common user errors by enforcing the following restrictions:
An array must have an attribute of either Source, Destination, or
Source+Destination to participate in the migration. When you configure a data migration job, Source LUNs can be assigned only from an array with the attribute Source (or (Source+Destination), and Destination LUNs can be assigned only from an array with the attribute Destination (or Source+Destination). Use these attributes properly to avoid errors.
A user acknowledgement is required for a data migration job after the job is
completed. This feature provides better accounting and record-keeping for the job. The data migration log indicates when the job was completed and when you acknowledge the completion status of the job.
After a LUN is configured as a Destination LUN for a specific data migration
job, the LUN cannot be configured for a different job until the current job is completed and you acknowledge or remove the job.
DMS detects the normal configuration of partitions on the data LUN. Before
fully configuring a data migration job, DMS provides a warning if it detects valid partition tables on the destination LUN.
Data Migration Jobs
DMS manages the data migration processes in terms of data migration jobs. A maximum of 256 jobs can be scheduled to run at any time.
Data Migration Job Attributes
Configure a data migration job for the following attributes:
Source and Destination LUN: You can configure a single source LUN to
migrate to one or multiple destination LUNs. Any specified destination LUN can be part of a single data migration job.
Job groups: For better manageability, you can configure data migration
jobs to belong to a specific, user-defined job group. By default, a job is assigned to a default group, Group 0.
Scheduling: You can configure data migration jobs to start immediately, to
start at a specified time, to have no start time (configure only), or to use a priority-based serial scheduling. For details, see the “Scheduling...” sections under “Using the Data Migration Wizard” on page 3-7.
I/O size: You can configure each data migration job to migrate data using a
specified I/O size. Different types of arrays and LUNs may provide optimum performance based on the I/O size. The default size is 64K.
1-6 ISR654606-00 A
Page 19
The Data Migration wizard enables you to configure multiple jobs in a batch mode. The jobs configured in batch mode have the same common attributes. For more details, see “Using the Data Migration Wizard” on page 3-7.
Data Migration Job States
Table 1-1 lists the possible data migration job states.
Job State Description
Running Job is currently running. You can pause or stop a running job.
Scheduled Job is waiting to be run.
Completed Job is complete. You must acknowledge a completed job.
Paused A running job has been interrupted.
Stopped A running, scheduled, failed, or pending job has been halted. You can
1–Introduction
Feature Details
Table 1-1. Data Migration Job States
restart or remove a job in the Stopped state.
Failed
Pending A job configured for a delayed start (either due to Delayed Scheduling
The
MPX200 lost access to the LUN during a data migration job, caus-
ing it to fail.
or Serial Scheduling) cannot start at the specified time because the source or destination LUN is offline. When the LUN becomes online, the job will go into the Running state. If you determine that the specified LUN will never come back online, you can remove the pending job.
Data Migration Job CLI Commands
DMS provides CLI commands (migration stop/start/pause/resume) to alter the state of the migration job. The migration stop/start command causes a job to be stopped and then restarted from the beginning. The migration stop command rewinds the job to the beginning.
You can use the migration pause/resume commands only on running jobs. The migration pause command causes the job to halt temporarily. The migration resume command causes the job to resume from the point where it was paused; it will not start from the beginning of the LUN. Pause a migration job if it is taking a lot of array bandwidth and causing other processes on the array to slow down. You can later resume the job when the I/O activity on the array is reduced.
ISR654606-00 A 1-7
Page 20
1–Introduction Feature Details
Logs
Users
DMS manages the following two log types:
Migration logs: Migration logs provide a detailed history of each data
migration job. The job history contains information such as the start and end time of the job, source and destination LUNs and arrays, size of the job, total time consumed for the job, and so on. Using the HP StorageWorks mpx Manager GUI, you can export the migration logs out of the MPX200. You can open this file with a spreadsheet application such as Microsoft Excel and use it as a data migration task report. QLogic highly recommends that you save migration logs after the data migration job is completed and cleared from the MPX200. This provides a record of every data migration job and makes it easier to differentiate between them.
System logs: System logs primarily record events, errors, and configuration
changes, and can be used for troubleshooting.
The MPX200 supports two types of users:
Administrative user: For managing the MPX200, you must be in an
administrative session. The default password for the administrator is config.
Data migration user (“miguser”): This user session is required to
configure migration-related activities. The default password is migration. For all DSM functions, you must run a miguser session.
1-8 ISR654606-00 A
Page 21
2 Getting Started
Single Blade
Dual Blade
This chapter helps you get started using Data Migration Service with the MPX200 and HP StorageWorks mpx Manager by describing the supported configurations, some “best practices” recommendations, and hardware and software setup.
Supported Configurations
This section describes and illustrates the supported topologies (direct attach and fabric), and lists the supported fabric and array types.
Supported Topologies
Supported topologies include direct attach configuration and fabric configuration, described in this section.
Direct Attach Configuration
Figure 2-1 shows a direct attach configuration with a single blade or dual blade
MPX200.
Figure 2-1 Single and Dual Blade Configuration
Table 2-1 shows the migration rates that can be achieved for single and dual
blades, depending on the bandwidth capability of the storage array.
ISR654606-00 A 2-1
Page 22
2–Getting Started
Single Blade
Dual Blade
Supported Configurations
Table 2-1. Migration Rates for Single and Dual Blade Configurations
Array Type Single Blade Dual Blade
2Gb Fibre Channel 700 GB/hour 1 TB/hour
4Gb Fibre Channel 1.25 TB/hour 2.5 TB/hour
8Gb Fibre Channel 2 TB/hour 4 TB/hour
Fabric Configuration
Figure 2-2 shows typical setup for data migration with a dual fabric high
availability (HA) configuration with both array controller ports and one port from each MPX200 blade connected to each fabric. This configuration enables the MPX200 to perform load balancing.
Figure 2-2 Single and Dual Blade High Availability Setup
Table 2-1 shows the migration rates that can be achieved for a single blade,
depending on the bandwidth capability of the storage array.
2-2 ISR654606-00 A
Page 23
2–Getting Started
Supported Configurations
Table 2-2. Migration Rates for Single Configuration
Source or
Destination Array
2Gb Fibre Channel 4Gb 1.25 TB/hour 2.5 TB/hour
4Gb Fibre Channel 8Gb 2.5 TB/hour 4 TB/hour
8Gb Fibre Channel 8Gb 4 TB/hour 4 TB/hour
Figure 2-3 shows the configuration used when you are:
Migrating from one vendor SAN to another vendor SAN.
Installing a new fabric and do not have enough ports available in the new
fabric.
This configuration provides data migration rates similar to the direct attach configuration (see page 2-1).
Fibre
Channel
Fabric
One Port per Array
Controller
Connected to Each
Fabric
Two Ports per
Array Controller
Connected to Each
Fabric
Figure 2-3 Migration Between Dissimilar Vendor SANs
Supported Fibre Channel Fabrics
DMS is currently supported with Brocade/McDATA, Cisco, and QLogic 2Gb, 4Gb, and 8Gb Fibre Channel fabrics.
Supported Storage Arrays
Table 2-3 lists the storage array types for which DMS currently provides support.
ISR654606-00 A 2-3
Page 24
2–Getting Started Best Practices
Table 2-3. Supported Storage Arrays
Vendor Storage Array
®
EMC
CLARiiON® CX family
®
CLARiiON
Symmetrix
AX family
®
DMX family
Hitachi Data Systems
(HDS)
Hewlett-Packard® (HP)
®
IBM
NEC D-Series SAN Storage arrays
Xiotech
®
Thunder 95xx V series
Lightning 99xx V series
Attachable Modular Storage (AMS) family
Workgroup Modular Storage (WMS) family
Universal Storage Platform (USP) family
HP StorageWorks Modular Storage Array (MSA) family
HP StorageWorks Enterprise Virtual Array (EVA) family
HP StorageWorks XP Disk Arrays family
System Storage DS3000 family
System Storage DS4000 family
System Storage DS5000 family
System Storage DS6000 family
System Storage DS8000 family
Emprise™ Storage family
®
Magnitude 3D
4000 family
Best Practices
This sections provides some “best practices” recommendations for DMS usage.
High Availability and Redundant Configurations
The following recommendations pertain to high availability (HA) and redundant configurations:
The MPX200 is capable of detecting and performing load balancing over
multiple paths. To achieve the highest data migration rates, zone multiple ports from each array controller with each port of the MPX200.
2-4 ISR654606-00 A
Page 25
To maximize performance, zone each MPX200 Fibre Channel port with one
or two ports from one of the array controllers.
To optimize performance, QLogic recommends that LUNs under migration
are balanced across two controllers of a storage array.
Choosing the Right DMS Options
Follow these guidelines when choosing DMS options:
Use the Configure Only option to configure migration jobs while applications
are still online. Then, start the migration jobs as soon as the server offline notification is received from the system administrator.
To get optimum MPX200 performance, schedule a maximum of eight jobs to
run simultaneously.
To sequentially run migration jobs, use the Serial Scheduling feature, which
allows the migration jobs to start automatically after the jobs with previous priority values are completed; no user intervention is required. Serial scheduling helps ensure optimum bandwidth usage without filling up array I/O queues, which may occur if jobs run simultaneously.
2–Getting Started
Best Practices
Use the array bandwidth feature when applications are still using different
LUNs of the array while DMS is migrating the data. This ensures that the MPX200 uses limited array bandwidth for the data migration and does not impact application performance during data migration.
General Precautions
Note the following general precautions:
Make sure that hosts connected to source and destination LUNs are either
zoned out completely, or that LUN masking is changed appropriately such that the LUNs being migrated are not touched by any host other than the MPX200 until the migration is complete.
In high availability (HA) configurations where the LUNs are visible from both
MPX200 ports, make sure that both ports from each MPX200 blade are configured under a single host or host group entity in the array management software. This configuration ensures that all MPX200 ports from the same virtual port group (VP group) see the same set of LUNs as having the same LUN ID. Failing to follow this configuration can lead to unpredictable or erroneous behavior.
For a dual blade configuration for the MPX200, add the same VP group WWPNs from both blades as one host entry. If you need to migrate more than 255 LUNs, you may create additional host entries in the array using WWPNs from additional VP groups in the MPX200.
ISR654606-00 A 2-5
Page 26
2–Getting Started Hardware and Software Setup
Migration logs require the following handling:
Always clear migration logs at the start of the project.
Export migration logs onto your system after the project completes.
Migration logs wrap after 1,024 migration log entries.
If the source array controllers are configured in redundant fabrics, configure
one MPX200 port into Fabric A and the second port into Fabric B.
When using the serial scheduling feature, configure similar size jobs with the
same priority.
Array reconfiguration precautions include the following:
If the LUN presentation from the array to the MPX200 is changed, click
Wait for a few seconds between retries because the MPX200 will be
Remove unused arrays for the following reasons:
the Refresh button two or three times to see the changes.
running the discovery process.
The maximum number of arrays configured at any time is 7.
Arrays stored in persistence consume resources even if the array is
offline and no longer needed.
After the migration is complete, QLogic recommends that you remove
the arrays.
If the array-based license was used and the array will not be used in
the next project, remove the license for this array.
Array-based license use requires the following precautions:
If you reconfigure a removed array, it may require a new array-based
license.
You can use a maximum of 32 array-based licenses at any time.
Use an array-based license if you require an ongoing replications of
LUNs for the array.
Hardware and Software Setup
Follow the procedures and guidelines in this section for setting up your hardware and software.
Hardware Setup
For information on installing your HP StorageWorks MPX200 Multifunction Router, refer to the MPX200 Hardware Installation Guide.
2-6 ISR654606-00 A
Page 27
2–Getting Started
Hardware and Software Setup
To set up the hardware for DMS:
1. To manage the MPX200, install the HP StorageWorks mpx Manager software on any computer running Windows 2003, Windows 2008, or Windows XP. The MPX200 must be accessible over the network connection from the machine on which HP StorageWorks mpx Manager is installed.
2. Set up the MPX200 management port IP address. For details, refer to the HP StorageWorks MPX200 Multifunction Router Quick Start Guide.
3. Connect the storage array (source and destination) controller ports to an Fibre Channel switch. For a high availability (HA) topology, connect the two ports of each array on two different switches.
4. Ensure that the controller ports are seen as online on the Fibre Channel switches.
5. Connect the Fibre Channel ports of the MPX200 to the Fibre Channel switches where the array controller ports are connected. For an HA topology, connect each Fibre Channel port of the MPX200 to a different Fibre Channel switch.
6. Ensure that the MPX200 Fibre Channel ports are seen as online on the Fibre Channel switches.
Software Setup
Software setup for DMS includes configuring switch zoning and LUN presentation.
Zoning: Perform zoning on the Fibre Channel switches such that array
controller ports are visible to the MPX200, and the array is able to see MPX200 Fibre Channel ports and can present LUNs to the MPX200.
LUN Presentation: Ensure the appropriate data LUNs are presented from
the storage arrays to the MPX200.
NOTE:
For HA configurations where the source or destination LUNs are visible from both MPX200 ports, make sure that both MPX200 ports are configured under a single host or host group entity in the array management software. This ensures that both MPX200 ports see the same set of LUNs as having the same LUN ID. Failure to do so can lead to unpredictable and erroneous behavior.
ISR654606-00 A 2-7
Page 28
2–Getting Started Hardware and Software Setup
Notes
2-8 ISR654606-00 A
Page 29
3 Using DMS
This chapter provides the following procedures for using DMS:
General Steps for Data Migration
“Setting Array Properties” on page 3-2
“Creating a Data Migration Job Group” on page 3-6
“Using the Data Migration Wizard” on page 3-7
“Starting Serial Scheduled Jobs” on page 3-18
“Viewing the Status of Data Migration Jobs” on page 3-19
“Rescanning Targets” on page 3-22
“Viewing Job Details and Controlling Job Actions” on page 3-23
“Viewing System and Data Migration Job Logs” on page 3-27
“Using the Verify Migration Job Wizard” on page 3-32
“Acknowledging a Data Migration Job” on page 3-36
“Removing an Offline Array” on page 3-36
General Steps for Data Migration
To perform data migration, follow these general steps:
1. Plan for data migration. For project guidelines, refer to the Data Migration Service for HP StorageWorks MX200 Planning Guide.
2. Zone the Fibre Channel ports from the HP StorageWorks MPX200 Multifunction Router with the Fibre Channel ports of the storage array.
3. Present the source LUNs and destination LUNs to the MPX200 using the array vendor’s configuration tools; for example, use Command View for HP Enterprise Storage Array (EVA) or Navisphere
4. Before beginning data migration, clear the migration logs (see “Viewing
System and Data Migration Job Logs” on page 3-27).
5. If the router fails to discover arrays, use the target rescan option (see
“Rescanning Targets” on page 3-22).
ISR654606-00 A 3-1
®
for EMC CLARiiON.
Page 30
3–Using DMS Setting Array Properties
6. If you are using an array-based license, follow the License Array wizard to
7. Set the array properties: symbolic name (optional) and target type (Source
8. Create the user-defined job groups (see “Creating a Data Migration Job
9. Configure data migration jobs (see “Using the Data Migration Wizard” on
10. Monitor your data migration jobs (see “Viewing the Status of Data Migration
11. Acknowledge completed data migration jobs (see “Acknowledging a Data
12. After the data migration project is complete, export the migration logs to your
apply the license.
or Destination) (see “Setting Array Properties” on page 3-2).
Group” on page 3-6).
page 3-7).
Jobs” on page 3-19).
Migration Job” on page 3-36).
local workstation (see “Viewing System and Data Migration Job Logs” on
page 3-27).
13. Make the array offline by zoning out the array ports from the MPX200, and then remove the array.
Setting Array Properties
The HP StorageWorks mpx Manager provides both GUI and CLI interfaces to view and edit array properties, including the bandwidth.
Setting Array Properties in the GUI
Follow these steps to set the array properties in the HP StorageWorks mpx Manager.
To set array properties in the GUI:
1. In the left pane, click FC Arrays to view all the Fibre Channel storage arrays detected by the MPX200.
2. Click the storage array you want to use as the source array.
The Information page in the right pane displays all the properties currently set for the selected array.
3. (Optional) In the Symbolic Name box, type a user-friendly array name.
4. From the Target Type list, select Source, as shown inFigure 3-1.
3-2 ISR654606-00 A
Page 31
3–Using DMS
Setting Array Properties
Figure 3-1 Setting Array Properties: Target Type
5. To save your changes, click Save.
6. In the Security Check dialog box, enter the administrative password. (The default password is migration.)
The mpx Manager displays an informative message indicating that the array properties have changed.
7. Click OK to close the message box.
8. To apply the changes and update the window before changing other array properties, click Refresh.
Setting the Array Bandwidth
After you have changed the Target Type to Source, saved your changes, and refreshed the mpx Manager (see “Setting Array Properties in the GUI” on
page 3-2), the right pane for the array shows an additional property, Array
Bandwidth. Follow the procedure in this section to change the array’s bandwidth setting for data transfers.
ISR654606-00 A 3-3
Page 32
3–Using DMS Setting Array Properties
NOTE:
To set the array bandwidth:
1. On the Information page of the selected array, click Array Bandwidth, and
2. If you select Throttle, type a value between 1 and 400 in the User Defined
Array bandwidth is only displayed and editable if the array target type is Source.
then click one of the following values:
Slow (50 MB/s) Medium (200 MB/s)
Fast (1600 MB/s)
Throttle
Bandwidth (MB/s) box. (Figure 3-2 shows an example.) By default, the
MPX200 uses all available bandwidth.
Figure 3-2 Setting Array Bandwidth
3. To save your changes, click Save.
3-4 ISR654606-00 A
Page 33
4. In the Security Check dialog box, enter the administrative password. (The default password is migration.)
The mpx Manager displays an informative message indicating that the array properties have changed.
5. Click OK to close the message box.
6. To apply the changes and update the window, click Refresh.
Setting Array Properties in the CLI
Follow these steps to change the array properties using the CLI. Note that all data migration operations are authorized only to the migration administrator session, miguser. For more information, see “Miguser Session” on page 5-2.
To set array properties in the CLI:
1. Log in to the MPX200 as guest and enter the password.
2. Open a miguser session using the following command:
3–Using DMS
Setting Array Properties
miguser start -p migration
(The default password for miguser is migration.)
3. To access the array properties, enter the following command:
set array
4. Select a target ID by entering its index number.
5. At the prompts, modify the symbolic name, target type, or array bandwidth for the source and destination arrays.
NOTE:
The DM CLI allows you to change the Bandwidth for Migration setting only if the Target Type is either Source or Src+Dest Target.
6. At the Do you want to apply array license (yes/no) prompt, enter Yes (the default is No) to apply your changes.
The following shows an example of how to change the array properties in the CLI.
MPX200 (miguser) #> set array
ISR654606-00 A 3-5
Page 34
3–Using DMS Creating a Data Migration Job Group
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
Index WWPN, PortId Symbolic Name Target Type
0 20:78:00:c0:ff:d5:9a:05, 00-00-00 HP MSA2012fc-0 Src+Dest
1 50:00:1f:e1:50:0a:e1:49, 82-07-00 HP HSV200-1 Src+Dest
2 50:06:01:60:4b:a0:35:de, 82-03-00 DGC RAID-2 Src+Dest
3 50:00:1f:e1:50:0a:37:18, 00-00-00 HP HSV210-3 Src+Dest
Please select a Target Id from the list above ('q' to quit): 0
Symbolic Name (Max = 128 characters) [HP MSA2012fc-0]
Target Type (1=SrcTarget, 2=DstTarget, 3=Src+Dest 4=None Target) [3 ]
Bandwidth for Migration (0=Array Bandwidth, 50-1600 MBps ) [0 ]
Enable Load Balancing (0=Enable, 1=Disable) [Enabled ]
Array based licensed applied.
All attribute values for that have been changed will now be saved.
Creating a Data Migration Job Group
The HP StorageWorks mpx Manager provides both GUI and CLI interfaces to create data migration job groups.
Creating a Data Migration Job Group in the GUI
Follow these steps to create a data migration job group in the HP StorageWorks mpx Manager.
To create a data migration job group in the GUI:
1. In the left pane, click the Services tab to open the Services page.
By default, the MPX200 shows Group 0 created under the Data Migration Jobs item.
2. Right-click Data Migration Jobs, and then on the shortcut menu, click Add Group.
3. In the Input dialog box, type a group name that you want to assign to administer a set of data migration jobs, and then click OK.
4. In the Security Check dialog box, type the data migration user password (default is migration), and then click OK.
3-6 ISR654606-00 A
Page 35
Using the Data Migration Wizard
Creating a Data Migration Job Group in the CLI
The data migration group name must be a minimum of 4 and a maximum of 128 alphanumeric characters. You can create a maximum of eight job groups in addition to the default job group.
To create a data migration job group in the CLI:
1. Log in to the MPX200 as guest and enter the password.
2. Open a miguser session using the following command:
miguser start -p migration
(The default password for misguser is migration.)
3. Create a migration group using the following command:
migration_group add
4. At the prompt, enter a name for the new group.
3–Using DMS
The following shows an example of how to add a migration group in the CLI.
MPX200 (miguser) #> migration_group add
Please Enter Group Name that you want to create (Min = 4 Max = 128
characters) MS_Exchg_2
Sucessfully created Group MS_Exchg_2
Using the Data Migration Wizard
The Data Migration wizard helps simplify the configuration and scheduling of both individual and batches of data migration jobs. This section contains the following information for the wizard:
“Starting the Data Migration Wizard” on page 3-7
“Scheduling an Individual Data Migration Job in the GUI” on page 3-8
“Scheduling an Individual Data Migration Job in the CLI” on page 3-11
“Scheduling Data Migration Jobs in Batch Mode” on page 3-15
Starting the Data Migration Wizard
Follow these steps to start the data migration wizard.
ISR654606-00 A 3-7
Page 36
3–Using DMS Using the Data Migration Wizard
To start the Data Migration wizard:
1. Start HP StorageWorks mpx Manager and connect to the MPX200 by providing the IP address of the
2. Start the Data Migration wizard using one of these methods:
On the Wizards menu, click Start Data Migration.
In the left pane, open the Services page, and then right-click Data
Migration Jobs.
3. Select the scheduling mode as follows:
a. In the top section of the Data Migration wizard, click Options.
b. In the Migration Schedule Options dialog box, select either Schedule
in batch mode or Schedule individual job, as shown in Figure 3-3.
c. Click OK.
MPX200.
Figure 3-3 Migration Schedule Options: Individual Job
4. Depending on your selection in the preceding step, continue with either
“Scheduling an Individual Data Migration Job in the GUI” on page 3-8 or “Scheduling Data Migration Jobs in Batch Mode” on page 3-15.
Scheduling an Individual Data Migration Job in the GUI
Follow these steps to schedule an individual data migration job in HP StorageWorks mpx Manager. (To perform this operation in the CLI instead, see
“Scheduling an Individual Data Migration Job in the CLI” on page 3-11.)
To schedule an individual data migration job in the GUI:
1. Start the Data Migration wizard by following the steps specified in “Starting
the Data Migration Wizard” on page 3-7.
2. In the Migration Schedule Options dialog box, click Schedule individual job, and then click OK.
3-8 ISR654606-00 A
Page 37
3–Using DMS
Using the Data Migration Wizard
The right pane of the Create Data Migration Job dialog box shows the type of array (Source, Destination, or Src+Dest) for each of the arrays available for configuring the data migration job.
3. Choose the appropriate Source and Destination LUN for the data migration job by dragging and dropping the LUNs from the right pane onto the Source LUN or Destination LUN for the data migration job in the left pane.
Figure 3-4 shows an example.
Figure 3-4 Create Data Migration Job: Individual Job
4. To save your migration job and assign job attributes, click Schedule. Or, to abandon your changes, click Close.
ISR654606-00 A 3-9
Page 38
3–Using DMS Using the Data Migration Wizard
NOTE:
The mpx Manager does not allow you to drag a LUN from an array
If you attempt to drop a Source LUN from the right pane onto a
5. In the Data Migration Jobs Options dialog box (see Figure 3-5), specify the job attributes as follows:
a. Under Scheduling Type, select one of the following:
Click Start Now to start the job immediately.
Click Schedule for Later, and then enter a Start Time and Start
of Source type in the right pane and drop it onto the Destination LUN in the left pane. However, if the array type is Src+Dest, you can drop the LUN from that array onto either a Source LUN or Destination LUN in the left pane.
Destination LUN of a smaller size in the left pane, an error
message appears.
Date.
Click Serial Schedule Jobs, and then assign a priority (1–256)
in the Job Priority box, where a lower value indicates that the job is scheduled earlier than jobs configured with higher values. For details on Serial Schedule Jobs, see “Starting Serial
Scheduled Jobs” on page 3-18.
Click Configure Only to configure the migration job without any
start time or priority. You may start this job at a later time. (To start the job, select it, and then click Start. Or, from the active job pane, right-click the job, and then click Start.)
b. In the Job Description box, enter a user-defined name to describe
this data migration job.
c. In the Group Name box, select a job group name from the list. The
group name makes it easier to view the job status on a group basis.
d. In the IO Size box, either select one of the default I/O sizes, or enter a
custom value.
3-10 ISR654606-00 A
Page 39
3–Using DMS
Using the Data Migration Wizard
Figure 3-5 Data Migration Jobs Options: Individual
6. To save the data migration job options, click Apply. Or to abandon changes to this data migration job, click Cancel.
Scheduling an Individual Data Migration Job in the CLI
Follow these steps to schedule an individual data migration job in the CLI. (To perform this operation in the mpx Manager instead, see “Scheduling an Individual
Data Migration Job in the GUI” on page 3-8.)
To schedule an individual data migration job in the CLI:
1. Log in to the MPX200 as guest and enter the password.
2. Open a miguser session using the following command:
miguser start -p migration
(The default password for misguser is migration.)
3. To create a migration job, enter the following command:
migration add
4. Every migration job is defined by a Source LUN and a Destination LUN. The CLI lists the source arrays that you have previously defined and prompts you to select one.
5. From the selected source array, the CLI lists the LUNs that have been exposed to the MPX200 for migration, and prompts you to select one LUN.
ISR654606-00 A 3-11
Page 40
3–Using DMS Using the Data Migration Wizard
6. The CLI lists the destination arrays that you have previously defined, and prompts you to select one.
7. From the selected destination array, the CLI lists the LUNs that have been exposed to the MPX200 for migration, and prompts you to select one LUN.
The destination LUN you select should not be a part of any other job, and its size should be equal to or greater than the source LUN.
The MPX200 warns you if it detects any valid metadata on the destination LUN. However, you can continue and use the LUN for migration if you are aware of the consequences and want to continue with the job scheduling.
8. At the prompts, specify the I/O size, job name, migration group, and scheduling type.
a. Enter an I/O size between 32K and 1 MB to optimize migration
performance based on the storage array under consideration.
b. (Optional) Enter a job name (maximum of 64 characters) to identify the
job.
c. Select one of the listed available migration groups.
d. Select a Migration Start Time: 1=Now, 2=Delayed, or
3=JobSerialScheduling.
If you choose Delayed, the CLI prompts you to input the date
and time to begin job execution.
If you choose JobSerialScheduling, the CLI prompts you to
to assign a priority level at which the job should be started when all the serial scheduled jobs start execution. The priority can range between 1 and 256. The jobs with priority 1 are executed before the scheduler executes jobs with priority 2.
The CLI informs you if the migration job is created successfully, and saves any changes you have made.
The MPX200 then schedules a migration job based on your inputs.
3-12 ISR654606-00 A
Page 41
3–Using DMS
Using the Data Migration Wizard
The following shows an example of scheduling an individual data migration job in the CLI:
MPX200 <1> (admin) (miguser) #> migration add
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
Index WWPN, PortId Symbolic Name Target Type
----- --------------------------------- -------------------- ------------
0 20:78:00:c0:ff:d5:9a:05, 00-00-00 HP MSA2012fc-0 Src+Dest
1 50:00:1f:e1:50:0a:e1:49, 82-07-00 HP HSV200-1 Src+Dest
2 50:06:01:60:4b:a0:35:de, 82-03-00 DGC RAID-2 Src+Dest
3 50:00:1f:e1:50:0a:37:18, 00-00-00 HP HSV210-3 Src+Dest
Please select a Source Target from the list above ('q' to quit): 2
Index (VpGroup Name)
----- --------------
1 VPGROUP_1
2 VPGROUP_2
3 VPGROUP_3
4 VPGROUP_4
Please select a VPGroup for Source Lun ('q' to quit): 4
LUN Vendor LUN Size( GB) Attributes
--- ------ -------------- ----------
0 DGC 5.00
1 DGC 5.00
2 DGC 5.00
3 DGC 5.00
4 DGC 5.00
Please select a LUN as a Source Lun ('q' to quit): 1
Index WWPN, PortId Symbolic Name Target Type
----- --------------------------------- -------------------- ------------
0 20:78:00:c0:ff:d5:9a:05, 00-00-00 HP MSA2012fc-0 Src+Dest
1 50:00:1f:e1:50:0a:e1:49, 82-07-00 HP HSV200-1 Src+Dest
2 50:06:01:60:4b:a0:35:de, 82-03-00 DGC RAID-2 Src+Dest
ISR654606-00 A 3-13
Page 42
3–Using DMS Using the Data Migration Wizard
3 50:00:1f:e1:50:0a:37:18, 00-00-00 HP HSV210-3 Src+Dest
Please select a Destination Target from the list above ('q' to quit): 3
Index (VpGroup Name)
----- --------------
1 VPGROUP_1
2 VPGROUP_2
3 VPGROUP_3
4 VPGROUP_4
Please select a VPGroup for Destination Lun ('q' to quit): 1
LUN Vendor LUN Size( GB) Attributes
--- ------ -------------- ----------
1 HP 10.00
2 HP 10.00
3 HP 20.00
4 HP 20.00
5 HP 10.00
6 HP 5.00
7 HP 5.00
8 HP 5.00
Please select a LUN as a Destination Lun('q' to quit): 1
I/O Size (0=32KB, 1=64KB, 2=128KB, 3=512KB, 4=1MB) [64KB ]
Please Enter a Job Description (Max = 64 characters)
default name [ DGC RAID-2:VPG4:001 to HP HSV210-3:VPG1:001 ]
Index Group Owner Group Name
----- ----------- ----------
0 1 Group 0
1 1 DM_Testing
Please select a Group that this Job should belong to [0]
Start Time (1=Now, 2=Delayed, 3=JobSerialScheduling, 4=ConfigureOnly) [Now ]
Successfully created Job
All attribute values for that have been changed will now be saved.
3-14 ISR654606-00 A
Page 43
Using the Data Migration Wizard
Scheduling Data Migration Jobs in Batch Mode
Batch mode for data migration jobs is an HP StorageWorks mpx Manager GUI-only feature used to schedule multiple jobs having the same priority, I/O size, and group options.
This option is particularly useful for migration jobs specified as Schedule for later and Serial Schedule Jobs on the Data Migration Jobs Options dialog box, where the jobs need to be classified under a specific group for better management.
DMS allows a maximum of eight jobs to run simultaneously at any specific time per source array. To optimize MPX200 performance, QLogic recommends that you run simultaneously no more than four jobs on any specified source or destination array.
Consider a data center having multiple applications running on multiple storage arrays that need to be consolidated, and data migration needs to be done on associated LUNs. The data migration administrator must plan the data migration operation to minimize the application downtime. In order to achieve this, the HP StorageWorks mpx Manager provides an option to create data migration job groups, as described in “Creating a Data Migration Job Group” on page 3-6.
3–Using DMS
You can combine all the source LUNs associated with a specific application into a single job group and schedule it for migration using the Schedule in batch mode option. That way all the jobs can start at a predefined time, which can be off-peak hours when the administrator can afford a small application downtime.
Follow these steps to schedule a batch of data migration jobs.
To schedule data migration jobs in batch mode:
1. Start the Data Migration wizard by following the steps specified in “Starting
the Data Migration Wizard” on page 3-7.
2. In the Migration Schedule Options dialog box, click Schedule in batch mode, and then click OK. (See Figure 3-6.)
Figure 3-6 Migration Schedule Options: Batch Mode
ISR654606-00 A 3-15
Page 44
3–Using DMS Using the Data Migration Wizard
The left pane of the Create Data Migration Job dialog box shows a
DataMigration Job (New) option with icons for Source LUNs and Destination LUNs.
The right pane of the Create Data Migration Job dialog box shows the type of array (Source, Destination, or Src+Dest) for each of the arrays available for configuring the data migration job.
3. Choose the appropriate source and destination LUN for the migration job by dragging and dropping the LUNs from the right pane onto the Source LUN or Destination LUN under DataMigration Job (New) in the left pane.
The HP StorageWorks mpx Manager populates the Source LUN and Destination LUN attributes and creates a new DataMigration Job n (New) object below the first one. The default job name is created by using the source and destination array names.
4. Repeat the preceding steps to create migration jobs for all source LUNs to be migrated in a batch, as shown in Figure 3-7.
Figure 3-7 Create Data Migration Job: Batch
3-16 ISR654606-00 A
Page 45
3–Using DMS
Using the Data Migration Wizard
5. To save your migration job and assign job attributes, click Schedule. Or, to abandon your changes, click Close.
6. In the Data Migration Jobs Options dialog box (see Figure 3-8), specify the job attributes as follows:
a. Under Scheduling Type, select one of the following:
Click Start Now to start the job immediately.
Click Schedule for Later, and then enter a Start Time and Start
Date.
Click Serial Schedule Jobs, and then assign a priority (1–256)
in the Job Priority box, where a lower value indicates that the job is scheduled earlier than jobs configured with higher values. For details on Serial Schedule Jobs, see “Starting Serial
Scheduled Jobs” on page 3-18.
Click Configure Only to configure the migration job without any
start time or priority. You may start this job at a later time. (To start the job, select it and then click Start, or from the active job pane, right-click the job and then click Start.)
b. In the Job Description box, enter a user-defined name to describe
this data migration job.
c. In the Group Name box, select a job group name from the list. The
group name makes it easier to view the job status on a group basis.
d. In the IO Size box, either select one of the default I/O sizes, or enter a
custom value.
ISR654606-00 A 3-17
Page 46
3–Using DMS Starting Serial Scheduled Jobs
Figure 3-8 Data Migration Jobs Options: Batch
7. To save the data migration job options, click Apply. Or, to abandon changes to this data migration job, click Cancel.
Starting Serial Scheduled Jobs
If the individual or batch data migration job you created was configured as a Serial Schedule Jobs scheduling type on the Data Migration Jobs Options dialog box(Figure 3-5 on page 3-11 or Figure 3-8 on page 3-18), the job is listed on the Active Data Migration Jobs page. The Status column shows the job as Serial
Scheduled.
To start a serial scheduled job:
1. Open the Serial Data Migration Jobs Options dialog box using one of these options:
On the Wizards menu, click Serial Schedule Job(s).
Right-click a serial scheduled job, and then click Start the Serial
Schedule. This option immediately starts the selected job, unless there are other jobs configured with a lower priority that must complete migration first.
The Serial Data Migration Jobs Options dialog box opens, as shown in
Figure 3-9.
3-18 ISR654606-00 A
Page 47
3–Using DMS
Viewing the Status of Data Migration Jobs
Figure 3-9 Serial Data Migration Jobs Options
2. Under Scheduling Type, click either Start Now or Schedule for later.
3. If you choose Schedule for later, enter the Start Time and Start Date.
4. To save your settings, click Apply.
5. When prompted for a security password, enter migration.
The serial scheduled jobs will start as you have scheduled.
Viewing the Status of Data Migration Jobs
You can use either the HP StorageWorks mpx Manager GUI or the CLI to view the status of data migration jobs.
Viewing Data Job Migration Jobs Status in the GUI
The right pane of the HP StorageWorks mpx Manager displays the job status for all active and completed data migration jobs that you have configured.
To view the status of data migration jobs in the GUI:
1. In the left pane, click the Services tab.
2. In the right pane, click the Active Data Migration Jobs tab.
The Active Data Migration Jobs page in the right pane shows a summarized view of all active jobs, as shown in Figure 3-10.
ISR654606-00 A 3-19
Page 48
3–Using DMS Viewing the Status of Data Migration Jobs
Figure 3-10 Active Data Migration Jobs
3. To see a summarized view of all completed jobs, click the Completed Data Migration Jobs tab in the right pane.
4. To view a list of all jobs, click Data Migration Jobs in the left pane.
5. To view a list of all jobs belonging to a specific migration group, click the migration group name in the left pane.
Viewing Data Job Migration Jobs Status in the CLI
To view the status of data migration jobs in the CLI, use the show migration command.
To view the status of data job migration jobs in the CLI:
1. Open a miguser session using the following command:
miguser start -p migration
2. To view the status of migration jobs, enter the following command:
show migration
3-20 ISR654606-00 A
Page 49
3–Using DMS
Viewing the Status of Data Migration Jobs
3. Enter the appropriate option to see only jobs in a specific state (Running, Failed, or Completed) or all jobs.
4. To see the configuration details for a specific job, enter the appropriate job ID.
The following shows an example of using the CLI to view the status of data migration jobs:
MPX200 <1> (admin) (miguser) #> show migration
Migration State Type ( 1=Running 2=Failed 3=Completed 4=All ) : 4
Job Owner Type Status Job Description
ID
--- ----- ---- ------------------------ ------------------------------
0 1 Offline Running ( 96%) HP HSV210-3:VPG1:001 to HP MS..
Please select a Migration Job Id from the list above ('q' to quit): 0
Migration Information
---------------------
Job Id 0
Job Owner b1
Job Description HP HSV210-3:VPG1:001 to HP MSA2012fc-0:VPG1:001
Group Name Group 0
Migration Type Offline
Priority Not Applicable
Migration Status Running
I/O Size 64 KB
Migration State 96% Complete
Migration Performance 86 MBps
Start Time Fri Oct 9 10:56:56 2009
End Time ---
Delta Time ---
Source Array HP HSV210-3
Source Lun VPG:ID 1:1
Source Lun WWULN 60:05:08:b4:00:05:4d:94:00:00:f0:00:35:a1:00:00
Source Lun Size 10.00 GB
Destination Array HP MSA2012fc-0
Destination Lun VPG:ID 1:1
Destination Lun WWULN 60:0c:0f:f0:00:d5:9a:cb:4d:00:25:4a:01:00:00:00
ISR654606-00 A 3-21
Page 50
3–Using DMS Rescanning Targets
Destination Lun Size 10.24 GB
Number of DRL Blocks 0
Rescanning Targets
To see if one or more data LUNs are exposed to the router ports from the target, you can rescan the target ports. A rescan causes the router to create an array entity for the target ports through which the router is able to see data LUNs.
To rescan targets in the GUI:
1. In the mpx Manager left pane, right-click the FC Discovered Targets node.
2. From the shortcut menu, click Rescan.
In the left pane under the FC Arrays node, the GUI shows the newly-generated array entity.
Alternately, you can click Refresh two or three to rescan the targets and generate the array entity for targets that are exposing LUNs to the router.
To rescan targets in the CLI:
1. Open a miguser session using the following command:
miguser start -p config
2. To rescan for target ports, enter the following command:
target rescan
For example:
MPX200 (admin) #> target rescan
Scanning Target WWPN 00:00:02:00:00:00:00:00
Target Rescan done
Scanning Target WWPN 00:00:01:00:00:00:00:00
Target Rescan done
Scanning Target WWPN 00:00:03:00:00:00:00:00
Target Rescan done
Scanning Target WWPN 50:08:05:f3:00:1a:15:11
Target Rescan done
Scanning Target WWPN 50:08:05:f3:00:1a:15:19
Target Rescan done
Target Re-Scan completed
3-22 ISR654606-00 A
Page 51
3–Using DMS
Viewing Job Details and Controlling Job Actions
Viewing Job Details and Controlling Job Actions
DMS allows you to view the details of a configured data migration job and control the job actions from either the mpx Manager GUI or the CLI.
Viewing Job Details and Controlling Job Actions in the GUI
The HP StorageWorks mpx Manager provides a view of the details of data migration jobs. From the detailed view, you can also control job actions, including pausing, stopping, deleting, resuming, and restarting the job.
To view data migration job details in the GUI:
1. In the mpx Manager left pane, click a migration group to view the status for all jobs belonging to that specific group.
2. In the left pane, click the job by JobID.
Details for the specified job are listed in the right pane, as shown in
Figure 3-11.
ISR654606-00 A 3-23
Page 52
3–Using DMS Viewing Job Details and Controlling Job Actions
Figure 3-11 Viewing Migration Job Details
3. (Optional) From the migration job details pane, perform any of the following job control actions as needed:
Click Pause to interrupt a running migration job. Click Stop to halt a running migration job. Click Remove to delete a migration job. Click Resume to continue a previously paused migration job. Click Start to restart a previously stopped migration job.
3-24 ISR654606-00 A
Page 53
3–Using DMS
Viewing Job Details and Controlling Job Actions
You can also perform the preceding job control actions from the summary view. To do so, right-click a specific job, and then click the appropriate action on the shortcut menu.
Viewing Job Details and Controlling Job Actions in the CLI
The CLI also provides a view of the details of data migration jobs and allows you to control job actions, including pausing, stopping, deleting, resuming, and restarting the job.
To view data migration job details in the CLI:
1. Open a miguser session using the following command:
miguser start -p migration
2. To pause, resume, stop, restart, or delete a migration job, enter the following commands:
To pause a running migration job, enter migration pause (see
“migration pause” on page 5-19).
To resume migration job operation from the state at which it was
paused, enter migration resume (see “migration resume” on
page 5-20).
To halt a running job, enter migration stop (see “migration stop” on
page 5-17). Use this operation if you want to later restart the migration
process without changing the configuration information associated with the job. You may need to also reschedule jobs that have been configured in Serial Scheduled or Delayed Scheduled mode and are not yet started.
To restart a stopped migration job from beginning, enter migration
start (see “migration start” on page 5-18). The data blocks
transmitted before the stop operations are re-migrated. If a job has not yet started, you can optionally change the scheduled time.
To remove a configured job in any state from the system persistence,
enter migration rm (see “migration rm” on page 5-16). Generally, you would use migration rm for completed jobs as an acknowledgement from the administrator. This frees the destination LUN for use by other migration operations. It can also be used to clean up failed jobs that require reconfiguration.
3. The CLI prompts you to select the appropriate job ID to perform the operation on the selected job.
The following shows examples of the migration job action commands:
ISR654606-00 A 3-25
Page 54
3–Using DMS Viewing Job Details and Controlling Job Actions
MPX200 (miguser) #> migration stop
Job Id Type Status LUN ID LUN Size(MB) Src Symbolic Name
------ ---- ----------------- ------ ------------ -----------------
0 Offline Scheduled 7 10000 HP MSA-1
1 Offline Running ( 4%) 8 10000 HP MSA-1
Please select a Migration Job Id from the list above ('q' to quit): 1
All attribute values for that have been changed will now be saved.
MPX200 (miguser) #> migration start
Job Id Type Status LUN ID LUN Size(MB) Src Symbolic Name
------ ---- ----------------- ------ ------------ -----------------
1 Offline Stopped 8 10000 HP MSA-1
Please select a Migration Job Id from the list above ('q' to quit): 1
Migration Start Time for JobId 1:(1=Now, 2=Delayed, 3=JobSerialScheduling) [Now ] 2
Please specify a Date & Time (in <MMddhhmmCCYY> format)
when the migration should start. This should be
within the next 30 days. [ ] 100815002009
All attribute values for that have been changed will now be saved.
MPX200 (miguser) #> migration pause
Job Id Type Status LUN ID LUN Size(MB) Src Symbolic Name
------ ---- ------------------ ------ ------------ ---------------
0 Offline Running ( 16%) 7 10000 HP MSA-1
Please select a Migration Job Id from the list above ('q' to quit): 0
All attribute values for that have been changed will now be saved.
MPX200 (miguser) #> migration resume
Job Id Type Status LUN ID LUN Size(MB) Src Symbolic Name
------ ---- ----------------- ------ ------------ -----------------
0 Offline Paused ( 18%) 7 10000 HP MSA-1
3-26 ISR654606-00 A
Page 55
3–Using DMS
Viewing System and Data Migration Job Logs
Please select a Migration Job Id from the list above ('q' to quit): 0
All attribute values for that have been changed will now be saved.
Viewing System and Data Migration Job Logs
HP StorageWorks mpx Manager provides two types of logs: system and data migration job. You can view system and data migration job logs from both the GUI and the CLI.
Viewing Logs in the GUI
This section provides procedures for viewing the system log and the data migration job log in the HP StorageWorks mpx Manager.
To view the system log in the GUI:
1. On the HP StorageWorks mpx Manager main window, click the View Logs button.
2. In the Log Type dialog box, click System Logs.
Figure 3-12 shows an example of the mpx Log: System Log dialog box.
ISR654606-00 A 3-27
Page 56
3–Using DMS Viewing System and Data Migration Job Logs
Figure 3-12 mpx Log: System Log
Data in the system log includes the date and time, application type, and description. Informational entries are shown with a white background, and error entries are shown with a red background.
Buttons on the bottom of the mpx Log: System Log dialog box provide the following actions:
Click OK to close the log window after you have finished viewing it.
Click Clear to delete the contents of the log.
Click Export to download the logs in CSV file format that can be
viewed in any spreadsheet application, such as Microsoft Excel.
Click Print to send the contents of the log to a printer.
To view the data migration job log in the GUI:
1. On the HP StorageWorks mpx Manager main window, click the View Logs button.
2. In the Log Type dialog box, click Data Migration Logs.
Figure 3-13 shows an example of the mpx Log: Migration Log dialog box.
3-28 ISR654606-00 A
Page 57
3–Using DMS
Viewing System and Data Migration Job Logs
Figure 3-13 mpx Log: Migration Log
The migration job log contains the following columns of information:
SeqID is the sequential ID of log entries.
Time Stamp is the log entry time, based on router system time.
Group Name is the user-defined job group or Group 0.
Job Name is the user-defined name for the job.
Job ID is a numeric ID.
Job Type is the migration job type (COMPARE or MIGRATION).
Operation is the task or action (ADDED, STARTED, COMPLETED, or
ACK).
Source Array LUN is the migration source LUN.
Dest Array LUN is the migration destination LUN.
ISR654606-00 A 3-29
Page 58
3–Using DMS Viewing System and Data Migration Job Logs
Source Array WWULN is the world wide unique LUN name for the
source array.
Dest Array WWULN: is the world wide unique LUN name for the
destination array.
Migr Size is the size of the migration job (source LUN).
Buttons on the bottom of the mpx Log: Migration Log dialog box provide the following actions:
Click OK to close the log window after you have finished viewing it.
Click Clear to delete the contents of the log.
Click Export to download the logs in CSV format that can be viewed in
a spreadsheet application, such as Microsoft Excel
Viewing Logs in the CLI
This section provides procedures for viewing the system log and the data migration job log in the CLI.
To view the system log in the CLI:
1. Open a miguser session using the following command:
miguser start -p migration
2. To view all logs related to all migration jobs, enter the following command:
show logs (see “show logs” on page 5-51)
3. To view only a limited number of log entries, specify a value; for example, show logs 10.
The following example shows how to view the system log in the CLI:
®
.
3-30 ISR654606-00 A
Page 59
3–Using DMS
Viewing System and Data Migration Job Logs
MPX200 <1> (admin) (miguser) #> show logs 10
10/09/2009 11:11:04 BridgeApp 3 QLFC_Login: Port Name 500601604ba035de
10/09/2009 11:15:29 QLFC 3 #0: QLIsrEventHandler: RSCN update (8015) rscnInfo:0x2080000 VpIndex:0x0
10/09/2009 11:15:29 QLFC 3 #0: QLIsrEventHandler: RSCN update (8015) rscnInfo:0x2080000 VpIndex:0x1
10/09/2009 11:15:29 QLFC 3 #0: QLIsrEventHandler: RSCN update (8015) rscnInfo:0x2080000 VpIndex:0x2
10/09/2009 11:15:29 QLFC 3 #0: QLIsrEventHandler: RSCN update (8015) rscnInfo:0x2080000 VpIndex:0x3
10/09/2009 11:15:29 QLFC 3 #1: QLIsrEventHandler: RSCN update (8015) rscnInfo:0x2080000 VpIndex:0x0
10/09/2009 11:15:29 QLFC 3 #1: QLIsrEventHandler: RSCN update (8015) rscnInfo:0x2080000 VpIndex:0x1
10/09/2009 11:15:29 QLFC 3 #1: QLIsrEventHandler: RSCN update (8015) rscnInfo:0x2080000 VpIndex:0x2
10/09/2009 11:15:29 QLFC 3 #1: QLIsrEventHandler: RSCN update (8015) rscnInfo:0x2080000 VpIndex:0x3
10/09/2009 11:18:41 UserApp 3 ValidateSerialSchedule: Previous time 0 New time 2
To view the data migration job log in the CLI:
1. Open a miguser session using the following command:
miguser start -p migration
2. To view all logs related to all migration jobs, enter the following command:
show migration_logs (see “show migration_logs” on page 5-50)
3. To view only a limited number of log entries, specify a value; for example, show migration_logs 5.
The following example shows how to view the data migration log in the CLI:
MPX200 (miguser) #> show migration_logs 5
Thu Sep 10 13:15:49 2009
Seq id: 645 : Job Type: Migration : miguser :COMPLETED : JobId 0(Offline) of group Group 0 with priority 0 from Target HP HSV200-0 Lun 60:05:08:b4:00:07:59:a4:00:02:a0:00:00:7e:00:00(6) to Target HP HSV200-0 Lun 60:05:08:b4:00:07:59:a4:00:02:a0:00:00:83:00:00(7) with migration size 5.00 GB
ISR654606-00 A 3-31
Page 60
3–Using DMS Using the Verify Migration Job Wizard
Thu Sep 10 13:33:16 2009
Seq id: 646 : Job Type: Migration : miguser :ACKNOWLEDGED : JobId 0(Offline) of group Group 0 with priority 0 from Target HP HSV200-0 Lun 60:05:08:b4:00:07:59:a4:00:02:a0:00:00:7e:00:00(6) to Target HP HSV200-0 Lun 60:05:08:b4:00:07:59:a4:00:02:a0:00:00:83:00:00(7) with migration size 5.00 GB
Thu Sep 10 13:38:37 2009
Seq id: 647 : Job Type: Migration : miguser :ADDED : JobId 0(Offline) of group Group 0 with priority 0 from Target HP HSV200-0 Lun Invalid Wwuln(6) to Target HP HSV200-0 Lun Invalid Wwuln(7) with migration size 5.00 GB
Thu Sep 10 13:38:37 2009
Seq id: 648 : Job Type: Migration : miguser :STARTING MIGRATION : JobId 0(Offline) of group Group 0 with priority 0 from Target HP HSV200-0 Lun Invalid Wwuln(6) to Target HP HSV200-0 Lun Invalid Wwuln(7) with migration size 5.00 GB
Thu Sep 10 13:39:45 2009
Seq id: 649 : Job Type: Migration : miguser :COMPLETED : JobId 0(Offline) of group Group 0 with priority 0 from Target HP HSV200-0 Lun Invalid Wwuln(6) to Target HP HSV200-0 Lun Invalid Wwuln(7) with migration size 5.00 GB
MPX200 (miguser) #>
Using the Verify Migration Job Wizard
The Verify Migration Job wizard helps you configure verification jobs to compare data residing on two LUNs. This ensures the data integrity of the migration process by performing a bit-by-bit comparison of the data on the source LUN with the corresponding data on the destination LUN. Job verification helps ensure that the source data migrated successfully without any data loss or corruption.
You can configure a verification job on a pair of source and destination LUNs only after the migration job configured on that pair has been completed and acknowledged. The Verify Migration Job wizard is generally the same as the Data Migration wizard (see “Using the Data Migration Wizard” on page 3-7). All scheduling options and job state changes (start, stop, pause, and so on) apply in the same way to both verification and migration jobs.
This section contains the following information for the Verify Migration Job wizard:
“Starting the Verify Migration Job Wizard” on page 3-33
“Scheduling Verification of Job Options” on page 3-34
3-32 ISR654606-00 A
Page 61
Starting the Verify Migration Job Wizard
Follow these steps to start the configure verifying jobs wizard.
To start the Verify Migration Job wizard:
1. Start the HP StorageWorks mpx Manager and connect to the MPX200 by providing the IP address of the MPX200.
2. Start the Verify Migration Job wizard using one of these methods:
From the Wizards menu, click Configure Verifying Jobs.
In the left pane, open the Services page, and then right-click
Configure Verifying Job.
3. In the Data Migration Security Check dialog box, enter your miguser password (the default is migration), and then click OK.
3–Using DMS
Using the Verify Migration Job Wizard
ISR654606-00 A 3-33
Page 62
3–Using DMS Using the Verify Migration Job Wizard
Scheduling Verification of Job Options
Follow these steps to schedule the verification of job options.
To schedule job option verification:
1. In the Verify Migration Jobs wizard (Figure 3-14), click Options.
Figure 3-14 Verify Migration Job Wizard
2. In the Verify Schedule Options dialog box, select the Scheduling Mode: either batch mode or individual job, and then click OK.
3. Click Schedule.
4. In the Verifying Jobs Options dialog box (Figure 3-15), specify the job attributes as follows:
a. Under Scheduling Type, select one of the following:
Click Start Now to start the job immediately.
3-34 ISR654606-00 A
Page 63
3–Using DMS
Using the Verify Migration Job Wizard
Click Schedule for Later, and then enter a Start Time and Start
Date.
Click Serial Schedule Jobs, and then assign a priority (1–256)
in the Job Priority box, where a lower value indicates that the job is scheduled earlier than jobs configured with higher values. For details on Serial Schedule Jobs, see “Starting Serial
Scheduled Jobs” on page 3-18.
Click Configure Only to configure the migration job without any
start time or priority. You may start this job at a later time. (To start the job, select it and then click Start, or from the active job pane, right-click the job and then click Start.)
b. In the Group Name box, select a job group name from the list. The
group name makes it easier to view the job status on a group basis.
c. In the IO Size box, either select one of the default I/O sizes, or enter a
custom value.
Figure 3-15 Verifying Jobs Options Dialog Box
d. To save the verifying jobs options, click Apply. Or, to abandon
changes to this job verification, click Cancel.
5. Add the source and destination LUN. For details, see “Using the Data
Migration Wizard” on page 3-7.
ISR654606-00 A 3-35
Page 64
3–Using DMS Acknowledging a Data Migration Job
Acknowledging a Data Migration Job
HP StorageWorks mpx Manager keeps a track of all the data migration jobs until you either delete them from the system or acknowledge them after job completion. You must acknowledge jobs to free up the destination LUN so that it can become part of another job, if required.
To acknowledge a completed data migration job:
1. In the left pane of the HP StorageWorks mpx Manager, click the Services tab, and then click Data Migration Jobs.
2. In the right pane, click the Completed Data Migration Jobs tab to bring that page to the front.
3. On the Completed Data Migration Jobs page, scroll over a job that is specified as 100% in the % Completed column.
4. On the shortcut menu, click Acknowledge Completed Data Migration.
Removing an Offline Array
You should remove arrays used in data migration because they are kept in persistent storage. If you used an array-based license for the data migration job and you plan to use this array again for migration, you may keep the license when removing the array.
To remove an offline array:
1. In the left pane of the HP StorageWorks mpx Manager, click the Services tab.
1. Under FC Arrays, right-click the name of the offline array you want to remove.
2. From the shortcut menu, click Remove Offline Array.
3-36 ISR654606-00 A
Page 65
4 Data Migration Licenses
This chapter provides information on data migration licenses, including:
Types of Data Migration Licenses
“Installing a Data Migration License Key” on page 4-2
“Applying an Array-based License to a Specific Array” on page 4-5
“Viewing Data Migration License Usage” on page 4-8
Types of Data Migration Licenses
The two types of data migration licenses include:
Capacity-based licenses Array-based licenses
Capacity-based Licenses
Capacity-based licenses allow you to migrate data up to a specific limit designated by the applied license key. This type of license is available in variants of 2TB, 5TB, and 10TB capacities, which can be consumed by one or more migration jobs that you specify. Every time you configure a data migration job, the available capacity is reduced by an amount equivalent to the size of the source LUN being migrated. The MPX200 does not allow you to add migration jobs when the job size exceeds available migration licenses. In addition, custom size license keys are available. A custom size license key allows you to purchase a single license key based on your requirements.
Array-based Licenses
Array-based licenses allow you to migrate unlimited amounts of data to and from the specific array that is licensed. These licenses are available in variants of SINGLE-ARRAY and 3-ARRAY capacity. The licensed array may be used as either a source or destination array while configuring jobs for data migration.
ISR654606-00 A 4-1
Page 66
4–Data Migration Licenses Installing a Data Migration License Key
Installing a Data Migration License Key
You can install a data migration license key from either the HP StorageWorks mpx Manager GUI or the CLI. This section provides both methods.
Installing a Data Migration License Key in the GUI
Follow this procedure to install a data migration license key in the HP StorageWorks mpx Manager GUI.
To install a data migration license key in the GUI:
1. In the HP StorageWorks mpx Manager, click the mpx Manager tab in the left pane.
2. In the left pane, click mpx HP StorageWorks MPX200:<IP address>.
3. In the right pane, click the Features tab.
4. On the Features page under License Information, click Add, as shown in
Figure 4-1.
4-2 ISR654606-00 A
Page 67
4–Data Migration Licenses
Installing a Data Migration License Key
Figure 4-1 Features Page: License Information
The New License Key dialog box opens, as shown in Figure 4-2.
Figure 4-2 New License Key Dialog Box
5. Type a valid DM license key, and then click OK.
The Add License dialog box (Figure 4-3) indicates the success of the license add operation.
ISR654606-00 A 4-3
Page 68
4–Data Migration Licenses Installing a Data Migration License Key
Figure 4-3 Add License Dialog Box
6. Click OK to close the verification dialog box.
7. Verify that the newly-added key appears in the list of keys on the Features page, as shown in Figure 4-1 on page 4-3.
Installing a Data Migration License Key in the CLI
Follow this procedure to install a data migration license key in the CLI.
To install a data migration license key in the CLI:
1. Open a miguser session using the following command:
miguser start -p migration
2. To add the license key, enter the following command:
set features (see “set features” on page 5-6)
3. To view a list of installed data migration licenses, enter the following command:
show features (see “show features” on page 5-49)
The following example shows the set features and show features commands.
MPX200 <1> (admin) set features
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
Enter feature key to be saved/activated: 2000800-LCWL13GAUWO5K-8-ARR-LIC
4-4 ISR654606-00 A
Page 69
4–Data Migration Licenses
Applying an Array-based License to a Specific Array
All attribute values that have been changed will now be saved
MPX200 (miguser) #> show features
Feature Key Information
-------------------------
Key 100000-LCMDSNDCESR3X-B751BF30-DM-2TB
Date Applied Fri Aug 22 21:59:58 2009
Key 200000-LCKROB9C6AKYA-B751BE8E-DM-5TB
Date Applied Wed Sep 17 10:05:09 2009
Key 100000-LCIGAALUMFE2S-B751BF0B-DM-2TB
Date Applied Wed Oct 8 09:54:28 2009
MPX200 (miguser) #>
Applying an Array-based License to a Specific Array
You can apply an array-based license to a specified storage array using either the HP StorageWorks mpx Manager GUI or the CLI. This section provides instructions for both methods.
Applying an Array-based License to a Specific Array in the GUI
If you have purchased array-based licenses and installed the licenses in the MPX200, follow these steps to license a specific array for data migration. For every array that is licensed, one license is consumed.
To apply an array-based license to a specific array in the GUI:
1. In the left pane of the HP StorageWorks mpx Manager main window, click the mpx Manager tab.
2. On the Wizards menu, click License an Array.
3. In the left pane under FC Arrays, click the name of the array for which you want to apply the license.
4. In the License Array dialog box (Figure 4-4), select the array for which you want to apply the license, and then click OK.
ISR654606-00 A 4-5
Page 70
4–Data Migration Licenses Applying an Array-based License to a Specific Array
Figure 4-4 License Array Dialog Box
The Information page for the selected array now shows the Array License as Licensed, as shown in Figure 4-5.
4-6 ISR654606-00 A
Page 71
4–Data Migration Licenses
Applying an Array-based License to a Specific Array
Figure 4-5 Information Page Showing Array is Licensed
Applying an Array-based License to a Specific Array in the CLI
To apply an array-based license to a specific array in the CLI:
If you have purchased array-based licenses and installed the licenses in the MPX200, follow these steps to license a specific array for data migration. For every array that is licensed, one license is consumed.
1. Open a miguser session using the following command:
miguser start -p migration
2. To apply a license, enter the following command:
set array (see “set array” on page 5-8)
3. At the prompt, Do you want to apply array license (yes/no), enter yes.
ISR654606-00 A 4-7
Page 72
4–Data Migration Licenses Viewing Data Migration License Usage
The following example shows the set array command.
MPX200 (miguser) #> set array
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
Index WWPN, PortId Symbolic Name Target Type
----- --------------------------------- --------------- -----------
0 50:00:1f:e1:50:0a:e1:4c, 01-2b-00 HP HSV200-0 Unknown
1 50:00:1f:e1:50:0a:37:18, 01-24-00 HP HSV210-1 Unknown
2 50:06:01:69:41:e0:18:94, 01-2d-00 DGC RAID-2 Unknown
3 20:70:00:c0:ff:d5:9a:05, 01-0f-ef HP MSA2012fc-3 Unknown
Please select a Target Id from the list above ('q' to quit): 1
Symbolic Name (Max = 128 characters) [HP HSV210-1]
Target Type (1=SrcTarget, 2=DstTarget, 3=Src+Dest Target) [3 ] 1
Bandwidth for Migration (0=Array Bandwidth, 1-400 MBps ) [0 ]
Do you want to apply array license (yes/no) [No ]yes
All attribute values for that have been changed will now be saved.
Viewing Data Migration License Usage
You can view the usage for the data migration licenses from either the HP StorageWorks mpx Manager GUI or the CLI. This section provides both methods.
Viewing Data Migration License Usage in the GUI
Follow this procedure to view the usage of data migration licenses in the GUI.
To view data migration license usage in the GUI:
1. In the left pane of the HP StorageWorks mpx Manager, click the Services tab.
2. In the left pane, click mpx MPX200:<IP address>.
License usage appears on the Data Migration Info page, as shown in
Figure 4-6.
4-8 ISR654606-00 A
Page 73
4–Data Migration Licenses
Viewing Data Migration License Usage
Figure 4-6 Data Migration Info
Viewing Data Migration License Usage in the CLI
Follow this procedure to view the usage of data migration licenses in the CLI.
To view data migration license usage in the CLI:
1. Open a miguser session using the following command:
miguser start -p migration
2. To view the status of migration license consumed and available on the current system, enter the following command:
show migration_usage (see “show migration_usage” on page 5-46)
ISR654606-00 A 4-9
Page 74
4–Data Migration Licenses Viewing Data Migration License Usage
The following example shows the show migration_usage command.
MPX200 (miguser) #> show migration_usage
Migration License Usage
-----------------------
Total capacity licensed 10240.00 GB
Migration license consumed 1.00 GB
License consumed by active jobs 10.00 GB
Total capacity available 10229.00 GB
Array Based Licenses
--------------------
Array based licences issued 3
Array based licences used 0
Available array based licenses 3
4-10 ISR654606-00 A
Page 75
5 Command Line Interface
This chapter provides information on using the command line interface (CLI) for data migration services. It defines the guest MPX200 account and the user sessions, admin and miguser. For each command, it provides a description, the required session type, and an example.
User Accounts
User accounts include the guest account. The guest account is the default user account used to log into the MPX200 Telnet session. The guest session has a view-only type of access. The default password for this account is password.
User Sessions
User sessions include the admin session and miguser session, as described in the following.
Admin Session
The admin is the system administrator session that provides access to CLI commands that manage the system resources. The default password for starting the admin session is config. You can start and stop an admin session using the following commands:
admin [start/begin]
admin [end/cancel/stop]
For example:
MPX200 #> admin start
Password : ******
MPX200 (admin) #>
MPX200 (admin) #> admin cancel
MPX200 #>
ISR654606-00 A 5-1
Page 76
5–Command Line Interface Commands
Miguser Session
The miguser is the migration administrator session that has privileges to run CLI commands related to the migration operations. The default password for starting the miguser session is migration. You can start and stop a miguser session using the following commands:
miguser [start/begin]
miguser [end/cancel/stop]
For example:
MPX200 #> miguser begin
Password : *********
MPX200 (miguser) #>
MPX200 (miguser) #> miguser stop
MPX200 #>
Commands
Table 5-1 lists by type the DMS commands used in the CLI, and provides a
cross-reference to the details for each one.
set commands “set system” on page 5-5
migration commands “migration_group add” on page 5-10
Table 5-1. CLI Commands
Command Type Commands
“set features” on page 5-6
“set fc” on page 5-7
“set array” on page 5-8
“set VPGroups” on page 5-9
“migration_group remove” on page 5-11
“migration_group edit” on page 5-12
“migration add” on page 5-13
“migration rm” on page 5-16
“migration stop” on page 5-17
“migration start” on page 5-18
“migration pause” on page 5-19
“migration resume” on page 5-20
“migration acknowledge” on page 5-21
5-2 ISR654606-00 A
Page 77
5–Command Line Interface
Table 5-1. CLI Commands (Continued)
Command Type Commands
start commands “start_serial_jobs” on page 5-22
compare_luns commands “compare_luns add” on page 5-23
“compare_luns rm” on page 5-26
“compare_luns stop” on page 5-27
“compare_luns start” on page 5-28
“compare_luns pause” on page 5-29
“compare_luns resume” on page 5-30
“compare_luns acknowledge” on page 5-31
show commands “show fc” on page 5-32
“show migration” on page 5-34
“show array” on page 5-36
“show luninfo” on page 5-38
“show migration_luninfo” on page 5-40
“show migration_params” on page 5-42
“show mgmt” on page 5-43
“show memory” on page 5-44
“show properties” on page 5-45
“show migration_usage” on page 5-46
“show perf” on page 5-47
“show perf byte” on page 5-48
“show features” on page 5-49
“show migration_logs” on page 5-50
“show logs” on page 5-51
“show luns” on page 5-52
“show targets” on page 5-54
“show vpgroups” on page 5-55
“show compare_luns” on page 5-61
Commands
array commands “show array” on page 5-36
target commands “show targets” on page 5-54
ISR654606-00 A 5-3
“set array” on page 5-8
“array rm” on page 5-58
“array_licensed_port rm” on page 5-59
“target rescan” on page 5-56
Page 78
5–Command Line Interface Commands
Command Type Commands
Miscellaneous commands “save capture” on page 5-57
Table 5-1. CLI Commands (Continued)
“readjust_priority” on page 5-60
5-4 ISR654606-00 A
Page 79
5–Command Line Interface
set system
set system
Changes the operational mode of the MPX200 to Data Migration from the default mode of iSCSI Server Connectivity. All the data migration CLI and GUI features are activated only in the Data Migration mode. This command removes all existing mapping-related settings and causes the MPX200 to reboot.
Session admin
Example The following example shows the set system command:
MPX200 <1> (admin) #> set system
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
System Symbolic Name (Max = 64 characters) [Blade-1 ]
Target Presentation Mode (0=Auto, 1=Manual) [Auto ]
Controller Lun AutoMap (0=Enable, 1=Disable) [Disabled ]
Target Access Control (0=Enable, 1=Disable) [Enabled ]
Telnet (0=Enable, 1=Disable) [Enabled ]
SSH (0=Enable, 1=Disable) [Enabled ]
System Log Level (Default,Min=0, Max=2) [0 ]
All attribute values that have been changed will now be saved.
ISR654606-00 A 5-5
Page 80
5–Command Line Interface set features
set features
Saves and activates the array’s data migration license key.
Session admin
Example The following example shows the set features command:
MPX200 <1> (admin) #> set features
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
Enter feature key to be saved/activated:
All attribute values that have been changed will now be saved.
2000800-LCWL13GAUWO5K-8-ARR-LIC
5-6 ISR654606-00 A
Page 81
5–Command Line Interface
set fc
set fc
Sets the port status and programmed connection status.
Session admin
Example The following example shows the set fc command:
MPX200 (admin) #> set fc
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
WARNING:
The following command might cause a loss of connections to both ports.
Configuring FC Port: 1
-------------------------
Port Status (0=Enable, 1=Disable) [Enabled ]
Link Rate (0=Auto, 1=1Gb, 2=2Gb, 4=4Gb, 8=8GB) [Auto ]
Frame Size (0=512B, 1=1024B, 2=2048B) [2048 ]
Execution Throttle (Min=16, Max=65535) [256 ]
All attribute values for Port 1 that have been changed will now be saved.
Configuring FC Port: 2
-------------------------
Port Status (0=Enable, 1=Disable) [Enabled ]
Link Rate (0=Auto, 1=1Gb, 2=2Gb, 4=4Gb, 8=8GB) [Auto ]
Frame Size (0=512B, 1=1024B, 2=2048B) [2048 ]
Execution Throttle (Min=16, Max=65535) [256 ]
All attribute values for Port 2 that have been changed will now be saved.
ISR654606-00 A 5-7
Page 82
5–Command Line Interface set array
set array
Sets the target type of an array to make it behave as either a source, a destination, or both.
Session miguser
Example The following example shows the set array command:
MPX200 <1> (admin)(miguser) #> set array
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
Index WWPN, PortId Symbolic Name Target Type
----- --------------------------------- --------------- -----------
0 20:78:00:c0:ff:d5:9a:05, 00-00-00 HP MSA2012fc-0 Src+Dest
1 50:00:1f:e1:50:0a:e1:49, 82-07-00 HP HSV200-1 Src+Dest
2 50:06:01:60:4b:a0:35:de, 82-03-00 DGC RAID-2 Src+Dest
3 50:00:1f:e1:50:0a:37:18, 00-00-00 HP HSV210-3 Src+Dest
Please select a Target Id from the list above ('q' to quit): 0
Symbolic Name (Max = 128 characters) [HP MSA2012fc-0]
Target Type (1=SrcTarget, 2=DstTarget, 3=Src+Dest 4=None Target) [3 ]
Bandwidth for Migration (0=Array Bandwidth, 50-1600 MBps ) [0 ]
Enable Load Balancing (0=Enable, 1=Disable) [Enabled ]
Array based licensed applied.
All attribute values for that have been changed will now be saved.
5-8 ISR654606-00 A
Page 83
5–Command Line Interface
set VPGroups
set VPGroups
Enables or disables the virtual port groups (VP groups), and specifies names to each VP group. VpGroup 1 cannot be disabled; however, you can change its name.
Session admin
Example The following shows an example of the set vpgroups command.
MPX200 <1> (admin) (miguser) #> set vpgroups
The following wizard will query for attributes before persisting
and activating the updated mapping in the system configuration.
If you wish to terminate this wizard before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
Configuring VpGroup: 1
-------------------------
Status (0=Enable, 1=Disable) [Enabled ]
VpGroup Name (Max = 64 characters) [VPGROUP_1 ] VPGroup 1
All attribute values for VpGroup 1 that have been changed will now be saved.
Configuring VpGroup: 2
-------------------------
Status (0=Enable, 1=Disable) [Enabled ]
VpGroup Name (Max = 64 characters) [VPGROUP_2 ] VPGroup 2
All attribute values for VpGroup 2 that have been changed will now be saved.
Configuring VpGroup: 3
-------------------------
Status (0=Enable, 1=Disable) [Enabled ]
VpGroup Name (Max = 64 characters) [VPGROUP_3 ] VPGroup 3
All attribute values for VpGroup 3 that have been changed will now be saved.
Configuring VpGroup: 4
-------------------------
Status (0=Enable, 1=Disable) [Enabled ]
VpGroup Name (Max = 64 characters) [VPGROUP_4 ] VPGroup 4
All attribute values for VpGroup 4 that have been changed will now be saved.
ISR654606-00 A 5-9
Page 84
5–Command Line Interface migration_group add
migration_group add
Creates a data migration job group that you can use to combine migration jobs to simplify scheduling and monitoring data migration processes.
Session miguser
Example The following example shows the migration_group add command:
MPX200 (miguser) #> migration_group add
Please Enter Group Name that you want to create (Min = 4 Max = 64 chars) DM_1
Successfully created Group DM_1
5-10 ISR654606-00 A
Page 85
5–Command Line Interface
migration_group remove
migration_group remove
Deletes or removes an existing data migration group that will not be used in any of the new data migration jobs that need to be scheduled. You may need to delete groups because there is limit of eight groups into which the MPX200 can classify data migration jobs.
Session miguser
Example The following example shows the migration_group rm command:
MPX200 (miguser) #> migration_group remove
Index Group Name
----- ----------
1 DM_1
2 DM_2
Please select a Group to be removed ('q' to quit): 1
Sucessfully removed Group DM_1
ISR654606-00 A 5-11
Page 86
5–Command Line Interface migration_group edit
migration_group edit
Renames an already existing data migration job group. Use this command to correct spelling mistakes that might have occurred when you typed the name while creating the data migration job group.
Session miguser
Example The following example shows the migration_group edit command:
MPX200 (miguser) #> migration_group edit
Index Group Name
----- ----------
0 Group 0
1 DM_1
2 DM_2
Please select a Group to be updated ('q' to quit): 0
Please Enter New Group Name (Min = 4 Max = 64 characters) [ Group 0 ]: DM_3
Successfully updated Group name to DM_3
5-12 ISR654606-00 A
Page 87
5–Command Line Interface
migration add
migration add
Schedules a data migration job. You can enter a name for the data migration job and associate it with a job group. Scheduling options include: immediately, at a pre-defined later time, or by serial scheduling. Serial scheduling requires that you assign a priority to the job that is used to schedule it prior to (lower priority value) or after (higher priority value) a specific job in the serial schedule queue of data migration jobs.
Session miguser
Example The following example shows the migration add command:
MPX200 <1> (admin) (miguser) #> migration add
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
Index WWPN, PortId Symbolic Name Target Type
----- --------------------------------- -------------------- ------------
0 20:78:00:c0:ff:d5:9a:05, 00-00-00 HP MSA2012fc-0 Src+Dest
1 50:00:1f:e1:50:0a:e1:49, 82-07-00 HP HSV200-1 Src+Dest
2 50:06:01:60:4b:a0:35:de, 82-03-00 DGC RAID-2 Src+Dest
3 50:00:1f:e1:50:0a:37:18, 00-00-00 HP HSV210-3 Src+Dest
Please select a Source Target from the list above ('q' to quit): 2
Index (VpGroup Name)
----- --------------
1 VPGROUP_1
2 VPGROUP_2
3 VPGROUP_3
4 VPGROUP_4
Please select a VPGroup for Source Lun ('q' to quit): 4
LUN Vendor LUN Size( GB) Attributes
--- ------ -------------- ----------
0 DGC 5.00
1 DGC 5.00
2 DGC 5.00
3 DGC 5.00
ISR654606-00 A 5-13
Page 88
5–Command Line Interface migration add
4 DGC 5.00
Please select a LUN as a Source Lun ('q' to quit): 1
Index WWPN, PortId Symbolic Name Target Type
----- --------------------------------- -------------------- ------------
0 20:78:00:c0:ff:d5:9a:05, 00-00-00 HP MSA2012fc-0 Src+Dest
1 50:00:1f:e1:50:0a:e1:49, 82-07-00 HP HSV200-1 Src+Dest
2 50:06:01:60:4b:a0:35:de, 82-03-00 DGC RAID-2 Src+Dest
3 50:00:1f:e1:50:0a:37:18, 00-00-00 HP HSV210-3 Src+Dest
Please select a Destination Target from the list above ('q' to quit): 3
Index (VpGroup Name)
----- --------------
1 VPGROUP_1
2 VPGROUP_2
3 VPGROUP_3
4 VPGROUP_4
Please select a VPGroup for Destination Lun ('q' to quit): 1
LUN Vendor LUN Size( GB) Attributes
--- ------ -------------- ----------
1 HP 10.00
2 HP 10.00
3 HP 20.00
4 HP 20.00
5 HP 10.00
6 HP 5.00
7 HP 5.00
8 HP 5.00
Please select a LUN as a Destination Lun('q' to quit): 1
I/O Size (0=32KB, 1=64KB, 2=128KB, 3=512KB, 4=1MB) [64KB ]
Please Enter a Job Description (Max = 64 characters)
default name [ DGC RAID-2:VPG4:001 to HP HSV210-3:VPG1:001 ]
Index Group Owner Group Name
----- ----------- ----------
0 1 Group 0
5-14 ISR654606-00 A
Page 89
5–Command Line Interface
migration add
1 1 DM_Testing
Please select a Group that this Job should belong to [0]
Start Time (1=Now, 2=Delayed, 3=JobSerialScheduling, 4=ConfigureOnly) [Now ]
Successfully created Job
All attribute values for that have been changed will now be saved.
ISR654606-00 A 5-15
Page 90
5–Command Line Interface migration rm
migration rm
Deletes a data migration job.
Session miguser
Example The following example shows the migration rm command:
MPX200 <1> (admin)(miguser) #> migration rm
Job Type Status Job Description
ID
--- ---- ----------------------- ------------------------------------
0 Offline Running ( 5%) DGC RAID-2:VPG4:001 to HP HSV210-3
Please select a Job Id from the list above ('q' to quit): 0
Do you wish to continue with the operation(yes/no)? [No] yes
All attribute values for that have been changed will now be saved.
5-16 ISR654606-00 A
Page 91
5–Command Line Interface
migration stop
migration stop
Stops running the data migration job. Use this command if you want to later restart the migration process due to some technical or business need. You can also use it on already scheduled jobs to change the scheduling time.
Session miguser
Example The following example shows the migration stop command:
MPX200 <1> (admin)(miguser) #> migration stop
Job Type Status Job Description
ID
--- ---- ----------------------- ------------------------------------
0 Offline Running ( 61%) HP HSV200-0:LUN1 to DGC RAID-1:LUN0
Please select a Job Id from the list above ('q' to quit): 0
All attribute values for that have been changed will now be saved.
ISR654606-00 A 5-17
Page 92
5–Command Line Interface migration start
migration start
Restarts a previously stopped migration job. The migration process starts over from the first block.
Session miguser
Example The following example shows the migration start command:
MPX200 <1> (admin)(miguser) #> migration start
Job Type Status Job Description
ID
--- ---- ------------------------ ------------------------------------
0 Offline Stopped HP HSV200-0:LUN1 to DGC RAID-1:LUN0
Please select a Job Id from the list above ('q' to quit): 0
Start Time for JobId 0:(1=Now, 2=Delayed, 3=JobSerialScheduling) [Now ] 2
Please specify a Date & Time (in <MMddhhmmCCYY> format)
when the scheduled job should start. This should be
within the next 30 days. [ ] 121215002009
All attribute values for that have been changed will now be saved.
5-18 ISR654606-00 A
Page 93
5–Command Line Interface
migration pause
migration pause
Pauses a running migration job. This command freezes the migration process. You can later resume the job from the block where the migration was paused.
Session miguser
Example The following example shows the migration pause command:
MPX200 <1> (admin)(miguser) #> migration pause
Job Type Status Job Description
ID
--- ---- ------------------------ ------------------------------------
0 Offline Running ( 67%) HP HSV200-0:LUN1 to DGC RAID-1:LUN0
Please select a Job Id from the list above ('q' to quit): 0
All attribute values for that have been changed will now be saved.
ISR654606-00 A 5-19
Page 94
5–Command Line Interface migration resume
migration resume
Resumes a paused data migration job. The job is resumed from the block where the data migration was paused.
Session miguser
Example The following example shows the migration resume command:
MPX200 <1> (admin)(miguser) #> migration resume
Job Type Status Job Description
ID
--- ---- ------------------------ ------------------------------------
0 Offline Paused ( 80%) HP HSV200-0:LUN1 to DGC RAID-1:LUN0
Please select a Job Id from the list above ('q' to quit): 0
All attribute values for that have been changed will now be saved..
5-20 ISR654606-00 A
Page 95
5–Command Line Interface
migration acknowledge
migration acknowledge
Acknowledges a completed data migration job. After running this command, the migration job is permanently deleted from the database.
Session miguser
Example The following example shows the migration acknowledge command:
MPX200 (miguser) #> migration acknowledge
Job Type Status Job Description
ID
--- ---- ------------------------ ------------------------------------
0 Offline Completed (100%) HP HSV200-0:LUN1 to DGC RAID-1:LUN0
Please select a Job Id from the list above ('q' to quit): 0
All attribute values for that have been changed will now be saved.
ISR654606-00 A 5-21
Page 96
5–Command Line Interface start_serial_jobs
start_serial_jobs
Starts one or more serial scheduled jobs that have been configured but not yet started.
Session miguser
Example The following example shows the start_serial jobs command:
MPX200 (miguser) #> start_serial_jobs
Serial Job Start Time (1=Now, 2=Delayed) [Now ] 2
Please specify a Date & Time (in <MMddhhmmCCYY> format)
when the serial schduled jobs should start. This should be
within the next 30 days. [ ] 121215002009
Started serial scheduled [migration | compare ] jobs
All attribute values for that have been changed will now be saved.
5-22 ISR654606-00 A
Page 97
5–Command Line Interface
compare_luns add
compare_luns add
Schedules a standalone LUN compare job. You can name the job and associate it with a job group. Scheduling options include: immediately, at a pre-defined later time, or by serial scheduling. Serial scheduling requires that you assign a priority to the job, which will be used to schedule it prior to (lower priority value) or after (higher priority value) a specific job in the serial schedule queue of jobs.
Session miguser
Example The following example shows the compare_luns add command:
MPX200 (miguser) #> compare_luns add
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
MPX200 <2> (admin) (miguser) #> compare_luns add
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
Index WWPN, PortId Symbolic Name Target Type
----- --------------------------------- -------------------- ------------
0 20:78:00:c0:ff:d5:9a:05, 8c-01-ef HP MSA2012fc-0 Src+Dest
1 50:00:1f:e1:50:0a:37:18, 82-01-00 HP HSV210-3 Src+Dest
Please select a Source Target from the list above ('q' to quit): 1
Index (VpGroup Name)
----- --------------
1 VPGROUP_1
2 VPGROUP_2
3 VPGROUP_3
4 VPGROUP_4
Please select a VPGroup for Source Lun ('q' to quit): 1
LUN Vendor LUN Size( GB) Attributes
--- ------ -------------- ----------
1 HP 10.00 SRC LUN
ISR654606-00 A 5-23
Page 98
5–Command Line Interface compare_luns add
2 HP 10.00
3 HP 20.00
4 HP 20.00
5 HP 10.00
6 HP 5.00
7 HP 5.00
8 HP 5.00
Please select a LUN as a Source Lun ('q' to quit): 1
Index WWPN, PortId Symbolic Name Target Type
----- --------------------------------- -------------------- ------------
0 20:78:00:c0:ff:d5:9a:05, 8c-01-ef HP MSA2012fc-0 Src+Dest
1 50:00:1f:e1:50:0a:37:18, 82-01-00 HP HSV210-3 Src+Dest
Please select a Destination Target from the list above ('q' to quit): 1
Index (VpGroup Name)
----- --------------
1 VPGROUP_1
2 VPGROUP_2
3 VPGROUP_3
4 VPGROUP_4
Please select a VPGroup for Destination Lun ('q' to quit): 1
LUN Vendor LUN Size( GB) Attributes
--- ------ -------------- ----------
1 HP 10.00 SRC LUN
2 HP 10.00
3 HP 20.00
4 HP 20.00
5 HP 10.00
6 HP 5.00
7 HP 5.00
8 HP 5.00
Please select a LUN as a Destination Lun('q' to quit): 2
I/O Size (0=32KB, 1=64KB, 2=128KB, 3=512KB, 4=1MB) [64KB ]
Please Enter a Job Description (Max = 64 characters)
default name [ HP HSV210-3:VPG1:001 to HP HSV210-3:VPG1:002 ]
5-24 ISR654606-00 A
Page 99
5–Command Line Interface
compare_luns add
Index Group Owner Group Name
----- ----------- ----------
0 2 Group 0
Please select a Group that this Job should belong to [0]
Start Time (1=Now, 2=Delayed, 3=JobSerialScheduling, 4=ConfigureOnly) [Now ]
Successfully created Job
All attribute values for that have been changed will now be saved.
ISR654606-00 A 5-25
Page 100
5–Command Line Interface compare_luns rm
compare_luns rm
Deletes a LUN compare job.
Session miguser
Example The following example shows the compare_luns rm command:
MPX200 (miguser) #> compare_luns rm
Job Type Status Job Description
ID
--- ---- ------------------------ -------------------------------------
0 Offline Verify Running HP HSV200-0:0001 to DGC RAID-1:0000
Please select a Job Id from the list above ('q' to quit): 0
Do you wish to continue with the operation(yes/no)? [No] yes
All attribute values for that have been changed will now be saved.
5-26 ISR654606-00 A
Loading...
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use