HELP!! Problem in database backup and restore!

Im trying to backup the databse by selecting the database source, backup type = full, name the backup set, and leave the rest as default. The backup seems to be successful.

The problem comes when I need to restore the backup database, I 've tried many times and a few different kinds of selection, all fails. I've selected the source for restore from device, that is the .bak file from backup folder and remains the rest of selection as default. Here is the error message I get:

System.Data.SqlClient.SqlError: The backup set holds a backup of the database other than the existing 'testing' database. (Microsoft.SqlServer.Express.Smo)

Anyone can help to solve this problem?!

Create new Database. In Restore window-> Options tab, check "Force restore over existing database". And then try to restore. This may work for you.

Santosh

|||

Thankz santosh...

the solution u had provided.... had successfully solved the problem mention above....but there are some database that still meets another problem during the database restore

here is the error occurs after that....

TITLE: Microsoft SQL Server Management Studio Express

Restore failed for Server 'COMP1\SQLEXPRESS'. (Microsoft.SqlServer.Express.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476

ADDITIONAL INFORMATION:

System.Data.SqlClient.SqlError: The file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\JGSQL.mdf' cannot be overwritten. It is being used by database 'JGSQL'. (Microsoft.SqlServer.Express.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&LinkId=20476

BUTTONS:

OK

|||

I've try to do the database restore using sql command as below:

RESTORE DATABASE testJG

FROM DISK = 'c:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\Backup\JGsql.bak'

GO

But I get this error message.

Does this means that I need to restore the master database from systems database to the database testJG before I restore the backup database?

Msg 3102, Level 16, State 1, Line 1

RESTORE cannot process database 'testJG' because it is in use by this session. It is recommended that the master database be used when performing this operation.

Msg 3013, Level 16, State 1, Line 1

RESTORE DATABASE is terminating abnormally.

|||It was helpfull to me. Thanx! :)sql

HELP!! Problem in database backup and restore!

Im trying to backup the databse by selecting the database source, backup type = full, name the backup set, and leave the rest as default. The backup seems to be successful.

The problem comes when I need to restore the backup database, I 've tried many times and a few different kinds of selection, all fails. I've selected the source for restore from device, that is the .bak file from backup folder and remains the rest of selection as default. Here is the error message I get:

System.Data.SqlClient.SqlError: The backup set holds a backup of the database other than the existing 'testing' database. (Microsoft.SqlServer.Express.Smo)

Anyone can help to solve this problem?!

Create new Database. In Restore window-> Options tab, check "Force restore over existing database". And then try to restore. This may work for you.

Santosh

|||

Thankz santosh...

the solution u had provided.... had successfully solved the problem mention above....but there are some database that still meets another problem during the database restore

here is the error occurs after that....

TITLE: Microsoft SQL Server Management Studio Express

Restore failed for Server 'COMP1\SQLEXPRESS'. (Microsoft.SqlServer.Express.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476

ADDITIONAL INFORMATION:

System.Data.SqlClient.SqlError: The file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\JGSQL.mdf' cannot be overwritten. It is being used by database 'JGSQL'. (Microsoft.SqlServer.Express.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&LinkId=20476

BUTTONS:

OK

|||

I've try to do the database restore using sql command as below:

RESTORE DATABASE testJG

FROM DISK = 'c:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\Backup\JGsql.bak'

GO

But I get this error message.

Does this means that I need to restore the master database from systems database to the database testJG before I restore the backup database?

Msg 3102, Level 16, State 1, Line 1

RESTORE cannot process database 'testJG' because it is in use by this session. It is recommended that the master database be used when performing this operation.

Msg 3013, Level 16, State 1, Line 1

RESTORE DATABASE is terminating abnormally.

|||It was helpfull to me. Thanx! :)

help! when I restore the database!

when I restore the database from a backup file.I failed
the code is "SQLstate 42000
because my sql server is chines
the message means
database "xxx" has 2 family members,but now provide 1
I think there is miss the log
how can I do?From the error msg it sounds like you striped your backup across multiple
devices and you have only specified 1 for the restore.
Provide all file locations that you backed up for that set when restoring.
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Silence" <anonymous@.discussions.microsoft.com> wrote in message
news:30617EBA-03E3-492F-986A-C85E94F15F72@.microsoft.com...
> when I restore the database from a backup file.I failed.
> the code is "SQLstate 42000"
> because my sql server is chinese
> the message means:
> database "xxx" has 2 family members,but now provide 1.
> I think there is miss the log.
> how can I do?|||but the file is my friend gave me
and now cannot backup again from original database
how can I do?|||> but the file is my friend gave me.
Can you re-phrase that?
> and now cannot backup again from original database.
> how can I do?
By original, do you mean the database you tried to restore into or the one that the backup was
produced on?
Can you explain a little bit more details what happened?
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Silence" <anonymous@.discussions.microsoft.com> wrote in message
news:6486E3F3-83D8-4506-91E7-F3B3B2344045@.microsoft.com...
> but the file is my friend gave me.
> and now cannot backup again from original database.
> how can I do?|||because the computer's hard disk was broken
so the data was los
he gave me the backup file is the only file.|||Just read about the RESTORE command in Books Online and do the restore based on your backup file
(from Query analyzer).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Silence" <anonymous@.discussions.microsoft.com> wrote in message
news:A1A4F50B-4ED9-4634-BD25-AB89D21C2729@.microsoft.com...
> because the computer's hard disk was broken.
> so the data was lost
> he gave me the backup file is the only file.|||which topic can I found?
can you type the command for me?
thank you!
-- Tibor Karaszi wrote: --
Just read about the RESTORE command in Books Online and do the restore based on your backup file
(from Query analyzer).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Silence" <anonymous@.discussions.microsoft.com> wrote in message
news:A1A4F50B-4ED9-4634-BD25-AB89D21C2729@.microsoft.com...
> because the computer's hard disk was broken.
> so the data was lost
> he gave me the backup file is the only file.|||The exact command to type depends on a lot of factors (the path to the backup file, the path to the
database files etc etc). In Books Online, you find the Transact-SQL Reference. Here you find the
RESTORE command documented.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"silence" <zjflyer@.hotmail.com> wrote in message
news:D32AE25A-E164-4B87-BD77-EE3B9E7C054C@.microsoft.com...
> which topic can I found?
> can you type the command for me?
> thank you!
> -- Tibor Karaszi wrote: --
> Just read about the RESTORE command in Books Online and do the restore based on your backup
file
> (from Query analyzer).
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Silence" <anonymous@.discussions.microsoft.com> wrote in message
> news:A1A4F50B-4ED9-4634-BD25-AB89D21C2729@.microsoft.com...
> > because the computer's hard disk was broken.
> > so the data was lost
> > he gave me the backup file is the only file.
>
>

HELP! Transaction Log is huge

Hi all,
I have an SQL2000 running on a W2K server. The mdf file is about 140MB but
the ldf shows over 11GB. I ran backups. The full DB backup is 138MB and the
Transaction log backup right after is 126MB. I tried shrinking and
everything else I could think of. I even deleted the DB and restored it from
a full DB backup. The ldf still comes up with 11GB. I have another
installation of the same database on another server where the ldf shows a
normal size (40MB).
Can anybody tell me what is going on? During the restore I moved the data
files to another disk that has lots of space but there is something wrong
here and I would like to get to the bottom of it.
Thanks for your help,
ClausHi, what is your recovery set too. If it is set to "Full" you need to do a
translog backup, and truncate after.
If you set it to simple, it will checkpoint and keep the log resonable.
Try backup log (database) with truncate_only
Then shrink the log file.
"cjobes" wrote:
> Hi all,
> I have an SQL2000 running on a W2K server. The mdf file is about 140MB but
> the ldf shows over 11GB. I ran backups. The full DB backup is 138MB and the
> Transaction log backup right after is 126MB. I tried shrinking and
> everything else I could think of. I even deleted the DB and restored it from
> a full DB backup. The ldf still comes up with 11GB. I have another
> installation of the same database on another server where the ldf shows a
> normal size (40MB).
> Can anybody tell me what is going on? During the restore I moved the data
> files to another disk that has lots of space but there is something wrong
> here and I would like to get to the bottom of it.
> Thanks for your help,
> Claus
>
>|||I have it set to full because we do a daily backup and then hourly
transaction log backups. The one instance works as expected but the other
one has this 11GB ldf and I don't seem to be able to get it down.
Now after reading your advice I switched the db to simple, run a backup and
then shrank the log file. Now it's down to 0.5MB. My question is, shouldn't
it do that automatically when the full db backup runs with the option to
remove inactive entries from the transaction log?
Thanks for your help,
Claus
"robert_at_cbb" <robertatcbb@.discussions.microsoft.com> wrote in message
news:CE6A255E-1443-41C5-BFEA-D366A848E3F9@.microsoft.com...
> Hi, what is your recovery set too. If it is set to "Full" you need to do a
> translog backup, and truncate after.
> If you set it to simple, it will checkpoint and keep the log resonable.
> Try backup log (database) with truncate_only
> Then shrink the log file.
>
> "cjobes" wrote:
> > Hi all,
> >
> > I have an SQL2000 running on a W2K server. The mdf file is about 140MB
but
> > the ldf shows over 11GB. I ran backups. The full DB backup is 138MB and
the
> > Transaction log backup right after is 126MB. I tried shrinking and
> > everything else I could think of. I even deleted the DB and restored it
from
> > a full DB backup. The ldf still comes up with 11GB. I have another
> > installation of the same database on another server where the ldf shows
a
> > normal size (40MB).
> >
> > Can anybody tell me what is going on? During the restore I moved the
data
> > files to another disk that has lots of space but there is something
wrong
> > here and I would like to get to the bottom of it.
> >
> > Thanks for your help,
> >
> > Claus
> >
> >
> >|||Hi,
As soon as you run the trasnaction log backup the inactive entries of
transaction log will be cleared. But the physcal file will not get shrink
automatically until or unless you enable to database option "AUTO_SHRINK".
Turning on this option in a production server is not recommended.
Because auto shrinking will reduce the performance.
To avoid this after the transaction log backup you could do a DBCC
SHRINKFILE (refer books online) on the LDF file frequently
(Daily or weekly once.. based on the LDF growth) to reduce the LDF file
size.
DBCC SQLPERF(LOGSPACE)
will give you the exact file size and usage
Thanks
Hari
MCDBA
"cjobes" <cjobes@.nova-tech.org> wrote in message
news:uReKjIYhEHA.3992@.TK2MSFTNGP11.phx.gbl...
> I have it set to full because we do a daily backup and then hourly
> transaction log backups. The one instance works as expected but the other
> one has this 11GB ldf and I don't seem to be able to get it down.
> Now after reading your advice I switched the db to simple, run a backup
and
> then shrank the log file. Now it's down to 0.5MB. My question is,
shouldn't
> it do that automatically when the full db backup runs with the option to
> remove inactive entries from the transaction log?
> Thanks for your help,
> Claus
>
> "robert_at_cbb" <robertatcbb@.discussions.microsoft.com> wrote in message
> news:CE6A255E-1443-41C5-BFEA-D366A848E3F9@.microsoft.com...
> > Hi, what is your recovery set too. If it is set to "Full" you need to do
a
> > translog backup, and truncate after.
> >
> > If you set it to simple, it will checkpoint and keep the log resonable.
> >
> > Try backup log (database) with truncate_only
> >
> > Then shrink the log file.
> >
> >
> > "cjobes" wrote:
> >
> > > Hi all,
> > >
> > > I have an SQL2000 running on a W2K server. The mdf file is about 140MB
> but
> > > the ldf shows over 11GB. I ran backups. The full DB backup is 138MB
and
> the
> > > Transaction log backup right after is 126MB. I tried shrinking and
> > > everything else I could think of. I even deleted the DB and restored
it
> from
> > > a full DB backup. The ldf still comes up with 11GB. I have another
> > > installation of the same database on another server where the ldf
shows
> a
> > > normal size (40MB).
> > >
> > > Can anybody tell me what is going on? During the restore I moved the
> data
> > > files to another disk that has lots of space but there is something
> wrong
> > > here and I would like to get to the bottom of it.
> > >
> > > Thanks for your help,
> > >
> > > Claus
> > >
> > >
> > >
>|||Thanks for the helpful advice. I will keep an eye on this.
Claus
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:eWRTv$ZhEHA.2624@.TK2MSFTNGP12.phx.gbl...
> Hi,
> As soon as you run the trasnaction log backup the inactive entries of
> transaction log will be cleared. But the physcal file will not get shrink
> automatically until or unless you enable to database option "AUTO_SHRINK".
> Turning on this option in a production server is not recommended.
> Because auto shrinking will reduce the performance.
> To avoid this after the transaction log backup you could do a DBCC
> SHRINKFILE (refer books online) on the LDF file frequently
> (Daily or weekly once.. based on the LDF growth) to reduce the LDF file
> size.
> DBCC SQLPERF(LOGSPACE)
> will give you the exact file size and usage
> Thanks
> Hari
> MCDBA
>
> "cjobes" <cjobes@.nova-tech.org> wrote in message
> news:uReKjIYhEHA.3992@.TK2MSFTNGP11.phx.gbl...
> > I have it set to full because we do a daily backup and then hourly
> > transaction log backups. The one instance works as expected but the
other
> > one has this 11GB ldf and I don't seem to be able to get it down.
> >
> > Now after reading your advice I switched the db to simple, run a backup
> and
> > then shrank the log file. Now it's down to 0.5MB. My question is,
> shouldn't
> > it do that automatically when the full db backup runs with the option to
> > remove inactive entries from the transaction log?
> >
> > Thanks for your help,
> >
> > Claus
> >
> >
> > "robert_at_cbb" <robertatcbb@.discussions.microsoft.com> wrote in message
> > news:CE6A255E-1443-41C5-BFEA-D366A848E3F9@.microsoft.com...
> > > Hi, what is your recovery set too. If it is set to "Full" you need to
do
> a
> > > translog backup, and truncate after.
> > >
> > > If you set it to simple, it will checkpoint and keep the log
resonable.
> > >
> > > Try backup log (database) with truncate_only
> > >
> > > Then shrink the log file.
> > >
> > >
> > > "cjobes" wrote:
> > >
> > > > Hi all,
> > > >
> > > > I have an SQL2000 running on a W2K server. The mdf file is about
140MB
> > but
> > > > the ldf shows over 11GB. I ran backups. The full DB backup is 138MB
> and
> > the
> > > > Transaction log backup right after is 126MB. I tried shrinking and
> > > > everything else I could think of. I even deleted the DB and restored
> it
> > from
> > > > a full DB backup. The ldf still comes up with 11GB. I have another
> > > > installation of the same database on another server where the ldf
> shows
> > a
> > > > normal size (40MB).
> > > >
> > > > Can anybody tell me what is going on? During the restore I moved the
> > data
> > > > files to another disk that has lots of space but there is something
> > wrong
> > > > here and I would like to get to the bottom of it.
> > > >
> > > > Thanks for your help,
> > > >
> > > > Claus
> > > >
> > > >
> > > >
> >
> >
>|||I have the same problem with a client as you do. I did the backup and
shrink but the log file is still at 23gigs!
Where do I find the option to 'truncate' in the SQL Server Enterprise
Manager?
"robert_at_cbb" <robertatcbb@.discussions.microsoft.com> wrote in message
news:CE6A255E-1443-41C5-BFEA-D366A848E3F9@.microsoft.com...
> Hi, what is your recovery set too. If it is set to "Full" you need to do a
> translog backup, and truncate after.
> If you set it to simple, it will checkpoint and keep the log resonable.
> Try backup log (database) with truncate_only
> Then shrink the log file.
>
> "cjobes" wrote:
> > Hi all,
> >
> > I have an SQL2000 running on a W2K server. The mdf file is about 140MB
but
> > the ldf shows over 11GB. I ran backups. The full DB backup is 138MB and
the
> > Transaction log backup right after is 126MB. I tried shrinking and
> > everything else I could think of. I even deleted the DB and restored it
from
> > a full DB backup. The ldf still comes up with 11GB. I have another
> > installation of the same database on another server where the ldf shows
a
> > normal size (40MB).
> >
> > Can anybody tell me what is going on? During the restore I moved the
data
> > files to another disk that has lots of space but there is something
wrong
> > here and I would like to get to the bottom of it.
> >
> > Thanks for your help,
> >
> > Claus
> >
> >
> >|||You have to do it in the analyzer
backup log "database" with truncate_only
You can also add it as a task in a job.
"Dean Penderghast" wrote:
> I have the same problem with a client as you do. I did the backup and
> shrink but the log file is still at 23gigs!
> Where do I find the option to 'truncate' in the SQL Server Enterprise
> Manager?
> "robert_at_cbb" <robertatcbb@.discussions.microsoft.com> wrote in message
> news:CE6A255E-1443-41C5-BFEA-D366A848E3F9@.microsoft.com...
> > Hi, what is your recovery set too. If it is set to "Full" you need to do a
> > translog backup, and truncate after.
> >
> > If you set it to simple, it will checkpoint and keep the log resonable.
> >
> > Try backup log (database) with truncate_only
> >
> > Then shrink the log file.
> >
> >
> > "cjobes" wrote:
> >
> > > Hi all,
> > >
> > > I have an SQL2000 running on a W2K server. The mdf file is about 140MB
> but
> > > the ldf shows over 11GB. I ran backups. The full DB backup is 138MB and
> the
> > > Transaction log backup right after is 126MB. I tried shrinking and
> > > everything else I could think of. I even deleted the DB and restored it
> from
> > > a full DB backup. The ldf still comes up with 11GB. I have another
> > > installation of the same database on another server where the ldf shows
> a
> > > normal size (40MB).
> > >
> > > Can anybody tell me what is going on? During the restore I moved the
> data
> > > files to another disk that has lots of space but there is something
> wrong
> > > here and I would like to get to the bottom of it.
> > >
> > > Thanks for your help,
> > >
> > > Claus
> > >
> > >
> > >
>
>|||I did that and the log file is still 23 gigs in size. I've done a full
transaction backup and tried to resize the file and still can't get it to
shrink. Am I missing something simple here?
Dean Penderghast
"robert_at_cbb" <robertatcbb@.discussions.microsoft.com> wrote in message
news:DF200740-7079-472C-8D0B-563ECC3FBBFD@.microsoft.com...
> You have to do it in the analyzer
> backup log "database" with truncate_only
> You can also add it as a task in a job.
> "Dean Penderghast" wrote:
> > I have the same problem with a client as you do. I did the backup and
> > shrink but the log file is still at 23gigs!
> >
> > Where do I find the option to 'truncate' in the SQL Server Enterprise
> > Manager?
> >
> > "robert_at_cbb" <robertatcbb@.discussions.microsoft.com> wrote in message
> > news:CE6A255E-1443-41C5-BFEA-D366A848E3F9@.microsoft.com...
> > > Hi, what is your recovery set too. If it is set to "Full" you need to
do a
> > > translog backup, and truncate after.
> > >
> > > If you set it to simple, it will checkpoint and keep the log
resonable.
> > >
> > > Try backup log (database) with truncate_only
> > >
> > > Then shrink the log file.
> > >
> > >
> > > "cjobes" wrote:
> > >
> > > > Hi all,
> > > >
> > > > I have an SQL2000 running on a W2K server. The mdf file is about
140MB
> > but
> > > > the ldf shows over 11GB. I ran backups. The full DB backup is 138MB
and
> > the
> > > > Transaction log backup right after is 126MB. I tried shrinking and
> > > > everything else I could think of. I even deleted the DB and restored
it
> > from
> > > > a full DB backup. The ldf still comes up with 11GB. I have another
> > > > installation of the same database on another server where the ldf
shows
> > a
> > > > normal size (40MB).
> > > >
> > > > Can anybody tell me what is going on? During the restore I moved the
> > data
> > > > files to another disk that has lots of space but there is something
> > wrong
> > > > here and I would like to get to the bottom of it.
> > > >
> > > > Thanks for your help,
> > > >
> > > > Claus
> > > >
> > > >
> > > >
> >
> >
> >sql

HELP! Transaction Log Backup!

Hello!!

I am relatively new to SQL and am having a problem. I have taken over
a SQL 2000 db that did not have any backup plans scheduled for it. I
created a maintenance plan that backs up the database every night and
another plan that backs up the system databases once a week. I ran
both these jobs successfully, but when I created a third plan to
backup the transaction log it fails with the following message:
Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTATE
42000] (Error 22029). The step failed. I then executed the following
statement: sp_grantlogin 'NT Authority\System' which did not work.
I still do not understand why I can't backup the log? The database
backs up fine with no errors so it can't be a permission thing and I
created the job with a maintenance plan so it has to be in full
recovery mode. Right? How do I tell? Thank you for all your
responses!!

NS"tech_guru" <nstimely@.cityofpasadena.net> wrote in message
news:3ff7efe5.0409091230.2126a3af@.posting.google.c om...
> Hello!!
> I am relatively new to SQL and am having a problem. I have taken over
> a SQL 2000 db that did not have any backup plans scheduled for it. I
> created a maintenance plan that backs up the database every night and
> another plan that backs up the system databases once a week. I ran
> both these jobs successfully, but when I created a third plan to
> backup the transaction log it fails with the following message:
> Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTATE
> 42000] (Error 22029). The step failed. I then executed the following
> statement: sp_grantlogin 'NT Authority\System' which did not work.
> I still do not understand why I can't backup the log? The database
> backs up fine with no errors so it can't be a permission thing and I
> created the job with a maintenance plan so it has to be in full
> recovery mode. Right? How do I tell? Thank you for all your
> responses!!

It probably is a permissions problem.

Where are you backing up to? If it's any place other than the same box, you
need to run SQL admin as a domain account, SYSTEM only has rights on the
local system.

> NS|||tech_guru (nstimely@.cityofpasadena.net) writes:
> I am relatively new to SQL and am having a problem. I have taken over
> a SQL 2000 db that did not have any backup plans scheduled for it. I
> created a maintenance plan that backs up the database every night and
> another plan that backs up the system databases once a week. I ran
> both these jobs successfully, but when I created a third plan to
> backup the transaction log it fails with the following message:
> Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTATE
> 42000] (Error 22029). The step failed. I then executed the following
> statement: sp_grantlogin 'NT Authority\System' which did not work.
> I still do not understand why I can't backup the log? The database
> backs up fine with no errors so it can't be a permission thing and I
> created the job with a maintenance plan so it has to be in full
> recovery mode. Right? How do I tell? Thank you for all your
> responses!!

I would double-check that the database is not in simple recovery mode.

One way to find out what the problem is, would be to go to the job
step, find the Advanced tab, and specify an output file. Hopefully
you can get a better error message that way.

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

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||I have the same problem. I output the log and recevied the following
message:

Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL
Server 'O4' as 'NT AUTHORITY\SYSTEM' (trusted)
Starting maintenance plan 'LouiseTest MaintenancePlan_2' on 1/28/2005
1:59:53 PM
Backup can not be performed on database 'LouiseTest'. This sub task is
ignored.

