Veritas-bu

[Veritas-bu] Database Cluster Policy Strategy

2007-03-22 08:48:36
Subject: [Veritas-bu] Database Cluster Policy Strategy
From: pkeating at bank-banque-canada.ca (Paul Keating)
Date: Thu, 22 Mar 2007 08:48:36 -0400
Put the .bch on both nodes on a drive letter that is common, ie. C:\

In your policy refence the C:\SWL\BACKUP\SCRIPT.bch

List the name of the cluster resource, not the physical node, in the
Policy.

ie. your cluster nodes are called node1 and node2, and the clustered SQL
resource's node name that can fail over and back is called SQL-cluster,
then you list SQL-cluster in the policy.

Paul

-- 


> -----Original Message-----
> From: veritas-bu-bounces at mailman.eng.auburn.edu 
> [mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf 
> Of Michael Klein
> Sent: March 21, 2007 10:10 PM
> To: veritas-bu at mailman.eng.auburn.edu
> Subject: [Veritas-bu] Database Cluster Policy Strategy
> 
> 
> I'm curious how people manage database backups in a an active-active
> or N+1 cluster in NetBackup.
> 
> I have four 2-node active-active SQL Server clusters (8 unique SQL
> instances) that share the same backup parameters and same backup
> window. The layout is as follows:
> 
> Cluster1
>   Node1 hosts SQLVS1\Instance1
>   Node2 hosts SQLVS2\Instance2
> 
> Cluster 2
>   Node3 hosts SQLVS3\Instance3
>   Node4 hosts SQLVS4\Instance4
> 
> .... you get the picture.
> 
> I'd like to configure a single policy to backup all 8 SQL instances. I
> created a .bch file for each instance with a generic name
> (SQL_Full.bch) and copied it to the dbext\mssql directory of the node
> that is primary for each instance. My policy includes all 8 virtual
> SQL server names and calls SQL_Full.bch. When all nodes of the cluster
> host their primary instance (i.e., all nodes are online) everything
> works perfectly. However, when one node of a cluster fails or is taken
> down for maintenance, the other node hosts both SQL instances. In that
> case, the primary instance is backed up twice and the instance that
> failed over is not because the batch file on the single working node
> (that now hosts both SQL virtual server names) only contains the
> details about it's primary instance.
> 
> I've thought about putting the .bch file on each SQL instance's data
> LUN and then referencing it in the policy but alas, there is no
> standard drive letter among the 4 clusters (one uses X: & Y:, the
> other V: & W:, the third T: & U:, etc.).
> 
> How do others manage database backup policies on multi-node clusters?
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
====================================================================================

La version fran?aise suit le texte anglais.

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

This email may contain privileged and/or confidential information, and the Bank 
of
Canada does not waive any related rights. Any distribution, use, or copying of 
this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately 
from
your system and notify the sender promptly by email that you have done so. 

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

Le pr?sent courriel peut contenir de l'information privil?gi?e ou 
confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute 
diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires d?sign?s est interdite. Si vous 
recevez
ce courriel par erreur, veuillez le supprimer imm?diatement et envoyer sans 
d?lai ?
l'exp?diteur un message ?lectronique pour l'aviser que vous avez ?limin? de 
votre
ordinateur toute copie du courriel re?u.


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