On Windows systems running NetBackup 7.x Media Server Deduplication, queue processing may fail if the sorted tmp file reaches 4 GB in size. (updated June 15, 2011)
| Article:TECH153084 | | | Created: 2011-02-10 | | | Updated: 2011-06-15 | | | Article URL http://www.symantec.com/docs/TECH153084 |
Problem
Document History:
June 15, 2011 - updated to reflect fix availability in maintenance release 7.1.0.1
Introduction:
On Windows systems running NetBackup 7.x Media Server Deduplication (MSDP), queue processing may fail when the sorted tmp file reaches 4 GB in size.
UNIX based systems are not impacted by this issue.
Detail:
A rare potential for dataloss has been discovered when performing Media Server Deduplication (MSDP) on Windows platforms due to an integer offset overflow issue. This problem can occur any time files such as sort-#####-#####.tmp or sorted-#####-#####.tlog reach a size of 4GB. The overflow may cause data loss if the problem occurs at the point the sorted file reaches the 4GB file boundary limit during the sort process, possibly causing the file to be overwritten or unusable.
All environments running MSDP on Windows platforms should apply the Emergency Engineering Binary (EEB) bundle available from support by referencing this document and Etrack 2233961 (for NetBackup 7.0.1) or 2300337 (for NetBackup 7.1) to mitigate the potential for any data loss.
This issue can also cause queue processing to stop, eventually leading to failures with status code 129 (Disk storage unit is full) reported after the storage unit becomes full. Status code 213 (no storage units available for use) may also be reported. In addition, other backups and deduplcations to the storage unit will begin to fail.
Error
In Storage\log\storaged.log, if a sort-#####-#####.tmp file reaches 4GB in size, queue processing will fail with the following errors:
February 08 11:22:54 INFO [0000000008E222F0]: Starting sort of tlog file range 1234567 - 2345678.
February 08 14:29:55 ERR [0000000008E222F0]: 25042:
CRC mismatch for spool entry header at offset 8
February 08 14:29:55 ERR [0000000008E222F0]: 25042:
Could not read spool entry: Illegal byte sequence
February 08 14:29:55 ERR [0000000008E222F0]: 25042: Could not read object.
February 08 14:29:55 ERR [0000000008E222F0]: 25000: Could not merge-sort tlog files 1234567 - 2345678:no error
Environment
What is Affected:
The following versions of NetBackup MSDP are affected on all supported Windows operating systems:
- NetBackup 7.0
- NetBackup 7.0 Release Update 1 (7.0.1)
- NetBackup 7.1
Note: At the time this Alert was issued, 64 bit Windows 2003 & 2008 were the supported Windows operating systems for these product versions.
Solution
The formal resolution to this issue (Etrack 2252912) is included the following release:
- NetBackup 7.1 Maintenance Release 1 (7.1.0.1)
This release is available via the download links provided in the "Related Documents" section below.
Workaround:
When this problem is encountered, tlog processing will stop and will not succeed until an Emergency Engineering Binary (EEB) is applied. If the binary is not applied, there is a potential for data loss as queue processing continues to fail to complete.
The EEB bundle is available on request by contacting Symantec technical support, referencing this document ID and the Etrack number appropriate to the version of NetBackup installed:
- For NetBackup 7.0.1, reference Etrack 2233961
- For NetBackup 7.1, reference Etrack 2300337
The Storage/queue directory should be examined. If tlogs exist in the range reported in the error messages found - for example, for the error messages seen above, the range would be between 12345.tlog and 23456.tlog - then recovery is possible after installing the appropriate EEB bundle.
If the tlog files do not exist in the Storage/queue directory, a support case should be opened for assistance with a recovery plan.
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 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 page:
http://www.symantec.com/business/support/index?page=content&key=15143&channel=ALERTS
|
|
| Source | ETrack |
| Value | 2252912 |
| Description | processqueue not running to completion. Currently have 242,054 tlogs on the media server |
Related Articles
Article URL http://www.symantec.com/docs/TECH153084
Terms of use for this information are found in Legal Notices
Thank you.