Implement high-availability solutions with HP Instant Capacity - easily and effectively

As before, failback to Server 1 can be accomplished simply by deactivating cores on server 2 and activating cores on

server 1 (the normal method of usage rights migration within a GiCAP group):

db2> icapmodify -d 12 OR OA2>icapmodify –p2 –d 12

db4> icapmodify -d 8 OR OA2>icapmodify –p4 –d 8

db1> icapmodify -a 15 OR OA1>icapmodify –p1 –a 15

db3> icapmodify -a 12 OR OA1>icapmodify –p3 –a 12

To return Db3 to its original state, we activated 12 cores, even though only eight cores were activated on the failover

partition Db4. We assumed the four seized usage rights that were not deployed to the failover partition Db4 remained

unused in the group; otherwise, the last activation might fail. (Or additional deactivations would be necessary.)

Alternatively, you can deactivate cores on server 2 and then use the restore command—(icapmanage -z) on the

Group Manager system, before rebooting server 1:

db2> icapmodify -d 12 OR OA>icapmodify –p2 –d 12

db4> icapmodify -d 8 OR OA>icapmodify –p4 –d 8

ap1> icapmanage -z OA1

In this case, no activations are necessary on Db1 or Db3, the restore automatically restores all seized usage rights. In

this example, the restore returns all 27 seized usage rights to server 1. Again, this is only possible if the usage rights had

either remained unused, or were otherwise deactivated before the restore.

Use the restore method if you want to restore usage rights before rebooting the failed partitions, or when you do not

want to specify the number of seized rights to restore. (The restore command is rejected if there are not enough usage

rights available for the restore.)

Recovery from a failure involving virtual partitions

While rights modification operations can be performed in a vPar environment, the rights seizure always operates on, and

affects, the entire server.

Some vPars down (migrate rights with vparmodify and icapmodify). If a subset of vPars within the nPartition are down

and you want to distribute those usage rights to other partitions in the group, you must use techniques other than rights

seizure. When the vPar is down, the usage rights of that partition will be available with the OA.

Activate cores in any other partition of the GiCAP group using the released core usage rights by running the following

command on that partition:

icapmodify –a <n>

Or, run the following from the OA:

icapmodify –p <partition number> -a <n>