Quite Often DBA’s use third party tools to implement mirroring solutions. Once solution is provided by Double take. I remember when I set up manual mirroring solution between sql servers using double take. While I was testing this software intially in our test~staging environments I ran into an interesting situation. When running full/transaction log backup jobs/any jobs based of maintenance plans the jobs run fine on source server but after a failover is implemented the jobs fail on the target. The error I received was:
‘Login failed for user ‘username’. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452)’
Interestingly, this login is a system administrator and also a member of administrators group on both source and target servers.
After spending almost a couple of hours on this I figured out that the target server required an alias from the source server. Here is how I configured it.
1) On the target server. Go to Sql server configuration Manager
2) Expand the SQL Native Client 10.0 Configuration
3) Right click–> New Alias
In the above screenshot I left the Alias Name to remain as the name of the source server and the port no: 1433 and the Server value was the name of target server.
Hope this helps