Video Screencast Help

SEPM 11.0.7 MP3 Replicating to new site takes forever

Created: 25 Jan 2013 • Updated: 28 Jan 2013 | 12 comments
This issue has been solved. See solution.

Hi all,

 

We are plan to move SEPM 11.0.7 MP3 from one machine to another machine with different IP and machine name following this KB article: http://www.symantec.com/business/support/index?pag....

After step 8, the replication keep running and running. I've check the sem5.db file on machine 2: the size always at around 250MB. Also check the size of replicate folder on machine 2 @: \Symantec Endpoint Protection Manager\data\replication\inbox\: always at zero KB.

I have force to stop the replication and try to run it 3 more time with different replicate site name but the replication keeps running forever.

Does anybody facing with this problem before?

Thank you all for you helpful answers and suggestions!

 

Kind Regards,

Nguyen Cao.

Comments 12 CommentsJump to latest comment

Chetan Savade's picture

Hi,

You can go with disaster recovery.

Refer this thread:

https://www-secure.symantec.com/connect/forums/add...

Chetan Savade
Sr Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

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

SebastianZ's picture

Are both machines in the same LAN?

What is the size of the database on the first SEPM?

You can try the offline replication steps if there are any connection/bandwith considerations between the 2 sepms:

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

Nguyen Cao's picture

Hi Sebastian,

 

Both machine is in the same LAN (1Gbps speed). The size of sem5.db file is 4.5GB. It's not bandwidth issue. On the first machine when go to remote site I found the notice: can not connect to remote site.

2 machine can ping properly, can get file sharing, netstat -na inform that machine 2 established connection with machine 1 via port 8443. Everything seems ok.

The KB you sent is very useful for far away remote site with limited bandwidth but no help with our situation.

Thank you.

SebastianZ's picture

Can you have a look in the SEPM scm-server.log on both machines (SEPM install folder\tomcat\logs) - if you find any errors from the time you tried the replication?

Nguyen Cao's picture

Regretful,

I have reinstalled SEPM on machine 2. On server 1 I have checked all smc-server-0.log and smc-server-1.log but all log for more than 4 hours ago are cleaned :(

Anyway, will try to replicate once again and see what happen in the log file.

Thanks a lot Sebastian :)

 

Nguyen Cao's picture

Hi Seb,

Here the log I got from 2 machines:

 

Machine 2:

2013-01-25 17:52:33.198 SEVERE: Unknown Exception
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (JZ00L: Login failed.  Examine the SQLWarnings chained to this exception for the reason(s).)
    at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549)

Machine 1:

