Restores or verification of a limited number of Exchange and Sharepoint images protected using NetBackup 7.1.0.x to PDDO/MSDP storage units fail with the error "invalid tar header encountered, attempting to continue"

Article:TECH200000  |  Created: 2012-11-21  |  Updated: 2013-10-27  |  Article URL http://www.symantec.com/docs/TECH200000
Article Type
Technical Solution


Subject

Issue



While running NetBackup 7.1.0.x, certain Exchange or Sharepoint images may be corrupted when backing up to PDDO/MSDP (PureDisk Deduplication Option/Media Server Deduplication Pool, including NetBackup 50xx and 52xx appliances) and cannot be restored without complex byte-by-byte manual manipulation.  The data corruption is detectable with a NetBackup verify operation (bpverify) or using the standalone utility attached to this document.  These corrupted images can be duplicated with apparent success to any other storage units, however, restores from the duplicated copy also fail.  Expiration of the original PDDO/MSDP copy of the image removes the ability to completely restore the image.


Error



Error messages are not triggered/displayed at the time of the backup to PDDO/MSDP storage units or when the data is duplicated to other storage units.

Corrupted images produced by this problem will fail a NetBackup verify operation (bpverify) or can be detected using the standalone utility attached to this document.  NOTE: the standalone utility (NBUMSDPSizeCheck or PDDOSizeCheck, contained in the TECH200000.zip archive) can only detect corruption in the original copy of a problematic image.  If a problematic image has been duplicated to other storage units, these corrupted copies would only be detected by a NetBackup verify or restore operation.

After a failed restore/verify operation, the following messages can be found in the Job Details as well as bptm (Tape/Basic Disk Storage Unit) or bpdm (Dedup Storage Unit) logs.

If Attempting to Restore from Tape:

10/23/2012 18:18:50 - Info bptm (pid=3284) PN1581
10/23/2012 18:18:50 - Info bptm (pid=3284) INF - Waiting for positioning of media id PN1581 on server mediaserver.nbudomain.com for reading.
10/23/2012 18:18:50 - positioning PN1581 to file 2
10/23/2012 18:19:48 - positioned PN1581; position time: 0:00:58
10/23/2012 18:19:49 - begin reading
10/23/2012 18:19:49 - Error bptm (pid=3288) invalid tar header encountered, attempting to continue
10/23/2012 18:31:11 - end Restore; elapsed time 0:14:06
10/23/2012 18:31:12 - Error bptm (pid=3284) media manager terminated by parent process
 


If attempting to verify an image on a Deduplication Storage Unit:

10/23/2012 13:19:18 - begin Verify
10/23/2012 13:19:18 - requesting resource @aaaab
10/23/2012 13:19:19 - Info bpbrm (pid=9147) mediaserver.nbudomain.com is the host to restore to
10/23/2012 13:19:19 - Info bpbrm (pid=9147) reading file list from client
10/23/2012 13:19:19 - Info bpbrm (pid=9147) starting tar on client
10/23/2012 13:19:19 - Info tar (pid=9150) Restore started
10/23/2012 13:19:19 - Info bpbrm (pid=9147) bpdm pid: 9151
10/23/2012 13:19:19 - granted resource  MediaID=@aaaab;​DiskVolume=PureDiskVolume;​DiskPool=diskpool5020;​ Path=PureDiskVolume;​StorageServer=storageserver5020.nbudomain.com;​ MediaServer=mediaserver.nbudomain.com
10/23/2012 13:19:20 - Info bpdm (pid=9151) started
10/23/2012 13:19:20 - started process bpdm (pid=9151)
10/23/2012 13:19:24 - Info bpdm (pid=9151) reading backup image
10/23/2012 13:19:24 - Info bpdm (pid=9151) using 30 data buffers
10/23/2012 13:19:24 - Info bpdm (pid=9151) spawning a child process
10/23/2012 13:19:24 - Info bpbrm (pid=9151) child pid: 9192
10/23/2012 13:19:24 - Info bpdm (pid=9151) requesting nbjm for media
10/23/2012 13:19:51 - begin reading
10/23/2012 14:23:42 - end reading; read time: 1:03:51
10/23/2012 14:24:05 - begin reading
10/23/2012 15:12:33 - end reading; read time: 0:48:28
10/23/2012 15:12:52 - begin reading
.....

10/23/2012 21:06:05 - end reading; read time: 0:17:36
10/23/2012 21:06:21 - begin reading
10/23/2012 21:07:43 - end reading; read time: 0:01:22
10/23/2012 21:07:43 - Error bpbrm (pid=9147) from client mediaserver.nbudomain.com: ERR - Unexpected EOF on archive file
10/23/2012 21:07:44 - Info tar (pid=9150) done. status: 3
10/23/2012 21:07:44 - Error bpbrm (pid=9147) ERR - Unexpected EOF reading image. The image information is not complete.
10/23/2012 21:07:44 - Info bpdm (pid=9151) completed reading backup image
10/23/2012 21:07:44 - Error bpverify (pid=9139) from host mediaserver.nbudomain.com, ERR - Unexpected EOF reading image. The image information is not complete.
10/23/2012 21:07:44 - Info bpdm (pid=9151) EXITING with status 0
10/23/2012 21:07:44 - Error bpverify (pid=9139) Verify of policy Exchange2010DAG, schedule Full_Backup (exchange.nbudomain.com_1349562378) failed, tar had an unexpected error.
10/23/2012 21:07:44 - Info mediaserver.nbudomain.com (pid=9151) StorageServer=PureDisk:storageserver5020.nbudomain.com; Report=PDDO Stats for (storageserver5020.nbudomain.com): read: 670122093 KB, stream rate: 23.67 MB/sec, CR received: 670428832 KB, dedup: 0.0%
10/23/2012 21:07:44 - Error bpverify (pid=9139) Status = no images were successfully processed.
10/23/2012 21:07:44 - end Verify; elapsed time 7:48:26
10/23/2012 21:07:44 - Info tar (pid=9150) done. status: 183: tar received an invalid archive
no images were successfully processed  (191)
 

 


Environment



The behavior described above can be exhibited for images of these policy types targeted to PDDO/MSDP storage units:  (which could include environments using NetBackup 50xx and 52xx appliances)

  • Exchange 2010 backups - both GRT (Granular Recovery Technology) and non-GRT images.
  • Exchange 2007 backups - affected if using VSS snapshots (not affected if using the legacy streaming type)
  • GRT Sharepoint backups - All GRT Sharepoint backups use VSS snapshots and are affected
  • non-GRT Sharepoint backups are NOT affected

This issue affects NetBackup 7.1 GA and all 7.1.0.x Release Updates.

This issue does NOT affect NetBackup 7.5 GA and its corresponding Release Updates.


Solution



The formal resolution for this issue (Etrack 2977982) is included in the following releases:

  • NetBackup 7.5
  • NetBackup 5200/5220 Appliances 2.5

NetBackup 7.5 is now available. It is strongly recommended to update to the latest 7.5 Release Update.

NetBackup Appliances 2.5 is available via the Related Article linked below.

Best Practices:
Symantec strongly recommends the following best practices:
1. Always perform a full DR backup prior to making any changes to your environment.
2. Always make sure that your environment is running the latest version and patch level.
3. Perform periodic "test" restores.
4. Subscribe to technical articles.

How to Subscribe to Email Notification:
Directly to this Article:
Subscribe to this article by clicking on the Subscribe via email link on this page to receive notification when this article is updated with Release Information.

Software Alerts:
If you have not received information about this TechNote from the Symantec Email Notification Service as a Software Alert, you may subscribe via email and/or RSS using the links provided at the following pages:
For NetBackup Enterprise Server: http://www.symantec.com/business/support/index?page=content&key=15143&channel=ALERTS
For NetBackup Appliances: http://www.symantec.com/business/support/index?page=content&key=58991&channel=ALERTS


Attachments

Zip file containing multiple versions (PDDO or MSDP) for multiple platforms (SuSE Linux for PDDO, all supported platforms for MSDP) of the standalone detection utility. README docx files are also included. MD5 (TECH200000.zip) = 36addb095cda2eedd17c50c034b1ee53
TECH200000.zip (11.9 MBytes)
Detailed contents (and checksums) of the TECH200000.zip archive. MD5 (TECH200000_utility_manifest.txt) = af3427a980d3363a01f39bc4c5a5b802
TECH200000_utility_manifest.txt (1 kBytes)


Supplemental Materials

SourceETrack
Value2977982
Description

Restores of non-GRT Exchange Information store fails with filter_image indicating "invalid tar header encountered, attempting to continue"




Article URL http://www.symantec.com/docs/TECH200000


Terms of use for this information are found in Legal Notices