Efficient SQL Backup?

Hi all,
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'Sounds like a typical log shipping scenario. If the job fails at source you
do may have the option of applying the logs manually to bring the standby
server up-to-date without restoring the complete backup.
The link below show the process using Microsoft's log shipping solution but
a manual method will achive the same result.
http://www.microsoft.com/technet/pr...fr=
true
"Vishal" wrote:

> Hi all,
> 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 suggest you try in a different forum for server or admin things.
David
"Vishal" <bajaj.vishal@.gmail.com> wrote in message
news:1145456687.737152.87130@.g10g2000cwb.googlegroups.com...
> Hi all,
> 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'
>|||Thanks a lot. let me try somthing else here .