Moving to a new Server

[clk430]

We are moving our production and development servers to more powerful and robust servers. Our first goal is to move the development server to a new one and then emulate the process for production.

Is it a simple copy, or do we have to re-install it on the new server? Do all the maps need to be recompiled? What are some things that we should be aware of when doing this? Any help or guidance would be appreciated..

ps we have mercator 6.7 on win2k.

 

[BocaBurger]

Well, if your new server has more CPUs, you would need to buy a license for them. On Windows, there are registry entries, and you would have to re-install the software. Maps don't have to be recompiled, but you might just want to create a new server in the IFD and deploy to the new server. If you maintain your directory structure, this should be easy.

Are the new servers Win2K or Win 2003?

BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[clk430]

Hi Boca,

They are forcing win2k as we are using 6.7. We plan on upgrading to 8.0, but not in the near future. Once we have 8.0, we'll move to Windows 2003.

Interestingly enough, we are only using one proc right now on the server. The new dev server has 2 procs....so, I guess I'll have to get with the licesning folks and investigate the purchase.

On a side note, we are moving servers because our current system/configuration cannot keep up with the volume of incoming/outgoing data. Will throwing more CPU's at Mercator help?

 

[BocaBurger]

CPUs and RAM always help. Tuning the maps and Event Server also. Get the 8.0 Design Studio now, use the map profiler and page size and count tuner on copies of your maps, then make the suggested changes to your 6.7 system (hopefully 6.7.1).



BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[clk430]

The map profiler is one feature I'm really looking forward to using. Thanks for your quick and helpful response.

 

[clk430]

You know what I just realized Boca, we will be running 2 procs on the Win2K OS. Does Mercator work well with distributing it's resources with two procs in a Win2K environment? What about 4 procs?

Also, on the server migration issue - when we migrate, does it matter if we move our source code (type trees/maps etc.) first THEN instal Mercator as you suggested above?

 

[BocaBurger]

The Event Server will use as many processors as it can get, based on the number of threads set in the .ini file and the IFD settings, and required by the maps. Not sure why you would want source files on the server running the Event Server. I would suggest keeping them on a file server on your network, and use an application server set up for your Win2K box.
If you ae expanding your server due to load, why add additional I/O? Have you Windows Admin shut off any Windows service not used, tune the OS, and make sure any back ups or anti-virus scans don't run at peak processing times.




BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[clk430]

BocaBurger,

We have come to the point where we have the new server (development) and are migrating. The new server is an exact replica (folder wise, OS wise) but just new hardware and a clean rebuild.

I stuck to my guns about what you said and voiced my opinion about NOT recompiling/regenerating and just moving the .mmc's and .msl's (basically, copying the entire Merc. Folder over). The team shot me down and said NO, they must bring over one map and system at a time, then recompile/regenerate each map and system and unit test everything. I disagree and think we should copy over everything first, then unit test next without recompiling.

Who's right?

 

[BocaBurger]

The best way to deploy to a new server is to deploy. This builds (recompiles) the maps. It also makes sure you can send the same systems to the old server if a problem appears.
Just add a new server to the IFD, and deploy.

To test, I suggest renaming all but one of the .msls (so they don't run) and test each one to make sure things are working as expected, then add them one at a time until you have the full system running. Since you have more CPUs, the mercator.ini's maxthreads and watchmaxthreads settings can be increased for more performance, but this can lead to problems, if there is a conflict in the system, that would only be seen if more maps are running.

Even just going from a single slow CPU to a much faster one can show a timing conflict / problem.



BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[clk430]

I've talked to the team and they like it. BUT, now the "consultants" are saying that currrent DEV and PROD are different (they found a few instances where there are small differences), therefore they want to copy the current PROD system to the new Development server.

MAN, what a hassle. Is this recommended? I know Dev and Prod should be similar, but straight copying it? That would mean changing ALL refrences to PROD (IFD settnings, maps etc.)

Also, they want us to copy PROD's MessageManager.msl. into the new dev box. I forsee many conflicts and not even working. Is this possilbe? Are there differeces between Prod and Dev Message Managers?

 

[BocaBurger]

The only differences are what your company has put into them. I can see differences between dev & prod. However, I would hope there would be a Q/A between the two and Q/A and prod should be identical, until you are Q/Aing a system change.

If they decide to copy, they will be running in an unsupported environment. If there is a problem, they will be told to deploy as written in the documenation, and try again.

They should have a backup of the prod source somewhere.



BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[clk430]

If copying will produce an unsupported environement, is there a SOP for getting them similar?

Unclear if you addressed my message manager question from prod to dev. That is a black box to me, and when we copied message manager from prod to the new dev, well, a lot of unresolved settings came up.