Backup failed: Operating system error 112(error not found).

Hi,
I keep getting this error message for a trans.log backup.
Operating system error
112(error not found).
The disk has about 6GB space free, and the backup should only take up
about 550 MB, so I would think it is not space related but...
The disk is NTFS.
Any ideas?smeagol (carlamichelle1@.hotmail.com) writes:
> I keep getting this error message for a trans.log backup.
> Operating system error
> 112(error not found).
> The disk has about 6GB space free, and the backup should only take up
> about 550 MB, so I would think it is not space related but...

... but NET HELPMSG 112 says

There is not enough space on the disk.

> The disk is NTFS.
> Any ideas?

Not many. I would perform all sorts of sanity checks that you are looking
on the right disk, that the transaction log is small as you believe it
to be etc.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Did you ever get this sorted ?
I'm having the same problem and have heaps of free disk space ? :confused:sql

Backup DB, but without one table

Hi,
I have a giant DB that I want to backup. One of it's table is taking a lot of space, and I don't need it in the backup, so I am searching for a way to backup everything but that table in particular.

Does any of you know of a way?
Thanks!

BTW, it's a Microsoft SQL Server 2000 - 8.00.2040 (Intel X86)Only way to do it is pretty ugly. You would need to BCP out all the data, and script all the objects in the database. This would still miss users and groups, however.|||Thanks for the quick answer man!
Then I'll change the question:
My original need is to setup a test DB server. I thought the best & easiest way to build it up was with a backup/restore. Of course, I came across this issue: my test server cannot hold all the data, and getting rid of this table was the solution.
Any bypass solution?
Thanks again,
Francisco.|||Slightly easier, then would be to generate the SQL script of all objects, and run that on the test database. After this, you can import any set of tables (and even a portion of the big table) into the test server. You will still need to create users, roles and make sure the permissions are correct, but the script will likely take care of most of that.|||There are ways to accomplish this IF you can change the production system. That isn't usually an option, so for now I'll disregard it.

I'd approach this problem by:

1) Scripting out the DDL needed to create the tables only (no constraints, no indicies, no code, no permissions, just the tables). Play this script into the currently empty test database.

2) Use either BCP or DTS to copy the data from the tables you need copied from the production database to the test database.

3) Script out the remainder of the schema (the parts you left out of the first script) from the production database, and play that script in the populated test database.

-PatPsql

Backup DB on compressed folder

Hi I have a very strange case here.
Currently our db server is short of space and as a temp solution database is backed up to a compressed folder. OS is W2K advanced Edition and SQL is Enterprise version. Database is 62GB now. every time Db backup fails after backup running for 2hrs and hal
f. the error msg says that "18210 :
BackupMedium::ReportIoError: write failure on backup device 'd:\mssql\backup\DataDMP01.BAK'. Operating system error 33(The process cannot access the file because another process has locked a portion of the file.)."
we have tried another file name or rebooting the server, but none helps.
I doubt that compressed fold causes the problem or exceeds the file size limit, but can not find any clue on it.
Pls help.
thanks for reply.
George
Compressed drives are not supported for sql server databases and to the best
of my knowledge backups either. If you are low on disk space I would
suggest using a product such as SQL LiteSpeed.
Andrew J. Kelly SQL MVP
"george" <georgey@.cryptologic.com> wrote in message
news:D916C3F2-92F3-405C-9951-39D3E1D095CC@.microsoft.com...
> Hi I have a very strange case here.
> Currently our db server is short of space and as a temp solution database
is backed up to a compressed folder. OS is W2K advanced Edition and SQL is
Enterprise version. Database is 62GB now. every time Db backup fails after
backup running for 2hrs and half. the error msg says that "18210 :
> BackupMedium::ReportIoError: write failure on backup device
'd:\mssql\backup\DataDMP01.BAK'. Operating system error 33(The process
cannot access the file because another process has locked a portion of the
file.)."
> we have tried another file name or rebooting the server, but none helps.
> I doubt that compressed fold causes the problem or exceeds the file size
limit, but can not find any clue on it.
> Pls help.
> thanks for reply.
> George

Backup DB on compressed folder

Hi I have a very strange case here.
Currently our db server is short of space and as a temp solution database is
backed up to a compressed folder. OS is W2K advanced Edition and SQL is Ent
erprise version. Database is 62GB now. every time Db backup fails after back
up running for 2hrs and hal
f. the error msg says that "18210 :
BackupMedium::ReportIoError: write failure on backup device 'd:\mssql\backup
\DataDMP01.BAK'. Operating system error 33(The process cannot access the fil
e because another process has locked a portion of the file.)."
we have tried another file name or rebooting the server, but none helps.
I doubt that compressed fold causes the problem or exceeds the file size lim
it, but can not find any clue on it.
Pls help.
thanks for reply.
GeorgeCompressed drives are not supported for sql server databases and to the best
of my knowledge backups either. If you are low on disk space I would
suggest using a product such as SQL LiteSpeed.
Andrew J. Kelly SQL MVP
"george" <georgey@.cryptologic.com> wrote in message
news:D916C3F2-92F3-405C-9951-39D3E1D095CC@.microsoft.com...
> Hi I have a very strange case here.
> Currently our db server is short of space and as a temp solution database
is backed up to a compressed folder. OS is W2K advanced Edition and SQL is
Enterprise version. Database is 62GB now. every time Db backup fails after
backup running for 2hrs and half. the error msg says that "18210 :
> BackupMedium::ReportIoError: write failure on backup device
'd:\mssql\backup\DataDMP01.BAK'. Operating system error 33(The process
cannot access the file because another process has locked a portion of the
file.)."
> we have tried another file name or rebooting the server, but none helps.
> I doubt that compressed fold causes the problem or exceeds the file size
limit, but can not find any clue on it.
> Pls help.
> thanks for reply.
> George

Backup Database Maintenance Plan eats up too much disk space

I created a basic DB maintenance plan to routinely backup our database.
Every backup job that runs through this plan is created using a unique name,
putting the date into the back file name, as in
DBProduction_db_200401120000.bak.
The problem is this creates a new backup file each day - our backups our
faily large and after only a few days, the drive space is completely used
up.
What is the best way to solve this problem? Currently, we manually remove
the older backup files. Is there an automated way to have SQL delete files
older than a given number of days - for example, remove all files older than
3 days. When we do a log ship using a maintenance plan, it asks for this
information, but I haven't seen it when just running basic back ups and
transaction log back ups.
What about changing the default name to something like 'DailyDBBackup.bak'
so that it just overwrites previous backup everytime?> What is the best way to solve this problem? Currently, we manually remove

quote:

---

> the older backup files. Is there an automated way to have SQL delete

---

files

quote:

---

> older than a given number of days - for example, remove all files older

---

than

quote:

---

> 3 days.

---

Run through the maint wiz again and you will find just that option :-).
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Dave Slinn" <dslinn@.gms.ca> wrote in message
news:OtxsPCc5DHA.564@.TK2MSFTNGP10.phx.gbl...

quote:

---

> I created a basic DB maintenance plan to routinely backup our database.
> Every backup job that runs through this plan is created using a unique

---

name,

quote:

---

> putting the date into the back file name, as in
> DBProduction_db_200401120000.bak.
> The problem is this creates a new backup file each day - our backups our
> faily large and after only a few days, the drive space is completely used
> up.
> What is the best way to solve this problem? Currently, we manually remove
> the older backup files. Is there an automated way to have SQL delete

---

files

quote:

---

> older than a given number of days - for example, remove all files older

---

than

quote:

---