2013-01-25 17:52:31.237 FINE: Test db connection successfully.
2013-01-25 17:52:31.377 INFO: PackageTask.publishGroup(): cmd= "H:\Symantec Manager\tomcat\bin\sempub.exe" "-group" "H:\Symantec Manager\data\outbox\agent\04C13E88AC18410200415B46EDDA118A" "7E5D2FD64B4E7D36ABFB9DD8B368FA28" "1044B113AC184102008393EF3C773381" "A09433DAAC18410201BA11BC87D72BDD" "8014" "H:\Symantec Manager"
2013-01-25 17:52:31.659 INFO: PackageTask.publishGroup(): returnCode = -12(Notify Agent Error) errBuf = StatusCode=500;
2013-01-25 17:52:31.659 INFO: PackageTask.publishGroup(): StatusCode=500;
2013-01-25 17:52:31.830 INFO: PackageTask.publishGroup(): cmd= "H:\Symantec Manager\tomcat\bin\sempub.exe" "-group" "H:\Symantec Manager\data\outbox\agent\D35ED739AC184102007D3BC4A98F9CDF" "7E5D2FD64B4E7D36ABFB9DD8B368FA28" "1044B113AC184102008393EF3C773381" "A09433DAAC18410201BA11BC87D72BDD" "8014" "H:\Symantec Manager"
2013-01-25 17:52:32.143 INFO: PackageTask.publishGroup(): returnCode = 0(Unknown Error Code) errBuf = success
2013-01-25 17:52:32.143 INFO: PackageTask.publishGroup(): success
2013-01-25 17:52:32.409 INFO: PackageTask.publishGroup(): cmd= "H:\Symantec Manager\tomcat\bin\sempub.exe" "-group" "H:\Symantec Manager\data\outbox\agent\C8C397EFAC184102018CE6513DC8E927" "7E5D2FD64B4E7D36ABFB9DD8B368FA28" "1044B113AC184102008393EF3C773381" "A09433DAAC18410201BA11BC87D72BDD" "8014" "H:\Symantec Manager"
2013-01-25 17:52:32.815 INFO: PackageTask.publishGroup(): returnCode = 0(Unknown Error Code) errBuf = success
2013-01-25 17:52:32.815 INFO: PackageTask.publishGroup(): success
2013-01-25 17:52:33.034 INFO: PackageTask.publishGroup(): cmd= "H:\Symantec Manager\tomcat\bin\sempub.exe" "-group" "H:\Symantec Manager\data\outbox\agent\9AA689F8AC18410200AF30A320EBA6B0" "7E5D2FD64B4E7D36ABFB9DD8B368FA28" "1044B113AC184102008393EF3C773381" "A09433DAAC18410201BA11BC87D72BDD" "8014" "H:\Symantec Manager"
2013-01-25 17:52:33.424 INFO: PackageTask.publishGroup(): returnCode = -12(Notify Agent Error) errBuf = StatusCode=500;
2013-01-25 17:52:33.424 INFO: PackageTask.publishGroup(): StatusCode=500;
2013-01-25 17:52:33.690 INFO: PackageTask.publishGroup(): cmd= "H:\Symantec Manager\tomcat\bin\sempub.exe" "-group" "H:\Symantec Manager\data\outbox\agent\87B2A9D7AC1841020114CD8080FE13AE" "7E5D2FD64B4E7D36ABFB9DD8B368FA28" "1044B113AC184102008393EF3C773381" "A09433DAAC18410201BA11BC87D72BDD" "8014" "H:\Symantec Manager"
2013-01-25 17:52:33.909 INFO: PackageTask.publishGroup(): returnCode = -12(Notify Agent Error) errBuf = StatusCode=500;
2013-01-25 17:52:33.909 INFO: PackageTask.publishGroup(): StatusCode=500;
2013-01-25 17:52:34.128 INFO: PackageTask.publishGroup(): cmd= "H:\Symantec Manager\tomcat\bin\sempub.exe" "-group" "H:\Symantec Manager\data\outbox\agent\8CCFE77FAC1841020155752573C36806" "7E5D2FD64B4E7D36ABFB9DD8B368FA28" "1044B113AC184102008393EF3C773381" "A09433DAAC18410201BA11BC87D72BDD" "8014" "H:\Symantec Manager"
2013-01-25 17:52:34.378 INFO: PackageTask.publishGroup(): returnCode = 0(Unknown Error Code) errBuf = success
2013-01-25 17:52:34.378 INFO: PackageTask.publishGroup(): success

SebastianZ's picture

Entry from machine 2 is interesting:

2013-01-25 17:52:33.198 SEVERE: Unknown Exception
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (JZ00L: Login failed.  Examine the SQLWarnings chained to this exception for the reason(s).)
    at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:

 

- can you check ODBC connection with the database on server 2?

http://www.symantec.com/business/support/index?pag...

- do you see any error messages regaridng the SEP database on the SQL server itself?

- are both servers 1 and 2 configured for SQL Databases or is one of them using embedded?

- have a look at similar thread:

https://www-secure.symantec.com/connect/forums/can...

 

... and one more KB:

http://www.symantec.com/business/support/index?pag...

Nguyen Cao's picture

Hi Sebastian,

I found the root cause already. During the replication process, server 1 will create replcation data folder in \data\replication\outbox\FB4103DEAC1... folder. After that server 1 will zip all data in that folder to data.zip file and send the data.zip file to server 2 for replication. That process need approx 2 times free space than the sem5.db file size (with our situation, we need about 12GB free space in H drive on Server 1). But the available space is not enough. That's why during the replication server 2 get login failed message from SQL.

I have tried to clean some space on H drive, deleted any temporary file of the previous replication and run the replication again. It finished successfully.

 

Hi Chetan,

I am now on 13th step of the replication process following this KB: http://www.symantec.com/business/support/index?page=content&id=TECH104389.

13. Wait at least one replication cycle.

After adding Management Server Lists I have to wait for one replication cycle. Do you have any idea of that step? Where can I find the replication cycle information? 

Thank you all for your valuable answers!

Regards,

Nguyen Cao

SOLUTION
pete_4u2002's picture

in the console of SEPM's if both the sites show successful for the first time then it is considered one cycle.

SebastianZ's picture

HI Nguyen,

great news that you managed to find the cause. Replication cycle will be determided by the first replication successfull - I would recommend though let it run for couple of time - just to make sure there are no other issues occuring and then you can proceed with the whole procedure.

Ambesh_444's picture

Agrred with above comments.

 

Thank& Regards,

Ambesh

"Your satisfaction is very important to us. If you find above information helpful or it has resolved your issue. Please don't forget to mark the thread as solved."

Nguyen Cao's picture

Hi all, 

In new SEPM server I saw clients reporting to the new server (green computer). I will wait for couple days to make sure that no issues occcurs and the first replication cycle finish. After that I will upgrade the new server to SEPM 12.1 and uninstall SEPM 11 on the old server.

Once again, thank you all.