Thursday, March 22, 2012

Database Mirroring

Hello,

I'm having some troubles to set up database mirroring on Itanium II based servers.
I have 3 servers registered in the same domain (windows authentication)
I have created manually the endpoint and there are all 3 started (port 5022)
When I do the alter database set partner on the mirror site it works.
When I do it on the principal instance, I have the following error: Msg 1418 the server instance "TCP:itanium8.sql.net:5022" is not running or does not exist.
If I telnet to the port 5022 I have a reply.
SAme error if I try to set up the mirroring using the GUI (wizard). I am using CTP June.
Any ideas?
Thanks
Jerome

Just to add some additional info regarding my settings:
- SQLServer is started as a service user a domain account (SQL\administrator)
- all my endpoint are started. the role is set to ALL
- I use the fully qualified name for the settings
Jerome|||Jerome,

OK, here we go:
1. Testers have confirmed that they have setup mirroring on Itanium II servers.
2. the fact that the mirror suceeds is normal. all that command does is put the server in a "wait to be contacted" mode.
3. this is different from what Pamb sees in the other thread. there, mirroring was able to log in, but the server name information didn't correctly compare. this is different from what you have. in your case, the server wasn't allowed to log in at all.

so, can you telnet from each server to the other server? you imply that it works one way, but does it work both ways? you should be able to type 16 characters and the connection should close. that tells you that you are able to connect to the port.

your error message implies that you didn't specify the '//' on the input string. it is important that you include the '//' on the server name setup.

what is in the errorlog?

check security again.

thanks,
mark|||Mark,

Ok .. it seems first of all that there is no way to do the setup using the GUI/Wizard. I always get the error described above even if the endpoints are already defined and started. I have discover that for strange reason if I create endpoint using three differents port (I have three independant server so according to the doc I should be able to use the same port) it works but only using command line:
These are the steps I have to go through to have the mirror configured:

1- backup on the principal
2- restore on the mirror with norecovery
3 - create endpoint
principal: state= started port=5022 role=partner
mirror: state=started port=5023 role=partner
witness: state=started port=5024 role=witness
4 - setup the mirror
mirror site: alter db set partner='TCP://itanium8.sql.net:5022'
principal site:
alter db set partner='TCP://itanium9.sql.net:5023'
alter db set partner='TCP://itanium10.sql.net:5024'
But again no way to set it up with the wizard....
Thanks
Jerome

|||so, you should be able to setup and manage mirroring through the GUI/UI. i watch 800 attendees do it today at a conference.

you do have to backup/restore through a different channel.

you have to setup certificates through t-sql.

glad you got it to work.

mark|||Hello Mark,

1 -You do have to backup/restore through a different channel.
What do you mean by that?

2- you have to setup certificates through t-sql.
Event if all the three instances are registered in the same domain? The wizard does not do that for you? In the BOL: "For communication accross non-trusted domain you must use certificate ....." ... in the BOL "If you are setting up database mirroring on a domain, and all SQL Server instances use the same service login and password, you do not need to create logins on the server"

I just want to understand....
Thanks
Jerome

|||1. "by a different channel" means that you have to have backed up and restored the database before you begin the wizard.

2. sorry, what i meant is that if you plan on using certificates, then you must use t-sql. using the domain account in the domain is probably the best way. but if you want to run as a non-domain account or accross non-trusted domains, then you MUST use certificates.

mark

No comments:

Post a Comment