Log Shipping with additional backups

I am planning to implement log shipping between two servers.
I understand that if I perform a full database backup of the primary
database during the log shipping, this will have no effect on the log
shipping. If I am log shipping every 30 minutes, so I have a log backup at
09:00 and 09:30, perform a full database backup at 09:15, the log backup at
09:30 will contain all changes from 09:00.
Can I use this full database backup and the log shipping logs to perform a
database recovery? Can I restore the 09:15 full backup and then the 09:30
log? Or, do I need to perform additional log backups, e.g. every hour? If
so, how do these log backups affect the log shipping backups?
Many ThanksYes you can use the log shipping log backups to do a recovery. You will
probably have to look at your log shipping scripts to make sure they are not
deleting the log backup files.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"si" <si@.discussions.microsoft.com> wrote in message
news:819CBAE2-0A90-42BB-8B2B-2B1DFF7DBE05@.microsoft.com...
>I am planning to implement log shipping between two servers.
> I understand that if I perform a full database backup of the primary
> database during the log shipping, this will have no effect on the log
> shipping. If I am log shipping every 30 minutes, so I have a log backup
> at
> 09:00 and 09:30, perform a full database backup at 09:15, the log backup
> at
> 09:30 will contain all changes from 09:00.
> Can I use this full database backup and the log shipping logs to perform a
> database recovery? Can I restore the 09:15 full backup and then the 09:30
> log? Or, do I need to perform additional log backups, e.g. every hour?
> If
> so, how do these log backups affect the log shipping backups?
> Many Thanks

Log Shipping with additional backups

I am planning to implement log shipping between two servers.
I understand that if I perform a full database backup of the primary
database during the log shipping, this will have no effect on the log
shipping. If I am log shipping every 30 minutes, so I have a log backup at
09:00 and 09:30, perform a full database backup at 09:15, the log backup at
09:30 will contain all changes from 09:00.
Can I use this full database backup and the log shipping logs to perform a
database recovery? Can I restore the 09:15 full backup and then the 09:30
log? Or, do I need to perform additional log backups, e.g. every hour? If
so, how do these log backups affect the log shipping backups?
Many ThanksYes you can use the log shipping log backups to do a recovery. You will
probably have to look at your log shipping scripts to make sure they are not
deleting the log backup files.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"si" <si@.discussions.microsoft.com> wrote in message
news:819CBAE2-0A90-42BB-8B2B-2B1DFF7DBE05@.microsoft.com...
>I am planning to implement log shipping between two servers.
> I understand that if I perform a full database backup of the primary
> database during the log shipping, this will have no effect on the log
> shipping. If I am log shipping every 30 minutes, so I have a log backup
> at
> 09:00 and 09:30, perform a full database backup at 09:15, the log backup
> at
> 09:30 will contain all changes from 09:00.
> Can I use this full database backup and the log shipping logs to perform a
> database recovery? Can I restore the 09:15 full backup and then the 09:30
> log? Or, do I need to perform additional log backups, e.g. every hour?
> If
> so, how do these log backups affect the log shipping backups?
> Many Thanks

Log Shipping with additional backups

I am planning to implement log shipping between two servers.
I understand that if I perform a full database backup of the primary
database during the log shipping, this will have no effect on the log
shipping. If I am log shipping every 30 minutes, so I have a log backup at
09:00 and 09:30, perform a full database backup at 09:15, the log backup at
09:30 will contain all changes from 09:00.
Can I use this full database backup and the log shipping logs to perform a
database recovery? Can I restore the 09:15 full backup and then the 09:30
log? Or, do I need to perform additional log backups, e.g. every hour? If
so, how do these log backups affect the log shipping backups?
Many Thanks
Yes you can use the log shipping log backups to do a recovery. You will
probably have to look at your log shipping scripts to make sure they are not
deleting the log backup files.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"si" <si@.discussions.microsoft.com> wrote in message
news:819CBAE2-0A90-42BB-8B2B-2B1DFF7DBE05@.microsoft.com...
>I am planning to implement log shipping between two servers.
> I understand that if I perform a full database backup of the primary
> database during the log shipping, this will have no effect on the log
> shipping. If I am log shipping every 30 minutes, so I have a log backup
> at
> 09:00 and 09:30, perform a full database backup at 09:15, the log backup
> at
> 09:30 will contain all changes from 09:00.
> Can I use this full database backup and the log shipping logs to perform a
> database recovery? Can I restore the 09:15 full backup and then the 09:30
> log? Or, do I need to perform additional log backups, e.g. every hour?
> If
> so, how do these log backups affect the log shipping backups?
> Many Thanks

