Forum Discussion
Wally_Heim
15 years agoLevel 6
Hi Sri,
I think I understand a little more. On Windows you can do a few tricks to get the application to believe it is running on a server with the virtual host name and not the physical server name. It sounds like your biggest problem for your Windows clusters will the installation.
For the installation, you have two chooses.
Option #1 (My recommended approach)
1. Rename the physical server name to be the virtual server name and reboot
2. Install your application.
3. After the installation, stop the services for your application and set them to manual startup (assuming that your application installs as a service.)
4. Rename the server back to the physical server name and reboot.
5. Repeat on the next node as needed to install your application.
Option #2 (This approach does not work for every application.)
1. Alter the ActiveComputerName registry location to be the virtual server name. This is done by entering the virtual server name in the following registry key
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ComputerName\ActiveComputerName\ComputerName
2. Install your appliation.
3. After the installation, stop the services for your application and set them to manual startup. (assuming that your application installs as a service.)
4. Reboot the server to reset the ActiveComputerName registry entry
5. Repeat on the next node as needed to install your application.
Now you just need to configure your service group. You will need to have NIC, IP, Lanman, VMDg, MountV and GenericService resources configured. The GenericService resource has attributes (UseVirtualName and LanmanResName) that allow it to start the service in the virtual server context of the Lanman resource.
If you want learn more about the Lanman or GenericService resource for the Windows product, please go to the VCS Bundled Agents Reference Guide for Windows located at: ftp://exftpp.symantec.com/pub/support/products/Storage_Foundation_for_Windows/306339.pdf
As for you application binaries being on shared storage. I'm assuming that you are going to install SFW-HA to local storage and have only the binaries from your application being clustered on shared storage. As mentioned this is not recommended but it will work and has been used on the Windows product in the past. The one thing to remember is that if the binaries get corrupt then they are corrupt for all nodes and SFW-HA will not be able to bring you application online until you fix the correpted binaries.
Thanks,
Wally
I think I understand a little more. On Windows you can do a few tricks to get the application to believe it is running on a server with the virtual host name and not the physical server name. It sounds like your biggest problem for your Windows clusters will the installation.
For the installation, you have two chooses.
Option #1 (My recommended approach)
1. Rename the physical server name to be the virtual server name and reboot
2. Install your application.
3. After the installation, stop the services for your application and set them to manual startup (assuming that your application installs as a service.)
4. Rename the server back to the physical server name and reboot.
5. Repeat on the next node as needed to install your application.
Option #2 (This approach does not work for every application.)
1. Alter the ActiveComputerName registry location to be the virtual server name. This is done by entering the virtual server name in the following registry key
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ComputerName\ActiveComputerName\ComputerName
2. Install your appliation.
3. After the installation, stop the services for your application and set them to manual startup. (assuming that your application installs as a service.)
4. Reboot the server to reset the ActiveComputerName registry entry
5. Repeat on the next node as needed to install your application.
Now you just need to configure your service group. You will need to have NIC, IP, Lanman, VMDg, MountV and GenericService resources configured. The GenericService resource has attributes (UseVirtualName and LanmanResName) that allow it to start the service in the virtual server context of the Lanman resource.
If you want learn more about the Lanman or GenericService resource for the Windows product, please go to the VCS Bundled Agents Reference Guide for Windows located at: ftp://exftpp.symantec.com/pub/support/products/Storage_Foundation_for_Windows/306339.pdf
As for you application binaries being on shared storage. I'm assuming that you are going to install SFW-HA to local storage and have only the binaries from your application being clustered on shared storage. As mentioned this is not recommended but it will work and has been used on the Windows product in the past. The one thing to remember is that if the binaries get corrupt then they are corrupt for all nodes and SFW-HA will not be able to bring you application online until you fix the correpted binaries.
Thanks,
Wally
Related Content
- 4 years ago