Showing posts with label mirror. Show all posts
Showing posts with label mirror. Show all posts

Friday, March 23, 2012

High Performance in Mirror

In this mode, I get that it's asynchronous. Does that just mean it sends the TX over and what happens, happens? Do I at least know it hit the comms stack, or the wire or anything? Or just it will do its est. Thanks.

You are referring to the mode when transaction safety is OFF. In this case, the principal sends the log to the mirror but does not wait for acknowledgement from the mirror. So Mirror can lag the Principal under heavy load. However, if mirror is down or if Principal is not receiving the response to the periodic ping (i.e. communication stack has a problem), the principal takes database offline.

Thanks,

|||When you say 'the principal takes database offline' you mean the MIRROR right, not the Principal database which could still live and service TXs, right?

Monday, March 12, 2012

High Availability over Distance

Hi,
I am looking for suggestions on creating a mirror site. Currently we have a
SQL server in a MS Cluster Environment. We will be creating another
clustered environment which will be 5+ miles away from the primary site.
What is the best way to create a mirror of the primary site?
I am looking for the Best option available (MS or third party). Currently I
am looking at Double Take and Replistor. We have sued Replistor in the past
with some good and very bad experiences. Primary goal is to make sure
secondary site is always up to date (within a minute or so). Money is not an
object (within reason, No Million $ options please :-) )
Thank you.
Hi Henrik,
Just be careful at using the high availabilty mode when the servers
(partners) are not on the same data center and pay special attention to
network reliability, network throughput and performance.
Take a look at this paper
Database Mirroring Best Practices and Performance Considerations
http://www.microsoft.com/technet/prodtechnol/sql/2005/technologies/dbm_best_pract.mspx
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Henrik Davidsen" wrote:

> Try to read up on SQL Server's Mirroring feature.
>
> There are different modes the mirroring can operate in. One is a High
> Availability mode, whichs offers guarantee that the mirror is ALWAYS 100%
> up-to-date. That however produces some performance degrading. But read up on
> the mirroring
>
> The mirrorring funktionality is available within SQL Server 2005, so no
> extra expenses is nessecary.
> /Sjang
>
>
|||Thanks Guys. I will look into mirroring for sure.
What about any other options?
Thanks.
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:25119072-74B9-4C84-BE55-042AFF85F735@.microsoft.com...[vbcol=seagreen]
> Hi Henrik,
> Just be careful at using the high availabilty mode when the servers
> (partners) are not on the same data center and pay special attention to
> network reliability, network throughput and performance.
> Take a look at this paper
> Database Mirroring Best Practices and Performance Considerations
> http://www.microsoft.com/technet/prodtechnol/sql/2005/technologies/dbm_best_pract.mspx
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Henrik Davidsen" wrote:
|||There are technologies available from SAN vendors. Although they probably
have million dollar + price tags. Call up EMC and tell them what you want to
do.
Jason Massie
www: http://statisticsio.com
rss: http://feeds.feedburner.com/statisticsio
"Dragon" <noSpam_baadil@.hotmail.com> wrote in message
news:unDj%23b4NIHA.4656@.TK2MSFTNGP03.phx.gbl...
> Thanks Guys. I will look into mirroring for sure.
> What about any other options?
> Thanks.
>
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:25119072-74B9-4C84-BE55-042AFF85F735@.microsoft.com...
>
|||Thank you Jason.
"jason" <jason-r3move@.statisticsio.com> wrote in message
news:72BEA593-F945-4A39-B413-E25B118AFA7B@.microsoft.com...
> There are technologies available from SAN vendors. Although they probably
> have million dollar + price tags. Call up EMC and tell them what you want
> to do.
> --
> Jason Massie
> www: http://statisticsio.com
> rss: http://feeds.feedburner.com/statisticsio
>
> "Dragon" <noSpam_baadil@.hotmail.com> wrote in message
> news:unDj%23b4NIHA.4656@.TK2MSFTNGP03.phx.gbl...
>

High Availability over Distance

