In the years that I work with SharePoint, I have made several farm backups. Usually I can make use of a backup location in the same Active Directory forest as that from the SharePoint server. For a few times the backup location was located in another Active Directory forest where there was a trust between the Active Directory forests.
The previous paragraph will be the case for the most of you. But what if you are in a situation where you have no choice than to use a backup location in another AD forest without any forest trusts.
To make it easier to understand I will talk about SharePoint.com forest where the SharePoint servers are located and the Backup.com forest where the backup server is located.
On the backup server a share has been made available for the SharePoint backup. When you access the shared location from the SharePoint.com forest, you will be prompted for your credentials.
But when you start a SharePoint backup, the current account needs to have access to the shared location, otherwise you will get access denied errors.
Working with mapped drives will not help you out, because SharePoint uses multiple accounts to transfer the data to the backup location (SharePoint Farm Admin Account and SQL service account).
When I was logged on with another user to the SharePoint server, I noticed that my credentials were not needed to gain access to the shared location.
After some investigation on the backup server, I discovered that the account I used on the SharePoint.com forest, was also defined as a local user on the backup server with the same password.
For certainty, I created a new local user on the backup server that also exists in the SharePoint.com forest with the same username and password. It turned out that this user also gained access to the shared location without being prompted for his credentials.
The solution to back up the SharePoint.com farm to the share in the Backup.com forest, is to create the same user that initiates the backup (SharePoint Farm Admin) and SQL Service account as a local user on the backup server (with the same passwords). Give these accounts read and write access on the shared location.
Restart your backup, normally the backup completes without any access denied errors.
If you still got any access denied errors, check the application logs to see which user does not have access to the shared location. Do the same process as described above for this user and restart the backup.