backup and restore issues using 5.2

ToehoToeho Posts: 73
edited October 26, 2007 2:08PM in SQL Backup Previous Versions
[Post Edited by Moderator to remove private information]

I have log shipping setup and today we started getting the following warning alerts. The backup says they are successfull on the retry but the retores are failing saying that the backups contain no lsn info and are not encrypted which in fact they are. Below are the to logs from the backup and retore jobs.

Backup log

Job 'ACS - Tlog Backup and Log Shipping for PRD' : Step 1, 'Backup PRD Tlog and ship to SWCS46DR' : Began Executing 2007-10-24 20:55:00
SQL Backup v5.2.0.2824
Backing up PRD (transaction log) to:
H:\Backups\PRD_10242007_205500_LOG.sqb

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.)
SQL error 3013: BACKUP LOG is terminating abnormally.

Memory profile
Type Maximum Minimum Average Blk count Total
Commit 1072431104 4096 2109131 1368 2885292032
Reserve 4128768 8192 450704 198 89239552
Free 19443712 4096 1091275 226 246628352
Private 1072431104 4096 2867884 1024 2936713216
Mapped 1019904 4096 124440 42 5226496
Image 7569408 4096 65183 500 32591872

Warning 300: Backup failed. Retry attempt: 1
Backup data size : 2.125 MB
Compressed data size: 116.500 KB
Compression rate : 94.65%

Processed 50 pages for database 'PRD', file 'PRDLOG1' on file 1.
BACKUP LOG successfully processed 50 pages in 0.043 seconds (9.513 MB/sec).

SQL Backup exit code: 300
name value
exitcode 300
sqlerrorcode 0
filename001 H:\Backups\PRD_10242007_205500_LOG.sqb
Job 'ACS - PRD Log Shipping Restore' started successfully. [SQLSTATE 01000]


Restore Log

Job 'ACS - PRD Log Shipping Restore' : Step 1, 'Restore PRD TLogs For Log Shipping' : Began Executing 2007-10-24 20:54:53
EXEC master.dbo.sqlbackup N'-SQL "RESTORE LOG [PRD] FROM DISK = ''G:\Logship\PRD_*_LOG.sqb'' WITH MAILTO_ONERROR = ''XXXX'', ERASEFILES = 2, NORECOVERY, FILEOPTIONS = 1 , MOVETO = ''G:\Logship\Applied'', PASSWORD = ''XXXX''"' [SQLSTATE 01000]SQL Backup v5.2.0.2824
Warning 170: No LSN information contained in file: 'PRD_10242007_145501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_150501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_151501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_152501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_153501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_154501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_155500_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_160501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_161501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_162501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_163501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_164500_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_165501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_170501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_171500_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_172501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_173501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_174500_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_175501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_180501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_181500_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_182501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_183501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_184501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_185501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_190500_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_191500_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_192501_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_193500_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_194500_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_195500_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_200500_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_201500_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_202500_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_203500_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_204500_LOG.sqb'
Warning 170: No LSN information contained in file: 'PRD_10242007_205500_LOG.sqb'
None of the backup files are encrypted.
Restoring PRD (transaction logs) from:
G:\Logship\PRD_10242007_145501_LOG.sqb
G:\Logship\PRD_10242007_150501_LOG.sqb
G:\Logship\PRD_10242007_151501_LOG.sqb
G:\Logship\PRD_10242007_152501_LOG.sqb
G:\Logship\PRD_10242007_153501_LOG.sqb
G:\Logship\PRD_10242007_154501_LOG.sqb
G:\Logship\PRD_10242007_155500_LOG.sqb
G:\Logship\PRD_10242007_160501_LOG.sqb
G:\Logship\PRD_10242007_161501_LOG.sqb
G:\Logship\PRD_10242007_162501_LOG.sqb
G:\Logship\PRD_10242007_163501_LOG.sqb
G:\Logship\PRD_10242007_164500_LOG.sqb
G:\Logship\PRD_10242007_165501_LOG.sqb
G:\Logship\PRD_10242007_170501_LOG.sqb
G:\Logship\PRD_10242007_171500_LOG.sqb
G:\Logship\PRD_10242007_172501_LOG.sqb
G:\Logship\PRD_10242007_173501_LOG.sqb
G:\Logship\PRD_10242007_174500_LOG.sqb
G:\Logship\PRD_10242007_175501_LOG.sqb
G:\Logship\PRD_10242007_180501_LOG.sqb
G:\Logship\PRD_10242007_181500_LOG.sqb
G:\Logship\PRD_10242007_182501_LOG.sqb
G:\Logship\PRD_10242007_183501_LOG.sqb
G:\Logship\PRD_10242007_184501_LOG.sqb
G:\Logship\PRD_10242007_185501_LOG.sqb
G:\Logship\PRD_10242007_190500_LOG.sqb
G:\Logship\PRD_10242007_191500_LOG.sqb
G:\Logship\PRD_10242007_192501_LOG.sqb
G:\Logship\PRD_10242007_193500_LOG.sqb
G:\Logship\PRD_10242007_194500_LOG.sqb
G:\Logship\PRD_10242007_195500_LOG.sqb
G:\Logship\PRD_10242007_200500_LOG.sqb
G:\Logship\PRD_10242007_201500_LOG.sqb
G:\Logship\PRD_10242007_202500_LOG.sqb
G:\Logship\PRD_10242007_203500_LOG.sqb
G:\Logship\PRD_10242007_204500_LOG.sqb
G:\Logship\PRD_10242007_205500_LOG.sqb

