Re: Log shipping and database backups how do they live together?

Tech-Archive recommends: Fix windows errors by optimizing your registry

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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1B0EAFC0-0E1E-441A-81CE-E8ED232C0EE6@xxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B716A708-983D-4201-BA61-6AECEA33D6A3@xxxxxxxxxxxxxxxx
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?





.

Relevant Pages

  • Re: database log truncated, transaction log backup job failed
    ... Under Management/SQL Server Agent/Jobs you find the jobs for the ... you should be able to find the transaction log dump. ... Unfortunately, I recall now, that maintenance plans do a good job of ... First of all it's a good idea to backup the transaction ...
    (microsoft.public.sqlserver.tools)
  • RE: Log shipping
    ... the transaction log on the primary server, ... backed up the transaction log manually or if there is another job/maintence ... not backup the transaction log. ... Online Partner Support Specialist ...
    (microsoft.public.sqlserver.tools)
  • Re: Jetstress performance strange results...
    ... My opinion of what to put on the RAID 1 drives if you add them would be the ... Microsoft Exchange Support ... >server is in production and I've a lot of applications abvailable on it. ... Because each storage group has its own set of transaction log ...
    (microsoft.public.exchange.admin)
  • Re: Disaster recovery
    ... The simplest way is to perform transaction log backup's on a regular basis. ... Using the maintenance job you can schedule backups, I suggest every 30 or 15 ... Then copy these transaction log off to another server. ... backup file and copy it to another server. ...
    (microsoft.public.sqlserver.programming)
  • RE: Transaction log backups
    ... successfully created the plan, in the SQL Server Enterprise Manager ... Management folder for the monitor server, the Log Shipping Monitor appears. ... | first step seems to be to set up hourly transaction log ...
    (microsoft.public.sqlserver.security)