Endpoint Protection

It is possible to restore my old DB to combined to new DB?

Thanks

Yes

you need to install same version of sepm and then restore the DB

follow this document 

http://service1.symantec.com/SUPPORT/ent-security.nsf/2326c6a13572aeb788257363002b62aa/a0edb796f583c886882574aa004c1f60?OpenDocument

my SEPM was upgraded from RU5 to RU6a,it is possible also?

so now I ask if old DB from RU5 can restore or combined with new DB of RU6a?

yes, follow the DR link from symantec

http://service1.symantec.com/SUPPORT/ent-security.nsf/2326c6a13572aeb788257363002b62aa/a0edb796f583c886882574aa004c1f60?OpenDocument

If you have RU5 DB backup ,first you have to uninstall RU6a SEPM.Then install RU5 SEPM and restore the DB...After this you have to restore the certificate files and reconfigure the SEPM..

only same version of backup /restore is allowed

Hi all,

This thread is now included in the Security Solutions Contest.  Just solve this thread, or any unsolved thread included in the contest, and you could win a weekly prize and be crowned "King of the Week!"  Find out more at the blog here:

https://www-secure.symantec.com/connect/forums/new-security-solutions-contest-be-king-week-starting-august-30th

Best,

Eric

1. To restore a RU5 DB you need to install RU5 SEPM..There cannot be version mismatch.

2. When you will restore old DB it will wipe out new DB. The Old DB will not get added to new DB.

Hi,

Here's a few links on moving the SQL database:

Moving the SEPM database to a new SQL server or instance using SQL backup/restore.

Best Practices guide to moving the Symantec Endpoint Protection Manager SQL Server database from an existing SQL Server database to a new SQL Server database

Going back to RU5 from RU6 is basically a DR process:

Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

Edit: I'm also looking into MS SQL for backup and restore procedures. If anyone finds one, please post it here. :D

Any updates?

I'm just thinking out loud here: Assuming that there are still some backup of the old dbs. You could do a restore on them from MS SQL. Then keep on going until you get to the most recent one.

I'm not sure how you'll attach this to SEPM to be able to generate the reports and logs you require.

I,ve tried that sol'n..but I need to know if there's a way to combine old and new DB (SQL DB).

thanks

i do not think so. because the restore remnoves the db, it does not append.

yes thats right....but i need to use my old and new db at same time...

old DB (SEPM & SQL) - DB for 10 months data

new DB (SEPM & SQL) - Db for 1 month data

both need to use...but if there's no way to combine it...maybe i prefered to use my old DB.

thank you

looks like you need to use the old DB in the case.

The best way is install RU5 SEPM in that server and follow the disaster recovery procedure .From the new DB if you want to use some rules ,you can restore in other server(I mean a test server) then export those rules and import in this server...

DB cannot be appended

I think the older DB would be  useful;

You would have not changed much in the policies or groups, if few are missing u can create the groups manually.

Older DB has lot of logs associated which would be helpful.

No, they cannot be combined. It's not possible...

Hypothetically, If there were 2 separate databases, what are the chances that there would be duplicate rows in there? I'm assuming that the second one could have been started after the first one. Based on my understanding, they'd probably have conflicts only in the risks table. Based on the event ID which could be the primary key for that table. The rest would mostly be identical.

you cannot add these database table