|
|
Posted by Greg D. Moore \(Strider\) on 05/10/06 06:49
"laststubborn" <arafatsalih@gmail.com> wrote in message
news:1147185632.084129.202140@j73g2000cwa.googlegroups.com...
>
> Greg D. Moore (Strider) wrote:
> > "laststubborn" <arafatsalih@gmail.com> wrote in message
> > news:1147164897.180455.80350@j33g2000cwa.googlegroups.com...
> > > Dear All,
> > >
> > > We have a big concern in our Database system. We have 2000
transactions
> > > daily in our database. We need to replicate some how the database for
> > > our fail over setup. I tried transactional replication at midnight but
> > > our all systems locked and we had a lot of complaints from the
> > > customers and It was taking a lot of time to snapshot part and I had
to
> > > abort it because of these reasons.
> >
> > Why do the transactional replication only at midnight? Better off doing
it
> > continually throughout the day.
>
> The thing is snapshot taking a lot of time to do it. Even at night we
> had a problem with customers.
I'm not following, or we're not communicating effectively. A transactional
backup should not be taking that long or have that much impact. How large
are these transactions? Like I say, I have a system doing that many a
minute (though that one we don't backup). The one we do transactional
backups on every 20 minutes probably does 2000/hour or more at peak time.
(plus a very high number of pure select only queries.)
>
> >
> > And btw, 2000 transactions, unless they're huge, is trivial. I have
systems
> > doing that per minute.
> >
> > The other option is to look into log shipping.
> >
> > There are scripts out there that let you do it even w/o Enterprise
edition,
> > though it is then admittedly more manual.
>
> As you said it is manual we can not afford manual solutions.
Well, what do you consider too manual. In the case of many of these scripts
the failover itself may or may not be automatic, but can generally be
scripted. The log-shipping itself is scripted.
In our case, we do log backups from our main server every 20 minutes and
restore them to our backup server every 20 minutes, but with either a 4 hour
or 6 hour delay (I forget which). To bring the backup system "up to date" I
can do in about 15 minutes.. either manually or via running a quick script.
The bigger delay (whcih we'd have using Enterprise Server also) is updating
our front end DSNs. And we have that scripted also.
All in all, a failover would probably take us 15 minutes or less to recover
from.
>
> Thanks
>
> >
> >
> > > I need an advice how I can create a replication or is there any other
> > > way to replicate or is there any way to do this process without
> > > bothering the system? Please give me some advice and help..
> > >
> > > Thanks
> > > asa.
> > >
>
Navigation:
[Reply to this message]
|