recover from a sql disaster

Is there any good sql 2000 or 2005 disaster recovery plan or guide out that
you guys used to come up with your own?
What's your procedures do have for backups and for recovery?
I asked that because i have been asked to implement a sql server to run a
finacial program. I am a bit nerves because i don't know how to recover from
a sql disaster can some help ?Depends on what you define as a disaster and what the
business requirements are in case of one of the defined
disasters. One source would be the MS SQL Server High
Availability book:
http://www.microsoft.com/mspress/books/6515.asp
SQL Server magazine has published a lot of articles on the
topic, addressing different issue, recovery requirements:
http://www.windowsitpro.com/SQLServer/
-Sue
On Tue, 27 Dec 2005 16:01:02 -0800, "alex"
<alex@.discussions.microsoft.com> wrote:
>Is there any good sql 2000 or 2005 disaster recovery plan or guide out that
>you guys used to come up with your own?
>What's your procedures do have for backups and for recovery?
>I asked that because i have been asked to implement a sql server to run a
>finacial program. I am a bit nerves because i don't know how to recover from
>a sql disaster can some help ?|||well i wasn't really looking for a book i was looking for past experiences or
advice as this needs to done within the next few weeks. Downtime is not an
option because this server will be handling all the companies $$$ records. So
again i ask What's your procedures for sql backups and for recovery in case
of any lost?
"Sue Hoegemeier" wrote:
> Depends on what you define as a disaster and what the
> business requirements are in case of one of the defined
> disasters. One source would be the MS SQL Server High
> Availability book:
> http://www.microsoft.com/mspress/books/6515.asp
> SQL Server magazine has published a lot of articles on the
> topic, addressing different issue, recovery requirements:
> http://www.windowsitpro.com/SQLServer/
> -Sue
> On Tue, 27 Dec 2005 16:01:02 -0800, "alex"
> <alex@.discussions.microsoft.com> wrote:
> >Is there any good sql 2000 or 2005 disaster recovery plan or guide out that
> >you guys used to come up with your own?
> >
> >What's your procedures do have for backups and for recovery?
> >
> >I asked that because i have been asked to implement a sql server to run a
> >finacial program. I am a bit nerves because i don't know how to recover from
> >a sql disaster can some help ?
>|||Lost data from what? User errors? Application errors?
Database loss? Server loss? Hardware failures? Flooding of
your server room? Is any downtime allowed? If yes, does that
depend on business hours, business cycles? If no, what are
you using for redundancy? Do you really need more than
99.999% uptime? Do you know how much downtime that
calculates to a year?
Again, it depends on everything you need to define as a
disaster and the business requirements for these. If you
need to have this done in a few weeks and don't have the
answers to these and the business requirements, you can only
throw something together and hope for the best but you will
be taking chances.
Do full backups, do log backups and there is no way to
answer the frequency without business needs, do
differentials if needed - there is no way to answer this
without know more on recover needs, database sizes, what is
available for backups. Where you backup to and how you save
those off depends on what's available to you, not what is
best if this is something that just has to be throw
together.
I can't say it's ever been the same at any client's sites
I've been to. All had different requirements and most have
different requirements for different servers, databases.
They have all been different so I'm not sure anyone can give
you the one and only answer you are looking for that will
ensure you are protected and able to recover all data with
no downtime under any circumstance. It's just not always as
simple as just backup and restore. If this is critical and
absolutely no downtime ever is tolerated, then you must have
some combination of clustering, replication, standby servers
in place at alternative locations so that makes things a bit
more complicated as well.
-Sue
On Tue, 27 Dec 2005 20:21:02 -0800, "alex"
<alex@.discussions.microsoft.com> wrote:
>well i wasn't really looking for a book i was looking for past experiences or
>advice as this needs to done within the next few weeks. Downtime is not an
>option because this server will be handling all the companies $$$ records. So
>again i ask What's your procedures for sql backups and for recovery in case
>of any lost?
>
>"Sue Hoegemeier" wrote:
>> Depends on what you define as a disaster and what the
>> business requirements are in case of one of the defined
>> disasters. One source would be the MS SQL Server High
>> Availability book:
>> http://www.microsoft.com/mspress/books/6515.asp
>> SQL Server magazine has published a lot of articles on the
>> topic, addressing different issue, recovery requirements:
>> http://www.windowsitpro.com/SQLServer/
>> -Sue
>> On Tue, 27 Dec 2005 16:01:02 -0800, "alex"
>> <alex@.discussions.microsoft.com> wrote:
>> >Is there any good sql 2000 or 2005 disaster recovery plan or guide out that
>> >you guys used to come up with your own?
>> >
>> >What's your procedures do have for backups and for recovery?
>> >
>> >I asked that because i have been asked to implement a sql server to run a
>> >finacial program. I am a bit nerves because i don't know how to recover from
>> >a sql disaster can some help ?
>>|||Well the server will be custom built raid 5 good tape back rotation and
shadow copy for this situation because there is no room to cluster servers
what so ever. Business hour are from 8am to 5pm and that whole time finacial
records are going in and reports are coming out. I think the only time
downtime would be allowed is if the system failed for some reason and then
they would have no choice but to wait. Taking chances with this is not really
an option i guess what i will end up doing is having some sort of back up
plan to back up that plan and a plan to back that up.
I just wanted to know how the sql pro's pre for any project dealing with
finacial servers.
"Sue Hoegemeier" wrote:
> Lost data from what? User errors? Application errors?
> Database loss? Server loss? Hardware failures? Flooding of
> your server room? Is any downtime allowed? If yes, does that
> depend on business hours, business cycles? If no, what are
> you using for redundancy? Do you really need more than
> 99.999% uptime? Do you know how much downtime that
> calculates to a year?
> Again, it depends on everything you need to define as a
> disaster and the business requirements for these. If you
> need to have this done in a few weeks and don't have the
> answers to these and the business requirements, you can only
> throw something together and hope for the best but you will
> be taking chances.
> Do full backups, do log backups and there is no way to
> answer the frequency without business needs, do
> differentials if needed - there is no way to answer this
> without know more on recover needs, database sizes, what is
> available for backups. Where you backup to and how you save
> those off depends on what's available to you, not what is
> best if this is something that just has to be throw
> together.
> I can't say it's ever been the same at any client's sites
> I've been to. All had different requirements and most have
> different requirements for different servers, databases.
> They have all been different so I'm not sure anyone can give
> you the one and only answer you are looking for that will
> ensure you are protected and able to recover all data with
> no downtime under any circumstance. It's just not always as
> simple as just backup and restore. If this is critical and
> absolutely no downtime ever is tolerated, then you must have
> some combination of clustering, replication, standby servers
> in place at alternative locations so that makes things a bit
> more complicated as well.
> -Sue
> On Tue, 27 Dec 2005 20:21:02 -0800, "alex"
> <alex@.discussions.microsoft.com> wrote:
> >well i wasn't really looking for a book i was looking for past experiences or
> >advice as this needs to done within the next few weeks. Downtime is not an
> >option because this server will be handling all the companies $$$ records. So
> >again i ask What's your procedures for sql backups and for recovery in case
> >of any lost?
> >
> >
> >"Sue Hoegemeier" wrote:
> >
> >> Depends on what you define as a disaster and what the
> >> business requirements are in case of one of the defined
> >> disasters. One source would be the MS SQL Server High
> >> Availability book:
> >> http://www.microsoft.com/mspress/books/6515.asp
> >> SQL Server magazine has published a lot of articles on the
> >> topic, addressing different issue, recovery requirements:
> >> http://www.windowsitpro.com/SQLServer/
> >>
> >> -Sue
> >>
> >> On Tue, 27 Dec 2005 16:01:02 -0800, "alex"
> >> <alex@.discussions.microsoft.com> wrote:
> >>
> >> >Is there any good sql 2000 or 2005 disaster recovery plan or guide out that
> >> >you guys used to come up with your own?
> >> >
> >> >What's your procedures do have for backups and for recovery?
> >> >
> >> >I asked that because i have been asked to implement a sql server to run a
> >> >finacial program. I am a bit nerves because i don't know how to recover from
> >> >a sql disaster can some help ?
> >>
> >>
>|||Are your systems sitting idle after 5pm till 8am the next day ?
Why do you say there is no room to cluster servers ?
Whats the cost of downtime ? You need to figure that out. how much would the
company lose in revenue should the server be unavailable for 5 mins vs 1hr
vs all day ? And not to mention the credibility that goes along with it.
All of these would help determine the appropriate solution.
I would be certain that the financial orgs have their highly critical
systems clustered at the very minimum and if some data loss is acceptable,
possibly go with log shipping.
A lot can be done using synchronous mirroring to a remote site. SQL 2005 has
that feature built in with Database Mirroring, whereby a write on one server
is committed to the primary and a secondary server before the user gets a
response. This ensures data is intact on both servers. However there is a
latency tied to this approach.
You could also work some sort of queueing/messaging system whereby if the
system goes offline, your transactions could start queuing..
Theres many ways to skin the cat.. Just start with the cost of downtime. And
at the very minimum implement log shipping I would say at 5 min intervals to
a hot standby server.
"alex" <alex@.discussions.microsoft.com> wrote in message
news:9B51E4FE-AAA7-4CAB-80C1-DDAA0A414DE2@.microsoft.com...
> Well the server will be custom built raid 5 good tape back rotation and
> shadow copy for this situation because there is no room to cluster servers
> what so ever. Business hour are from 8am to 5pm and that whole time
> finacial
> records are going in and reports are coming out. I think the only time
> downtime would be allowed is if the system failed for some reason and then
> they would have no choice but to wait. Taking chances with this is not
> really
> an option i guess what i will end up doing is having some sort of back up
> plan to back up that plan and a plan to back that up.
> I just wanted to know how the sql pro's pre for any project dealing with
> finacial servers.
> "Sue Hoegemeier" wrote:
>> Lost data from what? User errors? Application errors?
>> Database loss? Server loss? Hardware failures? Flooding of
>> your server room? Is any downtime allowed? If yes, does that
>> depend on business hours, business cycles? If no, what are
>> you using for redundancy? Do you really need more than
>> 99.999% uptime? Do you know how much downtime that
>> calculates to a year?
>> Again, it depends on everything you need to define as a
>> disaster and the business requirements for these. If you
>> need to have this done in a few weeks and don't have the
>> answers to these and the business requirements, you can only
>> throw something together and hope for the best but you will
>> be taking chances.
>> Do full backups, do log backups and there is no way to
>> answer the frequency without business needs, do
>> differentials if needed - there is no way to answer this
>> without know more on recover needs, database sizes, what is
>> available for backups. Where you backup to and how you save
>> those off depends on what's available to you, not what is
>> best if this is something that just has to be throw
>> together.
>> I can't say it's ever been the same at any client's sites
>> I've been to. All had different requirements and most have
>> different requirements for different servers, databases.
>> They have all been different so I'm not sure anyone can give
>> you the one and only answer you are looking for that will
>> ensure you are protected and able to recover all data with
>> no downtime under any circumstance. It's just not always as
>> simple as just backup and restore. If this is critical and
>> absolutely no downtime ever is tolerated, then you must have
>> some combination of clustering, replication, standby servers
>> in place at alternative locations so that makes things a bit
>> more complicated as well.
>> -Sue
>> On Tue, 27 Dec 2005 20:21:02 -0800, "alex"
>> <alex@.discussions.microsoft.com> wrote:
>> >well i wasn't really looking for a book i was looking for past
>> >experiences or
>> >advice as this needs to done within the next few weeks. Downtime is not
>> >an
>> >option because this server will be handling all the companies $$$
>> >records. So
>> >again i ask What's your procedures for sql backups and for recovery in
>> >case
>> >of any lost?
>> >
>> >
>> >"Sue Hoegemeier" wrote:
>> >
>> >> Depends on what you define as a disaster and what the
>> >> business requirements are in case of one of the defined
>> >> disasters. One source would be the MS SQL Server High
>> >> Availability book:
>> >> http://www.microsoft.com/mspress/books/6515.asp
>> >> SQL Server magazine has published a lot of articles on the
>> >> topic, addressing different issue, recovery requirements:
>> >> http://www.windowsitpro.com/SQLServer/
>> >>
>> >> -Sue
>> >>
>> >> On Tue, 27 Dec 2005 16:01:02 -0800, "alex"
>> >> <alex@.discussions.microsoft.com> wrote:
>> >>
>> >> >Is there any good sql 2000 or 2005 disaster recovery plan or guide
>> >> >out that
>> >> >you guys used to come up with your own?
>> >> >
>> >> >What's your procedures do have for backups and for recovery?
>> >> >
>> >> >I asked that because i have been asked to implement a sql server to
>> >> >run a
>> >> >finacial program. I am a bit nerves because i don't know how to
>> >> >recover from
>> >> >a sql disaster can some help ?
>> >>
>> >>
>>|||Are your systems sitting idle after 5pm till 8am the next day ? yes
Why do you say there is no room to cluster servers ? because there isn't
even a server room at this place. I am a tech for a company that does tech
support contracting and where all this is going on is one of my locations i
cover. But the servers are in some guys office because that's the only place
they could have gone.
Whats the cost of downtime ? You need to figure that out. how much would the
company lose in revenue should the server be unavailable for 5 mins vs 1hr
vs all day ? And not to mention the credibility that goes along with it.
The only major loss i can see is productivity 1 hr to one day would set them
back a few weeks to a month.
"Hassan" wrote:
> Are your systems sitting idle after 5pm till 8am the next day ?
> Why do you say there is no room to cluster servers ?
>
Whats the cost of downtime ? You need to figure that out. how much would the
company lose in revenue should the server be unavailable for 5 mins vs 1hr
vs all day ? And not to mention the credibility that goes along with it.
> All of these would help determine the appropriate solution.
> I would be certain that the financial orgs have their highly critical
> systems clustered at the very minimum and if some data loss is acceptable,
> possibly go with log shipping.
> A lot can be done using synchronous mirroring to a remote site. SQL 2005 has
> that feature built in with Database Mirroring, whereby a write on one server
> is committed to the primary and a secondary server before the user gets a
> response. This ensures data is intact on both servers. However there is a
> latency tied to this approach.
> You could also work some sort of queueing/messaging system whereby if the
> system goes offline, your transactions could start queuing..
> Theres many ways to skin the cat.. Just start with the cost of downtime. And
> at the very minimum implement log shipping I would say at 5 min intervals to
> a hot standby server.
>
> "alex" <alex@.discussions.microsoft.com> wrote in message
> news:9B51E4FE-AAA7-4CAB-80C1-DDAA0A414DE2@.microsoft.com...
> > Well the server will be custom built raid 5 good tape back rotation and
> > shadow copy for this situation because there is no room to cluster servers
> > what so ever. Business hour are from 8am to 5pm and that whole time
> > finacial
> > records are going in and reports are coming out. I think the only time
> > downtime would be allowed is if the system failed for some reason and then
> > they would have no choice but to wait. Taking chances with this is not
> > really
> > an option i guess what i will end up doing is having some sort of back up
> > plan to back up that plan and a plan to back that up.
> >
> > I just wanted to know how the sql pro's pre for any project dealing with
> > finacial servers.
> >
> > "Sue Hoegemeier" wrote:
> >
> >> Lost data from what? User errors? Application errors?
> >> Database loss? Server loss? Hardware failures? Flooding of
> >> your server room? Is any downtime allowed? If yes, does that
> >> depend on business hours, business cycles? If no, what are
> >> you using for redundancy? Do you really need more than
> >> 99.999% uptime? Do you know how much downtime that
> >> calculates to a year?
> >> Again, it depends on everything you need to define as a
> >> disaster and the business requirements for these. If you
> >> need to have this done in a few weeks and don't have the
> >> answers to these and the business requirements, you can only
> >> throw something together and hope for the best but you will
> >> be taking chances.
> >> Do full backups, do log backups and there is no way to
> >> answer the frequency without business needs, do
> >> differentials if needed - there is no way to answer this
> >> without know more on recover needs, database sizes, what is
> >> available for backups. Where you backup to and how you save
> >> those off depends on what's available to you, not what is
> >> best if this is something that just has to be throw
> >> together.
> >> I can't say it's ever been the same at any client's sites
> >> I've been to. All had different requirements and most have
> >> different requirements for different servers, databases.
> >> They have all been different so I'm not sure anyone can give
> >> you the one and only answer you are looking for that will
> >> ensure you are protected and able to recover all data with
> >> no downtime under any circumstance. It's just not always as
> >> simple as just backup and restore. If this is critical and
> >> absolutely no downtime ever is tolerated, then you must have
> >> some combination of clustering, replication, standby servers
> >> in place at alternative locations so that makes things a bit
> >> more complicated as well.
> >>
> >> -Sue
> >>
> >> On Tue, 27 Dec 2005 20:21:02 -0800, "alex"
> >> <alex@.discussions.microsoft.com> wrote:
> >>
> >> >well i wasn't really looking for a book i was looking for past
> >> >experiences or
> >> >advice as this needs to done within the next few weeks. Downtime is not
> >> >an
> >> >option because this server will be handling all the companies $$$
> >> >records. So
> >> >again i ask What's your procedures for sql backups and for recovery in
> >> >case
> >> >of any lost?
> >> >
> >> >
> >> >"Sue Hoegemeier" wrote:
> >> >
> >> >> Depends on what you define as a disaster and what the
> >> >> business requirements are in case of one of the defined
> >> >> disasters. One source would be the MS SQL Server High
> >> >> Availability book:
> >> >> http://www.microsoft.com/mspress/books/6515.asp
> >> >> SQL Server magazine has published a lot of articles on the
> >> >> topic, addressing different issue, recovery requirements:
> >> >> http://www.windowsitpro.com/SQLServer/
> >> >>
> >> >> -Sue
> >> >>
> >> >> On Tue, 27 Dec 2005 16:01:02 -0800, "alex"
> >> >> <alex@.discussions.microsoft.com> wrote:
> >> >>
> >> >> >Is there any good sql 2000 or 2005 disaster recovery plan or guide
> >> >> >out that
> >> >> >you guys used to come up with your own?
> >> >> >
> >> >> >What's your procedures do have for backups and for recovery?
> >> >> >
> >> >> >I asked that because i have been asked to implement a sql server to
> >> >> >run a
> >> >> >finacial program. I am a bit nerves because i don't know how to
> >> >> >recover from
> >> >> >a sql disaster can some help ?
> >> >>
> >> >>
> >>
> >>
>
>|||alex wrote:
> Are your systems sitting idle after 5pm till 8am the next day ? yes
> Why do you say there is no room to cluster servers ? because there isn't
> even a server room at this place. I am a tech for a company that does tech
> support contracting and where all this is going on is one of my locations i
> cover. But the servers are in some guys office because that's the only place
> they could have gone.
>
In that case you can forget about high availability. HA is not just a
DR procedure or some hardware - it is a whole approach and requires
commitment and planning of all aspects: physical location,
environmental control, security, power management, redundancy and all
the supporting policies, procedures and training. Aparently this
customer doesn't have the right level of commitment and without it,
your stated goal of "downtime is not an option" just isn't going to be
possible. Make sure the customer is aware of that fact.
One option is replication to some offsite location. Another may be
simply to shift the backups offsite and make arrangements for standby
hardware. You need to talk to the customer about the kind of scenarios
he wants to mitigate and decide what is possible within his budget. The
potential downtime will be the maximum amount of time it takes you to
recover and restore the system from go - something you should test out
for yourself.
--
David Portas
SQL Server MVP
--|||Pardon me for jumping in here, but your employers don't have a firm grasp on
reality. They are asking for everything and giving you nothing.
Fortunately, that is pretty common in this business and lots of us have
experience dealing with that sort of thing. Start by going back and getting
the book Sue recommended in her first post. This will teach you the
critical concepts of high availability that you need to understand. Once
you understand, then you need to communicate those concepts to your
company's management. The methodology is fairly simple, but the
implementation can be somewhat complex. First you find what are your actual
and potential barriers for availability. Sort them by greatest impact, then
address them with people, process, and technology.
For example, not having a secure computer room with redundant, conditioned
power and environment is probably your number one availability limiter.
I communicate this to management at various places by writing up a service
level agreement showing what their systems are capable of and what various
investments will do to change that availability. Flat out, this is what you
have and what you can get. Translate technical issues to dollars and risk
so the business decision makers can understand the problem.
Finally, don't expect technology to solve all your problems. As I said
before, a true highly available system has technology supported by people
and process. There are no shortcuts or discounts on the way.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"alex" <alex@.discussions.microsoft.com> wrote in message
news:1D9D751B-F1CA-4D45-B431-7043F8C5A946@.microsoft.com...
> Are your systems sitting idle after 5pm till 8am the next day ? yes
> Why do you say there is no room to cluster servers ? because there isn't
> even a server room at this place. I am a tech for a company that does tech
> support contracting and where all this is going on is one of my locations
> i
> cover. But the servers are in some guys office because that's the only
> place
> they could have gone.
> Whats the cost of downtime ? You need to figure that out. how much would
> the
> company lose in revenue should the server be unavailable for 5 mins vs 1hr
> vs all day ? And not to mention the credibility that goes along with it.
> The only major loss i can see is productivity 1 hr to one day would set
> them
> back a few weeks to a month.
> "Hassan" wrote:
>> Are your systems sitting idle after 5pm till 8am the next day ?
>> Why do you say there is no room to cluster servers ?
> Whats the cost of downtime ? You need to figure that out. how much would
> the
> company lose in revenue should the server be unavailable for 5 mins vs 1hr
> vs all day ? And not to mention the credibility that goes along with it.
>> All of these would help determine the appropriate solution.
>> I would be certain that the financial orgs have their highly critical
>> systems clustered at the very minimum and if some data loss is
>> acceptable,
>> possibly go with log shipping.
>> A lot can be done using synchronous mirroring to a remote site. SQL 2005
>> has
>> that feature built in with Database Mirroring, whereby a write on one
>> server
>> is committed to the primary and a secondary server before the user gets a
>> response. This ensures data is intact on both servers. However there is a
>> latency tied to this approach.
>> You could also work some sort of queueing/messaging system whereby if the
>> system goes offline, your transactions could start queuing..
>> Theres many ways to skin the cat.. Just start with the cost of downtime.
>> And
>> at the very minimum implement log shipping I would say at 5 min intervals
>> to
>> a hot standby server.
>>
>> "alex" <alex@.discussions.microsoft.com> wrote in message
>> news:9B51E4FE-AAA7-4CAB-80C1-DDAA0A414DE2@.microsoft.com...
>> > Well the server will be custom built raid 5 good tape back rotation and
>> > shadow copy for this situation because there is no room to cluster
>> > servers
>> > what so ever. Business hour are from 8am to 5pm and that whole time
>> > finacial
>> > records are going in and reports are coming out. I think the only time
>> > downtime would be allowed is if the system failed for some reason and
>> > then
>> > they would have no choice but to wait. Taking chances with this is not
>> > really
>> > an option i guess what i will end up doing is having some sort of back
>> > up
>> > plan to back up that plan and a plan to back that up.
>> >
>> > I just wanted to know how the sql pro's pre for any project dealing
>> > with
>> > finacial servers.
>> >
>> > "Sue Hoegemeier" wrote:
>> >
>> >> Lost data from what? User errors? Application errors?
>> >> Database loss? Server loss? Hardware failures? Flooding of
>> >> your server room? Is any downtime allowed? If yes, does that
>> >> depend on business hours, business cycles? If no, what are
>> >> you using for redundancy? Do you really need more than
>> >> 99.999% uptime? Do you know how much downtime that
>> >> calculates to a year?
>> >> Again, it depends on everything you need to define as a
>> >> disaster and the business requirements for these. If you
>> >> need to have this done in a few weeks and don't have the
>> >> answers to these and the business requirements, you can only
>> >> throw something together and hope for the best but you will
>> >> be taking chances.
>> >> Do full backups, do log backups and there is no way to
>> >> answer the frequency without business needs, do
>> >> differentials if needed - there is no way to answer this
>> >> without know more on recover needs, database sizes, what is
>> >> available for backups. Where you backup to and how you save
>> >> those off depends on what's available to you, not what is
>> >> best if this is something that just has to be throw
>> >> together.
>> >> I can't say it's ever been the same at any client's sites
>> >> I've been to. All had different requirements and most have
>> >> different requirements for different servers, databases.
>> >> They have all been different so I'm not sure anyone can give
>> >> you the one and only answer you are looking for that will
>> >> ensure you are protected and able to recover all data with
>> >> no downtime under any circumstance. It's just not always as
>> >> simple as just backup and restore. If this is critical and
>> >> absolutely no downtime ever is tolerated, then you must have
>> >> some combination of clustering, replication, standby servers
>> >> in place at alternative locations so that makes things a bit
>> >> more complicated as well.
>> >>
>> >> -Sue
>> >>
>> >> On Tue, 27 Dec 2005 20:21:02 -0800, "alex"
>> >> <alex@.discussions.microsoft.com> wrote:
>> >>
>> >> >well i wasn't really looking for a book i was looking for past
>> >> >experiences or
>> >> >advice as this needs to done within the next few weeks. Downtime is
>> >> >not
>> >> >an
>> >> >option because this server will be handling all the companies $$$
>> >> >records. So
>> >> >again i ask What's your procedures for sql backups and for recovery
>> >> >in
>> >> >case
>> >> >of any lost?
>> >> >
>> >> >
>> >> >"Sue Hoegemeier" wrote:
>> >> >
>> >> >> Depends on what you define as a disaster and what the
>> >> >> business requirements are in case of one of the defined
>> >> >> disasters. One source would be the MS SQL Server High
>> >> >> Availability book:
>> >> >> http://www.microsoft.com/mspress/books/6515.asp
>> >> >> SQL Server magazine has published a lot of articles on the
>> >> >> topic, addressing different issue, recovery requirements:
>> >> >> http://www.windowsitpro.com/SQLServer/
>> >> >>
>> >> >> -Sue
>> >> >>
>> >> >> On Tue, 27 Dec 2005 16:01:02 -0800, "alex"
>> >> >> <alex@.discussions.microsoft.com> wrote:
>> >> >>
>> >> >> >Is there any good sql 2000 or 2005 disaster recovery plan or guide
>> >> >> >out that
>> >> >> >you guys used to come up with your own?
>> >> >> >
>> >> >> >What's your procedures do have for backups and for recovery?
>> >> >> >
>> >> >> >I asked that because i have been asked to implement a sql server
>> >> >> >to
>> >> >> >run a
>> >> >> >finacial program. I am a bit nerves because i don't know how to
>> >> >> >recover from
>> >> >> >a sql disaster can some help ?
>> >> >>
>> >> >>
>> >>
>> >>
>>|||They have an offsite location but it doesn't have a internet connection if
they were to replicate the data offsite it would have to go to one of our
dc's. Stand by parts might be a good option but i don't want to have go
through that. They don't have any where to put servers because i guest they
never planned for a network. But based on what you folks have told me i will
put together options for them to choose from and hopefully at a good price
which should speed things up because this has been going on for months and i
am growing sick of it.
"David Portas" wrote:
> alex wrote:
> > Are your systems sitting idle after 5pm till 8am the next day ? yes
> >
> > Why do you say there is no room to cluster servers ? because there isn't
> > even a server room at this place. I am a tech for a company that does tech
> > support contracting and where all this is going on is one of my locations i
> > cover. But the servers are in some guys office because that's the only place
> > they could have gone.
> >
> In that case you can forget about high availability. HA is not just a
> DR procedure or some hardware - it is a whole approach and requires
> commitment and planning of all aspects: physical location,
> environmental control, security, power management, redundancy and all
> the supporting policies, procedures and training. Aparently this
> customer doesn't have the right level of commitment and without it,
> your stated goal of "downtime is not an option" just isn't going to be
> possible. Make sure the customer is aware of that fact.
> One option is replication to some offsite location. Another may be
> simply to shift the backups offsite and make arrangements for standby
> hardware. You need to talk to the customer about the kind of scenarios
> he wants to mitigate and decide what is possible within his budget. The
> potential downtime will be the maximum amount of time it takes you to
> recover and restore the system from go - something you should test out
> for yourself.
> --
> David Portas
> SQL Server MVP
> --
>