Backup stratagy Overview

9 Jan 2009 11:16 AM

David Hills

Good Morning

can some one point me in the direction of a good simple overview of back
stratagy
for sequal server. I'm running axapta, I run a full online backup
everynight, compress it, copy it to another server, reconnect just the mdb
file.

This works fine, but I would like to bring over the transcation file every x
minutes and apply it.

How and when does the transaction log get truncated, is it automatically
done for a full backup. we are actually doing two full backups of the data
base, will this work
or will I have incomplete transcation logs? because the second backup is not
copies across and restored because of day time band width restrictions?

Thnaks

David Hills

--
Thanks

David Hills

9 Jan 2009 4:33 PM

Russell Fields

David,

First, I would point you to the SQL Books Online, the documentation which is
pretty thorough:
http://technet.microsoft.com/en-us/library/ms187048.aspx -- Overall topic
http://technet.microsoft.com/en-us/library/ms191239(SQL.90).aspx --
Strategies

From your comments, you might find the Log Shipping topic interesting as
well, though maybe it is more than you want to do.
http://technet.microsoft.com/en-us/library/ms187103(SQL.90).aspx

RLF

Show quoteHide quote

"David Hills" <DavidHi***@discussions.microsoft.com> wrote in message
news:45136485-F371-4C7C-BD82-2EB304E001AD@microsoft.com...
> Good Morning
>
> can some one point me in the direction of a good simple overview of back
> stratagy
> for sequal server. I'm running axapta, I run a full online backup
> everynight, compress it, copy it to another server, reconnect just the mdb
> file.
>
> This works fine, but I would like to bring over the transcation file every
> x
> minutes and apply it.
>
> How and when does the transaction log get truncated, is it automatically
> done for a full backup. we are actually doing two full backups of the data
> base, will this work
> or will I have incomplete transcation logs? because the second backup is
> not
> copies across and restored because of day time band width restrictions?
>
> Thnaks
>
>
> David Hills
>
>
>
>
> --
> Thanks
>
>
>
> David Hills

9 Jan 2009 11:06 PM

Erland Sommarskog

David Hills (DavidHi***@discussions.microsoft.com) writes:

> How and when does the transaction log get truncated, is it automatically
> done for a full backup. we are actually doing two full backups of the
> data base, will this work or will I have incomplete transcation logs?
> because the second backup is not copies across and restored because of
> day time band width restrictions?

The transaction log is truncated when you back up the log. When you back
up the database, nothing happens to the log. (Well, records of the backup
is written to it.)

If you are in simple recovery, the log gets truncated every now in then.
You need to use the full recovery model to be able to ship your logs.

--
Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx