To do the latter, SQL Server must be running under a domain account (not a local one, or system). Once that is in place, you can specify the backup location to be a network drive.
For database content movement from one DB to another, you could use something like replication.|||To copy the backup to another server just in case the server crashes.|||Basically, once SQL server is running under a domain account, you can specify the backup location to be a network resource.
Depending on the backup type, it should be fairly straight forward. I use a file, so I would just specify the file name to be on the file share. You do have to use a UNC path.
There is another method, but I have not used it. Here's a google article about how you can do it:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&safe=off&selm=VA.000047b5.02137fee%40compuserve.com&rnum=5
Hope this helps.|||Thanks
No comments:
Post a Comment