|
|
Posted by Erland Sommarskog on 06/15/32 11:45
Vishal (bajaj.vishal@gmail.com) writes:
> I am having issues of efficiency of backing up data from one SQL data
> base to another.
>
> The two servers in questions are on different networks , behind
> different firewalls. We have MS SQL 2000.
>
> On the source data i run a job with the following steps:
>
> 1> take trans backup every 4 hrs
> 2> ftp to the remote server
> 3> if ftp fails , disable the whole job
>
> On the target server I run a job which does the following
>
> 1> restore the trans backup with NORECOVERY.
>
> If the job fails at target. I will have to go through the whole process
> of doing a complete backup of the source , restoring it at the other
> ens and then starting trans-backup again.
>
> Also, if we do a failover to the target server, then when we roll back
> to the source server again we have to da a back-up of the target and
> restore it on the source server.
>
> Is ther a more efficent way of doing this??
I'm not sure exactly the purpose of this home-made log shipping is,
but could replication be a better alternative?
(Although, I have no idea whether replication can cross your network
and firewalls.)
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|