In many cases, you will need to run a backup job under a specific Windows account. We recommend you do so when:
•Connecting to SQL Server using Windows authentication
•Adding a Local or Network Folder backup destination that requires network access
•You receive authentication failure error messages when a backup job executes
By default, SQL Backup Master executes these functions without impersonation, in which case they will run as the user assigned to the SQL Backup Master system service (which, by default, will be the "Local System" account). Configuring this option causes SQL Backup Master to create an impersonation context within which the backup job will execute. The backup thread will "log on" as the specified Windows user prior to running the following tasks:
•Connecting to SQL Server in order to generate database backup files
•Accessing the temporary backup folder
•Sending backups to destinations
However, you can use these settings to ensure that these backup steps execution within the context of some other Windows account. For example, setting the Windows account as "domain\johndoe" will cause the back up job to connect to SQL Server, create and zip database backup files, and upload backup files to their destinations as this user. If the backup destinations include a local or network folder, the user account will need proper write permissions.
Note: When specifying a domain account, enter the account name in the form of "domain\username".
Important: If you are attempting to back up remote databases, you will typically need to use these features to execute the backup job under a Windows user with the correct permissions (such as a domain administrator account). For more information, see the remote backups help topic.