# Recovering a Failed Application Group Member

There are different procedures to follow when recovering a failed MiVoice Business system that is a member of an AMC application group. The procedure you should use depends on several considerations including whether the failed system is the acting Designated License Manager
The Designated License Manager (DLM) connects with an Application Group on the AMC in order to obtain licenses which may then be shared among the group members. The DLM also tracks license usage and violations for the group, and provides statistics to the AMC. The DLM requires a Group Application Record ID (GARID) with Enterprise License Sharing enabled. (DLM) of the application group, whether you have a current backup of the system database, and whether the hardware ID has changed. Begin by reviewing the four scenarios below to identify the procedure that applies to your situation.

## Scenario 1

### Conditions

- You have a current backup from the system taken while it was in the application group.

- The ARID
  See Application Record ID. in the backup matches the ARID you will use on the recovered system.

- The Hardware ID
  When the installation of the MiVoice Business software is complete, it generates a unique Hardware ID that includes the MAC address of the controller. The DLM uses the Hardware ID and the Application Record ID to identify itself to the AMC. Upon synchronization with the AMC, purchased software and options for the application group become available. has not changed.

- The system is not the acting DLM.

### Procedure

1. Repair the system and return it to service. (See the Technician’s Handbook for hardware replacement procedures.)

2. Install the appropriate MCD 5.0 or later software. (See the Technician’s Handbook for instructions.)

3. License the system.

4. Restore the database.

5. From the DLM, go to the Network Elements form and sync the Application Group Licensing to all members of the group.

6. Resolve any SDS Distribution Errors or license violations that arise.

##
Scenario 2

### Conditions

- Same as Scenario 1 except the system is acting as the DLM.

### Procedure

1. Complete the steps for Scenario 1.

2. On the DLM,

- Navigate to Application Group Licensing form.

- Click Change.

- Verify that the GARID is correct.

- Click Save.

This syncs the group DLM data with AMC. If a License Violation caused by an incomplete application group occurs, click Change in the Application Group Licensing form, followed by No. Write down the GARID, then click Save. Go back into the form, click Change, followed by Yes, enter the GARID, and then click Save. This will reform the Application Group membership. Finish by syncing to the peers from the Network Element form in the DLM.

3. Resolve any SDS Distribution Errors or license violations that arise.

##
Scenario 3

### Conditions

- You have a current backup from the system taken while it was in the application group.

- The system may be the acting DLM or an application group member only.

- The ARID in the backup matches the ARID you will use on the recovered system.

- The hardware ID has changed. (Different controller, deployed new OVA
  Open Virtual Appliance (or Application) is a single file distribution of the OVF (Open Virtualization Format) file package, stored in the TAR format. See OVF for more information., rebuilt ISS server, etc.)

### Procedure

1. Repair the system and return it to service. (See the Technician’s Handbook for hardware replacement procedures.)

2. Install the appropriate MCD 5.0 or later software. (See the Technician’s Handbook for instructions.)

3. On AMC clear the hardware ID for the appropriate ARID.

4. License the system.

5. Restore the database.

6. On the DLM,

- Navigate to Application Group Licensing form.

- Click Change.

- Verify that the GARID is correct.

- Click Save.

This syncs the group DLM data with AMC.

7. From the DLM, go to the Network Elements form and sync the Application Group Licensing to all members of the group.

8. Resolve any SDS Distribution Errors or license violations that arise.

##
Scenario 4

### Conditions

- The backup you have is old, maybe from before group licensing was enabled or from pre MCD 5.0.

- The system is not the acting DLM

- The ARID in the backup matches the ARID you will use on the recovered system.

- The hardware ID has not changed.

### Procedure

1. Repair the system and return it to service. (See the Technician’s Handbook for hardware replacement procedures.)

2. Install the appropriate MCD 5.0 or later software. (See the Technician’s Handbook for instructions.)

3. License the system.

4. On a different system in the application group that is up and running take a screen capture of the Application Group License Distribution form data. This will allow you to reallocate the required licenses in a later step.

5. On the system you are recovering, go to the Network Elements form and add the system name as it appears in the Network Elements form of the other application group members.

6. From another member of the application group, go to the Network Elements form and sync with no forms selected to the recovered system.

7. On the DLM

- Navigate to Application Group Licensing form.

- Click Change.

- Verify that the GARID is correct.

- Click Save.

This syncs the group DLM data with AMC.

8. From the DLM, go to the Network Elements form and sync the Application Group Licensing to all members of the group.

9. On the system you are recovering,

- allocate the required licenses based on the data captured in step 5 above

- restore the database.

10. Resolve any SDS Distribution Errors or license violations that arise.

Related Topics

- Replacing a DLM

- Removing an Application Group Member