HP NetServer AA 4000 HP AA HP Netserver 4000 Reference Guide - Page 47

Server Shutdowns and Reboots, Avoiding Unnecessary Re-Mirror Operations

Get HP NetServer AA 4000 PDF manuals and user guides View all HP NetServer AA 4000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 47 highlights

Ch 2: HPAA System Boot Up Server Shutdowns and Reboots By now, it is apparent that MTCCONS or the Marathon Manager can be used to change the status of a component or the entire system. Server shutdown commands are no different. The most important aspect of a server shutdown to note is not the command to execute a shutdown, but instead knowing how to perform an actual shutdown and not just a reboot. Whenever a 'shutdown' command is issued, the array will attempt to reboot. If an actual shutdown is desired, then power off the servers before they can reboot. One other way to prevent the servers from trying to be a part of the array after a shutdown is not to issue a shutdown command, but rather, issue a disable command. Just remember, any component that has been disabled must be manually re-enabled; the AA 4000 software does not automatically enable components. Avoiding Unnecessary Re-Mirror Operations When performing shutdown commands, it is imperative to understand that any shutdown of an IOP while a CE is still active will result in a full disk re-mirror when the IOP is brought back online. If the intent is to perform maintenance on the system as a routine and steps have been taken to not require system availability, make sure to shutdown CEs before IOPs. CAUTION A disk re-mirror takes approximately 4 - 5 minutes per Gigabyte of disk space. Re-mirrors are not just the data, it is a block-by-block operation. Network Server Division 2-21

  • 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
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
Ch 2: HPAA System Boot Up
Network Server Division
2-21
Server Shutdowns and Reboots
By now, it is apparent that MTCCONS or the Marathon Manager can
be used to change the status of a component or the entire system.
Server shutdown commands are no different.
The most important
aspect of a server shutdown to note is not the command to execute a
shutdown, but instead knowing how to perform an actual shutdown
and not just a reboot.
Whenever a ‘shutdown’ command is issued, the array will attempt to
reboot.
If an actual shutdown is desired, then power off the servers
before they can reboot.
One other way to prevent the servers from
trying to be a part of the array after a shutdown is not to issue a
shutdown command, but rather, issue a disable command.
Just
remember, any component that has been disabled must be manually
re-enabled; the AA 4000 software does not automatically enable
components.
Avoiding Unnecessary Re-Mirror Operations
When performing shutdown commands, it is imperative to
understand that any shutdown of an IOP while a CE is still active
will result in a full disk re-mirror when the IOP is brought back
online.
If the intent is to perform maintenance on the system as a
routine and steps have been taken to not require system availability,
make sure to shutdown CEs before IOPs.
CAUTION
A disk re-mirror takes approximately 4 – 5 minutes per
Gigabyte of disk space.
Re-mirrors are not just the data, it
is a block-by-block operation.