How to find currpted backup file

1.How can i find out whether the backup file is currpted or good enough to
restore.
2.Is there any other ways to restore db without loosing any data when my
database files (mdf & Ldf) and my backup file is currupt
ThanksHello,
1.How can i find out whether the backup file is currpted or good enough to
restore.
RESTORE VERIFY ONLY
2. Is there any other ways to restore db without loosing any data when my
database files (mdf & Ldf) and my backup file is currupt
If both MDF and LDF is corrupted. You cant do much. Only way is to
restore from good backup. Incase if ur LDF is giving issues or if u have 803
error you can
1. Create a database with same
2. Stop SQL Server and copy the corrupted MDF above the new MDF file
3. Start SQL Server
4. Datbaase will be marked suspect. Change the mode to EMergency
5, Using DTS or Scripts to copy the data
Steps will varry based on the situation.
Thanks
Hari
"Khwaja Arshaduddin" <KhwajaArshaduddin@.discussions.microsoft.com> wrote in
message news:E5825040-0628-4821-8645-A5C833BDB601@.microsoft.com...
> 1.How can i find out whether the backup file is currpted or good enough to
> restore.
> 2.Is there any other ways to restore db without loosing any data when my
> database files (mdf & Ldf) and my backup file is currupt
> Thanks|||Thanks Hari
"Hari Prasad" wrote:
> Hello,
> 1.How can i find out whether the backup file is currpted or good enough to
> restore.
> RESTORE VERIFY ONLY
> 2. Is there any other ways to restore db without loosing any data when my
> database files (mdf & Ldf) and my backup file is currupt
> If both MDF and LDF is corrupted. You cant do much. Only way is to
> restore from good backup. Incase if ur LDF is giving issues or if u have 803
> error you can
> 1. Create a database with same
> 2. Stop SQL Server and copy the corrupted MDF above the new MDF file
> 3. Start SQL Server
> 4. Datbaase will be marked suspect. Change the mode to EMergency
> 5, Using DTS or Scripts to copy the data
> Steps will varry based on the situation.
> Thanks
> Hari
>
> "Khwaja Arshaduddin" <KhwajaArshaduddin@.discussions.microsoft.com> wrote in
> message news:E5825040-0628-4821-8645-A5C833BDB601@.microsoft.com...
> > 1.How can i find out whether the backup file is currpted or good enough to
> > restore.
> > 2.Is there any other ways to restore db without loosing any data when my
> > database files (mdf & Ldf) and my backup file is currupt
> > Thanks
>
>|||Note that RESTORE VERIFYONLY doesn't do a "true" verification unless you are on 2005 and did the
backup using CHECKSUM option. In such cases, you should do a real restore (into a new database, of
course; possibly on another server).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Khwaja Arshaduddin" <KhwajaArshaduddin@.discussions.microsoft.com> wrote in message
news:66EFEFEC-3A63-4F14-A955-C27DC137EA94@.microsoft.com...
> Thanks Hari
> "Hari Prasad" wrote:
>> Hello,
>> 1.How can i find out whether the backup file is currpted or good enough to
>> restore.
>> RESTORE VERIFY ONLY
>> 2. Is there any other ways to restore db without loosing any data when my
>> database files (mdf & Ldf) and my backup file is currupt
>> If both MDF and LDF is corrupted. You cant do much. Only way is to
>> restore from good backup. Incase if ur LDF is giving issues or if u have 803
>> error you can
>> 1. Create a database with same
>> 2. Stop SQL Server and copy the corrupted MDF above the new MDF file
>> 3. Start SQL Server
>> 4. Datbaase will be marked suspect. Change the mode to EMergency
>> 5, Using DTS or Scripts to copy the data
>> Steps will varry based on the situation.
>> Thanks
>> Hari
>>
>> "Khwaja Arshaduddin" <KhwajaArshaduddin@.discussions.microsoft.com> wrote in
>> message news:E5825040-0628-4821-8645-A5C833BDB601@.microsoft.com...
>> > 1.How can i find out whether the backup file is currpted or good enough to
>> > restore.
>> > 2.Is there any other ways to restore db without loosing any data when my
>> > database files (mdf & Ldf) and my backup file is currupt
>> > Thanks
>>|||Exactly, I agree with Tibor.
Khwaja ,
As a practice for critical databases you could restore the backup once in a
while and do a DBCC CHECKDB and confirm that ur backupis good.
Thanks
Hari
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%230FiC3aUHHA.4076@.TK2MSFTNGP05.phx.gbl...
> Note that RESTORE VERIFYONLY doesn't do a "true" verification unless you
> are on 2005 and did the backup using CHECKSUM option. In such cases, you
> should do a real restore (into a new database, of course; possibly on
> another server).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Khwaja Arshaduddin" <KhwajaArshaduddin@.discussions.microsoft.com> wrote
> in message news:66EFEFEC-3A63-4F14-A955-C27DC137EA94@.microsoft.com...
>> Thanks Hari
>> "Hari Prasad" wrote:
>> Hello,
>> 1.How can i find out whether the backup file is currpted or good enough
>> to
>> restore.
>> RESTORE VERIFY ONLY
>> 2. Is there any other ways to restore db without loosing any data when
>> my
>> database files (mdf & Ldf) and my backup file is currupt
>> If both MDF and LDF is corrupted. You cant do much. Only way is to
>> restore from good backup. Incase if ur LDF is giving issues or if u have
>> 803
>> error you can
>> 1. Create a database with same
>> 2. Stop SQL Server and copy the corrupted MDF above the new MDF file
>> 3. Start SQL Server
>> 4. Datbaase will be marked suspect. Change the mode to EMergency
>> 5, Using DTS or Scripts to copy the data
>> Steps will varry based on the situation.
>> Thanks
>> Hari
>>
>> "Khwaja Arshaduddin" <KhwajaArshaduddin@.discussions.microsoft.com> wrote
>> in
>> message news:E5825040-0628-4821-8645-A5C833BDB601@.microsoft.com...
>> > 1.How can i find out whether the backup file is currpted or good
>> > enough to
>> > restore.
>> > 2.Is there any other ways to restore db without loosing any data when
>> > my
>> > database files (mdf & Ldf) and my backup file is currupt
>> > Thanks
>>
>