Introduction:
A potential for data loss has been discovered in PureDisk Remote Office Edition 6.0, 6.1 and 6.2.  The Data Removal Policy may erroneously remove a file version if that file has recently been deleted from the client.

The ultimate effect of this issue is that Data Removal policies will remove more file versions than expected when the client itself performs a deletion of the file between backups.  This may result in a loss of a specific file version, or result in a complete loss of the file if that file didn't change for a period longer than the expiration period specified in the Data Removal policy.  See the How to Determine if Affected section below for examples.


What is Affected:
All environments running PureDisk Remote Office Edition 6.0, 6.1 and 6.2 using Data Removal.


How to Determine if Affected.:
All PureDisk environments using data removal policies are affected.  Below are examples of how either file data, or specific file versions may be lost.

Example 1: Loss of a specific file version:
Suppose that the following occurs:

- A Data Removal policy is configured to remove all versions older than 60 days

- Throughout 59 days, 10 different versions appeared (with different content) of a specific file

- On the 60th day, that specific file is deleted from the client, and at least one Backup is performed after that file is deleted.

The effect will be as follows:

- Only 9 versions of the file in question will be left after the next Data Removal.  The version that is erroneously deleted is the oldest version.  

Example 2: Loss of all file versions:
Suppose that the following occurs:

- A Data Removal policy is configured to remove all file versions older than 60 days

- A specific file did not change for more than 60 days (i.e. there is only 1 version for that file).

- The file is deleted from the client, and at least one Backup is performed after that file is deleted.

The effect will be as follows:

- The file will be removed during the next Data Removal, resulting in a loss of the file. The correct behavior should be that the file is removed 60 days after it was deleted.

Formal Resolution:
Symantec has acknowledged that the above-mentioned issue (ETrack 1224522) is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.

This issue will is resolved in the following patches:

- PureDisk Remote Office Edition 6.2.1.1

- PureDisk Remote Office Edition 6.1_MP2_P1

See the related documents section below for download links to these patches.  If running an affected PureDisk 6.0 environment, it is recommended to upgrade to at least 6.1 MP2 in order to apply a patch.


Workaround:
Until a formal resolution can be applied, it is recommended to Disable all Data Removal policies and monitor disk space.


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.


How to Subscribe to Software Alerts:
If you have not received this TechNote from the Symantec Email Notification Service as a Software Alert, please subscribe at the following
 http://maillist.entsupport.symantec.com/subscribe.asp