Backup a Database to a Remove Location

0 views
Skip to first unread message

Fábio Pinheiro

unread,
Oct 25, 2006, 1:59:34 PM10/25/06
to SQL-S...@googlegroups.com
How to backup a database to a remote network connection in a job ?
I Tried to use "\\server\sharedfolder" and don't worked.

tks

Fábio Pinheiro

Sam Densmore

unread,
Oct 25, 2006, 2:01:30 PM10/25/06
to SQL-S...@googlegroups.com
I use the ip address, or map a drive from the server...

Fábio Pinheiro

unread,
Oct 25, 2006, 2:17:41 PM10/25/06
to SQL-S...@googlegroups.com
Don't work with me.

appear this message.

Unable to verify the existence of the backup file location........

Sam Densmore escreveu:

Sam Densmore

unread,
Oct 25, 2006, 2:20:48 PM10/25/06
to SQL-S...@googlegroups.com
Verify the server has the appropriate access rights....

Fábio Pinheiro

unread,
Oct 25, 2006, 3:23:04 PM10/25/06
to SQL-S...@googlegroups.com
well,

when I access the mapped drive from Windows Explorer, it's ok, but I see
the error on the log of sql server and has the error for user or pasword
invalid.

What I do ?


Sam Densmore escreveu:

Jason Cumberland

unread,
Oct 25, 2006, 3:29:12 PM10/25/06
to SQL-S...@googlegroups.com
This is probably because the SQL Server Agent service account does not have permissions to the share.  Grant access rights to your remote share to your service account and then try it again.  If you are using LocalSystem you will need to change this to a domain account instead.  Since you are able to access the share you could theoretically use your account to do this, but I would advise against it.  You might also have a look at the job to see what account the job is executing under.
 
--
Jason
:wq

Janice

unread,
Oct 26, 2006, 9:47:30 AM10/26/06
to SQL Server
I backup to a Network Share and you definitely need to be starting the
SQL Server Agent with a Domain account that has permissions to the
Share. Then just Backup to the UNC path of the Share and you should be
good to go.

On Oct 25, 3:29 pm, "Jason Cumberland" <jcumberl...@gmail.com> wrote:
> This is probably because the SQL Server Agent service account does not have
> permissions to the share. Grant access rights to your remote share to your
> service account and then try it again. If you are using LocalSystem you
> will need to change this to a domain account instead. Since you are able to
> access the share you could theoretically use your account to do this, but I
> would advise against it. You might also have a look at the job to see what
> account the job is executing under.
>

> :wq- Hide quoted text -- Show quoted text -

Reply all
Reply to author
Forward
0 new messages