![\"Backup](\"https:\/\/www.backupassist.com\/app\/uploads\/sites\/3\/2018\/03\/settings-backup-user-identity.jpg\")
<\/p>\nDo you have a Backup User Identity? We’re not talking about the type of backup identity with a fake passport and tickets to Mexico. Rather, the kind you need to perform backup jobs properly.<\/p>\n
Backup jobs, by their very nature, require an account with read access to the data source, and full read-write access to the backup’s destination. In short, the permission to copy what it needs to copy, and transfer it to where it needs to go.<\/p>\n
For many reasons, it’s highly recommended you create a dedicated backup account solely for this purpose. After all, you don’t want to delete someone’s account when they leave your organization and then realize that was being used to perform your backups, right?<\/p>\n
Since it\u2019s a dedicated user account, it makes sense to name it something like \u201cBackup User\u201d to set it apart from your other accounts.<\/p>\n
Regardless of if you create a dedicated backup account or use another one, this account’s permissions will be validated both when the backup user identity is first entered, and whenever the backup job is executed.<\/p>\n
So what happens if you don’t put the account details in, or you enter one with insufficient permissions? The backup will fail (due to not having the read\/write access), and you’ll see an error in the backup report.<\/p>\n
\u2022 You need to make a Windows user account with the access required to the source data and backup destination. This access may also need to take into account domain level access.<\/p>\n
\u2022 For applications like Exchange, Hyper-V, SQL and DNS, you will also need to check the account access required to access the data as documented by Microsoft and Microsoft Technet, and test that the access is sufficient.<\/p>\n
\u2022 You should use a dedicated account and name it something appropriate like \u201cBackup User\u201d.<\/p>\n
\u2022 You will also need to be mindful if the account password is set to expire, the password will need to be updated in BackupAssist before the password expires. If you don’t and it expires, all backup jobs will fail.<\/p>\n
<\/p>\n
You’re almost done! You should test to see your Backup User Identity is properly set up by running a test backup job.<\/p>\n","protected":false},"excerpt":{"rendered":"
Creating a Backup User Identity is important to performing backup jobs with BackupAssist. Here’s how to make sure yours is set up properly.<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[93,634,683,98],"class_list":["post-10500","post","type-post","status-publish","format-standard","hentry","category-support","tag-backup","tag-featured","tag-setup","tag-user-identity"],"yoast_head":"\n