During this section the restored HP IO database will be updated. In the first phase, the mxsync tool will analyze the scheduled, pending approval or in-progress requests. To prevent the HP IO service from attempting to restart requests that may have already completed, during the execution step of this phase, the mxsync tool will terminate requests that were in-progress when the backup was taken or scheduled to run before the restore. The list of requests to be terminated will be displayed during the analysis step.
+---+
| Section 4 of 5 |
| Insight Orchestration | +---+
Terminate active requests, remove deleted services, and update allocated IP addresses.
**** Analysis: Terminate active requests. ****
**** Section 4 of 5, phase 1 of 3 ****
HPIO requests that were in-progress when the backup was taken, or scheduled to run before the restore, will be terminated. This will prevent HPIO from resuming requests that may have already completed.
Checking for active requests...[OK]
CREATE for S104_VM_Test is PAUSED_FOR_APPROVAL...[ACTION]
ISSUE: HPIO requests that are in an active state may cause undesirable results if they are resumed on HPIO restart. Requests scheduled for a future date will be preserved.
RESOLUTION: 1 request(s) will be terminated and marked as CANCELED.
Analysis completed successfully. You may choose to execute synchronization actions now or stop the synchronization process. If the synchronization process is stopped, it can be started again later.
>>> Would you like to perform the actions now? (Y/N): y
**** Execution: Terminate active requests. ****
**** Section 4 of 5, phase 1 of 3 ****
Terminating CREATE request for service S104_VM_Test...[OK]
Execution summary:
1 action performed 0 advisories 0 errors
>>> Please press [ENTER] to continue:
During the second phase, you will be asked to identify services that have been deleted after backup.
To help with this effort the mxsync tool will create a file,
<HPSIM>\mxsync\data\InfrastructureServices.txt, containing a list of the HP IO services defined in the restored database. Prior to performing the execution step, you will be asked to edit the generated file and mark, with a ‘*’, the services that have been deleted. The modified InfrastructureServices.txt file is shown in Figure 9.
**** Analysis: Remove deleted services. ****
**** Section 4 of 5, phase 2 of 3 ****
HPIO services in the restored database may have been been deleted after the backup was taken. If so, in this phase you can delete these services from the restored database.
>>> The file C:\Program Files\HP\Systems Insight
Manager\mxsync\data\InfrastructureServices.txt exists, would you like to use this file? (Y/N): n
File InfrastructureServices.txt renamed to InfrastructureService (3).txt The following infrastructure services were found in HPIO database:
Checking S100_VM_Test
AVAILABLE, Lease End: 11/04/2009 23:30:00...[OK]
Checking S2_VC_Test
AVAILABLE, Lease End: 11/04/2009 23:30:00...[OK]
Checking S1_VC_Test
AVAILABLE, Lease End: 11/04/2009 23:30:00...[OK]
Checking S101_VM_Test
AVAILABLE, Lease End: 11/04/2009 23:30:00...[OK]
Checking S5_VC_Test
AVAILABLE, Lease End: 10/05/2009 23:30:00, Expired...[OK]
Checking S103_VM_Test
AVAILABLE, Lease End: 11/05/2009 23:30:00...[OK]
Checking S4_VC_Test
AVAILABLE, Lease End: 11/05/2009 23:30:00...[OK]
Found: 7 infrastructure services in HPIO database.1 are expired.
Infrastructure services list saved in: C:\Program Files\HP\Systems Insight Manager\mxsync\data\InfrastructureServices.txt
Identify already deleted services...[INPUT]
ISSUE: Failure to remove infrastructure services that were deleted after the backup was taken will result in available resources being marked as in use.
RESOLUTION: Expired services will be automatically deleted. To delete other services, modify the
"InfrastructureServices.txt" file and mark the services that were deleted after the backup was taken.
ADVISORY: It is not mandatory to identify all post-backup deleted services. After resynchronization, you can use HPIO to remove them. However, it is recommended that you remove these services now, to free up the compute, storage, and network resources allocated to them.
Analysis summary:
8 checks performed
>>> Would you like to perform the actions now? (Y/N): y
**** Execution: Remove deleted services. ****
**** Section 4 of 5, phase 2 of 3 ****
Checking data\InfrastructureServices.txt
Found 3 infrastructure services marked for deletion.
S5_VC_Test: AVAILABLE, lease end: 10/05/2009 23:30:00, Expired S103_VM_Test: AVAILABLE, lease end: 11/05/2009 23:30:00
S4_VC_Test: AVAILABLE, lease end: 11/05/2009 23:30:00
>>> Are you sure that you want to delete these service(s)? (Y/N): y
Deleting S5_VC_Test...[OK]
Deleting S103_VM_Test...[OK]
Deleting S4_VC_Test...[OK]
Preserving file at "C:\Program Files\HP\Systems Insight Manager\mxsync\data\InfrastructureServices.20091006223052"
Execution summary:
3 actions performed 0 advisories
0 errors
>>> Please press [ENTER] to continue:
Figure 9. Contents of InfrastructureServices.txt file.
During the third phase, you will be given the opportunity to update the status of the dynamic and static IP addresses allocated to the defined HP IO networks. To help with this effort the mxsync tool will create a file, <HPSIM>\mxsync\data\network_analysis.txt, containing a list of the allocated IP addresses. Prior to performing the execution step, you will be asked to update the file to add any IP addresses that have been allocated after backup. The modified network_analysis.txt file is shown in Figure 10.
**** Analysis: Update allocated IP Addresses. ****
**** Section 4 of 5, phase 3 of 3 ****
HPIO maintains pools of available IP addresses for each network. IP addresses allocated after the backup was taken are marked as free in the restored
database. In this phase you can mark these IP addresses as in-use.
already exists. Would like to use this file in the execution step? (Y/N): n ADVISORY: The output file "network_analysis.txt" already exists. It
has been renamed to "network_analysis(3).txt" and a new
"network_analysis.txt" has been created.
Comparing network data files with restored HPIO database...[OK]
Identify additional IP addresses in use...[INPUT]
ISSUE: New IP addresses might have been allocated since the backup was taken.
RESOLUTION: You can specify dynamic and static IP addresses that have been allocated since the backup was taken.
Modify the file "C:\Program Files\HP\Systems Insight Manager\mxsync\data\network_analysis.txt" to add them. It contains the list of all in use IP addresses for each network.
ADVISORY: Failure to identify IP addresses that were allocated after the backup was taken may result in two servers with the same IP address. This will cause duplicate IP Addresses in your environment.
Analysis completed successfully. You may choose to execute synchronization actions now or stop the synchronization process. If the synchronization process is stopped, it can be started again later.
>>> Would you like to perform the actions now? (Y/N): y
**** Execution: Update allocated IP Addresses. ****
**** Section 4 of 5, phase 3 of 3 ****
Adding to HPInternalNetwork:
Static addresses: [15.186.24.83]
Adding to VM Network:
1 new DHCP addresses
>>> Are you sure you want to add these IP addresses? (Y/N): y
Adding IP address 15.186.24.83 to network HPInternalNetwork...[OK]
Adding 1 DHCP addresses to network VM Network...[OK]
Preserving file at "C:\Program Files\HP\Systems Insight Manager\mxsync\data\network_analysis.20091006223151"
Execution summary:
2 actions performed 0 advisories
0 errors
>>> Please press [ENTER] to continue:
Figure 10. Contents of network_analysis.txt file.
The iosync –IPDeletionTask command can be used to reclaim IP addresses once the server using the IP address is no longer in service or provisioned. In the example shown in Figure 11the IP addresses 15.186.24.80 and 15.186.24.84 are returned to the HP IO Usable IP Address Space. The contents of the network_deletion.txt file are shown in Figure 12.
Figure 11. iosync -IPDeletionTask command example.
Figure 12. Contents of the network_deletion.txt file.