Backup error - Warning: System error 87 ANOTHER
mdgraves
Posts: 53
Backup reports ERROR, then successfully completes. My batch processing captures returned error, and alerts me. What is up with this error?
I have batch process that (1) determines dbases that are in valid state; (2) performs DBCC commands (3) dynamically builds backup syntax (4) captures errors and generates support cases for those... Below LOGS are of Error run and Good run...
Below is error LOG
Below is same dbase, night before...
I have batch process that (1) determines dbases that are in valid state; (2) performs DBCC commands (3) dynamically builds backup syntax (4) captures errors and generates support cases for those... Below LOGS are of Error run and Good run...
Below is error LOG
SQL Backup log file
10/24/2007 9:00:26 PM: Backing up GYCA015MP2 (full database) on GYMP2 instance to:
10/24/2007 9:00:26 PM: G:\MSSQL$GYMP2\BACKUP\FULL_GYMP2_GYCA015MP2_20071024_210025.sqb
10/24/2007 9:00:26 PM: BACKUP DATABASE [GYCA015MP2] TO DISK = '<AUTO>' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', ERASEFILES_ATSTART = 2, COMPRESSION = 1, THREADS = 1
10/24/2007 9:02:01 PM: Thread 0 error:
Error 620: Error writing to backup file(s).
10/24/2007 9:02:01 PM: Warning 210: Thread 0 warning:
Warning 210: Error writing to backup file: G:\MSSQL$GYMP2\BACKUP\FULL_GYMP2_GYCA015MP2_20071024_210027.sqb
Warning: System error 87 (The parameter is incorrect)
Processed 40888 pages for database 'GYCA015MP2', file 'TESTDB_Data' on file 1.
Processed 1 pages for database 'GYCA015MP2', file 'TESTDB_Log' on file 1.
BACKUP DATABASE successfully processed 40889 pages in 88.073 seconds (3.803 MB/sec).
Below is same dbase, night before...
SQL Backup log file
10/22/2007 9:00:34 PM: Backing up GYCA015MP2 (full database) on GYMP2 instance to:
10/22/2007 9:00:34 PM: G:\MSSQL$GYMP2\BACKUP\FULL_GYMP2_GYCA015MP2_20071022_210034.sqb
10/22/2007 9:00:34 PM: BACKUP DATABASE [GYCA015MP2] TO DISK = '<AUTO>' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', ERASEFILES_ATSTART = 2, COMPRESSION = 1, THREADS = 1
10/22/2007 9:00:39 PM: Deleting old backup file: G:\MSSQL$GYMP2\BACKUP\FULL_GYMP2_GYCA015MP2_20071019_210026.sqb
10/22/2007 9:02:03 PM: Database size : 409.250 MB
10/22/2007 9:02:03 PM: Compressed data size: 91.893 MB
10/22/2007 9:02:03 PM: Compression rate : 77.55%
Processed 40576 pages for database 'GYCA015MP2', file 'TESTDB_Data' on file 1.
Processed 1 pages for database 'GYCA015MP2', file 'TESTDB_Log' on file 1.
BACKUP DATABASE successfully processed 40577 pages in 75.386 seconds (4.409 MB/sec).
10/22/2007 9:02:03 PM: SQL Backup process ended.
Comments
There was not a complete set of error handling information in previous versions so an unknown message was reported as "the parameter is incorrect".
Can you update to the latest version to see the correct windows error.
Red Gate Software Ltd
SQL Backup log file 5.2.0.2825
7/12/2007 10:37:49 AM: Backing up WTSUI (full database) to:
7/12/2007 10:37:49 AM: \Microsoft SQL Server\Backup\FULL_WTSUI.sqb
7/12/2007 10:37:49 AM: BACKUP DATABASE [WTSUI] TO DISK = 'D:\Microsoft SQL Server\Backup\<AUTO>.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', INIT, VERIFY, COMPRESSION = 0
7/12/2007 10:37:53 AM: Thread 0 error:
Error 620: Error writing to backup file(s).
7/12/2007 10:37:53 AM: Warning 210: Thread 0 warning:
Warning 210: Error writing to backup file: \Microsoft SQL Server\Backup\FULL_WTSUI.sqb
Warning: System error 87 (The parameter is incorrect)
Processed 6056 pages for database 'WTSUI', file 'WTSUI_Data' on file 1.
Processed 1 pages for database 'WTSUI', file 'WTSUI_Log' on file 1.
BACKUP DATABASE successfully processed 6057 pages in 3.403 seconds (14.578 MB/sec).
I hate problems like this because you can't be sure when they are going to re-appear.
Thank you
Oleg
Can you ensure that you are using the latest version of the software on the server, and if you still obtain this error message contact support directly.
We will then get you to email over some log files, or increase the logging to find out what the issue is.
Dan
Red Gate Software Ltd
You should at least upgrade to version 5.3, as this bug was fixed then.
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8