Backup failed 'The username or password is incorrect'

[shlomia]

Hi,

I'm using Veeam Backup & Replication 8.0
I have SMB shared folder on linux OpenMediaVault server.
I configured the shared folder to work with out credentials, I allowed guest connections so everyone can just open the shared path.
Now, I run my backup with the shared folder destination, and I receive this error:

Code: Select all

14/05/2017 13:37:28 :: Error: The user name or password is incorrect.
Cannot create folder. Folder path: [\\192.168.32.100\BackUp\VeeamBackup].
--tr:FC: Failed to create directory. Directory path: [\\192.168.32.100\BackUp\VeeamBackup].
--tr:Failed to call DoRpc. CmdName: [FcCreateDir].
The user name or password is incorrect.
Cannot create folder. Folder path: [\\192.168.32.100\BackUp\VeeamBackup].

[foggy]

Hi Shlomi, am I understanding right that you were able to add the location to Veeam B&R as CIFS repository, however, getting an error during the backup job? Does the account specified in the job also has sufficient rights to write into that folder?

[mark.just.mark]

Hi,

I'm getting the same problem.
Veeam B&R 9.5.0.1038
vSphere & ESXi 5.5
Backup server is Win 2016 VM
Repository is CIFS share on Synology 1817+, local account + password
Backups were working fine, now they keep failing with:

Code: Select all

25/10/2017 9:20:19 PM :: Processing Yorick Error: The user name or password is incorrect.
Failed to backup text locally. Backup: [VBK: 'veeamfs:-1:4e4bde26-6edc-4e27-8b61-3bedab2129ce (vm-61)\summary.xml@\\p-nas-01\veeambck\Temp\TempD2017-10-25T212016.vbk'].
Agent failed to process method {DataTransfer.BackupText}.
Agent failed to process method {DataTransfer.BackupText}.

And yet, the Configuration Backup (to the same repository) works fine.

Created a new backup with a single VM, and get the same error.
Connected to the share from windows with the username/password just fine.

[mark.just.mark]

Another data point - successfully restored a previous file from the failing backup.

[PTide]

Hi,

What happens if you go to the repository settings and try to go through the wizard once again?

Thanks

[mark.just.mark]

Ran through the repository wizard again.

On the way through, clicked Populate - it detected the total and available space.
Made a change (turned off NFSRecover thingy) just to make sure it had something to update.
Clicked Apply - all green ticks

[PTide]

So, does the backups work now? If not then I recommend you to contact our support team, so they can take a closer look at the setup, and post your case ID.

Thank you

[mark.just.mark]

No, it still did the same thing.
Updated the account that authenticates to the NAS.
Changed it from just Username to NasHostName\Username (same password)
Backups then started working.

[damago1]

This is definitely a bug in Veeam backup. The problem is probably caused by inconsistency in using CIFS libraries by Veeam.

I have pin-pointed the bug. I can always replicate this bug. I have one server that can be reached by WINS name \\SZUFLADA\ or can be reached by DNS name \\szuflada.mycompany.pl\ and:

- when I do enter the path (backup target path):
\\szuflada.mycompany.pl\backups\my_machine
than:
- in the wizard I can enter name and password, and it is accepted, but when I start the actual job it is claiming bad username / password and backup job fails. What's funny: the folder for backup is created by veeam, it is only empty.

- when I do enter the path as:
\\szuflada\backups\my_machine

it magically works.

[veremin]

Do you mind opening a ticket and providing our support team with the results of your investigation? If confirmed, the issue will be escalated to R&D and be fixed later on. Thanks.

[bhurrell@emond.ca]

Thank you so much for this! I've been banging my head against this for two hours with it making no sense. I was able to access everything through file explorer on the server being backed up. I even opened the agent and edited the job locally (all greyed out since it comes from the Veeam server) and was able to click the "populate" beside space available and get a response. But still the job failed with incorrect username/password every time.

When I saw your post, I went back to the veeam server and altered the credential's used in the job from ".\admin" to "<NAS Name>\admin" and magically it all started working!

Thanks!