How can we help you today? How can we help you today?
Toeho
Activity overview Badges (0) Posts (25) Comments (23)

Comments

Sort by recent activity
At this point we have rebuilt the cluster on Windows 2003 R2 as we had a client deadline to meet and MSFT could not identify what was going on in a short time frame. After doing some research it appeared that the default gateway was disappearing from the nics thus the cluster would die. MSFT could not determine is this was the casue of the issue of just another symptom of the main cause. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Sql Backup 6.2 support on Windows 2008 R2 Cluster
At this point we have rebuilt the cluster on Windows 2003 R2 as we had a client deadline to meet and MSFT could not identify what was going on in a short time frame. After doing some research it ap...
0 votes
That was it - Thanks / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Sql Backup Service will not start
That was it - Thanks
0 votes
When running filemon on this particular cluster I get the following error: "The image file c:\filemon64.exe is valid, but is for a machine type other than the current machine" It would appear that filemon is not compatible with Itanium 64 bit server. Please let me know if there is a log that the gui creates or if logging is available. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. SQL Backup GUI crashes
When running filemon on this particular cluster I get the following error: "The image file c:\filemon64.exe is valid, but is for a machine type other than the current machine" It would appear that ...
0 votes
Install goes perfectly and the only thing in the application log is this Computer: DALP1SQL02B Description: Product: SQL Backup 5 -- Installation operation completed successfully. Basicly when I try and open the GUI I get a splash screen and cpu goes up for about 10~15 seconds then the RedGate.SqlBackup.UI.exe*32 process dies. I have uninstalled and reinstalled the software but I keep getting the same results / comments
  1. Community
  2. SQL Backup Previous Versions
  3. SQL Backup GUI crashes
Install goes perfectly and the only thing in the application log is this Computer: DALP1SQL02B Description: Product: SQL Backup 5 -- Installation operation completed successfully. Basicly when I tr...
0 votes
Is there an update on this as I am havingthe same issue - version 5.3 / comments
  1. Community
  2. SQL Backup Previous Versions
  3. File locations during a restore
Is there an update on this as I am havingthe same issue - version 5.3
0 votes
It appears my problem was trying tp restore via UNC as after I copied the files to the local server I was able to do the restore. Is there a threshhold that you should not go above when doing a restore from a unc path, this backup file is close to 60gb in size?? / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Restore Error
It appears my problem was trying tp restore via UNC as after I copied the files to the local server I was able to do the restore. Is there a threshhold that you should not go above when doing a res...
0 votes
I have emailed you the file Thanks / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Log Shipping failing
I have emailed you the file Thanks
0 votes
Another bit of information. My full backup had the memory issue last night and was supposably successfull on the first retry basied on the logs but I wanted to validate the backup before I sent the tape to the DR site. When I try opening the backup files via the GUI there is a red X in the ok column and it does not give me the oportunity to decrypt the files. Again the backup looks to be successfull from the log and from SQL. I belive there is a major bug here that needs to be addressed. I have over 150 sql servers with almost 1000 databases and can not validate each backup every day. Hope you understand my growing frustration. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. backup and restore issues using 5.2
Another bit of information. My full backup had the memory issue last night and was supposably successfull on the first retry basied on the logs but I wanted to validate the backup before I sent the...
0 votes
Hovering over the red X provides the following Thread 0 Error Data decompression error: file may be corupted SQL error 3013: SQL error 3013: RESTORE FILELIST is terminating abnormally SQL error 3203: SQL error 3203: Read on 'SQLBACKUP_3FF96159_F376-40A4-8ACD-9DB902A90A92' failed. status = 995. See the SQL Server error logs for more details SQL error 0: Failed to read filelist details (o rows) SQL Backup exit code: 790 / comments
  1. Community
  2. SQL Backup Previous Versions
  3. backup and restore issues using 5.2
