Procedure 20 RESTORE SERVDI BACKUP

3.6.6 Procedure 20 RESTORE SERVDI BACKUP

Table 3-24 Procedure 20 RESTORE SERVDI BACKUP

STEP # This procedure restores the SERVDI Backup to the ELAP. Note: Estimated time of completion is 30 minutes. Check off (✓) each step as it is completed. Boxes have been provided for this purpose under each step number. Should this procedure fail, Contact Oracle technical services and ask for FULL UPGRADE ASSISTANCE.

STEP #	This procedure restores the SERVDI Backup to the ELAP. Note: Estimated time of completion is 30 minutes. Check off (✓) each step as it is completed. Boxes have been provided for this purpose under each step number. Should this procedure fail, Contact Oracle technical services and ask for FULL UPGRADE ASSISTANCE.
1. ☐	Active ELAP GUI: Using the new Virtual IP address (VIP) configured in step Procedure 12, Step 5 of Procedure 13, login to Active ELAP.
2. ☐	Active ELAP GUI: Expand the “Process Control” folder. Select the “Stop Software” link.
3. ☐	Active ELAP GUI: In the right panel, click on the “Stop ELAP Software” button.
4. ☐	ELAP A GUI: A message indicating that the ELAP software has been successfully halted should appear in the right panel.
5. ☐	ELAP-A G 1) Expand the “RTDB” folder. 3.6.1.1 2) Expand the “Maintenance” sub-folder. 3) Select the “Restore RTDB” link.
6. ☐	ELAP-A GUI: Select the database file radio button. Click on the “Restore RTDB from the Selected File” button.
7. ☐	ELAP A GUI: Click on the “Confirm RTDB Restore” button.
8. ☐	ELAP A GUI: A message showing that the RTDB Restore has been successfully started should appear in the right frame.
9. ☐	3.6.1.2 ELAP A GUI: The GUI banner should begin displaying the message shown to the right.
10. ☐	ELAP A GUI: The messages shown to the right display the stages of the RTDB Restore. Monitor these messages in the GUI banner as the process progresses.
11. ☐	ELAP A: The banner messages may alternatively be viewed from the command line using the “manageBannerInfo” command. NOTE: During this transitory state, access to the ELAP-A GUI may terminate unexpectedly. If sustained GUI access is problematic at this time, you may monitor these messages from the ELAPA command line.	`[elapdev@E5APP-B-a ~]$ manageBannerInfo -l ID: RESTORE_RTDB_STATUS SIDE: A MSG: RTDB restore 51 percent complete SetTime: 2016-05-19 10:29:13 ClearTime: 0000-00-00 00:00:00 [elapdev@E5APP-B-a ~]$`
12. ☐	ELAP A: If monitoring from the ELAP-A command line, the messages shown to the right display the stages of the RTDB Restore.	`MSG: RTDB restore started MSG: RTDB restore 13 percent complete MSG: RTDB restore completed successfully MSG: RTDB restore recompressing backup file There are currently no BannerInfo messages for this side in the database.`
13. ☐	ELAP A GUI: Expand the “Process Control” folder. Select the “Start Software” link.
14. ☐	ELAP A GUI: In the right panel, click on the “Start ELAP Software” button.
15. ☐	ELAP A GUI: A message indicating that the ELAP software has been successfully started should appear in the right panel.
16. ☐	ELAP A GUI: 3.6.1.3 1) Expand the “RTDB” folder. 2) Select the “View RTDB Status” link.
17. ☐	ELAP A GUI: Verify the “DB Status” and the “RTDB Level” shown in the right panel.
18. ☐	ELAP A GUI: Record the “DB Status” and the “RTDB Level” shown in the previous STEP.	`DB` `Status =` `______________________` `3.6.1.4` `RTDB` `Level =` `______________________`
19. ☐	LSMS: Login to the LSMS CLI as the “lsmsadm” user.
20. ☐	LSMS: Login to the LSMS CLI as the “lsmsadm” user.	`lsmsadm@<ISMS IP>'s password:` `Last login: Wed` `Jul 9` `18:40:24 2008 from 10.25.150.101 [lsmsadm@lsmspri` `~]$`
21. ☐	LSMS: Execute an “eagle status” command to verify the current status of the CLLI (EMS site being fully upgraded to 10.1).	`[lsmsadm@lsmspri ~]$ eagle status CLLI Pid State Resync Conn A Conn B EBDA Debug Queue Memory CPU Timestamp ELAP21 32269 A_ACTIVE COMPLETE ACTIVE --- IDLE OFF 0 % 500 M 0.0 % 17:42:59 STPA 15565 NONE_ACTIVE NO_CONNECTION DOWN --- IDLE OFF 0 % 500 M 0.0 % 17:43:00`
22. ☐	LSMS: Execute an “eagle stop” command using the CLLI of the EMS site being migrated to 11.0.	`[lsmsadm@lsmspri ~]$ eagle stop ELAP21 eagle: Stopping... eagle: eagleagent ELAP21 stopped at Wed Apr 27 17:43:25 2016`
23. ☐	LSMS: Execute an “eagle start” command using the CLLI of the EMS site being fully upgraded to 11.0.	`[lsmsadm@lsmspri ~]$ eagle start ELAP21 eagle: Starting... eagle: eagleagent ELAP21 started at Wed Apr 27 17:43:48 2016`
24. ☐	LSMS: Execute an “eagle status” command using the CLLI of the EMS site being fully upgraded to 11.0. Verify that the “State” and the “Connection VIP” reflect the values shown to the right.	`[lsmsadm@lsmspri ~]$ eagle status ELAP21 eagleagent: CLLI = ELAP21 Pid = 3110 State = NONE_ACTIVE Resync = NO_CONNECTION Connection VIP = ACTIVE EBDA = IDLE Debug logging = OFF Pending queue = 0 of 2000000 bytes (0%) Keepalive timestamp = Wed Apr 27 17:45:19 IST 2016 Virtual memory = 500308 K bytes CPU usage = 0.0 %`
25. ☐	ELAP A GUI: Note down the timestamp in log.	Run the following command: `$ date`

