Veritas-bu

Re: [Veritas-bu] backing up MS cluster

2007-12-14 01:31:24
Subject: Re: [Veritas-bu] backing up MS cluster
From: "WEAVER, Simon (external)" <simon.weaver AT astrium.eads DOT net>
To: "'VERITAS-BU AT mailman.eng.auburn DOT edu'" <VERITAS-BU AT mailman.eng.auburn DOT edu>
Date: Fri, 14 Dec 2007 06:15:12 -0000
Your cluster is providing a service by using a VSN (Virtual Server Name).
This name is not tied to a physical node. Therefore, when doing the backups
for SQL use the Virtual Server name.

For the "physical" nodes (ie: the computers themselves), create a backup
policy for their physical drive letters. This may be the C: Drive, System
State for example.

All Local Drive is no good, especially for a cluster setup. Also avoid
backing up the quorom drive too.

For SQL, I would assume you are doing online SQL Backups? If not, them dump
the SQL Backups to disk, and ensure that the data is stored on a drive that
is accessible by the VSN. These would be known as SAN disks - they are
cluster resources again and can move between nodes, where the physical
"local drives" cannot :-)

I know Symantec offer NetBackup client in a cluster configuration, and you
could configure this as a resource in cluster administrator, but to be
honest, its not really essential. From the backups perspective, as long as
it can see the VSN and IP address of the device, Netbackup treats it like a
client and performs the backup.

Im sure there are some good technotes out there regarding cluster backups
(maybe the operations guide too).

Hope this has helped a little

S.


-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of X_S
Sent: Thursday, December 13, 2007 5:56 PM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] backing up MS cluster



We have 4 MS 2003 servers with MS multi-node cluster configurations for SQL
2005.  What is the best way to configure the policies?  We have tried using
both the All Local Drives directive and specifying each individual drive
letters (pain when resources fail over).  But what concerns us how NB reacts
when resources are moved or failed over.  we have had instances where
resources were moved but NB didn't pick the drive up on the new owner-node.

+----------------------------------------------------------------------
|This was sent by xspak1 AT yahoo DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

This email (including any attachments) may contain confidential and/or
privileged information or information otherwise protected from disclosure.
If you are not the intended recipient, please notify the sender
immediately, do not copy this message or any attachments and do not use it
for any purpose or disclose its content to any person, but delete this
message and any attachments from your system. Astrium disclaims any and all
liability if this email transmission was virus corrupted, altered or
falsified.
---------------------------------------------------------------------
Astrium Limited, Registered in England and Wales No. 2449259
REGISTERED OFFICE:-
Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Veritas-bu] backing up MS cluster, WEAVER, Simon (external) <=