Accelerating the migration of an SBR Reconfiguration Plan (by clicking Accelerate) is generally a better option than cancelling an SBR Reconfiguration Plan.
Accelerating the migration for a binding database reconfiguration causes the binding audit to look for non-migrated bindings. If such a binding is found, an RAR is sent to the policy client that created the binding, including a Session-Release-Cause AVP asking the policy client to terminate the session. When the policy client terminates the session and creates a new session, that record is created in the target and is successfully migrated.
Accelerating the migration for a session database reconfiguration causes the session to look for non-migrated binding capable sessions. If such a session is found, an RAR is sent to the policy client that created the binding capable session, including a Session-Release-Cause AVP asking the policy client to terminate the session. When the policy client terminates the session and creates a new session, that record is created in the target and is successfully migrated. Acceleration of a session database reconfiguration has no effect on binding dependent or binding independent sessions. However, such sessions are short-lived and are less likely to hinder migration.
Accelerating migration causes signaling disruptions since binding capable sessions are being torn down and recreated. However, split bindings do not occur.