☐

Active ELAP GUI:

Using the new Virtual IP address (VIP) configured in step Procedure 12, Step 5 of Procedure 13, login to Active ELAP.

☐

Active ELAP GUI:

Expand the “Process Control” folder.
Select the “Stop Software” link.

ELAP Process Control menu with Stop Software indicated.

☐

Active ELAP GUI:

In the right panel, click on the “Stop ELAP Software” button.

☐

ELAP A GUI:

A message indicating that the ELAP software has been successfully halted should appear in the right panel.

Confirmation that ELAP software has stopped.

☐

ELAP-A G

1) Expand the “RTDB” folder.

3.6.1.1 2) Expand the “Maintenance” sub-folder.

3) Select the “Restore RTDB” link.

ELAP RTDB Maintenance menu with Restore RTDB highlighted.

☐

ELAP-A GUI:

Select the database file radio button.
Click on the “Restore RTDB from the Selected File” button.

Restore RTDB screen with the backup file selected.

☐

ELAP A GUI:

Click on the “Confirm RTDB Restore” button.

Confirmation to restore RTDB from the selected backup file.

☐

ELAP A GUI:

A message showing that the RTDB Restore has been successfully started should appear in the right frame.

Confirmation that the RTDB restore has started.

☐

3.6.1.2 ELAP A GUI:

The GUI banner should begin displaying the message shown to the right.

RTDB restore message showing the backup file being uncompressed.

10.

☐

ELAP A GUI:

The messages shown to the right display the stages of the RTDB Restore.

Monitor these messages in the GUI banner as the process progresses.

11.

☐

ELAP A:

The banner messages may alternatively be viewed from the command line using the “manageBannerInfo” command.

NOTE: During this transitory state, access to the ELAP-A GUI may terminate unexpectedly. If sustained GUI access is problematic at this time, you may monitor these messages from the ELAPA command line.

