Re: Restoring Server which utilizes Log Shipping
From: Andrew J. Kelly (sqlmvpnooospam_at_shadhawk.com)
Date: 07/30/04
- Next message: michelle: "Re: Assertion Errors, temdb guest account, and other errors"
- Previous message: Wayne Snyder: "Re: DB Maintainance Plan"
- In reply to: Will Wirtz: "Restoring Server which utilizes Log Shipping"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 30 Jul 2004 14:02:26 -0400
The Log shipping wizard will only truncate the log after it has backed it up
so they are still fine for a restore. Why do you have 1000 log files?
You only need the ones from the last full backup. How often are you issuing
log backups? You might consider doing differentials during the day as well
if you backup the log frequently to save restore time. Then you only have
to restore logs from the last Diff.
-- Andrew J. Kelly SQL MVP "Will Wirtz" <WillCWirtz@Yahoo.com> wrote in message news:223f5e88.0407300924.10482dca@posting.google.com... > I have a large database that gets a full backup every night. We > utilize Log Shipping from this database to another database on a > reporting server. During the day Log Shipping creates log files on > the local server and truncates the transaction log for the database. > Everything works great. Lets say at 2:00pm the database crashes. I > restore the database from the previous nights full backup. Now I want > to restore the transaction log up to 2:00pm. The problem is that it's > empty because the log shipping has truncated it throughout the day. > What I do have is over 1000 small transaction files that were created > for log shipping. How can I apply all 1000 transaction files in the > shortest amount of time? I won't even think about doing each one > seperately. > > Will
- Next message: michelle: "Re: Assertion Errors, temdb guest account, and other errors"
- Previous message: Wayne Snyder: "Re: DB Maintainance Plan"
- In reply to: Will Wirtz: "Restoring Server which utilizes Log Shipping"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