Log Shipping will not restore tran logs on secondary server

We're planning to implement log shipping on our databases, and I have been toiling with it all weekend trying to get it to work on some test databases. The result is the same whether I do it via the wizard or manually via T-SQL.

I am using 3 servers, all SQL Server 2005 Standard SP1. All 3 SQL Servers are configured identically.

When I setup log shipping, it initializes with no problems. When it processes the first tran log file, it restores it with no problem. Every successive log file thereafter is not restored. No errors are generated. The only outright indication of a problem is that the monitor server shows that there has not been a recent restore.

The backup and copy both suceed. The restore claims to suceed. If I review the job history for each step, it says that it skipped the log file and then reports that it did not fina any log files to restore.

Message
2006-11-06 05:00:01.92 Skipped log backup file. Secondary DB: 'MyDemo', File: 'D:\MSSQL\Backup\MyDemo\MyDemo_20061106115619.trn'

Message
2006-11-06 05:00:01.95 Could not find a log backup file that could be applied to secondary database 'MyDemo'.
2006-11-06 05:00:01.96 The restore operation was successful. Secondary Database: 'MyDemo', Number of log backup files restored: 0

Any ideas or suggestions?

A little more info for you. I can manually restore the successive log file backups without any errors. However, the output says that there were 0 pages processed. The successive log files are being created empty. Well, these are test databases, so there are no active transactions ocurring, so no big surprise, right? I updated a lot of data in the tables, and the next log file is ....... empty.

So even with committed transactions ocurring, the tran log backup is still empty.

|||

I found the problem. It was a security setting that the Log Shipping wizard does not give you the ability to change. It defaulted to using Windows security (the account used by SQL Agent) for the connection to the Monitor server to update the state of the restore process. Because we use local system accounts, not domain accounts, for SQL Agent, it was not able to update the Monitor.

My scripts were based off of the first log shipping instance that I set up, so the option to change it there wasn’t included in the script generated by SQL Server. Since I originally set it up with the primary, secondary, and monitor on my local machine, it worked fine.

In the wizard, there is a setting for the account that the monitor should use, but it only affects the primary's connection to the monitor, not the secondary's connection.

log shipping question

Hi Guys,
i am planning to implement logshipping on sql 2000 EE.
i have two questions on this.
i am planning to use log shipping interval of 2 minutes
1) can dump the transaction log backup on network share
instead of production server.
if yes will it have any other impact?
2) every month i am rebuilding my indexes which will
create a huge transaction log
will it create any problem on log shipping.
pls advice me
Biju
Biju,
1: network share is OK. Obviously if the sahre is unavailable then there'll
be a problem, so local folders are normally used.
2: make sure the load and copy frequency are both one minute and this should
prevent a backlog building up.
HTH,
Paul Ibison

Log shipping procedure with replication

hello experts,

Im new to sqlserver database and i really need ur advice on this.

We are planning to setup logshipping for our sqlserver 2005 database.Our setup is like this

we have a primary database on server A which has to be logshipped to Server C.A reporting server B is also maintained by doing transactional replication between Server A and Server B.

Now i want to know whether the procedure for carrying out logshipping process between server A and Server C will remain the same or wil there be any change because a replication is also going on server A .Please give me a step by step procedure for doing the logshipping on a server which is even involved in replication process.

Thanks in advance

Regards

Arvind L

Hi Arvind,
Welcome to the world of Sql Server
pls refer the link it might help you, http://msdn2.microsoft.com/en-us/library/ms151224.aspx

Thanxx
Deepak

|||

Thanks deepak..

Log shipping procedure with replication

hello experts,

Im new to sqlserver database and i really need ur advice on this.

We are planning to setup logshipping for our sqlserver 2005 database.Our setup is like this

we have a primary database on server A which has to be logshipped to Server C.A reporting server B is also maintained by doing transactional replication between Server A and Server B.