[elapdev@E5APP-B-a ~]$ manageBannerInfo -l 
ID: RESTORE_RTDB_STATUS  SIDE: A 
MSG: RTDB restore 51 percent complete 
SetTime: 2016-05-19 10:29:13  ClearTime: 0000-00-00 00:00:00  
[elapdev@E5APP-B-a ~]$

12.

☐

ELAP A:

If monitoring from the ELAP-A command line, the messages shown to the right display the stages of the RTDB Restore.

MSG: RTDB restore started 
MSG: RTDB restore 13 percent complete 
MSG: RTDB restore completed successfully 
MSG: RTDB restore recompressing backup file 
There are currently no BannerInfo messages for this side in the database.

13.

☐

ELAP A GUI:

Expand the “Process Control” folder.
Select the “Start Software” link.

14.

☐

ELAP A GUI:

In the right panel, click on the “Start ELAP Software” button.

Start ELAP Software confirmation screen.

15.

☐

ELAP A GUI:

A message indicating that the ELAP software has been successfully started should appear in the right panel.

Confirmation that ELAP software has started.

16.

☐

ELAP A GUI:

3.6.1.3 1) Expand the “RTDB” folder.

2) Select the “View RTDB Status” link.

ELAP RTDB navigation menu showing View RTDB Status.

17.

☐

ELAP A GUI:

Verify the “DB Status” and the “RTDB Level” shown in the right panel.

ELAP RTDB Status screen with Coherent database status circled.

18.

☐

ELAP A GUI:

Record the “DB Status” and the “RTDB Level” shown in the previous STEP.

DB Status = ______________________

3.6.1.4 RTDB Level = ______________________

19.

☐

LSMS:

20.

☐

LSMS:

lsmsadm@<ISMS IP>'s password:

Last login: Wed Jul 9 18:40:24 2008 from 10.25.150.101 [lsmsadm@lsmspri ~]$

21.

☐

LSMS:

Execute an “eagle status” command to verify the current status of the CLLI (EMS site being fully upgraded to 10.1).

[lsmsadm@lsmspri ~]$ eagle status 
CLLI Pid State Resync Conn A Conn B EBDA Debug Queue 
Memory CPU Timestamp 
ELAP21 32269 A_ACTIVE COMPLETE ACTIVE --- IDLE OFF 0 % 500 
M 0.0 % 17:42:59 
STPA 15565 NONE_ACTIVE NO_CONNECTION DOWN --- IDLE OFF 0 % 500 M 0.0 % 17:43:00

22.

☐

LSMS:

Execute an “eagle stop” command using the CLLI of the EMS site being migrated to 11.0.

[lsmsadm@lsmspri ~]$ eagle stop ELAP21 
 eagle: Stopping... 
eagle: eagleagent ELAP21 stopped at Wed Apr 27 17:43:25 
2016

23.

☐

LSMS:

Execute an “eagle start” command using the CLLI of the EMS site being fully upgraded to 11.0.

[lsmsadm@lsmspri ~]$ eagle start ELAP21 
 eagle: Starting... 
eagle: eagleagent ELAP21 started at Wed Apr 27 17:43:48 
2016

24.

☐

LSMS:

Execute an “eagle status” command using the CLLI of the EMS site being fully upgraded to 11.0.
Verify that the “State” and the “Connection VIP” reflect the values shown to the right.

[lsmsadm@lsmspri ~]$ eagle status ELAP21 
 eagleagent: CLLI = ELAP21 
Pid = 3110 
State = NONE_ACTIVE 
Resync = NO_CONNECTION 
Connection VIP = ACTIVE 
EBDA = IDLE 
Debug logging = OFF 
Pending queue = 0 of 2000000 bytes (0%) 
Keepalive timestamp = Wed Apr 27 17:45:19 IST 2016 
Virtual memory = 500308 K bytes 
CPU usage = 0.0 %

25.

☐

ELAP A GUI: Note down the timestamp in log.

Run the following command:

$ date

This procedure is complete!