January 11, 2012 at 3:27 am
sorry
January 11, 2012 at 3:34 am
no firewalls between them, and both node are in same subnet mask..
and i have checked using telnet command for this port,
but i m configuring in primary server, how can system can't reach to own.
January 11, 2012 at 3:44 am
Dhirju (1/11/2012)
no firewalls between them, and both node are in same subnet mask..and i have checked using telnet command for this port,
but i m configuring in primary server, how can system can't reach to own.
Have you made the host file entries on both server for each other ? I am not sure why, but this works some times.
January 11, 2012 at 3:44 am
Dhirju (1/11/2012)
how can system can't reach to own.
what do you mean by this?
Are both instances on the same server?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 11, 2012 at 4:25 am
there r two server
1st one is primary server and
2nd server are two instances (Mirror and Witness)
both are running on two different ports, and both server in one domain controller.
January 11, 2012 at 4:53 am
Fully Qualified Domain Name (e.g. http://www.google.com)
January 11, 2012 at 5:22 am
Dhirju (1/11/2012)
there r two server1st one is primary server and
2nd server are two instances (Mirror and Witness)
both are running on two different ports, and both server in one domain controller.
do you have Windows firewall enabled on the servers
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 11, 2012 at 5:36 am
windows firewall is disable on both servers.
January 11, 2012 at 6:47 am
Apply the most recent transaction log to your mirror server and leave it.If you get the same error to reapply again.
“When I hear somebody sigh, ‘Life is hard,’ I am always tempted to ask, ‘Compared to what?’” - Sydney Harris
January 11, 2012 at 6:50 am
Dhirju (1/11/2012)
windows firewall is disable on both servers.
ok simple test, on the principal server go into administrative tools and open data source administrator. Create a new system DSN pointing to the mirror instance, at the end of the wizard click the test data source option and ensure it's successful
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 11, 2012 at 8:40 am
tomorrow i'll do it and get back to u for the same.
i have not enable filestream. is any type of relation of both?.
January 11, 2012 at 8:52 am
May or May not be...
Per BOL:
Database mirroring can be used with the following features or components of SQL Server.
•Log shipping
•Full-text catalogs
•Database snapshots
•Replication
Don’t find anything on FILESTREAM articles either way (accepting / rejecting).
For More:
January 11, 2012 at 9:09 am
Databases that have a filestream filegroup can't be mirrored, so if you haven't enabled filestream then you're fine to mirror that DB.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 11, 2012 at 9:25 am
i mean to say, enable filestream for t-sql access in sql server configuration manager for sql server services.
January 11, 2012 at 9:30 am
Mirroring doesn't need any particular filestream setting. As I said, you can't mirror a DB that has a filestream column in it, so it would be a little weird if the filestream setting was necessary (it is not)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 15 posts - 16 through 30 (of 40 total)
You must be logged in to reply to this topic. Login to reply