Backup device

Hi all,
I tried to create the new backup device with UNC path on the remote server
\\remoteserver\share on the sql server. But, I got "can not verify the
path" message and I have no problem to access the share through the sql
server. I checked the share and file security on the share and file and they
are fine.
I can not verify why I can not create UNC backup device on this sql server.
(windows 2003 R2 SP2 and sql 2000)
Can anyone help?
Try using sp_addumpdevice directly. It might just be the GUI which try to "assist" you.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"John" <John@.discussions.microsoft.com> wrote in message
news:75486005-3FAB-499B-9C38-7C128149BFF9@.microsoft.com...
> Hi all,
> I tried to create the new backup device with UNC path on the remote server
> \\remoteserver\share on the sql server. But, I got "can not verify the
> path" message and I have no problem to access the share through the sql
> server. I checked the share and file security on the share and file and they
> are fine.
> I can not verify why I can not create UNC backup device on this sql server.
> (windows 2003 R2 SP2 and sql 2000)
> Can anyone help?
|||> I have no problem to access the share through the sql
> server.
How did you access the share through the SQL instance?
Linchi
"John" wrote:

> Hi all,
> I tried to create the new backup device with UNC path on the remote server
> \\remoteserver\share on the sql server. But, I got "can not verify the
> path" message and I have no problem to access the share through the sql
> server. I checked the share and file security on the share and file and they
> are fine.
> I can not verify why I can not create UNC backup device on this sql server.
> (windows 2003 R2 SP2 and sql 2000)
> Can anyone help?

Backup Device

I am trying to add a backup device to SQL that will use our NAS. When I enter
the UNC \\ProCom-SERVER\BACKUP\DISK.BAK for the file location I get a message
that SQL Server can not verify the existenance of the backup file location.
The path \\PROCOM-SERVER\BACKUP exist and I use it for other backup files.
The SQL Server is a stand alone server and is not a member of a domain and
neither is the NAS, this is in a peer to peer workgroup network. I have
applied service pack 4 as well.
Any help will be appreciated.
Does the account that SQL Server is running under have rights to that share
on the NAS?
Andrew J. Kelly SQL MVP
"ProCom" <ProCom@.discussions.microsoft.com> wrote in message
news:5FB2ABE4-6012-46AF-910C-C375DA6D6ABA@.microsoft.com...
>I am trying to add a backup device to SQL that will use our NAS. When I
>enter
> the UNC \\ProCom-SERVER\BACKUP\DISK.BAK for the file location I get a
> message
> that SQL Server can not verify the existenance of the backup file
> location.
> The path \\PROCOM-SERVER\BACKUP exist and I use it for other backup files.
> The SQL Server is a stand alone server and is not a member of a domain and
> neither is the NAS, this is in a peer to peer workgroup network. I have
> applied service pack 4 as well.
>
> Any help will be appreciated.
>

Backup Device

I am trying to add a backup device to SQL that will use our NAS. When I ente
r
the UNC \\ProCom-SERVER\BACKUP\DISK.BAK for the file location I get a messag
e
that SQL Server can not verify the existenance of the backup file location.
The path \\PROCOM-SERVER\BACKUP exist and I use it for other backup files.
The SQL Server is a stand alone server and is not a member of a domain and
neither is the NAS, this is in a peer to peer workgroup network. I have
applied service pack 4 as well.
Any help will be appreciated.Does the account that SQL Server is running under have rights to that share
on the NAS?
Andrew J. Kelly SQL MVP
"ProCom" <ProCom@.discussions.microsoft.com> wrote in message
news:5FB2ABE4-6012-46AF-910C-C375DA6D6ABA@.microsoft.com...
>I am trying to add a backup device to SQL that will use our NAS. When I
>enter
> the UNC \\ProCom-SERVER\BACKUP\DISK.BAK for the file location I get a
> message
> that SQL Server can not verify the existenance of the backup file
> location.
> The path \\PROCOM-SERVER\BACKUP exist and I use it for other backup files.
> The SQL Server is a stand alone server and is not a member of a domain and
> neither is the NAS, this is in a peer to peer workgroup network. I have
> applied service pack 4 as well.
>
> Any help will be appreciated.
>

Backup device

Hi all,
I tried to create the new backup device with UNC path on the remote server
\\remoteserver\share on the sql server. But, I got "can not verify the
path" message and I have no problem to access the share through the sql
server. I checked the share and file security on the share and file and they
are fine.
I can not verify why I can not create UNC backup device on this sql server.
(windows 2003 R2 SP2 and sql 2000)
Can anyone help?Try using sp_addumpdevice directly. It might just be the GUI which try to "assist" you.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"John" <John@.discussions.microsoft.com> wrote in message
news:75486005-3FAB-499B-9C38-7C128149BFF9@.microsoft.com...
> Hi all,
> I tried to create the new backup device with UNC path on the remote server
> \\remoteserver\share on the sql server. But, I got "can not verify the
> path" message and I have no problem to access the share through the sql
> server. I checked the share and file security on the share and file and they
> are fine.
> I can not verify why I can not create UNC backup device on this sql server.
> (windows 2003 R2 SP2 and sql 2000)
> Can anyone help?|||> I have no problem to access the share through the sql
> server.
How did you access the share through the SQL instance?
Linchi
"John" wrote:
> Hi all,
> I tried to create the new backup device with UNC path on the remote server
> \\remoteserver\share on the sql server. But, I got "can not verify the
> path" message and I have no problem to access the share through the sql
> server. I checked the share and file security on the share and file and they
> are fine.
> I can not verify why I can not create UNC backup device on this sql server.
> (windows 2003 R2 SP2 and sql 2000)
> Can anyone help?sql

Backup Device

I am trying to add a backup device to SQL that will use our NAS. When I enter
the UNC \\ProCom-SERVER\BACKUP\DISK.BAK for the file location I get a message
that SQL Server can not verify the existenance of the backup file location.
The path \\PROCOM-SERVER\BACKUP exist and I use it for other backup files.
The SQL Server is a stand alone server and is not a member of a domain and
neither is the NAS, this is in a peer to peer workgroup network. I have
applied service pack 4 as well.
Any help will be appreciated.Does the account that SQL Server is running under have rights to that share
on the NAS?
--
Andrew J. Kelly SQL MVP
"ProCom" <ProCom@.discussions.microsoft.com> wrote in message
news:5FB2ABE4-6012-46AF-910C-C375DA6D6ABA@.microsoft.com...
>I am trying to add a backup device to SQL that will use our NAS. When I
>enter
> the UNC \\ProCom-SERVER\BACKUP\DISK.BAK for the file location I get a
> message
> that SQL Server can not verify the existenance of the backup file
> location.
> The path \\PROCOM-SERVER\BACKUP exist and I use it for other backup files.
> The SQL Server is a stand alone server and is not a member of a domain and
> neither is the NAS, this is in a peer to peer workgroup network. I have
> applied service pack 4 as well.
>
> Any help will be appreciated.
>

backing up to network share issue.

Hi,
As mentioned in a previous post, I am trying to backup to a network drive. When I add the dump device using the unc and try to backup, I get the following error message "cannot open backup device. Device error or device off-line.." So I did research on
this error and found out a MS kb which states that this might be happening if I do not have write access to that drive. Now I do have write access there but I know it has something to do with SQL Server trying to write to that shared drive in disguise of
local account instead of me.. (as account). Now, another article here http://www.winnetmag.com/Article/Art...025/14025.html describes what needs to be done but the problem is that I can do all this at my office. But we are creating shrink wrapped
app using MSDE and we will be providing a simple user interface to the client to do backup/restore. So what should I tell my clients or even best what should I do so that the backups to the network share work seemlessly.
The quest is unsatiable!!
This is really a windows issue, not a SQL Server issue. Every piece of software runs under a user account in
Windows (NT). And every user who accesses a resource (like a share) need permissions to that resource. If the
software (user) - SQL Server in this case - doesn't have access to the share, then Windows will not allow
access. You have to make sure that SQL Server is using an account that has permissions on the share in
question.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"whynot" <anonymous@.discussions.microsoft.com> wrote in message
news:92D21681-63A8-40DD-8C86-583DA99F27FB@.microsoft.com...
> Hi,
> As mentioned in a previous post, I am trying to backup to a network drive. When I add the dump device using
the unc and try to backup, I get the following error message "cannot open backup device. Device error or
device off-line.." So I did research on this error and found out a MS kb which states that this might be
happening if I do not have write access to that drive. Now I do have write access there but I know it has
something to do with SQL Server trying to write to that shared drive in disguise of local account instead of
me.. (as account). Now, another article here http://www.winnetmag.com/Article/Art...025/14025.html
describes what needs to be done but the problem is that I can do all this at my office. But we are creating
shrink wrapped app using MSDE and we will be providing a simple user interface to the client to do
backup/restore. So what should I tell my clients or even best what should I do so that the backups to the
network share work seemlessly.
> The quest is unsatiable!!

