RESTORE HEADERONLY returns with INCOMPLETE for SQL 2016 SP2CU3 but not SP1CU7

  • I have a process that verifies a backup and determines if I have enough space available to do a restore prior to actually attempting the restore.  In this particular instance I have a SQL 2016 database with TDE encryption and my backup is compressed and split across multiple files.  When running the following I get two different results

    On a server with SQL 2016 SP2 CU1, CU2, or CU3
    restore headeronly from disk =N'\\sqlshare\TempDBBackups\DO_NOT_DELETE_20190108_041034.1.bak'
    *** INCOMPLETE ***   NULL   NULL   NULL   NULL   1      NULL   NULL   NULL   NULL   NULL   NULL   NULL       NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL       NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL       NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL   NULL       NULL

    On a server with SQL 2016 SP1 CU7 or SP2
    restore headeronly from disk =N'\\sqlshare\TempDBBackups\DO_NOT_DELETE_20190108_041034.1.bak'
    NULL   NULL   1      NULL   1      1      2      sqluser destserver       dbname      852    2019-01-08 02:36:42.000    395003413504  1402654000007798600025       1402654000022040800001     1402654000007798600025     1398581000000633600300     2019-01-08 09:22:05.000  2019-01-08 09:36:25.000    52     0      1033   196609 130    4608   13     0      4466       destserver      512    F82706AB-DE2F-4295-9338-673C4895C4CC     F5DC7316-F94A-45BB-9AB0-89D213BA6791  SQL_Latin1_General_CP1_CI_AS      8C837805-2B44-45C9-AA49-7C0078F46A19     0      0       0      0      0      0      0      0      0      0      F5DC7316-F94A-45BB-9AB0-89D213BA6791       NULL   FULL   NULL   NULL   Database      3916B0B4-F6EA-4492-B771-82111995D2CB     112184519168       0      NULL   NULL   NULL

    So what I am seeing is an issue with attempting to read header information from a split and compressed TDE backup on SQL 2016 with anything above SP2 installed.  I have not tried CU4 yet.  Just curious if anyone else has run into this issue and has a workaround or if I should open a ticket with MS

    Thanks in advance for any information/replies

Viewing post 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply