June 9, 2010 at 6:41 pm
we have a server which was made made virtual. The same server now has the physical server too. The physical will have software upgrade done and will not be production. hence the virtual will be used to accomodate the process and remain as production while the application software upgrade on the physical is being done.
the problem is that they have changed the name of the physical and want to bring it to domain. so both are going to be used at the same time and the sql services on the physical box can be turned off. But the catch is that on the physical which is being used for upgrade, the application client config file still points to the (name of the) virtual which is now prodcution.
I was concerned of the potential that while the application software is being upgraded, this might result in an "unwanted talk" between physical and virtual as the name of the virtual is being referenced from the physical. It seems they still have it pointed to the production server (vm) for fall back purposes. Is this safe? they feel as no one will use it, nothing will happen...
June 9, 2010 at 7:33 pm
My primary concern would be that you have an application config file on the database server. Typically you would not want to host the application on the same server as the database server. SQL Server works best on a server by itself.
Second concern is has this process been tested?
Third concern would be with the config file still pointing to the VM from a box that the application should not be running on but there is always a possibility. I would do any of the following and try multiple things if possible.
1. Comment out the connection in the config file. This can quickly be reversed if you need to fail back.
2. Enable a firewall rule between the two servers and disallow communications. This too can quickly be reversed if you need to use the physical box for some reason.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
June 10, 2010 at 12:18 am
Thank you for the reply and the alternatives. From what I heard, it is still the same server, where the vm was once physical except that the name has changed and after the upgrade, the physical will continue to be the production with a new name and the data during the transition which was in the VM so long will be exported to the physical. But my concern was about both being in the domain at the same time while the upgrade would take place and the possible cross talk. Will try to get the name commented out in the config file. Thank you
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply