Hi Ianh,
It's Stuart here and I'm a level 3 technician for BackupAssist. I came across this forum and thought I may be able to help contribute.
Looking over the details this is my current understanding of your configuration:
1 Server running Server 2008 R2 which has BackupAssist (unsure exact BA version).
1 Server running Exchange 2010
Both systems are running on the same domain (I'm not 100% sure on this however - can you confirm for me?).
If both systems are running on the same domain; then you don't need to create a 'local' user at all. By the sounds of it; you're able to detect the Exchange server through BackupAssist and select which mailboxes you wish to back up. If you required the local/domain matching accounts then you wouldn't have made it that far.
The reason for the local user and a domain user is when you're attempting to backup Exchange mailboxes from a Hyper-V Host (physical) machine while your Exchange server is within a Hyper-V guest (virtual). Microsoft recommended best practice is that the host machine should be on the separate work-group and not the same domain as the guest machines. MS MVP Philip Elder indicates this at social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/b69d782d-9dad-4168-b1af-2efb52629b6e/.
To be able to authenticate to the domain from the host we've found that creating a local/work-group account on the Host and a Domain account on the guests with exactly the same username and password allow for a pass-through effect.
Now I do notice that you said the manual export of the mailboxes worked; however the backup doesn't work when the scheduled backup runs.
Have you tried being logged in as the same user when a scheduled backup runs as you were when you ran the manual export?
It could be something to do with permissions on the account running the BackupAssist service. I've seen in the past that people have had successful scheduled backups when logged in as a user; however if they log out of Windows and leave the machine alone while the exact same backup runs and encounter errors.
This would indicate a permissions issue with the local system account (which by default is used to run the BackupAssist service). I'm not a permissions guru by any stretch; however I believe that sometimes the local system account binds itself to the user currently logged in - which maybe allowing greater access in your case.
Also make sure that you're running the latest update for the BackupAssist version your running (either v5.4.8 or v6.2.8). They're located on the BackupAssist website.
Apologies as well for not posting links - apparently I need to post a few more times before I can do this.
Give these suggestion a try Ian and let me know the result.
Thanks,
Stuart
