SQL Server 2005 sp2 database Mirroring problems

Question

SQL Server 2005 sp2 database Mirroring problems

sendtoibrahim

SSC Enthusiast

Points: 161
More actions
April 20, 2008 at 8:41 am

#206058

Hello, how guys how are you doing?
I am new for database Mirroring but as i read i have prepared 3 PC's for Principal, Mirror and the Witness server. and the Principal data is SP2. So, now i will have
1. high availability and the failover type is Automatic and manual
2. the same end points i.e ( 5022)
what i did is, i have " Accounting database" and first i took the FULL bakup and i restored again WITH NORECOVERY MODE, but the problem is i can't access my database just to configure security Mirroring because it is in the RESTORING MODE. so, how could i prepare my database for mirroring before configuring the security?
could you please show me guys how to mirror my database step by step? example with " Accounting" database.
thank you very much
God bless you

Viewing 15 posts - 1 through 15 (of 17 total)

You must be logged in to reply to this topic. Login to reply

MarkusB SSC-Dedicated Points: 37370 More actions · Answer 1

What do you mean by "configure security"?

Once you restored the backup to the mirror server with norecovery, you can start the mirror session from your principal.

The only security related issue I can think of is that you might need to transfer the login(s) to the mirror server but that's something in the master database not your mirror database.

[font="Verdana"]Markus Bohse[/font]

sendtoibrahim SSC Enthusiast Points: 161 More actions · Answer 2

Hi, man how are you doing?

i can not proceed with the configuring security because after i have restored my data with NORECOVERY then it becomes as a loding RESTORE MODE. that is why i can't configure the Mirroring.

so, could you please show me how to start from the begining of this database restore?

thanks

Vidhya Sagar SSCrazy Eights Points: 8216 More actions · Answer 3

I hope you are trying to configure mirroring from the mirror server!!! You need to configure mirroring from the principal server. Refer the below link which will be helpful to configure mirroring.

Database Mirroring

Regards..Vidhya Sagar
SQL-Articles

sendtoibrahim SSC Enthusiast Points: 161 More actions · Answer 4

Hello, guys how you doing?

before i started Mirroring i made FULL backup for my database " Accounting" in Principal database and restored this FULL backup in Mirror server with NORECOVERY and this database stays as RESTORING MODE. then i have started mirroring every thing was ok. but the problem is, it asked me whether i " start Mirroring or not " then i click start mirroring. and i found the error messege. it says that......." the server network address ' TCP// csc.ababa.com: 5022' can't be reached or doesn't exist. check the network address name and the ports for the local and remote endpoints are operational ( micosoft sql error 1481).

when i check the mirror server, my database is changed from " RESORING TO IN RECOVERY"

example: - Accounting ( in recovery)

- Hospitality ( in recovery )

- Otolaryngology ( in recovery)

right now my question is, am i right that with the restoring of the Mirror server with NORECOVERY?

please guys i need your help?

thank you very much

MarkusB SSC-Dedicated Points: 37370 More actions · Answer 5

Restoring the database on the mirror server with the norecovery option is right. Your error message points to a network connectivity issue. Of course lot's of possible reasons for this, but the first thing I would check if port 5022 is already in use by another endpoint or some application.

To test connectivity you can also try to telnet to the server on port 5022.

[font="Verdana"]Markus Bohse[/font]

Craig Purnell SSCrazy Points: 2720 More actions · Answer 6

You must first setup the endpoints, then assign correct security on them. Sounds like you have network connectivity issues or something is not configured right. Please see the troubleshooting slides in this excellent presentation:

[url= http://support.microsoft.com/kb/925067%5D%5B/url%5D

Hope this helps.

sendtoibrahim SSC Enthusiast Points: 161 More actions · Answer 7

Hello, guys how are you doing?

i think the end points are correct because the three instances are running in 3 defferent machines. but i don't know how to assign the security. as you said may be because of security is not configured and this might be one of the error cause.

so, could you please show me how assign the security endpoints?

thanks

Craig Purnell SSCrazy Points: 2720 More actions · Answer 8

It's much easier to configure security the 1st time using the GUI (Mirroring Wizard). Right click on your DB, then select Tasks > Mirror... Then click the "Configure Security" button and follow the steps. This will do all of the configuration for you. Also, the GUI usually has better / more informative error messages than T-SQL commands.

Thanks Craig

sendtoibrahim SSC Enthusiast Points: 161 More actions · Answer 9

Hello, how are you doing?

regarding this " configure security" i have laready done it successfully. but i though that after this configuration, may be there is another configuration for assigning permission in this mirroring. any how the error is still not yet solved. because it asks whether i have a problem with networking and the error is sql server 1481 database mirrorig.

thanks

Craig Purnell SSCrazy Points: 2720 More actions · Answer 10

Take a look at:

http://technet.microsoft.com/en-us/library/ms189127.aspx

and

http://technet.microsoft.com/en-us/library/aa337361.aspx

odanwada SSCrazy Points: 2133 More actions · Answer 11

HI i also face the same error. I think once after restore the database you might have forgot to restore the transactional backup. Try this i hope it works. Reply me if it works fine.

anand.gotikala Grasshopper Points: 21 More actions · Answer 12

It turns out that the service account for the instances of running SQL Serves has to be a domain account, otherwise you need to set up certificates. First try to change the accounts for your database servers to the doamin admin.

r.sukumar369 SSC Enthusiast Points: 120 More actions · Answer 13

May be this error indicated that the two database endpoints did not have the same encryption algorithm selected. You can check this by running the following query on both servers:

SELECT * FROM sys.database_mirroring_endpoints

Compare the values of the encryption_algorithm_desc column from both servers. for example one server with RC4 and one server with None. They have to match. The solution was to drop the endpoint on the new server ('DROP ENDPOINT Mirroring') and re-run the mirror setup wizard and checking that the mirror server required encryption.

r.sukumar369 SSC Enthusiast Points: 120 More actions · Answer 14

May be this error indicated that the two database endpoints did not have the same encryption algorithm selected. You can check this by running the following query on both servers:

SELECT * FROM sys.database_mirroring_endpoints

Compare the values of the encryption_algorithm_desc column from both servers. For example one server with RC4 and one server with None. They have to match. The solution was to drop the endpoint on the new server ('DROP ENDPOINT Mirroring') and re-run the mirror setup wizard and checking that the mirror server required encryption.