December 5, 2006 at 2:01 pm
Many thanks in advance.
December 5, 2006 at 4:23 pm
If your service account has the access I belive you can use UNC name like '\\servername\c$\test.bak'
OR
Run the backup locally and copy the backup file or FTP it.
MohammedU
Microsoft SQL Server MVP
December 6, 2006 at 3:03 pm
You should definitely run the backup locally and then copy/ftp it to the other server. Your chances of getting a corrupted backup go up exponentially if you do it cross server.
December 6, 2006 at 3:15 pm
If you're going to backup using UNC paths or copying the file, you'll need to have a trust relationship setup between domains. You'll need a Domain Administrator to do this for you.
If you plan to backup locally and then FTP to the other server, make sure you have your FTP session set to Binary.
December 6, 2006 at 3:55 pm
You can copy the backup to another non-trusted domain without a trust. Just make sure the sql server agent account that is running on source is a local user on destination server.
At my job we have two non-trusted domains that are connected by a dedicated T1 Line. I have a Production backup that is copied across T1 and then restored on LAN (non-trusted domains). It's been working great!
December 6, 2006 at 3:57 pm
You can also fire up a VPN connection and use mapped drives instead of a trusted connection.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply