You say they are writing to (and you're trying to backup) a "floating drive"
and that you've defined "vir1" in your backups.
Your "vir1" must not be in the same Cluster Group as the resources you're
trying to back up.
I'm guessing you're trying to backup the Network Name resource called Cluster
Name, by default placed into a group called Cluster Group, and the Physical
Disk resource you're going after is not in that group (hence, can be owned by a
different node).
... and don't just move the Physical Disk resource to the Cluster Group or
you'll break their backups to the disk and maybe more. Create a new name or
use an existing name in the resource group that already holds the Physical Disk
resource and use that name for your backups.
P Go Green! Print this email only when necessary. Thank you for helping Time
Warner Cable be environmentally responsible.
-----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
smwoodcrafts
Sent: Friday, June 12, 2009 11:34 AM
To: VERITAS-BU AT MAILMAN.ENG.AUBURN DOT EDU
Subject: [Veritas-bu] Backing up cluster after failover
ewilts wrote:
> On Fri, Jun 12, 2009 at 9:48 AM, smwoodcrafts <netbackup-forum < at >
> backupcentral.com (netbackup-forum < at > backupcentral.com)> wrote:
>
> The client name set on the host is actually irrelevant - it's only used when
> you want to do a restore.
>
> On your Windows cluster, you want to make sure that you have 3 backup
> policies - 1a, 1b, and vir1. The policies for 1a & 1b would back up just the
> OS - for example, C: and System_State:. You could likely combine those 2
> into a single policy if the drive letters are the same between the systems.
> The vir1 policy would back up just the volumes that are floating between the
> hosts - for example, E: & F:. You have to make sure you don't try to back up
> the data volumes in the OS policy or you will get a status 71.
>
>
>
> > .../Ed
> >
> > Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewilts < at > ewilts.org
> > (ewilts < at > ewilts.org)
>
This is the problem, the business owners don't care about the OS or local
drives. They do an SQL back up and have it written on one of the floating
drives. The only thing we are backing up is the backup files so I only need the
one policy for the cluster (vir1). The problem is that the active node changed
and the host properties are still pointing to the old active node. Not the new
active node. In other words, I go to host properties for the cluster. The
Client tab says 1a (old active) not 1b (new active).
+----------------------------------------------------------------------
|This was sent by dseymour AT ap DOT org via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
This E-mail and any of its attachments may contain Time Warner
Cable proprietary information, which is privileged, confidential,
or subject to copyright belonging to Time Warner Cable. This E-mail
is intended solely for the use of the individual or entity to which
it is addressed. If you are not the intended recipient of this
E-mail, you are hereby notified that any dissemination,
distribution, copying, or action taken in relation to the contents
of and attachments to this E-mail is strictly prohibited and may be
unlawful. If you have received this E-mail in error, please notify
the sender immediately and permanently delete the original and any
copy of this E-mail and any printout.
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|