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»»

DR setup for a customer server Expand / Collapse
Author
Message
Posted Wednesday, January 11, 2012 5:47 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, August 26, 2014 10:52 AM
Points: 202, Visits: 354
One of our customers has requested to setup a Disaster recovery site..
Their motive is just to cover up for some auditing and must be demonstrated only twice in a year..
Which high availability is the best to use in this scenario?
We will have to make sure to use minimal resources.
Post #1233910
Posted Wednesday, January 11, 2012 8:09 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Wednesday, August 20, 2014 9:31 AM
Points: 3,903, Visits: 7,138
This is a rather large and open question (really more information is needed to more accurately answer your question)...What is the customer's SLA on downtime? What kinds of things need to be backed up?

If you just need to back up the DB's (and they are currently in FULL recovery mode) you can set up logshipping to a DR site/server, if you have to backup SQL Agent jobs (which include SSIS jobs) you'll need to script some things out...

Can you please be more specific?


______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1234010
Posted Wednesday, January 11, 2012 8:15 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 6:53 PM
Points: 2,013, Visits: 1,589
Their motive is just to cover up for some auditing and must be demonstrated only twice in a year..


It's not a good reason for DR solution.


Dev

Devendra Shirbad | BIG Data Architect / DBA | Ex-Microsoft CSS (SQL 3T)
*** Open Network for Database Professionals ***

LinkedIn: http://www.linkedin.com/in/devendrashirbad
Post #1234014
Posted Wednesday, January 11, 2012 8:15 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, August 26, 2014 10:52 AM
Points: 202, Visits: 354
The DR should be up within 24 hours after the disaster...
Post #1234015
Posted Wednesday, January 11, 2012 8:22 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Wednesday, August 20, 2014 9:31 AM
Points: 3,903, Visits: 7,138
Please be more specific:
1) What's an "acceptable" amount of lost data? i.e. Anything since the last full backup? 2 hours of data? 6 hour? NONE?

2) What recovery modes are currently being used in this environment?

3) Is this DR-scenario for a transactional-based enviornment or just for historical data (i.e a datawarehouse)?

4) What dependencies/gotchas exist?


______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1234027
Posted Wednesday, January 11, 2012 8:22 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, January 12, 2012 7:08 AM
Points: 2, Visits: 131
Consider:

Clustering - Provide failover to another server should the active server running the database fail (not including SAN). This is not a full DR solution (unless you have a mirrored SAN offsite with associated 2nd cluster).
http://www.sql-server-performance.com/2002/clustering-intro/

Log shipping - Can be onsite, offsite and the latency is fully configurable and dependent on bandwidth
http://www.sql-server-performance.com/2002/log-shipping-70/

Mirroring - similar benefits to log shipping but much easier to configure. Requires SQL 2005 and later.
http://technet.microsoft.com/en-us/library/cc917680.aspx


...also consider replication..


Robert Murphy
Post #1234028
Posted Wednesday, January 11, 2012 8:31 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, August 26, 2014 10:52 AM
Points: 202, Visits: 354
MyDoggieJessie (1/11/2012)
Please be more specific:
1) What's an "acceptable" amount of lost data? i.e. Anything since the last full backup? 2 hours of data? 6 hour? NONE?

2) What recovery modes are currently being used in this environment?

3) Is this DR-scenario for a transactional-based enviornment or just for historical data (i.e a datawarehouse)?

4) What dependencies/gotchas exist?

I am sorry..I didn't have much info about a lot of these questions...

1 - Data loss is not appreciated..Hardly a couple of hours of data should be ok

2 - Full recovery models

3 - Definitely transactional based environment

4 - I didn't understand this?
Post #1234039
Posted Wednesday, January 11, 2012 11:07 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Wednesday, August 20, 2014 9:31 AM
Points: 3,903, Visits: 7,138
1 - Data loss is not appreciated..Hardly a couple of hours of data should be ok
2 - Full recovery models
3 - Definitely transactional based environment
4 - I didn't understand this?

Sounds like logshipping would suffice for this type of scenario, and as rob has already pointed out, there are a couple other options. IMHO, the log shipping is probably the easiest to set up and get going.

What I meant by #4 was if there were things like SSIS packages that perform ETL-like processes or Custom scripts, SQL Agent jobs, specific applications running on the existing DB server, and etc that you would need to take into consideration to have mirrored on the DR box - youo'd need to take that into consideration


______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1234221
Posted Wednesday, January 11, 2012 11:42 AM


Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, August 15, 2014 5:59 PM
Points: 20, Visits: 139
Hi Benki,

I think there are a few things that you may be missing on the answers that everyone has provided to you. I hope this answer helps you.

There is a ton of potential answers to your question, we could talk about RAID levels, and how that is a DR solution for a bad disk. We could talk about hot sites, or cold sites. A DR solution has to be driven by the requirements that your customer has. You are going to have to sit down with them and help them answer the questions to make sure that it meets their requirements. Many clients are not going to understand some of the questions that you need to have answered. Things like acceptable data loss, acceptable recovery time, hot or cold site, or do you even need a DR Site.

I would recommend a multiple step approach, give them an example and ask them what they would like to have done, and what they must have done to not impact the revenue to their company. Base on the answers then you can begin with the next level of requirements gathering. Your messaged stated this was for an audit requirement. What is it?

If its for Audit Only and it has to be practiced every 6 months, then does a backup and restore of the databases meet the requirements? That is a very valid DR solution.



Post #1234246
Posted Thursday, October 17, 2013 6:48 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 7:08 AM
Points: 1,232, Visits: 6,643
Benki Chendu (1/11/2012)
One of our customers has requested to setup a Disaster recovery site..
Their motive is just to cover up for some auditing and must be demonstrated only twice in a year..
Which high availability is the best to use in this scenario?
We will have to make sure to use minimal resources.


'Site' implies should you lose your building and hardware, how would you get up and running?
This is a lot more than just proving you can restore a couple backups.
And does conflict with minimal resources, as it would involve additional hardware and physical location, etc.
You need to get a much clearer picture of what is truly being expected to research your options.
And be sure to take into account your physical / virtual machines, hardware, and processes today.
Post #1505677
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse