Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Restoring TLogs

Status
Not open for further replies.

R7Dave

Programmer
Oct 31, 2007
181
US
Hello

I am using SQL 2008 and have a project where a client is sending us transaction logs that we will restore on our server.

Some logs, I am able to apply, some get the ...

Code:
The log in this backup set terminates at LSN 8470802000000442300001, which is too early to apply to the database. A more recent log backup that includes LSN 8471611000001355300001 can be restored.

The BAK file is delivered to me on an external hard drive and the log files are transfered by FTP. The BAK file is > 15gb so what our project manager wanted was to use one BAK files and apply the transaction logs every day to keep the databases in sync.

From what I can tell, if the client backs up his database at his location, the transaction files from the FTP arent usable if the client does a full backup on the database and doesnt send me the BAK file

I can see the CheckPointLSN changes for some of the tlogs - I'm assuming the client backed up the database - I tested the scenario locally and can see the CheckpointLSN changes when you do a full backup.

Am I understanding this correctly? I need to let management know what the options are and need to make sure my facts are straight.

My questions are
- can I restore a database with one BAK file and transaction logs from a database that is being fully backed up periodically?
- Is a backup the only way the CheckpointLSN changes?

Any other suggestions appreciated

Thanks in advance
Dave

 
If the client is backing up the database, it will 'mess' up the log backups.

Here's a suggestion. Let the client know what is going on. By doing backups that are not sent on to you, they are causing the restores to fail since the log backups are out-of-sync. The solution is for the client to use the option 'WITH COPY_ONLY' on any backups that they are not forwarding to you. That will keep their backup from interfering with the 'sequence' of backups.

-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875
 
Thanks SQLBill - I followed your suggestion.

Thanks
Dave
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top