Hp XP Racks Bedienungsanleitung Seite 1

HP XP7 Auto LUN User GuideAbstractThis document describes and provides instructions for using Auto LUN to migrate volumes on the HP XP7 Storage system

Table 2 Candidates for source and target volumes by program product (continued)Target Volume Candidate?Source Volume Candidate?Volume Type/StatusProgr

Table 2 Candidates for source and target volumes by program product (continued)Target Volume Candidate?Source Volume Candidate?Volume Type/StatusProgr

Table 2 Candidates for source and target volumes by program product (continued)Target Volume Candidate?Source Volume Candidate?Volume Type/StatusProgr

must ensure that the capacity of a Thin Provisioning or Thin Provisioning Z virtual volume is notincreasing if you plan on using that virtual volume i

Table 5 Poor target volume candidates for Cnt Ac-S/Cnt Ac-J pair combinationsPoor Target Volume CandidateSource VolumeContinuous Access Synchronous or

Table 6 Pair status when primary volume of Continuous Access Journal Z delta resync pair is as asource volumeStatusPair NameSUSPEND or DUPLEXContinuou

Figure 4 3DC multi-target configurationTable 8 Pair status when primary volume of Continuous Access Journal delta resync pair is a sourcevolumeStatusP

Table 10 Access attributes and permissible Auto LUN operationsOperations from RAID ManagerOperations from Remote Web ConsoleAccess attributes oftarget

NOTE: A source volume exchanges the role with a target volume by the Auto LUN operation.However, the access attribute of the source volume and the tar

3 Auto LUN planningThis topic provides information about Auto LUN planning.Migration plansTo migrate volumes, you must create migration plans. A migra

© Copyright 2014 Hewlett-Packard Development Company, L.P.Confidential computer software. Valid license from HP required for possession, use or copyin

Table 13 Number of control cylinders based on emulation type (continued)Number of Control CylindersEmulation Type233390-L, 3390-LA, 3390-LB533390-A, 3

Total number of differential tables per migration plan = (X ÷ 256) ÷ ZThe variables are explained below:• X: The capacity of the volume to be migrated

Table 15 The number of differential tables, pair tables and system volumes per additional sharedmemory typethe number of systemvolumesthe number of pa

4 Auto LUN operationsThis topic contains operations performed in the Auto LUN window.Migrating a volumeA volume can be migrated through the Migration

Prerequisite• You must have the Storage Administrator (View only) role to perform this task.To view migration plans:Click Actions > Logical Device

Prerequisite• You must have the Storage Administrator (Provisioning) role to perform this task.Procedure 3 To delete all history logs:1. Click Actions

5 Auto LUN monitoringThis topic contains the system messages that appear in Auto LUN history logs.Migration History messagesThe following table contai

NOTE: Copy operations that are stopped by the Copy Threshold option will resume once theload on the storage system becomes light.Effects of Auto LUN o

6 TroubleshootingThis topic gives troubleshooting information on Auto LUN.Troubleshooting Auto LUNAn error message appears on the Remote Web Console w

7 Support and other resourcesContacting HPFor worldwide technical support information, see the HP support website:http://www.hp.com/supportBefore cont

Contents1 Overview of Auto LUN...5Overview of Auto LUN...

HP websitesFor additional information, see the following HP websites:• http://www.hp.com• http://www.hp.com/go/storage• http://www.hp.com/service_loca

Table 19 Document conventions (continued)ElementConventionMonospace text• File and directory names• System output• Code• Commands, their arguments, a

A Using RAID Manager for Auto LUNUse RAID Manager from an open-system host to perform migration operations on open-system andmainframe volumes.Auto LU

• If you delete an Auto LUN plan, the volume status changes from SMPL(PD) to SMPL. You cancheck the status of the volume by viewing the list at the bo

Table 20 RAID Manager errors related to migration plans (continued)Required ActionMessageError Code(SSB2)Release the volume from Continuous AccessJour