Now i want to know whether the procedure for carrying out logshipping process between server A and Server C will remain the same or wil there be any change because a replication is also going on server A .Please give me a step by step procedure for doing the logshipping on a server which is even involved in replication process.

Thanks in advance

Regards

Arvind L

Hi Arvind,
Welcome to the world of Sql Server
pls refer the link it might help you, http://msdn2.microsoft.com/en-us/library/ms151224.aspx

Thanxx
Deepak

|||

Thanks deepak..

Log Shipping prerequistes

Hello

We are using SQL Server 2005 EE in Production and Staging Datacenters. We are planning to set up LS between Prod XXX DB and Staging YYY DB.

1. IF Secondary DB is not with the same name of Primary any conflicts for restore?

2. If Primary DB has data drives different than secondary db, any issues with file and file systems in LS?

3. ANY Open issues related to LS

Please advice and give us sites and links to watch this LS scenario. Thanks

refer this link,
http://sql-articles.com/articles/lship/lship.htm

1. No, primary db and secondary db can be with different names.
2. That should not be a problem
3. Ensure that the recovery model is Full for your db

But in database mirroring the principal db and secondary db need to have the same name......
ensure that there is sufficient privileges for the service accounts in primary and secondary servers for the shared folder as mentioned in the above link.....

log shipping initial backup restore

hi,
sql2000 enterprise edi. Planning for 15 min log shipping .
database size is around 6 gb. took the full backup and try to copy to the
secondary server over the network taking too much of time (say .5mb/sec).
meanwhile i stoped the transaction log backup . because the full backup is
not restored in the secondary server. my question is , ' can i restore log
backups after the full backup restore on secondary to make sync. ? then start
the log shipping process? or peer to peer connection needed in between
primary and secondary?
2) Another question : after the reindex process, the log file size will be
similar to dbsize. so transafering the log file over the network will take
take and log shipping may break because of copy time? how can i handle this?
thanks
Hello
I had a quick question - Did you start the file copy process for your
Complete backup through the Log Shipping Setup wizard?
Assuming that you did not, then regarding your first question :
You can actually perform the transaction log backups on your primary server
while the complete backup is copying over.
1. Once the complete backup is finished copying, start the restore of this
complete backup in NORECOVERY mode and in the meantime start copying over
the transaction log backups.
2. When the restore of the complete backup is complete, start applying the
transaction logs with NORECOVERY option.
3. At some point, stop performing transaction log backups on your primary
server and complete copying/restoring the transaction log backups on the
secondary server.
4. Once the secondary database is ready, start the Log Shipping Setup
Wizard (through the Maintenance Plan) and on the Log Shipping secondary
dialog, select Existing database option and select the NORECOVERY database
that you have created in steps earlier. Selecting this option will prevent
the Wizard from actually initiating a copy/load of the complete backup
during setup.
Regarding your second question:
Since rebuilding an index is a logged operation, there is no way for you to
get around this problem. The only way you can avoid this is by
reinitializing log shipping which is going to be more time consuming. Think
of this process as "keeping your secondary database in complete sync with
your primary". Assume for a second that as soon as you've finished
restoring the large transaction log backup (performed after the index
rebuild operation) to the secondary standby database, your primary database
goes offline. At this point since you have to bring the secondary online,
you would expect it to perform just as fast as your primary (given all
other factors including hardware etc are the same between the 2 machines).
Well if there was a way for you to avoid transferring the info related to
index rebuild to the secondary, the performance on your secondary most
likely would be very slow since there were no index updates performed on it.
Let me know if you have further questions.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||pankaj,
Thanks for you suggestion.
I took the full backup and copied over the network to the standby server,
before starting Logshipping process Setup. But it was very slow. For setting
up logshipping for production environment, i dont want any sync problems
like copying delay and restore log after the reindex process. I want to
know that whether i missed something.
I am thinking of adding one more NIC to my production server to connect to
the standby to improve the copy process.
"Pankaj Agarwal [MSFT]" <pankaja@.online.microsoft.com> wrote in message
news:k0XK9CVkEHA.2656@.cpmsftngxa10.phx.gbl...
> Hello
> I had a quick question - Did you start the file copy process for your
> Complete backup through the Log Shipping Setup wizard?
> Assuming that you did not, then regarding your first question :
> You can actually perform the transaction log backups on your primary
server
> while the complete backup is copying over.
> 1. Once the complete backup is finished copying, start the restore of this
> complete backup in NORECOVERY mode and in the meantime start copying over
> the transaction log backups.
> 2. When the restore of the complete backup is complete, start applying the
> transaction logs with NORECOVERY option.
> 3. At some point, stop performing transaction log backups on your primary
> server and complete copying/restoring the transaction log backups on the
> secondary server.
> 4. Once the secondary database is ready, start the Log Shipping Setup
> Wizard (through the Maintenance Plan) and on the Log Shipping secondary
> dialog, select Existing database option and select the NORECOVERY database
> that you have created in steps earlier. Selecting this option will prevent
> the Wizard from actually initiating a copy/load of the complete backup
> during setup.
> Regarding your second question:
> Since rebuilding an index is a logged operation, there is no way for you
to
> get around this problem. The only way you can avoid this is by
> reinitializing log shipping which is going to be more time consuming.
Think
> of this process as "keeping your secondary database in complete sync with
> your primary". Assume for a second that as soon as you've finished
> restoring the large transaction log backup (performed after the index
> rebuild operation) to the secondary standby database, your primary
database
> goes offline. At this point since you have to bring the secondary online,
> you would expect it to perform just as fast as your primary (given all
> other factors including hardware etc are the same between the 2 machines).
> Well if there was a way for you to avoid transferring the info related to
> index rebuild to the secondary, the performance on your secondary most
> likely would be very slow since there were no index updates performed on
it.
> Let me know if you have further questions.
> Thank you for using Microsoft newsgroups.
> Sincerely
> Pankaj Agarwal
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
|||Unfortunately there is no way to get around the large transaction log when
you are performing index rebuild. If you feel that adding another NIC will
provide better bandwidth and hence faster copy, then that may be something
to consider.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

log shipping initial backup restore

hi,
sql2000 enterprise edi. Planning for 15 min log shipping .
database size is around 6 gb. took the full backup and try to copy to the
secondary server over the network taking too much of time (say .5mb/sec).
meanwhile i stoped the transaction log backup . because the full backup is
not restored in the secondary server. my question is , ' can i restore log
backups after the full backup restore on secondary to make sync. ? then star
t
the log shipping process? or peer to peer connection needed in between
primary and secondary?
2) Another question : after the reindex process, the log file size will be
similar to dbsize. so transafering the log file over the network will take
take and log shipping may break because of copy time? how can i handle this
?
thanksHello
I had a quick question - Did you start the file copy process for your
Complete backup through the Log Shipping Setup wizard?
Assuming that you did not, then regarding your first question :
You can actually perform the transaction log backups on your primary server
while the complete backup is copying over.
1. Once the complete backup is finished copying, start the restore of this
complete backup in NORECOVERY mode and in the meantime start copying over
the transaction log backups.
2. When the restore of the complete backup is complete, start applying the
transaction logs with NORECOVERY option.
3. At some point, stop performing transaction log backups on your primary
server and complete copying/restoring the transaction log backups on the
secondary server.
4. Once the secondary database is ready, start the Log Shipping Setup
Wizard (through the Maintenance Plan) and on the Log Shipping secondary
dialog, select Existing database option and select the NORECOVERY database
that you have created in steps earlier. Selecting this option will prevent
the Wizard from actually initiating a copy/load of the complete backup
during setup.
Regarding your second question:
Since rebuilding an index is a logged operation, there is no way for you to
get around this problem. The only way you can avoid this is by
reinitializing log shipping which is going to be more time consuming. Think
of this process as "keeping your secondary database in complete sync with
your primary". Assume for a second that as soon as you've finished
restoring the large transaction log backup (performed after the index
rebuild operation) to the secondary standby database, your primary database
goes offline. At this point since you have to bring the secondary online,
you would expect it to perform just as fast as your primary (given all
other factors including hardware etc are the same between the 2 machines).
Well if there was a way for you to avoid transferring the info related to
index rebuild to the secondary, the performance on your secondary most
likely would be very slow since there were no index updates performed on it.
Let me know if you have further questions.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||pankaj,
Thanks for you suggestion.
I took the full backup and copied over the network to the standby server,
before starting Logshipping process Setup. But it was very slow. For setting
up logshipping for production environment, i dont want any sync problems
like copying delay and restore log after the reindex process. I want to
know that whether i missed something.
I am thinking of adding one more NIC to my production server to connect to
the standby to improve the copy process.
"Pankaj Agarwal [MSFT]" <pankaja@.online.microsoft.com> wrote in message
news:k0XK9CVkEHA.2656@.cpmsftngxa10.phx.gbl...
> Hello
> I had a quick question - Did you start the file copy process for your
> Complete backup through the Log Shipping Setup wizard?
> Assuming that you did not, then regarding your first question :
> You can actually perform the transaction log backups on your primary
server
> while the complete backup is copying over.
> 1. Once the complete backup is finished copying, start the restore of this
> complete backup in NORECOVERY mode and in the meantime start copying over
> the transaction log backups.
> 2. When the restore of the complete backup is complete, start applying the
> transaction logs with NORECOVERY option.
> 3. At some point, stop performing transaction log backups on your primary
> server and complete copying/restoring the transaction log backups on the
> secondary server.
> 4. Once the secondary database is ready, start the Log Shipping Setup
> Wizard (through the Maintenance Plan) and on the Log Shipping secondary
> dialog, select Existing database option and select the NORECOVERY database
> that you have created in steps earlier. Selecting this option will prevent
> the Wizard from actually initiating a copy/load of the complete backup
> during setup.
> Regarding your second question:
> Since rebuilding an index is a logged operation, there is no way for you
to
> get around this problem. The only way you can avoid this is by
> reinitializing log shipping which is going to be more time consuming.
Think
> of this process as "keeping your secondary database in complete sync with
> your primary". Assume for a second that as soon as you've finished
> restoring the large transaction log backup (performed after the index
> rebuild operation) to the secondary standby database, your primary
database
> goes offline. At this point since you have to bring the secondary online,
> you would expect it to perform just as fast as your primary (given all
> other factors including hardware etc are the same between the 2 machines).
> Well if there was a way for you to avoid transferring the info related to
> index rebuild to the secondary, the performance on your secondary most
> likely would be very slow since there were no index updates performed on
it.
> Let me know if you have further questions.
> Thank you for using Microsoft newsgroups.
> Sincerely
> Pankaj Agarwal
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>|||Unfortunately there is no way to get around the large transaction log when
you are performing index rebuild. If you feel that adding another NIC will
provide better bandwidth and hence faster copy, then that may be something
to consider.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

