Showing posts with label power. Show all posts
Showing posts with label power. Show all posts

Tuesday, March 20, 2012

Replication and power outages/offline servers

The setup: Two sql server 2005 SP1 clusters replicating with about 25 transactional publications and 10 merge publications. (Both clusters are being tested, nothing is in publication)

Currently, the servers are in the same building, which is prone to power outages. When a power outage occurs, how are the publications going to act once power is restored? Will we have to reinitialize the publications? This would be bad considering one of our publications takes around four hours to deliver a complete snapshot. What happens if one of the clusters where to go offline? When it comes back would it continue to replicate, or would the publication need to be reinitialized? Curious if anyone has any experience with this.

I've tried searching for any articles on this topic and have not been successful. If anyone knows of any, point me in that direction. Thanks!

-mike
replication should pick up where it left off in case of power or network outage. reinits should not happen due to those issues.

Replication and power outages/offline servers

The setup: Two sql server 2005 SP1 clusters replicating with about 25 transactional publications and 10 merge publications. (Both clusters are being tested, nothing is in publication)

Currently, the servers are in the same building, which is prone to power outages. When a power outage occurs, how are the publications going to act once power is restored? Will we have to reinitialize the publications? This would be bad considering one of our publications takes around four hours to deliver a complete snapshot. What happens if one of the clusters where to go offline? When it comes back would it continue to replicate, or would the publication need to be reinitialized? Curious if anyone has any experience with this.

I've tried searching for any articles on this topic and have not been successful. If anyone knows of any, point me in that direction. Thanks!

-mikereplication should pick up where it left off in case of power or network outage. reinits should not happen due to those issues.

Saturday, February 25, 2012

Replicating to over 70 databases...why??

Is this reasonable or is this poor design...why not just a few power servers
and all users have high speed internet connections or at least DSL'
Thanks
Ken S.Think you will have to explain your situation a little more to get any good
feedback
Ray Higdon MCSE, MCDBA, CCNA
--
"SMAN" <ksanti@.nycap.rr.com> wrote in message
news:O1ct4n9AEHA.2404@.TK2MSFTNGP11.phx.gbl...
> Is this reasonable or is this poor design...why not just a few power
servers
> and all users have high speed internet connections or at least DSL'
> Thanks
> Ken S.
>

Replicating to over 70 databases...why??

Is this reasonable or is this poor design...why not just a few power servers
and all users have high speed internet connections or at least DSL'
Thanks
Ken S.Think you will have to explain your situation a little more to get any good
feedback
--
Ray Higdon MCSE, MCDBA, CCNA
--
"SMAN" <ksanti@.nycap.rr.com> wrote in message
news:O1ct4n9AEHA.2404@.TK2MSFTNGP11.phx.gbl...
> Is this reasonable or is this poor design...why not just a few power
servers
> and all users have high speed internet connections or at least DSL'
> Thanks
> Ken S.
>