Recovery problem

In my production database i have lost data in three tables.so i just want to restore the data from my backup which was created.

I am connecting over remote desktop connetion to the server.

With in the databases i right click the database which has my three tables within them.

Then select all tasks->restore database

In restore i select files or file groups

then i select the day i want to restore the ok

It comes up with this error

Cannot open the back up device 'C:\programs\......'

device error or device online

Restore database is terminating abnormally

Is it because i am not doing at the server as i am connecting over remote desktop....

And my database has several tables apart from these three tables.is it possible for me just to restore these three tables.

i am using sql server 2000 database

Please let me know..

Are you using the GUI on the remote server or the GUI on your local machine? The GUI you use will need to be on the machine that the file resides if you are using localfile paths.

Also, you will only be able to restore those 3 tables using a PARTIAL restore if they exist in a separate filegroup to the rest of the data.If you only have one filegroup then you will have to restore the whole thing.

Either way, i think your only option is to do the restore to a separate database and then copy the data to your "live" db.

Check out the RESTORE information in Books Online as this gives a fairly thorough rundown of all the options.

HTH!

|||

Hi,

YOU CAN RETRIEVE THE BACKUP DATA FROM THE DELETED DATA..

I AM WORKING WITH SQL SERVER 2005.

JUST TRY ONCE AFTER THAT YOU CAN!!!!!!!!!!

Recovery Plan -

I want to make sure that what I'm thinking can actually be
done.
We currently have our production server with the datafiles
(including systems) on one removeable drive (E) and the
logs on another (F).We maintain a backup server that hold
all the data/log files on the D drive. Both server's have
the same server configurations.
The backup server is kept up to date via log shipping. If
we had disk failure, we would be able to bring the
databases out of standby mode and rename the server (with
a few other steps in there)...
HERE"S MY REAL QUESTION -
Now if we had a different failure where we had our disk
drives, but could no longer use the server, would the
following be possible.
Could we add the E and F drive to the backup server.
leaving the exsisting database in place. Modify the SQL
Server startup paramenters to use the master database on
the E drive instead of the D drive.
The master on the E drive would then point to all the
databases we have on the E and F drive and we would be
ready to go'
I hope that makes sense... It just seems a little too
easy...
Please advise and poke holes.
ThanksDefine removable drive here ... I'm not sure what you mean.
If you had a disk failure, why would you bother even
attempting an operation that may not work if your log
shipped secondary is brought online? I assume you'd want
to do some sort of attach, but that makes no sense. You
still have issues of DB users, etc.
You would also be changing the drive signatures, etc. I
wouldn't go there. And renaming everything (server, IP,
etc.) is always IMHO not the way to go. Your DR plans
should be able to tolerate the name change of the server
in a log shipping situation. Too many manual steps, too
many moving parts ... too many things that could go wrong.
Log shipping just works.|||By removable drives I mean external drives that can be
taken from one server and added to another. We do this
right now when we have large backups (150gig)that we need
to move to different servers. You haven't heard of this
before?
Since our log shipping server can be up to an hour behind,
if we have our production data we would prefer to use
that. The log shipping server is to be used only when we
cannot recovery the data from production.
Our current failover method does have attaching involved,
but I was thinking if my system databases are on the drive
we just moved over, why couldn't I point my SQL startup
paraments to the new master database, which in turn would
already have the databases/logins already setup.
>--Original Message--
>Define removable drive here ... I'm not sure what you
mean.
>If you had a disk failure, why would you bother even
>attempting an operation that may not work if your log
>shipped secondary is brought online? I assume you'd want
>to do some sort of attach, but that makes no sense. You
>still have issues of DB users, etc.
>You would also be changing the drive signatures, etc. I
>wouldn't go there. And renaming everything (server, IP,
>etc.) is always IMHO not the way to go. Your DR plans
>should be able to tolerate the name change of the server
>in a log shipping situation. Too many manual steps, too
>many moving parts ... too many things that could go wrong.
>Log shipping just works.
>
>.
>

Recovery model problem; db properities

Hello,

I've follow problem - thing to consider.

SQLServer 200 sp3a, ms win 2003 server
db simple recovery

There is a production database, wich is around 20gb big. Db is backed
up each day completely, but it takes up to 30 minutes.
Because there is a simple recovery model, there is no transaction log
backup (it fails anyway), and we do not have up-to-point recovery.

I'm considering to switch to full recovery model, but ...
The problem is, I do not want to affect performance (when the backup is
running, database is hardly avalible).

So my question will be: does the full recovery model, will be better
for db performance (for acces and blocking db; means, does it will take
shorter?)
Strategy will be (I hope ok) to back up during the week only
transaction log (incremental), and once at the weekend, full database
backup.

Generaly, which one is better for performance?
Which strategy will be the best, to keep performance at high level, but
also have the possibility to restore data (in case of emergency) from
the newest possible backup.

Thanks for help

Matik"Matik" <marzec@.sauron.xo.pl> wrote in message
news:1140084783.803830.233070@.g14g2000cwa.googlegr oups.com...
> Hello,
>
> I've follow problem - thing to consider.
> SQLServer 200 sp3a, ms win 2003 server
> db simple recovery
> There is a production database, wich is around 20gb big. Db is backed
> up each day completely, but it takes up to 30 minutes.

What's the form of backup? disk, NAS, tape?

> Because there is a simple recovery model, there is no transaction log
> backup (it fails anyway), and we do not have up-to-point recovery.
> I'm considering to switch to full recovery model, but ...
> The problem is, I do not want to affect performance (when the backup is
> running, database is hardly avalible).

That's unusual. Generally a full-backup shouldn't hurt performance that
much.

If it really is, I'd do some more digging and try to find out why.

> So my question will be: does the full recovery model, will be better
> for db performance (for acces and blocking db; means, does it will take
> shorter?)

We do backups of similar size databases every 20 minutes with no noticable
impact on performance. I may eventually move to 10 minute backup windows.
Generally the backups shouldn't be blocking the db at all, the biggest cost
is generally disk I/O.

> Strategy will be (I hope ok) to back up during the week only
> transaction log (incremental), and once at the weekend, full database
> backup.

Only problem with this may be that in the event of a failure, say right
before you do your weekly full, you'll have a LOT of transaction logs to
restore. This will impact your time to recovery, so take that into account.
You may also want to use differential backups during the week to speed
things up in the event of having to recovery.

> Generaly, which one is better for performance?
> Which strategy will be the best, to keep performance at high level, but
> also have the possibility to restore data (in case of emergency) from
> the newest possible backup.
> Thanks for help
> Matik|||Matik (marzec@.sauron.xo.pl) writes:
> I'm considering to switch to full recovery model, but ...
> The problem is, I do not want to affect performance (when the backup is
> running, database is hardly avalible).

Then you have something investigate. The footprint of a backup should
be light. Database should certainly be available during this time.

> So my question will be: does the full recovery model, will be better
> for db performance (for acces and blocking db; means, does it will take
> shorter?)
> Strategy will be (I hope ok) to back up during the week only
> transaction log (incremental), and once at the weekend, full database
> backup.

Daily differential backups would be a better choice in that case.

Most of our customers run a daily full backup, and then translog backups
at least once an hour, some every ten or fifteen minutes.

Depending on your activity in the database, the log can grow big it
you back it up once a day. If your run a maintenance job, it could
grow bigger than the data file itself.

> Generaly, which one is better for performance?
> Which strategy will be the best, to keep performance at high level, but
> also have the possibility to restore data (in case of emergency) from
> the newest possible backup.

The backup strategy should be determined of your requirements for
disaster recovery. If you are content with restoring a backup in
case of failure, continue with simple recovery. Switch to full if
you want up-to-the-point recovery.

A tip is that if you go for full recovery, is that you should allocate
a couple of GB for the log file on the spot, to prevent autogrow
growing the file piece by piece, which could lead to fragmentation
on file-syste level.

--
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.mspxsql

Recovery from a database Image

Hello,
First...this isn't a production recover issue.
I have a image of my hard drive that includes all my sql server databases
"in the raw". I suffered a hard disk crash and have reinstalled SQL Server
etc...How can I get these databases back. I tried just copying the two data
files from the "Data" directory off my backup onto the new SQL Server
install...but no cigar.
Surely there is a way to do this.
Regards,
Paul Reed
Jackson-Reed, Inc. www.jacksonreed.com
You can try to attach each database using sp_attach_db (or the Enterprise
Manager attach). This might not work if the databases weren't cleanly
detached, though. See the Books Online for more information.
Hope this helps.
Dan Guzman
SQL Server MVP
"paul" <paul@.discussions.microsoft.com> wrote in message
news:6515DCCF-A02E-4ACD-B59A-C22BB63D087B@.microsoft.com...
> Hello,
> First...this isn't a production recover issue.
> I have a image of my hard drive that includes all my sql server databases
> "in the raw". I suffered a hard disk crash and have reinstalled SQL Server
> etc...How can I get these databases back. I tried just copying the two
> data
> files from the "Data" directory off my backup onto the new SQL Server
> install...but no cigar.
> Surely there is a way to do this.
> Regards,
> Paul Reed
> --
> Jackson-Reed, Inc. www.jacksonreed.com
|||You might also
1. Open a call to MS PSS, maybe they have some magic ( but I doubt you'll be
able to recover.) Try them anyway, only $250
2. When you get past all of this, set up a good database maintenance plan to
backup and maintain your databases..
Good luck friend!
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.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
"paul" <paul@.discussions.microsoft.com> wrote in message
news:6515DCCF-A02E-4ACD-B59A-C22BB63D087B@.microsoft.com...
> Hello,
> First...this isn't a production recover issue.
> I have a image of my hard drive that includes all my sql server databases
> "in the raw". I suffered a hard disk crash and have reinstalled SQL Server
> etc...How can I get these databases back. I tried just copying the two
data
> files from the "Data" directory off my backup onto the new SQL Server
> install...but no cigar.
> Surely there is a way to do this.
> Regards,
> Paul Reed
> --
> Jackson-Reed, Inc. www.jacksonreed.com

Recovery from a database Image

Hello,
First...this isn't a production recover issue.
I have a image of my hard drive that includes all my sql server databases
"in the raw". I suffered a hard disk crash and have reinstalled SQL Server
etc...How can I get these databases back. I tried just copying the two data
files from the "Data" directory off my backup onto the new SQL Server
install...but no cigar.
Surely there is a way to do this.
Regards,
Paul Reed
--
---
Jackson-Reed, Inc. www.jacksonreed.comYou can try to attach each database using sp_attach_db (or the Enterprise
Manager attach). This might not work if the databases weren't cleanly
detached, though. See the Books Online for more information.
Hope this helps.
Dan Guzman
SQL Server MVP
"paul" <paul@.discussions.microsoft.com> wrote in message
news:6515DCCF-A02E-4ACD-B59A-C22BB63D087B@.microsoft.com...
> Hello,
> First...this isn't a production recover issue.
> I have a image of my hard drive that includes all my sql server databases
> "in the raw". I suffered a hard disk crash and have reinstalled SQL Server
> etc...How can I get these databases back. I tried just copying the two
> data
> files from the "Data" directory off my backup onto the new SQL Server
> install...but no cigar.
> Surely there is a way to do this.
> Regards,
> Paul Reed
> --
> ---
> Jackson-Reed, Inc. www.jacksonreed.com|||You might also
1. Open a call to MS PSS, maybe they have some magic ( but I doubt you'll be
able to recover.) Try them anyway, only $250
2. When you get past all of this, set up a good database maintenance plan to
backup and maintain your databases..
Good luck friend!
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.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
"paul" <paul@.discussions.microsoft.com> wrote in message
news:6515DCCF-A02E-4ACD-B59A-C22BB63D087B@.microsoft.com...
> Hello,
> First...this isn't a production recover issue.
> I have a image of my hard drive that includes all my sql server databases
> "in the raw". I suffered a hard disk crash and have reinstalled SQL Server
> etc...How can I get these databases back. I tried just copying the two
data
> files from the "Data" directory off my backup onto the new SQL Server
> install...but no cigar.
> Surely there is a way to do this.
> Regards,
> Paul Reed
> --
> ---
> Jackson-Reed, Inc. www.jacksonreed.com