Cannot specify more than 32 devices.
Error 640: Cannot specify more than 32 devices.
Warning 151: MAILTO error: Failed to send mail. (Socket Error # 10060 Connection timed out.)

SQL Backup exit code: 640
name value
exitcode 640
sqlerrorcode 0
· Share on Twitter

Comments

  • Jason CookJason Cook Posts: 185
    Hi Toeho,
    The reason for the retries is that the amount of free contiguous memory is very low - currently 19.4MB.

    If you are using any keywords such as THREADCOUNT or FILECOUNT, it could be that SQL Backup then requiers more contiguous memory than is available, so attempts a retry with the MAXDATABLOCK keyword at half the previous value (down to 65536, the minimum).

    The simplest solution to resolving the first error is to restart the SQL Server instance, this will clean up any fragmentation that has occurred in the SQL Server memory space and the backup should succeed first time.

    As for your second issue, that seems rather strange, I will look into this one further and will follow up once I've investigated it further.

    Thanks,
    Jason
    · Share on Twitter
  • ToehoToeho Posts: 73
    My issue with the first error is that Sql Backup is telling Sql Server that a successfull backup has taken place but when Sql Backup tries to use these files it is unable to do so thus breaking the log chain. At this point I have two issues First I can not do a point in time recovery since 2:55pm yesterday and Second for my DR solution to work I now have to ship the tape that has the full backup (150gb backup file) to the DR site and then start rolling the logs to catch up again.

    Not sure if this is possible but it would be nice if Sql Backup was sure the backup file had been written out before it acknowledged to Sql Server that a sucessfull backup had taken place.
    · Share on Twitter
  • Jason CookJason Cook Posts: 185
    In the case of the restore, the problem appears not to be with the backup portion, but with the LSN information written afterwards.

    It is possible to restore each log individually, and this should restore correctly; but without valid LSN information it would not be possible to do "batch" log restores as you are trying to perform.

    Jason
    · Share on Twitter
  • ToehoToeho Posts: 73
    Sorry to disagree - when running the following command I get the error below - It would appear that the backup files are corupted


    EXEC master.dbo.sqlbackup N'-SQL "RESTORE LOG [PRD] FROM DISK = ''G:\Logship\bad\PRD_10242007_145501_LOG.sqb'' WITH MAILTO_ONERROR = ''xxx'', ERASEFILES = 2, NORECOVERY, FILEOPTIONS = 1 , MOVETO = ''G:\Logship\Applied'', PASSWORD = ''xxx''"'


    SQL Backup v5.2.0.2824
    None of the backup files are encrypted.
    Restoring PRD (transaction logs) from:
    G:\Logship\bad\PRD_10242007_145501_LOG.sqb

    Thread 0 error:
    Data decompression error: ZLib decompression error: data error
    Thread 1 error:
    Data decompression error: ZLib decompression error: data error
    Thread 2 error:
    Data decompression error: ZLib decompression error: data error

    SQL error 3013: SQL error 3013: RESTORE LOG is terminating abnormally.
    SQL error 3203: SQL error 3203: Read on 'SQLBACKUP_E5B3F5E8-3707-4CF4-AB94-3B25CF95B07401' failed, status = 995. See the SQL Server error log for more details.
    Warning 151: MAILTO error: Failed to send mail. (Socket Error # 10060 Connection timed out.)

    SQL Backup exit code: 790
    SQL error code: 3203

    (17 row(s) affected)

    name value
    exitcode 790
    sqlerrorcode 3203

    (2 row(s) affected)
    · Share on Twitter
  • Jason CookJason Cook Posts: 185
    Hi,
    I would agree with your thoughts given that last log; it does look like something has happened to the file.

    Out of interest, what compression level were you using during the backups? If you were using compression level 3, you may want to try dropping to compression level 2.

    I agree that the response from SQL Server indicating the backup was successful is rather concerning, I'll look into it further and try and establish what is going on.

    Thanks for your feedback,
    Jason
    · Share on Twitter
  • ToehoToeho Posts: 73
    We are using compression level 3
    · Share on Twitter
  • ToehoToeho Posts: 73
    At this point I have change the job script and moved compression level to 2 and removed the THREADCOUNT option. Should this create some stability in the backup job when the memory becomes fragmented or should I also look at setting the MAXDATABLOCK option as well??
    · Share on Twitter
  • ToehoToeho Posts: 73
    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.
    · Share on Twitter
  • ToehoToeho Posts: 73
    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)
    · Share on Twitter
  • Jason CookJason Cook Posts: 185
    To answer the questions in turn (since there are a few seperate ones):

    There is an issue with Compression Level 3 on some systems that is causing the backup to fail or be incomplete (as is the case in your latest log). Changing to level 2 should resolved any issues there.

    Some details on the THREADCOUNT keyword and memory usage is covered in another post here: http://www.red-gate.com/messageboard/vi ... php?t=5871

    If you are running that short of memory that you need to start using MAXDATABLOCK on a regular basis, your memory space is pretty fragmented. The simplest solution at this stage would be to restart the SQL Server instance when possible.

    In the GUI, if you hover over the red X it should explain why it's failed... that information will be quite useful in identifying why it doesn't like that backup. The missing LSN information in itself is an issue, but it won't cause the restore step to fail.

    Hope that helps,
    Jason
    · Share on Twitter
  • ToehoToeho Posts: 73
    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
    · Share on Twitter
Sign In or Register to comment.