Video Screencast Help

SEPM sql db restore failure in VM

Created: 30 Oct 2012 • Updated: 09 Dec 2012 | 6 comments
cus000's picture
This issue has been solved. See solution.

Dear all,

 

any idea what this error means?

 

"Retore failed due to DB problem"

 

SQL 2008 r2.... SEPM

 

 

 

thanks

Comments 6 CommentsJump to latest comment

Ashish-Sharma's picture

Hello

 

Did u perform the step to "To restore the server certificate" before trying to restore the database ?

"Best Practices for Disaster Recovery with Symantec Endpoint Protection"
http://www.symantec.com/business/support/index?page=content&id=TECH102333&locale=en_US

 

Thanks In Advance

Ashish Sharma

 

 

pete_4u2002's picture

what's the step you trying to restore?

can you post the screen shot of error message?

 

cus000's picture

This thread is on behalf of my colleague..i'll ask him to take a screenshot..

 

on the keystore part... yes he did that before restoring the db

Mithun Sanghavi's picture

Hello,

This Error could be due to two issues -

1) Either the Database is Corrupt.

OR

2) Trying to Restore the Database of a higher version on the SEPM of a Lower Version.

Ideally, use the same version of SEPM to which the Database Backup belongs to.

Try installing the same Database on the same version of SEPM again and check if that works.

Reference: https://www-secure.symantec.com/connect/forums/downgrade-sepm-117-mp2-sepm-117

Secondly, check this Article:

How to move the Symantec Endpoint Protection Manager server to a new VM or server machine with a different IP.

http://www.symantec.com/docs/TECH95311

Hope that helps!!

 

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

toby's picture

Can you check whether your database user is having the correct permissions and make sure it is the same user as it was used previously for what you have the backup.

------------------------------------------------------------------

Best regards!

toby

CISSP / STS / MCP 

cus000's picture

My colleague has found the possible root cause, it's due to sem5 password given by customer was incorrect.

 

Thanks all for the input and suggestion!!

SOLUTION