ADSM-L

Re: [ADSM-L] DP for SQL Server mirroring

2007-11-14 04:50:22
Subject: Re: [ADSM-L] DP for SQL Server mirroring
From: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 14 Nov 2007 10:49:03 +0100
Hi Del!
Let's say ServerA is the Principal and ServerB is the Mirror.
Normally you would schedule a DP backup on ServerA. The
(mirror-)database on ServerB is running in a state which doesn't allow
backing up (restore mode?)
Now there is a take-over and ServerB becomes the new Principal. Now you
will have to start backing up the database on ServerB.
And if everything is switched back to normal, you will be stuck with
backups on the ServerB DP node which never expire, since the backup is
running on ServerA again.
I hope I made myself a little bit more clear?
Again, thank you very much for your reply!!!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Del Hoobler
Sent: dinsdag 13 november 2007 16:28
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: DP for SQL Server mirroring

There is nothing built into DP for SQL that does that, but I am still
trying to understand what the issue is.
If you have an automated schedule to back up ALL databases (*) that are
active on any given SQL Server instance, it will find that the Principal
database is running on the second instance, and back it up from there.

Thanks,

Del

----------------------------------------------------


"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 11/13/2007
10:07:25 AM:

> Hi Del!
> I just spoke with the SQL guy and his question is a little bit more 
> clear to me now.
> The database is running on the Principal and a copy is running on the 
> Mirror.
> The database is backed up on the Principal. After a take-over the 
> Mirror becomes the new Principal, so the backup should be backed up on

> another physical Windows node.
> The only one who knows about the take-over is the Witness, so for the 
> backup application to know on which Windows node to execute the 
> backup, he should talk to the Witness.
> My SQL guy actually wants to know how he can assure that the backup 
> continues on the other node after a take-over.
> Thanks again in advance for you reply!!!
> Kindest regards,
> Eric van Loon
> KLM Royal Dutch Airlines
>
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain
confidential and privileged material intended for the addressee
only. If you are not the addressee, you are notified that no part
of the e-mail or any attachment may be disclosed, copied or
distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor
responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286 
**********************************************************************

<Prev in Thread] Current Thread [Next in Thread>