Log Shipping In Syn?

Hi,
If I set up the backup of the log file every 5 mins and I also setup the
copy every 5 mins same as restore every 5 mins, I don't think I am going to
get the database updated every 5 mins since the backup and copy could take
more time to finish. Is there any way to make sure everything in sequence,
Cackup-->Copy-->Restore in stead of calculating the time for log shipping?
Thanks
Ed
Ed - one thing you can do is to have a higher frequency fro the restores
than the copies eg once a minute for the restore. This way you can minimise
the dead time.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||That is a good idea, Paul. I think the same setup can be applied for copy
and backup, higher frequency for copy than backup
Thanks
"Paul Ibison" wrote:

> Ed - one thing you can do is to have a higher frequency fro the restores
> than the copies eg once a minute for the restore. This way you can minimise
> the dead time.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
|||There are two ways of doing log shipping - synchronously - the way you do
it, and asynchronously.
With synchronous a job, does the backup, copies it to the secondary, and
then applies the log there. Then the job completes and the next scheduled
job runs. If there is some overlap you miss a scheduled backup, copy,
restore operation, but log shipping is resilient to this.
With asynchronous you dump, and then another job does the copy and a third
job does the restore. Backups will be queued at the primary until they are
copied, and then queued at the secondary and applied in order there. The
advantage of this is that your exposure to data loss is much less.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:9F855BA3-1813-4ACA-B2A0-008FC8ED8B40@.microsoft.com...
> Hi,
> If I set up the backup of the log file every 5 mins and I also setup the
> copy every 5 mins same as restore every 5 mins, I don't think I am going
> to
> get the database updated every 5 mins since the backup and copy could take
> more time to finish. Is there any way to make sure everything in
> sequence,
> Cackup-->Copy-->Restore in stead of calculating the time for log shipping?
> Thanks
> Ed
|||Hilary ,
I would like to make sure I don't misunderstand what you mean
Do you mean I should put three steps (backup --> copy --> restore) into one
job? Inside the job, I should do "Go To Next Step if succeed" in order to do
"synchronously".
The way that the SSMS uses to setup is "asynchronously"?
Thanks again
Ed
"Hilary Cotter" wrote:

> There are two ways of doing log shipping - synchronously - the way you do
> it, and asynchronously.
> With synchronous a job, does the backup, copies it to the secondary, and
> then applies the log there. Then the job completes and the next scheduled
> job runs. If there is some overlap you miss a scheduled backup, copy,
> restore operation, but log shipping is resilient to this.
> With asynchronous you dump, and then another job does the copy and a third
> job does the restore. Backups will be queued at the primary until they are
> copied, and then queued at the secondary and applied in order there. The
> advantage of this is that your exposure to data loss is much less.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Ed" <Ed@.discussions.microsoft.com> wrote in message
> news:9F855BA3-1813-4ACA-B2A0-008FC8ED8B40@.microsoft.com...
>
>
|||Yes, for an example of how to do this have a look at this -
http://www.sql-server-performance.com/sql_server_log_shipping.asp
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:D29A7CCA-621C-4202-9452-AE814179F8D4@.microsoft.com...[vbcol=seagreen]
> Hilary ,
> I would like to make sure I don't misunderstand what you mean
> Do you mean I should put three steps (backup --> copy --> restore) into
> one
> job? Inside the job, I should do "Go To Next Step if succeed" in order to
> do
> "synchronously".
> The way that the SSMS uses to setup is "asynchronously"?
> Thanks again
> Ed
> "Hilary Cotter" wrote: