Comments
Sort by recent activity
Congratulations - that fixed it. Tested both LATEST_FULL and LATEST_ALL successfully on multiple servers, multiple databases, mixed number of FULL, DIFF and LOG backup files. All OK.
Thanks for your help and THANK YOU for a great set of products in the SQL Toolkit. Backup is great, while Compare and DataCompare are absolutely essential to me now. [image] / comments
Congratulations - that fixed it. Tested both LATEST_FULL and LATEST_ALL successfully on multiple servers, multiple databases, mixed number of FULL, DIFF and LOG backup files. All OK.
Thanks for y...
The Lucky 13 syndrome - alas, not the cause. When I first hit this problem I was using a different test database and there were just 4 skipped log backups out of 5 or 6 total. :?
Not so easy after all! [image] / comments
The Lucky 13 syndrome - alas, not the cause. When I first hit this problem I was using a different test database and there were just 4 skipped log backups out of 5 or 6 total. :?
Not so easy afte...
The backups were created using 6.4.0.56 (unpatched). Multiple backup threads, 256 bit encryption, compression level 4.
The restore attempt was done on the dev/test server using the patched 6.4.0.1001 files. When I initially tried this with the unpatched .56 release, the restore attempt would never start at all as per the >10 files bug. / comments
The backups were created using 6.4.0.56 (unpatched). Multiple backup threads, 256 bit encryption, compression level 4.
The restore attempt was done on the dev/test server using the patched 6.4.0.1...
How many log backup files are in your test set? I did not see any log restore attempts when I only had 3 log backups after the differential, but I did see the wrong-log-backup restore attempt when I had quite a few more. / comments
How many log backup files are in your test set? I did not see any log restore attempts when I only had 3 log backups after the differential, but I did see the wrong-log-backup restore attempt when...
I have run a profiler trace against 3 different restore processes. One in which Latest_All succeeds, one in which it fails on a "to new" log backup restore and then one using restore log against the full log set that the previous "latest_all" should have used.
In the Latest_all attempt that fails, the last action attempted by the SQBCoreService process is the first log restore (from a set of 3 virtual devices) after the database restores for, presummably, the preceeding full and differential backups, also from sets of virtual devices. / comments
I have run a profiler trace against 3 different restore processes. One in which Latest_All succeeds, one in which it fails on a "to new" log backup restore and then one using restore log against t...
I made a further discovery by chance when I tried the RESTORE_LATEST on a different database from my primary test candidate. This one had far more frequent log backups, so I had about 8 log backup files after the differential. The RESTORE_LATEST correctly identified the FULL and DIFF backups and restored those, but then it tried to start restoring the LOG from the 5th one in the sequence and failed due to mismatched LSN. So, it may be that it is not the restore component that is failing when "it doesn't restore the LOG backups" but rather the backup file search component. If I can get a chance, I will redo this test with a trace in the next couple of days. / comments
I made a further discovery by chance when I tried the RESTORE_LATEST on a different database from my primary test candidate. This one had far more frequent log backups, so I had about 8 log backup...
FYI - the error at the end of my last post was not from SQL Backup. It was from the USE [Database] statement at the end of my test script. SQL Backup's last result was "successful". I will re-do the script with profiler as requested when I get a chance, but I had to revert to release .0.56 on this server because the .1001 version was failing on larger log shipping restores (>8GB log change on 80GB DB after index rebuild) - it would start restoring, but would not complete, ever. Same with a full restore of the same DB.
I will "re-install" the 1001 files and try testing again, but I will have to set up a designated test server with a trial install to do so - no more "testing" on our production hot-spare log shipping system! / comments
FYI - the error at the end of my last post was not from SQL Backup. It was from the USE [Database] statement at the end of my test script. SQL Backup's last result was "successful". I will re-do...
I have been having a similar issue with the Latest_All switch on SQLBackup 6.4.0.56. In my case, the latest full backup would restore correctly but then the process would hang indefinitely, never starting the subsequent differential and/or log restores. I downloaded the patch listed in this thread and now I get a different issue. The full restore succeeds, but then any subsequent differential restores fail with the following errors:
SQL error 5069: ALTER DATABASE statement failed.
SQL error 5052: ALTER DATABASE is not permitted while a database is in the Restoring state.
I get this even if I use a full and differential backup generated from the same DB on the same server immediately prior to the restore attempt, as per the script below:
EXEC master..sqlbackup '-SQL "BACKUP DATABASE [FMP] To DISK = [E:\Temp\AMRSQLRepl_FMP_20100707_1536_Full.sqb] WITH CHECKSUM, COMPRESSION=4, KEYSIZE=128, PASSWORD=[pwd], VERIFY"'
GO
EXEC master..sqlbackup '-SQL "BACKUP DATABASE [FMP] To DISK = [E:\Temp\AMRSQLRepl_FMP_20100707_1536_Diff.sqb] WITH DIFFERENTIAL, CHECKSUM, COMPRESSION=4, KEYSIZE=128, PASSWORD=[pwd], VERIFY"'
GO
EXEC master..sqlbackup '-SQL "BACKUP LOG [FMP] To DISK = [E:\Temp\AMRSQLRepl_FMP_20100707_1537_Log.sqb] WITH CHECKSUM, COMPRESSION=4, KEYSIZE=128, PASSWORD=[pwd], VERIFY"'
GO
EXEC master..sqlbackup '-SQL "RESTORE DATABASE [FMP] FROM DISK = [E:\Temp\AMRSQLRepl_FMP*.sqb] LATEST_ALL WITH DISCONNECT_EXISTING, PASSWORD=[pwd], REPLACE"'
GO
All three backup stages completed normally, as did the full restore stage.
SQL server version is 9.0.4053. Script run under the "sa" account.
Suggestions?? / comments
I have been having a similar issue with the Latest_All switch on SQLBackup 6.4.0.56. In my case, the latest full backup would restore correctly but then the process would hang indefinitely, never ...