V-287-40960-39685 - Deduplication Folder creation or recreation fails with the error "An Error Occurred While Creating the deduplication storage folder"

Article: 100024258
Last Published: 2019-04-17
Ratings: 1 2
Product(s): Backup Exec

Problem

V-287-40960-39685 - Deduplication Folder creation or recreation fails with the error "An Error Occurred While Creating the deduplication storage folder" in BE 2010 or "Unable to create the deduplication disk storage" in BE 2012 and later.

 

Error Message

The Backup Exec User Interface shows the following error :
An error occurred while creating the deduplication storage folder

Solution

  1. Make sure there are no instances of Postgre, Spoold and Spad processes running in task manager before an attempt is made to create or import the deduplication folder. By default, the deduplication services are disabled and will be in stopped state if a deduplication folder is not configured.
  2. Add the Backup Exec service account (BESA) to the local administrators group on the media server (Backup Exec Server). In case the deduplication folder exists and it is being reimported make sure system and BESA have full rights on each folder and subfolders of deduplication storage. Check the permission recursively and make sure it is being inherited properly.
  3. Make sure User Access Control (UAC) is disabled.
  4. If the Deduplication folder is being configured on the same place where it existed before and the files are present then make sure the user account and password used to recreate this deduplication matches to the one used when the folder was created for the first time. If the password was changed in dedupe then make sure to use the latest updated password.
  5. The username and password used when creating the deduplication folder may contain invalid characters. Refer Backup Exec administrator's guide -> Deduplication disk storage credentials section.
  6. File named 'Backup' under Program Files\Symantec\ or under the folder where Backup Exec is Installed might pose a problem for postgresql service startup and cause a failure during the deduplication folder creation/import. Remove/Rename it, if such a file exist at this path.
  7. If the server name contains non ASCII characters.  This most often occurs on servers that are setup in non English languages.  In this case, the server must be renamed to contain all ASCII characters before it can host a deduplication storage folder.  
    Examples of non ASCII characters are c cedilla, vowels with accents, etc.  Note that an attempt was already made to create a deduplication folder on this system, that deduplication folder can not be re-used even after renaming the server.  Please delete the partially created deduplication folder from disk before attempting to use the same directory.  Details on valid internet hostnames (A-Z, a-z, 0-1, dash, and period) can be found at https://tools.ietf.org/html/rfc1034#section-3.5
  8. Refer the pdde-config.log present in DedupeFolderLocation\Log folder for clues.
  9. Backup Exec Dedupe folder before version BE 20 cannot be imported in BE 20 due to the difference in folder structure. The BE 16 and earlier dedupe folder will need to be converted to suit BE 20 requirement. By default the conversion is carried out after the BE upgrade to 20 completes. If in case there are some problem please refer this conversion article for help.
  10. The Dedupe import can also fail due to a table in Backup Exec SQL database still containing an orphan entry, if the deletion of earlier deduplication storage folder was not done properly.

The above are some points that can be checked before contacting the Veritas Technical Support team.

Please Refer Article In The Related Article section for BESA Rights for further information

 

 

References

UMI : V-287-40960-39695 UMI : V-287-40960-39685

Was this content helpful?