Redundancy

Is there any untility, program, or script that I can use to backup a SQL
database and will look for the main SQL server? If for anyreason that server
is not seen on the network a backup server will pick up from the last back up
and carry on where the first server left off. It seems logical there would
be.For starters, check out Fail-over Clustering in the SQL Server Books Online.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:64D81DCB-E75E-437C-9FE4-D007EB19B016@.microsoft.com...
> Is there any untility, program, or script that I can use to backup a SQL
> database and will look for the main SQL server? If for anyreason that
> server
> is not seen on the network a backup server will pick up from the last back
> up
> and carry on where the first server left off. It seems logical there
> would
> be.|||Hi
For the various highg availablility options check out:
http://www.microsoft.com/sql/techinfo/administration/2000/availability.asp
John
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:64D81DCB-E75E-437C-9FE4-D007EB19B016@.microsoft.com...
> Is there any untility, program, or script that I can use to backup a SQL
> database and will look for the main SQL server? If for anyreason that
> server
> is not seen on the network a backup server will pick up from the last back
> up
> and carry on where the first server left off. It seems logical there
> would
> be.|||Dan,
Would this only work on either NT or 2k Server or could this be done on any
MS OS? Exactly what I am trying to solve is this: I am working with a Point
of Sale software that uses either MSDE or SQL Server for the larger sites to
control the databases. My problem is what happens if the main server goes
down? Clustering could be an option. Any other ideas?
"Dan Guzman" wrote:
> For starters, check out Fail-over Clustering in the SQL Server Books Online.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:64D81DCB-E75E-437C-9FE4-D007EB19B016@.microsoft.com...
> > Is there any untility, program, or script that I can use to backup a SQL
> > database and will look for the main SQL server? If for anyreason that
> > server
> > is not seen on the network a backup server will pick up from the last back
> > up
> > and carry on where the first server left off. It seems logical there
> > would
> > be.
>
>|||> Would this only work on either NT or 2k Server or could this be done on
> any
> MS OS?
You need SQL Server Enterprise edition as well as one of the server OS
editions below. From the Books Online Fail-over Clustering overview:
<Excerpt href-"adminsql.chm::/ad_clustering_7t9v.htm">
Before installing failover clustering, you must install Microsoft Windows
NT® 4.0, Enterprise Edition, Microsoft Windows® 2000 Advanced Server or
Windows 2000 Datacenter Server, and the Microsoft Cluster Service (MSCS).
</Excerpt>
Additionally, you need to have supported hardware, including shared disks.
Clustering may be an option for you larger POS implementations but not for
the MSDE ones.
There are some new high-availability features in the upcoming SQL 2005
version that don't require specialized clustering hardware. See the
high-availability demo at
http://www.microsoft.com/sql/2005/productinfo/demos/hademo.asp
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:3D25F3F5-E235-41CA-9693-2E176116AA8A@.microsoft.com...
> Dan,
> Would this only work on either NT or 2k Server or could this be done on
> any
> MS OS? Exactly what I am trying to solve is this: I am working with a
> Point
> of Sale software that uses either MSDE or SQL Server for the larger sites
> to
> control the databases. My problem is what happens if the main server goes
> down? Clustering could be an option. Any other ideas?
> "Dan Guzman" wrote:
>> For starters, check out Fail-over Clustering in the SQL Server Books
>> Online.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Paul" <Paul@.discussions.microsoft.com> wrote in message
>> news:64D81DCB-E75E-437C-9FE4-D007EB19B016@.microsoft.com...
>> > Is there any untility, program, or script that I can use to backup a
>> > SQL
>> > database and will look for the main SQL server? If for anyreason that
>> > server
>> > is not seen on the network a backup server will pick up from the last
>> > back
>> > up
>> > and carry on where the first server left off. It seems logical there
>> > would
>> > be.
>>|||Paul,
SQL Server Enterprise Edition is going to cost you a fair bit. One of the
best third party products I have seen is XOSoft's WANYSyncHA.
see: www.xosoft.com
The WANYSyncHA product allows automatic failover to another server, with
continously replicating changes at the byte level.
It also includes Data Rewind which allows you to restore the database to a
particular snapshot should both databases become corrupt.
Regards,
Andrew
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:3D25F3F5-E235-41CA-9693-2E176116AA8A@.microsoft.com...
> Dan,
> Would this only work on either NT or 2k Server or could this be done on
any
> MS OS? Exactly what I am trying to solve is this: I am working with a
Point
> of Sale software that uses either MSDE or SQL Server for the larger sites
to
> control the databases. My problem is what happens if the main server goes
> down? Clustering could be an option. Any other ideas?
> "Dan Guzman" wrote:
> > For starters, check out Fail-over Clustering in the SQL Server Books
Online.
> >
> > --
> > Hope this helps.
> >
> > Dan Guzman
> > SQL Server MVP
> >
> > "Paul" <Paul@.discussions.microsoft.com> wrote in message
> > news:64D81DCB-E75E-437C-9FE4-D007EB19B016@.microsoft.com...
> > > Is there any untility, program, or script that I can use to backup a
SQL
> > > database and will look for the main SQL server? If for anyreason that
> > > server
> > > is not seen on the network a backup server will pick up from the last
back
> > > up
> > > and carry on where the first server left off. It seems logical there
> > > would
> > > be.
> >
> >
> >|||Correction, product is WANSynchHA, not WANYSyncHA..
Andrew
"Andrew" <me@.anonymous.com> wrote in message
news:41bf7b50$1_1@.news.iprimus.com.au...
> Paul,
> SQL Server Enterprise Edition is going to cost you a fair bit. One of the
> best third party products I have seen is XOSoft's WANYSyncHA.
> see: www.xosoft.com
> The WANYSyncHA product allows automatic failover to another server, with
> continously replicating changes at the byte level.
> It also includes Data Rewind which allows you to restore the database to a
> particular snapshot should both databases become corrupt.
> Regards,
> Andrew
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:3D25F3F5-E235-41CA-9693-2E176116AA8A@.microsoft.com...
> > Dan,
> >
> > Would this only work on either NT or 2k Server or could this be done on
> any
> > MS OS? Exactly what I am trying to solve is this: I am working with a
> Point
> > of Sale software that uses either MSDE or SQL Server for the larger
sites
> to
> > control the databases. My problem is what happens if the main server
goes
> > down? Clustering could be an option. Any other ideas?
> >
> > "Dan Guzman" wrote:
> >
> > > For starters, check out Fail-over Clustering in the SQL Server Books
> Online.
> > >
> > > --
> > > Hope this helps.
> > >
> > > Dan Guzman
> > > SQL Server MVP
> > >
> > > "Paul" <Paul@.discussions.microsoft.com> wrote in message
> > > news:64D81DCB-E75E-437C-9FE4-D007EB19B016@.microsoft.com...
> > > > Is there any untility, program, or script that I can use to backup a
> SQL
> > > > database and will look for the main SQL server? If for anyreason
that
> > > > server
> > > > is not seen on the network a backup server will pick up from the
last
> back
> > > > up
> > > > and carry on where the first server left off. It seems logical
there
> > > > would
> > > > be.
> > >
> > >
> > >
>