> 3 days. When we do a log ship using a maintenance plan, it asks for this
> information, but I haven't seen it when just running basic back ups and
> transaction log back ups.
> What about changing the default name to something like 'DailyDBBackup.bak'
> so that it just overwrites previous backup everytime?
>
>

---

|||D-oh! I feel so stupid...
Thanks Tibor!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eU$VRHc5DHA.360@.TK2MSFTNGP12.phx.gbl...

quote:

---

remove[QUOTE]
> files
> than
> Run through the maint wiz again and you will find just that option :-).
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
>

---

http://groups.google.com/groups?oi=...ublic.sqlserver

quote:

---

>
> "Dave Slinn" <dslinn@.gms.ca> wrote in message
> news:OtxsPCc5DHA.564@.TK2MSFTNGP10.phx.gbl...
> name,
used[QUOTE]
remove[QUOTE]
> files
> than
this[QUOTE]
'DailyDBBackup.bak'[QUOTE]
>

---

Backup Database Maintenance Plan eats up too much disk space

I created a basic DB maintenance plan to routinely backup our database.
Every backup job that runs through this plan is created using a unique name,
putting the date into the back file name, as in
DBProduction_db_200401120000.bak.
The problem is this creates a new backup file each day - our backups our
faily large and after only a few days, the drive space is completely used
up.
What is the best way to solve this problem? Currently, we manually remove
the older backup files. Is there an automated way to have SQL delete files
older than a given number of days - for example, remove all files older than
3 days. When we do a log ship using a maintenance plan, it asks for this
information, but I haven't seen it when just running basic back ups and
transaction log back ups.
What about changing the default name to something like 'DailyDBBackup.bak'
so that it just overwrites previous backup everytime?> What is the best way to solve this problem? Currently, we manually remove
> the older backup files. Is there an automated way to have SQL delete
files
> older than a given number of days - for example, remove all files older
than
> 3 days.
Run through the maint wiz again and you will find just that option :-).
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Dave Slinn" <dslinn@.gms.ca> wrote in message
news:OtxsPCc5DHA.564@.TK2MSFTNGP10.phx.gbl...
> I created a basic DB maintenance plan to routinely backup our database.
> Every backup job that runs through this plan is created using a unique
name,
> putting the date into the back file name, as in
> DBProduction_db_200401120000.bak.
> The problem is this creates a new backup file each day - our backups our
> faily large and after only a few days, the drive space is completely used
> up.
> What is the best way to solve this problem? Currently, we manually remove
> the older backup files. Is there an automated way to have SQL delete
files
> older than a given number of days - for example, remove all files older
than
> 3 days. When we do a log ship using a maintenance plan, it asks for this
> information, but I haven't seen it when just running basic back ups and
> transaction log back ups.
> What about changing the default name to something like 'DailyDBBackup.bak'
> so that it just overwrites previous backup everytime?
>
>|||D-oh! I feel so stupid...
Thanks Tibor!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eU$VRHc5DHA.360@.TK2MSFTNGP12.phx.gbl...
> > What is the best way to solve this problem? Currently, we manually
remove
> > the older backup files. Is there an automated way to have SQL delete
> files
> > older than a given number of days - for example, remove all files older
> than
> > 3 days.
> Run through the maint wiz again and you will find just that option :-).
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Dave Slinn" <dslinn@.gms.ca> wrote in message
> news:OtxsPCc5DHA.564@.TK2MSFTNGP10.phx.gbl...
> > I created a basic DB maintenance plan to routinely backup our database.
> > Every backup job that runs through this plan is created using a unique
> name,
> > putting the date into the back file name, as in
> > DBProduction_db_200401120000.bak.
> >
> > The problem is this creates a new backup file each day - our backups our
> > faily large and after only a few days, the drive space is completely
used
> > up.
> >
> > What is the best way to solve this problem? Currently, we manually
remove
> > the older backup files. Is there an automated way to have SQL delete
> files
> > older than a given number of days - for example, remove all files older
> than
> > 3 days. When we do a log ship using a maintenance plan, it asks for
this
> > information, but I haven't seen it when just running basic back ups and
> > transaction log back ups.
> >
> > What about changing the default name to something like
'DailyDBBackup.bak'
> > so that it just overwrites previous backup everytime?
> >
> >
> >
>

backup

My backups have been successful until last week. I am suddenly getting the
message telling me there is not enough space on the disk. The disk has 215gb
of free space. I am backing up to an external firewire hardrive. I can
successfully do a backup to the same disk as the database.
I do a differential backup on certain days and a full back up on others. I
append the transaction logs to the backup.
The database is only 18gb.
Any ideas why this is happening?log file size ?
scott
"Curtis" <Curtis@.discussions.microsoft.com> wrote in message
news:D8773822-D6B8-44A6-A2A7-DA981D5081D3@.microsoft.com...
> My backups have been successful until last week. I am suddenly getting the
> message telling me there is not enough space on the disk. The disk has
> 215gb
> of free space. I am backing up to an external firewire hardrive. I can
> successfully do a backup to the same disk as the database.
> I do a differential backup on certain days and a full back up on others. I
> append the transaction logs to the backup.
> The database is only 18gb.
> Any ideas why this is happening?|||The log file is 13.2 gb. The log says the transaction log portion of the
backup was successful. It seems to fail on the full and differential.
"scott" wrote:
> log file size ?
> scott
> "Curtis" <Curtis@.discussions.microsoft.com> wrote in message
> news:D8773822-D6B8-44A6-A2A7-DA981D5081D3@.microsoft.com...
> > My backups have been successful until last week. I am suddenly getting the
> > message telling me there is not enough space on the disk. The disk has
> > 215gb
> > of free space. I am backing up to an external firewire hardrive. I can
> > successfully do a backup to the same disk as the database.
> >
> > I do a differential backup on certain days and a full back up on others. I
> > append the transaction logs to the backup.
> >
> > The database is only 18gb.
> >
> > Any ideas why this is happening?
>
>|||How do you perform BACKUP operation? In two /three steps?
What does the ERROR.LOG say?
"Curtis" <Curtis@.discussions.microsoft.com> wrote in message
news:AE908938-E143-46E1-AA98-9860EBDD4E3F@.microsoft.com...
> The log file is 13.2 gb. The log says the transaction log portion of the
> backup was successful. It seems to fail on the full and differential.
> "scott" wrote:
>> log file size ?
>> scott
>> "Curtis" <Curtis@.discussions.microsoft.com> wrote in message
>> news:D8773822-D6B8-44A6-A2A7-DA981D5081D3@.microsoft.com...
>> > My backups have been successful until last week. I am suddenly getting
>> > the
>> > message telling me there is not enough space on the disk. The disk has
>> > 215gb
>> > of free space. I am backing up to an external firewire hardrive. I can
>> > successfully do a backup to the same disk as the database.
>> >
>> > I do a differential backup on certain days and a full back up on
>> > others. I
>> > append the transaction logs to the backup.
>> >
>> > The database is only 18gb.
>> >
>> > Any ideas why this is happening?
>>|||I have a maintenance plan set up. Full/Differential are executed first and
then I append the transaction log to the backup.
Executing the query "BACKUP LOG [Database] TO [ WK 4 SU Full] WITH
NOFORMAT, NOINIT, NAME = N'backup_20060827211052', SKIP, REWIND, NOUNLOAD,
STATS = 10
" failed with the following error: "Write on "WK 4 SU Full(I:\\Week 4\\WK 4
SU Full)" failed: 112(There is not enough space on the disk.)
BACKUP LOG is terminating abnormally.". Possible failure reasons: Problems
with the query, "ResultSet" property not set correctly, parameters not set
correctly, or connection not established correctly.
"Uri Dimant" wrote:
> How do you perform BACKUP operation? In two /three steps?
> What does the ERROR.LOG say?
>
> "Curtis" <Curtis@.discussions.microsoft.com> wrote in message
> news:AE908938-E143-46E1-AA98-9860EBDD4E3F@.microsoft.com...
> > The log file is 13.2 gb. The log says the transaction log portion of the
> > backup was successful. It seems to fail on the full and differential.
> >
> > "scott" wrote:
> >
> >> log file size ?
> >>
> >> scott
> >>
> >> "Curtis" <Curtis@.discussions.microsoft.com> wrote in message
> >> news:D8773822-D6B8-44A6-A2A7-DA981D5081D3@.microsoft.com...
> >> > My backups have been successful until last week. I am suddenly getting
> >> > the
> >> > message telling me there is not enough space on the disk. The disk has
> >> > 215gb
> >> > of free space. I am backing up to an external firewire hardrive. I can
> >> > successfully do a backup to the same disk as the database.
> >> >
> >> > I do a differential backup on certain days and a full back up on
> >> > others. I
> >> > append the transaction logs to the backup.
> >> >
> >> > The database is only 18gb.
> >> >
> >> > Any ideas why this is happening?
> >>
> >>
> >>
>
>

