https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2I0MTIwIiwiaGFzaCI6IjlmMDBjMGRkLWViNzAtNDgzZC1hMzFhLTNmZTY1OTQ2YjBiOSJ9
1-800-691-1991 | 9am - 8pm ET
EN

SMB credentials cached by macOS

Challenge

After you change credentials for the SMB share in the backup policy settings and re-apply the backup policy, macOS may still use obsolete credentials to connect to the SMB share. As a result, if incorrect credentials are specified in the backup policy settings, the policy application and backup will still be successful until the Mac computer reboot.

Cause

MacOS saves credentials for the SMB share in a cache. If credentials specified in the backup policy settings are incorrect, macOS may failover to cached credentials and use cached credentials to connect to the SMB share.

Solution

After you change credentials for the SMB share in backup policy settings, it is recommended to reboot the Mac computer. After that, macOS will refresh the cache and apply updated credentials to connect to the SMB share.

More information

KB ID: 4120
Product: Veeam Agent for Mac 1.0
Published: 2021-03-02
Last Modified: 2021-03-03
Please rate how helpful this article was to you:
3.3 out of 5 based on 3 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.