Backup system databases may have not been updated

st8floorsup

SQL Backup log file 6.3.0.48

-SQL "BACKUP DATABASE [dbname] TO DISK = '\\backupserver\SQL_BACKUPS\DEV\servername\dbname-20091214_012639_full.sqb' WITH NAME = 'dbname Full backup', DESCRIPTION = 'SQLBackup Full Backup', INIT, MAILTO_ONERROR = 'sqladmin@medassets.com', ERASEFILES_ATSTART = 2, COMPRESSION = 1 "

---

ERRORS AND WARNINGS

---

12/14/2009 1:26:39 AM: Backing up dbname (full database) to:
12/14/2009 1:26:39 AM: \\backupserver\SQL_BACKUPS\DEV\servername\dbname-20091214_012639_full.sqb

12/14/2009 1:28:40 AM: BACKUP DATABASE [dbname] TO VIRTUAL_DEVICE = 'SQLBACKUP_3BE2CBE3-4E23-435D-8FC7-1314D6BE4BE3' WITH BUFFERCOUNT = 6, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576, NAME = N'dbname Full backup', DESCRIPTION = N'SQLBackup Full Backup', FORMAT

12/14/2009 1:47:55 AM: Warning 202: Thread 0 warning:
12/14/2009 1:33:44 AM: Warning 480: Failed to create output folder: \\backupserver\SQL_BACKUPS\DEV\servername\.
12/14/2009 1:39:18 AM: Warning 480: Failed to create output folder: \\backupserver\SQL_BACKUPS\DEV\servername\.
12/14/2009 1:47:55 AM:
12/14/2009 1:48:56 AM: Database size : 1.232 GB

12/14/2009 1:48:56 AM: Processed 154584 pages for database 'dbname', file 'dbname3' on file 1.
12/14/2009 1:48:56 AM: Processed 1 pages for database 'dbname', file 'dbname3_log' on file 1.
12/14/2009 1:48:56 AM: BACKUP DATABASE successfully processed 154585 pages in 186.045 seconds (6.806 MB/sec).

If I try to restore from the console it tells me the selected backup cannot be restored. SQL Backup has detected that more recent backups have used the same backup file name(s).
The physical file exist. I can restore the backup just fine from SQL Server Management Studio. It seems the backup succeeded but didn't update system tables.

EXECUTE master..sqlbackup
'-SQL "RESTORE DATABASE [dbname]
FROM DISK = ''\\backupserver\SQL_BACKUPS\DEV\servername\dbname-20091214_012639_full.sqb''
WITH RECOVERY,
MOVE ''DW_UPMC_LCC3'' TO ''F:\MSSQL.1\MSSQL\Data\dbname.mdf'',
MOVE ''DW_UPMC_LCC3_log'' TO ''F:\MSSQL.1\MSSQL\Data\dbname_log.ldf'', ORPHAN_CHECK"'

Is this a known issue? In the console the backup record says "successful" but files= 0. Compressed size is 0 too. The messages are misleading.

peter.peart

Hi there,

I have knows SQL Backup not update a system table if it cannot gain access, i.e. the table is corrupt, doesn't exist (has happened!) or there is another process blocking the update, however the log file normally details this.

Is this the full log file? You can obtain the full log by right clicking on the job and selecting "Show Log".

Also, I am guessing that this is scheduled job? Can you send me the specific syntax that you have for this job?

Many thanks!

st8floorsup

That is all of the log. The sql job is involved but the call to the backup is at the top of the log. Give me your email and I can mail it to you.

peter.peart

Hi,

If you would like to send that across to peter.peart(at)redgate.com then I can attach it to the support call we have raised for you and go from there.

Many thanks!

Pete

Brian Donahue

Hi Kenny,

I'm looking at the SQL Backup log while Peter is away, but I don't see any errors that would cause the backup history to be updated. FYI, backup history is managed by SQL Server and is first written to the MSDB system database, then it is written to SQL Backup's SQL CE server-side data store, and each SQL Backup console replicates the server-side store for each server registered in SQL Backup's console. This is going to make it complicated to find the point of failure.

How long after the backup are you trying to restore it? Maybe the history just needs more time to replicate.

Also, the client-side data could be corrupt. You could try deleting all of it because it will just be replenished the next time you connect to the server.

The client-side files are in %userprofile%\local settings\application data\sql backup\server data.