September 24, 2007 at 5:25 pm
| BackupName | FirstLSN | LastLSN | DatabaseBackupLSN | BackupStartDate | BackupFinishDate | BackupTypeDescription |
| ECOMLIVE backup | 36717000001665700002 | 36717000001771100001 | 36717000001676500066 | 2007-09-19 21:00:03.000 | 2007-09-19 21:21:08.000 | Database |
| ECOMLIVE log backup | 36717000001771600001 | 36717000001771600001 | 36717000001676500066 | 2007-09-19 21:21:09.000 | 2007-09-19 21:21:17.000 | Transaction Log |
Full backup occurs nightly starting at 9:00PM finishes aroung 9:20-ish.
Two Step Job:
Step 1: BACKUP DATABASE [ECOMLIVE] TO [ECOMLIVE Data] WITH INIT , NOUNLOAD , NAME = N'ECOMLIVE backup', STATS = 10, FORMAT
Step 2: BACKUP LOG [ECOMLIVE] TO [ECOMLIVE Log] WITH INIT , NOUNLOAD , NAME = N'ECOMLIVE log backup', STATS = 10, FORMAT
Transaction Log Backups occurs every five minutes continuously 'round the clock.
One Step Job:
Step 1: BACKUP LOG [ECOMLIVE] TO [ECOMLIVE Log] WITH NOINIT , NOUNLOAD , NAME = N'ECOMLIVE Log backup', NOSKIP , STATS = 10, NOFORMAT
PROBLEM: Did the Transaction Log Backup Job atempt to write to the transaction log backup device while the Full Backup Job was performing a full backup at 9:20PM thus making my transaction log un-usable because it has different LSN's?
Why don't my Last LSn from my backup and my First LSN from the log backup match up thus giving me the opportunity to use the backup and then use the transaction log?
September 25, 2007 at 1:50 am
If I read it correctly your making a tranasaction log backup every 5 minutes to the same backup device.
BACKUP LOG [ECOMLIVE] TO [ECOMLIVE Log] WITH INIT ,....
The problem is the that WITH INIT overwrites all the old backups files when making a new one. So either replace it witj NO INIT or even better use a separate file for each backup.
Hope this helps
Markus
[font="Verdana"]Markus Bohse[/font]
September 25, 2007 at 8:23 am
You should use separated log files so that you can recover the "chain". Some people do like a single TLOG backup file but my personal experience indicate that is easier to manage them using separated files.
* Noel
September 25, 2007 at 9:03 am
third vote to concur with what's above. Search for a script on this site to do log backups. There are lots of them and most create a separate file for each log backup.
September 26, 2007 at 12:40 pm
There are two jobs:
One job has two steps: backup database with init and backup log with init runs once a day.
The other job has one step: backup log with no init so that it accumulates every five minutes.
Again, why wasn't I able to restore the full backup plus the transaction logs?
The full backup completed at 21:21:08 seconds and the first transaction log started at 21:21:09 seconds yet the LastLSN of the backup and FirstLSN of the transaction log ARE NOT EQUAL?
Why not?
The responses above are not accurate as I am only initializing the log once a day right after the full backup occurs.
The only possible speculation I can come up with is that during the execution of the first job, the full backup the second job fired off, but why does the LIST HEADERONLY info say the first job completed 8 seconds after the minute and the transaction log started 9 seconds after the minute. I should have been able to restore the full, which I did successfully, leave the database in NORECOVERY mode which I did, and apply the transaction log, which failed saying LSN's weren't correct.....
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply