Performing a Sharepoint agent Incremental or Differential backup to different storage type than full backup results in error: 0xe000fe21 - An invalid path or file name was specified

Article:TECH191798  |  Created: 2012-06-26  |  Updated: 2014-06-19  |  Article URL http://www.symantec.com/docs/TECH191798
Article Type
Technical Solution


Issue



If a GRT enabled full backup is run to tape and a GRT differential or incremental backup is run to disk, the differential or incremental backup may fail with a job error.


Error



Final error: 0xe000fe21 - An invalid path or file name was specified.
Final error category: Job Errors

 


Environment



 FULL backup of the SharePoint Farm  is done to tape. Differential or incremental backup to a disk target fails. If the differential or incremental runs to tape, it completes successfully.


Cause



The data changes that make up a Sharepoint incremental or differential backup are combined with the full backup to create a composite view of the data.  When the full and incremental/differential backups are targeted to different storage device types this combination step is not working properly.


Solution



 

This issue is resolved in Backup Exec 2014 or later versions. 
 To resolve this issue and receive the new Backup Exec improvements please upgrade to the current version of Backup Exec
 NOTE:   Symantec continues to focus on the current release and future releases, there are no plans to address this issue by way of a patch or hotfix in earlier versions of the software at the present time. Please contact your Symantec Sales representative or the Symantec Partner for upgrade information including upgrade eligibility to the release containing the resolution for this issue. For information on how to contact Symantec Sales, please see  http://www.symantec.com

Supplemental Materials

SourceETrack
Value2827360
Description

SPS:Diff and Inc backups to disk fail if full backup was done to tape


SourceUMI
ValueV-79-57344-65057


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


Terms of use for this information are found in Legal Notices