Data migration fails during an upgrade of a secondary SAN Shared Storage Option (SSO) server.
For the SAN Shared Storage Option (SSO), during an upgrade of a secondary server, the data migration operation may fail because the data partition ID has an incorrect value. An error message, similar to the following, appears in the installation log on the secondary server:
The system cannot find the file specified. : \\ServerName\C$\Program Files\Symantec\Backup Exec\Data\SSOData\bedb_datTESTMZ2_1.mdf
11-24-2009,15:15:17 : Error message:The system cannot find the file specified. : File \\ServerName\C$\Program Files\Symantec\Backup Exec\Data\SSOData\bedb_datServerName.mdf is not found in C:\Program Files\Symantec\Backup Exec\Data\
11-24-2009,15:15:17 : Dump SSO data to the secondary server ends with rc=2
11-24-2009,15:15:17 : Job Migration Failed
11-24-2009,15:15:17 : Failure 2 running migration library 1
During the upgrade of the primary server, a file is created on the primary server for the secondary server’s data. This file name contains the original partition ID. To successfully migrate the secondary server’s data, edit the partition ID registry key and enter the original partition ID, and then run bemig.exe again.
1. On the secondary server, edit the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Server\dataPartitionID
2. Enter the partition ID that is indicated in the data partition file name, which resides on the primary server. The file is located where the server partition database path points to,under HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Server”.
The format of the file is as follows:
In the example install log message, bedb_datServerName.mdf is the original partition ID of the secondary server.
3. On the secondary server, from the installation directory, run bemig.exe. The default installation directory is C:\Program Files\Symantec\Backup Exec.