End of maintenance plan 'LouiseTest MaintenancePlan_2' on 1/28/2005
1:59:53 PM
SQLMAINT.EXE Process Exit Code: 1 (Failed)

What setting must I change? Is it an access thing?

Erland Sommarskog wrote:
> tech_guru (nstimely@.cityofpasadena.net) writes:
> > I am relatively new to SQL and am having a problem. I have taken
over
> > a SQL 2000 db that did not have any backup plans scheduled for it.
I
> > created a maintenance plan that backs up the database every night
and
> > another plan that backs up the system databases once a week. I ran
> > both these jobs successfully, but when I created a third plan to
> > backup the transaction log it fails with the following message:
> > Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed.
[SQLSTATE
> > 42000] (Error 22029). The step failed. I then executed the
following
> > statement: sp_grantlogin 'NT Authority\System' which did not
work.
> > I still do not understand why I can't backup the log? The
database
> > backs up fine with no errors so it can't be a permission thing and
I
> > created the job with a maintenance plan so it has to be in full
> > recovery mode. Right? How do I tell? Thank you for all your
> > responses!!
> I would double-check that the database is not in simple recovery
mode.
> One way to find out what the problem is, would be to go to the job
> step, find the Advanced tab, and specify an output file. Hopefully
> you can get a better error message that way.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp|||chrispycrunch (chrispycrunch@.gmail.com) writes:
> I have the same problem. I output the log and recevied the following
> message:
>
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL
> Server 'O4' as 'NT AUTHORITY\SYSTEM' (trusted)
> Starting maintenance plan 'LouiseTest MaintenancePlan_2' on 1/28/2005
> 1:59:53 PM
> Backup can not be performed on database 'LouiseTest'. This sub task is
> ignored.
> End of maintenance plan 'LouiseTest MaintenancePlan_2' on 1/28/2005
> 1:59:53 PM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>
> What setting must I change? Is it an access thing?

And just like the guy who had the same problem, you need to find the
job under SQL Server Agent->Jobs, right-click it and Select View job
history and check the box "Show step details" in the upper-right corner.
Then you will find what the error actually is.

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

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thanks - that worked. Another problem is transaction backups:

Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTATE
42000] (Error 22029). The step failed.

The database is on a network drive.
I am creating the plan locally. Could that be an issue? The same thing
is done for index tuning and database backup (i figured out you should
save the files by the default location) and those tasks work.|||chrispycrunch (chrispycrunch@.gmail.com) writes:
> Thanks - that worked. Another problem is transaction backups:
> Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTATE
> 42000] (Error 22029). The step failed.
> The database is on a network drive.

And the actual error message is?

When performing any access to network drives from SQL Server, including
backups, the account under which SQL Server runs must have access to
the network drive. Typically this is not the case if the SQL Server runs
as Local System. The remedy is run SQL Server under a domain user with
the necessary access rights.

