log shipping question

What happens when you check the " Allow database to assume primary role"
option during log shipping setup. What happens if you dont check it ?
Also, does anyone have any links as far as recovery procedures for a log
shipping implementation used for disaster recovery..i.e. if Server A fails,
what are the exact steps to follow to recover the application onto Server B
which would also include changing the servername from Server B to Server A
...
Allow database to assume primary role - When this option is enabled, this secondary server becomes the primary server if there are any problems on the original primary server. If you select this option, you must provide a share where the transaction logs
are stored when the server assumes the role of a primary server (for example, (\\secondary_computername\sharename).
KBA http://support.microsoft.com/default...314515&sd=tech about complete FAQ sheet on Log shipping.
--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Performance topic.
"Hassan" wrote:

> What happens when you check the " Allow database to assume primary role"
> option during log shipping setup. What happens if you dont check it ?
> Also, does anyone have any links as far as recovery procedures for a log
> shipping implementation used for disaster recovery..i.e. if Server A fails,
> what are the exact steps to follow to recover the application onto Server B
> which would also include changing the servername from Server B to Server A
> ...
>
>

log shipping question

What happens when you check the " Allow database to assume primary role"
option during log shipping setup. What happens if you dont check it ?
Also, does anyone have any links as far as recovery procedures for a log
shipping implementation used for disaster recovery..i.e. if Server A fails,
what are the exact steps to follow to recover the application onto Server B
which would also include changing the servername from Server B to Server A
...Allow database to assume primary role - When this option is enabled, this se
condary server becomes the primary server if there are any problems on the o
riginal primary server. If you select this option, you must provide a share
where the transaction logs
are stored when the server assumes the role of a primary server (for example
, (\\secondary_computername\sharename).
KBA http://support.microsoft.com/defaul...;314515&sd=tech a
bout complete FAQ sheet on Log shipping.
--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Perform
ance topic.
"Hassan" wrote:

> What happens when you check the " Allow database to assume primary role"
> option during log shipping setup. What happens if you dont check it ?
> Also, does anyone have any links as far as recovery procedures for a log
> shipping implementation used for disaster recovery..i.e. if Server A fails
,
> what are the exact steps to follow to recover the application onto Server
B
> which would also include changing the servername from Server B to Server A
> ...
>
>

log shipping question

What happens when you check the " Allow database to assume primary role"
option during log shipping setup. What happens if you dont check it ?
Also, does anyone have any links as far as recovery procedures for a log
shipping implementation used for disaster recovery..i.e. if Server A fails,
what are the exact steps to follow to recover the application onto Server B
which would also include changing the servername from Server B to Server A
...Allow database to assume primary role - When this option is enabled, this secondary server becomes the primary server if there are any problems on the original primary server. If you select this option, you must provide a share where the transaction logs are stored when the server assumes the role of a primary server (for example, (\\secondary_computername\sharename).
KBA http://support.microsoft.com/default.aspx?scid=kb;en-us;314515&sd=tech about complete FAQ sheet on Log shipping.
--
--
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on Performance topic.
"Hassan" wrote:
> What happens when you check the " Allow database to assume primary role"
> option during log shipping setup. What happens if you dont check it ?
> Also, does anyone have any links as far as recovery procedures for a log
> shipping implementation used for disaster recovery..i.e. if Server A fails,
> what are the exact steps to follow to recover the application onto Server B
> which would also include changing the servername from Server B to Server A
> ...
>
>

Log shipping fail over

I assume this is the correct spot for a log shipping question. Pardon if
it's not.
I've set up a log shipping pair (first time) and everything 'appears' to be
running fine, but I have a question about fail over.
In my research I have found that, in order to bring the secondary up as the
primary, I have to run a few procedures. The first of which is to be run on
the primary server to change its role. How would I do this if the server has
crashed? What steps should I take if this is the scenario?
Thanks in advance.
So what's the best fail over method should the primary server crash? This is
how I see it,
1) Run sp_change_secondary_role on the secondary server.
2) Switch app to point to secondary server or rename and re-IP secondary
server.
3) The users log into the application and the app uses one SQL login, so I
assume I don't need to worry too much about resolving logins.
This will get my users back to functional? What about once the old primary
is back up? Should I then run sp_change_primary_role? Or would it be best
to delete the maintenance jobs and recreate the log shipping pair?
Sorry about all of the questions, I've seen plenty of information on how to
change roles if the primary is still functional, but nothing concerning a
primary server crash.
Again, thanks in advance.
"Paul Ibison" wrote:

> Mick,
> you're correct - sp_change_primary_role removes the
> primary server from the maintenance plan and it will not
> usually be possible to do this in reality. The key
> failover procedure is sp_change_secondary_role which gets
> the last log and restores the system with recovery.
> Rgds,
> Paul Ibison (SQL Server MVP)
>
>
|||Mick,
Run sp_change_secondary_role, rename the server and use sp_dropserver,
sp_addserver, restart services. Create the login you require and use
sp_change_users_login if you haven't taken the SID.
There's no simple way of switching back roles to the primary, apart from
setting up a new log shipping pair and reversing the process.
The old maintenance plan at this stage is now defunct and needs to be
removed if the primary server comes online at some later stage.
HTH,
Paul Ibison (SQL Server MVP)
[vbcol=seagreen]