Has this issue been identified by anyone else, and if so, is there a
workaround.
Thanks,
Brent
daveg
daveg
If I add the disk to clustering as a physical disk type instead of a Volume
manager disk group type, the resource is found.
DPM was unable to protect the members in the Resource group
\\?\Volume{e63fb408-0dc9-402e-b64e-935d05f17fac}\. This Resource group
contains some resources that have dependancies which not present as part of
this group
1) Check your cluster configuration to ensure that shares and disks on which
these shares reside, are part of the same resource group
2) Check your cluster configuration to ensure that the application and the
disks it requires are part of the same resource group
ID: 199
DPM appears to be looking at the veritas disk as a local disk instead of
clustered disk.
When creating a new protection group, the clustered disk resources that were
defined as the "physical disk" type are not available under the individual
cluster nodes as available resources as expected since it is a shared disk
and not owned by one node. The same is not true however with the veritas
"Volume Manager Disk Group" type. These resources show up from the DPM point
of view as local resource and not clustered resource.
How does DPM determine if a physical disk is clustered or not? It seems
that either Veritas needs to present dynamic disks in a way that DPM can
understand those resources just like a physical disk, or the DPM agent needs
to understand other disk resource types as a clustered disk type.
Thanks,
Brent
Best regards.
Thanks for the feedback. This is not a configuration supported by DPM 2007.
We have received similar feedback from some customers like you. We are
evaluating this scenario for a future DPM relea
--
Thanks,
Asim Mitra [MSFT].
--
The posting is provided " AS IS" with no warranties and confers no rights.
"Jordibe" <Jor...@discussions.microsoft.com> wrote in message
news:B7C17AAA-949C-4D17...@microsoft.com...