Problem with dedupe folder
I've created a new Backup Exec server after our old one crashed. I'm trying to create a depdupe folder by pointing it to the old dedupe folder that we had on another storage device (I'd like to save the old backups if possible). When I go to create the folder and point it to the existing location I get this message:
"An error occurred while creating the deduplication folder. See the following link..."
I checked the logs and this is what I've found:
E:\BackupExecDeduplicationFolder\etc\puredisk\spa.cfg: verified OK
Error: 25012: Authentication failed, No such user backupexec !
Tue 01/19/2016 8:13:08.53 ERR: "G:\Program Files\Symantec\Backup Exec\spad.exe" --check_creds encountered an error.
I think it might be permission issue but I'm not sure how to resolve it. Any help is greatly appreciated!!
Log a support call with Veritas so that they can assist...don't mess around with a dedupe folder because unless you know what you're doing, you run the risk of corrupting the dedupe folder and rendering all backups unrestorable.
Thanks!
The deduplication database has a separate account and username from those the Backup Exec Services or Backup Exec System logon.
Info here: http://www.veritas.com/docs/000005292
Quoting from: http://www.veritas.com/docs/000005534
-----
ATTENTION: The spauser utility prompts for the previous password before allowing the user to create a new password. It is critical to keep track of this password. If this password is lost and the password is changed in the matching Backup Exec logon account, it will not be possible to bring this Deduplication folder online again.
----
Of course this quote implies you know the username as well which from the error message you provided might mean you do not. Both links provided above give a command to show the username however you will still need the password.
If you have the original BEDB (and if BE 15 the exported database encryption key) and the deduplication folder can be attached on the original drive letter to a Backup Exec Server with the original hostname, then you night be able to get back up and running however this is likely to need advanced help and you should probably invest in some support.