Zorba,
A full database backup does not truncate the transaction log. When you =
start log shipping, you can make as many full backups of the primary =
database as you want - it will not affect log shipping. However, you =
cannot make both a full database backup and a transaction log backup of =
the same database at the same time.
Hope this helps,
Ron
--=20
Ron Talmage
SQL Server MVP
[quoted text, click to view] "Zorba" <nospam@nonexistent> wrote in message =
news:OX0Z6LemEHA.3336@TK2MSFTNGP10.phx.gbl...
Hi,
I am in the process of setting up log shipping for a large database ~ =
1GB over VPN and slow WAN link.=20
I intend to setup and sync the servers on main office and ship after =
that, the warm standby db to remote site.
My question is how the daily full backups of database will afect my =
log shipping.=20
To keep this servers in sync I intend to use only daily transaction =
logs backups/restores. I do not want to copy a full backup of 1GB daily =
over the WAN. However at local site I still want to perform a daily full =
backup.=20
As I know when a full backup run it will also truncate the transaction =
logs, so if these large daily full backups will not be copied and =
restored over the WAN, the warm standby server will run out of sync. =
This is because a part of transaction log that will be truncated when =
full backup is done will not be restored to remote site.
Is there any way to do full backups after initial sync without =
truncating the transaction logs? Has anyone an answer to my problem?
Thank you,