SBR Database Migration

3.2 SBR Database Migration

Perform the following procedure to migrate SBR data.

Run the following command on Active and StandBy SOAM to verify if the value is 1.
```
iqt -pE IdbParamDef where "param='IdbDisableUpgBarrier'"
```
If value is 0, then run the following command:
```
iset -fvalue=1 IdbParamDef where "param='IdbDisableUpgBarrier'"
sudo init 6
```
Run the below command on all 8.6.x SBR servers in this order:
1. Spare
2. Standby
3. Active
```
iset -fvalue=1 IdbParamDef where "param='IdbDisableUpgBarrier'"
sudo init 6
```
Note:
After restarting the server, wait till the server comes up and becomes serviceable. Then, run the above command on next server in the same server group.
Create new VMs for SBR Binding (Active, Standby and Spare).
Create new VMs for SBR Session (Active, Standby and Spare).
Add a new vDSR SBR-B/S in the existing path.
Create new server group for SBR-B/S consisting the vDSR 9.0.1 release.
Create new ResourceDomains for vDSR for both SBR-B/S.
Navigate to Status & Manage from Main Menu, then select Server. Click Restart, to enable the new vDSR SBR-B/S servers.
From Active NOAM, navigate to Configuration from Main Menu: SBR, then select SBR Database Resizing Plans.
Create new resizing plans for both binding and session. Keep BM SBR 8.6 as initial resource domain and vDSR 9.0.1 as target resource domain.
Navigate to Maintenance from Main Menu: SBR, then select SBR Database Reconfiguration Status.
Click Prepare for binding and session plan 1 by 1.
When status is in prepared state, click Start for binding and session resizing plan one after another.
Check if the vDSR SBR-B/S are created on all the new sessions and bindings.
Wait for existing binding and sessions to be cleared from BM.
When resizing is complete, perform the following steps:
- Remove BM SBR from the resource domain
- Change SBR Binding or Session MP role to OOS
- Remove BM SBR-B/S from Server group
- Remove BM SBR-B/S from Server configuration