Re: STANDBY mode

Thanks for the help. Works now. It's permission related.


"Tibor Karaszi" <tibor_please.no.email_karaszi@xxxxxxxxxxxxxxxxxx> wrote in
message news:u5ZhuUaqKHA.5736@xxxxxxxxxxxxxxxxxxxxxxx
I'm thinking put it to recovery and then apply next transation log file
with
NOCOVERY, can I do that?

As already stated: No.


I still can't make standby mode works, actually there are no tuf files
in
primary/secondary, it related to restore process, and also with nocovery
mode, copy/restore works fine.

I'm sorry, but above sentence is hard to make heads and tails out of.
Standby work just fine. Probably you are using some tool whcih constructs
the restore commands for you and possibly copies the undo file to some
other
location - which is what is causing your problems. You need to
troubleshoot
this tool - that is where the problem is, not with the RESTORE and STANDBY
process. Possibly the tool is the log shipping functionality which is
shipped with the product.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi



<someone@xxxxxx> wrote in message
news:eMtEmPaqKHA.4636@xxxxxxxxxxxxxxxxxxxxxxx
Thanks Kalen,

I'm thinking put it to recovery and then apply next transation log file
with
NOCOVERY, can I do that?

I still can't make standby mode works, actually there are no tuf files
in
primary/secondary, it related to restore process, and also with nocovery
mode, copy/restore works fine.
How to find out why and fix for stanndby mode?


"Kalen Delaney" <please_reply_on_newsgroups@xxxxxxxxxx> wrote in message
news:37B55CFE-5C33-4E32-B960-E11F9062095A@xxxxxxxxxxxxxxxx
Once you have run RECOVERY, you cannot restore any more logs.

It is exactly the purpose of STANDBY to let access the db to check
values
and integrity, and then to keep restoring logs.
As Tibor has said already "That is what STANDBY is for"!

--
HTH
Kalen
----------------------------------------
Kalen Delaney
SQL Server MVP
www.SQLServerInternals.com

<someone@xxxxxx> wrote in message
news:unwL0TQqKHA.4492@xxxxxxxxxxxxxxxxxxxxxxx
Thansk Tibor,

After swith with RECOVERY, how to make it restoring, ready for
restoring
log again? I'm thinking sometimes need to check the data integrity.


"Tibor Karaszi" <tibor_please.no.email_karaszi@xxxxxxxxxxxxxxxxxx>
wrote
in
message news:u59TN9PqKHA.4284@xxxxxxxxxxxxxxxxxxxxxxx
Are you asking of one can get to a database restore using
NORECOVERY?
If
so,
the answer is no. That is what STANDBY is for (or, of course,
RECOVERY).

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi



<someone@xxxxxx> wrote in message
news:OlHuqqPqKHA.1144@xxxxxxxxxxxxxxxxxxxxxxx
Thanks Tibor,

Using NORECOVERY mode, is it possbile to run some query to simple
check
the
secondary data, for example, how many records in clients table
compare
with
primary database.



"Tibor Karaszi" <tibor_please.no.email_karaszi@xxxxxxxxxxxxxxxxxx>
wrote
in
message news:%23e$dsLJqKHA.5696@xxxxxxxxxxxxxxxxxxxxxxx
There is something strange going on here. You say you do STANDBY
with
below
and undo file name:





STANDBY='C:\Database\SecondaryData\DatabaseBackup\ROLLBACK_UNDO_DisasterData
base.BAK'

But the error message from SQL Server tells a very different
story.
According to the error message, the prior restore was done with
below
as
standby file:

\\X-Database\SecondaryData\Logs\x_20100205054523.tuf'

And, according to the error message, above file doesn't exist.
So,
the
process seems messed up. Or perhaps above is the standby file for
a
following log restore? Ah, yes, I now see that in the error
message.
So,
probably the first log restore using the standby file (the one
you
created)
was OK. But a following log restore failed, because a prior
standby
file
was
inaccessible (network drive not available, somebody deleted the
file
or
something like that).

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi



<someone@xxxxxx> wrote in message
news:OCJa4XnpKHA.1548@xxxxxxxxxxxxxxxxxxxxxxx
Thanks Tibor,