Hovering over the red X provides the following Thread 0 Error Data decompression error: file may be corupted SQL error 3013: SQL error 3013: RESTORE FILELIST is terminating abnormally SQL error 320...
0 votes
Hope this is helpful, curious as to why the backup log says it is successfull but all the verifications say otherwise?? Is it safe to assume it the backup is not successfull on the first pass then it will not be successfull even tough the log says it is???? Here is the log from the full backup: SQL Backup log file 5.2.0.2824 10/25/2007 9:00:06 PM: Backing up PRD (full database) to: 10/25/2007 9:00:06 PM: h:\Backups\PRD_10252007_210006_FULL_01.sqb 10/25/2007 9:00:06 PM: h:\Backups\PRD_10252007_210006_FULL_02.sqb 10/25/2007 9:00:06 PM: h:\Backups\PRD_10252007_210006_FULL_03.sqb 10/25/2007 9:00:06 PM: h:\Backups\PRD_10252007_210006_FULL_04.sqb 10/25/2007 9:00:06 PM: h:\Backups\PRD_10252007_210006_FULL_05.sqb 10/25/2007 9:00:06 PM: h:\Backups\PRD_10252007_210006_FULL_06.sqb 10/25/2007 9:00:06 PM: h:\Backups\PRD_10252007_210006_FULL_07.sqb 10/25/2007 9:00:06 PM: h:\Backups\PRD_10252007_210006_FULL_08.sqb 10/25/2007 9:00:06 PM: BACKUP DATABASE [PRD] TO DISK = 'h:\Backups\<AUTO>' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', INIT, PASSWORD = 'XXXXXXXXXX', KEYSIZE = 128, MAILTO_ONERROR = 'xxxx', COMPRESSION = 1, THREADS = 8 10/25/2007 9:00:06 PM: VDI error 1010: Failed to get configuration from server. Check that the SQL Server instance is running, and that you have the SQL Server Systems Administrator server role. Error code: (-2139684860: An abort request is preventing anything except termination actions.) 10/25/2007 9:00:07 PM: SQL error 3013: BACKUP DATABASE is terminating abnormally. 10/25/2007 9:00:07 PM: 10/25/2007 9:00:07 PM: Memory profile 10/25/2007 9:00:07 PM: Type Maximum Minimum Average Blk count Total 10/25/2007 9:00:07 PM: 10/25/2007 9:00:07 PM: Commit 1072431104 4096 2100156 1374 2885615616 10/25/2007 9:00:07 PM: Reserve 4128768 8192 450332 198 89165824 10/25/2007 9:00:07 PM: Free 19443712 4096 1052899 234 246378496 10/25/2007 9:00:07 PM: Private 1072431104 4096 2865150 1025 2936778752 10/25/2007 9:00:07 PM: Mapped 1019904 4096 115123 47 5410816 10/25/2007 9:00:07 PM: Image 7569408 4096 65183 500 32591872 10/25/2007 9:00:07 PM: 10/25/2007 9:00:07 PM: Warning 300: Backup failed. Retry attempt: 1 10/25/2007 9:00:09 PM: BACKUP DATABASE [PRD] TO DISK = 'h:\Backups\PRD_10252007_210006_FULL_01.sqb', DISK = 'h:\Backups\PRD_10252007_210006_FULL_02.sqb', DISK = 'h:\Backups\PRD_10252007_210006_FULL_03.sqb', DISK = 'h:\Backups\PRD_10252007_210006_FULL_04.sqb', DISK = 'h:\Backups\PRD_10252007_210006_FULL_05.sqb', DISK = 'h:\Backups\PRD_10252007_210006_FULL_06.sqb', DISK = 'h:\Backups\PRD_10252007_210006_FULL_07.sqb', DISK = 'h:\Backups\PRD_10252007_210006_FULL_08.sqb' WITH NAME = 'Database (PRD), 10/25/2007 9:00:06 PM', DESCRIPTION = 'Backup on 10/25/2007 9:00:06 PM Server: SWCS46CI Database: PRD', INIT, PASSWORD = 'XXXXXXXXXX', KEYSIZE = 128, MAILTO_ONERROR = 'xxxx', COMPRESSION = 1, THREADS = 8 10/25/2007 9:54:35 PM: Database size : 678.954 GB 10/25/2007 9:54:35 PM: Compressed data size: 129.178 GB 10/25/2007 9:54:35 PM: Compression rate : 80.97% Processed 10971712 pages for database 'PRD', file 'PRDDATA1' on file 1. Processed 10884784 pages for database 'PRD', file 'PRDDATA2' on file 1. Processed 10827208 pages for database 'PRD', file 'PRDDATA3' on file 1. Processed 10890352 pages for database 'PRD', file 'PRDDATA4' on file 1. Processed 10871016 pages for database 'PRD', file 'PRDDATA5' on file 1. Processed 10906784 pages for database 'PRD', file 'PRDDATA6' on file 1. Processed 10922776 pages for database 'PRD', file 'PRDDATA7' on file 1. Processed 10924384 pages for database 'PRD', file 'PRDDATA8' on file 1. Processed 776840 pages for database 'PRD', file 'PRDDATA9' on file 1. Processed 2252 pages for database 'PRD', file 'PRDLOG1' on file 1. BACKUP DATABASE successfully processed 87978108 pages in 3257.421 seconds (221.253 MB/sec). Here is the out put from RESTORE SQBHEADERONLY SQL Backup v5.2.0.2824 Reading SQB file header of "H:\Backups\PRD_10252007_210006_FULL_01.sqb" Backup group ID : 0 File number : 0 of 0 Backup type : 1 (Database) Native backup size : 83.580 GB Backup start : Thursday, October 25, 2007 9:00:09 PM Backup end : Thursday, October 25, 2007 9:54:35 PM Server name : SWCS46CI Database name : PRD First LSN : Last LSN : Checkpoint LSN : Database backup LSN : Reading SQB file header of "H:\Backups\PRD_10252007_210006_FULL_02.sqb" Backup group ID : 0 File number : 0 of 0 Backup type : 1 (Database) Native backup size : 84.197 GB Backup start : Thursday, October 25, 2007 9:00:09 PM Backup end : Thursday, October 25, 2007 9:54:35 PM Server name : SWCS46CI Database name : PRD First LSN : Last LSN : Checkpoint LSN : Database backup LSN : Reading SQB file header of "H:\Backups\PRD_10252007_210006_FULL_03.sqb" Backup group ID : 0 File number : 0 of 0 Backup type : 1 (Database) Native backup size : 84.043 GB Backup start : Thursday, October 25, 2007 9:00:09 PM Backup end : Thursday, October 25, 2007 9:54:35 PM Server name : SWCS46CI Database name : PRD First LSN : Last LSN : Checkpoint LSN : Database backup LSN : Reading SQB file header of "H:\Backups\PRD_10252007_210006_FULL_04.sqb" Backup group ID : 0 File number : 0 of 0 Backup type : 1 (Database) Native backup size : 83.681 GB Backup start : Thursday, October 25, 2007 9:00:09 PM Backup end : Thursday, October 25, 2007 9:54:35 PM Server name : SWCS46CI Database name : PRD First LSN : Last LSN : Checkpoint LSN : Database backup LSN : Reading SQB file header of "H:\Backups\PRD_10252007_210006_FULL_05.sqb" Backup group ID : 0 File number : 0 of 0 Backup type : 1 (Database) Native backup size : 83.719 GB Backup start : Thursday, October 25, 2007 9:00:09 PM Backup end : Thursday, October 25, 2007 9:54:35 PM Server name : SWCS46CI Database name : PRD First LSN : Last LSN : Checkpoint LSN : Database backup LSN : Reading SQB file header of "H:\Backups\PRD_10252007_210006_FULL_06.sqb" Backup group ID : 0 File number : 0 of 0 Backup type : 1 (Database) Native backup size : 83.933 GB Backup start : Thursday, October 25, 2007 9:00:09 PM Backup end : Thursday, October 25, 2007 9:54:35 PM Server name : SWCS46CI Database name : PRD First LSN : Last LSN : Checkpoint LSN : Database backup LSN : Reading SQB file header of "H:\Backups\PRD_10252007_210006_FULL_07.sqb" Backup group ID : 0 File number : 0 of 0 Backup type : 1 (Database) Native backup size : 84.084 GB Backup start : Thursday, October 25, 2007 9:00:09 PM Backup end : Thursday, October 25, 2007 9:54:35 PM Server name : SWCS46CI Database name : PRD First LSN : Last LSN : Checkpoint LSN : Database backup LSN : Reading SQB file header of "H:\Backups\PRD_10252007_210006_FULL_08.sqb" Backup group ID : 0 File number : 0 of 0 Backup type : 1 (Database) Native backup size : 84.091 GB Backup start : Thursday, October 25, 2007 9:00:09 PM Backup end : Thursday, October 25, 2007 9:54:35 PM Server name : SWCS46CI Database name : PRD First LSN : Last LSN : Checkpoint LSN : Database backup LSN : (152 row(s) affected) name value exitcode 0 sqlerrorcode 0 filename001 H:\Backups\PRD_10252007_210006_FULL_01.sqb filename002 H:\Backups\PRD_10252007_210006_FULL_02.sqb filename003 H:\Backups\PRD_10252007_210006_FULL_03.sqb filename004 H:\Backups\PRD_10252007_210006_FULL_04.sqb filename005 H:\Backups\PRD_10252007_210006_FULL_05.sqb filename006 H:\Backups\PRD_10252007_210006_FULL_06.sqb filename007 H:\Backups\PRD_10252007_210006_FULL_07.sqb filename008 H:\Backups\PRD_10252007_210006_FULL_08.sqb (10 row(s) affected) Output from RESTORE VERIFYONLY first attempt SQL Backup v5.2.0.2824 Verifying files: H:\Backups\PRD_10252007_210006_FULL_01.sqb H:\Backups\PRD_10252007_210006_FULL_02.sqb H:\Backups\PRD_10252007_210006_FULL_03.sqb H:\Backups\PRD_10252007_210006_FULL_04.sqb H:\Backups\PRD_10252007_210006_FULL_05.sqb H:\Backups\PRD_10252007_210006_FULL_06.sqb H:\Backups\PRD_10252007_210006_FULL_07.sqb H:\Backups\PRD_10252007_210006_FULL_08.sqb Error 715: Backup file is not encrypted. SQL Backup exit code: 715 (13 row(s) affected) name value exitcode 715 sqlerrorcode 0 filename001 H:\Backups\PRD_10252007_210006_FULL_01.sqb filename002 H:\Backups\PRD_10252007_210006_FULL_02.sqb filename003 H:\Backups\PRD_10252007_210006_FULL_03.sqb filename004 H:\Backups\PRD_10252007_210006_FULL_04.sqb filename005 H:\Backups\PRD_10252007_210006_FULL_05.sqb filename006 H:\Backups\PRD_10252007_210006_FULL_06.sqb filename007 H:\Backups\PRD_10252007_210006_FULL_07.sqb filename008 H:\Backups\PRD_10252007_210006_FULL_08.sqb (10 row(s) affected) Output from RESTORE VERIFYONLY second attempt SQL Backup v5.2.0.2824 Verifying files: H:\Backups\PRD_10252007_210006_FULL_01.sqb H:\Backups\PRD_10252007_210006_FULL_02.sqb H:\Backups\PRD_10252007_210006_FULL_03.sqb H:\Backups\PRD_10252007_210006_FULL_04.sqb H:\Backups\PRD_10252007_210006_FULL_05.sqb H:\Backups\PRD_10252007_210006_FULL_06.sqb H:\Backups\PRD_10252007_210006_FULL_07.sqb H:\Backups\PRD_10252007_210006_FULL_08.sqb Thread 0 error: Data decompression error: file may be corrupted Process terminated unexpectedly. Error code: -2139684860 Thread 1 error: Data decompression error: file may be corrupted Process terminated unexpectedly. Error code: -2139684860 Thread 2 error: Process terminated unexpectedly. Error code: -2139684860 Thread 3 error: Process terminated unexpectedly. Error code: -2139684860 Thread 4 error: Process terminated unexpectedly. Error code: -2139684860 Thread 5 error: Process terminated unexpectedly. Error code: -2139684860 Thread 6 error: Process terminated unexpectedly. Error code: -2139684860 Thread 7 error: Process terminated unexpectedly. Error code: -2139684860 SQL error 3013: SQL error 3013: VERIFY DATABASE is terminating abnormally. SQL error 3203: SQL error 3203: Read on 'SQLBACKUP_D9230D54-61BB-498F-A848-BE959DE42D60' failed, status = 995. See the SQL Server error log for more details. SQL Backup exit code: 790 SQL error code: 3203 (34 row(s) affected) name value exitcode 790 sqlerrorcode 3203 filename001 H:\Backups\PRD_10252007_210006_FULL_01.sqb filename002 H:\Backups\PRD_10252007_210006_FULL_02.sqb filename003 H:\Backups\PRD_10252007_210006_FULL_03.sqb filename004 H:\Backups\PRD_10252007_210006_FULL_04.sqb filename005 H:\Backups\PRD_10252007_210006_FULL_05.sqb filename006 H:\Backups\PRD_10252007_210006_FULL_06.sqb filename007 H:\Backups\PRD_10252007_210006_FULL_07.sqb filename008 H:\Backups\PRD_10252007_210006_FULL_08.sqb (10 row(s) affected) / comments
  1. Community
  2. SQL Backup Previous Versions
  3. backup and restore issues using 5.2
Hope this is helpful, curious as to why the backup log says it is successfull but all the verifications say otherwise?? Is it safe to assume it the backup is not successfull on the first pass then ...
0 votes
Total activity
59
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
11