Hi,
I'm getting "BackupMedium::ReportIoError: write failure on
backup device 'd:\select
legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK'.
Operating system error 112(error not found)" messages in
the SQL 2000 Server logs when we try to backup our
databases. This is followed by "Internal I/O request
0x53BE4B78: Op: Write, pBuffer: 0x0D6A0000, Size: 983040,
Position: 21632512, UMS: Internal: 0x103, InternalHigh:
0x0, Offset: 0x14A1600, OffsetHigh: 0x0, m_buf:
0x0D6A0000, m_len: 983040, m_actualBytes: 0, m_errcode:
112, BackupFile: d:\select
legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK" and
then "BACKUP failed to complete the command BACKUP
DATABASE [legal] TO DISK = N'd:\select
legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK' WITH
INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT"
messages. The database is around 300Mb and we have 40Gb of
free space on the drive.
The server is Dell PE2600 with a Perc Raid controller
handling 3 drives in Raid 5 config. These are split into
two drives; C: for OS and D: for applications and data.
The smaller system databases back up OK as do the
transaction logs. I've found a reference to writeback
cache but don't know if this is the root cause of the
problem. The OS is Windows 2003 Small Business Server with
SQL Server SP3a.
TIA
Trevor>
> Hi,
> I'm getting "BackupMedium::ReportIoError: write failure on
> backup device 'd:\select
> legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK'.
> Operating system error 112(error not found)" messages in
> the SQL 2000 Server logs when we try to backup our
> databases. This is followed by "Internal I/O request
> 0x53BE4B78: Op: Write, pBuffer: 0x0D6A0000, Size: 983040,
> Position: 21632512, UMS: Internal: 0x103, InternalHigh:
> 0x0, Offset: 0x14A1600, OffsetHigh: 0x0, m_buf:
> 0x0D6A0000, m_len: 983040, m_actualBytes: 0, m_errcode:
> 112, BackupFile: d:\select
> legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK" and
> then "BACKUP failed to complete the command BACKUP
> DATABASE [legal] TO DISK = N'd:\select
> legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK' WITH
> INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT"
> messages. The database is around 300Mb and we have 40Gb of
> free space on the drive.
> The server is Dell PE2600 with a Perc Raid controller
> handling 3 drives in Raid 5 config. These are split into
> two drives; C: for OS and D: for applications and data.
> The smaller system databases back up OK as do the
> transaction logs. I've found a reference to writeback
> cache but don't know if this is the root cause of the
> problem. The OS is Windows 2003 Small Business Server with
> SQL Server SP3a.
> TIA
> Trevor
>
--
Hi Trevor,
Are you using a compressed volume? It is possible that you are out of
diskspace.
Compressed volumes are not supported. Also checkout the following article:
INF: SQL Server and Striped Backups
http://support.microsoft.com/?id=325334
Hope this helps,
--
Eric Cárdenas
SQL Server senior support professional|||Eric Cardenas wrote:
> >
> > Hi,
> > I'm getting "BackupMedium::ReportIoError: write failure on
> > backup device 'd:\select
> > legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK'.
> > Operating system error 112(error not found)" messages in
> > the SQL 2000 Server logs when we try to backup our
> > databases. This is followed by "Internal I/O request
> > 0x53BE4B78: Op: Write, pBuffer: 0x0D6A0000, Size: 983040,
> > Position: 21632512, UMS: Internal: 0x103, InternalHigh:
> > 0x0, Offset: 0x14A1600, OffsetHigh: 0x0, m_buf:
> > 0x0D6A0000, m_len: 983040, m_actualBytes: 0, m_errcode:
> > 112, BackupFile: d:\select
> > legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK" and
> > then "BACKUP failed to complete the command BACKUP
> > DATABASE [legal] TO DISK = N'd:\select
> > legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK' WITH
> > INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT"
> > messages. The database is around 300Mb and we have 40Gb of
> > free space on the drive.
> > The server is Dell PE2600 with a Perc Raid controller
> > handling 3 drives in Raid 5 config. These are split into
> > two drives; C: for OS and D: for applications and data.
> > The smaller system databases back up OK as do the
> > transaction logs. I've found a reference to writeback
> > cache but don't know if this is the root cause of the
> > problem. The OS is Windows 2003 Small Business Server with
> > SQL Server SP3a.
> > TIA
> > Trevor
> >
> --
> Hi Trevor,
> Are you using a compressed volume? It is possible that you are out of
> diskspace.
> Compressed volumes are not supported. Also checkout the following
> article:
> INF: SQL Server and Striped Backups
> http://support.microsoft.com/?id=325334
> Hope this helps,
> --
> Eric Cardenas
> SQL Server senior support professional
Eric,
We should have plenty of disk space. The drives aren't compressed as
far as I am aware.
The databases reside on the same drive that we are backing up to.
We are backing up the databases to a folder on the drive using the SQL
Server backup, and then to tape; the actual database files we exclude
from the tape backup.
The server reports around 40Gb of free space on a 60Gb drive, and the
databases that it fails to back up are our main data database which is
around 200Mb to 250Mb in size, and one of the SQL Server system
databases which looks to be only around 25Mb! The other smaller system
databases back up OK.
The drive is on a Raid 5 array which comprises three 60Gb drives.
We can copy and otherwise create large files on the drive without any
problems; we can copy the database files manually with out any problems
(when we shutdown the SQL Server)
It just seems to be the SQL Server backup of the databases that are
reporting an error.
I've seen some references to writeback cache causing a problem like
this, but nothing that I can say "this is how we fix the problem"
I can't believe that the problem is with the raid striping as I would
then expect loads of people to be reporting this.
Trevor
Showing posts with label write. Show all posts
Showing posts with label write. Show all posts
Sunday, March 11, 2012
Backup problems
Hi,
I'm getting "BackupMedium::ReportIoError: write failure on
backup device 'd:\select
legal\MSSQL$LEGAL\BACKUP\legal_db_200404
292100.BAK'.
Operating system error 112(error not found)" messages in
the SQL 2000 Server logs when we try to backup our
databases. This is followed by "Internal I/O request
0x53BE4B78: Op: Write, pBuffer: 0x0D6A0000, Size: 983040,
Position: 21632512, UMS: Internal: 0x103, InternalHigh:
0x0, Offset: 0x14A1600, OffsetHigh: 0x0, m_buf:
0x0D6A0000, m_len: 983040, m_actualBytes: 0, m_errcode:
112, BackupFile: d:\select
legal\MSSQL$LEGAL\BACKUP\legal_db_200404
292100.BAK" and
then "BACKUP failed to complete the command BACKUP
DATABASE [legal] TO DISK = N'd:\select
legal\MSSQL$LEGAL\BACKUP\legal_db_200404
292100.BAK' WITH
INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT"
messages. The database is around 300Mb and we have 40Gb of
free space on the drive.
The server is Dell PE2600 with a Perc Raid controller
handling 3 drives in Raid 5 config. These are split into
two drives; C: for OS and D: for applications and data.
The smaller system databases back up OK as do the
transaction logs. I've found a reference to writeback
cache but don't know if this is the root cause of the
problem. The OS is Windows 2003 Small Business Server with
SQL Server SP3a.
TIA
Trevor>
> Hi,
> I'm getting "BackupMedium::ReportIoError: write failure on
> backup device 'd:\select
> legal\MSSQL$LEGAL\BACKUP\legal_db_200404
292100.BAK'.
> Operating system error 112(error not found)" messages in
> the SQL 2000 Server logs when we try to backup our
> databases. This is followed by "Internal I/O request
> 0x53BE4B78: Op: Write, pBuffer: 0x0D6A0000, Size: 983040,
> Position: 21632512, UMS: Internal: 0x103, InternalHigh:
> 0x0, Offset: 0x14A1600, OffsetHigh: 0x0, m_buf:
> 0x0D6A0000, m_len: 983040, m_actualBytes: 0, m_errcode:
> 112, BackupFile: d:\select
> legal\MSSQL$LEGAL\BACKUP\legal_db_200404
292100.BAK" and
> then "BACKUP failed to complete the command BACKUP
> DATABASE [legal] TO DISK = N'd:\select
> legal\MSSQL$LEGAL\BACKUP\legal_db_200404
292100.BAK' WITH
> INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT"
> messages. The database is around 300Mb and we have 40Gb of
> free space on the drive.
> The server is Dell PE2600 with a Perc Raid controller
> handling 3 drives in Raid 5 config. These are split into
> two drives; C: for OS and D: for applications and data.
> The smaller system databases back up OK as do the
> transaction logs. I've found a reference to writeback
> cache but don't know if this is the root cause of the
> problem. The OS is Windows 2003 Small Business Server with
> SQL Server SP3a.
> TIA
> Trevor
>
--
Hi Trevor,
Are you using a compressed volume? It is possible that you are out of
diskspace.
Compressed volumes are not supported. Also checkout the following article:
INF: SQL Server and Striped Backups
http://support.microsoft.com/?id=325334
Hope this helps,
Eric Crdenas
SQL Server senior support professional|||Eric Cardenas wrote:
> --
> Hi Trevor,
> Are you using a compressed volume? It is possible that you are out of
> diskspace.
> Compressed volumes are not supported. Also checkout the following
> article:
> INF: SQL Server and Striped Backups
> http://support.microsoft.com/?id=325334
> Hope this helps,
> --
> Eric Cardenas
> SQL Server senior support professional
Eric,
We should have plenty of disk space. The drives aren't compressed as
far as I am aware.
The databases reside on the same drive that we are backing up to.
We are backing up the databases to a folder on the drive using the SQL
Server backup, and then to tape; the actual database files we exclude
from the tape backup.
The server reports around 40Gb of free space on a 60Gb drive, and the
databases that it fails to back up are our main data database which is
around 200Mb to 250Mb in size, and one of the SQL Server system
databases which looks to be only around 25Mb! The other smaller system
databases back up OK.
The drive is on a Raid 5 array which comprises three 60Gb drives.
We can copy and otherwise create large files on the drive without any
problems; we can copy the database files manually with out any problems
(when we shutdown the SQL Server)
It just seems to be the SQL Server backup of the databases that are
reporting an error.
I've seen some references to writeback cache causing a problem like
this, but nothing that I can say "this is how we fix the problem"
I can't believe that the problem is with the raid striping as I would
then expect loads of people to be reporting this.
Trevor
I'm getting "BackupMedium::ReportIoError: write failure on
backup device 'd:\select
legal\MSSQL$LEGAL\BACKUP\legal_db_200404
292100.BAK'.
Operating system error 112(error not found)" messages in
the SQL 2000 Server logs when we try to backup our
databases. This is followed by "Internal I/O request
0x53BE4B78: Op: Write, pBuffer: 0x0D6A0000, Size: 983040,
Position: 21632512, UMS: Internal: 0x103, InternalHigh:
0x0, Offset: 0x14A1600, OffsetHigh: 0x0, m_buf:
0x0D6A0000, m_len: 983040, m_actualBytes: 0, m_errcode:
112, BackupFile: d:\select
legal\MSSQL$LEGAL\BACKUP\legal_db_200404
292100.BAK" and
then "BACKUP failed to complete the command BACKUP
DATABASE [legal] TO DISK = N'd:\select
legal\MSSQL$LEGAL\BACKUP\legal_db_200404
292100.BAK' WITH
INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT"
messages. The database is around 300Mb and we have 40Gb of
free space on the drive.
The server is Dell PE2600 with a Perc Raid controller
handling 3 drives in Raid 5 config. These are split into
two drives; C: for OS and D: for applications and data.
The smaller system databases back up OK as do the
transaction logs. I've found a reference to writeback
cache but don't know if this is the root cause of the
problem. The OS is Windows 2003 Small Business Server with
SQL Server SP3a.
TIA
Trevor>
> Hi,
> I'm getting "BackupMedium::ReportIoError: write failure on
> backup device 'd:\select
> legal\MSSQL$LEGAL\BACKUP\legal_db_200404
292100.BAK'.
> Operating system error 112(error not found)" messages in
> the SQL 2000 Server logs when we try to backup our
> databases. This is followed by "Internal I/O request
> 0x53BE4B78: Op: Write, pBuffer: 0x0D6A0000, Size: 983040,
> Position: 21632512, UMS: Internal: 0x103, InternalHigh:
> 0x0, Offset: 0x14A1600, OffsetHigh: 0x0, m_buf:
> 0x0D6A0000, m_len: 983040, m_actualBytes: 0, m_errcode:
> 112, BackupFile: d:\select
> legal\MSSQL$LEGAL\BACKUP\legal_db_200404
292100.BAK" and
> then "BACKUP failed to complete the command BACKUP
> DATABASE [legal] TO DISK = N'd:\select
> legal\MSSQL$LEGAL\BACKUP\legal_db_200404
292100.BAK' WITH
> INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT"
> messages. The database is around 300Mb and we have 40Gb of
> free space on the drive.
> The server is Dell PE2600 with a Perc Raid controller
> handling 3 drives in Raid 5 config. These are split into
> two drives; C: for OS and D: for applications and data.
> The smaller system databases back up OK as do the
> transaction logs. I've found a reference to writeback
> cache but don't know if this is the root cause of the
> problem. The OS is Windows 2003 Small Business Server with
> SQL Server SP3a.
> TIA
> Trevor
>
--
Hi Trevor,
Are you using a compressed volume? It is possible that you are out of
diskspace.
Compressed volumes are not supported. Also checkout the following article:
INF: SQL Server and Striped Backups
http://support.microsoft.com/?id=325334
Hope this helps,
Eric Crdenas
SQL Server senior support professional|||Eric Cardenas wrote:
> --
> Hi Trevor,
> Are you using a compressed volume? It is possible that you are out of
> diskspace.
> Compressed volumes are not supported. Also checkout the following
> article:
> INF: SQL Server and Striped Backups
> http://support.microsoft.com/?id=325334
> Hope this helps,
> --
> Eric Cardenas
> SQL Server senior support professional
Eric,
We should have plenty of disk space. The drives aren't compressed as
far as I am aware.
The databases reside on the same drive that we are backing up to.
We are backing up the databases to a folder on the drive using the SQL
Server backup, and then to tape; the actual database files we exclude
from the tape backup.
The server reports around 40Gb of free space on a 60Gb drive, and the
databases that it fails to back up are our main data database which is
around 200Mb to 250Mb in size, and one of the SQL Server system
databases which looks to be only around 25Mb! The other smaller system
databases back up OK.
The drive is on a Raid 5 array which comprises three 60Gb drives.
We can copy and otherwise create large files on the drive without any
problems; we can copy the database files manually with out any problems
(when we shutdown the SQL Server)
It just seems to be the SQL Server backup of the databases that are
reporting an error.
I've seen some references to writeback cache causing a problem like
this, but nothing that I can say "this is how we fix the problem"
I can't believe that the problem is with the raid striping as I would
then expect loads of people to be reporting this.
Trevor
Backup problems
Hi,
I'm getting "BackupMedium::ReportIoError: write failure on
backup device 'd:\select
legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK '.
Operating system error 112(error not found)" messages in
the SQL 2000 Server logs when we try to backup our
databases. This is followed by "Internal I/O request
0x53BE4B78: Op: Write, pBuffer: 0x0D6A0000, Size: 983040,
Position: 21632512, UMS: Internal: 0x103, InternalHigh:
0x0, Offset: 0x14A1600, OffsetHigh: 0x0, m_buf:
0x0D6A0000, m_len: 983040, m_actualBytes: 0, m_errcode:
112, BackupFile: d:\select
legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK " and
then "BACKUP failed to complete the command BACKUP
DATABASE [legal] TO DISK = N'd:\select
legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK ' WITH
INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT"
messages. The database is around 300Mb and we have 40Gb of
free space on the drive.
The server is Dell PE2600 with a Perc Raid controller
handling 3 drives in Raid 5 config. These are split into
two drives; C: for OS and D: for applications and data.
The smaller system databases back up OK as do the
transaction logs. I've found a reference to writeback
cache but don't know if this is the root cause of the
problem. The OS is Windows 2003 Small Business Server with
SQL Server SP3a.
TIA
Trevor
>
> Hi,
> I'm getting "BackupMedium::ReportIoError: write failure on
> backup device 'd:\select
> legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK '.
> Operating system error 112(error not found)" messages in
> the SQL 2000 Server logs when we try to backup our
> databases. This is followed by "Internal I/O request
> 0x53BE4B78: Op: Write, pBuffer: 0x0D6A0000, Size: 983040,
> Position: 21632512, UMS: Internal: 0x103, InternalHigh:
> 0x0, Offset: 0x14A1600, OffsetHigh: 0x0, m_buf:
> 0x0D6A0000, m_len: 983040, m_actualBytes: 0, m_errcode:
> 112, BackupFile: d:\select
> legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK " and
> then "BACKUP failed to complete the command BACKUP
> DATABASE [legal] TO DISK = N'd:\select
> legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK ' WITH
> INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT"
> messages. The database is around 300Mb and we have 40Gb of
> free space on the drive.
> The server is Dell PE2600 with a Perc Raid controller
> handling 3 drives in Raid 5 config. These are split into
> two drives; C: for OS and D: for applications and data.
> The smaller system databases back up OK as do the
> transaction logs. I've found a reference to writeback
> cache but don't know if this is the root cause of the
> problem. The OS is Windows 2003 Small Business Server with
> SQL Server SP3a.
> TIA
> Trevor
>
Hi Trevor,
Are you using a compressed volume? It is possible that you are out of
diskspace.
Compressed volumes are not supported. Also checkout the following article:
INF: SQL Server and Striped Backups
http://support.microsoft.com/?id=325334
Hope this helps,
Eric Crdenas
SQL Server senior support professional
|||Eric Cardenas wrote:
> --
> Hi Trevor,
> Are you using a compressed volume? It is possible that you are out of
> diskspace.
> Compressed volumes are not supported. Also checkout the following
> article:
> INF: SQL Server and Striped Backups
> http://support.microsoft.com/?id=325334
> Hope this helps,
> --
> Eric Cardenas
> SQL Server senior support professional
Eric,
We should have plenty of disk space. The drives aren't compressed as
far as I am aware.
The databases reside on the same drive that we are backing up to.
We are backing up the databases to a folder on the drive using the SQL
Server backup, and then to tape; the actual database files we exclude
from the tape backup.
The server reports around 40Gb of free space on a 60Gb drive, and the
databases that it fails to back up are our main data database which is
around 200Mb to 250Mb in size, and one of the SQL Server system
databases which looks to be only around 25Mb! The other smaller system
databases back up OK.
The drive is on a Raid 5 array which comprises three 60Gb drives.
We can copy and otherwise create large files on the drive without any
problems; we can copy the database files manually with out any problems
(when we shutdown the SQL Server)
It just seems to be the SQL Server backup of the databases that are
reporting an error.
I've seen some references to writeback cache causing a problem like
this, but nothing that I can say "this is how we fix the problem"
I can't believe that the problem is with the raid striping as I would
then expect loads of people to be reporting this.
Trevor
I'm getting "BackupMedium::ReportIoError: write failure on
backup device 'd:\select
legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK '.
Operating system error 112(error not found)" messages in
the SQL 2000 Server logs when we try to backup our
databases. This is followed by "Internal I/O request
0x53BE4B78: Op: Write, pBuffer: 0x0D6A0000, Size: 983040,
Position: 21632512, UMS: Internal: 0x103, InternalHigh:
0x0, Offset: 0x14A1600, OffsetHigh: 0x0, m_buf:
0x0D6A0000, m_len: 983040, m_actualBytes: 0, m_errcode:
112, BackupFile: d:\select
legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK " and
then "BACKUP failed to complete the command BACKUP
DATABASE [legal] TO DISK = N'd:\select
legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK ' WITH
INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT"
messages. The database is around 300Mb and we have 40Gb of
free space on the drive.
The server is Dell PE2600 with a Perc Raid controller
handling 3 drives in Raid 5 config. These are split into
two drives; C: for OS and D: for applications and data.
The smaller system databases back up OK as do the
transaction logs. I've found a reference to writeback
cache but don't know if this is the root cause of the
problem. The OS is Windows 2003 Small Business Server with
SQL Server SP3a.
TIA
Trevor
>
> Hi,
> I'm getting "BackupMedium::ReportIoError: write failure on
> backup device 'd:\select
> legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK '.
> Operating system error 112(error not found)" messages in
> the SQL 2000 Server logs when we try to backup our
> databases. This is followed by "Internal I/O request
> 0x53BE4B78: Op: Write, pBuffer: 0x0D6A0000, Size: 983040,
> Position: 21632512, UMS: Internal: 0x103, InternalHigh:
> 0x0, Offset: 0x14A1600, OffsetHigh: 0x0, m_buf:
> 0x0D6A0000, m_len: 983040, m_actualBytes: 0, m_errcode:
> 112, BackupFile: d:\select
> legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK " and
> then "BACKUP failed to complete the command BACKUP
> DATABASE [legal] TO DISK = N'd:\select
> legal\MSSQL$LEGAL\BACKUP\legal_db_200404292100.BAK ' WITH
> INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT"
> messages. The database is around 300Mb and we have 40Gb of
> free space on the drive.
> The server is Dell PE2600 with a Perc Raid controller
> handling 3 drives in Raid 5 config. These are split into
> two drives; C: for OS and D: for applications and data.
> The smaller system databases back up OK as do the
> transaction logs. I've found a reference to writeback
> cache but don't know if this is the root cause of the
> problem. The OS is Windows 2003 Small Business Server with
> SQL Server SP3a.
> TIA
> Trevor
>
Hi Trevor,
Are you using a compressed volume? It is possible that you are out of
diskspace.
Compressed volumes are not supported. Also checkout the following article:
INF: SQL Server and Striped Backups
http://support.microsoft.com/?id=325334
Hope this helps,
Eric Crdenas
SQL Server senior support professional
|||Eric Cardenas wrote:
> --
> Hi Trevor,
> Are you using a compressed volume? It is possible that you are out of
> diskspace.
> Compressed volumes are not supported. Also checkout the following
> article:
> INF: SQL Server and Striped Backups
> http://support.microsoft.com/?id=325334
> Hope this helps,
> --
> Eric Cardenas
> SQL Server senior support professional
Eric,
We should have plenty of disk space. The drives aren't compressed as
far as I am aware.
The databases reside on the same drive that we are backing up to.
We are backing up the databases to a folder on the drive using the SQL
Server backup, and then to tape; the actual database files we exclude
from the tape backup.
The server reports around 40Gb of free space on a 60Gb drive, and the
databases that it fails to back up are our main data database which is
around 200Mb to 250Mb in size, and one of the SQL Server system
databases which looks to be only around 25Mb! The other smaller system
databases back up OK.
The drive is on a Raid 5 array which comprises three 60Gb drives.
We can copy and otherwise create large files on the drive without any
problems; we can copy the database files manually with out any problems
(when we shutdown the SQL Server)
It just seems to be the SQL Server backup of the databases that are
reporting an error.
I've seen some references to writeback cache causing a problem like
this, but nothing that I can say "this is how we fix the problem"
I can't believe that the problem is with the raid striping as I would
then expect loads of people to be reporting this.
Trevor
Thursday, March 8, 2012
Backup or Restore with Stats clause
hi,
I am using Delphi for programing and i am using adocommand for my sql.
I write restore sql with stats clause like this,
"RESTORE DATABASE FINANCE
FROM DISK=C:\FINANCE.BCK
WITH STATS=10"
My problem is how can I read STATS results for my "Progress Bar" process.
Please help?
Best Regards
N.nsal Uslubas
You can add an InfoMessage event handler to your connection object to get
these messages. See
http://msdn.microsoft.com/library/de...fomessage.asp.
Hope this helps.
Dan Guzman
SQL Server MVP
"N.nsal Uslubas via droptable.com" <forum@.droptable.com> wrote in message
news:54015C3C60232@.droptable.com...
> hi,
> I am using Delphi for programing and i am using adocommand for my sql.
> I write restore sql with stats clause like this,
> "RESTORE DATABASE FINANCE
> FROM DISK=C:\FINANCE.BCK
> WITH STATS=10"
> My problem is how can I read STATS results for my "Progress Bar" process.
> Please help?
> Best Regards
> N.nsal Uslubas
I am using Delphi for programing and i am using adocommand for my sql.
I write restore sql with stats clause like this,
"RESTORE DATABASE FINANCE
FROM DISK=C:\FINANCE.BCK
WITH STATS=10"
My problem is how can I read STATS results for my "Progress Bar" process.
Please help?
Best Regards
N.nsal Uslubas
You can add an InfoMessage event handler to your connection object to get
these messages. See
http://msdn.microsoft.com/library/de...fomessage.asp.
Hope this helps.
Dan Guzman
SQL Server MVP
"N.nsal Uslubas via droptable.com" <forum@.droptable.com> wrote in message
news:54015C3C60232@.droptable.com...
> hi,
> I am using Delphi for programing and i am using adocommand for my sql.
> I write restore sql with stats clause like this,
> "RESTORE DATABASE FINANCE
> FROM DISK=C:\FINANCE.BCK
> WITH STATS=10"
> My problem is how can I read STATS results for my "Progress Bar" process.
> Please help?
> Best Regards
> N.nsal Uslubas
Backup or Restore with Stats clause
hi,
I am using Delphi for programing and i am using adocommand for my sql.
I write restore sql with stats clause like this,
"RESTORE DATABASE FINANCE
FROM DISK=C:\FINANCE.BCK
WITH STATS=10"
My problem is how can I read STATS results for my "Progress Bar" process.
Please help?
Best Regards
N.Ünsal UslubasYou can add an InfoMessage event handler to your connection object to get
these messages. See
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdevtinfomessage.asp.
Hope this helps.
Dan Guzman
SQL Server MVP
"N.Ünsal Uslubas via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:54015C3C60232@.SQLMonster.com...
> hi,
> I am using Delphi for programing and i am using adocommand for my sql.
> I write restore sql with stats clause like this,
> "RESTORE DATABASE FINANCE
> FROM DISK=C:\FINANCE.BCK
> WITH STATS=10"
> My problem is how can I read STATS results for my "Progress Bar" process.
> Please help?
> Best Regards
> N.Ünsal Uslubas
I am using Delphi for programing and i am using adocommand for my sql.
I write restore sql with stats clause like this,
"RESTORE DATABASE FINANCE
FROM DISK=C:\FINANCE.BCK
WITH STATS=10"
My problem is how can I read STATS results for my "Progress Bar" process.
Please help?
Best Regards
N.Ünsal UslubasYou can add an InfoMessage event handler to your connection object to get
these messages. See
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdevtinfomessage.asp.
Hope this helps.
Dan Guzman
SQL Server MVP
"N.Ünsal Uslubas via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:54015C3C60232@.SQLMonster.com...
> hi,
> I am using Delphi for programing and i am using adocommand for my sql.
> I write restore sql with stats clause like this,
> "RESTORE DATABASE FINANCE
> FROM DISK=C:\FINANCE.BCK
> WITH STATS=10"
> My problem is how can I read STATS results for my "Progress Bar" process.
> Please help?
> Best Regards
> N.Ünsal Uslubas
Backup or Restore with Stats clause
hi,
I am using Delphi for programing and i am using adocommand for my sql.
I write restore sql with stats clause like this,
"RESTORE DATABASE FINANCE
FROM DISK=C:\FINANCE.BCK
WITH STATS=10"
My problem is how can I read STATS results for my "Progress Bar" process.
Please help?
Best Regards
N.nsal UslubasYou can add an InfoMessage event handler to your connection object to get
these messages. See
http://msdn.microsoft.com/library/d...nfomessage.asp.
Hope this helps.
Dan Guzman
SQL Server MVP
"N.nsal Uslubas via droptable.com" <forum@.droptable.com> wrote in message
news:54015C3C60232@.droptable.com...
> hi,
> I am using Delphi for programing and i am using adocommand for my sql.
> I write restore sql with stats clause like this,
> "RESTORE DATABASE FINANCE
> FROM DISK=C:\FINANCE.BCK
> WITH STATS=10"
> My problem is how can I read STATS results for my "Progress Bar" process.
> Please help?
> Best Regards
> N.nsal Uslubas
I am using Delphi for programing and i am using adocommand for my sql.
I write restore sql with stats clause like this,
"RESTORE DATABASE FINANCE
FROM DISK=C:\FINANCE.BCK
WITH STATS=10"
My problem is how can I read STATS results for my "Progress Bar" process.
Please help?
Best Regards
N.nsal UslubasYou can add an InfoMessage event handler to your connection object to get
these messages. See
http://msdn.microsoft.com/library/d...nfomessage.asp.
Hope this helps.
Dan Guzman
SQL Server MVP
"N.nsal Uslubas via droptable.com" <forum@.droptable.com> wrote in message
news:54015C3C60232@.droptable.com...
> hi,
> I am using Delphi for programing and i am using adocommand for my sql.
> I write restore sql with stats clause like this,
> "RESTORE DATABASE FINANCE
> FROM DISK=C:\FINANCE.BCK
> WITH STATS=10"
> My problem is how can I read STATS results for my "Progress Bar" process.
> Please help?
> Best Regards
> N.nsal Uslubas
Friday, February 24, 2012
Backup Master key, Cannot write into file 'c:\temp\master'. Verify that you have write permiss
Hi,
I tried to backup the master key by the following syntax :
OPEN MASTER KEY DECRYPTION BY PASSWORD = 'mypassword'
BACKUP MASTER KEY TO FILE = 'c:\temp\master' ENCRYPTION BY PASSWORD = 'mypassword'
but it failed and i got the following message:
Cannot write into file 'c:\temp\master'. Verify that you have write permissions, that the file path is valid, and that the file does not already exist.
NB: I am using the "sa" user to execute this command.
I know that we have a security permission issue , but where and how ?
Regards,
Tarek Ghazali
SQL Server MVP
In this case the permissions check are done by Windows to verify that the SQL Server service account has access to create the file. Most likely you are running SQL Server using a low privileged domain account (which is highly recommended). To check the name of the service account being used, you can use SQL Server Configuration Manager (SCM).
Rather than granting permissions directly to this service account on local Windows resources, you can grant the permissions to the corresponding Windows group that SQL Server 2005 setup created for you. You can find the name of this group in the local users and groups management tool in Windows (Computer Management tool).
The name for the SQL Server 2005 groups should be based on the following pattern:
SQLServer2005MSSQLUser$<<Server_name>>$<<Instance_name >>
For example: SQLServer2005MSSQLUser$MY_SERVER$MSSQLSERVER
Once you have found the name for the service account group, you can grant the proper permissions on Windows resources (such as write permissions on folders or read permissions on files you need to import).
I hope this information will help you,
-Raul Garcia
SDE/T
SQL Server Engine
|||Hi Raul,
first Thanks for your reply.
I tried that also but it didn't work,
Any other idea ?
Thanks,
Tarek Ghazali
SQL Server MVP
Web site: www.sqlmvp.com
|||I forgot another reason why backup may fail: the backup operations for keys won’t replace any files, make sure the file name is unique. Let me know if changing the name of the file worked.
BTW. If you create backups of your master keys on a regular schedule and regenerate the keys (which is highly recommended), it is a good idea to keep an archive of your old keys (protected in a safe place) in case you need to access data from some old backup.
Thanks,
-Raul Garcia
SDE/T
SQL Server Engine
Backup Master key, Cannot write into file 'c:\temp\master'. Verify that you have write per
Hi,
I tried to backup the master key by the following syntax :
OPEN MASTER KEY DECRYPTION BY PASSWORD = 'mypassword'
BACKUP MASTER KEY TO FILE = 'c:\temp\master' ENCRYPTION BY PASSWORD = 'mypassword'
but it failed and i got the following message:
Cannot write into file 'c:\temp\master'. Verify that you have write permissions, that the file path is valid, and that the file does not already exist.
NB: I am using the "sa" user to execute this command.
I know that we have a security permission issue , but where and how ?
Regards,
Tarek Ghazali
SQL Server MVP
In this case the permissions check are done by Windows to verify that the SQL Server service account has access to create the file. Most likely you are running SQL Server using a low privileged domain account (which is highly recommended). To check the name of the service account being used, you can use SQL Server Configuration Manager (SCM).
Rather than granting permissions directly to this service account on local Windows resources, you can grant the permissions to the corresponding Windows group that SQL Server 2005 setup created for you. You can find the name of this group in the local users and groups management tool in Windows (Computer Management tool).
The name for the SQL Server 2005 groups should be based on the following pattern:
SQLServer2005MSSQLUser$<<Server_name>>$<<Instance_name >>
For example: SQLServer2005MSSQLUser$MY_SERVER$MSSQLSERVER
Once you have found the name for the service account group, you can grant the proper permissions on Windows resources (such as write permissions on folders or read permissions on files you need to import).
I hope this information will help you,
-Raul Garcia
SDE/T
SQL Server Engine
|||Hi Raul,
first Thanks for your reply.
I tried that also but it didn't work,
Any other idea ?
Thanks,
Tarek Ghazali
SQL Server MVP
Web site: www.sqlmvp.com
|||I forgot another reason why backup may fail: the backup operations for keys won’t replace any files, make sure the file name is unique. Let me know if changing the name of the file worked.
BTW. If you create backups of your master keys on a regular schedule and regenerate the keys (which is highly recommended), it is a good idea to keep an archive of your old keys (protected in a safe place) in case you need to access data from some old backup.
Thanks,
-Raul Garcia
SDE/T
SQL Server Engine
Thursday, February 16, 2012
backup log terminated abormally
I backup the transaction log unsuccessfully.
It pops up :
Error Box Title : Microsoft SQL-DMO(ODBC SQLState 42000)
DetailMessgae : Write
on 'c:\MSSQL\Backup\mydata_db_2004043.BAK' failed, status
=112.
Has anyone experienced this before or knows what is
going wrong ?You can type 'NET HELPMSG 112' from a command prompt window to get the
following Windows error message text:
There is not enough space on the disk.
Try the backup again after freeing some disk space.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:618b01c481ad$b566e040$a401280a@.phx.gbl...
> I backup the transaction log unsuccessfully.
> It pops up :
> Error Box Title : Microsoft SQL-DMO(ODBC SQLState 42000)
> DetailMessgae : Write
> on 'c:\MSSQL\Backup\mydata_db_2004043.BAK' failed, status
> =112.
> Has anyone experienced this before or knows what is
> going wrong ?
>|||Thanks Dan for the answers...
>--Original Message--
>You can type 'NET HELPMSG 112' from a command prompt
window to get the
>following Windows error message text:
> There is not enough space on the disk.
>Try the backup again after freeing some disk space.
>--
>Hope this helps.
>Dan Guzman
>SQL Server MVP
>"Newbie" <anonymous@.discussions.microsoft.com> wrote in
message
>news:618b01c481ad$b566e040$a401280a@.phx.gbl...
>> I backup the transaction log unsuccessfully.
>> It pops up :
>> Error Box Title : Microsoft SQL-DMO(ODBC SQLState
42000)
>> DetailMessgae : Write
>> on 'c:\MSSQL\Backup\mydata_db_2004043.BAK' failed,
status
>> =112.
>> Has anyone experienced this before or knows what is
>> going wrong ?
>>
>
>.
>
It pops up :
Error Box Title : Microsoft SQL-DMO(ODBC SQLState 42000)
DetailMessgae : Write
on 'c:\MSSQL\Backup\mydata_db_2004043.BAK' failed, status
=112.
Has anyone experienced this before or knows what is
going wrong ?You can type 'NET HELPMSG 112' from a command prompt window to get the
following Windows error message text:
There is not enough space on the disk.
Try the backup again after freeing some disk space.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:618b01c481ad$b566e040$a401280a@.phx.gbl...
> I backup the transaction log unsuccessfully.
> It pops up :
> Error Box Title : Microsoft SQL-DMO(ODBC SQLState 42000)
> DetailMessgae : Write
> on 'c:\MSSQL\Backup\mydata_db_2004043.BAK' failed, status
> =112.
> Has anyone experienced this before or knows what is
> going wrong ?
>|||Thanks Dan for the answers...
>--Original Message--
>You can type 'NET HELPMSG 112' from a command prompt
window to get the
>following Windows error message text:
> There is not enough space on the disk.
>Try the backup again after freeing some disk space.
>--
>Hope this helps.
>Dan Guzman
>SQL Server MVP
>"Newbie" <anonymous@.discussions.microsoft.com> wrote in
message
>news:618b01c481ad$b566e040$a401280a@.phx.gbl...
>> I backup the transaction log unsuccessfully.
>> It pops up :
>> Error Box Title : Microsoft SQL-DMO(ODBC SQLState
42000)
>> DetailMessgae : Write
>> on 'c:\MSSQL\Backup\mydata_db_2004043.BAK' failed,
status
>> =112.
>> Has anyone experienced this before or knows what is
>> going wrong ?
>>
>
>.
>
Subscribe to:
Posts (Atom)