NGX Backup - Restore??

[btoler23]

I am running NGX_R62 SmartCenter Server (SPLAT) and peform a normal backup (backup -f <filename>) from production server.

Built a new SmartCenter Server and performed a restore on a lab server. I am able to manage using GUI client with no problems. Once the SmartCenter server gets rebooted, I can no longer manage using GUI client??

Am I missing something here as I was successful with this using NG-AI R55 with no problems doing restores from production server to lab server??

Thanks,
Bob

[northlandboy]

You should be able to do this.

Could you be more specific about not being able to manage using the GUI client - i.e. what is happening? Are the processes still running, and is the GUI client still defined? What error messages are you getting?

[btoler23]

After reboot of SmartCenter Server - launch GUI to connect. Get this message:

"Please make sure that the Server <NAME> is up and running and that you are defined as a GUI client"

I am able to ping the GUI client IP address from SmartCenter server and able to ping the SmartCenter server from GUI client. I am successful with doing this before the reboot of server.

I am able to login to SmartCenter server, run cpconfig and confirmed that any machine on the GUI client list that makes a connection - gets the message above.

I am a little stumped on this one.........


What I did today just to see what else I could find was to do an export from current production and perform new installation and use the import option.

Once that was successful, rebooted server, made some changes to objects to get lab working properly and performed a backup.

Performed another new installation on same lab server and used the restore option with that backup and works just fine after reboot.

Any ideas or help would be greatly appreciated.

Thanks,
Bob

[northlandboy]

Pinging is only one part of connectivity testing - and often a poor one.

Make sure that the Check Point services are running correctly - e.g cpstat mg

ps -ef|grep cp

netstat -an|grep 18190

Have a look in the logs too.

Are there any other changes you have made after restoring - e.g. changing IP address of the system? It's possibly a licensing-related issue.

Check in $FWDIR/log/fwm.elg, and $CPDIR/log/cpstart.log

[trieder]

I recently upgraded from NGX R60 to NGX R62 and got the same issue..
What we found out after about 8 hours of troubleshooting was when the upgrade was halfway through the process (process of upgrading eventia reporter) it asked for a reboot.. We selected no, and the upgrade continued.. We then finshed the upgrade and rebooted and got this issue..

We beleive the that caused it issue.. The core checkpoint system did not complete get installed during the process..

We reinstalled NGX R60 from scratch with eventia reporter and selected no again on the reboot and the exact same thing occured.. Everything was working except for 18190.. It was not listening.. and yet again we have the exact same issue...

We then reinstalled again and this time selected yes to the reboot and then it worked fine.. we then had to use the upgrade_import tool to recover the checkpoint configuration.. and it worked without any dramas..

The problem is, once you do it the first time and you don't reboot during the process, there is no comming back.. You need to either recover from a image backup.. or you do what we had to do and perform full reinstallation of OS / Checkpoint NGX and then perform an upgrade_import and recover from a backup..

Very painful exercise...

At least it proves that the upgrade_export and upgrade_import tools work very well..

Saved me...

[btoler23]

I reviewed the logs and nothing there to say that there are any issues with startup?? I also verified that Server is listening on 18190.

The only thing that I can think of now is what the restore is actually restoring for system configuration information?? If for some reason the servers are not identical, would that be an issue with using the restore??

[btoler23]

Trieder

I think you are mentioning doing an export/import for an upgrade, correct?? I have already completed the upgrade and now updating my disaster recovery procedures and have come across this issue after performing a restore.

Right now, export/import seems to be the option now and looking to see if there is an issue with different hardware on each server causing the issue??