Hi,
I am looking for suggestions on creating a mirror site. Currently we have a
SQL server in a MS Cluster Environment. We will be creating another
clustered environment which will be 5+ miles away from the primary site.
What is the best way to create a mirror of the primary site?
I am looking for the Best option available (MS or third party). Currently I
am looking at Double Take and Replistor. We have sued Replistor in the past
with some good and very bad experiences. Primary goal is to make sure
secondary site is always up to date (within a minute or so). Money is not an
object (within reason, No Million $ options please :-) )
Thank you.> I am looking for suggestions on creating a mirror site.
Try to read up on SQL Server's Mirroring feature.

> Primary goal is to make sure secondary site is always up to date (within a
> minute or so).
There are different modes the mirroring can operate in. One is a High
Availability mode, whichs offers guarantee that the mirror is ALWAYS 100%
up-to-date. That however produces some performance degrading. But read up on
the mirroring

> Money is not an object (within reason, No Million $ options please :-) )
The mirrorring funktionality is available within SQL Server 2005, so no
extra expenses is nessecary.
/Sjang|||Hi Henrik,
Just be careful at using the high availabilty mode when the servers
(partners) are not on the same data center and pay special attention to
network reliability, network throughput and performance.
Take a look at this paper
Database Mirroring Best Practices and Performance Considerations
http://www.microsoft.com/technet/pr...ct.
mspx
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Henrik Davidsen" wrote:

> Try to read up on SQL Server's Mirroring feature.
>
> There are different modes the mirroring can operate in. One is a High
> Availability mode, whichs offers guarantee that the mirror is ALWAYS 100%
> up-to-date. That however produces some performance degrading. But read up
on
> the mirroring
>
> The mirrorring funktionality is available within SQL Server 2005, so no
> extra expenses is nessecary.
> /Sjang
>
>|||Thanks Guys. I will look into mirroring for sure.
What about any other options?
Thanks.
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:25119072-74B9-4C84-BE55-042AFF85F735@.microsoft.com...[vbcol=seagreen]
> Hi Henrik,
> Just be careful at using the high availabilty mode when the servers
> (partners) are not on the same data center and pay special attention to
> network reliability, network throughput and performance.
> Take a look at this paper
> Database Mirroring Best Practices and Performance Considerations
> http://www.microsoft.com/technet/pr...c
t.mspx
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Henrik Davidsen" wrote:
>|||There are technologies available from SAN vendors. Although they probably
have million dollar + price tags. Call up EMC and tell them what you want to
do.
Jason Massie
www: http://statisticsio.com
rss: http://feeds.feedburner.com/statisticsio
"Dragon" <noSpam_baadil@.hotmail.com> wrote in message
news:unDj%23b4NIHA.4656@.TK2MSFTNGP03.phx.gbl...
> Thanks Guys. I will look into mirroring for sure.
> What about any other options?
> Thanks.
>
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:25119072-74B9-4C84-BE55-042AFF85F735@.microsoft.com...
>|||Thank you Jason.
"jason" <jason-r3move@.statisticsio.com> wrote in message
news:72BEA593-F945-4A39-B413-E25B118AFA7B@.microsoft.com...
> There are technologies available from SAN vendors. Although they probably
> have million dollar + price tags. Call up EMC and tell them what you want
> to do.
> --
> Jason Massie
> www: http://statisticsio.com
> rss: http://feeds.feedburner.com/statisticsio
>
> "Dragon" <noSpam_baadil@.hotmail.com> wrote in message
> news:unDj%23b4NIHA.4656@.TK2MSFTNGP03.phx.gbl...
>

High Availability over Distance