Backing up to a UNC path versus a local drive doesn't act the same way

Hi
I have just noticed a difference in how BACKUP works when I back up to a
local drive versu when I do it to a UNC path.
When I run the backup to a local drive, I can see that the .bak file gets
created, but then stays a 0 Kb until the backup is finished. When it's
finished, the .bak file is then being updated.
If I then run the same backup to the same location, but specify the location
as e.g. '\\Myserver\D$\MyBackupFolder\MybackupFile.bak' it acts differently.
Now the file id being updated on the fly every 3-4 seconds. I also noticed
that the latter takes significantly longer to complete the backup.
I assume that there's a reason for this difference so does any of you know
this reason? I have tried to look around so see if I could find something
that describes this but with no luck. Not that it matters, but I'm just
curious...:-).
Regards
SteenHi
With UNC paths, backup up to the local machine, the traffic has to go to the
network re-director, down the TCP/IP stack, get turned around when it finds
the host, and go up the stack again. Totally expected.
File access on networks, compared to local disk access is very different at
API level.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Steen Persson" wrote:
> Hi
> I have just noticed a difference in how BACKUP works when I back up to a
> local drive versu when I do it to a UNC path.
> When I run the backup to a local drive, I can see that the .bak file gets
> created, but then stays a 0 Kb until the backup is finished. When it's
> finished, the .bak file is then being updated.
> If I then run the same backup to the same location, but specify the location
> as e.g. '\\Myserver\D$\MyBackupFolder\MybackupFile.bak' it acts differently.
> Now the file id being updated on the fly every 3-4 seconds. I also noticed
> that the latter takes significantly longer to complete the backup.
> I assume that there's a reason for this difference so does any of you know
> this reason? I have tried to look around so see if I could find something
> that describes this but with no luck. Not that it matters, but I'm just
> curious...:-).
> Regards
> Steen
>
>|||Mike Epprecht (SQL MVP) wrote:
> Hi
> With UNC paths, backup up to the local machine, the traffic has to go to the
> network re-director, down the TCP/IP stack, get turned around when it finds
> the host, and go up the stack again. Totally expected.
> File access on networks, compared to local disk access is very different at
> API level.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Steen Persson" wrote:
>
>>Hi
>>I have just noticed a difference in how BACKUP works when I back up to a
>>local drive versu when I do it to a UNC path.
>>When I run the backup to a local drive, I can see that the .bak file gets
>>created, but then stays a 0 Kb until the backup is finished. When it's
>>finished, the .bak file is then being updated.
>>If I then run the same backup to the same location, but specify the location
>>as e.g. '\\Myserver\D$\MyBackupFolder\MybackupFile.bak' it acts differently.
>>Now the file id being updated on the fly every 3-4 seconds. I also noticed
>>that the latter takes significantly longer to complete the backup.
>>I assume that there's a reason for this difference so does any of you know
>>this reason? I have tried to look around so see if I could find something
>>that describes this but with no luck. Not that it matters, but I'm just
>>curious...:-).
>>Regards
>>Steen
>>
>>
Thanks for the input Mike.
I know that using a UNC path involves the network, and therefore it's
also understandable that it takes longer time to do the backup.
Do you know why the file updates differently with the two scenarios? I'd
assume that it's due to the differnet ways the file is being
addressed, but do you know the correct reason?
Regards
Steen