Table 20 RAID Manager errors related to migration plans (continued)Required ActionMessageError Code(SSB2)Wait until the capacity increase is completed

Table 20 RAID Manager errors related to migration plans (continued)Required ActionMessageError Code(SSB2)The volume cannot be migrated. Check theconfi

Table 20 RAID Manager errors related to migration plans (continued)Required ActionMessageError Code(SSB2)Release the volume from Auto LUN, and thenmig

Table 20 RAID Manager errors related to migration plans (continued)Required ActionMessageError Code(SSB2)The volume cannot be migrated. Check theconfi

B Auto LUN GUI referenceThe GUI elements of Auto LUN windows are summarized.Auto LUN wizardRelated links:“Migrating a volume” (page 23)Migrate Volumes

Subscription service...29Documentation feedba

Selected Source Volume table• TableDescriptionItemSelected LDEV's identifierLDEV IDSelected LDEV's nameLDEV NameID for the parity group. The

Available Target Volumes tableDescriptionItemSelected LDEV's identifierLDEV IDSelected LDEV's name.LDEV NameThis field is blank if the LDEV

Selected Migration Plans table• TableDescriptionItemSource Volume◦ LDEV ID: Source volume's LDEV identifier◦ LDEV Name: Selected LDEV's name

• ButtonDescriptionItemWhen clicked, removes the migration plan from the table.RemoveSelect Source Volume windowProvisioning TypeTypes of LDEV which c

DescriptionItemDisplays the data drive type and RPM of the source volume.Drive Type/RPMIndicates the number and name of the CLPR corresponding to the

Confirm windowDescriptionItemSource Volume• LDEV ID: Source volume's LDEV identifier• LDEV Name: Selected LDEV's name. This field is blank i

DescriptionItemRAID Level: The RAID level of the target volume•• Emulation Type: The emulation type of the target volume• Capacity: The target volume&

Migration Plans tableMigration Plans window 47

• TableDescriptionItemSource Volume◦ LDEV ID: Source volume's LDEV identifier◦ LDEV Name: Selected LDEV's name. This field is blank if the L

DescriptionItem◦ LDEV ID: Target volume's LDEV identifier◦ LDEV Name: Selected LDEV's name. This field is blank if the LDEV name is notset.◦

1 Overview of Auto LUNThis is an overview of Auto LUN.Overview of Auto LUNAuto LUN is used to optimize your data storage by balancing resource utiliza

Delete Migration Plans window50 Auto LUN GUI reference

Selected Migration Plans tableDescriptionItemSource Volume• LDEV ID: Source volume's LDEV identifier• LDEV Name: Selected LDEV's name. This

Histories windowHistories (Page.x) table• TableDescriptionItemOperation date and timeDate and TimeThe name of the operationActionSource Volume◦ LDEV I

• ButtonDescriptionItemWhen clicked, deletes all histories information.Delete All HistoriesWhen clicked, outputs the history information.ExportRelated

Glossaryallocation The ratio of allocated storage capacity versus total capacity as a percentage. Allocated storagerefers to those logical devices (LD

to be associated with 1 to 36 LDEVs. Essentially, LUSE makes it possible for applications to accessa single large pool of storage.M-VOL Main volume.MC

IndexAauto LUNwindow, 39Ccalculating differential tablesfor a mainframe volume, 19candidates for source and target volumes, 9contacting HP, 29control

is repeated until all differential data on the source volume is copied. The following figure illustratesthe data flow during a migration operation.Fig

When to use volume migrationIn the following scenarios, you must perform a migration plan:• To analyze processor and access path usage• To migrate ext

2 RequirementsThis topic provides information about Auto LUN requirements.System requirementsTo perform Auto LUN operations using Remote Web Console o

Table 1 Information about whether you can create migration plans when using Resource Partition(continued)Resource groups where target volumes belongRe