Hi,
I am looking for suggestions on creating a mirror site. Currently we have a
SQL server in a MS Cluster Environment. We will be creating another
clustered environment which will be 5+ miles away from the primary site.
What is the best way to create a mirror of the primary site?
I am looking for the Best option available (MS or third party). Currently I
am looking at Double Take and Replistor. We have sued Replistor in the past
with some good and very bad experiences. Primary goal is to make sure
secondary site is always up to date (within a minute or so). Money is not an
object (within reason, No Million $ options please :-) )
Thank you.> I am looking for suggestions on creating a mirror site.
Try to read up on SQL Server's Mirroring feature.
> Primary goal is to make sure secondary site is always up to date (within a
> minute or so).
There are different modes the mirroring can operate in. One is a High
Availability mode, whichs offers guarantee that the mirror is ALWAYS 100%
up-to-date. That however produces some performance degrading. But read up on
the mirroring :)
> Money is not an object (within reason, No Million $ options please :-) )
The mirrorring funktionality is available within SQL Server 2005, so no
extra expenses is nessecary.
/Sjang|||Hi Henrik,
Just be careful at using the high availabilty mode when the servers
(partners) are not on the same data center and pay special attention to
network reliability, network throughput and performance.
Take a look at this paper
Database Mirroring Best Practices and Performance Considerations
http://www.microsoft.com/technet/prodtechnol/sql/2005/technologies/dbm_best_pract.mspx
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Henrik Davidsen" wrote:
> > I am looking for suggestions on creating a mirror site.
> Try to read up on SQL Server's Mirroring feature.
> > Primary goal is to make sure secondary site is always up to date (within a
> > minute or so).
> There are different modes the mirroring can operate in. One is a High
> Availability mode, whichs offers guarantee that the mirror is ALWAYS 100%
> up-to-date. That however produces some performance degrading. But read up on
> the mirroring :)
> > Money is not an object (within reason, No Million $ options please :-) )
> The mirrorring funktionality is available within SQL Server 2005, so no
> extra expenses is nessecary.
> /Sjang
>
>|||Thanks Guys. I will look into mirroring for sure.
What about any other options?
Thanks.
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:25119072-74B9-4C84-BE55-042AFF85F735@.microsoft.com...
> Hi Henrik,
> Just be careful at using the high availabilty mode when the servers
> (partners) are not on the same data center and pay special attention to
> network reliability, network throughput and performance.
> Take a look at this paper
> Database Mirroring Best Practices and Performance Considerations
> http://www.microsoft.com/technet/prodtechnol/sql/2005/technologies/dbm_best_pract.mspx
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Henrik Davidsen" wrote:
>> > I am looking for suggestions on creating a mirror site.
>> Try to read up on SQL Server's Mirroring feature.
>> > Primary goal is to make sure secondary site is always up to date
>> > (within a
>> > minute or so).
>> There are different modes the mirroring can operate in. One is a High
>> Availability mode, whichs offers guarantee that the mirror is ALWAYS 100%
>> up-to-date. That however produces some performance degrading. But read up
>> on
>> the mirroring :)
>> > Money is not an object (within reason, No Million $ options please
>> > :-) )
>> The mirrorring funktionality is available within SQL Server 2005, so no
>> extra expenses is nessecary.
>> /Sjang
>>|||There are technologies available from SAN vendors. Although they probably
have million dollar + price tags. Call up EMC and tell them what you want to
do.
--
Jason Massie
www: http://statisticsio.com
rss: http://feeds.feedburner.com/statisticsio
"Dragon" <noSpam_baadil@.hotmail.com> wrote in message
news:unDj%23b4NIHA.4656@.TK2MSFTNGP03.phx.gbl...
> Thanks Guys. I will look into mirroring for sure.
> What about any other options?
> Thanks.
>
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:25119072-74B9-4C84-BE55-042AFF85F735@.microsoft.com...
>> Hi Henrik,
>> Just be careful at using the high availabilty mode when the servers
>> (partners) are not on the same data center and pay special attention to
>> network reliability, network throughput and performance.
>> Take a look at this paper
>> Database Mirroring Best Practices and Performance Considerations
>> http://www.microsoft.com/technet/prodtechnol/sql/2005/technologies/dbm_best_pract.mspx
>> Hope this helps,
>> Ben Nevarez
>> Senior Database Administrator
>> AIG SunAmerica
>>
>> "Henrik Davidsen" wrote:
>> > I am looking for suggestions on creating a mirror site.
>> Try to read up on SQL Server's Mirroring feature.
>> > Primary goal is to make sure secondary site is always up to date
>> > (within a
>> > minute or so).
>> There are different modes the mirroring can operate in. One is a High
>> Availability mode, whichs offers guarantee that the mirror is ALWAYS
>> 100%
>> up-to-date. That however produces some performance degrading. But read
>> up on
>> the mirroring :)
>> > Money is not an object (within reason, No Million $ options please
>> > :-) )
>> The mirrorring funktionality is available within SQL Server 2005, so no
>> extra expenses is nessecary.
>> /Sjang
>>
>|||Thank you Jason.
"jason" <jason-r3move@.statisticsio.com> wrote in message
news:72BEA593-F945-4A39-B413-E25B118AFA7B@.microsoft.com...
> There are technologies available from SAN vendors. Although they probably
> have million dollar + price tags. Call up EMC and tell them what you want
> to do.
> --
> Jason Massie
> www: http://statisticsio.com
> rss: http://feeds.feedburner.com/statisticsio
>
> "Dragon" <noSpam_baadil@.hotmail.com> wrote in message
> news:unDj%23b4NIHA.4656@.TK2MSFTNGP03.phx.gbl...
>> Thanks Guys. I will look into mirroring for sure.
>> What about any other options?
>> Thanks.
>>
>> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
>> news:25119072-74B9-4C84-BE55-042AFF85F735@.microsoft.com...
>> Hi Henrik,
>> Just be careful at using the high availabilty mode when the servers
>> (partners) are not on the same data center and pay special attention to
>> network reliability, network throughput and performance.
>> Take a look at this paper
>> Database Mirroring Best Practices and Performance Considerations
>> http://www.microsoft.com/technet/prodtechnol/sql/2005/technologies/dbm_best_pract.mspx
>> Hope this helps,
>> Ben Nevarez
>> Senior Database Administrator
>> AIG SunAmerica
>>
>> "Henrik Davidsen" wrote:
>> > I am looking for suggestions on creating a mirror site.
>> Try to read up on SQL Server's Mirroring feature.
>> > Primary goal is to make sure secondary site is always up to date
>> > (within a
>> > minute or so).
>> There are different modes the mirroring can operate in. One is a High
>> Availability mode, whichs offers guarantee that the mirror is ALWAYS
>> 100%
>> up-to-date. That however produces some performance degrading. But read
>> up on
>> the mirroring :)
>> > Money is not an object (within reason, No Million $ options please
>> > :-) )
>> The mirrorring funktionality is available within SQL Server 2005, so no
>> extra expenses is nessecary.
>> /Sjang
>>
>>
>