I restore as:
RESTORE DATABASE cashx
FROM disk ='C:\Database\SecondaryData\DatabaseBackup\mydb.bak'
WITH




STANDBY='C:\Database\SecondaryData\DatabaseBackup\ROLLBACK_UNDO_DisasterData
base.BAK'

The old log files system will handle: Skipped log backup file.
Secondary
DB:
xxx

and the database is Standby/Read-Only, but store log failed:
Message
2010-02-05 00:45:26.50 *** Error: Could not apply log backup
file
'\\Database\SecondaryData\Logs\x_20100205011501.trn' to
secondary
database
'cashx'.(Microsoft.SqlServer.Management.LogShipping) ***
2010-02-05 00:45:26.50 *** Error: During startup of warm
standby
database
'x' (database ID 7), its standby file
('\\X-Database\SecondaryData\Logs\x_20100205054523.tuf') was
inaccessible
to
the RESTORE statement. The operating system error was '5(Access
is
denied.)'. Diagnose the operating system error, correct the
problem,
and
retry startup.
RESTORE LOG is terminating abnormally.
Processed 0 pages for database 'x', file 'x_Data' on file 1.
Processed 841 pages for database 'x', file 'x_Log' on file
1.(.Net
SqlClient
Data Provider) ***

I checked, I don't have tuf file. Can you please help here?




"Tibor Karaszi"
<tibor_please.no.email_karaszi@xxxxxxxxxxxxxxxxxx>
wrote
in
message news:OBZrblRpKHA.4348@xxxxxxxxxxxxxxxxxxxxxxx
Use the STANDBY option of the RESTORE command (along with a
file
to
be
created by the restore process where to keep the info needed
in
order
to
undo the UNDO performed by the recovery process). Or, you can
also
use
NORECOVERY. What you can't use is ECOVERY (or none of these
options).

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi



<someone@xxxxxx> wrote in message
news:ugSsJMRpKHA.1548@xxxxxxxxxxxxxxxxxxxxxxx
Hi Tibor,
How to put database in standby mode when restoring from a
full
back?
Thanks.


"Tibor Karaszi"
<tibor_please.no.email_karaszi@xxxxxxxxxxxxxxxxxx>
wrote
in
message news:uGm2jmQpKHA.3748@xxxxxxxxxxxxxxxxxxxxxxx
You can't. I.e., you need to re-do a prior database restore
and
get
going
from there.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi



<someone@xxxxxx> wrote in message
news:#ww1cVQpKHA.5224@xxxxxxxxxxxxxxxxxxxxxxx
Hi how to put the database to standby mode for log
shipping:
*** Error: The restore operation cannot proceed
because the secondary database 'mydatabase' is not in
NORECOVERY/STANDBY
mode.(Microsoft.SqlServer.Management.LogShipping)

Thanks...














.

Relevant Pages

  • Re: Database Restore Error
    ... Tibor Karaszi, SQL Server MVP ... I changed the default database to master and then tried opening the restore window and the connection was not there. ...
    (microsoft.public.sqlserver.tools)
  • Re: Another question about DB Mirroring
    ... changed with my domain account and I have to re set manually. ... domain account") when you do that restore. ... Tibor Karaszi, SQL Server MVP ...
    (microsoft.public.sqlserver.setup)
  • Thank you!
    ... Just for the sake of completeness, as of 2005, we are recommended to ... use a modern way to move database files: ... Tibor Karaszi, SQL Server MVP ...
    (microsoft.public.sqlserver.server)
  • Re: problem with query moving data from 1 dbase to another.
    ... You register a SQL Server instance, where such an instance can have several databases. ... Tibor Karaszi, SQL Server MVP ... > you know how to connect to an existing database, ... >> Tibor Karaszi, SQL Server MVP ...
    (microsoft.public.sqlserver.server)
  • Re: Moving a database
    ... it doesn't matter how you do the restore. ... >> nel messaggio news:uN4JIG0CEHA.3348@TK2MSFTNGP11.phx.gbl... ... >>> Tibor Karaszi, SQL Server MVP ...
    (microsoft.public.sqlserver.tools)