HP EVA P6000 HP Enterprise Virtual Array Updating Product Software Guide (xcs1 - Page 39

Task checklist, HP Storage System Scripting Utility Reference, HP Storage System

Get HP EVA P6000 PDF manuals and user guides View all HP EVA P6000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 39 highlights

4. Enter CAPTURE CONFIGURATION, specifying the full paths and filenames of the output files for the configuration data. The configuration data is stored in a series of one to five files, which are scripts. The file names begin with the name you select, followed by the restore step. For example, if you specify a file name of LargeEVA.txt, the configuration files would be named LargeEVA_Step1A.txt, LargeEVA_Step1B.txt, etc. Files that do not contain configuration information are not created and therefore cannot be restored. You can view the contents of the configuration files with a text editor. 5. Enter exit. NOTE: You cannot use the utility to restore a configuration that contains disk drives of different capacities. You must manually restore that type of configuration. See "Restoring an array configuration with different disk sizes and types" in the HP Storage System Scripting Utility Reference for more information. TIP: When capturing the HP P6000 Command View configuration, it is a best practice to specify the SAVE ALL option. This captures critical data such as the WWN, which is useful for rebuilding the array configuration. You can run the CAPTURE VALIDATE command for each file generated by the CAPTURE CONFIGURATION command to determine if the file has been modified since the initial capture. As a best practice, also use the following commands to collect configuration data: • LS DISK_GROUP FULL • LS HOST FULL • LS VDISK FULL If applicable, use the following commands as well: • LS ISCSI_HOST FULL • LS ISCSI_LUN FULL For more information about using the utility or the CAPTURE commands, see the HP Storage System Scripting Utility Reference. See "Reference documentation" (page 6) for the link to this document. Task checklist Use the following checklist to track your progress and mark when a task is complete. Table 8 Pre-upgrade task checklist Task "Checking the controller software version" (page 8) Time required: About 5 minutes When to perform: Anytime before the upgrade Task complete "Checking management software versions" (page 8) Time required: 10-15 minutes When to perform: Anytime before the upgrade "Checking the array hardware" (page 10) Time required: 15-20 minutes When to perform: 1-2 weeks before the upgrade, and then daily until the upgrade is complete. Provide enough time to order and replace any failed components. Task checklist 39

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
4.
Enter
CAPTURE CONFIGURATION
, specifying the full paths and filenames of the output files
for the configuration data.
The configuration data is stored in a series of one to five files, which are scripts. The file names
begin with the name you select, followed by the restore step. For example, if you specify a
file name of
LargeEVA.txt
, the configuration files would be named
LargeEVA_Step1A.txt, LargeEVA_Step1B.txt
, etc. Files that do not contain
configuration information are not created and therefore cannot be restored.
You can view the contents of the configuration files with a text editor.
5.
Enter
exit
.
NOTE:
You cannot use the utility to restore a configuration that contains disk drives of different
capacities. You must manually restore that type of configuration. See “Restoring an array
configuration with different disk sizes and types” in the
HP Storage System Scripting Utility Reference
for more information.
TIP:
When capturing the HP P6000 Command View configuration, it is a best practice to specify
the
SAVE ALL
option. This captures critical data such as the WWN, which is useful for rebuilding
the array configuration.
You can run the
CAPTURE VALIDATE
command for each file generated by the
CAPTURE
CONFIGURATION
command to determine if the file has been modified since the initial capture.
As a best practice, also use the following commands to collect configuration data:
•
LS DISK_GROUP FULL
•
LS HOST FULL
•
LS VDISK FULL
If applicable, use the following commands as well:
•
LS ISCSI_HOST FULL
•
LS ISCSI_LUN FULL
For more information about using the utility or the
CAPTURE
commands, see the
HP Storage System
Scripting Utility Reference
. See
“Reference documentation” (page 6)
for the link to this document.
Task checklist
Use the following checklist to track your progress and mark when a task is complete.
Table 8 Pre-upgrade task checklist
Task complete
Task
“Checking the controller software version” (page 8)
Time required:
About 5 minutes
When to perform:
Anytime before the upgrade
“Checking management software versions” (page 8)
Time required:
10–15 minutes
When to perform:
Anytime before the upgrade
“Checking the array hardware” (page 10)
Time required:
15–20 minutes
When to perform:
1–2 weeks before the upgrade, and then daily until the upgrade is complete.
Provide enough time to order and replace any failed components.
Task checklist
39