Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

113526

January 22nd, 2013 01:00

Moving SANHQ to a new server

Hi,

We have SANHQ 2.2 on a server, but would like to install 2.5 on another server. Is there a way to keep the historic data please?

7 Technologist

 • 

729 Posts

January 22nd, 2013 08:00

To migrate a SAN HQ instance from one server to another:

1. Install the new SAN HQ server, and add the existing group.

2. Stop the EqlxPerf service on the new SAN HQ server.

3. Stop the EqlxPerf service on the old SAN HQ server.

4. Copy the log directory from the old server to the new server.

5. Start the EqlxPerf service on the new server.

At this point, the new service is running with the historical data in place and polling new data as well.

At some point you will need to remove the old version from the other server (please don’t run both at the same time, as this can impact your group performance).

When you uninstall the old version of SANHQ, you should be prompted to save or delete the log files.  It’s recommended to save them, and copy them for safe keeping, until you are satisfied that your new v2.5 setup is working as expected.

-joe

61 Posts

January 22nd, 2013 07:00

I'd like to do the same thing.

61 Posts

January 22nd, 2013 08:00

Thanks, Joe!

If you're not sure where to find your logs: open San HQ, click on Settings>General Settings, and the location is listed Installation Settings.

37 Posts

January 23rd, 2013 03:00

Thanks,

This sort of works. On the new SANHQ window, I have the old SANHQ server IP address with a red cross and the new server. I can see the old logs. Is there a way to merge the two together.  Hope this makes sense?

37 Posts

January 23rd, 2013 06:00

7 Technologist

 • 

729 Posts

January 23rd, 2013 06:00

Can you provide a screen shot?

-joe

7 Technologist

 • 

729 Posts

January 23rd, 2013 07:00

The “x” in a red circle (and the group name or IP address in red) indicates that an event requiring immediate attention exists or that the group cannot be reached by SAN Headquarters.

-joe

7 Technologist

 • 

729 Posts

January 23rd, 2013 07:00

You should be able to right click on the name "10.0.0.191" and have the option to rename it.

-joe

37 Posts

January 23rd, 2013 07:00

Hi Joe,

Thanks for your help. There seems to be confusion. Let me try and clear things up.

There was an Old server running SANHQ 2.2, we need to install SANHQ 2.5 onto another server and keep the old log files. So it's a new server and a version upgrade.

37 Posts

January 23rd, 2013 08:00

Hi Joe,

No 10.0.0.191 is the old server that SANHQ was installed onto. The group management IP on the LAN has not changed.

Your last statement is correct.

7 Technologist

 • 

729 Posts

January 23rd, 2013 08:00

Prior to coping the logs from the old 2.2 server, to the new 2.5 server, you first setup the Group (the 10.0.0.191) for monitoring on the new server.  At that point did the group display properly (i.e., had a check mark in a green circle)?

Then if it did, you at that point stopped the EqlxPerf service on the new server, and copied the logs into the new server, restarted eqlxperf, and it turned to red?

-joe

7 Technologist

 • 

729 Posts

January 23rd, 2013 11:00

You will need to do the following:

1. On the original v2.2 server, stop eqlxperf service

You will need the following two directory structures and files from the original server:

Logs: [path]\all users\Application Data\Equallogic\San HQ\Logs (this is the default, yours may be different)

Config: [Path]\ \Local Settings\Application Data\Dell\SANHQ\ \user.config (this is the default, yours may be different)

Select the that is currently installed on the host

2. Uninstall the SANHQ v2.5 on the new server, you can choose to save the logs, but you will need to move them to another location (we are not going to use them at this point).  The net effect is that v2.5 is uninstalled, and the log file directory is empty.

3. On the new server, install the same version of SANHQ (v2.2) as the original server (can be either 32 or 64 bit, but must be the same version)

4. After the install is complete, stop the eqlxperf service on the new server

5. Copy The logs and user.config file to the new server that is running v2.2

6. Start eqlxperf on the new server

Check to ensure all everything is working

Make sure that the files have the appropriate permissions. Particularly with 2008 as it has enhanced security measures. Note that the files may be 'hidden' and you'll need to un-hide them to correct the permissions.

7. Now you can update to v2.5 on the new server

-joe

2 Posts

February 15th, 2018 08:00

If you copy the log folder and the user.config on the old server, then paste it to the new server, will you need to change any files to point to the IP address of the new server?

As I would like to use a different IP address to the old server.

No Events found!

Top