NOTE: FOR LEGACY SYSTEMS ONLY
Exchange Backup was not running while temp path was on a NAS drive. Normal backups were working fine.
In Windows XP, Windows Server 2003, and earlier versions of Windows, all services run in Session 0 along with applications. According to Microsoft, this situation poses a security risk. That is why in Windows Vista, Windows Server 2008, and later versions of Windows, the operating system isolates services in Session 0 and runs applications in other sessions, so services are protected from attacks that originate in application code.
The RBS Endpoint exchange service is designed to read the permissions from the services panel. Since the service was not running in session 0 (zero) session, it was not able to resolve the permissions to this mapped drive (K:), where K:\ drive was the temp path location assigned for the RBackup Client.
Follow the steps below -
1) Create a new mapped drive letter (M:). The reason for creating this was because actual R: drive was under another share(\\machine3\D$\ExchangeBackup). Need not do it if there is no nesting.
2) Create a new file name called "Exchangeincremental.ini" in Remote Backup folder with the commands to read the permissions of this mapped drive.
Insert the following parameters in this INI file (case sensitive). Example below:
USER=$DomainName$\Administrator (check the root node under 'Active Directory system and users'.)
3) Restart the Endpoint.