Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

High availability best practice? Expand / Collapse
Author
Message
Posted Thursday, December 6, 2012 8:51 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Tuesday, November 18, 2014 2:47 AM
Points: 453, Visits: 590
I have a vendor supplied database driven application, I need to place a copy in another city for DR purposes, replication doesnt work because the around 30% of the tables do not have primary keys and I can't change the table schemas in case the app falls over, Mirroring disconnects everytime I put the server under heavy load. Log shipping seems to be ok but I dont like being left with huge numbers of TRN files and no regular BAK files. I have scripted a set of daily bak and trn routines that i can schedule to build fresh copy every day but this leaves me humping 90Gb across a WAN link everyday, which makes the Infrastructure team a little cross.
What other options have I got and what do other people do? I am expected to provide failover to within an hour or so if it all goes wrong
Post #1393576
Posted Thursday, December 6, 2012 9:09 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:31 AM
Points: 40,456, Visits: 36,912
Martin Stephenson (12/6/2012)
Log shipping seems to be ok but I dont like being left with huge numbers of TRN files and no regular BAK files.


Log shipping does not remove the need for full backups.
You need regular full backups, not for the log shipping, but for normal recovery strategies. In the case of a disaster or accidental delete, you absolutely do not want to be restoring a full backup then months of log backups.

I have scripted a set of daily bak and trn routines that i can schedule to build fresh copy every day but this leaves me humping 90Gb across a WAN link everyday, which makes the Infrastructure team a little cross.


Why do you need to copy all 90 GB every day? Are you doing something odd like switching to simple recovery model before taking backups?



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1393593
Posted Thursday, December 6, 2012 9:14 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Tuesday, November 18, 2014 2:47 AM
Points: 453, Visits: 590
If I set up log shipping, the translogs are applied to the target database, if the source gets a new full backup, doesnt that break the log chain for transaction log backups and therefore stop you applying it to the target database?
Post #1393598
Posted Thursday, December 6, 2012 9:43 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:31 AM
Points: 40,456, Visits: 36,912
Martin Stephenson (12/6/2012)
if the source gets a new full backup, doesnt that break the log chain for transaction log backups and therefore stop you applying it to the target database?


No.

http://www.sqlskills.com/blogs/paul/post/Misconceptions-around-the-log-and-log-backups-how-to-convince-yourself.aspx



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1393618
Posted Thursday, December 6, 2012 10:17 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Tuesday, November 18, 2014 2:47 AM
Points: 453, Visits: 590
In that case I'll just go and get it setup then
Post #1393638
Posted Thursday, December 6, 2012 2:06 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Sunday, November 23, 2014 9:55 PM
Points: 222, Visits: 249

The only time you need to send your full to secondary is if you need a reinit. Otherwise take your fulls nightly and store locally, tran log baks will never be interrupted to secondary.

Frequently take log baks, every 15min, watch sizes, e.g. during maint when we rebuild indexes those logs get big and latency backs up just a bit so this process is managed closely.

Regards,
Chris
mssqlconsulting.com



Post #1393746
Posted Thursday, December 6, 2012 11:54 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 2:42 PM
Points: 35,612, Visits: 32,208
I you have SANS from the same company at each site, you can do SAN replication and relieve SQL Server a bit. That'll also work for non-SQL Server files, as well.

--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1393884
Posted Friday, December 7, 2012 4:04 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 9:21 AM
Points: 6,643, Visits: 14,230
Martin Stephenson (12/6/2012)
If I set up log shipping, the translogs are applied to the target database, if the source gets a new full backup, doesnt that break the log chain for transaction log backups and therefore stop you applying it to the target database?

No, what it does do is to reset the differential backup chain by incrementing the differential base LSN.


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1393977
Posted Friday, December 7, 2012 2:01 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, October 24, 2014 6:14 AM
Points: 65, Visits: 404
Martin Stephenson (12/6/2012)
Mirroring disconnects everytime I put the server under heavy load.


Are you setting it up as asynchronous(high-performance)?
Post #1394238
Posted Monday, December 10, 2012 2:59 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Tuesday, November 18, 2014 2:47 AM
Points: 453, Visits: 590
It was set up as high performance, I dont have a spare server to act as a witness at the moment . It does document management and everytime there was intense file movement and sql activity the mirror would be suspended and never be able to re-sync. The application is not mirror aware so any failover would be manual, log shipping seems the to be the path of least resistance at the moment.
According to the vendor the latest version is SQL2012 compliant and mirror aware so maybe next year I shall be revisiting the mirror options
Post #1394508
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse