ADSM-L

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

2007-11-15 05:34:10
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: Thu, 15 Nov 2007 11:33:01 +0100
Hoi Del!
I understand that using the same TSM node for backing up the Principal
and the new Principal after a take-over is a solution.
So: if ServerA is the principal, one has to execute the backup script on
this server. After a take-over, ServerB becomes the principal and one
has to execute the backup script (using the same TSM nodename) on
ServerB. If I understand you correctly, one has to use external tools to
determine which server (ServerA of ServerB) is the current Principal?
Thanks again!!!
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: woensdag 14 november 2007 13:36
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: DP for SQL Server mirroring

As Steve suggested, test out your scenario using a common nodename.
However, you will need to be careful because both servers will have
common databases (like master and msdb)... and you do not want those
backups for different servers to get mixed in with each other.
You could have a separate line in the backup script on both machines
that backs up the "mirrored" database on both servers (and point to a
similar DSM.OPT file) knowing that the backup on the Mirror machine will
fail.
You can also look into "Proxy Node". It allows one node to store data on
behalf of another node if the correct permissions are granted from the
TSM Server side.
There are probably a number of other ways to get your desired result.

Thanks,

Del

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

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 11/14/2007
04:49:03 AM:

> 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
**********************************************************************
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>