November 29, 2007 at 9:09 am
We recently had a DR test. We double take the files from one of our critical servers to our DR site. When we cut the line to our DR site and renamed the physical servers to match our Production server names, we brought up SQL Server and there were several databases in suspect mode. The problem ended up being the way double take was working. Anyway, we would like to perform another small test to just bring up the DR Sql Server to make sure none of the DB's come up suspect.
The name of our physical production server is SQL2 and the DR server that receives the double taked files is called QTSQL2. We would like to run a small test on the DR server by just bringing up the sql services and making sure the DB's no longer come up suspect. We would like to do this without cutting the line between our production site and the DR site since it will only be for this one server. If the line is still up and we do not rename the QTSQL2 server to SQL2, the master db that is double taked to QTSQL2 will still think the server name is SQL2. Since the line between the production site and the DR site has not been cut, will this cause us any problems? Obviously the physical server names will not match, but both master databases will be the same so if someone tries to run something in production SQL2, is there any chance it could accidentally go to the DR server since master thinks its SQL2 also?
Thanks for any help.
November 29, 2007 at 5:25 pm
If i am reading this right you are asking that if you have both the production(source) and DR(target) on the same line (network) will it cause problems. Yes, this will cause problems not only for the master server but for the application as well. Also the main this thing is this. Double-take will not be running on either of the servers IF you have both sql server services running at the same time. The reason is... if there are changes to a (source)production system database then double-take will need access to the system databases on the (target)server where it should be replicating from/to (or vice versa) as these databases are not open due to the fact that the system has them open and double-take can not write to them in this state. Now if the Sql services are turned off on the (target or source)server that is not being used then you dont have any worries. I have set double-take up many times and have been very pleased with it. I do hope i have addressed the problem you are asking
Good Luck
D
DHeath
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply