log shipping vs. Replication

>Now, having said that, once box A is back up, in an ideal
>world, why would you make the switch back to A as a
>primary since B should hopefully have the same capacity.
>
Because BoxA is in a location that meets the specs for our
customers. BoxB is not.

>As for a full restore back on A, it depends on what state
>it was in, where the secondary was, etc. Even if you
wind
>up depending on your situation having to do a full
restore
>on A, you essentially set up log shipping. Do your point
>in time on B, restore on A, then use log shipping to
catch
>up.
Ive never used it so please bear with me. I was told that
I would have to:
Take a full backup of BoxB.
Transfer it to the Location of BoxA.
Restore it on BoxA.
Is this not the case? I thought it sounded odd but was re-
assured.
The way I look at it is
1) Clustering replicates/clones a server
2) backing up and restoring the database to the standy server, replicates
the database
3) Log Shipping is a continous backup and restore of the database
4) replication replicates transactions
It depends on your requirements, and how expensive downtime is to you, or
how valuable your data is. For disaster recovery most people look at
clustering solutions.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Allan Hirt" <anonymous@.discussions.microsoft.com> wrote in message
news:53e601c47424$b14a55a0$a601280a@.phx.gbl...
> Usually it is a capacity issue, not one like this. So if
> Box B is in an unsuitable location, do your customers
> know? Usually this is part of any SLA you establish with
> them.
>
> Again, it depends, especially on the type of failure. If
> you were able to grab the tail of the log on the primary,
> and at some point get it to standby, the secondary when
> all logs are applied at the time BEFORE you redirect
> traffic, they are in the same place data/etc. wise.
> Now, if your DBs are inconsistent, it's pretty much
> impossible. Remember that backup is an online operation,
> so if you need to do a full backup, do it, still allow
> work on B, restore the backup on A, then configure log
> shipping from B to A, and make the switch. It's pretty
> painless.
> If you did it your way, you would need to pretty much stop
> activity on B to ensure they are at the same point, which
> is probably what you don't want to do. Transaction logs
> exist for a reason.
> So again, it is completely dependent upon what state
> you're in at the time of failure.
> I've had customers do upgrades using log shipping and
> we've incurred only minutes of actual downtime because of
> it.

Log Shipping -SQL 2000

Is there a way to detach a database that is in warm
standby mode and attach it back in the same mode and
continue with T-logs restores ?Not to my knowledge, no.
Why would you want to do such a thing? It seems illogical.
>--Original Message--
>Is there a way to detach a database that is in warm
>standby mode and attach it back in the same mode and
>continue with T-logs restores ?
>.
>sql

Log shipping recover

I have changed the roles of primary and secondary servers due to server failure.
Can anyone advise how to revert back to previous main server? Are these any links available?See BOL topic:
How to set up and perform a log shipping role change (Transact-SQL)

In couple words - you have to set up log shipping again (move last backup from secondary to primary with stopping any activity of course on first one).|||If I set up log shipping with the old server, it becomes secondary. But I want to make my old server primary again.

Would I need to copy the db from current primary to old primary server, switch off the current server and switch on the old one?

Log Shipping question

Hi!
I managed to make a plan of log shipping and have some questions.
In the first trn back up I recieved an error
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201: [Microsoft][ODBC SQL
Server Driver][SQL Server]Cannot open backup device
'D:\logshipping\Pergam2_tlog_200312250945.TRN'. Device error or device
off-line. See the SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
abnormally.
All other back ups are fine and databases seeens to be identical. But Log
shipping monitor shows out of sync ?!!!
What it can be?
if backup/restore or restore fails what will be with databases in the next
step when all will work fine?
Thanks
DmitryI have seen messages like this sometimes on our log
shipping installation too. I believe Sql Server sometimes
starts reading the log files even before they have been
completely transferred. This seems to be best ignored. Set
your monitor to a higher out of sync value.
If the databases get out of sync, the best way is to back
up and restore them and restart log shipping.
>--Original Message--
>Hi!
>I managed to make a plan of log shipping and have some
questions.
>In the first trn back up I recieved an error
>[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201:
[Microsoft][ODBC SQL
>Server Driver][SQL Server]Cannot open backup device
>'D:\logshipping\Pergam2_tlog_200312250945.TRN'. Device
error or device
>off-line. See the SQL Server error log for more details.
>[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE
LOG is terminating
>abnormally.
>All other back ups are fine and databases seeens to be
identical. But Log
>shipping monitor shows out of sync ?!!!
>What it can be?
>if backup/restore or restore fails what will be with
databases in the next
>step when all will work fine?
>Thanks
>Dmitry
>
>.
>

Log shipping Fail over

Hi Paul,
To switch back roles from the new primary to old primary, why you need to
rename the server, use sp_dropserver, sp_addserver and restart the services?
Thanks for your help.
Pierre,
the reason is that you can't (easily) have 2 computers with the same NETBIOS
name on the same LAN.
Rgds,
Paul Ibison (SQL Server MVP)
|||Pierre,
Normally in log shipping role changes you do not change the server names.
Instead, the application must change its connection string to reference the
correct server.
Ron
Ron Talmage
SQL Server MVP
"Pierre Pilon" <Pierre Pilon@.discussions.microsoft.com> wrote in message
news:36E83F31-CEC9-4082-ABAF-96AC51DBA8BC@.microsoft.com...
> Hi Paul,
> To switch back roles from the new primary to old primary, why you need to
> rename the server, use sp_dropserver, sp_addserver and restart the
services?
> Thanks for your help.
|||Ron,
with respect, I think this depends on the setup
implemented. EG if there are loads of desktop
applications using DSNs which refer to the servername,
then changing each connection string may not be so
feasible. Also, if linked servers are being used to
reference the production server with 4-part qualified
names this will cause issues. Rescuing replication with
existing subscribers would be another issue, although
the 'standard' seems to be setting it up from scratch.
Master-slave jobs would probably be another difficulty.
Rgds,
Paul Ibison (SQL Server MVP)

Log Shipping and Backup Log

Hello,
Can anyone tell me whether having your log file back up
affects the Log Shipping in any way ?
Jim
Hi
Yes it does as log shipping relies on dumping and re-applying each log dump
in sequence.
If you need to do an out of sequence dump, run the job created by log
shipping.
What is your scenario?
Regards
Mike
"Jimbo" wrote:

> Hello,
> Can anyone tell me whether having your log file back up
> affects the Log Shipping in any way ?
> Jim
>
|||Thanks for your reply.
As part of our disaster recovery we want a warm standby
machine, with log shipping, from out Production Server to
our Warm Standby server.
We also want to backup the log file from our production
server once every 10 minutes.
I suppose my question is can we do both ?
TIA

>--Original Message--
>Hi
>Yes it does as log shipping relies on dumping and re-
applying each log dump
>in sequence.
>If you need to do an out of sequence dump, run the job
created by log
>shipping.
>What is your scenario?
>Regards
>Mike
>"Jimbo" wrote:
>.
>