October 25, 2012 at 5:10 am
Hi,
We have mirroing setup for DR purposes.
i.e.
server mdr is mirroing server m
Question:
1-
When I go to the mdr machine in sql server, I see the word restoring for all the databases and so when I try to do a select query from one of the databases, it says that the database is in the middle of a restore and therefore does not return data.
How can I then chek to see if the data inside mdr is indeed correct ?
2-
in machine m, there are sql server agent jobs.
in mdr machine, I do not see the sql server agents. How do I see them.
Thanks
October 25, 2012 at 5:22 am
If the mirroring is working, the data in the mirror DB will be correct. You could take a snapshot off the mirror and query that if you want.
SQL Agent jobs are not included in mirroring, mirroring is just the DB you configure, jobs are in MSDB. If you want them, you have to transfer them.
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
October 25, 2012 at 5:34 am
GilaMonster (10/25/2012)
If the mirroring is working, the data in the mirror DB will be correct. You could take a snapshot off the mirror and query that if you want.SQL Agent jobs are not included in mirroring, mirroring is just the DB you configure, jobs are in MSDB. If you want them, you have to transfer them.
The applications (User screens) are pointing to the machine m (Prod server).
how do I know that if the machine m goes down, then automatically the applications are redirected to the mdr (DR database machine)?
October 25, 2012 at 5:43 am
GilaMonster (10/25/2012)
SQL Agent jobs are not included in mirroring, mirroring is just the DB you configure, jobs are in MSDB. If you want them, you have to transfer them.
How can the sql server jobs appear in the mdr machine?
I mean how can they be copied so that I see them as I do in the prod management studio in sql server?
Thanks
October 25, 2012 at 5:59 am
arkiboys (10/25/2012)
GilaMonster (10/25/2012)
If the mirroring is working, the data in the mirror DB will be correct. You could take a snapshot off the mirror and query that if you want.SQL Agent jobs are not included in mirroring, mirroring is just the DB you configure, jobs are in MSDB. If you want them, you have to transfer them.
The applications (User screens) are pointing to the machine m (Prod server).
how do I know that if the machine m goes down, then automatically the applications are redirected to the mdr (DR database machine)?
Depending on your applications connectivity (only through ADO.NET or SQL Native client IIRC) there is a "Failover Partner =" option for the connection string which will automatically redirect to a mirror partner.
What mode is your mirroring session using, do you have a witness server?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 25, 2012 at 6:00 am
arkiboys (10/25/2012)
GilaMonster (10/25/2012)
SQL Agent jobs are not included in mirroring, mirroring is just the DB you configure, jobs are in MSDB. If you want them, you have to transfer them.How can the sql server jobs appear in the mdr machine?
I mean how can they be copied so that I see them as I do in the prod management studio in sql server?
Thanks
script the jobs out and copy them same as the logins too.
Either that or use an SSIS package task to transfer the objects for you 😉
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 25, 2012 at 6:07 am
arkiboys (10/25/2012)
how do I know that if the machine m goes down, then automatically the applications are redirected to the mdr (DR database machine)?
Run a DR test. Fail the mirroring over and check that the apps reconnect properly. You can fail back afterwards. If you have the connection string set correctly it should work. Actually, should work even without that, read up on transparent client redirect.
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
October 25, 2012 at 8:38 am
Perry Whittle (10/25/2012)
arkiboys (10/25/2012)
GilaMonster (10/25/2012)
SQL Agent jobs are not included in mirroring, mirroring is just the DB you configure, jobs are in MSDB. If you want them, you have to transfer them.How can the sql server jobs appear in the mdr machine?
I mean how can they be copied so that I see them as I do in the prod management studio in sql server?
Thanks
script the jobs out and copy them same as the logins too.
Either that or use an SSIS package task to transfer the objects for you 😉
I can script the job in production.
In the script, I see the name for the production server.
On running this script in the mdr (mirrored server), do I change the production server name to the mirrored server name?
October 25, 2012 at 8:46 am
arkiboys (10/25/2012)
I can script the job in production.In the script, I see the name for the production server.
On running this script in the mdr (mirrored server), do I change the production server name to the mirrored server name?
Hmm, for a local server job you generally won't see the server name, is this a mutli server job?
Can you post the section of the script in question?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 26, 2012 at 4:41 am
Some of these jobs are executing ssis packages with parameters, etc...
That is fine, I just change the name of the server in the sql jobs.
Thanks
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply