KNOWN ISSUE: Restoring SQL database from backup cause duplicate clients to be created
|Article:TECH39620|||||Created: 2008-03-13|||||Updated: 2008-04-30|||||Article URL http://www.symantec.com/docs/TECH39620|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
After Recovery Solution SQL database has been restored from backup, the following problems appear:
- Error event ID 11 in Application event log:
Event Type: Error
Event Source: Altiris Recovery Solution
Event Category: Server Administration
Event ID: 11
Time: 7:04:38 PM
There was an error getting the SBS key from the given GUID.
Local Event Code: 0xc009000b
- Recovery Solution Service keeps hanging and SQL server CPU usage goes up to 100 percent.
Recovery Solution 6.x
SQL database has been restored from backup
If clients kept registering Recovery Solution Agents with the Recovery Solution Server after backup and then SQL database has been restored from backup, new clients will receive same SBSKeys as other clients.
This behavior causes two problems:
- Client is unable to find itself in the database but still triggers Recovery Solution Server to search.
- More than one client are associated with the account created on the server.
These issues are causing Recovery Solution Server to run some stored procedures pegging SQL server.
Current resolution is to remove the Recovery Solution agent from all clients which have had Recovery Solution agents installed after SQL database backup took place.
|Description||Logged in tlndev (Altiris - Talinn) database|
Article URL http://www.symantec.com/docs/TECH39620