You change the account for SQL Server by right-clicking My Computer,
select Manage. Find Services, then the MS SQL Server service. Open it,
and log-on information is on the second tab.

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

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thanks, for the help and for tolerating my easy questions...I'm very
new to the 'admin' of NT, SQL, etc.
Also, I noticed the account was locked out, so see if that does the
trick.|||Update: that didn't work - i'm frustrated! Is there a book or website
that can give further instructions on windows security?|||chrispycrunch (chrispycrunch@.gmail.com) writes:
> Update: that didn't work - i'm frustrated!

And the error message is?

To repeat from earlier in the thread:

And just like the guy who had the same problem, you need to find the
job under SQL Server Agent->Jobs, right-click it and Select View job
history and check the box "Show step details" in the upper-right corner.
Then you will find what the error actually is.

> Is there a book or website that can give further instructions on windows
> security?

Probably, but Windows is not my speciality. Anyway, without the error
message, books are not going to help you.

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

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

HELP! I/O error (torn page) when attaching mdf and ldf files

We are using cloning software to directly backup the mdf and ldf files. I am
testing a restore of these files by using sp_attach_db.
When I do this I am receiving an error on the ldf file: See below:
Server: Msg 823, Level 24, State 6, Line 1
I/O error (torn page) detected during read at offset 0000000000000000 in
file 'D:\Data\FRPP01_log.ldf'.
Connection Broken
Please help........Your clone is no good. It was taken during while a page was partially
written.
You need to have your clone software interact with the SQL VDI (Virtual
Device Interface) that will quiesce database writes for a moment while the
clone occurs. You need to contact your clone software vendor to see if they
support this technology and if so, how to enable it for your environment.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kristen" <Kristen@.discussions.microsoft.com> wrote in message
news:3ED62BD7-738E-4399-A845-98BA25919E53@.microsoft.com...
> We are using cloning software to directly backup the mdf and ldf files. I
> am
> testing a restore of these files by using sp_attach_db.
> When I do this I am receiving an error on the ldf file: See below:
> Server: Msg 823, Level 24, State 6, Line 1
> I/O error (torn page) detected during read at offset 0000000000000000 in
> file 'D:\Data\FRPP01_log.ldf'.
> Connection Broken
> Please help........

HELP! I/O error (torn page) when attaching mdf and ldf files

We are using cloning software to directly backup the mdf and ldf files. I a
m
testing a restore of these files by using sp_attach_db.
When I do this I am receiving an error on the ldf file: See below:
Server: Msg 823, Level 24, State 6, Line 1
I/O error (torn page) detected during read at offset 0000000000000000 in
file 'D:\Data\FRPP01_log.ldf'.
Connection Broken
Please help........Your clone is no good. It was taken during while a page was partially
written.
You need to have your clone software interact with the SQL VDI (Virtual
Device Interface) that will quiesce database writes for a moment while the
clone occurs. You need to contact your clone software vendor to see if they
support this technology and if so, how to enable it for your environment.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kristen" <Kristen@.discussions.microsoft.com> wrote in message
news:3ED62BD7-738E-4399-A845-98BA25919E53@.microsoft.com...
> We are using cloning software to directly backup the mdf and ldf files. I
> am
> testing a restore of these files by using sp_attach_db.
> When I do this I am receiving an error on the ldf file: See below:
> Server: Msg 823, Level 24, State 6, Line 1
> I/O error (torn page) detected during read at offset 0000000000000000 in
> file 'D:\Data\FRPP01_log.ldf'.
> Connection Broken
> Please help........

HELP! I/O error (torn page) when attaching mdf and ldf files

We are using cloning software to directly backup the mdf and ldf files. I am
testing a restore of these files by using sp_attach_db.
When I do this I am receiving an error on the ldf file: See below:
Server: Msg 823, Level 24, State 6, Line 1
I/O error (torn page) detected during read at offset 0000000000000000 in
file 'D:\Data\FRPP01_log.ldf'.
Connection Broken
Please help........
Your clone is no good. It was taken during while a page was partially
written.
You need to have your clone software interact with the SQL VDI (Virtual
Device Interface) that will quiesce database writes for a moment while the
clone occurs. You need to contact your clone software vendor to see if they
support this technology and if so, how to enable it for your environment.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kristen" <Kristen@.discussions.microsoft.com> wrote in message
news:3ED62BD7-738E-4399-A845-98BA25919E53@.microsoft.com...
> We are using cloning software to directly backup the mdf and ldf files. I
> am
> testing a restore of these files by using sp_attach_db.
> When I do this I am receiving an error on the ldf file: See below:
> Server: Msg 823, Level 24, State 6, Line 1
> I/O error (torn page) detected during read at offset 0000000000000000 in
> file 'D:\Data\FRPP01_log.ldf'.
> Connection Broken
> Please help........

Help! How can I attach a DB with Corrupted Log Files

I have a backup of a Database files that its log files are damaged ( so I
can't attach it to SQL Server) please tell me if there is a way to attach a
database when its log files are corrupted? ( this DB has two ndf files so I
couldn't use the sp_attach_single_db_file)Look at
Syntax
sp_attach_single_file_db [ @.dbname = ] 'dbname'
, [ @.physname = ] 'physical_name'
in BOL
"Par" <beatles1692@.yahoo.com> wrote in message
news:#$q3$tcdDHA.656@.tk2msftngp13.phx.gbl...
> I have a backup of a Database files that its log files are damaged ( so I
> can't attach it to SQL Server) please tell me if there is a way to attach
a
> database when its log files are corrupted? ( this DB has two ndf files so
I
> couldn't use the sp_attach_single_db_file)
>|||You might try to
1. save off the good mdf and ndf files.
2. recreate the database with the same structure.
3. detach the new empty db,
and try using THAT log to re-attach the originals...
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Par" <beatles1692@.yahoo.com> wrote in message
news:%23$q3$tcdDHA.656@.tk2msftngp13.phx.gbl...
> I have a backup of a Database files that its log files are damaged ( so I
> can't attach it to SQL Server) please tell me if there is a way to attach
a
> database when its log files are corrupted? ( this DB has two ndf files so
I
> couldn't use the sp_attach_single_db_file)
>|||This may be of interest:
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
--
Andrew J. Kelly
SQL Server MVP
"Par" <beatles1692@.yahoo.com> wrote in message
news:%23$q3$tcdDHA.656@.tk2msftngp13.phx.gbl...
> I have a backup of a Database files that its log files are damaged ( so I
> can't attach it to SQL Server) please tell me if there is a way to attach
a
> database when its log files are corrupted? ( this DB has two ndf files so
I
> couldn't use the sp_attach_single_db_file)
>

help! backing up sql server 2005 using osql.exe

Hi

I am trying to make a backup of my SQL server 2005, used with Web Developer 2005 Express, in osql.exe (can't find any other way of doing it). I get the error that "under the default settings SQL server does not allow remote connections".

I connect to it fine from the Web Developer 2005 and my application . I followed another post's instructions where I enabled the TCP/IP and named pipes for "Protocols for SQLEXPRESS", but didn't work. In fact when I changed TCP/IP properties/ IP Addresses/TCP Dynamic port to nothing , and TCP Port to 1357, the server wouldn't start again !! (not doin THAT again)

Regards

Amanda

Godditt !!!!

I needed to enable the SQL Server Browser service, found in article:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277

Thanks...

Help! a database can not be backed up!

Hi,
I have a 80 GB database. The backup can not be completed.
The error message were:
1. BackupMedium::ReportIoError: write failure on backup
device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
Operating system error 33(The process cannot access the
file because another process has locked a portion of the
file.).
2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
m_actualBytes: 0, m_errcode: 33, BackupFile:
d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
3. BACKUP failed to complete the command BACKUP DATABASE
[DistribuGIS] TO DISK = N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
NOSKIP , STATS = 10, NOFORMAT
I checked the disk were working fine.
I checked the database by using dbcc checkdb with
repair_rebuild option. It reported me no error found.
Please help if anything could be wrong/what should I do.
Thank you in advance.try backing up the database to a different machine that
has enough space for the database. This way you can verify
if there is something wrong with the local disk array.
>--Original Message--
>Hi,
>I have a 80 GB database. The backup can not be completed.
>The error message were:
>1. BackupMedium::ReportIoError: write failure on backup
>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>Operating system error 33(The process cannot access the
>file because another process has locked a portion of the
>file.).
>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>m_actualBytes: 0, m_errcode: 33, BackupFile:
>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>3. BACKUP failed to complete the command BACKUP DATABASE
>[DistribuGIS] TO DISK =>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>NOSKIP , STATS = 10, NOFORMAT
>I checked the disk were working fine.
>I checked the database by using dbcc checkdb with
>repair_rebuild option. It reported me no error found.
>
>Please help if anything could be wrong/what should I do.
>Thank you in advance.
>
>.
>|||Unfortunately, since this database is big I can not try
backing up the database to a different machine.
But I have other databases in the same machine and they
all could be backed up successfully. Since this, can I say
the local disk array is ok?
Do you think this is because that the database files are
damaged?
Thank you.
>--Original Message--
>try backing up the database to a different machine that
>has enough space for the database. This way you can
verify
>if there is something wrong with the local disk array.
>
>>--Original Message--
>>Hi,
>>I have a 80 GB database. The backup can not be
completed.
>>The error message were:
>>1. BackupMedium::ReportIoError: write failure on backup
>>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>>Operating system error 33(The process cannot access the
>>file because another process has locked a portion of the
>>file.).
>>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>>m_actualBytes: 0, m_errcode: 33, BackupFile:
>>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>>3. BACKUP failed to complete the command BACKUP DATABASE
>>[DistribuGIS] TO DISK =>>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>>NOSKIP , STATS = 10, NOFORMAT
>>I checked the disk were working fine.
>>I checked the database by using dbcc checkdb with
>>repair_rebuild option. It reported me no error found.
>>
>>Please help if anything could be wrong/what should I do.
>>Thank you in advance.
>>
>>.
>.
>|||It's the .bak backup file that's the issue, not your
database. Something else is accessing the file - are you
also running NT backup at the same time? That puts a lock on
the file. If you are always hitting the error, try just
backing up to another file name.
Filemon from www.sysinternals.com should tell you what
process has a lock on the file.
-Sue
On Wed, 1 Oct 2003 09:51:23 -0700, "Juan"
<juan_wu@.hotmail.com> wrote:
>Hi,
>I have a 80 GB database. The backup can not be completed.
>The error message were:
>1. BackupMedium::ReportIoError: write failure on backup
>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>Operating system error 33(The process cannot access the
>file because another process has locked a portion of the
>file.).
>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>m_actualBytes: 0, m_errcode: 33, BackupFile:
>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>3. BACKUP failed to complete the command BACKUP DATABASE
>[DistribuGIS] TO DISK =>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>NOSKIP , STATS = 10, NOFORMAT
>I checked the disk were working fine.
>I checked the database by using dbcc checkdb with
>repair_rebuild option. It reported me no error found.
>
>Please help if anything could be wrong/what should I do.
>Thank you in advance.
>|||To ensure the database is in a good state run DBCC CHECKDB against it
--
HTH
Ryan Waight, MCDBA, MCSE
"Juan" <juan_wu@.hotmail.com> wrote in message
news:192401c3884a$93780660$a001280a@.phx.gbl...
> Unfortunately, since this database is big I can not try
> backing up the database to a different machine.
> But I have other databases in the same machine and they
> all could be backed up successfully. Since this, can I say
> the local disk array is ok?
> Do you think this is because that the database files are
> damaged?
> Thank you.
> >--Original Message--
> >try backing up the database to a different machine that
> >has enough space for the database. This way you can
> verify
> >if there is something wrong with the local disk array.
> >
> >
> >>--Original Message--
> >>Hi,
> >>
> >>I have a 80 GB database. The backup can not be
> completed.
> >>The error message were:
> >>1. BackupMedium::ReportIoError: write failure on backup
> >>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
> >>Operating system error 33(The process cannot access the
> >>file because another process has locked a portion of the
> >>file.).
> >>
> >>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
> >>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
> >>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
> >>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
> >>m_actualBytes: 0, m_errcode: 33, BackupFile:
> >>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
> >>
> >>3. BACKUP failed to complete the command BACKUP DATABASE
> >>[DistribuGIS] TO DISK => >>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
> >>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
> >>NOSKIP , STATS = 10, NOFORMAT
> >>
> >>I checked the disk were working fine.
> >>I checked the database by using dbcc checkdb with
> >>repair_rebuild option. It reported me no error found.
> >>
> >>
> >>Please help if anything could be wrong/what should I do.
> >>
> >>Thank you in advance.
> >>
> >>
> >>.
> >>
> >.
> >|||Hi,
It got backed up successfully to a different folder. But
in the meantime, I used to back it up as compressed file
since the shortage of my disk and this time I backed it up
as normal file. Do you think the compression also possibly
cause problem?
I will try the Filemon once I got a chance.
Thank you so much for your help.
--Juan
>--Original Message--
>It's the .bak backup file that's the issue, not your
>database. Something else is accessing the file - are you
>also running NT backup at the same time? That puts a lock
on
>the file. If you are always hitting the error, try just
>backing up to another file name.
>Filemon from www.sysinternals.com should tell you what
>process has a lock on the file.
>-Sue
>On Wed, 1 Oct 2003 09:51:23 -0700, "Juan"
><juan_wu@.hotmail.com> wrote:
>>Hi,
>>I have a 80 GB database. The backup can not be
completed.
>>The error message were:
>>1. BackupMedium::ReportIoError: write failure on backup
>>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>>Operating system error 33(The process cannot access the
>>file because another process has locked a portion of the
>>file.).
>>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>>m_actualBytes: 0, m_errcode: 33, BackupFile:
>>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>>3. BACKUP failed to complete the command BACKUP DATABASE
>>[DistribuGIS] TO DISK =>>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>>NOSKIP , STATS = 10, NOFORMAT
>>I checked the disk were working fine.
>>I checked the database by using dbcc checkdb with
>>repair_rebuild option. It reported me no error found.
>>
>>Please help if anything could be wrong/what should I do.
>>Thank you in advance.
>.
>|||I'm not sure Juan - I've never messed with compression for
database backups. Filemon should show you what's locking the
file though and if it's a system process, you'll see that.
It's a good tool to have and pretty easy to use.
-Sue
On Thu, 2 Oct 2003 14:01:20 -0700, "Juan"
<juan_wu@.hotmail.com> wrote:
>Hi,
>It got backed up successfully to a different folder. But
>in the meantime, I used to back it up as compressed file
>since the shortage of my disk and this time I backed it up
>as normal file. Do you think the compression also possibly
>cause problem?
>I will try the Filemon once I got a chance.
>Thank you so much for your help.
>--Juan
>>--Original Message--
>>It's the .bak backup file that's the issue, not your
>>database. Something else is accessing the file - are you
>>also running NT backup at the same time? That puts a lock
>on
>>the file. If you are always hitting the error, try just
>>backing up to another file name.
>>Filemon from www.sysinternals.com should tell you what
>>process has a lock on the file.
>>-Sue
>>On Wed, 1 Oct 2003 09:51:23 -0700, "Juan"
>><juan_wu@.hotmail.com> wrote:
>>Hi,
>>I have a 80 GB database. The backup can not be
>completed.
>>The error message were:
>>1. BackupMedium::ReportIoError: write failure on backup
>>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>>Operating system error 33(The process cannot access the
>>file because another process has locked a portion of the
>>file.).
>>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>>m_actualBytes: 0, m_errcode: 33, BackupFile:
>>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>>3. BACKUP failed to complete the command BACKUP DATABASE
>>[DistribuGIS] TO DISK =>>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>>NOSKIP , STATS = 10, NOFORMAT
>>I checked the disk were working fine.
>>I checked the database by using dbcc checkdb with
>>repair_rebuild option. It reported me no error found.
>>
>>Please help if anything could be wrong/what should I do.
>>Thank you in advance.
>>
>>.