Friday, March 9, 2012

High "Disk Write Bytes/sec" in Mirror server

I have do some benchmark test between the "Principle", "Mirror" and "Witness", things seems normal, the System usage (CPU, Disk Read/Write) on the "Witness" is very small and the CPU usage on Principle and Mirror is similar, However....

For the "Disk Write Bytes/sec", the usage on Principle is 200,000 and the Mirror is 1,500,000, the mirror server is talking about x7 times Disk Write Bytes/sec on the Mirror.

I cannot think of any reason why the Disk Write Bytes /sec is so much higher than the Principle, can somebody help me?

Hi Benny,

Just curious - is the mirrored database the only thing that's running on the mirror machine, or you may have other workloads there?

Could you please run the sp_dbmmonitorresults stored proc on the principal and the mirror, and check whether the send and receive queues show something reasonable?

-- Kaloian.

|||

Hi Kaloian, in the mirror server, I find 19 row but only 1 row in the principle server, is it normal?

According to the result of sp_dbmmonitorresults, I find that the transaction delay on the mirror server is quite long. We are using hardware RAID-5 on the Principle server and normal disk (no RAID) on mirror server, will it increase the write byte /sec, because of the slower in "disk" speed, should be make it lower, am I right?

Thank you very much for your help.

This are the result for your reference:

