SQL-Server 2005 default trace log file not inherits directory permissions

If you do not have a domain, you can set up the same user (name) on all machines, and then use the local user to run SQL Server.

For example, on ServerA (which has SQL Server running), I can set up the user MySQLServerUser as a local user. Use Configuration Manager to set this as the account to run SQL Server.

Then on ServerB, which is where I want to send the backups, I set up the same account (MySQLServerUser) with the same password.

Since Windows will pass this through as the first user/password, it should authenticate.

Note that backups across the network are not recommended. The SQL backup process is intolerant of network delays. Anything that hiccups will fail the backup. And it will likely happen when your disks fail. Back up locally, copy to the remote machine. Copies will retry themselves automatically.

Kind of a brute approach, but have you tried uninstalling and re-installing SQL Server? If it won't let you, you might try these steps.

As another option, you could try these steps to fix the local account SID issue, but it looks like kind of a pain.