Does the DataPartition information in the Backup Exec database match the Backup Exec registry?

Article:TECH136210  |  Created: 2010-01-15  |  Updated: 2013-04-03  |  Article URL http://www.symantec.com/docs/TECH136210
Article Type
Technical Solution

Product(s)

Environment

Issue



Does the DataPartition information in the Backup Exec database match the Backup Exec registry?


Solution



This report examines the Backup Exec Database to determine if the data in the DataPartition table matches corresponding settings in the registry.

If these settings don't match, the Backup Exec services may not start correctly.

This usually occurs when the server has been renamed or the database has been moved to another server with a different name.

If this report has identified a problem, please locate the problem description below and follow the directions to resolve the problems.

Warnings:
 
  • Before following any of the directions, please create backups of your Backup Exec Database (BEDB) and Windows Registry.  Instructions for backing up BEDB are located in Related Documents.
  • Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

Solution 1: One or more erroneous entries have been located in the database.
 
The Backup Exec Support Tool (BE_ST) has identified that at least one set of entries in the registry and DataPartition match, however, additional table entries are present and could prevent Backup Exec services from starting.
 

 
To remove the erroneous entries using OSQL, perform the following:
 
1. Stop all of the Backup Exec services
 
2. Open a command line window and connect to the Microsoft SQL Server instance and open the Backup Exec database (BEDB).
 
To connect to the Backup Exec SQL instance of  type:
 
osql -E -S server name\BKUPEXEC
 
  • Successful OSQL commands return the following prompt:
1>
 
To open BEDB, type the following lines, pressing Enter after each line:
 
use bedb
 
go
 
3. Using the table shown in the report from BE_ST, only execute the following command for each row displayed:
 
delete from DataPartition where PartitionID=PartitionID and PartitionName='PartitionName' and PartitionGUID='PartitionGUID'
 
go
 
Example:
 
1> delete from DataPartition where PartitionID=18 and PartitionName='BESERVER' and PartitionGUID='1E1A88CF-4A82-456A-859A-1B1F2019BEF1'
 
2> go
 
(1 row affected)
 
1>
 
4. When finished, close OSQL by typing Exit and pressing Enter.
 
5. Start all of the Backup Exec services.
 

NOTE: If multiple rows are returned in the error table for this report with the error messages below, execute the solutions for the error message once.  Then run BE_ST again, to determine if additional actions are required to ensure proper operations.

Solution 2: Database has the correct PartitionName.  The PartitionID and PartitionGUID need to be regenerated.
 
The Backup Exec Support Tool (BE_ST) has identified that the Server Name matches the PartitionName in the Backup Exec Database, while the PartitionID and PartitionGUID need to be regenerated.
 

 
To have Backup Exec regenerate the PartitionGUID and PartitionID perform the following steps:
 
1. Stop all of the Backup Exec services.
 
2. Using the Registry editor, navigate to the following path:
 
HKEY_LOCAL_MACHINE\Software\Symantec\Backup Exec for Windows\Backup Exec\Server
 
3. Delete the following values:
 
  • DataPartitionID
  • DataPartitionGUID
4. Start all of the Backup Exec services.
 

 
Solution 3: Database has the correct PartitionName and PartitionID.  The PartitionGUID needs to be regenerated.
 
The Backup Exec Support Tool (BE_ST) has identified that the Server Name matches the PartitionName and PartitionID matches the DataPartitionID registry value, while the PartitionGUID needs to be regenerated.
 

 
To have Backup Exec regenerate the PartitionGUID perform the following steps:
 
1. Stop all of the Backup Exec services.
 
2. Using the Registry editor, navigate to the following path:
 
HKEY_LOCAL_MACHINE\Software\Symantec\Backup Exec for Windows\Backup Exec\Server
 
3.  Delete the following value:
 
  • DataPartitionGUID
4. Start all of the Backup Exec services.
 

Solution 4: Database has the correct PartitionName and PartitionGUID.  The PartitionID needs to be regenerated.
 
The Backup Exec Support Tool (BE_ST) has identified that the Server Name matches the PartitionName and PartitionGUID matches the DataPartitionGUID registry value, while the PartitionID needs to be regenerated.
 

 
To have Backup Exec regenerate the PartitionID perform the following steps:
 
1. Stop all of the Backup Exec services.
 
2. Using the Registry editor, navigate to the following path:
 
HKEY_LOCAL_MACHINE\Software\Symantec\Backup Exec for Windows\Backup Exec\Server
 
3.  Delete the following value:
 
  • DataPartitionID
4. Start all of the Backup Exec services.
 

Solution 5: Database has the correct PartitionID.  The PartitionName needs to be updated and the PartitionGUID needs to be regenerated.
 
The Backup Exec Support Tool (BE_ST) has identified that the PartitionGUID matches the DataPartitionGUID registry value, while the PartitionName needs to be updated and the PartitionGUID needs to be regenerated.
 

 
To update the PartitionName using OSQL, use the following commands:
 
1. Stop all of the Backup Exec services
 
2. Open a command line window and connect to the Microsoft SQL Server instance and open the Backup Exec database (BEDB).
 
To connect to the Backup Exec SQL instance of  type:
 
osql -E -S server name\BKUPEXEC
 
  • Successful OSQL commands return the following prompt:
1>
 
To open BEDB, type the following lines, pressing Enter after each line:
 
use bedb
 
go
 
3. Using the table shown in the report from BE_ST, only execute the following command for the row(s) displayed:
 
update DataPartition set PartitionName='PartitionName' where PartitionID=PartitionID
 
go
 
Example:
 
1> update DataPartition set PartitionName='NewServerName' where PartitionID=0
 
2> go
 
(1 row affected)
 
1>
 

 
To have Backup Exec regenerate the PartitionGUID perform the following steps:
 
1. Using the Registry editor, navigate to the following path:
 
HKEY_LOCAL_MACHINE\Software\Symantec\Backup Exec for Windows\Backup Exec\Server
 
2.  Delete the following value:
 
  • DataPartitionGUID
3. Start all of the Backup Exec services.
 

In the event that none of these solutions have resolved the problem, please contact Technical Support for additional assistance.

 

Supplemental Materials

SourceUMI
ValueV-370-59792-00036
Description

"Does the DataPartition information in the Backup Exec database match the Backup Exec registry?"



Legacy ID



355589


Article URL http://www.symantec.com/docs/TECH136210


Terms of use for this information are found in Legal Notices