Avamar: During r2r cutover from multinode to single-node, a lockbox offset error occurs.

Summary: During a Root to Root (r2r) migration from a multi to a single node migration the lockbox file fails to complete on the lockbox restore step. This error indicates that the client-offset field could not be updated on a specific node such as 0.1. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

The r2r process is interrupted due to the lockbox script failing to complete without errors. The script will request to update the Management Console Database (MCDB) offset field and after pressing 'yes' the script generates database error messages and terminates.

Cause

The script adjusts client-offset variables for a multinode system, but the target is a single-node system, which causes the mismatch. And the multinode cannot update the related node variable for the node in question. For example, 0.1 does not exist on the target so the script encounters an invalid parameter and terminates. 

 

The key is in line 1022 of the lockbox script. This is where the request is initiated for the update of the Management Console Server (MCS) client offset:

Use of uninitialized value $info{"NEW_VALUE"} in concatenation (.) or string at lockbox_restore.pl line 1022, <STDIN> line 5.

 

Resolution

This is the intended behavior as the target of the r2r is a single node server and there are no values associated with a multinode system. The script cannot complete updating the client messages offset field. This can be ignored as it is not strictly necessary to update offset to complete the r2r cutover. However, since the MCDB must be updated anyways it is still required to enter yes for the updates.

 

Note: During the r2r migration the script errors out, but once it finishes. It will go to the next step of updating the mcserver.xml file per the documentation.
Note: If no is selected instead of yes, the client messages script must be ran afterwards to resolve the MCDB client messages offset value manually. It is better to select yes and let the script error out and continue to the next steps.

 

Article Properties
Article Number: 000340091
Article Type: Solution
Last Modified: 23 مايو 2026
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.