How can we help you today? How can we help you today?
David Smith
Activity overview Badges (0) Posts (3) Comments (7)

Comments

Sort by recent activity
Same thing happened with one of our backups this morning.... At least the MAILTO_ONERROR worked and we got notified. But the GUI showing all is well isn't so great. David SQL Backup log file 27/09/2007 1:00:00 a.m.: Backing up db1 (full database) to: 27/09/2007 1:00:00 a.m.: F:\sqlbackup\db1\db1_db_20070927010000.sqb 27/09/2007 1:00:00 a.m.: \\svr1\shipping\nzsql2005-1\db1\db1_db_20070927010000.sqb 27/09/2007 1:00:00 a.m.: BACKUP DATABASE [db1] TO DISK = 'F:\sqlbackup\db1\db1_db_<DATETIME yyyymmddhhnnss>.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', INIT, MIRRORFILE = '\\svr1\shipping\nzsql2005-1\db1\db1_db_<DATETIME yyyymmddhhnnss>.sqb', VERIFY, ERASEFILES = 2, MAILTO_ONERROR = 'servers@site.com', COPYTO = '\\svr2\nzsql2005-1\db1\', FILEOPTIONS = 5, COMPRESSION = 2, THREADCOUNT = 2 27/09/2007 1:55:43 a.m.: Database size : 151.517 GB 27/09/2007 1:55:43 a.m.: Compressed data size: 52.078 GB 27/09/2007 1:55:43 a.m.: Compression rate : 65.63% Processed 9811848 pages for database 'db1', file 'db1_Data' on file 1. Processed 6655760 pages for database 'db1', file 'db1_data2' on file 1. Processed 110168 pages for database 'db1', file 'db1_clientdata' on file 1. Processed 640920 pages for database 'db1', file 'db1_mailheader' on file 1. Processed 13645 pages for database 'db1', file 'db1_Log' on file 1. BACKUP DATABASE successfully processed 17232341 pages in 3340.114 seconds (42.264 MB/sec). 27/09/2007 1:56:14 a.m.: 27/09/2007 1:56:14 a.m.: Validating files: 27/09/2007 1:56:14 a.m.: F:\sqlbackup\db1\db1_db_20070927010000.sqb 27/09/2007 1:56:14 a.m.: 27/09/2007 1:56:14 a.m.: RESTORE VERIFYONLY FROM DISK = 'F:\sqlbackup\db1\db1_db_20070927010000.sqb' 27/09/2007 1:58:35 a.m.: Thread 0 error: Device index out of range: 238 27/09/2007 1:58:35 a.m.: Thread 1 error: Device index out of range: 238 SQL error 3013: SQL error 3013: VERIFY DATABASE is terminating abnormally. SQL error 3203: SQL error 3203: Read on "SQLBACKUP_5D7C1B82-8F55-493D-9E16-BE14DBCA9B17" failed: 995(error not found) 27/09/2007 1:58:36 a.m.: Validation of all backup files failed. 27/09/2007 1:58:36 a.m.: Mail sent successfully to: servers@site.com / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Random verify failures but the GUI is reporting success
Same thing happened with one of our backups this morning.... At least the MAILTO_ONERROR worked and we got notified. But the GUI showing all is well isn't so great. David SQL Backup log file 27/09/...
0 votes
Doh, I feel like a goober. Dunno how i missed that, but rereading the docs, it makes sense Thanks David / comments
  1. Community
  2. SQL Backup Previous Versions
  3. ERASEFILES dosen't erase files...
Doh, I feel like a goober. Dunno how i missed that, but rereading the docs, it makes sense Thanks David
0 votes
Great, I've been using SQL Backup for less than two months and have run smack bang into two bugs. [image] Never mind, hopefully the fixed version will be covered by our license to use 5.1. I'll give the @exitcode & @sqlerrorcode example from soonyu a try. David / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Failed backup not reported as failed
Great, I've been using SQL Backup for less than two months and have run smack bang into two bugs. Never mind, hopefully the fixed version will be covered by our license to use 5.1. I'll give th...
0 votes
Not really. What I expected was that the MAILTO and MAILTO_ONERROR to have been honored even though I specified an incorrect option, and the correct status code being returned to sql. In this case I would have expected 3 emails, one for each of MAILTO, MAILTO_ONERROR directives and an alert from the SQL Server Agent because the job step exit code indicated the step failed. David / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Failed backup not reported as failed
Not really. What I expected was that the MAILTO and MAILTO_ONERROR to have been honored even though I specified an incorrect option, and the correct status code being returned to sql. In this case...
0 votes
Cut and paste from the log file(20070726 043000 01.log) that corresponds to the failed backup. SQL Backup log file 26/07/2007 4:30:00 a.m.: Error 516: Multi database operations cannot use MIRRORFILE option. David / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Failed backup not reported as failed
Cut and paste from the log file(20070726 043000 01.log) that corresponds to the failed backup. SQL Backup log file 26/07/2007 4:30:00 a.m.: Error 516: Multi database operations cannot use MIRRORFIL...
0 votes
Some clarification, the job was reported as Failed in the SQL Backup Activity History window, but the SQL Server Agent reported the job as successful. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Failed backup not reported as failed
Some clarification, the job was reported as Failed in the SQL Backup Activity History window, but the SQL Server Agent reported the job as successful.
0 votes
Thanks for replying... Yup pretty obvious. The mirroring ( with the compression ) is an awsome feature. We used to rely on the native backup tool in sql 7 ( just switched to 2005 in last week) and strugled with the 140Gb ( and growing) backup and being able to archive it to a backup server. Backup now all done in 3/4 hour verses 2+hours with the native tool and xcopy. Is there a timeframe on the next release? David / comments
  1. Community
  2. SQL Backup Previous Versions
  3. MIRRORFILE not working as expected
Thanks for replying... Yup pretty obvious. The mirroring ( with the compression ) is an awsome feature. We used to rely on the native backup tool in sql 7 ( just switched to 2005 in last week) an...
0 votes
Total activity
14
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
4