[Resolved] Backup Metadata working, data/files not starting

[alie2n]

Hi,
I just setup a new instance of Veeam Backup for Salesforce. The setup went smooth and the backup starts. But only the Metadata subjob finishes. The files or data subjob never start (at least not in the last hour) and still shows "no data.." in the job details page.

The logfiles do not show any progress besides that apps being started. No errors are recorded in the logfiles as far as I can tell.

Is this normal and the backup needs time to start? Or did I miss something here?


Cheers,

[alie2n]

After I found some warnings in the logs regarding postgresql-14 I now reinstalled the whole server from scratch. But still the same problem persists. Metadata backup finish successfully, but Data backups are not starting.

[Mildur]

Hello,

That sounds like a technical issue. We cannot investigate such issues through a forum topic.
Please provide a support case ID for this issue, as requested when you click New Topic. Without case number, the topic will eventually be deleted by moderators.

Please contact our customer support team and provide them with a current log collection:
https://helpcenter.veeam.com/docs/backu ... pport-case

Best regards,
Fabian

PS: support can only help if you upload logs: https://helpcenter.veeam.com/docs/backu ... oduct-logs

[MIvanov]

Hello @alie2n ,
It would be better indeed to open a case so that the larger team could review your case.

Just to confirm, data and file jobs don't show up in sessions at all or sessions are started but without progress?
We've seen rarely that some orgs can be very slow on responding to metadata describe requests. In that case, the sessions are there but without visible progress. Support team can help you resolve this one.

[alie2n]

Hi,
as I don't have a license as we are still in the evaluation phase. I will try to open a support ticket. But that, as to my understanding, will take a while.

Thanks for all the feedback until now.

@MIvanov: The tasks are there, but no progress is visible.

[alie2n]

Hi,
I just opened the support case #07256236.


Cheers,
Nicki

[guramowski]

Hi,

I've got same issue Is there any knowledge base article about it?

Many thanks,
Greg

[david.domask]

Hi Greg, welcome to the forums.

It's best to open a Support case and let the Veeam Support Team review the situation.

Previous cases pointed to a lack of resources on the management server, and there were improvements once ensuring the system requirements were met: https://helpcenter.veeam.com/docs/backu ... tml?ver=20

You can start with checking this, but if it doesn't help, a support case is the way to go.

[guramowski]

Hi David,

I think I am good on resources . I did not run out of space or RAM.

I've opened support case #07256915.

Many thanks,
Greg

[david.domask]

Got it, thank you for sharing the case number and for including logs. Let's allow the Support Team a bit of time to review the details and develop a plan of action.

[absent]

I've faced the same thing after 2.0 to 2.1 upgrade. It's purely related to lack of vCPUs on the management server. Veeam has always recommended to have 4 vCPUs, but never truly enforced that until version 2.1. So, previously you could be just fine running on 2 vCPUs, not using this version. Solution is to stop a VM, give it at least 4 vCPUs and then run the VM/application/backup policy again. Hope it helps

[alie2n]

Hi absent,
that was the same solution for me in the support case. I wonder why they are enforcing 4 vCPUs as the vm was (and is) idle all the time. Adding 4 vCPU is just a big waste of ressources...

[alie2n]

This thread has a solution. How can I mark it as solved?

[david.domask]

Hi alie2n,

Right now not possible for you to mark it as "resolved", but I've edited the topic title as the solution seems pretty straight forward.