Hello,
Could you tell me please if there is something a DBA is supposed to do to
override an operating system error that states the device is offline and the
backups fail? The error is as follows:
BackupDiskFile::CreateMedia: Backup device
'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
system error = 32(The process cannot access the file because it is being used
by another process.).
Note*There was a job running that was doing some db activity, but this
should not prevent a backup from occurring. The job was running from 9:30 PM
to 11:30 PM and the dump starts at 11 PM.
BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEdge] TO
DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
NOFORMAT
How do you override an operating system error if it is possible to be sure
that production dumps are successful? Is there something the DBA can do?
Thanks
Your message is telling you that another process still has a hold of your
file.
You would need to figure out what process has a hold of it. I would go ask
whoever is in charge of putting your backups onto tape if his job is still
running. I used to always have these when my guy was trying to read from my
backup device to put my backup on tape, but I was trying to write to the file
to do a backup.
ChrisR
"Cynthia" wrote:
> Hello,
> Could you tell me please if there is something a DBA is supposed to do to
> override an operating system error that states the device is offline and the
> backups fail? The error is as follows:
> BackupDiskFile::CreateMedia: Backup device
> 'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
> system error = 32(The process cannot access the file because it is being used
> by another process.).
> Note*There was a job running that was doing some db activity, but this
> should not prevent a backup from occurring. The job was running from 9:30 PM
> to 11:30 PM and the dump starts at 11 PM.
> BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEdge] TO
> DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
> NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
> NOFORMAT
> How do you override an operating system error if it is possible to be sure
> that production dumps are successful? Is there something the DBA can do?
> Thanks
>
Showing posts with label device. Show all posts
Showing posts with label device. Show all posts
Wednesday, March 7, 2012
Backups Failing on Production Servers
Hello,
Could you tell me please if there is something a DBA is supposed to do to
override an operating system error that states the device is offline and the
backups fail? The error is as follows:
BackupDiskFile::CreateMedia: Backup device
'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
system error = 32(The process cannot access the file because it is being used
by another process.).
Note*There was a job running that was doing some db activity, but this
should not prevent a backup from occurring. The job was running from 9:30 PM
to 11:30 PM and the dump starts at 11 PM.
BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEdge] TO
DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
NOFORMAT
How do you override an operating system error if it is possible to be sure
that production dumps are successful? Is there something the DBA can do?
ThanksYour message is telling you that another process still has a hold of your
file.
You would need to figure out what process has a hold of it. I would go ask
whoever is in charge of putting your backups onto tape if his job is still
running. I used to always have these when my guy was trying to read from my
backup device to put my backup on tape, but I was trying to write to the file
to do a backup.
--
ChrisR
"Cynthia" wrote:
> Hello,
> Could you tell me please if there is something a DBA is supposed to do to
> override an operating system error that states the device is offline and the
> backups fail? The error is as follows:
> BackupDiskFile::CreateMedia: Backup device
> 'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
> system error = 32(The process cannot access the file because it is being used
> by another process.).
> Note*There was a job running that was doing some db activity, but this
> should not prevent a backup from occurring. The job was running from 9:30 PM
> to 11:30 PM and the dump starts at 11 PM.
> BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEdge] TO
> DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
> NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
> NOFORMAT
> How do you override an operating system error if it is possible to be sure
> that production dumps are successful? Is there something the DBA can do?
> Thanks
>
Could you tell me please if there is something a DBA is supposed to do to
override an operating system error that states the device is offline and the
backups fail? The error is as follows:
BackupDiskFile::CreateMedia: Backup device
'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
system error = 32(The process cannot access the file because it is being used
by another process.).
Note*There was a job running that was doing some db activity, but this
should not prevent a backup from occurring. The job was running from 9:30 PM
to 11:30 PM and the dump starts at 11 PM.
BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEdge] TO
DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
NOFORMAT
How do you override an operating system error if it is possible to be sure
that production dumps are successful? Is there something the DBA can do?
ThanksYour message is telling you that another process still has a hold of your
file.
You would need to figure out what process has a hold of it. I would go ask
whoever is in charge of putting your backups onto tape if his job is still
running. I used to always have these when my guy was trying to read from my
backup device to put my backup on tape, but I was trying to write to the file
to do a backup.
--
ChrisR
"Cynthia" wrote:
> Hello,
> Could you tell me please if there is something a DBA is supposed to do to
> override an operating system error that states the device is offline and the
> backups fail? The error is as follows:
> BackupDiskFile::CreateMedia: Backup device
> 'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
> system error = 32(The process cannot access the file because it is being used
> by another process.).
> Note*There was a job running that was doing some db activity, but this
> should not prevent a backup from occurring. The job was running from 9:30 PM
> to 11:30 PM and the dump starts at 11 PM.
> BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEdge] TO
> DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
> NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
> NOFORMAT
> How do you override an operating system error if it is possible to be sure
> that production dumps are successful? Is there something the DBA can do?
> Thanks
>
Backups Failing on Production Servers
Hello,
Could you tell me please if there is something a DBA is supposed to do to
override an operating system error that states the device is offline and the
backups fail? The error is as follows:
BackupDiskFile::CreateMedia: Backup device
'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
system error = 32(The process cannot access the file because it is being use
d
by another process.).
Note*There was a job running that was doing some db activity, but this
should not prevent a backup from occurring. The job was running from 9:30 PM
to 11:30 PM and the dump starts at 11 PM.
BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEdge
] TO
DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
NOFORMAT
How do you override an operating system error if it is possible to be sure
that production dumps are successful? Is there something the DBA can do?
ThanksYour message is telling you that another process still has a hold of your
file.
You would need to figure out what process has a hold of it. I would go ask
whoever is in charge of putting your backups onto tape if his job is still
running. I used to always have these when my guy was trying to read from my
backup device to put my backup on tape, but I was trying to write to the fil
e
to do a backup.
ChrisR
"Cynthia" wrote:
> Hello,
> Could you tell me please if there is something a DBA is supposed to do to
> override an operating system error that states the device is offline and t
he
> backups fail? The error is as follows:
> BackupDiskFile::CreateMedia: Backup device
> 'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
> system error = 32(The process cannot access the file because it is being u
sed
> by another process.).
> Note*There was a job running that was doing some db activity, but this
> should not prevent a backup from occurring. The job was running from 9:30
PM
> to 11:30 PM and the dump starts at 11 PM.
> BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEd
ge] TO
> DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
> NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
> NOFORMAT
> How do you override an operating system error if it is possible to be sure
> that production dumps are successful? Is there something the DBA can do?
> Thanks
>
Could you tell me please if there is something a DBA is supposed to do to
override an operating system error that states the device is offline and the
backups fail? The error is as follows:
BackupDiskFile::CreateMedia: Backup device
'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
system error = 32(The process cannot access the file because it is being use
d
by another process.).
Note*There was a job running that was doing some db activity, but this
should not prevent a backup from occurring. The job was running from 9:30 PM
to 11:30 PM and the dump starts at 11 PM.
BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEdge
] TO
DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
NOFORMAT
How do you override an operating system error if it is possible to be sure
that production dumps are successful? Is there something the DBA can do?
ThanksYour message is telling you that another process still has a hold of your
file.
You would need to figure out what process has a hold of it. I would go ask
whoever is in charge of putting your backups onto tape if his job is still
running. I used to always have these when my guy was trying to read from my
backup device to put my backup on tape, but I was trying to write to the fil
e
to do a backup.
ChrisR
"Cynthia" wrote:
> Hello,
> Could you tell me please if there is something a DBA is supposed to do to
> override an operating system error that states the device is offline and t
he
> backups fail? The error is as follows:
> BackupDiskFile::CreateMedia: Backup device
> 'F:\mssql\backup\PES_PortfolioEdge backup.dmp' failed to create. Operating
> system error = 32(The process cannot access the file because it is being u
sed
> by another process.).
> Note*There was a job running that was doing some db activity, but this
> should not prevent a backup from occurring. The job was running from 9:30
PM
> to 11:30 PM and the dump starts at 11 PM.
> BACKUP failed to complete the command BACKUP DATABASE [PES_PortfolioEd
ge] TO
> DISK = N'F:\mssql\backup\PES_PortfolioEdge backup.dmp' WITH INIT ,
> NOUNLOAD , NAME = N'PES_PortfolioEdge backup', NOSKIP , STATS = 10,
> NOFORMAT
> How do you override an operating system error if it is possible to be sure
> that production dumps are successful? Is there something the DBA can do?
> Thanks
>
Backups and Backup Devices in SQL2005
Hi,
Credentials are needed to access resources outside of SQL. Is a backup
and/or backup device regarded as a resource outside of SQL? Do I need to
create a credential to use a backup and/or backup device?
Thanks
Chris
Essentially yes. If you are going to schedule the backups you will need to
use a proxy account. The proxy will require a credential to access the file
system.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:O7uEn1IGGHA.608@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Credentials are needed to access resources outside of SQL. Is a backup
> and/or backup device regarded as a resource outside of SQL? Do I need to
> create a credential to use a backup and/or backup device?
> Thanks
> Chris
>
Credentials are needed to access resources outside of SQL. Is a backup
and/or backup device regarded as a resource outside of SQL? Do I need to
create a credential to use a backup and/or backup device?
Thanks
Chris
Essentially yes. If you are going to schedule the backups you will need to
use a proxy account. The proxy will require a credential to access the file
system.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:O7uEn1IGGHA.608@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Credentials are needed to access resources outside of SQL. Is a backup
> and/or backup device regarded as a resource outside of SQL? Do I need to
> create a credential to use a backup and/or backup device?
> Thanks
> Chris
>
Backups and Backup Devices in SQL2005
Hi,
Credentials are needed to access resources outside of SQL. Is a backup
and/or backup device regarded as a resource outside of SQL? Do I need to
create a credential to use a backup and/or backup device?
Thanks
ChrisEssentially yes. If you are going to schedule the backups you will need to
use a proxy account. The proxy will require a credential to access the file
system.
--
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:O7uEn1IGGHA.608@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Credentials are needed to access resources outside of SQL. Is a backup
> and/or backup device regarded as a resource outside of SQL? Do I need to
> create a credential to use a backup and/or backup device?
> Thanks
> Chris
>
Credentials are needed to access resources outside of SQL. Is a backup
and/or backup device regarded as a resource outside of SQL? Do I need to
create a credential to use a backup and/or backup device?
Thanks
ChrisEssentially yes. If you are going to schedule the backups you will need to
use a proxy account. The proxy will require a credential to access the file
system.
--
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:O7uEn1IGGHA.608@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Credentials are needed to access resources outside of SQL. Is a backup
> and/or backup device regarded as a resource outside of SQL? Do I need to
> create a credential to use a backup and/or backup device?
> Thanks
> Chris
>
Backups and Backup Devices in SQL2005
Hi,
Credentials are needed to access resources outside of SQL. Is a backup
and/or backup device regarded as a resource outside of SQL? Do I need to
create a credential to use a backup and/or backup device?
Thanks
ChrisEssentially yes. If you are going to schedule the backups you will need to
use a proxy account. The proxy will require a credential to access the file
system.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:O7uEn1IGGHA.608@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Credentials are needed to access resources outside of SQL. Is a backup
> and/or backup device regarded as a resource outside of SQL? Do I need to
> create a credential to use a backup and/or backup device?
> Thanks
> Chris
>
Credentials are needed to access resources outside of SQL. Is a backup
and/or backup device regarded as a resource outside of SQL? Do I need to
create a credential to use a backup and/or backup device?
Thanks
ChrisEssentially yes. If you are going to schedule the backups you will need to
use a proxy account. The proxy will require a credential to access the file
system.
Andrew J. Kelly SQL MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:O7uEn1IGGHA.608@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Credentials are needed to access resources outside of SQL. Is a backup
> and/or backup device regarded as a resource outside of SQL? Do I need to
> create a credential to use a backup and/or backup device?
> Thanks
> Chris
>
Saturday, February 25, 2012
Backups
I have created a backup schedule for all databases on a
SQL server. I have Created a Backup device for each db.
and a single stored procedure that is called with database
name, device & retain days passed as parameters. All
Devices are network locations. I didn't want these backups
to swallow the entire disk space so i set the retain days
to 14. After 2 weeks i hoped that each backup would have
been overwriten. Well that was my logic. 2 weeks are up
and the files created are still growing. After some
investigation it is apparent that the expiry dates have
been passed but the backups sets have not been
overwritten. So much for my plan. I have now re-read BOL
and realised that i have got my wires crossed, the entire
media is overwriten when the expiry dates of all backups
within have been reached. To me this is topsy turvy, why
would i wish to overwrite an entire backup file, maybe if
i had taken a back up of the backup then i would wish to
delete it. Have i yet again misunderstood BOL. What i want
to do is maintain a dynamic history of backups. I back up
my database to a device, this backup lasts for 2 weeks and
then is overwriten. so the actual physical file is never
deleted, only the contents within when the expiry date is
reached.
Help!!!!!!!Expiredays and retaindays are only there to not allow you to overwrite using
the INIT before a certain day. If you aren't using INIT or if you are using
NOINIT, it will always be append. And, it is all or nothing.
If you want generation handling, either use the Maint Wizard, a 3:rd party
like www.dbmaint.com or some TSQL programming to handle this (using more
than one backup device).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"mat" <anonymous@.discussions.microsoft.com> wrote in message
news:a5ce01c40a8e$5c4c13e0$a601280a@.phx.gbl...
> I have created a backup schedule for all databases on a
> SQL server. I have Created a Backup device for each db.
> and a single stored procedure that is called with database
> name, device & retain days passed as parameters. All
> Devices are network locations. I didn't want these backups
> to swallow the entire disk space so i set the retain days
> to 14. After 2 weeks i hoped that each backup would have
> been overwriten. Well that was my logic. 2 weeks are up
> and the files created are still growing. After some
> investigation it is apparent that the expiry dates have
> been passed but the backups sets have not been
> overwritten. So much for my plan. I have now re-read BOL
> and realised that i have got my wires crossed, the entire
> media is overwriten when the expiry dates of all backups
> within have been reached. To me this is topsy turvy, why
> would i wish to overwrite an entire backup file, maybe if
> i had taken a back up of the backup then i would wish to
> delete it. Have i yet again misunderstood BOL. What i want
> to do is maintain a dynamic history of backups. I back up
> my database to a device, this backup lasts for 2 weeks and
> then is overwriten. so the actual physical file is never
> deleted, only the contents within when the expiry date is
> reached.
> Help!!!!!!!
>|||Thanks Tibor
Are there any sys SP's or XP's that can be used to edit
backup files? Maybe i could remove expired files..
I have created a stored procedure that looks at a backup
device and tells me which full, DIff and TL backups need
to be applied to restore to a specified point in time. It
looks as if this will nor work if i have to create new
devices..rats...
I pull my hair out some times with the illogical-ness of
SQL server
>--Original Message--
>Expiredays and retaindays are only there to not allow you
to overwrite using
>the INIT before a certain day. If you aren't using INIT
or if you are using
>NOINIT, it will always be append. And, it is all or
nothing.
>If you want generation handling, either use the Maint
Wizard, a 3:rd party
>like www.dbmaint.com or some TSQL programming to handle
this (using more
>than one backup device).
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>
>"mat" <anonymous@.discussions.microsoft.com> wrote in
message
>news:a5ce01c40a8e$5c4c13e0$a601280a@.phx.gbl...
database
backups
days
entire
why
if
want
up
and
is
>
>.
>|||There are no tool with which you can remove selective backups inside a
backup file, I'm afraid.
One alternative is to do append, say over one day (assume db backup once per
day and log backup once per hour). Then after one day, you rename the Active
to give it a timestamp (so you have generations) and then do INIT to the
active one. This is how we did it in Db Maint up until the current version,
where we decided to not do append anymore.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"mat" <anonymous@.discussions.microsoft.com> wrote in message
news:d7ca01c40a92$7eb09060$a101280a@.phx.gbl...
> Thanks Tibor
> Are there any sys SP's or XP's that can be used to edit
> backup files? Maybe i could remove expired files..
> I have created a stored procedure that looks at a backup
> device and tells me which full, DIff and TL backups need
> to be applied to restore to a specified point in time. It
> looks as if this will nor work if i have to create new
> devices..rats...
> I pull my hair out some times with the illogical-ness of
> SQL server
>
> to overwrite using
> or if you are using
> nothing.
> Wizard, a 3:rd party
> this (using more
> message
> database
> backups
> days
> entire
> why
> if
> want
> up
> and
> is|||Thanks tibor, thats great. Part of my backup script now
contains code to create a backup device every time it is
run that is named depending on a variable passed.
Alternating every week the physical file names change and
the retain days are set to 7. So as you advised i create a
file and add my backups. After a week i swich to a second
file and use this for a week. After another 7 days i
switch back to the original file that is now ready tbe
overwriten.
My SP that advises me of what backup files to aply now
works in pretty much the same way. It creates a device
based on the parameters and returns the backup history. it
then re-creates the device with the second file name and
apends this to the first run.
Thanks so much, you have been a great help..
>--Original Message--
>There are no tool with which you can remove selective
backups inside a
>backup file, I'm afraid.
>One alternative is to do append, say over one day (assume
db backup once per
>day and log backup once per hour). Then after one day,
you rename the Active
>to give it a timestamp (so you have generations) and then
do INIT to the
>active one. This is how we did it in Db Maint up until
the current version,
>where we decided to not do append anymore.
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>
>"mat" <anonymous@.discussions.microsoft.com> wrote in
message
>news:d7ca01c40a92$7eb09060$a101280a@.phx.gbl...
It
you
on a
db.
have
are up
have
BOL
backups
maybe
wish to
back
weeks
never
date
>
>.
>|||I'm glad I could help, mat. Just one thing: As far as I can see, retains
days doesn't really buy you anything. I only mention this so you don't read
anything into this parameter which isn't there... :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"mat" <anonymous@.discussions.microsoft.com> wrote in message
news:d55d01c40aad$fb535920$a501280a@.phx.gbl...
> Thanks tibor, thats great. Part of my backup script now
> contains code to create a backup device every time it is
> run that is named depending on a variable passed.
> Alternating every week the physical file names change and
> the retain days are set to 7. So as you advised i create a
> file and add my backups. After a week i swich to a second
> file and use this for a week. After another 7 days i
> switch back to the original file that is now ready tbe
> overwriten.
> My SP that advises me of what backup files to aply now
> works in pretty much the same way. It creates a device
> based on the parameters and returns the backup history. it
> then re-creates the device with the second file name and
> apends this to the first run.
> Thanks so much, you have been a great help..
>
> backups inside a
> db backup once per
> you rename the Active
> do INIT to the
> the current version,
> message
> It
> you
> on a
> db.
> have
> are up
> have
> BOL
> backups
> maybe
> wish to
> back
> weeks
> never
> date
SQL server. I have Created a Backup device for each db.
and a single stored procedure that is called with database
name, device & retain days passed as parameters. All
Devices are network locations. I didn't want these backups
to swallow the entire disk space so i set the retain days
to 14. After 2 weeks i hoped that each backup would have
been overwriten. Well that was my logic. 2 weeks are up
and the files created are still growing. After some
investigation it is apparent that the expiry dates have
been passed but the backups sets have not been
overwritten. So much for my plan. I have now re-read BOL
and realised that i have got my wires crossed, the entire
media is overwriten when the expiry dates of all backups
within have been reached. To me this is topsy turvy, why
would i wish to overwrite an entire backup file, maybe if
i had taken a back up of the backup then i would wish to
delete it. Have i yet again misunderstood BOL. What i want
to do is maintain a dynamic history of backups. I back up
my database to a device, this backup lasts for 2 weeks and
then is overwriten. so the actual physical file is never
deleted, only the contents within when the expiry date is
reached.
Help!!!!!!!Expiredays and retaindays are only there to not allow you to overwrite using
the INIT before a certain day. If you aren't using INIT or if you are using
NOINIT, it will always be append. And, it is all or nothing.
If you want generation handling, either use the Maint Wizard, a 3:rd party
like www.dbmaint.com or some TSQL programming to handle this (using more
than one backup device).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"mat" <anonymous@.discussions.microsoft.com> wrote in message
news:a5ce01c40a8e$5c4c13e0$a601280a@.phx.gbl...
> I have created a backup schedule for all databases on a
> SQL server. I have Created a Backup device for each db.
> and a single stored procedure that is called with database
> name, device & retain days passed as parameters. All
> Devices are network locations. I didn't want these backups
> to swallow the entire disk space so i set the retain days
> to 14. After 2 weeks i hoped that each backup would have
> been overwriten. Well that was my logic. 2 weeks are up
> and the files created are still growing. After some
> investigation it is apparent that the expiry dates have
> been passed but the backups sets have not been
> overwritten. So much for my plan. I have now re-read BOL
> and realised that i have got my wires crossed, the entire
> media is overwriten when the expiry dates of all backups
> within have been reached. To me this is topsy turvy, why
> would i wish to overwrite an entire backup file, maybe if
> i had taken a back up of the backup then i would wish to
> delete it. Have i yet again misunderstood BOL. What i want
> to do is maintain a dynamic history of backups. I back up
> my database to a device, this backup lasts for 2 weeks and
> then is overwriten. so the actual physical file is never
> deleted, only the contents within when the expiry date is
> reached.
> Help!!!!!!!
>|||Thanks Tibor
Are there any sys SP's or XP's that can be used to edit
backup files? Maybe i could remove expired files..
I have created a stored procedure that looks at a backup
device and tells me which full, DIff and TL backups need
to be applied to restore to a specified point in time. It
looks as if this will nor work if i have to create new
devices..rats...
I pull my hair out some times with the illogical-ness of
SQL server
>--Original Message--
>Expiredays and retaindays are only there to not allow you
to overwrite using
>the INIT before a certain day. If you aren't using INIT
or if you are using
>NOINIT, it will always be append. And, it is all or
nothing.
>If you want generation handling, either use the Maint
Wizard, a 3:rd party
>like www.dbmaint.com or some TSQL programming to handle
this (using more
>than one backup device).
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>
>"mat" <anonymous@.discussions.microsoft.com> wrote in
message
>news:a5ce01c40a8e$5c4c13e0$a601280a@.phx.gbl...
database
backups
days
entire
why
if
want
up
and
is
>
>.
>|||There are no tool with which you can remove selective backups inside a
backup file, I'm afraid.
One alternative is to do append, say over one day (assume db backup once per
day and log backup once per hour). Then after one day, you rename the Active
to give it a timestamp (so you have generations) and then do INIT to the
active one. This is how we did it in Db Maint up until the current version,
where we decided to not do append anymore.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"mat" <anonymous@.discussions.microsoft.com> wrote in message
news:d7ca01c40a92$7eb09060$a101280a@.phx.gbl...
> Thanks Tibor
> Are there any sys SP's or XP's that can be used to edit
> backup files? Maybe i could remove expired files..
> I have created a stored procedure that looks at a backup
> device and tells me which full, DIff and TL backups need
> to be applied to restore to a specified point in time. It
> looks as if this will nor work if i have to create new
> devices..rats...
> I pull my hair out some times with the illogical-ness of
> SQL server
>
> to overwrite using
> or if you are using
> nothing.
> Wizard, a 3:rd party
> this (using more
> message
> database
> backups
> days
> entire
> why
> if
> want
> up
> and
> is|||Thanks tibor, thats great. Part of my backup script now
contains code to create a backup device every time it is
run that is named depending on a variable passed.
Alternating every week the physical file names change and
the retain days are set to 7. So as you advised i create a
file and add my backups. After a week i swich to a second
file and use this for a week. After another 7 days i
switch back to the original file that is now ready tbe
overwriten.
My SP that advises me of what backup files to aply now
works in pretty much the same way. It creates a device
based on the parameters and returns the backup history. it
then re-creates the device with the second file name and
apends this to the first run.
Thanks so much, you have been a great help..
>--Original Message--
>There are no tool with which you can remove selective
backups inside a
>backup file, I'm afraid.
>One alternative is to do append, say over one day (assume
db backup once per
>day and log backup once per hour). Then after one day,
you rename the Active
>to give it a timestamp (so you have generations) and then
do INIT to the
>active one. This is how we did it in Db Maint up until
the current version,
>where we decided to not do append anymore.
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>
>"mat" <anonymous@.discussions.microsoft.com> wrote in
message
>news:d7ca01c40a92$7eb09060$a101280a@.phx.gbl...
It
you
on a
db.
have
are up
have
BOL
backups
maybe
wish to
back
weeks
never
date
>
>.
>|||I'm glad I could help, mat. Just one thing: As far as I can see, retains
days doesn't really buy you anything. I only mention this so you don't read
anything into this parameter which isn't there... :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"mat" <anonymous@.discussions.microsoft.com> wrote in message
news:d55d01c40aad$fb535920$a501280a@.phx.gbl...
> Thanks tibor, thats great. Part of my backup script now
> contains code to create a backup device every time it is
> run that is named depending on a variable passed.
> Alternating every week the physical file names change and
> the retain days are set to 7. So as you advised i create a
> file and add my backups. After a week i swich to a second
> file and use this for a week. After another 7 days i
> switch back to the original file that is now ready tbe
> overwriten.
> My SP that advises me of what backup files to aply now
> works in pretty much the same way. It creates a device
> based on the parameters and returns the backup history. it
> then re-creates the device with the second file name and
> apends this to the first run.
> Thanks so much, you have been a great help..
>
> backups inside a
> db backup once per
> you rename the Active
> do INIT to the
> the current version,
> message
> It
> you
> on a
> db.
> have
> are up
> have
> BOL
> backups
> maybe
> wish to
> back
> weeks
> never
> date
Friday, February 24, 2012
BackupDiskFile::CreateMedia: Backup device failed to create.
Hi there,
I am getting this error message:
BackupDiskFile::CreateMedia: Backup device failed to create. Operating
system error = 1130(Not enough server storage is available to process this
command.).
Someone has already posted this question below.
http://groups.google.com/group/micro...error+%3D+1130(Not+enough+server+storage+is+a
vailable+to+process+this+command.).&rnum=1&hl=en#d 438e8317739acd8
I checked our security and it is alright. Also, I won't get this error if I
run manually and I am little bit confused.
Could you help?
Thanks.
Abel Chan
Hello Abel,
First, please make sure you have the latest OS/SQL server service pack.
Also, I found similar issue is resolved by incresae size of IRPStacksize.
Please refer to the following article to test
285089 IRPStackSize Parameter in Windows 2000
http://support.microsoft.com/?id=285089
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: BackupDiskFile::CreateMedia: Backup device failed to create.
>thread-index: AcYzStfdEVNmKflURjaV99MKSuljqQ==
>X-WBNR-Posting-Host: 206.253.218.194
>From: =?Utf-8?B?QWJlbCBDaGFu?= <awong@.newsgroup.nospam>
>Subject: BackupDiskFile::CreateMedia: Backup device failed to create.
>Date: Thu, 16 Feb 2006 14:46:36 -0800
>Lines: 19
>Message-ID: <6155BC54-E793-4FA0-9FF0-B8C03E93F9FF@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:421397
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi there,
>I am getting this error message:
>BackupDiskFile::CreateMedia: Backup device failed to create. Operating
>system error = 1130(Not enough server storage is available to process this
>command.).
>Someone has already posted this question below.
http://groups.google.com/group/micro...browse_thread/
thread/edcd04268b1d040e/d438e8317739acd8?lnk=st&q=BackupDiskFile%3A%3ACrea te
Media%3A+Backup+device+failed+to+create.+Operating +system+error+%3D+1130(Not
+enough+server+storage+is+available+to+process+thi s+command.).&rnum=1&hl=en#
d438e8317739acd8
>I checked our security and it is alright. Also, I won't get this error if
I
>run manually and I am little bit confused.
>Could you help?
>Thanks.
>Abel Chan
>
I am getting this error message:
BackupDiskFile::CreateMedia: Backup device failed to create. Operating
system error = 1130(Not enough server storage is available to process this
command.).
Someone has already posted this question below.
http://groups.google.com/group/micro...error+%3D+1130(Not+enough+server+storage+is+a
vailable+to+process+this+command.).&rnum=1&hl=en#d 438e8317739acd8
I checked our security and it is alright. Also, I won't get this error if I
run manually and I am little bit confused.
Could you help?
Thanks.
Abel Chan
Hello Abel,
First, please make sure you have the latest OS/SQL server service pack.
Also, I found similar issue is resolved by incresae size of IRPStacksize.
Please refer to the following article to test
285089 IRPStackSize Parameter in Windows 2000
http://support.microsoft.com/?id=285089
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: BackupDiskFile::CreateMedia: Backup device failed to create.
>thread-index: AcYzStfdEVNmKflURjaV99MKSuljqQ==
>X-WBNR-Posting-Host: 206.253.218.194
>From: =?Utf-8?B?QWJlbCBDaGFu?= <awong@.newsgroup.nospam>
>Subject: BackupDiskFile::CreateMedia: Backup device failed to create.
>Date: Thu, 16 Feb 2006 14:46:36 -0800
>Lines: 19
>Message-ID: <6155BC54-E793-4FA0-9FF0-B8C03E93F9FF@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:421397
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi there,
>I am getting this error message:
>BackupDiskFile::CreateMedia: Backup device failed to create. Operating
>system error = 1130(Not enough server storage is available to process this
>command.).
>Someone has already posted this question below.
http://groups.google.com/group/micro...browse_thread/
thread/edcd04268b1d040e/d438e8317739acd8?lnk=st&q=BackupDiskFile%3A%3ACrea te
Media%3A+Backup+device+failed+to+create.+Operating +system+error+%3D+1130(Not
+enough+server+storage+is+available+to+process+thi s+command.).&rnum=1&hl=en#
d438e8317739acd8
>I checked our security and it is alright. Also, I won't get this error if
I
>run manually and I am little bit confused.
>Could you help?
>Thanks.
>Abel Chan
>
BackupDiskFile::CreateMedia: Backup device failed to create.
Hi there,
I am getting this error message:
BackupDiskFile::CreateMedia: Backup device failed to create. Operating
system error = 1130(Not enough server storage is available to process this
command.).
Someone has already posted this question below.
http://groups.google.com/group/microsoft.public.sqlserver.dts/browse_thread/thread/edcd04268b1d040e/d438e8317739acd8?lnk=st&q=BackupDiskFile%3A%3ACreateMedia%3A+Backup+device+failed+to+create.+Operating+system+error+%3D+1130(Not+enough+server+storage+is+available+to+process+this+command.).&rnum=1&hl=en#d438e8317739acd8
I checked our security and it is alright. Also, I won't get this error if I
run manually and I am little bit confused.
Could you help?
Thanks.
Abel ChanHello Abel,
First, please make sure you have the latest OS/SQL server service pack.
Also, I found similar issue is resolved by incresae size of IRPStacksize.
Please refer to the following article to test
285089 IRPStackSize Parameter in Windows 2000
http://support.microsoft.com/?id=285089
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: BackupDiskFile::CreateMedia: Backup device failed to create.
>thread-index: AcYzStfdEVNmKflURjaV99MKSuljqQ==>X-WBNR-Posting-Host: 206.253.218.194
>From: =?Utf-8?B?QWJlbCBDaGFu?= <awong@.newsgroup.nospam>
>Subject: BackupDiskFile::CreateMedia: Backup device failed to create.
>Date: Thu, 16 Feb 2006 14:46:36 -0800
>Lines: 19
>Message-ID: <6155BC54-E793-4FA0-9FF0-B8C03E93F9FF@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:421397
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi there,
>I am getting this error message:
>BackupDiskFile::CreateMedia: Backup device failed to create. Operating
>system error = 1130(Not enough server storage is available to process this
>command.).
>Someone has already posted this question below.
http://groups.google.com/group/microsoft.public.sqlserver.dts/browse_thread/
thread/edcd04268b1d040e/d438e8317739acd8?lnk=st&q=BackupDiskFile%3A%3ACreate
Media%3A+Backup+device+failed+to+create.+Operating+system+error+%3D+1130(Not
+enough+server+storage+is+available+to+process+this+command.).&rnum=1&hl=en#
d438e8317739acd8
>I checked our security and it is alright. Also, I won't get this error if
I
>run manually and I am little bit confused.
>Could you help?
>Thanks.
>Abel Chan
>
I am getting this error message:
BackupDiskFile::CreateMedia: Backup device failed to create. Operating
system error = 1130(Not enough server storage is available to process this
command.).
Someone has already posted this question below.
http://groups.google.com/group/microsoft.public.sqlserver.dts/browse_thread/thread/edcd04268b1d040e/d438e8317739acd8?lnk=st&q=BackupDiskFile%3A%3ACreateMedia%3A+Backup+device+failed+to+create.+Operating+system+error+%3D+1130(Not+enough+server+storage+is+available+to+process+this+command.).&rnum=1&hl=en#d438e8317739acd8
I checked our security and it is alright. Also, I won't get this error if I
run manually and I am little bit confused.
Could you help?
Thanks.
Abel ChanHello Abel,
First, please make sure you have the latest OS/SQL server service pack.
Also, I found similar issue is resolved by incresae size of IRPStacksize.
Please refer to the following article to test
285089 IRPStackSize Parameter in Windows 2000
http://support.microsoft.com/?id=285089
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: BackupDiskFile::CreateMedia: Backup device failed to create.
>thread-index: AcYzStfdEVNmKflURjaV99MKSuljqQ==>X-WBNR-Posting-Host: 206.253.218.194
>From: =?Utf-8?B?QWJlbCBDaGFu?= <awong@.newsgroup.nospam>
>Subject: BackupDiskFile::CreateMedia: Backup device failed to create.
>Date: Thu, 16 Feb 2006 14:46:36 -0800
>Lines: 19
>Message-ID: <6155BC54-E793-4FA0-9FF0-B8C03E93F9FF@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:421397
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi there,
>I am getting this error message:
>BackupDiskFile::CreateMedia: Backup device failed to create. Operating
>system error = 1130(Not enough server storage is available to process this
>command.).
>Someone has already posted this question below.
http://groups.google.com/group/microsoft.public.sqlserver.dts/browse_thread/
thread/edcd04268b1d040e/d438e8317739acd8?lnk=st&q=BackupDiskFile%3A%3ACreate
Media%3A+Backup+device+failed+to+create.+Operating+system+error+%3D+1130(Not
+enough+server+storage+is+available+to+process+this+command.).&rnum=1&hl=en#
d438e8317739acd8
>I checked our security and it is alright. Also, I won't get this error if
I
>run manually and I am little bit confused.
>Could you help?
>Thanks.
>Abel Chan
>
BackupDiskFile::CreateMedia: Backup device failed to create.
Hi there,
I am getting this error message:
BackupDiskFile::CreateMedia: Backup device failed to create. Operating
system error = 1130(Not enough server storage is available to process this
command.).
Someone has already posted this question below.
http://groups.google.com/group/micr...+error+%3D+1130(Not+enough+serv
er+storage+is+a
vailable+to+process+this+command.).&rnum=1&hl=en#d438e8317739acd8
I checked our security and it is alright. Also, I won't get this error if I
run manually and I am little bit confused.
Could you help?
Thanks.
Abel ChanHello Abel,
First, please make sure you have the latest OS/SQL server service pack.
Also, I found similar issue is resolved by incresae size of IRPStacksize.
Please refer to the following article to test
285089 IRPStackSize Parameter in Windows 2000
http://support.microsoft.com/?id=285089
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: BackupDiskFile::CreateMedia: Backup device failed to create.
>thread-index: AcYzStfdEVNmKflURjaV99MKSuljqQ==
>X-WBNR-Posting-Host: 206.253.218.194
>From: examnotes <awong@.newsgroup.nospam>
>Subject: BackupDiskFile::CreateMedia: Backup device failed to create.
>Date: Thu, 16 Feb 2006 14:46:36 -0800
>Lines: 19
>Message-ID: <6155BC54-E793-4FA0-9FF0-B8C03E93F9FF@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:421397
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi there,
>I am getting this error message:
>BackupDiskFile::CreateMedia: Backup device failed to create. Operating
>system error = 1130(Not enough server storage is available to process this
>command.).
>Someone has already posted this question below.
http://groups.google.com/group/micr.../browse_thread/
thread/edcd04268b1d040e/d438e8317739acd8?lnk=st&q=BackupDiskFile%3A%3ACreate
Media%3A+Backup+device+failed+to+create.+Operating+system+error+%3D+1130(Not
+enough+server+storage+is+available+to+p
rocess+this+command.).&rnum=1&hl=en#
d438e8317739acd8
>I checked our security and it is alright. Also, I won't get this error if
I
>run manually and I am little bit confused.
>Could you help?
>Thanks.
>Abel Chan
>
I am getting this error message:
BackupDiskFile::CreateMedia: Backup device failed to create. Operating
system error = 1130(Not enough server storage is available to process this
command.).
Someone has already posted this question below.
http://groups.google.com/group/micr...+error+%3D+1130(Not+enough+serv
er+storage+is+a
vailable+to+process+this+command.).&rnum=1&hl=en#d438e8317739acd8
I checked our security and it is alright. Also, I won't get this error if I
run manually and I am little bit confused.
Could you help?
Thanks.
Abel ChanHello Abel,
First, please make sure you have the latest OS/SQL server service pack.
Also, I found similar issue is resolved by incresae size of IRPStacksize.
Please refer to the following article to test
285089 IRPStackSize Parameter in Windows 2000
http://support.microsoft.com/?id=285089
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: BackupDiskFile::CreateMedia: Backup device failed to create.
>thread-index: AcYzStfdEVNmKflURjaV99MKSuljqQ==
>X-WBNR-Posting-Host: 206.253.218.194
>From: examnotes <awong@.newsgroup.nospam>
>Subject: BackupDiskFile::CreateMedia: Backup device failed to create.
>Date: Thu, 16 Feb 2006 14:46:36 -0800
>Lines: 19
>Message-ID: <6155BC54-E793-4FA0-9FF0-B8C03E93F9FF@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:421397
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi there,
>I am getting this error message:
>BackupDiskFile::CreateMedia: Backup device failed to create. Operating
>system error = 1130(Not enough server storage is available to process this
>command.).
>Someone has already posted this question below.
http://groups.google.com/group/micr.../browse_thread/
thread/edcd04268b1d040e/d438e8317739acd8?lnk=st&q=BackupDiskFile%3A%3ACreate
Media%3A+Backup+device+failed+to+create.+Operating+system+error+%3D+1130(Not
+enough+server+storage+is+available+to+p
rocess+this+command.).&rnum=1&hl=en#
d438e8317739acd8
>I checked our security and it is alright. Also, I won't get this error if
I
>run manually and I am little bit confused.
>Could you help?
>Thanks.
>Abel Chan
>
BackupDiskFile::CreateMedia: Backup device failed to create
Hi,
In SQL Query Analyzer, I run the following command.
Backup database sharepoint_webspace To sharepoint_webspace with init,
name='sharepoint_webspace_full'.
The result was,
Server: Msg 3201, Level 16, State 1, Line 1
Cannot open backup device 'sharepoint_webspace'. Device error or device
off-line. See the SQL Server error log for more details.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
SQL server log shows:
=== BACKUP failed to complete the command Backup database SharePoint_WebSpace To
sharepoint_webspace with init, name='SharePoint_WebSpace_full'
BackupDiskFile::CreateMedia: Backup device
'z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK' failed to create. Operating
system error=32 (The process cannot access the file because it is being used
by another process.)
===
The backup disk file z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK has some
old backed up stuff. It's over 11G right now.
Question I have:
How should I know what process is using the sharepoint_webspace.BAK file? I
checked Process Info in EM, there are four processes associated with the
sharepoint_webspace database, but three of them are connections from the IIS
web server (Network Library: TCP/IP). The other one is the Backup command
I'm running in SQL Query Analyzer (Network Library).
How should I get the problem fixed?
Thanks much in advance,
BingNever mind. I've figured it out. Another process is trying to write the
backup disk file to tapes but no more tapes available.
Bing
"bing" wrote:
> Hi,
> In SQL Query Analyzer, I run the following command.
> Backup database sharepoint_webspace To sharepoint_webspace with init,
> name='sharepoint_webspace_full'.
> The result was,
> Server: Msg 3201, Level 16, State 1, Line 1
> Cannot open backup device 'sharepoint_webspace'. Device error or device
> off-line. See the SQL Server error log for more details.
> Server: Msg 3013, Level 16, State 1, Line 1
> BACKUP DATABASE is terminating abnormally.
> SQL server log shows:
> ===> BACKUP failed to complete the command Backup database SharePoint_WebSpace To
> sharepoint_webspace with init, name='SharePoint_WebSpace_full'
> BackupDiskFile::CreateMedia: Backup device
> 'z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK' failed to create. Operating
> system error=32 (The process cannot access the file because it is being used
> by another process.)
> ===> The backup disk file z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK has some
> old backed up stuff. It's over 11G right now.
> Question I have:
> How should I know what process is using the sharepoint_webspace.BAK file? I
> checked Process Info in EM, there are four processes associated with the
> sharepoint_webspace database, but three of them are connections from the IIS
> web server (Network Library: TCP/IP). The other one is the Backup command
> I'm running in SQL Query Analyzer (Network Library).
> How should I get the problem fixed?
> Thanks much in advance,
> Bing
In SQL Query Analyzer, I run the following command.
Backup database sharepoint_webspace To sharepoint_webspace with init,
name='sharepoint_webspace_full'.
The result was,
Server: Msg 3201, Level 16, State 1, Line 1
Cannot open backup device 'sharepoint_webspace'. Device error or device
off-line. See the SQL Server error log for more details.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
SQL server log shows:
=== BACKUP failed to complete the command Backup database SharePoint_WebSpace To
sharepoint_webspace with init, name='SharePoint_WebSpace_full'
BackupDiskFile::CreateMedia: Backup device
'z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK' failed to create. Operating
system error=32 (The process cannot access the file because it is being used
by another process.)
===
The backup disk file z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK has some
old backed up stuff. It's over 11G right now.
Question I have:
How should I know what process is using the sharepoint_webspace.BAK file? I
checked Process Info in EM, there are four processes associated with the
sharepoint_webspace database, but three of them are connections from the IIS
web server (Network Library: TCP/IP). The other one is the Backup command
I'm running in SQL Query Analyzer (Network Library).
How should I get the problem fixed?
Thanks much in advance,
BingNever mind. I've figured it out. Another process is trying to write the
backup disk file to tapes but no more tapes available.
Bing
"bing" wrote:
> Hi,
> In SQL Query Analyzer, I run the following command.
> Backup database sharepoint_webspace To sharepoint_webspace with init,
> name='sharepoint_webspace_full'.
> The result was,
> Server: Msg 3201, Level 16, State 1, Line 1
> Cannot open backup device 'sharepoint_webspace'. Device error or device
> off-line. See the SQL Server error log for more details.
> Server: Msg 3013, Level 16, State 1, Line 1
> BACKUP DATABASE is terminating abnormally.
> SQL server log shows:
> ===> BACKUP failed to complete the command Backup database SharePoint_WebSpace To
> sharepoint_webspace with init, name='SharePoint_WebSpace_full'
> BackupDiskFile::CreateMedia: Backup device
> 'z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK' failed to create. Operating
> system error=32 (The process cannot access the file because it is being used
> by another process.)
> ===> The backup disk file z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK has some
> old backed up stuff. It's over 11G right now.
> Question I have:
> How should I know what process is using the sharepoint_webspace.BAK file? I
> checked Process Info in EM, there are four processes associated with the
> sharepoint_webspace database, but three of them are connections from the IIS
> web server (Network Library: TCP/IP). The other one is the Backup command
> I'm running in SQL Query Analyzer (Network Library).
> How should I get the problem fixed?
> Thanks much in advance,
> Bing
BackupDiskFile::CreateMedia: Backup device failed to create
Hi,
In SQL Query Analyzer, I run the following command.
Backup database sharepoint_webspace To sharepoint_webspace with init,
name='sharepoint_webspace_full'.
The result was,
Server: Msg 3201, Level 16, State 1, Line 1
Cannot open backup device 'sharepoint_webspace'. Device error or device
off-line. See the SQL Server error log for more details.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
SQL server log shows:
===
BACKUP failed to complete the command Backup database SharePoint_WebSpace To
sharepoint_webspace with init, name='SharePoint_WebSpace_full'
BackupDiskFile::CreateMedia: Backup device
'z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK' failed to create. Operating
system error=32 (The process cannot access the file because it is being used
by another process.)
===
The backup disk file z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK has some
old backed up stuff. It's over 11G right now.
Question I have:
How should I know what process is using the sharepoint_webspace.BAK file? I
checked Process Info in EM, there are four processes associated with the
sharepoint_webspace database, but three of them are connections from the IIS
web server (Network Library: TCP/IP). The other one is the Backup command
I'm running in SQL Query Analyzer (Network Library).
How should I get the problem fixed?
Thanks much in advance,
Bing
Never mind. I've figured it out. Another process is trying to write the
backup disk file to tapes but no more tapes available.
Bing
"bing" wrote:
> Hi,
> In SQL Query Analyzer, I run the following command.
> Backup database sharepoint_webspace To sharepoint_webspace with init,
> name='sharepoint_webspace_full'.
> The result was,
> Server: Msg 3201, Level 16, State 1, Line 1
> Cannot open backup device 'sharepoint_webspace'. Device error or device
> off-line. See the SQL Server error log for more details.
> Server: Msg 3013, Level 16, State 1, Line 1
> BACKUP DATABASE is terminating abnormally.
> SQL server log shows:
> ===
> BACKUP failed to complete the command Backup database SharePoint_WebSpace To
> sharepoint_webspace with init, name='SharePoint_WebSpace_full'
> BackupDiskFile::CreateMedia: Backup device
> 'z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK' failed to create. Operating
> system error=32 (The process cannot access the file because it is being used
> by another process.)
> ===
> The backup disk file z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK has some
> old backed up stuff. It's over 11G right now.
> Question I have:
> How should I know what process is using the sharepoint_webspace.BAK file? I
> checked Process Info in EM, there are four processes associated with the
> sharepoint_webspace database, but three of them are connections from the IIS
> web server (Network Library: TCP/IP). The other one is the Backup command
> I'm running in SQL Query Analyzer (Network Library).
> How should I get the problem fixed?
> Thanks much in advance,
> Bing
In SQL Query Analyzer, I run the following command.
Backup database sharepoint_webspace To sharepoint_webspace with init,
name='sharepoint_webspace_full'.
The result was,
Server: Msg 3201, Level 16, State 1, Line 1
Cannot open backup device 'sharepoint_webspace'. Device error or device
off-line. See the SQL Server error log for more details.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
SQL server log shows:
===
BACKUP failed to complete the command Backup database SharePoint_WebSpace To
sharepoint_webspace with init, name='SharePoint_WebSpace_full'
BackupDiskFile::CreateMedia: Backup device
'z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK' failed to create. Operating
system error=32 (The process cannot access the file because it is being used
by another process.)
===
The backup disk file z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK has some
old backed up stuff. It's over 11G right now.
Question I have:
How should I know what process is using the sharepoint_webspace.BAK file? I
checked Process Info in EM, there are four processes associated with the
sharepoint_webspace database, but three of them are connections from the IIS
web server (Network Library: TCP/IP). The other one is the Backup command
I'm running in SQL Query Analyzer (Network Library).
How should I get the problem fixed?
Thanks much in advance,
Bing
Never mind. I've figured it out. Another process is trying to write the
backup disk file to tapes but no more tapes available.
Bing
"bing" wrote:
> Hi,
> In SQL Query Analyzer, I run the following command.
> Backup database sharepoint_webspace To sharepoint_webspace with init,
> name='sharepoint_webspace_full'.
> The result was,
> Server: Msg 3201, Level 16, State 1, Line 1
> Cannot open backup device 'sharepoint_webspace'. Device error or device
> off-line. See the SQL Server error log for more details.
> Server: Msg 3013, Level 16, State 1, Line 1
> BACKUP DATABASE is terminating abnormally.
> SQL server log shows:
> ===
> BACKUP failed to complete the command Backup database SharePoint_WebSpace To
> sharepoint_webspace with init, name='SharePoint_WebSpace_full'
> BackupDiskFile::CreateMedia: Backup device
> 'z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK' failed to create. Operating
> system error=32 (The process cannot access the file because it is being used
> by another process.)
> ===
> The backup disk file z:\data\MYSQL\BACKUP\sharepoint_webspace.BAK has some
> old backed up stuff. It's over 11G right now.
> Question I have:
> How should I know what process is using the sharepoint_webspace.BAK file? I
> checked Process Info in EM, there are four processes associated with the
> sharepoint_webspace database, but three of them are connections from the IIS
> web server (Network Library: TCP/IP). The other one is the Backup command
> I'm running in SQL Query Analyzer (Network Library).
> How should I get the problem fixed?
> Thanks much in advance,
> Bing
BackupDiskFile::CreateMedia: Backup device failed to create
Hi,
In SQL Query Analyzer, I run the following command.
Backup database sharepoint_webspace To sharepoint_webspace with init,
name='sharepoint_webspace_full'.
The result was,
Server: Msg 3201, Level 16, State 1, Line 1
Cannot open backup device 'sharepoint_webspace'. Device error or device
off-line. See the SQL Server error log for more details.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
SQL server log shows:
===
BACKUP failed to complete the command Backup database SharePoint_WebSpace To
sharepoint_webspace with init, name='SharePoint_WebSpace_full'
BackupDiskFile::CreateMedia: Backup device
'z:\data\MYSQL\BACKUP\sharepoint_webspac
e.BAK' failed to create. Operating
system error=32 (The process cannot access the file because it is being used
by another process.)
===
The backup disk file z:\data\MYSQL\BACKUP\sharepoint_webspace
.BAK has some
old backed up stuff. It's over 11G right now.
Question I have:
How should I know what process is using the sharepoint_webspace.BAK file? I
checked Process Info in EM, there are four processes associated with the
sharepoint_webspace database, but three of them are connections from the IIS
web server (Network Library: TCP/IP). The other one is the Backup command
I'm running in SQL Query Analyzer (Network Library).
How should I get the problem fixed?
Thanks much in advance,
BingNever mind. I've figured it out. Another process is trying to write the
backup disk file to tapes but no more tapes available.
Bing
"bing" wrote:
> Hi,
> In SQL Query Analyzer, I run the following command.
> Backup database sharepoint_webspace To sharepoint_webspace with init,
> name='sharepoint_webspace_full'.
> The result was,
> Server: Msg 3201, Level 16, State 1, Line 1
> Cannot open backup device 'sharepoint_webspace'. Device error or device
> off-line. See the SQL Server error log for more details.
> Server: Msg 3013, Level 16, State 1, Line 1
> BACKUP DATABASE is terminating abnormally.
> SQL server log shows:
> ===
> BACKUP failed to complete the command Backup database SharePoint_WebSpace
To
> sharepoint_webspace with init, name='SharePoint_WebSpace_full'
> BackupDiskFile::CreateMedia: Backup device
> 'z:\data\MYSQL\BACKUP\sharepoint_webspac
e.BAK' failed to create. Operatin
g
> system error=32 (The process cannot access the file because it is being us
ed
> by another process.)
> ===
> The backup disk file z:\data\MYSQL\BACKUP\sharepoint_webspace
.BAK has some
> old backed up stuff. It's over 11G right now.
> Question I have:
> How should I know what process is using the sharepoint_webspace.BAK file?
I
> checked Process Info in EM, there are four processes associated with the
> sharepoint_webspace database, but three of them are connections from the I
IS
> web server (Network Library: TCP/IP). The other one is the Backup command
> I'm running in SQL Query Analyzer (Network Library).
> How should I get the problem fixed?
> Thanks much in advance,
> Bing
In SQL Query Analyzer, I run the following command.
Backup database sharepoint_webspace To sharepoint_webspace with init,
name='sharepoint_webspace_full'.
The result was,
Server: Msg 3201, Level 16, State 1, Line 1
Cannot open backup device 'sharepoint_webspace'. Device error or device
off-line. See the SQL Server error log for more details.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
SQL server log shows:
===
BACKUP failed to complete the command Backup database SharePoint_WebSpace To
sharepoint_webspace with init, name='SharePoint_WebSpace_full'
BackupDiskFile::CreateMedia: Backup device
'z:\data\MYSQL\BACKUP\sharepoint_webspac
e.BAK' failed to create. Operating
system error=32 (The process cannot access the file because it is being used
by another process.)
===
The backup disk file z:\data\MYSQL\BACKUP\sharepoint_webspace
.BAK has some
old backed up stuff. It's over 11G right now.
Question I have:
How should I know what process is using the sharepoint_webspace.BAK file? I
checked Process Info in EM, there are four processes associated with the
sharepoint_webspace database, but three of them are connections from the IIS
web server (Network Library: TCP/IP). The other one is the Backup command
I'm running in SQL Query Analyzer (Network Library).
How should I get the problem fixed?
Thanks much in advance,
BingNever mind. I've figured it out. Another process is trying to write the
backup disk file to tapes but no more tapes available.
Bing
"bing" wrote:
> Hi,
> In SQL Query Analyzer, I run the following command.
> Backup database sharepoint_webspace To sharepoint_webspace with init,
> name='sharepoint_webspace_full'.
> The result was,
> Server: Msg 3201, Level 16, State 1, Line 1
> Cannot open backup device 'sharepoint_webspace'. Device error or device
> off-line. See the SQL Server error log for more details.
> Server: Msg 3013, Level 16, State 1, Line 1
> BACKUP DATABASE is terminating abnormally.
> SQL server log shows:
> ===
> BACKUP failed to complete the command Backup database SharePoint_WebSpace
To
> sharepoint_webspace with init, name='SharePoint_WebSpace_full'
> BackupDiskFile::CreateMedia: Backup device
> 'z:\data\MYSQL\BACKUP\sharepoint_webspac
e.BAK' failed to create. Operatin
g
> system error=32 (The process cannot access the file because it is being us
ed
> by another process.)
> ===
> The backup disk file z:\data\MYSQL\BACKUP\sharepoint_webspace
.BAK has some
> old backed up stuff. It's over 11G right now.
> Question I have:
> How should I know what process is using the sharepoint_webspace.BAK file?
I
> checked Process Info in EM, there are four processes associated with the
> sharepoint_webspace database, but three of them are connections from the I
IS
> web server (Network Library: TCP/IP). The other one is the Backup command
> I'm running in SQL Query Analyzer (Network Library).
> How should I get the problem fixed?
> Thanks much in advance,
> Bing
Monday, February 13, 2012
Backup w/RETAINDAYS just keeps growin', and growin'
Hi all;
I need to make daily backups to a computer in another domain, where I can't map a drive, so I use the TSQL to create a dump device, which works fine:
EXEC sp_addumpdevice 'disk', 'MyBackupDevice', [ipaddress & directory/file]
Then I schedule a server job which faithfully backs up my database, with one hitch - it never deletes days older than 5 as per the code - it just keeps growing. The command couldn't be much simpler:
BACKUP DATABASE ProductionETC to MyBackupDevice WITH RETAINDAYS = 5
For now, I just create a new backup device every now and then and go back and forth, deleting the oldest one when I create a new one. But it's annoying! Any ideas what I'm doing wrong?
Thanks,
L. Rap
RETAINDAYS only prevents SQL Server from overwriting the file unless the specified number of days have elapsed. It doesn't mean that SQL Server will automatically delete the file or erase the media after the specified number of days. So you will have to delete the files using your own scheduled job or use a database maintainence task (you can create from Enterprise Manager or SSMS).|||Thanks Umachandar, that's very helpful. I misunderstood the instructions.
Would you happen to know if it is possible to delete the earliest backup from the set using T-SQL or some other preset command, or if I need to schedule an OS job to simply delete the file and start over?
Regards,
L. Rap
Sunday, February 12, 2012
Backup Transaction Log
We are running SQL Server 2000, SP 3. We want to backup the Transaction log
by backup to a backup device. However, the transaction log is greyed out.
What are we doing wrong?
Thanks.Have you done a full database backup yet? You cannot backup the log until
you have backed up the database. A restore operation always starts by
restoring the full database, and then applying each of the log backups. If
you don't have a full db backup, the log backups can't be used for anything.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Jill Johnson" <jjohnson362000@.yahoo.com> wrote in message
news:u6MXhIfZDHA.2668@.TK2MSFTNGP09.phx.gbl...
> We are running SQL Server 2000, SP 3. We want to backup the Transaction
log
> by backup to a backup device. However, the transaction log is greyed out.
> What are we doing wrong?
> Thanks.
>|||Thank you for your quick response, Kalen.
I backup each database (master, msdb, etc.) to each backup device. Then, I
back up those files to a tape drive. Do you consider that I have a full
database backup? I don't know what I am doing.
Thanks.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:e1tG1MfZDHA.388@.TK2MSFTNGP10.phx.gbl...
> Have you done a full database backup yet? You cannot backup the log until
> you have backed up the database. A restore operation always starts by
> restoring the full database, and then applying each of the log backups. If
> you don't have a full db backup, the log backups can't be used for
anything.
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "Jill Johnson" <jjohnson362000@.yahoo.com> wrote in message
> news:u6MXhIfZDHA.2668@.TK2MSFTNGP09.phx.gbl...
> > We are running SQL Server 2000, SP 3. We want to backup the Transaction
> log
> > by backup to a backup device. However, the transaction log is greyed
out.
> > What are we doing wrong?
> >
> > Thanks.
> >
> >
>|||What is the recovery model of your database(s).
If 'simple' you don't have this option
>--Original Message--
>Thank you for your quick response, Kalen.
>I backup each database (master, msdb, etc.) to each
backup device. Then, I
>back up those files to a tape drive. Do you consider
that I have a full
>database backup? I don't know what I am doing.
>Thanks.
>"Kalen Delaney" <replies@.public_newsgroups.com> wrote in
message
>news:e1tG1MfZDHA.388@.TK2MSFTNGP10.phx.gbl...
>> Have you done a full database backup yet? You cannot
backup the log until
>> you have backed up the database. A restore operation
always starts by
>> restoring the full database, and then applying each of
the log backups. If
>> you don't have a full db backup, the log backups can't
be used for
>anything.
>> --
>> HTH
>> --
>> Kalen Delaney
>> SQL Server MVP
>> www.SolidQualityLearning.com
>>
>> "Jill Johnson" <jjohnson362000@.yahoo.com> wrote in
message
>> news:u6MXhIfZDHA.2668@.TK2MSFTNGP09.phx.gbl...
>> > We are running SQL Server 2000, SP 3. We want to
backup the Transaction
>> log
>> > by backup to a backup device. However, the
transaction log is greyed
>out.
>> > What are we doing wrong?
>> >
>> > Thanks.
>> >
>> >
>>
>
>.
>|||I don't know what my recovery model of my database(s). What are my
options?
Please explain to me that my thinking of recovery method is wrong. If I
need to do a recovery, first, I need to restore the file from the tape.
Then, I open the Enterprise Manager and select Restore.
Thanks.
"Rohan pitiya" <rpitiyar@.hotmail.com> wrote in message
news:091f01c365f7$a6074e50$a101280a@.phx.gbl...
> What is the recovery model of your database(s).
> If 'simple' you don't have this option
>
> >--Original Message--
> >Thank you for your quick response, Kalen.
> >
> >I backup each database (master, msdb, etc.) to each
> backup device. Then, I
> >back up those files to a tape drive. Do you consider
> that I have a full
> >database backup? I don't know what I am doing.
> >
> >Thanks.
> >
> >"Kalen Delaney" <replies@.public_newsgroups.com> wrote in
> message
> >news:e1tG1MfZDHA.388@.TK2MSFTNGP10.phx.gbl...
> >> Have you done a full database backup yet? You cannot
> backup the log until
> >> you have backed up the database. A restore operation
> always starts by
> >> restoring the full database, and then applying each of
> the log backups. If
> >> you don't have a full db backup, the log backups can't
> be used for
> >anything.
> >>
> >> --
> >> HTH
> >> --
> >> Kalen Delaney
> >> SQL Server MVP
> >> www.SolidQualityLearning.com
> >>
> >>
> >> "Jill Johnson" <jjohnson362000@.yahoo.com> wrote in
> message
> >> news:u6MXhIfZDHA.2668@.TK2MSFTNGP09.phx.gbl...
> >> > We are running SQL Server 2000, SP 3. We want to
> backup the Transaction
> >> log
> >> > by backup to a backup device. However, the
> transaction log is greyed
> >out.
> >> > What are we doing wrong?
> >> >
> >> > Thanks.
> >> >
> >> >
> >>
> >>
> >
> >
> >.
> >|||The other possibility is that your database is in SIMPLE recovery mode. In
that case, the log is automatically truncated at regular intervals, so there
will be nothing left to back up. Check the database property sheet in
Enterprise Manager.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Jill Johnson" <jjohnson362000@.yahoo.com> wrote in message
news:eSfnKRfZDHA.2932@.tk2msftngp13.phx.gbl...
> Thank you for your quick response, Kalen.
> I backup each database (master, msdb, etc.) to each backup device. Then,
I
> back up those files to a tape drive. Do you consider that I have a full
> database backup? I don't know what I am doing.
> Thanks.
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:e1tG1MfZDHA.388@.TK2MSFTNGP10.phx.gbl...
> > Have you done a full database backup yet? You cannot backup the log
until
> > you have backed up the database. A restore operation always starts by
> > restoring the full database, and then applying each of the log backups.
If
> > you don't have a full db backup, the log backups can't be used for
> anything.
> >
> > --
> > HTH
> > --
> > Kalen Delaney
> > SQL Server MVP
> > www.SolidQualityLearning.com
> >
> >
> > "Jill Johnson" <jjohnson362000@.yahoo.com> wrote in message
> > news:u6MXhIfZDHA.2668@.TK2MSFTNGP09.phx.gbl...
> > > We are running SQL Server 2000, SP 3. We want to backup the
Transaction
> > log
> > > by backup to a backup device. However, the transaction log is greyed
> out.
> > > What are we doing wrong?
> > >
> > > Thanks.
> > >
> > >
> >
> >
>|||Every database is set to one of three recovery models which affects how much
information is logged and how the transaction log is handled.
Please open up Books Online from your SQL Server Program Group and read
about Recovery Models before you start planning your backup and restore
strategy. There is also a lot of information in the Books Online about
backup and restore.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Jill Johnson" <jjohnson362000@.yahoo.com> wrote in message
news:e$MRbNgZDHA.2580@.TK2MSFTNGP09.phx.gbl...
> I don't know what my recovery model of my database(s). What are my
> options?
> Please explain to me that my thinking of recovery method is wrong. If I
> need to do a recovery, first, I need to restore the file from the tape.
> Then, I open the Enterprise Manager and select Restore.
> Thanks.
> "Rohan pitiya" <rpitiyar@.hotmail.com> wrote in message
> news:091f01c365f7$a6074e50$a101280a@.phx.gbl...
> > What is the recovery model of your database(s).
> > If 'simple' you don't have this option
> >
> >
> > >--Original Message--
> > >Thank you for your quick response, Kalen.
> > >
> > >I backup each database (master, msdb, etc.) to each
> > backup device. Then, I
> > >back up those files to a tape drive. Do you consider
> > that I have a full
> > >database backup? I don't know what I am doing.
> > >
> > >Thanks.
> > >
> > >"Kalen Delaney" <replies@.public_newsgroups.com> wrote in
> > message
> > >news:e1tG1MfZDHA.388@.TK2MSFTNGP10.phx.gbl...
> > >> Have you done a full database backup yet? You cannot
> > backup the log until
> > >> you have backed up the database. A restore operation
> > always starts by
> > >> restoring the full database, and then applying each of
> > the log backups. If
> > >> you don't have a full db backup, the log backups can't
> > be used for
> > >anything.
> > >>
> > >> --
> > >> HTH
> > >> --
> > >> Kalen Delaney
> > >> SQL Server MVP
> > >> www.SolidQualityLearning.com
> > >>
> > >>
> > >> "Jill Johnson" <jjohnson362000@.yahoo.com> wrote in
> > message
> > >> news:u6MXhIfZDHA.2668@.TK2MSFTNGP09.phx.gbl...
> > >> > We are running SQL Server 2000, SP 3. We want to
> > backup the Transaction
> > >> log
> > >> > by backup to a backup device. However, the
> > transaction log is greyed
> > >out.
> > >> > What are we doing wrong?
> > >> >
> > >> > Thanks.
> > >> >
> > >> >
> > >>
> > >>
> > >
> > >
> > >.
> > >
>
by backup to a backup device. However, the transaction log is greyed out.
What are we doing wrong?
Thanks.Have you done a full database backup yet? You cannot backup the log until
you have backed up the database. A restore operation always starts by
restoring the full database, and then applying each of the log backups. If
you don't have a full db backup, the log backups can't be used for anything.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Jill Johnson" <jjohnson362000@.yahoo.com> wrote in message
news:u6MXhIfZDHA.2668@.TK2MSFTNGP09.phx.gbl...
> We are running SQL Server 2000, SP 3. We want to backup the Transaction
log
> by backup to a backup device. However, the transaction log is greyed out.
> What are we doing wrong?
> Thanks.
>|||Thank you for your quick response, Kalen.
I backup each database (master, msdb, etc.) to each backup device. Then, I
back up those files to a tape drive. Do you consider that I have a full
database backup? I don't know what I am doing.
Thanks.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:e1tG1MfZDHA.388@.TK2MSFTNGP10.phx.gbl...
> Have you done a full database backup yet? You cannot backup the log until
> you have backed up the database. A restore operation always starts by
> restoring the full database, and then applying each of the log backups. If
> you don't have a full db backup, the log backups can't be used for
anything.
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "Jill Johnson" <jjohnson362000@.yahoo.com> wrote in message
> news:u6MXhIfZDHA.2668@.TK2MSFTNGP09.phx.gbl...
> > We are running SQL Server 2000, SP 3. We want to backup the Transaction
> log
> > by backup to a backup device. However, the transaction log is greyed
out.
> > What are we doing wrong?
> >
> > Thanks.
> >
> >
>|||What is the recovery model of your database(s).
If 'simple' you don't have this option
>--Original Message--
>Thank you for your quick response, Kalen.
>I backup each database (master, msdb, etc.) to each
backup device. Then, I
>back up those files to a tape drive. Do you consider
that I have a full
>database backup? I don't know what I am doing.
>Thanks.
>"Kalen Delaney" <replies@.public_newsgroups.com> wrote in
message
>news:e1tG1MfZDHA.388@.TK2MSFTNGP10.phx.gbl...
>> Have you done a full database backup yet? You cannot
backup the log until
>> you have backed up the database. A restore operation
always starts by
>> restoring the full database, and then applying each of
the log backups. If
>> you don't have a full db backup, the log backups can't
be used for
>anything.
>> --
>> HTH
>> --
>> Kalen Delaney
>> SQL Server MVP
>> www.SolidQualityLearning.com
>>
>> "Jill Johnson" <jjohnson362000@.yahoo.com> wrote in
message
>> news:u6MXhIfZDHA.2668@.TK2MSFTNGP09.phx.gbl...
>> > We are running SQL Server 2000, SP 3. We want to
backup the Transaction
>> log
>> > by backup to a backup device. However, the
transaction log is greyed
>out.
>> > What are we doing wrong?
>> >
>> > Thanks.
>> >
>> >
>>
>
>.
>|||I don't know what my recovery model of my database(s). What are my
options?
Please explain to me that my thinking of recovery method is wrong. If I
need to do a recovery, first, I need to restore the file from the tape.
Then, I open the Enterprise Manager and select Restore.
Thanks.
"Rohan pitiya" <rpitiyar@.hotmail.com> wrote in message
news:091f01c365f7$a6074e50$a101280a@.phx.gbl...
> What is the recovery model of your database(s).
> If 'simple' you don't have this option
>
> >--Original Message--
> >Thank you for your quick response, Kalen.
> >
> >I backup each database (master, msdb, etc.) to each
> backup device. Then, I
> >back up those files to a tape drive. Do you consider
> that I have a full
> >database backup? I don't know what I am doing.
> >
> >Thanks.
> >
> >"Kalen Delaney" <replies@.public_newsgroups.com> wrote in
> message
> >news:e1tG1MfZDHA.388@.TK2MSFTNGP10.phx.gbl...
> >> Have you done a full database backup yet? You cannot
> backup the log until
> >> you have backed up the database. A restore operation
> always starts by
> >> restoring the full database, and then applying each of
> the log backups. If
> >> you don't have a full db backup, the log backups can't
> be used for
> >anything.
> >>
> >> --
> >> HTH
> >> --
> >> Kalen Delaney
> >> SQL Server MVP
> >> www.SolidQualityLearning.com
> >>
> >>
> >> "Jill Johnson" <jjohnson362000@.yahoo.com> wrote in
> message
> >> news:u6MXhIfZDHA.2668@.TK2MSFTNGP09.phx.gbl...
> >> > We are running SQL Server 2000, SP 3. We want to
> backup the Transaction
> >> log
> >> > by backup to a backup device. However, the
> transaction log is greyed
> >out.
> >> > What are we doing wrong?
> >> >
> >> > Thanks.
> >> >
> >> >
> >>
> >>
> >
> >
> >.
> >|||The other possibility is that your database is in SIMPLE recovery mode. In
that case, the log is automatically truncated at regular intervals, so there
will be nothing left to back up. Check the database property sheet in
Enterprise Manager.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Jill Johnson" <jjohnson362000@.yahoo.com> wrote in message
news:eSfnKRfZDHA.2932@.tk2msftngp13.phx.gbl...
> Thank you for your quick response, Kalen.
> I backup each database (master, msdb, etc.) to each backup device. Then,
I
> back up those files to a tape drive. Do you consider that I have a full
> database backup? I don't know what I am doing.
> Thanks.
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:e1tG1MfZDHA.388@.TK2MSFTNGP10.phx.gbl...
> > Have you done a full database backup yet? You cannot backup the log
until
> > you have backed up the database. A restore operation always starts by
> > restoring the full database, and then applying each of the log backups.
If
> > you don't have a full db backup, the log backups can't be used for
> anything.
> >
> > --
> > HTH
> > --
> > Kalen Delaney
> > SQL Server MVP
> > www.SolidQualityLearning.com
> >
> >
> > "Jill Johnson" <jjohnson362000@.yahoo.com> wrote in message
> > news:u6MXhIfZDHA.2668@.TK2MSFTNGP09.phx.gbl...
> > > We are running SQL Server 2000, SP 3. We want to backup the
Transaction
> > log
> > > by backup to a backup device. However, the transaction log is greyed
> out.
> > > What are we doing wrong?
> > >
> > > Thanks.
> > >
> > >
> >
> >
>|||Every database is set to one of three recovery models which affects how much
information is logged and how the transaction log is handled.
Please open up Books Online from your SQL Server Program Group and read
about Recovery Models before you start planning your backup and restore
strategy. There is also a lot of information in the Books Online about
backup and restore.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Jill Johnson" <jjohnson362000@.yahoo.com> wrote in message
news:e$MRbNgZDHA.2580@.TK2MSFTNGP09.phx.gbl...
> I don't know what my recovery model of my database(s). What are my
> options?
> Please explain to me that my thinking of recovery method is wrong. If I
> need to do a recovery, first, I need to restore the file from the tape.
> Then, I open the Enterprise Manager and select Restore.
> Thanks.
> "Rohan pitiya" <rpitiyar@.hotmail.com> wrote in message
> news:091f01c365f7$a6074e50$a101280a@.phx.gbl...
> > What is the recovery model of your database(s).
> > If 'simple' you don't have this option
> >
> >
> > >--Original Message--
> > >Thank you for your quick response, Kalen.
> > >
> > >I backup each database (master, msdb, etc.) to each
> > backup device. Then, I
> > >back up those files to a tape drive. Do you consider
> > that I have a full
> > >database backup? I don't know what I am doing.
> > >
> > >Thanks.
> > >
> > >"Kalen Delaney" <replies@.public_newsgroups.com> wrote in
> > message
> > >news:e1tG1MfZDHA.388@.TK2MSFTNGP10.phx.gbl...
> > >> Have you done a full database backup yet? You cannot
> > backup the log until
> > >> you have backed up the database. A restore operation
> > always starts by
> > >> restoring the full database, and then applying each of
> > the log backups. If
> > >> you don't have a full db backup, the log backups can't
> > be used for
> > >anything.
> > >>
> > >> --
> > >> HTH
> > >> --
> > >> Kalen Delaney
> > >> SQL Server MVP
> > >> www.SolidQualityLearning.com
> > >>
> > >>
> > >> "Jill Johnson" <jjohnson362000@.yahoo.com> wrote in
> > message
> > >> news:u6MXhIfZDHA.2668@.TK2MSFTNGP09.phx.gbl...
> > >> > We are running SQL Server 2000, SP 3. We want to
> > backup the Transaction
> > >> log
> > >> > by backup to a backup device. However, the
> > transaction log is greyed
> > >out.
> > >> > What are we doing wrong?
> > >> >
> > >> > Thanks.
> > >> >
> > >> >
> > >>
> > >>
> > >
> > >
> > >.
> > >
>
backup to tape failed
I was trying to do a backup to tape but it failed with the following message:
Msg 3229, Level 16, State 2, Line 2
Request for device '\\.\Tape0' timed out.
Msg 3013, Level 16, State 1, Line 2
BACKUP DATABASE is terminating abnormally.
Any clues why this happened?
Any help is appreciated.
Take a look at the system event log and sql errorlogs.
You may have a hardware issue with the tape drive (or the connection to it...).
If the OS returned an error code to sql server, it will have been logged in the errorlog.
That 3229 is also raised if a tape mount was pending but a new tape was not loaded prior to the timeout. However, that instance should have "state = 1" and not 2 as you report.
|||Thanks for the help. The problem was with the MEDIANAME. i was specifying a new Medianame.
If MEDIANAME is specified, it must match the previously specified media name already existing on the backup volume.
Thanks Anyways
Friday, February 10, 2012
Backup to NAS device fails under SQL2k5 X64...
Here is my scenario: we have SQL2K5 X64 running in VM (ESX server). When I
use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after some
non-deterministic period of time) with the error
BackupMedium::ReportIoError: write failure on backup device
'\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735.bak'. Operating
system error 64(The specified network name is no longer available.).
The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried this
on another box with OS patched to max/SQL2K5 at level 3215 with the same
results.
The really weird thing is if I run this exact scenario in the 32-bit
environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's related
to the 64-bit environment. If I point the landing spot for the backup file to
locally attached storage (in a 64-bit VM environment), it works fine.
Has anybody seen this in their 64-bit environment? If so, what did you do to
get around this issue?
PaulIt doesn't sound like a SQL problem. Try copying a large file with xcopy or
explorer and see if the same thing happens.
--
Jason Massie
Web: http://statisticsio.com
RSS: http://feeds.feedburner.com/statisticsio
"psligar" <psligar@.discussions.microsoft.com> wrote in message
news:B7994C94-7224-4F34-82B2-37D8C7D84BB2@.microsoft.com...
> Here is my scenario: we have SQL2K5 X64 running in VM (ESX server). When I
> use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after
> some
> non-deterministic period of time) with the error
> BackupMedium::ReportIoError: write failure on backup device
> '\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735.bak'. Operating
> system error 64(The specified network name is no longer available.).
> The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried
> this
> on another box with OS patched to max/SQL2K5 at level 3215 with the same
> results.
> The really weird thing is if I run this exact scenario in the 32-bit
> environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's
> related
> to the 64-bit environment. If I point the landing spot for the backup file
> to
> locally attached storage (in a 64-bit VM environment), it works fine.
> Has anybody seen this in their 64-bit environment? If so, what did you do
> to
> get around this issue?
> Paul|||Does the NAS location your trying to write to exist?
'The specified network name is no longer available'
Can you map to the nas location via my computer? If yes to both, then make
sure the ID your using has access to the nas device (read,write, modify,
etc).
I currently have all my SQL2k5 servers backing up to a NAS and I ran into
something similiar and it was due to the Id I was using no longer had access
to the NAS device.
"psligar" <psligar@.discussions.microsoft.com> wrote in message
news:B7994C94-7224-4F34-82B2-37D8C7D84BB2@.microsoft.com...
> Here is my scenario: we have SQL2K5 X64 running in VM (ESX server). When I
> use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after
> some
> non-deterministic period of time) with the error
> BackupMedium::ReportIoError: write failure on backup device
> '\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735.bak'. Operating
> system error 64(The specified network name is no longer available.).
> The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried
> this
> on another box with OS patched to max/SQL2K5 at level 3215 with the same
> results.
> The really weird thing is if I run this exact scenario in the 32-bit
> environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's
> related
> to the 64-bit environment. If I point the landing spot for the backup file
> to
> locally attached storage (in a 64-bit VM environment), it works fine.
> Has anybody seen this in their 64-bit environment? If so, what did you do
> to
> get around this issue?
> Paul|||Jason:
Thanks for the reply. I should have included that info in my question - that
was our thinking, as well. Our first inclination was to think we had a 64-bit
network driver issue. However, we have copied (via XCOPY) large (~30 GB)
files continuously across the network to the device in question (from the
64-bit VM SQL machine) with no problems.
"Jason Massie" wrote:
> It doesn't sound like a SQL problem. Try copying a large file with xcopy or
> explorer and see if the same thing happens.
> --
> Jason Massie
> Web: http://statisticsio.com
> RSS: http://feeds.feedburner.com/statisticsio
> "psligar" <psligar@.discussions.microsoft.com> wrote in message
> news:B7994C94-7224-4F34-82B2-37D8C7D84BB2@.microsoft.com...
> > Here is my scenario: we have SQL2K5 X64 running in VM (ESX server). When I
> > use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after
> > some
> > non-deterministic period of time) with the error
> >
> > BackupMedium::ReportIoError: write failure on backup device
> > '\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735.bak'. Operating
> > system error 64(The specified network name is no longer available.).
> >
> > The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried
> > this
> > on another box with OS patched to max/SQL2K5 at level 3215 with the same
> > results.
> >
> > The really weird thing is if I run this exact scenario in the 32-bit
> > environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's
> > related
> > to the 64-bit environment. If I point the landing spot for the backup file
> > to
> > locally attached storage (in a 64-bit VM environment), it works fine.
> >
> > Has anybody seen this in their 64-bit environment? If so, what did you do
> > to
> > get around this issue?
> >
> > Paul
>
>|||Mike:
Thanks for the reply. To answer your question, yes, the location exists - we
are backing up multiple SQL2K 32-bit servers to that location across the
network. Some of those machines are in the ESX environment, as well. I can
map a drive to the network share point on the NAS device from 64-bit VM's in
question. I can copy large files to that share (see my reply to Jason). The
issue in question only surfaces when I try to use the 'BACKUP DATABASE' T-SQL
cmd from within SQL2K5.
In reference to the UID issue you mention, at times, one or more databases
will successfully backup to this device, before it fails on a subsequent DB.
So I'm confident that the UID being used has access to the network share.
NOTE: It's the same UID that is being used by the 32-bit SQL boxes that do
not exhibit this problem.
If I had the hardware availability, I might try setting up a stand alone
64-bit test box (to eliminate the ESX part of this scenario). Unfortunately,
I don't have that option (currently).
Paul
"Mike" wrote:
> Does the NAS location your trying to write to exist?
> 'The specified network name is no longer available'
> Can you map to the nas location via my computer? If yes to both, then make
> sure the ID your using has access to the nas device (read,write, modify,
> etc).
> I currently have all my SQL2k5 servers backing up to a NAS and I ran into
> something similiar and it was due to the Id I was using no longer had access
> to the NAS device.
> "psligar" <psligar@.discussions.microsoft.com> wrote in message
> news:B7994C94-7224-4F34-82B2-37D8C7D84BB2@.microsoft.com...
> > Here is my scenario: we have SQL2K5 X64 running in VM (ESX server). When I
> > use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after
> > some
> > non-deterministic period of time) with the error
> >
> > BackupMedium::ReportIoError: write failure on backup device
> > '\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735.bak'. Operating
> > system error 64(The specified network name is no longer available.).
> >
> > The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried
> > this
> > on another box with OS patched to max/SQL2K5 at level 3215 with the same
> > results.
> >
> > The really weird thing is if I run this exact scenario in the 32-bit
> > environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's
> > related
> > to the 64-bit environment. If I point the landing spot for the backup file
> > to
> > locally attached storage (in a 64-bit VM environment), it works fine.
> >
> > Has anybody seen this in their 64-bit environment? If so, what did you do
> > to
> > get around this issue?
> >
> > Paul
>
>|||And the saga continues:
I installed the MS tool NetMon version 3.1 'cause I wanted to see what was
going on vis-a-vis the network, and reran the backup job. Lo and behold, it
completed - 5 DB's backed up across the network to a NAS device - a total of
approximately 52 GB. I know that the NetMon tool loaded a packet capture
driver into the network stack - I'm just unsure what other changes it made.
"psligar" wrote:
> Here is my scenario: we have SQL2K5 X64 running in VM (ESX server). When I
> use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after some
> non-deterministic period of time) with the error
> BackupMedium::ReportIoError: write failure on backup device
> '\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735.bak'. Operating
> system error 64(The specified network name is no longer available.).
> The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried this
> on another box with OS patched to max/SQL2K5 at level 3215 with the same
> results.
> The really weird thing is if I run this exact scenario in the 32-bit
> environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's related
> to the 64-bit environment. If I point the landing spot for the backup file to
> locally attached storage (in a 64-bit VM environment), it works fine.
> Has anybody seen this in their 64-bit environment? If so, what did you do to
> get around this issue?
> Paul
use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after some
non-deterministic period of time) with the error
BackupMedium::ReportIoError: write failure on backup device
'\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735.bak'. Operating
system error 64(The specified network name is no longer available.).
The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried this
on another box with OS patched to max/SQL2K5 at level 3215 with the same
results.
The really weird thing is if I run this exact scenario in the 32-bit
environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's related
to the 64-bit environment. If I point the landing spot for the backup file to
locally attached storage (in a 64-bit VM environment), it works fine.
Has anybody seen this in their 64-bit environment? If so, what did you do to
get around this issue?
PaulIt doesn't sound like a SQL problem. Try copying a large file with xcopy or
explorer and see if the same thing happens.
--
Jason Massie
Web: http://statisticsio.com
RSS: http://feeds.feedburner.com/statisticsio
"psligar" <psligar@.discussions.microsoft.com> wrote in message
news:B7994C94-7224-4F34-82B2-37D8C7D84BB2@.microsoft.com...
> Here is my scenario: we have SQL2K5 X64 running in VM (ESX server). When I
> use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after
> some
> non-deterministic period of time) with the error
> BackupMedium::ReportIoError: write failure on backup device
> '\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735.bak'. Operating
> system error 64(The specified network name is no longer available.).
> The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried
> this
> on another box with OS patched to max/SQL2K5 at level 3215 with the same
> results.
> The really weird thing is if I run this exact scenario in the 32-bit
> environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's
> related
> to the 64-bit environment. If I point the landing spot for the backup file
> to
> locally attached storage (in a 64-bit VM environment), it works fine.
> Has anybody seen this in their 64-bit environment? If so, what did you do
> to
> get around this issue?
> Paul|||Does the NAS location your trying to write to exist?
'The specified network name is no longer available'
Can you map to the nas location via my computer? If yes to both, then make
sure the ID your using has access to the nas device (read,write, modify,
etc).
I currently have all my SQL2k5 servers backing up to a NAS and I ran into
something similiar and it was due to the Id I was using no longer had access
to the NAS device.
"psligar" <psligar@.discussions.microsoft.com> wrote in message
news:B7994C94-7224-4F34-82B2-37D8C7D84BB2@.microsoft.com...
> Here is my scenario: we have SQL2K5 X64 running in VM (ESX server). When I
> use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after
> some
> non-deterministic period of time) with the error
> BackupMedium::ReportIoError: write failure on backup device
> '\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735.bak'. Operating
> system error 64(The specified network name is no longer available.).
> The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried
> this
> on another box with OS patched to max/SQL2K5 at level 3215 with the same
> results.
> The really weird thing is if I run this exact scenario in the 32-bit
> environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's
> related
> to the 64-bit environment. If I point the landing spot for the backup file
> to
> locally attached storage (in a 64-bit VM environment), it works fine.
> Has anybody seen this in their 64-bit environment? If so, what did you do
> to
> get around this issue?
> Paul|||Jason:
Thanks for the reply. I should have included that info in my question - that
was our thinking, as well. Our first inclination was to think we had a 64-bit
network driver issue. However, we have copied (via XCOPY) large (~30 GB)
files continuously across the network to the device in question (from the
64-bit VM SQL machine) with no problems.
"Jason Massie" wrote:
> It doesn't sound like a SQL problem. Try copying a large file with xcopy or
> explorer and see if the same thing happens.
> --
> Jason Massie
> Web: http://statisticsio.com
> RSS: http://feeds.feedburner.com/statisticsio
> "psligar" <psligar@.discussions.microsoft.com> wrote in message
> news:B7994C94-7224-4F34-82B2-37D8C7D84BB2@.microsoft.com...
> > Here is my scenario: we have SQL2K5 X64 running in VM (ESX server). When I
> > use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after
> > some
> > non-deterministic period of time) with the error
> >
> > BackupMedium::ReportIoError: write failure on backup device
> > '\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735.bak'. Operating
> > system error 64(The specified network name is no longer available.).
> >
> > The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried
> > this
> > on another box with OS patched to max/SQL2K5 at level 3215 with the same
> > results.
> >
> > The really weird thing is if I run this exact scenario in the 32-bit
> > environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's
> > related
> > to the 64-bit environment. If I point the landing spot for the backup file
> > to
> > locally attached storage (in a 64-bit VM environment), it works fine.
> >
> > Has anybody seen this in their 64-bit environment? If so, what did you do
> > to
> > get around this issue?
> >
> > Paul
>
>|||Mike:
Thanks for the reply. To answer your question, yes, the location exists - we
are backing up multiple SQL2K 32-bit servers to that location across the
network. Some of those machines are in the ESX environment, as well. I can
map a drive to the network share point on the NAS device from 64-bit VM's in
question. I can copy large files to that share (see my reply to Jason). The
issue in question only surfaces when I try to use the 'BACKUP DATABASE' T-SQL
cmd from within SQL2K5.
In reference to the UID issue you mention, at times, one or more databases
will successfully backup to this device, before it fails on a subsequent DB.
So I'm confident that the UID being used has access to the network share.
NOTE: It's the same UID that is being used by the 32-bit SQL boxes that do
not exhibit this problem.
If I had the hardware availability, I might try setting up a stand alone
64-bit test box (to eliminate the ESX part of this scenario). Unfortunately,
I don't have that option (currently).
Paul
"Mike" wrote:
> Does the NAS location your trying to write to exist?
> 'The specified network name is no longer available'
> Can you map to the nas location via my computer? If yes to both, then make
> sure the ID your using has access to the nas device (read,write, modify,
> etc).
> I currently have all my SQL2k5 servers backing up to a NAS and I ran into
> something similiar and it was due to the Id I was using no longer had access
> to the NAS device.
> "psligar" <psligar@.discussions.microsoft.com> wrote in message
> news:B7994C94-7224-4F34-82B2-37D8C7D84BB2@.microsoft.com...
> > Here is my scenario: we have SQL2K5 X64 running in VM (ESX server). When I
> > use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after
> > some
> > non-deterministic period of time) with the error
> >
> > BackupMedium::ReportIoError: write failure on backup device
> > '\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735.bak'. Operating
> > system error 64(The specified network name is no longer available.).
> >
> > The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried
> > this
> > on another box with OS patched to max/SQL2K5 at level 3215 with the same
> > results.
> >
> > The really weird thing is if I run this exact scenario in the 32-bit
> > environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's
> > related
> > to the 64-bit environment. If I point the landing spot for the backup file
> > to
> > locally attached storage (in a 64-bit VM environment), it works fine.
> >
> > Has anybody seen this in their 64-bit environment? If so, what did you do
> > to
> > get around this issue?
> >
> > Paul
>
>|||And the saga continues:
I installed the MS tool NetMon version 3.1 'cause I wanted to see what was
going on vis-a-vis the network, and reran the backup job. Lo and behold, it
completed - 5 DB's backed up across the network to a NAS device - a total of
approximately 52 GB. I know that the NetMon tool loaded a packet capture
driver into the network stack - I'm just unsure what other changes it made.
"psligar" wrote:
> Here is my scenario: we have SQL2K5 X64 running in VM (ESX server). When I
> use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after some
> non-deterministic period of time) with the error
> BackupMedium::ReportIoError: write failure on backup device
> '\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735.bak'. Operating
> system error 64(The specified network name is no longer available.).
> The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried this
> on another box with OS patched to max/SQL2K5 at level 3215 with the same
> results.
> The really weird thing is if I run this exact scenario in the 32-bit
> environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's related
> to the 64-bit environment. If I point the landing spot for the backup file to
> locally attached storage (in a 64-bit VM environment), it works fine.
> Has anybody seen this in their 64-bit environment? If so, what did you do to
> get around this issue?
> Paul
Backup to NAS device fails under SQL2k5 X64...
Here is my scenario: we have SQL2K5 X64 running in VM (ESX server). When I
use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after some
non-deterministic period of time) with the error
BackupMedium::ReportIoError: write failure on backup device
'\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735. bak'. Operating
system error 64(The specified network name is no longer available.).
The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried this
on another box with OS patched to max/SQL2K5 at level 3215 with the same
results.
The really weird thing is if I run this exact scenario in the 32-bit
environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's related
to the 64-bit environment. If I point the landing spot for the backup file to
locally attached storage (in a 64-bit VM environment), it works fine.
Has anybody seen this in their 64-bit environment? If so, what did you do to
get around this issue?
Paul
It doesn't sound like a SQL problem. Try copying a large file with xcopy or
explorer and see if the same thing happens.
Jason Massie
Web: http://statisticsio.com
RSS: http://feeds.feedburner.com/statisticsio
"psligar" <psligar@.discussions.microsoft.com> wrote in message
news:B7994C94-7224-4F34-82B2-37D8C7D84BB2@.microsoft.com...
> Here is my scenario: we have SQL2K5 X64 running in VM (ESX server). When I
> use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after
> some
> non-deterministic period of time) with the error
> BackupMedium::ReportIoError: write failure on backup device
> '\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735. bak'. Operating
> system error 64(The specified network name is no longer available.).
> The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried
> this
> on another box with OS patched to max/SQL2K5 at level 3215 with the same
> results.
> The really weird thing is if I run this exact scenario in the 32-bit
> environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's
> related
> to the 64-bit environment. If I point the landing spot for the backup file
> to
> locally attached storage (in a 64-bit VM environment), it works fine.
> Has anybody seen this in their 64-bit environment? If so, what did you do
> to
> get around this issue?
> Paul
|||Does the NAS location your trying to write to exist?
'The specified network name is no longer available'
Can you map to the nas location via my computer? If yes to both, then make
sure the ID your using has access to the nas device (read,write, modify,
etc).
I currently have all my SQL2k5 servers backing up to a NAS and I ran into
something similiar and it was due to the Id I was using no longer had access
to the NAS device.
"psligar" <psligar@.discussions.microsoft.com> wrote in message
news:B7994C94-7224-4F34-82B2-37D8C7D84BB2@.microsoft.com...
> Here is my scenario: we have SQL2K5 X64 running in VM (ESX server). When I
> use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after
> some
> non-deterministic period of time) with the error
> BackupMedium::ReportIoError: write failure on backup device
> '\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735. bak'. Operating
> system error 64(The specified network name is no longer available.).
> The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried
> this
> on another box with OS patched to max/SQL2K5 at level 3215 with the same
> results.
> The really weird thing is if I run this exact scenario in the 32-bit
> environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's
> related
> to the 64-bit environment. If I point the landing spot for the backup file
> to
> locally attached storage (in a 64-bit VM environment), it works fine.
> Has anybody seen this in their 64-bit environment? If so, what did you do
> to
> get around this issue?
> Paul
|||Jason:
Thanks for the reply. I should have included that info in my question - that
was our thinking, as well. Our first inclination was to think we had a 64-bit
network driver issue. However, we have copied (via XCOPY) large (~30 GB)
files continuously across the network to the device in question (from the
64-bit VM SQL machine) with no problems.
"Jason Massie" wrote:
> It doesn't sound like a SQL problem. Try copying a large file with xcopy or
> explorer and see if the same thing happens.
> --
> Jason Massie
> Web: http://statisticsio.com
> RSS: http://feeds.feedburner.com/statisticsio
> "psligar" <psligar@.discussions.microsoft.com> wrote in message
> news:B7994C94-7224-4F34-82B2-37D8C7D84BB2@.microsoft.com...
>
>
|||Mike:
Thanks for the reply. To answer your question, yes, the location exists - we
are backing up multiple SQL2K 32-bit servers to that location across the
network. Some of those machines are in the ESX environment, as well. I can
map a drive to the network share point on the NAS device from 64-bit VM's in
question. I can copy large files to that share (see my reply to Jason). The
issue in question only surfaces when I try to use the 'BACKUP DATABASE' T-SQL
cmd from within SQL2K5.
In reference to the UID issue you mention, at times, one or more databases
will successfully backup to this device, before it fails on a subsequent DB.
So I'm confident that the UID being used has access to the network share.
NOTE: It's the same UID that is being used by the 32-bit SQL boxes that do
not exhibit this problem.
If I had the hardware availability, I might try setting up a stand alone
64-bit test box (to eliminate the ESX part of this scenario). Unfortunately,
I don't have that option (currently).
Paul
"Mike" wrote:
> Does the NAS location your trying to write to exist?
> 'The specified network name is no longer available'
> Can you map to the nas location via my computer? If yes to both, then make
> sure the ID your using has access to the nas device (read,write, modify,
> etc).
> I currently have all my SQL2k5 servers backing up to a NAS and I ran into
> something similiar and it was due to the Id I was using no longer had access
> to the NAS device.
> "psligar" <psligar@.discussions.microsoft.com> wrote in message
> news:B7994C94-7224-4F34-82B2-37D8C7D84BB2@.microsoft.com...
>
>
|||And the saga continues:
I installed the MS tool NetMon version 3.1 'cause I wanted to see what was
going on vis-a-vis the network, and reran the backup job. Lo and behold, it
completed - 5 DB's backed up across the network to a NAS device - a total of
approximately 52 GB. I know that the NetMon tool loaded a packet capture
driver into the network stack - I'm just unsure what other changes it made.
"psligar" wrote:
> Here is my scenario: we have SQL2K5 X64 running in VM (ESX server). When I
> use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after some
> non-deterministic period of time) with the error
> BackupMedium::ReportIoError: write failure on backup device
> '\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735. bak'. Operating
> system error 64(The specified network name is no longer available.).
> The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried this
> on another box with OS patched to max/SQL2K5 at level 3215 with the same
> results.
> The really weird thing is if I run this exact scenario in the 32-bit
> environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's related
> to the 64-bit environment. If I point the landing spot for the backup file to
> locally attached storage (in a 64-bit VM environment), it works fine.
> Has anybody seen this in their 64-bit environment? If so, what did you do to
> get around this issue?
> Paul
use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after some
non-deterministic period of time) with the error
BackupMedium::ReportIoError: write failure on backup device
'\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735. bak'. Operating
system error 64(The specified network name is no longer available.).
The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried this
on another box with OS patched to max/SQL2K5 at level 3215 with the same
results.
The really weird thing is if I run this exact scenario in the 32-bit
environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's related
to the 64-bit environment. If I point the landing spot for the backup file to
locally attached storage (in a 64-bit VM environment), it works fine.
Has anybody seen this in their 64-bit environment? If so, what did you do to
get around this issue?
Paul
It doesn't sound like a SQL problem. Try copying a large file with xcopy or
explorer and see if the same thing happens.
Jason Massie
Web: http://statisticsio.com
RSS: http://feeds.feedburner.com/statisticsio
"psligar" <psligar@.discussions.microsoft.com> wrote in message
news:B7994C94-7224-4F34-82B2-37D8C7D84BB2@.microsoft.com...
> Here is my scenario: we have SQL2K5 X64 running in VM (ESX server). When I
> use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after
> some
> non-deterministic period of time) with the error
> BackupMedium::ReportIoError: write failure on backup device
> '\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735. bak'. Operating
> system error 64(The specified network name is no longer available.).
> The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried
> this
> on another box with OS patched to max/SQL2K5 at level 3215 with the same
> results.
> The really weird thing is if I run this exact scenario in the 32-bit
> environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's
> related
> to the 64-bit environment. If I point the landing spot for the backup file
> to
> locally attached storage (in a 64-bit VM environment), it works fine.
> Has anybody seen this in their 64-bit environment? If so, what did you do
> to
> get around this issue?
> Paul
|||Does the NAS location your trying to write to exist?
'The specified network name is no longer available'
Can you map to the nas location via my computer? If yes to both, then make
sure the ID your using has access to the nas device (read,write, modify,
etc).
I currently have all my SQL2k5 servers backing up to a NAS and I ran into
something similiar and it was due to the Id I was using no longer had access
to the NAS device.
"psligar" <psligar@.discussions.microsoft.com> wrote in message
news:B7994C94-7224-4F34-82B2-37D8C7D84BB2@.microsoft.com...
> Here is my scenario: we have SQL2K5 X64 running in VM (ESX server). When I
> use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after
> some
> non-deterministic period of time) with the error
> BackupMedium::ReportIoError: write failure on backup device
> '\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735. bak'. Operating
> system error 64(The specified network name is no longer available.).
> The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried
> this
> on another box with OS patched to max/SQL2K5 at level 3215 with the same
> results.
> The really weird thing is if I run this exact scenario in the 32-bit
> environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's
> related
> to the 64-bit environment. If I point the landing spot for the backup file
> to
> locally attached storage (in a 64-bit VM environment), it works fine.
> Has anybody seen this in their 64-bit environment? If so, what did you do
> to
> get around this issue?
> Paul
|||Jason:
Thanks for the reply. I should have included that info in my question - that
was our thinking, as well. Our first inclination was to think we had a 64-bit
network driver issue. However, we have copied (via XCOPY) large (~30 GB)
files continuously across the network to the device in question (from the
64-bit VM SQL machine) with no problems.
"Jason Massie" wrote:
> It doesn't sound like a SQL problem. Try copying a large file with xcopy or
> explorer and see if the same thing happens.
> --
> Jason Massie
> Web: http://statisticsio.com
> RSS: http://feeds.feedburner.com/statisticsio
> "psligar" <psligar@.discussions.microsoft.com> wrote in message
> news:B7994C94-7224-4F34-82B2-37D8C7D84BB2@.microsoft.com...
>
>
|||Mike:
Thanks for the reply. To answer your question, yes, the location exists - we
are backing up multiple SQL2K 32-bit servers to that location across the
network. Some of those machines are in the ESX environment, as well. I can
map a drive to the network share point on the NAS device from 64-bit VM's in
question. I can copy large files to that share (see my reply to Jason). The
issue in question only surfaces when I try to use the 'BACKUP DATABASE' T-SQL
cmd from within SQL2K5.
In reference to the UID issue you mention, at times, one or more databases
will successfully backup to this device, before it fails on a subsequent DB.
So I'm confident that the UID being used has access to the network share.
NOTE: It's the same UID that is being used by the 32-bit SQL boxes that do
not exhibit this problem.
If I had the hardware availability, I might try setting up a stand alone
64-bit test box (to eliminate the ESX part of this scenario). Unfortunately,
I don't have that option (currently).
Paul
"Mike" wrote:
> Does the NAS location your trying to write to exist?
> 'The specified network name is no longer available'
> Can you map to the nas location via my computer? If yes to both, then make
> sure the ID your using has access to the nas device (read,write, modify,
> etc).
> I currently have all my SQL2k5 servers backing up to a NAS and I ran into
> something similiar and it was due to the Id I was using no longer had access
> to the NAS device.
> "psligar" <psligar@.discussions.microsoft.com> wrote in message
> news:B7994C94-7224-4F34-82B2-37D8C7D84BB2@.microsoft.com...
>
>
|||And the saga continues:
I installed the MS tool NetMon version 3.1 'cause I wanted to see what was
going on vis-a-vis the network, and reran the backup job. Lo and behold, it
completed - 5 DB's backed up across the network to a NAS device - a total of
approximately 52 GB. I know that the NetMon tool loaded a packet capture
driver into the network stack - I'm just unsure what other changes it made.
"psligar" wrote:
> Here is my scenario: we have SQL2K5 X64 running in VM (ESX server). When I
> use T-SQL cmd "BACKUP DATABASE" landing on NAS device, if fails (after some
> non-deterministic period of time) with the error
> BackupMedium::ReportIoError: write failure on backup device
> '\\sql-snap\data\BACKUP\sql_dev\ArchiveDB_20080409132735. bak'. Operating
> system error 64(The specified network name is no longer available.).
> The OS is Win2K3 SP2 X64; SQL2K5 is running at level 1399. I have tried this
> on another box with OS patched to max/SQL2K5 at level 3215 with the same
> results.
> The really weird thing is if I run this exact scenario in the 32-bit
> environment (VM/Win2K3/SQL2K5 @. level 3215), it works fine. So it's related
> to the 64-bit environment. If I point the landing spot for the backup file to
> locally attached storage (in a 64-bit VM environment), it works fine.
> Has anybody seen this in their 64-bit environment? If so, what did you do to
> get around this issue?
> Paul
Backup to NAS - Permissions
I am trying to backup my database to a NAS device. I have added a dump device
successfully:
[USE master
EXEC sp_addumpdevice 'disk', 'mydb_bu_nas', '\\nas1\dbbackups\mydb_bu.BAK']
...but when I try to run the backup:
[use mydb
BACKUP DATABASE mydb TO mydb_bu_nas]
...I get the error:
[Cannot open backup device 'digitaldraw_bu_nas_2'. Device error or device
off-line. See the SQL Server error log for more details.]
The event log shows the following details:
[18204 :
BackupDiskFile::CreateMedia: Backup device '\\nas1\dbbackups\mydb_bu.BAK'
failed to create. Operating system error = 5(Access is denied.).]
The MSSQLSERVER Service is running under the local system account. I assume
that this is the user that would need permissions to write to the NAS. If I
change the MSSQLSERVER Service to run as a Domain User are there any other
implications that I should be aware of?
Backups are always done under the account that SQL Server service uses and
must have rights to the share on the NAS. You should use a Domain account
that has the minimum permissions to do the things you need done and no more.
Andrew J. Kelly SQL MVP
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:6BE37CF7-54A1-4DE4-A71B-DE5F58A991FD@.microsoft.com...
>I am trying to backup my database to a NAS device. I have added a dump
>device
> successfully:
> [USE master
> EXEC sp_addumpdevice 'disk', 'mydb_bu_nas',
> '\\nas1\dbbackups\mydb_bu.BAK']
> ..but when I try to run the backup:
> [use mydb
> BACKUP DATABASE mydb TO mydb_bu_nas]
> ..I get the error:
> [Cannot open backup device 'digitaldraw_bu_nas_2'. Device error or device
> off-line. See the SQL Server error log for more details.]
> The event log shows the following details:
> [18204 :
> BackupDiskFile::CreateMedia: Backup device '\\nas1\dbbackups\mydb_bu.BAK'
> failed to create. Operating system error = 5(Access is denied.).]
> The MSSQLSERVER Service is running under the local system account. I
> assume
> that this is the user that would need permissions to write to the NAS. If
> I
> change the MSSQLSERVER Service to run as a Domain User are there any other
> implications that I should be aware of?
>
|||HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/default...b;en-us;555128
The requirements are the same whether you are backing up to a NAS device or
a Windows file share.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:6BE37CF7-54A1-4DE4-A71B-DE5F58A991FD@.microsoft.com...
>I am trying to backup my database to a NAS device. I have added a dump
>device
> successfully:
> [USE master
> EXEC sp_addumpdevice 'disk', 'mydb_bu_nas',
> '\\nas1\dbbackups\mydb_bu.BAK']
> ..but when I try to run the backup:
> [use mydb
> BACKUP DATABASE mydb TO mydb_bu_nas]
> ..I get the error:
> [Cannot open backup device 'digitaldraw_bu_nas_2'. Device error or device
> off-line. See the SQL Server error log for more details.]
> The event log shows the following details:
> [18204 :
> BackupDiskFile::CreateMedia: Backup device '\\nas1\dbbackups\mydb_bu.BAK'
> failed to create. Operating system error = 5(Access is denied.).]
> The MSSQLSERVER Service is running under the local system account. I
> assume
> that this is the user that would need permissions to write to the NAS. If
> I
> change the MSSQLSERVER Service to run as a Domain User are there any other
> implications that I should be aware of?
>
successfully:
[USE master
EXEC sp_addumpdevice 'disk', 'mydb_bu_nas', '\\nas1\dbbackups\mydb_bu.BAK']
...but when I try to run the backup:
[use mydb
BACKUP DATABASE mydb TO mydb_bu_nas]
...I get the error:
[Cannot open backup device 'digitaldraw_bu_nas_2'. Device error or device
off-line. See the SQL Server error log for more details.]
The event log shows the following details:
[18204 :
BackupDiskFile::CreateMedia: Backup device '\\nas1\dbbackups\mydb_bu.BAK'
failed to create. Operating system error = 5(Access is denied.).]
The MSSQLSERVER Service is running under the local system account. I assume
that this is the user that would need permissions to write to the NAS. If I
change the MSSQLSERVER Service to run as a Domain User are there any other
implications that I should be aware of?
Backups are always done under the account that SQL Server service uses and
must have rights to the share on the NAS. You should use a Domain account
that has the minimum permissions to do the things you need done and no more.
Andrew J. Kelly SQL MVP
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:6BE37CF7-54A1-4DE4-A71B-DE5F58A991FD@.microsoft.com...
>I am trying to backup my database to a NAS device. I have added a dump
>device
> successfully:
> [USE master
> EXEC sp_addumpdevice 'disk', 'mydb_bu_nas',
> '\\nas1\dbbackups\mydb_bu.BAK']
> ..but when I try to run the backup:
> [use mydb
> BACKUP DATABASE mydb TO mydb_bu_nas]
> ..I get the error:
> [Cannot open backup device 'digitaldraw_bu_nas_2'. Device error or device
> off-line. See the SQL Server error log for more details.]
> The event log shows the following details:
> [18204 :
> BackupDiskFile::CreateMedia: Backup device '\\nas1\dbbackups\mydb_bu.BAK'
> failed to create. Operating system error = 5(Access is denied.).]
> The MSSQLSERVER Service is running under the local system account. I
> assume
> that this is the user that would need permissions to write to the NAS. If
> I
> change the MSSQLSERVER Service to run as a Domain User are there any other
> implications that I should be aware of?
>
|||HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/default...b;en-us;555128
The requirements are the same whether you are backing up to a NAS device or
a Windows file share.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:6BE37CF7-54A1-4DE4-A71B-DE5F58A991FD@.microsoft.com...
>I am trying to backup my database to a NAS device. I have added a dump
>device
> successfully:
> [USE master
> EXEC sp_addumpdevice 'disk', 'mydb_bu_nas',
> '\\nas1\dbbackups\mydb_bu.BAK']
> ..but when I try to run the backup:
> [use mydb
> BACKUP DATABASE mydb TO mydb_bu_nas]
> ..I get the error:
> [Cannot open backup device 'digitaldraw_bu_nas_2'. Device error or device
> off-line. See the SQL Server error log for more details.]
> The event log shows the following details:
> [18204 :
> BackupDiskFile::CreateMedia: Backup device '\\nas1\dbbackups\mydb_bu.BAK'
> failed to create. Operating system error = 5(Access is denied.).]
> The MSSQLSERVER Service is running under the local system account. I
> assume
> that this is the user that would need permissions to write to the NAS. If
> I
> change the MSSQLSERVER Service to run as a Domain User are there any other
> implications that I should be aware of?
>
Backup to NAS - Permissions
I am trying to backup my database to a NAS device. I have added a dump devic
e
successfully:
[USE master
EXEC sp_addumpdevice 'disk', 'mydb_bu_nas', '\\nas1\dbbackups\mydb_bu.BAK']
..but when I try to run the backup:
[use mydb
BACKUP DATABASE mydb TO mydb_bu_nas]
..I get the error:
[Cannot open backup device 'digitaldraw_bu_nas_2'. Device error or devic
e
off-line. See the SQL Server error log for more details.]
The event log shows the following details:
[18204 :
BackupDiskFile::CreateMedia: Backup device '\\nas1\dbbackups\mydb_bu.BAK'
failed to create. Operating system error = 5(Access is denied.).]
The MSSQLSERVER Service is running under the local system account. I assume
that this is the user that would need permissions to write to the NAS. If I
change the MSSQLSERVER Service to run as a Domain User are there any other
implications that I should be aware of?Backups are always done under the account that SQL Server service uses and
must have rights to the share on the NAS. You should use a Domain account
that has the minimum permissions to do the things you need done and no more.
Andrew J. Kelly SQL MVP
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:6BE37CF7-54A1-4DE4-A71B-DE5F58A991FD@.microsoft.com...
>I am trying to backup my database to a NAS device. I have added a dump
>device
> successfully:
> [USE master
> EXEC sp_addumpdevice 'disk', 'mydb_bu_nas',
> '\\nas1\dbbackups\mydb_bu.BAK']
> ..but when I try to run the backup:
> [use mydb
> BACKUP DATABASE mydb TO mydb_bu_nas]
> ..I get the error:
> [Cannot open backup device 'digitaldraw_bu_nas_2'. Device error or dev
ice
> off-line. See the SQL Server error log for more details.]
> The event log shows the following details:
> [18204 :
> BackupDiskFile::CreateMedia: Backup device '\\nas1\dbbackups\mydb_bu.BAK'
> failed to create. Operating system error = 5(Access is denied.).]
> The MSSQLSERVER Service is running under the local system account. I
> assume
> that this is the user that would need permissions to write to the NAS. If
> I
> change the MSSQLSERVER Service to run as a Domain User are there any other
> implications that I should be aware of?
>|||HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/defaul...kb;en-us;555128
The requirements are the same whether you are backing up to a NAS device or
a Windows file share.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:6BE37CF7-54A1-4DE4-A71B-DE5F58A991FD@.microsoft.com...
>I am trying to backup my database to a NAS device. I have added a dump
>device
> successfully:
> [USE master
> EXEC sp_addumpdevice 'disk', 'mydb_bu_nas',
> '\\nas1\dbbackups\mydb_bu.BAK']
> ..but when I try to run the backup:
> [use mydb
> BACKUP DATABASE mydb TO mydb_bu_nas]
> ..I get the error:
> [Cannot open backup device 'digitaldraw_bu_nas_2'. Device error or dev
ice
> off-line. See the SQL Server error log for more details.]
> The event log shows the following details:
> [18204 :
> BackupDiskFile::CreateMedia: Backup device '\\nas1\dbbackups\mydb_bu.BAK'
> failed to create. Operating system error = 5(Access is denied.).]
> The MSSQLSERVER Service is running under the local system account. I
> assume
> that this is the user that would need permissions to write to the NAS. If
> I
> change the MSSQLSERVER Service to run as a Domain User are there any other
> implications that I should be aware of?
>
e
successfully:
[USE master
EXEC sp_addumpdevice 'disk', 'mydb_bu_nas', '\\nas1\dbbackups\mydb_bu.BAK']
..but when I try to run the backup:
[use mydb
BACKUP DATABASE mydb TO mydb_bu_nas]
..I get the error:
[Cannot open backup device 'digitaldraw_bu_nas_2'. Device error or devic
e
off-line. See the SQL Server error log for more details.]
The event log shows the following details:
[18204 :
BackupDiskFile::CreateMedia: Backup device '\\nas1\dbbackups\mydb_bu.BAK'
failed to create. Operating system error = 5(Access is denied.).]
The MSSQLSERVER Service is running under the local system account. I assume
that this is the user that would need permissions to write to the NAS. If I
change the MSSQLSERVER Service to run as a Domain User are there any other
implications that I should be aware of?Backups are always done under the account that SQL Server service uses and
must have rights to the share on the NAS. You should use a Domain account
that has the minimum permissions to do the things you need done and no more.
Andrew J. Kelly SQL MVP
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:6BE37CF7-54A1-4DE4-A71B-DE5F58A991FD@.microsoft.com...
>I am trying to backup my database to a NAS device. I have added a dump
>device
> successfully:
> [USE master
> EXEC sp_addumpdevice 'disk', 'mydb_bu_nas',
> '\\nas1\dbbackups\mydb_bu.BAK']
> ..but when I try to run the backup:
> [use mydb
> BACKUP DATABASE mydb TO mydb_bu_nas]
> ..I get the error:
> [Cannot open backup device 'digitaldraw_bu_nas_2'. Device error or dev
ice
> off-line. See the SQL Server error log for more details.]
> The event log shows the following details:
> [18204 :
> BackupDiskFile::CreateMedia: Backup device '\\nas1\dbbackups\mydb_bu.BAK'
> failed to create. Operating system error = 5(Access is denied.).]
> The MSSQLSERVER Service is running under the local system account. I
> assume
> that this is the user that would need permissions to write to the NAS. If
> I
> change the MSSQLSERVER Service to run as a Domain User are there any other
> implications that I should be aware of?
>|||HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/defaul...kb;en-us;555128
The requirements are the same whether you are backing up to a NAS device or
a Windows file share.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:6BE37CF7-54A1-4DE4-A71B-DE5F58A991FD@.microsoft.com...
>I am trying to backup my database to a NAS device. I have added a dump
>device
> successfully:
> [USE master
> EXEC sp_addumpdevice 'disk', 'mydb_bu_nas',
> '\\nas1\dbbackups\mydb_bu.BAK']
> ..but when I try to run the backup:
> [use mydb
> BACKUP DATABASE mydb TO mydb_bu_nas]
> ..I get the error:
> [Cannot open backup device 'digitaldraw_bu_nas_2'. Device error or dev
ice
> off-line. See the SQL Server error log for more details.]
> The event log shows the following details:
> [18204 :
> BackupDiskFile::CreateMedia: Backup device '\\nas1\dbbackups\mydb_bu.BAK'
> failed to create. Operating system error = 5(Access is denied.).]
> The MSSQLSERVER Service is running under the local system account. I
> assume
> that this is the user that would need permissions to write to the NAS. If
> I
> change the MSSQLSERVER Service to run as a Domain User are there any other
> implications that I should be aware of?
>
Subscribe to:
Posts (Atom)