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
Showing posts with label strange. Show all posts
Showing posts with label strange. Show all posts
Tuesday, March 20, 2012
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
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
Wednesday, March 7, 2012
Backup and Restore issue
I have a strange case. I do a full backup this morning. The size of
the backup is about 300MB which is 4 times larger than the actual
database file. Now when I restore the backup, some of the objects (eg
some tables) are not there!!.
Now I just do another backup, the size of this backup is now about
80MB, which is normal and when I restore this backup, I got all the
tables.
What am I missing? Did someone has similar experience?
Probably earlier you would have appended to a older backup file (WITH NOINIT
which is default).
That caused the backup file to show a bigger size. While restoring you
restore the first backup file
which was taken some days back and that do not have some new tables.
This is just my assumption. If you have the backup file which you has issues
just try
RESTORE HEADERONLY FROM DISK='Backupfilename.BAK'
The above command will give you all the backup sets in the backup file.
Thanks
Hari
"akkha1234@.gmail.com" wrote:
> I have a strange case. I do a full backup this morning. The size of
> the backup is about 300MB which is 4 times larger than the actual
> database file. Now when I restore the backup, some of the objects (eg
> some tables) are not there!!.
> Now I just do another backup, the size of this backup is now about
> 80MB, which is normal and when I restore this backup, I got all the
> tables.
> What am I missing? Did someone has similar experience?
>
|||Dear Hari,
You are absolutely correct. Learn one more thing on MSSQL again.
the backup is about 300MB which is 4 times larger than the actual
database file. Now when I restore the backup, some of the objects (eg
some tables) are not there!!.
Now I just do another backup, the size of this backup is now about
80MB, which is normal and when I restore this backup, I got all the
tables.
What am I missing? Did someone has similar experience?
Probably earlier you would have appended to a older backup file (WITH NOINIT
which is default).
That caused the backup file to show a bigger size. While restoring you
restore the first backup file
which was taken some days back and that do not have some new tables.
This is just my assumption. If you have the backup file which you has issues
just try
RESTORE HEADERONLY FROM DISK='Backupfilename.BAK'
The above command will give you all the backup sets in the backup file.
Thanks
Hari
"akkha1234@.gmail.com" wrote:
> I have a strange case. I do a full backup this morning. The size of
> the backup is about 300MB which is 4 times larger than the actual
> database file. Now when I restore the backup, some of the objects (eg
> some tables) are not there!!.
> Now I just do another backup, the size of this backup is now about
> 80MB, which is normal and when I restore this backup, I got all the
> tables.
> What am I missing? Did someone has similar experience?
>
|||Dear Hari,
You are absolutely correct. Learn one more thing on MSSQL again.
Backup and Restore issue
I have a strange case. I do a full backup this morning. The size of
the backup is about 300MB which is 4 times larger than the actual
database file. Now when I restore the backup, some of the objects (eg
some tables) are not there!!.
Now I just do another backup, the size of this backup is now about
80MB, which is normal and when I restore this backup, I got all the
tables.
What am I missing? Did someone has similar experience?Probably earlier you would have appended to a older backup file (WITH NOINIT
which is default).
That caused the backup file to show a bigger size. While restoring you
restore the first backup file
which was taken some days back and that do not have some new tables.
This is just my assumption. If you have the backup file which you has issues
just try
RESTORE HEADERONLY FROM DISK='Backupfilename.BAK'
The above command will give you all the backup sets in the backup file.
Thanks
Hari
"akkha1234@.gmail.com" wrote:
> I have a strange case. I do a full backup this morning. The size of
> the backup is about 300MB which is 4 times larger than the actual
> database file. Now when I restore the backup, some of the objects (eg
> some tables) are not there!!.
> Now I just do another backup, the size of this backup is now about
> 80MB, which is normal and when I restore this backup, I got all the
> tables.
> What am I missing? Did someone has similar experience?
>|||Dear Hari,
You are absolutely correct. Learn one more thing on MSSQL again.|||Thats good to know...
Thanks
Hari
<akkha1234@.gmail.com> wrote in message
news:1170369045.337711.234660@.l53g2000cwa.googlegroups.com...
> Dear Hari,
> You are absolutely correct. Learn one more thing on MSSQL again.
>
the backup is about 300MB which is 4 times larger than the actual
database file. Now when I restore the backup, some of the objects (eg
some tables) are not there!!.
Now I just do another backup, the size of this backup is now about
80MB, which is normal and when I restore this backup, I got all the
tables.
What am I missing? Did someone has similar experience?Probably earlier you would have appended to a older backup file (WITH NOINIT
which is default).
That caused the backup file to show a bigger size. While restoring you
restore the first backup file
which was taken some days back and that do not have some new tables.
This is just my assumption. If you have the backup file which you has issues
just try
RESTORE HEADERONLY FROM DISK='Backupfilename.BAK'
The above command will give you all the backup sets in the backup file.
Thanks
Hari
"akkha1234@.gmail.com" wrote:
> I have a strange case. I do a full backup this morning. The size of
> the backup is about 300MB which is 4 times larger than the actual
> database file. Now when I restore the backup, some of the objects (eg
> some tables) are not there!!.
> Now I just do another backup, the size of this backup is now about
> 80MB, which is normal and when I restore this backup, I got all the
> tables.
> What am I missing? Did someone has similar experience?
>|||Dear Hari,
You are absolutely correct. Learn one more thing on MSSQL again.|||Thats good to know...
Thanks
Hari
<akkha1234@.gmail.com> wrote in message
news:1170369045.337711.234660@.l53g2000cwa.googlegroups.com...
> Dear Hari,
> You are absolutely correct. Learn one more thing on MSSQL again.
>
Backup and Restore issue
I have a strange case. I do a full backup this morning. The size of
the backup is about 300MB which is 4 times larger than the actual
database file. Now when I restore the backup, some of the objects (eg
some tables) are not there!!.
Now I just do another backup, the size of this backup is now about
80MB, which is normal and when I restore this backup, I got all the
tables.
What am I missing? Did someone has similar experience?Probably earlier you would have appended to a older backup file (WITH NOINIT
which is default).
That caused the backup file to show a bigger size. While restoring you
restore the first backup file
which was taken some days back and that do not have some new tables.
This is just my assumption. If you have the backup file which you has issues
just try
RESTORE HEADERONLY FROM DISK='Backupfilename.BAK'
The above command will give you all the backup sets in the backup file.
Thanks
Hari
"akkha1234@.gmail.com" wrote:
> I have a strange case. I do a full backup this morning. The size of
> the backup is about 300MB which is 4 times larger than the actual
> database file. Now when I restore the backup, some of the objects (eg
> some tables) are not there!!.
> Now I just do another backup, the size of this backup is now about
> 80MB, which is normal and when I restore this backup, I got all the
> tables.
> What am I missing? Did someone has similar experience?
>|||Dear Hari,
You are absolutely correct. Learn one more thing on MSSQL again.|||Thats good to know...
Thanks
Hari
<akkha1234@.gmail.com> wrote in message
news:1170369045.337711.234660@.l53g2000cwa.googlegroups.com...
> Dear Hari,
> You are absolutely correct. Learn one more thing on MSSQL again.
>
the backup is about 300MB which is 4 times larger than the actual
database file. Now when I restore the backup, some of the objects (eg
some tables) are not there!!.
Now I just do another backup, the size of this backup is now about
80MB, which is normal and when I restore this backup, I got all the
tables.
What am I missing? Did someone has similar experience?Probably earlier you would have appended to a older backup file (WITH NOINIT
which is default).
That caused the backup file to show a bigger size. While restoring you
restore the first backup file
which was taken some days back and that do not have some new tables.
This is just my assumption. If you have the backup file which you has issues
just try
RESTORE HEADERONLY FROM DISK='Backupfilename.BAK'
The above command will give you all the backup sets in the backup file.
Thanks
Hari
"akkha1234@.gmail.com" wrote:
> I have a strange case. I do a full backup this morning. The size of
> the backup is about 300MB which is 4 times larger than the actual
> database file. Now when I restore the backup, some of the objects (eg
> some tables) are not there!!.
> Now I just do another backup, the size of this backup is now about
> 80MB, which is normal and when I restore this backup, I got all the
> tables.
> What am I missing? Did someone has similar experience?
>|||Dear Hari,
You are absolutely correct. Learn one more thing on MSSQL again.|||Thats good to know...
Thanks
Hari
<akkha1234@.gmail.com> wrote in message
news:1170369045.337711.234660@.l53g2000cwa.googlegroups.com...
> Dear Hari,
> You are absolutely correct. Learn one more thing on MSSQL again.
>
Subscribe to:
Posts (Atom)