Issues with working out where a incorrect username is showing up

[aduxorth]

Hi there,
Need a bit of help trying to work out where an invalid user is showing up in v12. Case number is 05940263
If I manually run backups it works, but automated backups fail.

Code: Select all

[03.04.2023 22:15:16.027] <177> Info                 [SatelliteProcessClient]Check if Process has been initialized (attempt 7): SUNRISE_SYSTEM_PowerShell_SHS-DC-Veeam_412c9936-0fba-49f7-80ef-c151253e995f 

I have no idea where this sunrise\system is coming from. It started before we changed from 'Local System Account'. Credential tests pass successfully.
Its not a valid domain account. All the veeam services have been changed to a new local admin account with the log on account, with the same result.
Does anyone have pointers on where to look?
Thanks
Andrew

#MOD: Log removed, please don't post Logs to the forum

[Mildur]

Hi Andrew

Welcome to the forum.
I removed Log files from your post. Posting Log files is against our forum rules.

Thanks for the case number.
Is it possible, that you are leveraging job or guest scripts in your backup job?
Please check the guest os credentials configured in this step:
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Our recommendation is to run Veeam Services as LOCAL SYSTEM. A dedicated Service Account may be required if you need to connect to a remote SQL with domain credentials running in a remote domain.

Best,
Fabian

[aduxorth]

Hi Fabian,
Thanks for the reply, sorry about the logs.
We are not using any scripting with any of our veeam backup hosts, either before or after the backup.
I have re-entered the admin creds as per that link, which was mentioned in the support reply, and they all pass a 'test now' for connectivity and creds check.
It doesn't matter if it is the system account or a local admin account.
The reply from the support case suggested using a local admin account instead.
I still see the sunrise\system account in the veeam logs, when they fail.

It really has me stumped.

[Mildur]

Hi Andrew

I have reviewed the case. But it was closed because of no response for more than 2 weeks.
My advice is to start a new case. You can reference the old one. If you have checked every credential in Veeam, only support can help you solve this problem.
Places to Check:
- Job Guest OS Credentials
- vSphere/HyperV credentials

Best,
Fabian

[aduxorth]

OK, no worries.
Thanks for your time.