A very rare potential for data loss has been discovered on Non-Windows hosts running NetBackup PureDisk Remote Office (PDRO) 6.0 - 6.6.0.3 or with NetBackup Media Servers using Deduplication (such as PDDO, PDDE, MSDP).

Problem

A very rare potential for data loss has been discovered on Non-Windows hosts running NetBackup PureDisk Remote Office (PDRO) 6.0 - 6.6.0.3 or with NetBackup Media Servers using Deduplication (such as PDDO, PDDE, MSDP). This also affects Non-Windows media servers running NetBackup 7.0 Server/Enterprise server with the deduplication option / engine.

Solution

Introduction:
A very rare potential for data loss has been discovered on Non-Windows hosts running NetBackup PureDisk Remote Office (PDRO) 6.0 - 6.6.0.3 or with NetBackup Media Servers using Deduplication options (such as PDDO, PDDE, MSDP).  This also affects Non-Windows media servers running NetBackup 7.0 Server/Enterprise server with the deduplication option.  If connection to the storage volume is lost due to a system/hardware issue at a very precise moment, data loss can occur.  Windows platforms are not affected by data loss resulting from this issue (See the Related Documents section below for a note on how this affects Windows).  

Please note that this Linux/Solaris centered data loss issue was discovered during recent code inspection and affects PureDisk versions 6.0 - 6.6.0.3, but has not been reported in the field due to the timing and circumstances required for the issue to surface.  

This alert is being written only as a measure of policy to communicate any data loss issues, no matter how vague or improbable.


What is affected:
- PureDisk Remote Office (PDRO) content routers running versions 6.0 - 6.6.0.3
- PureDisk DeDuplication Option (PDDO) versions 6.0 - 6.6.0.3, as the underlying PureDisk server is Non-Windows.
- NetBackup 7.0 NetBackup Media Server Deduplication Option (Also known as PDDE) where the server performing Deduplication is Non-Windows (Such as Linux and Solaris).
 
 
How to determine if affected:
Data loss has been known to occur if ALL of the following conditions are met:
-  A PureDisk version mentioned above are being run on a PDRO or PDDE Server running on a non-Windows Platform.
-  An environmental circumstance (such as a bad disk or cable connection) causes a write error to the storage volume.
-  The timing is such that this connection error prevents the "tlogid update" event
-  All other write events are not prevented and complete successfully.
 
When a "tlogid update" failure occurs, but all other writes succeed, the follow log message will be displayed in the spoold.log (or other session based log files) in /Storage/log/spoold:
<date> ERR [0000000001230AC0]: 25013: Could not update tlogid in file <spool path>\spool\.tlogid to 511 (Permission denied)
If affected, The command <spool path>//log/spoold, 'grep -r "Could not update tlogid"' would display a message such as the above.

Additionally, an "object not found" message would be seen if a restore were attempted on a file object affected by this issue.


Workaround:
If it is believed that the environment is affected and a Formal Resolution (below) is not yet available or feasible to apply, please contact Technical Services and reference this TechNote ID (350196) and Etrack 2017260 for an Emergency Fix and further instructions.


Formal Resolution:
Symantec has acknowledged that the above mentioned issue (Etrack 2017260) is present in the current version(s) of the product(s) mentioned at the end of this article.  Symantec is actively investigating this and working towards a formal fix for this issue for the following release(s):
 
- PureDisk 6.6.1 Remote Office Edition / Deduplication Option (PDDO)
- NetBackup 7.0.1 NetBackup Media Server Deduplication Option (Also known as PDDE or MSD)

Please check with this document as fixes are released to confirm details.


Best Practices:
Symantec strongly recommends the following best practices:
1. Always perform a full backup prior to and after 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 / alerts


Article Subscription:
Subscribe to this TechNote for any updates that are made to this article, by clicking on the following link:
 http://maillist.support.veritas.com/notification.asp?doc=350196


Software Alerts:
If you have not received this from the Symantec Technical Support Email Notification Service, please click on the following link to subscribe to future Notifications:
 http://maillist.entsupport.symantec.com/subscribe.asp
 

 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)