Recovery from a database Image

Hello,
First...this isn't a production recover issue.
I have a image of my hard drive that includes all my sql server databases
"in the raw". I suffered a hard disk crash and have reinstalled SQL Server
etc...How can I get these databases back. I tried just copying the two data
files from the "Data" directory off my backup onto the new SQL Server
install...but no cigar.
Surely there is a way to do this.
Regards,
Paul Reed
--
---
Jackson-Reed, Inc. www.jacksonreed.comYou can try to attach each database using sp_attach_db (or the Enterprise
Manager attach). This might not work if the databases weren't cleanly
detached, though. See the Books Online for more information.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"paul" <paul@.discussions.microsoft.com> wrote in message
news:6515DCCF-A02E-4ACD-B59A-C22BB63D087B@.microsoft.com...
> Hello,
> First...this isn't a production recover issue.
> I have a image of my hard drive that includes all my sql server databases
> "in the raw". I suffered a hard disk crash and have reinstalled SQL Server
> etc...How can I get these databases back. I tried just copying the two
> data
> files from the "Data" directory off my backup onto the new SQL Server
> install...but no cigar.
> Surely there is a way to do this.
> Regards,
> Paul Reed
> --
> ---
> Jackson-Reed, Inc. www.jacksonreed.com|||You might also
1. Open a call to MS PSS, maybe they have some magic ( but I doubt you'll be
able to recover.) Try them anyway, only $250
2. When you get past all of this, set up a good database maintenance plan to
backup and maintain your databases..
Good luck friend!
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.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
"paul" <paul@.discussions.microsoft.com> wrote in message
news:6515DCCF-A02E-4ACD-B59A-C22BB63D087B@.microsoft.com...
> Hello,
> First...this isn't a production recover issue.
> I have a image of my hard drive that includes all my sql server databases
> "in the raw". I suffered a hard disk crash and have reinstalled SQL Server
> etc...How can I get these databases back. I tried just copying the two
data
> files from the "Data" directory off my backup onto the new SQL Server
> install...but no cigar.
> Surely there is a way to do this.
> Regards,
> Paul Reed
> --
> ---
> Jackson-Reed, Inc. www.jacksonreed.comsql

Recovery

Dear Guys...
Let's assume I have a Database Name "Production" and I have two Harddisk C
and D. In C drive I have production.mdf file and in D Drive I have
production.ldf. After a month C drive has been corrupted but D drive is
still live so now I am in a position to recover whole data or not through
production.LDF file?
Thanks
NOOR
Only if you have a backup of the database. Then you make a backup of the
current transaction log, and then restore the database and the transaction
log in order.
Jacco Schalkwijk
SQL Server MVP
"Noor" <noor@.ngsol.com> wrote in message
news:eirYAKpYEHA.4004@.TK2MSFTNGP10.phx.gbl...
> Dear Guys...
> Let's assume I have a Database Name "Production" and I have two Harddisk C
> and D. In C drive I have production.mdf file and in D Drive I have
> production.ldf. After a month C drive has been corrupted but D drive is
> still live so now I am in a position to recover whole data or not through
> production.LDF file?
> Thanks
> NOOR
>
|||Hi,
With LDF file you can not recover the database. LDF file contains only
active transactions.
In the otherway if you have the MDF file you can try recovering the
database using sp_attach_single_file_db (see books online).
In your case only way to recover the database is using the last full
database backup. After that you can apply the transaction log backups,
provided if you have taken transaction log backup.
Thanks
Hari
MCDBA
"Noor" <noor@.ngsol.com> wrote in message
news:eirYAKpYEHA.4004@.TK2MSFTNGP10.phx.gbl...
> Dear Guys...
> Let's assume I have a Database Name "Production" and I have two Harddisk C
> and D. In C drive I have production.mdf file and in D Drive I have
> production.ldf. After a month C drive has been corrupted but D drive is
> still live so now I am in a position to recover whole data or not through
> production.LDF file?
> Thanks
> NOOR
>

Recovering from resource problems

Hi,
Yesterday we had some 701 resource messages on one of our production
servers. This was followed by a number of Downgrading backup log buffers
from 1024K to 64K messages in our backup jobs. This is an SQL2005 build 3159
server on W2K3 SP2. We had similar problems last year with an SQL2000 server
and we found that a reboot or stop/start SQL appeared the only way to stop
the problem. We did this last night on this server.
Is this the best way on SQL2005 or will it recover from its resource
problems without a reboot or stop/start SQL?
Thanks
ChrisIt is hard to say if this would address the specific problem but this is
about as close as you can get w/o a restart:
dbcc dropcleanbuffers
DBCC FREESYSTEMCACHE ( 'ALL' ) WITH MARK_IN_USE_FOR_REMOVAL
exec sp_msforeachdb 'alter ? set single_user with rollback immediate'
exec sp_msforeachdb 'alter ? set multi_user with rollback immediate'
Be careful. I'd use this like a hail mary with 2 seconds left.
--
Jason Massie
Web: http://statisticsio.com
RSS: http://feeds.feedburner.com/statisticsio
"Chris Wood" <anonymous@.microsoft.com> wrote in message
news:O$Ta6z0jIHA.5084@.TK2MSFTNGP04.phx.gbl...
> Hi,
> Yesterday we had some 701 resource messages on one of our production
> servers. This was followed by a number of Downgrading backup log buffers
> from 1024K to 64K messages in our backup jobs. This is an SQL2005 build
> 3159 server on W2K3 SP2. We had similar problems last year with an SQL2000
> server and we found that a reboot or stop/start SQL appeared the only way
> to stop the problem. We did this last night on this server.
> Is this the best way on SQL2005 or will it recover from its resource
> problems without a reboot or stop/start SQL?
> Thanks
> Chris
>|||That is pretty harsh!!! I was hoping that SQL2005 was more robust than
SQL2000.
Thanks
Chris
"Jason Massie" <jason**R3move**@.statisticsio.com> wrote in message
news:ud9ZVO1jIHA.4940@.TK2MSFTNGP02.phx.gbl...
> It is hard to say if this would address the specific problem but this is
> about as close as you can get w/o a restart:
> dbcc dropcleanbuffers
> DBCC FREESYSTEMCACHE ( 'ALL' ) WITH MARK_IN_USE_FOR_REMOVAL
> exec sp_msforeachdb 'alter ? set single_user with rollback immediate'
> exec sp_msforeachdb 'alter ? set multi_user with rollback immediate'
> Be careful. I'd use this like a hail mary with 2 seconds left.
> --
> Jason Massie
> Web: http://statisticsio.com
> RSS: http://feeds.feedburner.com/statisticsio
>
> "Chris Wood" <anonymous@.microsoft.com> wrote in message
> news:O$Ta6z0jIHA.5084@.TK2MSFTNGP04.phx.gbl...
>> Hi,
>> Yesterday we had some 701 resource messages on one of our production
>> servers. This was followed by a number of Downgrading backup log buffers
>> from 1024K to 64K messages in our backup jobs. This is an SQL2005 build
>> 3159 server on W2K3 SP2. We had similar problems last year with an
>> SQL2000 server and we found that a reboot or stop/start SQL appeared the
>> only way to stop the problem. We did this last night on this server.
>> Is this the best way on SQL2005 or will it recover from its resource
>> problems without a reboot or stop/start SQL?
>> Thanks
>> Chris
>

recover - how do I tell if it is really happening?

