Backing up SQL to a different server

I am trying to send backups of SQL databases and
transaction logs to a different server. I thought it
would work if the UNC name and path were used. So, first
of all, I don't if this is correct. I think it's trying
to do the backup, but the error I am getting
is "BackupDeviceFile::Backup device "\\erlfs1
\sqlbackups\..." failed to create. Operating system error
=5 (Access is denied.)" I have given the Everyone group
full control, and I still get the same error. Does anyone
have recommendations for sending backups to a different
machine?Make sure you are running SQL under a domain-level account and that the
account has permissions to create and write files on the remote location.
Logging in to the console of the SQL server as the service account and
copying files is a good way to test remote file access.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"teresa" <anonymous@.discussions.microsoft.com> wrote in message
news:1454601c3c33c$58da9540$a601280a@.phx.gbl...
> I am trying to send backups of SQL databases and
> transaction logs to a different server. I thought it
> would work if the UNC name and path were used. So, first
> of all, I don't if this is correct. I think it's trying
> to do the backup, but the error I am getting
> is "BackupDeviceFile::Backup device "\\erlfs1
> \sqlbackups\..." failed to create. Operating system error
> =5 (Access is denied.)" I have given the Everyone group
> full control, and I still get the same error. Does anyone
> have recommendations for sending backups to a different
> machine?|||The SQL server is logged in under the domain admin account
and the domain admin has full control on the remote folder
that SQL is trying to back up to. Also, SQL Server Agent
service is started under the domain admin account and the
particular job is owned by the domain admin. I was able
to copy a file from the console to the backup server.
Looking at the event viewer, after a job has failed, one
error says "operating system eror = 5 (access is denied),"
another one says that the job failed and that it was
invoked by user 'sa'. I mention this because I don't
if 'sa' trying to invoke the job is the problem.
>--Original Message--
>Make sure you are running SQL under a domain-level
account and that the
>account has permissions to create and write files on the
remote location.
>Logging in to the console of the SQL server as the
service account and
>copying files is a good way to test remote file access.
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>
>"teresa" <anonymous@.discussions.microsoft.com> wrote in
message
>news:1454601c3c33c$58da9540$a601280a@.phx.gbl...
>> I am trying to send backups of SQL databases and
>> transaction logs to a different server. I thought it
>> would work if the UNC name and path were used. So,
first
>> of all, I don't if this is correct. I think it's trying
>> to do the backup, but the error I am getting
>> is "BackupDeviceFile::Backup device "\\erlfs1
>> \sqlbackups\..." failed to create. Operating system
error
>> =5 (Access is denied.)" I have given the Everyone group
>> full control, and I still get the same error. Does
anyone
>> have recommendations for sending backups to a different
>> machine?
>
>.
>|||Ping the second server from the first using UNC (ping
Servername). If you can not ping, use the IP address (To
find IP...Ipconfig).
Second Check the the 'Domain Admins' group is added
to 'Administrators' group of the second server.
>--Original Message--
>The SQL server is logged in under the domain admin
account
>and the domain admin has full control on the remote
folder
>that SQL is trying to back up to. Also, SQL Server Agent
>service is started under the domain admin account and the
>particular job is owned by the domain admin. I was able
>to copy a file from the console to the backup server.
>Looking at the event viewer, after a job has failed, one
>error says "operating system eror = 5 (access is
denied),"
>another one says that the job failed and that it was
>invoked by user 'sa'. I mention this because I don't
>if 'sa' trying to invoke the job is the problem.
>>--Original Message--
>>Make sure you are running SQL under a domain-level
>account and that the
>>account has permissions to create and write files on the
>remote location.
>>Logging in to the console of the SQL server as the
>service account and
>>copying files is a good way to test remote file access.
>>--
>>Geoff N. Hiten
>>Microsoft SQL Server MVP
>>Senior Database Administrator
>>Careerbuilder.com
>>
>>"teresa" <anonymous@.discussions.microsoft.com> wrote in
>message
>>news:1454601c3c33c$58da9540$a601280a@.phx.gbl...
>> I am trying to send backups of SQL databases and
>> transaction logs to a different server. I thought it
>> would work if the UNC name and path were used. So,
>first
>> of all, I don't if this is correct. I think it's
trying
>> to do the backup, but the error I am getting
>> is "BackupDeviceFile::Backup device "\\erlfs1
>> \sqlbackups\..." failed to create. Operating system
>error
>> =5 (Access is denied.)" I have given the Everyone
group
>> full control, and I still get the same error. Does
>anyone
>> have recommendations for sending backups to a different
>> machine?
>>
>>.
>.
>sql

Backing up Encryption Master Key

Hello,
I have problems backing up the Master key. The message is cannot write into
file 'file path' verify that you have the write permissions. I don't
understand why because I am using user dbo and defaul schema dbo on the
database.
If someone can help me to clarify the permissions part.
Thanks for your help.Make sure the SQL Server service account has write access to the path where
you want to save the file.
Thanks
Laurentiu Cristofor [MSFT]
Software Development Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Car" <Car@.discussions.microsoft.com> wrote in message
news:AF3C125B-D6D3-4304-87F2-C332DD562626@.microsoft.com...
> Hello,
> I have problems backing up the Master key. The message is cannot write
> into
> file 'file path' verify that you have the write permissions. I don't
> understand why because I am using user dbo and defaul schema dbo on the
> database.
> If someone can help me to clarify the permissions part.
> Thanks for your help.|||Well I am not login as sa. I am using windows authentication and the login
user I have is member of the Administrators group on the local computer wher
e
I am trying to save the file containing the backup of the master key.
Thanks for your help anyway.
"Laurentiu Cristofor [MSFT]" wrote:

> Make sure the SQL Server service account has write access to the path wher
e
> you want to save the file.
> Thanks
> --
> Laurentiu Cristofor [MSFT]
> Software Development Engineer
> SQL Server Engine
> http://blogs.msdn.com/lcris/
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Car" <Car@.discussions.microsoft.com> wrote in message
> news:AF3C125B-D6D3-4304-87F2-C332DD562626@.microsoft.com...
>
>|||How you connect and the permissions you have don't matter in this case -
when you go outside the server, you go out with the service account
credentials, not with the credentials you connected to the server.
So, find out what account SQL Server is running as, and make sure that
account has access to the location where you want to save the backup file.
Thanks
Laurentiu Cristofor [MSFT]
Software Development Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Car" <Car@.discussions.microsoft.com> wrote in message
news:DFF1B05E-DE27-4C72-BCE5-16C640CDFCB3@.microsoft.com...[vbcol=seagreen]
> Well I am not login as sa. I am using windows authentication and the
> login
> user I have is member of the Administrators group on the local computer
> where
> I am trying to save the file containing the backup of the master key.
>
> Thanks for your help anyway.
> "Laurentiu Cristofor [MSFT]" wrote:
>|||I got it. I find out that the SQL Server Account I was running does not hav
e
permissions on the Local computer. Now I am running the backup statements a
s
a job under the right account and I have to create another job to restore th
e
backup of the master key into the suscriber database.
Thanks again for your assistance.
"Laurentiu Cristofor [MSFT]" wrote:

> How you connect and the permissions you have don't matter in this case -
> when you go outside the server, you go out with the service account
> credentials, not with the credentials you connected to the server.
> So, find out what account SQL Server is running as, and make sure that
> account has access to the location where you want to save the backup file.
> Thanks
> --
> Laurentiu Cristofor [MSFT]
> Software Development Engineer
> SQL Server Engine
> http://blogs.msdn.com/lcris/
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Car" <Car@.discussions.microsoft.com> wrote in message
> news:DFF1B05E-DE27-4C72-BCE5-16C640CDFCB3@.microsoft.com...
>
>sql

Backing up database over network

I am trying to get my database to backup to a network
path (\\myserver\backup\db.bak) instead of a local path.
But, unfortunately it is not working, I keep the message
that it cannot connect to the device or the device is
offline.
Here is my backup statement
BACKUP DATABASE test
TO DISK = 'c:\temp\test.bak'
WITH FORMAT,
NAME = 'Test Backup'
Any Ideas?The account that sqls erver runs under is the one that is used when backups
occur. So you need to ensure that this account has permissions to the
network share you are attempting to backup to. Chances are the account is
the local admin account which has no domain privileges.
--
Andrew J. Kelly
SQL Server MVP
"Ben Skolmoski" <ben.skolmoski@.imcentric.com> wrote in message
news:02e901c3a581$03d068a0$a601280a@.phx.gbl...
> I am trying to get my database to backup to a network
> path (\\myserver\backup\db.bak) instead of a local path.
> But, unfortunately it is not working, I keep the message
> that it cannot connect to the device or the device is
> offline.
> Here is my backup statement
> BACKUP DATABASE test
> TO DISK = 'c:\temp\test.bak'
> WITH FORMAT,
> NAME = 'Test Backup'
> Any Ideas?|||I have already checked all of that and the account has
full access to my network share.
>--Original Message--
>The account that sqls erver runs under is the one that
is used when backups
>occur. So you need to ensure that this account has
permissions to the
>network share you are attempting to backup to. Chances
are the account is
>the local admin account which has no domain privileges.
>--
>Andrew J. Kelly
>SQL Server MVP
>
>"Ben Skolmoski" <ben.skolmoski@.imcentric.com> wrote in
message
>news:02e901c3a581$03d068a0$a601280a@.phx.gbl...
>> I am trying to get my database to backup to a network
>> path (\\myserver\backup\db.bak) instead of a local
path.
>> But, unfortunately it is not working, I keep the
message
>> that it cannot connect to the device or the device is
>> offline.
>> Here is my backup statement
>> BACKUP DATABASE test
>> TO DISK = 'c:\temp\test.bak'
>> WITH FORMAT,
>> NAME = 'Test Backup'
>> Any Ideas?
>
>.
>|||Ben,
The example you showed was not using UNC and was obviously not the real
code. It helps to show the actual code to alleviate any assumptions or the
possibility of simply a typo that doesn't get relayed with a simpler
example. So I assume from what you state you have logged on to the server
under the account sqls erver is running under and were able to copy a file
with the exact name of the backup to the UNC you want. If not then check to
ensure there isn't already a file with that name that is locked by some
other resource.
--
Andrew J. Kelly
SQL Server MVP
"Ben Skolmoski" <ben.skolmoski@.imcentric.com> wrote in message
news:037301c3a589$687422d0$a601280a@.phx.gbl...
> I have already checked all of that and the account has
> full access to my network share.
>
> >--Original Message--
> >The account that sqls erver runs under is the one that
> is used when backups
> >occur. So you need to ensure that this account has
> permissions to the
> >network share you are attempting to backup to. Chances
> are the account is
> >the local admin account which has no domain privileges.
> >
> >--
> >
> >Andrew J. Kelly
> >SQL Server MVP
> >
> >
> >"Ben Skolmoski" <ben.skolmoski@.imcentric.com> wrote in
> message
> >news:02e901c3a581$03d068a0$a601280a@.phx.gbl...
> >> I am trying to get my database to backup to a network
> >> path (\\myserver\backup\db.bak) instead of a local
> path.
> >> But, unfortunately it is not working, I keep the
> message
> >> that it cannot connect to the device or the device is
> >> offline.
> >>
> >> Here is my backup statement
> >>
> >> BACKUP DATABASE test
> >> TO DISK = 'c:\temp\test.bak'
> >> WITH FORMAT,
> >> NAME = 'Test Backup'
> >>
> >> Any Ideas?
> >
> >
> >.
> >|||If you log on to the SQL Server machine with the SQL Server startup account
can you access the remote share that you are trying to restore to/
Rand
This posting is provided "as is" with no warranties and confers no rights.sql

AWE Memory fix (899761) problems

Hi all,
we have some problem installing the path KB899761 (Fix: Not All Memory
is Available When AWE is Enabled on a Computer Running 32-bit Version
of SQL Server 2000 SP4)
Our scenario is:
1 - we added a third node on an existing cluster
2 - The main differences are that the new node have 64 GB of RAM (the
existing ones have only 8 GB) and the "machine" is 64 bit
3 - On this new server we installed windows 2003 (32 bit) with sql
server 2000 SP4 (with "add node" procedure)
4 - To use all the 64 GB of memory we enabled the AWE feature but
we've seen that we could only use 32 GB. For this reason we've found
out that we need the 899761 patch.
Now we tried to install the patch but it seems that it just work on the
old (32 bit) nodes. If we try to install the patch on the new node (we
have the correct instance up and running) we get the following error:
"this machine does not have a product that matches this installation
package"
On the log file we see:
"No products were found which can be serviced by this package"
At the moment we don't know what to try to solve the problem. (maybe
problem with hardware at 64 bit (core 2 duo) and OS at 32 bit ?)
If someone as any idea it would be fantastic ...
Thanks very much in advance.
Kind regards,
Daniel HubeliHi Daniel
You don't say what edition you are using, but I guess from your combination
it can't be Datacenter!
Windows Server 2003, Enterprise Edition supports 32 GB of physical RAM and
Windows Server 2003, Datacenter Edition supports 64 GB of physical RAM
You will not be taking full advantage of your new hardware by running
mismatched products and you would also need to consider if failing over to
the lower spec machines is actually a viable alternative.
John
"daniel.hubeli@.aduno.ch" wrote:

> Hi all,
> we have some problem installing the path KB899761 (Fix: Not All Memory
> is Available When AWE is Enabled on a Computer Running 32-bit Version
> of SQL Server 2000 SP4)
> Our scenario is:
> 1 - we added a third node on an existing cluster
> 2 - The main differences are that the new node have 64 GB of RAM (the
> existing ones have only 8 GB) and the "machine" is 64 bit
> 3 - On this new server we installed windows 2003 (32 bit) with sql
> server 2000 SP4 (with "add node" procedure)
> 4 - To use all the 64 GB of memory we enabled the AWE feature but
> we've seen that we could only use 32 GB. For this reason we've found
> out that we need the 899761 patch.
> Now we tried to install the patch but it seems that it just work on the
> old (32 bit) nodes. If we try to install the patch on the new node (we
> have the correct instance up and running) we get the following error:
> "this machine does not have a product that matches this installation
> package"
> On the log file we see:
> "No products were found which can be serviced by this package"
> At the moment we don't know what to try to solve the problem. (maybe
> problem with hardware at 64 bit (core 2 duo) and OS at 32 bit ?)
> If someone as any idea it would be fantastic ...
> Thanks very much in advance.
> Kind regards,
> Daniel Hubeli
>

AWE Memory fix (899761) problems

Hi all,
we have some problem installing the path KB899761 (Fix: Not All Memory
is Available When AWE is Enabled on a Computer Running 32-bit Version
of SQL Server 2000 SP4)
Our scenario is:
1 - we added a third node on an existing cluster
2 - The main differences are that the new node have 64 GB of RAM (the
existing ones have only 8 GB) and the "machine" is 64 bit
3 - On this new server we installed windows 2003 (32 bit) with sql
server 2000 SP4 (with "add node" procedure)
4 - To use all the 64 GB of memory we enabled the AWE feature but
we've seen that we could only use 32 GB. For this reason we've found
out that we need the 899761 patch.
Now we tried to install the patch but it seems that it just work on the
old (32 bit) nodes. If we try to install the patch on the new node (we
have the correct instance up and running) we get the following error:
"this machine does not have a product that matches this installation
package"
On the log file we see:
"No products were found which can be serviced by this package"
At the moment we don't know what to try to solve the problem. (maybe
problem with hardware at 64 bit (core 2 duo) and OS at 32 bit ?)
If someone as any idea it would be fantastic ...
Thanks very much in advance.
Kind regards,
Daniel Hubeli
Hi Daniel
You don't say what edition you are using, but I guess from your combination
it can't be Datacenter!
Windows Server 2003, Enterprise Edition supports 32 GB of physical RAM and
Windows Server 2003, Datacenter Edition supports 64 GB of physical RAM
You will not be taking full advantage of your new hardware by running
mismatched products and you would also need to consider if failing over to
the lower spec machines is actually a viable alternative.
John
"daniel.hubeli@.aduno.ch" wrote:

> Hi all,
> we have some problem installing the path KB899761 (Fix: Not All Memory
> is Available When AWE is Enabled on a Computer Running 32-bit Version
> of SQL Server 2000 SP4)
> Our scenario is:
> 1 - we added a third node on an existing cluster
> 2 - The main differences are that the new node have 64 GB of RAM (the
> existing ones have only 8 GB) and the "machine" is 64 bit
> 3 - On this new server we installed windows 2003 (32 bit) with sql
> server 2000 SP4 (with "add node" procedure)
> 4 - To use all the 64 GB of memory we enabled the AWE feature but
> we've seen that we could only use 32 GB. For this reason we've found
> out that we need the 899761 patch.
> Now we tried to install the patch but it seems that it just work on the
> old (32 bit) nodes. If we try to install the patch on the new node (we
> have the correct instance up and running) we get the following error:
> "this machine does not have a product that matches this installation
> package"
> On the log file we see:
> "No products were found which can be serviced by this package"
> At the moment we don't know what to try to solve the problem. (maybe
> problem with hardware at 64 bit (core 2 duo) and OS at 32 bit ?)
> If someone as any idea it would be fantastic ...
> Thanks very much in advance.
> Kind regards,
> Daniel Hubeli
>

AWE Memory fix (899761) problems

Hi all,
we have some problem installing the path KB899761 (Fix: Not All Memory
is Available When AWE is Enabled on a Computer Running 32-bit Version
of SQL Server 2000 SP4)
Our scenario is:
1 - we added a third node on an existing cluster
2 - The main differences are that the new node have 64 GB of RAM (the
existing ones have only 8 GB) and the "machine" is 64 bit
3 - On this new server we installed windows 2003 (32 bit) with sql
server 2000 SP4 (with "add node" procedure)
4 - To use all the 64 GB of memory we enabled the AWE feature but
we've seen that we could only use 32 GB. For this reason we've found
out that we need the 899761 patch.
Now we tried to install the patch but it seems that it just work on the
old (32 bit) nodes. If we try to install the patch on the new node (we
have the correct instance up and running) we get the following error:
"this machine does not have a product that matches this installation
package"
On the log file we see:
"No products were found which can be serviced by this package"
At the moment we don't know what to try to solve the problem. (maybe
problem with hardware at 64 bit (core 2 duo) and OS at 32 bit ?)
If someone as any idea it would be fantastic ...
Thanks very much in advance.
Kind regards,
Daniel HubeliHi Daniel
You don't say what edition you are using, but I guess from your combination
it can't be Datacenter!
Windows Server 2003, Enterprise Edition supports 32 GB of physical RAM and
Windows Server 2003, Datacenter Edition supports 64 GB of physical RAM
You will not be taking full advantage of your new hardware by running
mismatched products and you would also need to consider if failing over to
the lower spec machines is actually a viable alternative.
John
"daniel.hubeli@.aduno.ch" wrote:
> Hi all,
> we have some problem installing the path KB899761 (Fix: Not All Memory
> is Available When AWE is Enabled on a Computer Running 32-bit Version
> of SQL Server 2000 SP4)
> Our scenario is:
> 1 - we added a third node on an existing cluster
> 2 - The main differences are that the new node have 64 GB of RAM (the
> existing ones have only 8 GB) and the "machine" is 64 bit
> 3 - On this new server we installed windows 2003 (32 bit) with sql
> server 2000 SP4 (with "add node" procedure)
> 4 - To use all the 64 GB of memory we enabled the AWE feature but
> we've seen that we could only use 32 GB. For this reason we've found
> out that we need the 899761 patch.
> Now we tried to install the patch but it seems that it just work on the
> old (32 bit) nodes. If we try to install the patch on the new node (we
> have the correct instance up and running) we get the following error:
> "this machine does not have a product that matches this installation
> package"
> On the log file we see:
> "No products were found which can be serviced by this package"
> At the moment we don't know what to try to solve the problem. (maybe
> problem with hardware at 64 bit (core 2 duo) and OS at 32 bit ?)
> If someone as any idea it would be fantastic ...
> Thanks very much in advance.
> Kind regards,
> Daniel Hubeli
>