log shipping between sql 2005 clusters

hi

I am working for a small govt dept.We are planning to implement sql 2005.

We will be having sql 2005 instance in active/passive cluster mode

We will also have a standby sql server 2005 in active/passive cluster mode.

i need to know how to configure log shipping between my primary and secondary?

Is logshipping the best option?

Thanks

Is logshipping the best option for what? Logshipping is a fine technology but there are other ways to get data to a secondary server. You can use database mirroring in SQL Server 2005. For failover purposes this is a great option. You can also use database snapshots on the same server for various reasons to. Logshipping is perfectly viable too. What are you trying to accomplish? Having redundancy outside of the cluster? Read Only reporting copy of data?

Having that info can help us help you make your choice. I would say look up in Books Online Logshipping, Database Snapshots and Database Mirroring.

|||

Thank you very much for the reply.

I need to have an exact replica of the live enviornment (production cluster) to be switched to (standby cluster) in case of any probs to the primary. We also do switching between primary and standby every week. Basically the standby is like having a disaster recovery site. Its having Redundancy outside the cluster.

Please suggest....

Thanks in advance

|||

Options are

Database Mirroring

Can be operated in Synchronous mode which means your standby will be an exact replica of your primary database. Switching between the two is easy.

However it doesn't support replication and in synchronous mode the data has to be written to the standby and so may impact performance of your app if your network connection isn't great.

You can work in Asynchronous mode in which case the data is written to the standby at some point after the application has finished the transaction, i.e. no impact on the application. However in this mode you may loose data if your primary goes down and the transaction hasn't made it to the standby.

Database Mirroing has automatic failover in the event of a failure (when used with a witness server)

Log Shipping

Very much like asynchronous mirroring however it supports multiple targets i.e. you could have 2 standby servers, you can't do that with mirroring. Also the mechanism for applying the logs is via a copy and restore model which is slightly different to mirroring.

Replication

