I haven't seen exactly that ("Error attempting to find volumes to snap"), but
I've just slogged through a variety of 130 errors to get to a working
configuration.
Are your replicas healthy in the Exchange console?
Did you set the HKLM\System\CCS\Services\MSExchangeIS\ParametersSystem\Enable
Remote Streaming Backup registry key, as explained at
http://msdn2.microsoft.com/en-us/library/aa580485(EXCHG.80).aspx?
Did you restart the clustered mailbox server after setting the registry key (as
is not mentioned at that link but is mentioned in the Exchange help topic)? You
do that in the Exchange Management Shell like this:
Stop-ClusteredMailboxServer <CMSName> -StopReason "Enable Remote Streaming
Backup" -Confirm:$False
Start-ClusteredMailboxServer <CMSName>
The client-side log you want to be looking at is bpfis, and you'll want to look
at it both on the active and on the passive node. While testing, I recommend
that you force backups to the passive node (they'll fail with a 130 if it's
unavailable), but you probably want to permit falling back to the active node
once you're running live.
--
gabriel rosenkoetter
Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup & Recovery
gabriel.rosenkoetter AT radian DOT biz, 215 231 1556
-----Original Message-----
From: Michitsch, John [mailto:JMICHITS AT gannett DOT com]
Sent: Friday, September 26, 2008 10:43 AM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Exchange 2007 with CCR - Passive Node Backup
Has anyone seen these errors when trying an Exchange 2007 with CCR - Passive
Node Backup? The client is the Exchange cluster virtual name.
9/26/2008 10:40:11 AM - begin Create Snapshot
9/26/2008 10:40:29 AM - Critical bpbrm(pid=404) from client ent-mocexcmb10: FTL
- snapshot preparation failed - Error attempting to find volumes to snap.,
status 130
9/26/2008 10:40:29 AM - Critical bpbrm(pid=404) from client ent-mocexcmb10: FTL
- snapshot preparation failed, status 130
9/26/2008 10:40:37 AM - end Create Snapshot; elapsed time: 00:00:26
9/26/2008 10:40:39 AM - end writing
-----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 oersted
Sent: 24 September, 2008 5:42 PM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Exchange 2007 with CCR - Passive Node Backup
this is spot on
Rosenkoetter, Gabriel wrote:
> You shouldn't be specifying either the active or passive node name as a
> client, you should be specifying the cluster's virtual name as a client.
>
> Also, note that you must run the NetBackup Client Service as an AD-level (not
> local) account that has local admin access on each server and admin access to
> the Exchange cluster for LCR/CCR snapshot backups. Running the client as
> LocalSystem will not work. (The documentation's a bit hazy on this point.
> It's clear that that's necessary for individual mailbox backups, it's not so
> clear that it's required for the cluster backups, but it makes sense when you
> think about it: the Exchange cluster isn't logically attached to either node,
> so neither node's LocalSystem has sufficient permissions.)
>
> --
> gabriel rosenkoetter
> Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup & Recovery
> gabriel.rosenkoetter < at > radian.biz, 215 231 1556
>
> From: Scheef Jr, Ed E. [mailto:CXScheef < at > tecoenergy.com]
> Sent: Tuesday, September 23, 2008 3:36 PM
> To: veritas-bu < at > mailman.eng.auburn.edu
> Subject: [Veritas-bu] Exchange 2007 with CCR - Passive Node Backup
>
>
>
>
> Folks,
>
> We're running Netbackup 6.5.2.
>
> We're just now setting up a Netbackup Policy for Exchange 2007 running in a
> CCR cluster.
> The backup has been defined to "backup the passive node first, but if not
> available, backup
> the active node".
>
> The question I have is client definition in the Snapshot policy (within
> Exchange Policy) required
> to backup the Exchange database:
>
> When we put both physical CCR cluster node names in the policy's client list,
> it starts backups
> for both nodes, and looks like it does "snapshots" for both nodes, when only
> the "passive node"
> should be snapshotting, and getting backed up. Why is that happening ??
> Anybody have a
> "passive node" Exchange backup set up and working ???
>
> An obvious solution would be to take the "active" node server out of the
> policy's client list, but
> then if a failover occurred , and the "passive" node switched to what is now
> the "active" node,
> would the "passive" node backup still work without that physical server in
> the policy's client list ??
>
> The Netbackup documentation update for 6.5.2 is not too clear on this !!
>
> Thanks Much,
> Ed Scheef
> Tampa Electric Company
+----------------------------------------------------------------------
|This was sent by solaris AT cablespeed 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
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
