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

Migrate from 4.7.4.658 to 4.8 issue

Created: 20 Nov 2012 | 10 comments
Lind311's picture

Hi

Thought I should sink my teeth in upgrading my SSIM to version 4.8.
Read what should be red and got to the point when the migration tool is to be used.
At first it seemed to work properly. During the backup process i looked in the folder i pointed out to be used for the backup and files fell in place. Then once the backup procedure is finished it says that there is a .bckp placed in the folder.
All the previously noticed files are gone, whitch they should, but also there is no .bckp file either?!

Why does it erase this file? Anyone have any idea?
Can't really go any further until this issue is resolved.

/Oscar

Comments 10 CommentsJump to latest comment

Laszlo2's picture

Hi,

I used the migration tool without any problem for backup purposes, altough I only use that for backing the configuration.

After that I restored the configuration to a 4.8 SSIM, everything looks fine, the migration tool said that the restore was successful. At the end of the restore process, the migration tool rebooted the server and the SIMDBMU and SIMSERVER service stopped working. In the SIMDBMU.log there are many error messages:

2012-11-19 15:14:07,241 0    [DBMU] WARN  com.symantec.sim.simdb.Config - Unable to load config file: simdbmu.ini
2012-11-19 15:14:07,247 6    [DBMU] WARN  com.symantec.sim.simdb.Config - Using the default values
2012-11-19 15:14:07,369 128  [DBMU] WARN  com.symantec.sim.sal.dir.HANamespaceManager - created: 5f297ee0
2012-11-19 15:14:09,278 0    [DBMU] WARN  com.symantec.sim.sal.dir.HANamespaceManager - created: 1bd5b1dc
2012-11-19 15:14:11,162 1884 [DBMU] WARN  com.symantec.sim.sal.dir.HANamespaceManager - created: 3c1a42fa
2012-11-19 15:14:11,979 2701 [DBMU] WARN  com.symantec.sim.dbmusvc.DbmuServiceMonitor - DbmuServiceMonitor started
2012-11-19 15:14:12,118 2840 [DBMU] WARN  com.symantec.sim.sal.dir.HANamespaceManager - created: 62fd7773
2012-11-19 15:30:36,776 987498 [RX Service Shutdown] WARN  com.symantec.sim.rx.RXTcpService - Shutting down the RX service
2012-11-19 15:30:36,776 987498 [RX Service Shutdown] WARN  com.symantec.sim.rx.RXTcpService - Shutting down the RX service listener thread
2012-11-19 15:30:36,776 987498 [RX Service Shutdown] WARN  com.symantec.sim.rx.RXTcpService - Shutting down all RX service worker threads
2012-11-19 15:38:28,952 0    [DBMU] WARN  com.symantec.sim.sal.dir.HANamespaceManager - created: 308820b0
2012-11-19 15:38:29,874 922  [DBMU] WARN  com.symantec.sim.sal.dir.HANamespaceManager - created: 3c1a42fa
2012-11-19 15:38:30,647 1695 [DBMU] WARN  com.symantec.sim.dbmusvc.DbmuServiceMonitor - DbmuServiceMonitor started
2012-11-19 15:38:30,798 1846 [DBMU] WARN  com.symantec.sim.sal.dir.HANamespaceManager - created: 2a05c100
2012-11-21 13:58:00,354 166771402 [RX Service Shutdown] WARN  com.symantec.sim.rx.RXTcpService - Shutting down the RX service
2012-11-21 13:58:00,355 166771403 [RX Service Shutdown] WARN  com.symantec.sim.rx.RXTcpService - Shutting down the RX service listener thread
2012-11-21 13:58:00,355 166771403 [RX Service Shutdown] WARN  com.symantec.sim.rx.RXTcpService - Shutting down all RX service worker threads
2012-11-21 14:20:44,849 0    [DBMU] WARN  com.symantec.sim.sal.dir.HANamespaceManager - created: 391a1bb4
2012-11-21 14:20:44,862 13   [log4ssim] WARN  com.symantec.sim.nio.PacketSink - Unable to connect to /127.0.0.1:10012
2012-11-21 14:20:46,687 0    [DBMU] WARN  com.symantec.sim.sal.dir.HANamespaceManager - created: 4a96d110
2012-11-21 14:20:46,700 13   [log4ssim] WARN  com.symantec.sim.nio.PacketSink - Unable to connect to /127.0.0.1:10012
2012-11-21 14:20:51,197 4510 [DBMU] WARN  com.symantec.sim.sal.dir.HANamespaceManager - created: 36862391
2012-11-21 14:20:53,727 7040 [DBMU] ERROR com.symantec.sim.dbmusvc.DbmuServiceMonitor - Error determining current directory IP
2012-11-21 14:20:53,728 7041 [DBMU] ERROR com.symantec.sim.dbmusvc.DbmuServiceMonitor - Unable to establish dirops connection
2012-11-21 14:20:53,729 7042 [DBMU] WARN  com.symantec.sim.dbmusvc.DbmuServiceMonitor - DbmuServiceMonitor started
2012-11-21 14:21:02,716 16029 [DBMU] WARN  com.symantec.sim.dbmusvc.ManagedJobsListener - Cannot retrieve revision list. Retrying in 10 sec.
2012-11-21 14:21:14,721 28034 [DBMU] WARN  com.symantec.sim.dbmusvc.ManagedJobsListener - Cannot retrieve revision list. Retrying in 10 sec.
2012-11-21 14:21:26,725 40038 [DBMU] WARN  com.symantec.sim.dbmusvc.ManagedJobsListener - Cannot retrieve revision list. Retrying in 10 sec.
2012-11-21 14:21:38,728 52041 [DBMU] WARN  com.symantec.sim.dbmusvc.ManagedJobsListener - Cannot retrieve revision list. Retrying in 10 sec.
2012-11-21 14:21:46,755 0    [DBMU] WARN  com.symantec.sim.sal.dir.HANamespaceManager - created: 1bd5b1dc
2012-11-21 14:21:46,766 11   [log4ssim] WARN  com.symantec.sim.nio.PacketSink - Unable to connect to /127.0.0.1:10012
2012-11-21 14:21:51,853 5098 [DBMU] WARN  com.symantec.sim.sal.dir.HANamespaceManager - created: 4d7369fd
2012-11-21 14:21:54,782 8027 [DBMU] ERROR com.symantec.sim.dbmusvc.DbmuServiceMonitor - Error determining current directory IP
2012-11-21 14:21:54,783 8028 [DBMU] ERROR com.symantec.sim.dbmusvc.DbmuServiceMonitor - Unable to establish dirops connection
2012-11-21 14:21:54,784 8029 [DBMU] WARN  com.symantec.sim.dbmusvc.DbmuServiceMonitor - DbmuServiceMonitor started
2012-11-21 14:21:57,758 11003 [DBMU] WARN  com.symantec.sim.dbmusvc.ManagedJobsListener - Cannot retrieve revision list. Retrying in 10 sec.
2012-11-21 14:22:07,784 21029 [DBMU] WARN  com.symantec.sim.dbmusvc.ManagedJobsListener - Cannot retrieve revision list. Retrying in 10 sec.
2012-11-21 14:22:19,787 33032 [DBMU] WARN  com.symantec.sim.dbmusvc.ManagedJobsListener - Cannot retrieve revision list. Retrying in 10 sec.
2012-11-21 14:22:31,803 45048 [DBMU] WARN  com.symantec.sim.dbmusvc.ManagedJobsListener - Cannot retrieve revision list. Retrying in 10 sec.
2012-11-21 14:22:43,817 57062 [DBMU] WARN  com.symantec.sim.dbmusvc.ManagedJobsListener - Cannot retrieve revision list. Retrying in 10 sec.