On Principle Server:

all the counter are "0"

On Mirror Server:

database namerolemirroring_statewitness_statuslog_generation_rateunsent_logsend_rateunrestored_logrecovery_ratetransaction_delaytransactions_per_secaverage_delaytime_recordedTime_behindlocal_time
Mirror2142710710026744630:00.729:00.130:00.7
Mirror2141830830032450629:00.129:00.129:00.1
Mirror2141740740039742928:01.028:01.028:01.0
Mirror21410000001027:00.827:00.827:00.8
Mirror21410000001026:00.726:00.726:00.7
Mirror21410000001025:00.525:00.525:00.5
Mirror21410000001024:00.424:00.424:00.4
Mirror21410000001023:00.223:00.223:00.2
Mirror21410000001022:00.122:00.122:00.1
Mirror21410000001021:00.921:00.921:00.9
Mirror21410000001020:00.820:00.820:00.8
Mirror21417070082419:00.619:00.619:00.6
Mirror21410000021218:00.518:00.518:00.5
Mirror21410000001017:00.317:00.317:00.3
Mirror21410000001016:00.216:00.216:00.2
Mirror21410000000015:40.215:40.215:40.2
Mirror21210000000044:00.115:40.244:00.1
Mirror21210000000043:00.115:40.243:00.1
Mirror21210000000042:00.115:40.242:00.1

High "Disk Write Bytes/sec" in Mirror server

I have do some benchmark test between the "Principle", "Mirror" and "Witness", things seems normal, the System usage (CPU, Disk Read/Write) on the "Witness" is very small and the CPU usage on Principle and Mirror is similar, However....

For the "Disk Write Bytes/sec", the usage on Principle is 200,000 and the Mirror is 1,500,000, the mirror server is talking about x7 times Disk Write Bytes/sec on the Mirror.

I cannot think of any reason why the Disk Write Bytes /sec is so much higher than the Principle, can somebody help me?

Hi Benny,

Just curious - is the mirrored database the only thing that's running on the mirror machine, or you may have other workloads there?

Could you please run the sp_dbmmonitorresults stored proc on the principal and the mirror, and check whether the send and receive queues show something reasonable?

-- Kaloian.

|||

Hi Kaloian, in the mirror server, I find 19 row but only 1 row in the principle server, is it normal?

According to the result of sp_dbmmonitorresults, I find that the transaction delay on the mirror server is quite long. We are using hardware RAID-5 on the Principle server and normal disk (no RAID) on mirror server, will it increase the write byte /sec, because of the slower in "disk" speed, should be make it lower, am I right?

Thank you very much for your help.

This are the result for your reference:

On Principle Server:

all the counter are "0"

On Mirror Server:

database namerolemirroring_statewitness_statuslog_generation_rateunsent_logsend_rateunrestored_logrecovery_ratetransaction_delaytransactions_per_secaverage_delaytime_recordedTime_behindlocal_time
Mirror2142710710026744630:00.729:00.130:00.7
Mirror2141830830032450629:00.129:00.129:00.1
Mirror2141740740039742928:01.028:01.028:01.0
Mirror21410000001027:00.827:00.827:00.8
Mirror21410000001026:00.726:00.726:00.7
Mirror21410000001025:00.525:00.525:00.5
Mirror21410000001024:00.424:00.424:00.4
Mirror21410000001023:00.223:00.223:00.2
Mirror21410000001022:00.122:00.122:00.1
Mirror21410000001021:00.921:00.921:00.9
Mirror21410000001020:00.820:00.820:00.8
Mirror21417070082419:00.619:00.619:00.6
Mirror21410000021218:00.518:00.518:00.5
Mirror21410000001017:00.317:00.317:00.3
Mirror21410000001016:00.216:00.216:00.2
Mirror21410000000015:40.215:40.215:40.2
Mirror21210000000044:00.115:40.244:00.1
Mirror21210000000043:00.115:40.243:00.1
Mirror21210000000042:00.115:40.242:00.1