Any insight? My backups are pretty much useless at this point.
RE: Restores failing with exit code 790
↧
↧
RE: Restores failing with exit code 790
Here's the error in detail.
Dev-Thor: Restore - Failed
==========================
Restoring full backup - Successful
----------------------------------
This operation completed successfully.
Restoring RIP_Onyx (database) from:
\\redgate1\SQLBackups\thor\Onyx\FULL_Onyx_20130113_025441.sqb
Processed 4387672 pages for database 'RIP_Onyx', file 'Vanilla500054_Data' on file 1.
Processed 9 pages for database 'RIP_Onyx', file 'Vanilla500054_Log' on file 1.
RESTORE DATABASE successfully processed 4387681 pages in 470.348 seconds (72.879 MB/sec).
SQL Backup process ended.
Restoring differential backup - Failed
--------------------------------------
This operation failed with errors.
Restoring RIP_Onyx (database) from:
\\redgate1\SQLBackups\thor\Onyx\DIFF_Onyx_20130116_023012.sqb
Thread 0 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
SQL error 3013: SQL error 3013: RESTORE DATABASE is terminating abnormally.
SQL error 3136: SQL error 3136: This differential backup cannot be restored because the database has not been restored to the correct earlier state.
SQL Backup exit code: 790
SQL error code: 3136
Updating SQL Server information - Pending
-----------------------------------------
Operation pending.
Dev-Thor: Restore - Failed
==========================
Restoring full backup - Successful
----------------------------------
This operation completed successfully.
Restoring RIP_Onyx (database) from:
\\redgate1\SQLBackups\thor\Onyx\FULL_Onyx_20130113_025441.sqb
Processed 4387672 pages for database 'RIP_Onyx', file 'Vanilla500054_Data' on file 1.
Processed 9 pages for database 'RIP_Onyx', file 'Vanilla500054_Log' on file 1.
RESTORE DATABASE successfully processed 4387681 pages in 470.348 seconds (72.879 MB/sec).
SQL Backup process ended.
Restoring differential backup - Failed
--------------------------------------
This operation failed with errors.
Restoring RIP_Onyx (database) from:
\\redgate1\SQLBackups\thor\Onyx\DIFF_Onyx_20130116_023012.sqb
Thread 0 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
SQL error 3013: SQL error 3013: RESTORE DATABASE is terminating abnormally.
SQL error 3136: SQL error 3136: This differential backup cannot be restored because the database has not been restored to the correct earlier state.
SQL Backup exit code: 790
SQL error code: 3136
Updating SQL Server information - Pending
-----------------------------------------
Operation pending.
↧
RE: Restores failing with exit code 790
Could you please run this query on the instance where the backup was taken?
This query should tell you the full backup set that the differential backup requires.
| Code: |
| SELECT d.physical_device_name FROM msdb..backupset a INNER JOIN msdb..backupset b ON a.database_backup_lsn = b.checkpoint_lsn INNER JOIN msdb..backupmediafamily c ON a.media_set_id = c.media_set_id INNER JOIN msdb..backupmediafamily d ON b.media_set_id = d.media_set_id WHERE c.physical_device_name LIKE '%DIFF_Onyx_20130116_023012.sqb' |
This query should tell you the full backup set that the differential backup requires.
↧
The meaning of the codes on Failed BCK
I got this msg during the backup operations! - someone let me know why it is happening and where I'm doing wrong while my user that is connected to he SQL Server is in sysAdmin role and it is windows user in the Administrators Group. Normal BCK with SSMS are performing with no problems. I have permission to Read'n'Write everything in my Server.
Any way to avoid this failed operation!?
MyServer : Backup - Failed
=====================
Performing full backups - Failed
--------------------------------
This operation failed with errors.
Backing up MyDB (full database) to:
MyPath:\FULL_(local)_MyDB_20130117_212623.sqb
Error 880: BACKUP DATABASE permission denied in database: (MyDB)
SQL error 916: The server principal "NT AUTHORITY\SYSTEM" is not able to access the database "MyDB" under the current security context.
SQL Backup exit code: 880
SQL error code: 916
Updating SQL Server information - Successful
--------------------------------------------
This operation completed successfully.
Any way to avoid this failed operation!?
MyServer : Backup - Failed
=====================
Performing full backups - Failed
--------------------------------
This operation failed with errors.
Backing up MyDB (full database) to:
MyPath:\FULL_(local)_MyDB_20130117_212623.sqb
Error 880: BACKUP DATABASE permission denied in database: (MyDB)
SQL error 916: The server principal "NT AUTHORITY\SYSTEM" is not able to access the database "MyDB" under the current security context.
SQL Backup exit code: 880
SQL error code: 916
Updating SQL Server information - Successful
--------------------------------------------
This operation completed successfully.
↧
RE: The meaning of the codes on Failed BCK
Could you please check if the SQL Backup Agent service startup account has the SQL Server sysadmin fixed server role assigned to it?
↧
↧
Full/Differential Backups extremely slow
Hi,
Our Full and Differential backups have become extremely slow.
Backing up over 1400 databases takes over 12 hours or longer.
Using SQL Backup 7.2.1.4.
Does SQL Backup start choking with a large number of databases in an Instance?
Thanks.
Tim
Our Full and Differential backups have become extremely slow.
Backing up over 1400 databases takes over 12 hours or longer.
Using SQL Backup 7.2.1.4.
Does SQL Backup start choking with a large number of databases in an Instance?
Thanks.
Tim
↧
RE: Full/Differential Backups extremely slow
Could you please post the entire backup command you are using?
Thanks.
Thanks.
↧
RE: Full/Differential Backups extremely slow
Here's the backup command:
EXECUTE master..sqlbackup '-SQL "BACKUP DATABASES EXCLUDE [tempdb] TO DISK = ''\\prod.ent\proddfs\DBBackupFolders\backup_sql_db07\Backup_SQL\<AUTO>.sqb'' WITH ERASEFILES = 3b, MAILTO_ONERRORONLY = ''sqlalerts@bbbbb.com'', CHECKSUM, DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, COMPRESSION = 4"'
Thanks for your help.
Tim
EXECUTE master..sqlbackup '-SQL "BACKUP DATABASES EXCLUDE [tempdb] TO DISK = ''\\prod.ent\proddfs\DBBackupFolders\backup_sql_db07\Backup_SQL\<AUTO>.sqb'' WITH ERASEFILES = 3b, MAILTO_ONERRORONLY = ''sqlalerts@bbbbb.com'', CHECKSUM, DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, COMPRESSION = 4"'
Thanks for your help.
Tim
↧
RE: Full/Differential Backups extremely slow
The bottleneck is probably the ERASEFILES option. You could check if that is the case by omitting this option once and see if the backup completes faster.
If it is indeed the ERASEFILES option that's causing the slowdown, it's because:
1. the backups for all 1400 databases are stored in the same folder, on a network share. As there are 3 backup sets of each database at any one time, that's 4200 files that SQL Backup needs to check every time it backs up a database, to determine which backup file to delete. It needs to read the header of each file to match the database and backup type.
2. the files are stored on a network share. That makes reading the header of 4200 files, 1400 times (once for each database), even slower.
What you could try doing is to separate each database's backup file into their own folder using the <DATABASE> tag e.g.
In this way, SQL Backup only needs to read the header of 4 files each time, to determine which backup sets to delete.
If it is indeed the ERASEFILES option that's causing the slowdown, it's because:
1. the backups for all 1400 databases are stored in the same folder, on a network share. As there are 3 backup sets of each database at any one time, that's 4200 files that SQL Backup needs to check every time it backs up a database, to determine which backup file to delete. It needs to read the header of each file to match the database and backup type.
2. the files are stored on a network share. That makes reading the header of 4200 files, 1400 times (once for each database), even slower.
What you could try doing is to separate each database's backup file into their own folder using the <DATABASE> tag e.g.
| Code: |
| EXEC master..sqlbackup '-sql "BACKUP ... TO DISK = [\\prod.ent\proddfs\DBBackupFolders\backup_sql_db07\Backup_SQL\<DATABASE>\<AUTO>.sqb] ... |
In this way, SQL Backup only needs to read the header of 4 files each time, to determine which backup sets to delete.
↧
↧
RE: Full/Differential Backups extremely slow
Thanks Peter.
Good idea. I'll let you know how it goes.
Thanks.
Tim
Good idea. I'll let you know how it goes.
Thanks.
Tim
↧
RE: Restores failing with exit code 790
Ok, I had a chance to try again. The restore is only 2 files, a full backup from sunday and last nights diff. Here's the error and the results of the query you wanted me to run with the current diff.
Dev-Thor: Restore - Failed
==========================
Restoring full backup - Successful
----------------------------------
This operation completed successfully.
Restoring RIP_Onyx (database) from:
\\redgate1\SQLBackups\thor\Onyx\FULL_Onyx_20130120_025056.sqb
Processed 4396432 pages for database 'RIP_Onyx', file 'Vanilla500054_Data' on file 1.
Processed 17 pages for database 'RIP_Onyx', file 'Vanilla500054_Log' on file 1.
RESTORE DATABASE successfully processed 4396449 pages in 469.187 seconds (73.205 MB/sec).
SQL Backup process ended.
Restoring differential backup - Failed
--------------------------------------
This operation failed with errors.
Restoring RIP_Onyx (database) from:
\\redgate1\SQLBackups\thor\Onyx\DIFF_Onyx_20130123_023009.sqb
Thread 0 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
SQL error 3013: SQL error 3013: RESTORE DATABASE is terminating abnormally.
SQL error 3136: SQL error 3136: This differential backup cannot be restored because the database has not been restored to the correct earlier state.
SQL Backup exit code: 790
SQL error code: 3136
Updating SQL Server information - Pending
-----------------------------------------
Operation pending.
SELECT d.physical_device_name
FROM msdb..backupset a
INNER JOIN msdb..backupset b ON a.database_backup_lsn = b.checkpoint_lsn
INNER JOIN msdb..backupmediafamily c ON a.media_set_id = c.media_set_id
INNER JOIN msdb..backupmediafamily d ON b.media_set_id = d.media_set_id
WHERE c.physical_device_name LIKE '%DIFF_Onyx_20130123_023009.sqb'
Results
physical_device_name
{E2E5B7E6-6FD4-415D-8989-36FAD01A243E}14
d:\temp\Onyx\LOG_Onyx_20130122_190001.sqb
NUL
d:\temp\Onyx\LOG_Onyx_20130122_191501.sqb
d:\temp\Onyx\LOG_Onyx_20130122_193001.sqb
d:\temp\Onyx\LOG_Onyx_20130122_194501.sqb
d:\temp\Onyx\LOG_Onyx_20130122_200001.sqb
d:\temp\Onyx\LOG_Onyx_20130122_201501.sqb
d:\temp\Onyx\LOG_Onyx_20130122_203001.sqb
d:\temp\Onyx\LOG_Onyx_20130122_204501.sqb
d:\temp\Onyx\LOG_Onyx_20130122_210001.sqb
d:\temp\Onyx\LOG_Onyx_20130122_211501.sqb
d:\temp\Onyx\LOG_Onyx_20130122_213000.sqb
d:\temp\Onyx\LOG_Onyx_20130122_214501.sqb
d:\temp\Onyx\LOG_Onyx_20130122_220001.sqb
d:\temp\Onyx\LOG_Onyx_20130122_221501.sqb
d:\temp\Onyx\LOG_Onyx_20130122_223000.sqb
d:\temp\Onyx\LOG_Onyx_20130122_224501.sqb
d:\temp\Onyx\LOG_Onyx_20130122_230001.sqb
d:\temp\Onyx\LOG_Onyx_20130122_231501.sqb
d:\temp\Onyx\LOG_Onyx_20130122_233001.sqb
d:\temp\Onyx\LOG_Onyx_20130122_234500.sqb
Dev-Thor: Restore - Failed
==========================
Restoring full backup - Successful
----------------------------------
This operation completed successfully.
Restoring RIP_Onyx (database) from:
\\redgate1\SQLBackups\thor\Onyx\FULL_Onyx_20130120_025056.sqb
Processed 4396432 pages for database 'RIP_Onyx', file 'Vanilla500054_Data' on file 1.
Processed 17 pages for database 'RIP_Onyx', file 'Vanilla500054_Log' on file 1.
RESTORE DATABASE successfully processed 4396449 pages in 469.187 seconds (73.205 MB/sec).
SQL Backup process ended.
Restoring differential backup - Failed
--------------------------------------
This operation failed with errors.
Restoring RIP_Onyx (database) from:
\\redgate1\SQLBackups\thor\Onyx\DIFF_Onyx_20130123_023009.sqb
Thread 0 error:
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
SQL error 3013: SQL error 3013: RESTORE DATABASE is terminating abnormally.
SQL error 3136: SQL error 3136: This differential backup cannot be restored because the database has not been restored to the correct earlier state.
SQL Backup exit code: 790
SQL error code: 3136
Updating SQL Server information - Pending
-----------------------------------------
Operation pending.
SELECT d.physical_device_name
FROM msdb..backupset a
INNER JOIN msdb..backupset b ON a.database_backup_lsn = b.checkpoint_lsn
INNER JOIN msdb..backupmediafamily c ON a.media_set_id = c.media_set_id
INNER JOIN msdb..backupmediafamily d ON b.media_set_id = d.media_set_id
WHERE c.physical_device_name LIKE '%DIFF_Onyx_20130123_023009.sqb'
Results
physical_device_name
{E2E5B7E6-6FD4-415D-8989-36FAD01A243E}14
d:\temp\Onyx\LOG_Onyx_20130122_190001.sqb
NUL
d:\temp\Onyx\LOG_Onyx_20130122_191501.sqb
d:\temp\Onyx\LOG_Onyx_20130122_193001.sqb
d:\temp\Onyx\LOG_Onyx_20130122_194501.sqb
d:\temp\Onyx\LOG_Onyx_20130122_200001.sqb
d:\temp\Onyx\LOG_Onyx_20130122_201501.sqb
d:\temp\Onyx\LOG_Onyx_20130122_203001.sqb
d:\temp\Onyx\LOG_Onyx_20130122_204501.sqb
d:\temp\Onyx\LOG_Onyx_20130122_210001.sqb
d:\temp\Onyx\LOG_Onyx_20130122_211501.sqb
d:\temp\Onyx\LOG_Onyx_20130122_213000.sqb
d:\temp\Onyx\LOG_Onyx_20130122_214501.sqb
d:\temp\Onyx\LOG_Onyx_20130122_220001.sqb
d:\temp\Onyx\LOG_Onyx_20130122_221501.sqb
d:\temp\Onyx\LOG_Onyx_20130122_223000.sqb
d:\temp\Onyx\LOG_Onyx_20130122_224501.sqb
d:\temp\Onyx\LOG_Onyx_20130122_230001.sqb
d:\temp\Onyx\LOG_Onyx_20130122_231501.sqb
d:\temp\Onyx\LOG_Onyx_20130122_233001.sqb
d:\temp\Onyx\LOG_Onyx_20130122_234500.sqb
↧
RE: Restores failing with exit code 790
You may be interested in this. Here's the problem. http://support.microsoft.com/default.aspx?scid=kb;EN-US;937683
Veeam, our virtual backup software has been writing to the msdb database after a filesystem backup. I just did a full backup and then a diff and the restore worked.
Veeam, our virtual backup software has been writing to the msdb database after a filesystem backup. I just did a full backup and then a diff and the restore worked.
↧
RE: Full/Differential Backups extremely slow
Hi Peter,
Worked great. Thanks.
Tim
Worked great. Thanks.
Tim
↧
↧
RE: Restores failing with exit code 790
Thanks for the update. I was wondering about the '{E2E5B7E6-6FD4-415D-8989-36FAD01A243E}14' device name.
↧
RE: Restores failing with exit code 790
Seems that veeam is causing all kinds of problems on our servers.
↧
RE: Click on server name, green circle spins forever
This is an old thread, but I have the same kind of situation with one of our servers that has 86 databases on it. If I close and reopen SQL Backup UI a couple of times it eventually displays the activity history, but it takes a while. It seems like maybe it should display the top 100 records quickly, then try to load the rest in the background or something.
Any news on this?
Reinis
Any news on this?
Reinis
↧
RE: Click on server name, green circle spins forever
It's not really about the amount of backup history as it is the process of creating "timeline" objects.
The best advice I give customers is to disable the timeline - that will leave you with the backup history, but the graphical display showing the times backups are predicted to run will not be populated.
You can create the registry key (the final bit should be a DWORD)
HKLM\Software\Wow6432Node\Red Gate\SQLBackup\Client\DisableTimelineItemRequests
and setting the value to "1"
The best advice I give customers is to disable the timeline - that will leave you with the backup history, but the graphical display showing the times backups are predicted to run will not be populated.
You can create the registry key (the final bit should be a DWORD)
HKLM\Software\Wow6432Node\Red Gate\SQLBackup\Client\DisableTimelineItemRequests
and setting the value to "1"
↧
↧
RE: Click on server name, green circle spins forever
Thanks for the prompt response. I will try that when I get a chance.
I have to say that does seem a slightly heavy-handed approach. That basically disables part of the selling points of SQL Backup. To check if everything succeeded, I have to click on each server seperately and look for any failures - which requires some scrolling for the servers I have 15min transaction log backups on (unless there is another way to look at all the backup history at once that I don't know of). Also, the first page of the timeline actually displays quickly (sometimes) but the activity doesn't load. Is the whole timeline attempting to load or something? The other servers only load a day or two initially as well but their activity history shows up quickly.
Thanks,
Reinis
I have to say that does seem a slightly heavy-handed approach. That basically disables part of the selling points of SQL Backup. To check if everything succeeded, I have to click on each server seperately and look for any failures - which requires some scrolling for the servers I have 15min transaction log backups on (unless there is another way to look at all the backup history at once that I don't know of). Also, the first page of the timeline actually displays quickly (sometimes) but the activity doesn't load. Is the whole timeline attempting to load or something? The other servers only load a day or two initially as well but their activity history shows up quickly.
Thanks,
Reinis
↧
RE: Network Copy to Multiple locations
hi this is Hedward Marsh, i am a beginner to SQL i want to know more information about a SQL i have searched in google i found this website this website contains lots of information about SQL controls, backups etc this site contains very useful information thanks for posting
↧
DB Restore Status Remains
Using SQL Backup 7.2.1.4
Restored database from a backup file from another with "Overwrite existing database" option and "Kill any existing connections to the database" checked.
Anyway, it's a big database, but the restore has been running for 2 days now. And the status is still in Restoring ...
When I look at Activity History tab below, it says Successful; and when I double click the history, it says "There are no errors or warnings associated with this restore".
This is the final line of the Activity Log
1/28/2013 9:21:42 AM: SQL Backup process ended.
But the status is still in Restoring... and I cannot connect to it using SSMS2008. I am getting the following error
Msg 927, Level 14, State 2, Line 5
Database 'abc' cannot be opened. It is in the middle of a restore.
Edit: Have since restarted SQL Backup Agent service on the server. Didn't help ...
How do I fix this issue?
Restored database from a backup file from another with "Overwrite existing database" option and "Kill any existing connections to the database" checked.
Anyway, it's a big database, but the restore has been running for 2 days now. And the status is still in Restoring ...
When I look at Activity History tab below, it says Successful; and when I double click the history, it says "There are no errors or warnings associated with this restore".
This is the final line of the Activity Log
1/28/2013 9:21:42 AM: SQL Backup process ended.
But the status is still in Restoring... and I cannot connect to it using SSMS2008. I am getting the following error
Msg 927, Level 14, State 2, Line 5
Database 'abc' cannot be opened. It is in the middle of a restore.
Edit: Have since restarted SQL Backup Agent service on the server. Didn't help ...
How do I fix this issue?
↧
More Pages to Explore .....
