During a backup operation on a deduplication folder that is on a volume that has been extended, the low space threshold is reported incorrectly.
When the volume where a Backup Exec Deduplication Storage Folder is located is made larger by using the Windows extend functionality, the Backup Exec reports the wrong error when reaching the low volume threshold. Normally, when the low volume threshold is reached, an alert is generated informing the administrator that the low volume threshold has been reached and that more disk space needs to be made available to the deduplication folder before the backup can continue.
On a volume that has already been extended, a backup continues until it reaches another internal threshold. The job then fails with the following error:
0x17V-79-57344-34028 - A backup storage read/write error has occurred.
If this error is encountered, check the properties of the deduplication folder. If the deduplication folder is below the threshold of available free space on the volume, then either more space needs to be made available to the deduplication folder by extending the volume again or by reducing the amount of data that is being backed up to this deduplication folder.
Symantec Corporation has acknowledged that the above-mentioned issue 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 is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see http://www.symantec.com
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.