Endpoint Protection

I'm getting an error while restoring database in SEPM 12.1.5(RU5).

Is there any way to rebuild database if it is corrupted?

yes, even one of the technician from symantec also tried to restore the database but still facing same issue.

I have 3 backup files of different dates and tried to restore with all of them but facing same problem for all.

Does old SEPM version are same ?

yes both are 12.1.5(RU5)

SEPM was upgraded in november 2014 and all backup files are taken after upgradation.

if database are corrupted no way to rebuild database.

what are the ways to find out whether backup is corrupted or not?

Because how come all backups will be corrupted at a time?

I'm getting same error for all backup files.

Have you take backup as per below process ?

Disaster recovery best practices for Symantec Endpoint Protection 12.1

https://support.symantec.com/en_US/article.TECH160736.html

Yes.

Even technicien from symantec also checked all the files like server private key and backup files, but he also got the same error while restoring it.

That's bad to know backups are not restoring successfully & there isn't any way to verify backup veracity.

However, you can still perform disaster recovery without a database backup, but the following points apply in this case:

• All policies must be re-created or imported from other backups (e.g. exported policy files).
• Clients will be able to communicate with SEPM, but will re-appear in the console only after their next check-in.
• Clients will reappear in the default group as they check in, unless you enable automatic creation of client groups on the re-installed SEPM by editing "scm.agent.groupcreation=true" to the conf.properties file. This file is located <drive>Program files or(x86)/Symantec/Symantec Endpoint Protection Manager/tomcat/etc.
• If you originally had multiple SEPM domains beyond the default domain, you must re-create them using the domain IDs from SEPBackup.txt.

@chetan

I don't have any exported policy files and re-configuring of complete SEP is also not possible because we have more than 1000 endpoints and different policies to handle them. So, is there any mid way to get out of this?

And now I'm not able to login to SEPM console.

Unfortunately if database is corrupted there isn't any mid way to get out of this unless you have followed proper disaster recovery steps.

& I think database restored was unsuccessful that's the reason you aren't able to login into the SEPM.

I would suggest to do a fresh install and restore the communication by choosing one of the available option.

It seems you need to manualy create policies again.

I am not able to understand why you are restoring database? Because not able to login? or Moved SEPM to another machine?

Do you still have a backup of the database before it was upgraded to RU5? If so use that to restore against and RU5 will upgrade the schema in the process to bring it back in line. 

Checked with symantec advance team and duty manager, only solution for this type of problem is reconfigure your SEPM with server private key to communicate with endpoints. :( :(

@chetan

When I logged case with symantec technical support for my windows definition update, symantec technician used content cleanup tool and changed some config file to resolve the problem, but it couldn't help so at end he tried to restore SEPM with old db.