Anyone else met this problem?

Regards,

Laszlo

olaf's picture

Main problem seems that simdbmu service is unable to determine the directory to connect to.

That means SSIM is unable to retrieve any information to which database it should connect and therefore the simdbmu service doesn't start up.

I would be interested to see the follwoing files.

/opt/Symantec/sesa/ses_common.xml

/opt/Symantec/sesa/SESAManagerConnectionConfig.xml

/opt/Symantec/sesa/FailSafeDirectoryCache.xml

There is also an entry in the LDAP which might be relevant, but if you could provide the information first it might already give me some indication what is wrong.

I also strongly recommend to open a Case with Technical Support for such issues.

 

 

 

var's picture

This is a two appliance setup.  1 Correlation appliance (master directory which is down) and a collector. 

On this end the SESAManagerConnectionConfig.xml for the two appliances share a Database Key Value.  They have their own Directory Key Values that reflect what was set at the time of dirreg.

The ses_common.xml for each has the opposite appliances directory configuration stored. 

jitendra_patil's picture

Some Additional Steps in case of dbmu service being off.

1) Check for /etc/hosts file whether it has all the correct entries

2) Is the date time of the server correct ? In case if it is an multi-appliance setup check if the date time of master directory appliance and that of the registered appliance is correct ? If it is incorrect change the date time from WEB UI

3) Check the state of the agent ?

   a) Go into directory /opt/Symantec/sesa/Agent

   b) run sh agentmgmt.sh

   c) check if agent is running.

   d) Use option 3) to reload agent configurations and 4) to force  Agent to send its Software Inventory and State Updates. If this is successful restart the simdbmu service.

If not please open a case with technical support.

 

 

Laszlo2's picture

Hi,

Thanks for the replies. I think Olaf is right, because I made the backup from a secondary SSIM with a replica LDAP so it's tries to connect to the master LDAP. I will try again the restore procedure with a master device and notify you about the result.

Thank,

Laszlo

jitendra_patil's picture

Hello, 

We do not support migration when replication is on. For migration to be successful you need to break the replication and then migrate the appliance. After migration is complete then you may recreate the replication setup again.

Thanks

Jitendra.

Laszlo2's picture

Hello,

Ok, but before the migration we have to do a restore and a migration test. So because of a migration test I cannot break the replication on the production environment. As I understand to test the migration I have to build an identical LDAP replicated test environment. Restore the production environment and after that I can start the migration testing after I break the replication.

 

Laszlo

jitendra_patil's picture

Hello,

Ok got it. If you are trying to build an identical setup for testing purposes, I will suggest that you keep different hostname and ip address for the new setup. Then try migration from production to test. After that you can recreate the replication and test the setup.

If you want to test using same ip and hostname do not backup and restore from production to test using migration utility. Instead create an isolated 474 environment, create replication in between them and do migration as documented in migration guide.

Thanks,

Jitendra. 

olaf's picture

Oscar,

for the missing backup file.

Can you post the file migration.log and migration.err from the /opt/symantec/simserver/logs directory?

Thanks,

Olaf