Hello all -
this is the first restore I've attempted on a real production database.
I used EM to execute the restore, and it correctly found my last full backup
, diffs and tran log files.
(I run full recovery mode).
I can see in the log where things are happening, and the status of the datab
ase is being displayed as loading.
But after 3.5 hours you just start to wonder if anything is really happening
.. Any advice?How long did the backup take? Restore is usually longer. Sometimes 2 or 3x
longer.
Run sp_who2 and see if the CPU and IO counters change for the restore task.
Watch the blinkey lights on the case.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"randyvol" <randy.volters@.whaleyfoodservice.com> wrote in message
news:81408CF6-B061-4514-87C7-D582E3DF9058@.microsoft.com...
> Hello all -
> this is the first restore I've attempted on a real production database.
> I used EM to execute the restore, and it correctly found my last full
backup, diffs and tran log files.
> (I run full recovery mode).
> I can see in the log where things are happening, and the status of the
database is being displayed as loading.
> But after 3.5 hours you just start to wonder if anything is really
happening... Any advice?|||Hi Randy.
For future reference, you might find RESTORE's STATS option useful. I use
this pretty much on autopilot - RESTORE.. WITH STATS=10 - it writes a
progress response to the console / query analyser every 10 percent. That way
you get an idea of how far the restore's progressed.
HTH
Regards,
Greg Linwood
SQL Server MVP
"randyvol" <randy.volters@.whaleyfoodservice.com> wrote in message
news:81408CF6-B061-4514-87C7-D582E3DF9058@.microsoft.com...
> Hello all -
> this is the first restore I've attempted on a real production database.
> I used EM to execute the restore, and it correctly found my last full
backup, diffs and tran log files.
> (I run full recovery mode).
> I can see in the log where things are happening, and the status of the
database is being displayed as loading.
> But after 3.5 hours you just start to wonder if anything is really
happening... Any advice?|||Hi Randy,
I am reviewing your post and we have not heard from you for some time. I
want to know if your restore is fine now. Our community members have
provide some informaitons by using WITH STATS in recovery and it might be
longer than backup. If you still have questions, please feel free to let me
know and we are glad to help.
Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.

recover - how do I tell if it is really happening?

Hello all -
this is the first restore I've attempted on a real production database.
I used EM to execute the restore, and it correctly found my last full backup, diffs and tran log files.
(I run full recovery mode).
I can see in the log where things are happening, and the status of the database is being displayed as loading.
But after 3.5 hours you just start to wonder if anything is really happening... Any advice?
How long did the backup take? Restore is usually longer. Sometimes 2 or 3x
longer.
Run sp_who2 and see if the CPU and IO counters change for the restore task.
Watch the blinkey lights on the case.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"randyvol" <randy.volters@.whaleyfoodservice.com> wrote in message
news:81408CF6-B061-4514-87C7-D582E3DF9058@.microsoft.com...
> Hello all -
> this is the first restore I've attempted on a real production database.
> I used EM to execute the restore, and it correctly found my last full
backup, diffs and tran log files.
> (I run full recovery mode).
> I can see in the log where things are happening, and the status of the
database is being displayed as loading.
> But after 3.5 hours you just start to wonder if anything is really
happening... Any advice?
|||Hi Randy.
For future reference, you might find RESTORE's STATS option useful. I use
this pretty much on autopilot - RESTORE.. WITH STATS=10 - it writes a
progress response to the console / query analyser every 10 percent. That way
you get an idea of how far the restore's progressed.
HTH
Regards,
Greg Linwood
SQL Server MVP
"randyvol" <randy.volters@.whaleyfoodservice.com> wrote in message
news:81408CF6-B061-4514-87C7-D582E3DF9058@.microsoft.com...
> Hello all -
> this is the first restore I've attempted on a real production database.
> I used EM to execute the restore, and it correctly found my last full
backup, diffs and tran log files.
> (I run full recovery mode).
> I can see in the log where things are happening, and the status of the
database is being displayed as loading.
> But after 3.5 hours you just start to wonder if anything is really
happening... Any advice?
|||Hi Randy,
I am reviewing your post and we have not heard from you for some time. I
want to know if your restore is fine now. Our community members have
provide some informaitons by using WITH STATS in recovery and it might be
longer than backup. If you still have questions, please feel free to let me
know and we are glad to help.
Thanks.
Best regards
Baisong Wei
Microsoft Online Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.