Standalone backup agents for Linux, Mac, AIX & Solaris workloads on-premises or in the public cloud
Post Reply
sdenman
Lurker
Posts: 1
Liked: never
Joined: Dec 11, 2018 7:55 pm
Full Name: Scot Denman
Contact:

a space is being added to backup location

Post by sdenman »

Testing out Veeam for Linux, I made a full server backup job. The job is failing I believe due to it putting a space in the path. I specified /media/nfs/Veeam as the target. The application is adding the path with a space in it. The job fails with the following. Any advise?

Code: Select all

[11.12.2018 11:45:59] <140175303616256> lpbcore| ERR |Input/output error
[11.12.2018 11:45:59] <140175303616256> lpbcore| >>  |Failed to lock file [/media/nfs/Veeam/db3-p DB-3/DB3_2018-12-11T114544.vbk].
[11.12.2018 11:45:59] <140175303616256> lpbcore| >>  |--tr:Failed to open storage for read/write access. Storage: [/media/nfs/Veeam/db3-p DB-3/DB3_2018-12-11T114544.vbk].
[11.12.2018 11:45:59] <140175303616256> lpbcore| >>  |--tr:Failed to upgrade/fix the storage [/media/nfs/Veeam/db3-p DB-3/DB3_2018-12-11T114544.vbk].
[11.12.2018 11:45:59] <140175303616256> lpbcore| >>  |--tr:Client failed to process the command. Command: [prepStorageForWriteEx].
[11.12.2018 11:45:59] <140175303616256> lpbcore| >>  |--tr:event:3:
[11.12.2018 11:45:59] <140175303616256> lpbcore| >>  |--tr:Backup client has failed to execute command.
[11.12.2018 11:45:59] <140175303616256> lpbcore| >>  |--tr:Failed to prepare backup storage file.
[11.12.2018 11:45:59] <140175303616256> lpbcore| >>  |Backup job has failed.
[11.12.2018 11:45:59] <140175303616256> lpbcore| >>  |An exception was thrown from thread [140175303616256].
[11.12.2018 11:45:59] <140175349348224>        |   Closing socket device.
[11.12.2018 11:45:59] <140175349348224> lpbcore| LpbManSession: Processing commands. ok.
[11.12.2018 11:45:59] <140175292241664>        | Thread finished. Role: 'free space watcher'.
[11.12.2018 11:45:59] <140175349348224>        | Closing socket device.
[11.12.2018 11:45:59] <140175303616256> lpbcore| JOB STATUS: FAILED.
[11.12.2018 11:45:59] <140175303616256>        | Thread finished. Role: 'Volume backup job execution'.
[11.12.2018 11:45:59] <140175349348224>        | Closing socket device.
[11.12.2018 11:45:59] <140175349348224>        | Closing socket device.
[11.12.2018 11:45:59] <140175349348224> lpbman | Application session has been finished.
wishr
Veteran
Posts: 3077
Liked: 453 times
Joined: Aug 07, 2018 3:11 pm
Full Name: Fedor Maslov
Contact:

Re: a space is being added to backup location

Post by wishr »

Hi Scott,

Welcome to Veeam community forums and thank you for posting your question.

Please note, that according to Veeam forum rules, you should include support case ID when posting about any technical issue, as requested when you click the "New topic" button. Please post your support case ID once you get it in the original post in this thread, we'll keep an eye on it.

Thanks,
Fedor
PTide
Product Manager
Posts: 6405
Liked: 720 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: a space is being added to backup location

Post by PTide »

Hi,
Testing out Veeam for Linux, I made a full server backup job. The job is failing I believe due to it putting a space in the path. I specified /media/nfs/Veeam as the target. The application is adding the path with a space in it. The job fails with the following. Any advise?
Right, the application creates a directory named as <"hostname" + " " + "jobname"> on the target share. That is, the space is added by design, that has been tested and should not cause issues.

Did you configure the NFS target from the UI by choosing "Network" at the "Destination" step, or the share is just mounted to the local directory manually? If the latter, then please check if the error persists if you configure the share from UI.

The reason why I ask you to do that, is that during NFS configuration via UI the application checks if it has enough permissions on the share.

Thanks!
Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests