Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Migrate SEP database to different SQL instance

Created: 11 Aug 2010 • Updated: 13 Sep 2010 | 2 comments
This issue has been solved. See solution.

We are planning to migrate our SEP database to different SQL instance. Below is our current setup detail,

Two SEP servers replicating each other and connected to common SQL DB (Separate MSSQL 2005 server) and the instance name is "SERVERNAME".

The new plan will be Two SEP servers replicating each other and connected to common SQL DB (Separate MSSQL 2005 server) and the instance name ll be "SERVERNAME\SEP".

Is there any doc and procedure can i get for my reference? Your help is most appreciated.

Thanks in advance.
HMB

Comments 2 CommentsJump to latest comment

Topa 101's picture

Make a copy of your current Server Host List and add the new sepm's name and IP's that you plan to create or build later, then create a backup of this Sepm using the Sepm's backup utility.

Do not apply the Sepms server lists to any groups untill the new sepms are up and running.

Now Do a Sepm restore to create or build the New SEPM servers and the SQL DB, do not forget to capture the Keystore files from the old sepm.

Once the new sepm is up and running you can simply move your agent over to this new Identicle Sepm Enviroment by adding the Server Host List you create above to the policy groups on the old Sepm or the sepm being replaced, agent s will start to move over within their next heatbeat into the old sepm.

Then reconnect any of your othe sepm's to the new SEPM instance.

The sepm Restore process is smart enough to reconfigure the servers local ip settings, so as long as you have correct information in the server host list files your agents will re-connect and land in the groups they had been asigned to previously on the old Sepm.

Gregory A Anderson

Symantec Certified specialist - SEP v11.x - v12.1.x

Symantec DLP 12.x Boot Camp survivor