I know there are many blog posts similar to this, and I have read them all and as far as I can tell things are setup correctly, but I still get invalid username or password when kicking off the copy job. My setup and procedure is below:
- Server A hosts source database in Domain A
- Server B and C are in a cluster in Domain B. I am log shipping to both of these servers to prep for eventual migration and adding into an Availability Group.
- SQL Server agent accounts are created in AD on both domains as this: Server A: A\sqlagent - Server B and C: B\sqlagent
- As above shows all 3 servers have the same exact username and password with the exception of the domains being different before each one
- Log backups are placed locally on Server A, shared out with full permissions given to the A\sqlagent account.
As far as I am aware, that is all that is needed from a SQL perspective to get cross-domain LS working, however whenever the copy job runs, it fails for "invalid username and password". We have a VPN tunnel between the 2 domains, however no Trust relationship exists.
I am able to path out to the backup share on Server A from Server B and C using the admin login to manually pull the backups over if I want, so I know the tunnel is properly working.
There is mention of using a local network account Here when doing cross domain log shipping instead of a domain login, but I am not sure how to create and use that. Is that created as a different type of account in Active Directory? I already have the A\sqlagent and B\sqlagent created in AD. Does the account need to be created differently to be a local network account? I don't have much experience with AD and accounts.
Is this something that might be caused by network pass-through security? unfortunately I am not finding any helpful information on setting up network passthrough security online. As far as I am aware, this should happen independently of SQL Server, but if anyone has any info about what might be causing this issue, it would be most appreciated.