backup

My backups have been successful until last week. I am suddenly getting the
message telling me there is not enough space on the disk. The disk has 215gb
of free space. I am backing up to an external firewire hardrive. I can
successfully do a backup to the same disk as the database.
I do a differential backup on certain days and a full back up on others. I
append the transaction logs to the backup.
The database is only 18gb.
Any ideas why this is happening?log file size ?
scott
"Curtis" <Curtis@.discussions.microsoft.com> wrote in message
news:D8773822-D6B8-44A6-A2A7-DA981D5081D3@.microsoft.com...
> My backups have been successful until last week. I am suddenly getting the
> message telling me there is not enough space on the disk. The disk has
> 215gb
> of free space. I am backing up to an external firewire hardrive. I can
> successfully do a backup to the same disk as the database.
> I do a differential backup on certain days and a full back up on others. I
> append the transaction logs to the backup.
> The database is only 18gb.
> Any ideas why this is happening?|||The log file is 13.2 gb. The log says the transaction log portion of the
backup was successful. It seems to fail on the full and differential.
"scott" wrote:

> log file size ?
> scott
> "Curtis" <Curtis@.discussions.microsoft.com> wrote in message
> news:D8773822-D6B8-44A6-A2A7-DA981D5081D3@.microsoft.com...
>
>|||How do you perform BACKUP operation? In two /three steps?
What does the ERROR.LOG say?
"Curtis" <Curtis@.discussions.microsoft.com> wrote in message
news:AE908938-E143-46E1-AA98-9860EBDD4E3F@.microsoft.com...[vbcol=seagreen]
> The log file is 13.2 gb. The log says the transaction log portion of the
> backup was successful. It seems to fail on the full and differential.
> "scott" wrote:
>|||I have a maintenance plan set up. Full/Differential are executed first and
then I append the transaction log to the backup.
Executing the query "BACKUP LOG [Database] TO [ WK 4 SU Full] WITH
NOFORMAT, NOINIT, NAME = N'backup_20060827211052', SKIP, REWIND, NOUNLOAD,
STATS = 10
" failed with the following error: "Write on "WK 4 SU Full(I:\\Week 4\\WK 4
SU Full)" failed: 112(There is not enough space on the disk.)
BACKUP LOG is terminating abnormally.". Possible failure reasons: Problems
with the query, "ResultSet" property not set correctly, parameters not set
correctly, or connection not established correctly.
"Uri Dimant" wrote:

> How do you perform BACKUP operation? In two /three steps?
> What does the ERROR.LOG say?
>
> "Curtis" <Curtis@.discussions.microsoft.com> wrote in message
> news:AE908938-E143-46E1-AA98-9860EBDD4E3F@.microsoft.com...
>
>