Much more complicated than the two above but allows for your production to be in read/write mode (although changes are not replicated back to the primary). This is a great option for maintaining a reporting server as you can have different indexes on your reporting database.

Personally if your two clusters are connected by a highspeed network (Gb/s) I would go for synchronous mirroring.

More details can be found here

ms-help://MS.VSCC.v80/MS.VSIPCC.v80/MS.SQLSVR.v9.en/udb9/html/b2eda634-0f8e-4703-801b-7ba895544ff5.htm in BOL under the heading "Configuring for high availability."

Log Shipping AND Database Mirroring ?

We are in the planning stages of setting up a redundant failover SQL
environment and were wondering if it's possible to integrate Database
Mirroring for some our databases (<10) and log shipping for the rest of our
databases.
All DB's are on a single instance of SQL
Thanks
Nick
Answered my own question.
http://msdn2.microsoft.com/en-us/library/ms187016.aspx
"N." <larosan@.yahoo.com> wrote in message
news:6Nznh.158$cK.82@.newsfe11.lga...
> We are in the planning stages of setting up a redundant failover SQL
> environment and were wondering if it's possible to integrate Database
> Mirroring for some our databases (<10) and log shipping for the rest of
> our databases.
> All DB's are on a single instance of SQL
> Thanks
> Nick
>
>
>

Log shipping and database backups how do they live together?

Hello,
We are planning to use log shipping as replication method for standby
database. My understanding that I have to make full database backup, restore
it on standby server (with NORECOVERY option) and then can just copy
transaction logs to standby server and apply them there periodically. I'm not
using enterprise edition so I'll use SimpleLogShipper from resource kit.
My question is what kind of backups I can make on primary server in order
for this to work? If I do transaction log backup my understanding transaction
log will be truncated and nothing will be shipped to standby server?
Second question if I may. What happens if I have tons of transactions which
modify small subsets of rows in primary database will shipping and restoring
differential backups will be a better method?
Log shipping works in the full and bulk logged recovery models. You need to
start off with a full backup, and then do transaction log dumps. Inactive
portions of the log are marked for reuse after the log is dumped, it is not
truncated. The file which you dump your transaction log is what you ship and
apply on the standby server.
If you have tones of logged activity (small subsets of rows) your
transaction log dumps will be larger and take longer to dump, copy and
restore on the standby server, but typically not appreciably longer.
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
"ChanKaiShi" <ChanKaiShi@.discussions.microsoft.com> wrote in message
news:B716A708-983D-4201-BA61-6AECEA33D6A3@.microsoft.com...
> Hello,
> We are planning to use log shipping as replication method for standby
> database. My understanding that I have to make full database backup,
> restore
> it on standby server (with NORECOVERY option) and then can just copy
> transaction logs to standby server and apply them there periodically. I'm
> not
> using enterprise edition so I'll use SimpleLogShipper from resource kit.
> My question is what kind of backups I can make on primary server in order
> for this to work? If I do transaction log backup my understanding
> transaction
> log will be truncated and nothing will be shipped to standby server?
> Second question if I may. What happens if I have tons of transactions
> which
> modify small subsets of rows in primary database will shipping and
> restoring
> differential backups will be a better method?
|||Can I make differential backups along with log dumps without screwing up log
shipping?
"Hilary Cotter" wrote:

> Log shipping works in the full and bulk logged recovery models. You need to
> start off with a full backup, and then do transaction log dumps. Inactive
> portions of the log are marked for reuse after the log is dumped, it is not
> truncated. The file which you dump your transaction log is what you ship and
> apply on the standby server.
> If you have tones of logged activity (small subsets of rows) your
> transaction log dumps will be larger and take longer to dump, copy and
> restore on the standby server, but typically not appreciably longer.
> --
> 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
>
> "ChanKaiShi" <ChanKaiShi@.discussions.microsoft.com> wrote in message
> news:B716A708-983D-4201-BA61-6AECEA33D6A3@.microsoft.com...
>
>
|||absolutely.
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
"ChanKaiShi" <ChanKaiShi@.discussions.microsoft.com> wrote in message
news:1B0EAFC0-0E1E-441A-81CE-E8ED232C0EE6@.microsoft.com...[vbcol=seagreen]
> Can I make differential backups along with log dumps without screwing up
> log
> shipping?
> "Hilary Cotter" wrote: