Support for volumes managed by Symantec Storage Foundation (Verita

[Brent]

When using Symantec storage foundation to manage dynamic disk, DPM 2007 is
unable to see these volumes. This is particularly a problem when using
Symantec storage foundation with Microsoft Clustering. DPM 2007 is unable to
enumerate the file shares or volumes managed by Symantec Storage Foundation.

Has this issue been identified by anyone else, and if so, is there a
workaround.

Thanks,
Brent

[Daveg]

I believe you need to present the LUNs as RAW. DPM will format them
with NTFS and make them dynamic disks. You can then add them to
storage pool.

daveg

[Brent]

I was referring to the client side of DPM when protecting a MSCS cluster
server that is using Symantec Storage foundation as the disk management
system. The storage foundation product provides a way to use dynamic disks
with clustering. When the cluster server is using native disks, the DPM
server understands the volumes, but when the cluster server uses Storage
Foundation managed disks, the DPM server throws an error when attemting to
enumerate the share and volume information of the cluster.

Post by Daveg
I believe you need to present the LUNs as RAW. DPM will format them
with NTFS and make them dynamic disks. You can then add them to
storage pool.
daveg

[Daveg]

Understood. Can you share the exact error? I am not sure why dynamic
disks would be a factor on the client. Perhaps there is another
variable we are missing?

daveg

[Brent]

Here is the error I recieve in the DPM console when attempting to enumerate
the clustered resources.

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

Post by Daveg
Understood. Can you share the exact error? I am not sure why dynamic
disks would be a factor on the client. Perhaps there is another
variable we are missing?
daveg

[Brent]

It appears to be an issue with the enumerating the Resource type:
Volume Manager Disk Group
VXRES.DLL

If I add the disk to clustering as a physical disk type instead of a Volume
manager disk group type, the resource is found.

Post by Daveg
Understood. Can you share the exact error? I am not sure why dynamic
disks would be a factor on the client. Perhaps there is another
variable we are missing?
daveg

[Brent]

Any thoughts on this issue?

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

Post by Daveg
Understood. Can you share the exact error? I am not sure why dynamic
disks would be a factor on the client. Perhaps there is another
variable we are missing?
daveg

[Jordibe]

Hi Brent,
we have the same problem with cluster resource on Veritas Volum Manager and
Symantec Storage Foundation, can you solve this problem ?
Any have resolved this limitation with Physical Dics in Microsoft Cluster
configuration ?.

Best regards.

Post by Brent
Any thoughts on this issue?
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

Post by Daveg
Understood. Can you share the exact error? I am not sure why dynamic
disks would be a factor on the client. Perhaps there is another
variable we are missing?
daveg

[Asim Mitra [MS]]

Hi folks,

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.

Post by Jordibe
Hi Brent,
we have the same problem with cluster resource on Veritas Volum Manager and
Symantec Storage Foundation, can you solve this problem ?
Any have resolved this limitation with Physical Dics in Microsoft Cluster
configuration ?.
Best regards.

Post by Brent
Any thoughts on this issue?
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

Post by Daveg
Understood. Can you share the exact error? I am not sure why dynamic
disks would be a factor on the client. Perhaps there is another
variable we are missing?
daveg

[g***@gmail.com]

As MS recommend Storage Foundation for MSCS clusters, see http://support.microsoft.com/?kbid=816307 , it seems a little incredible that they don't then support those configurations with DPM. Any updates re this?

Post by Asim Mitra [MS]
Hi folks,
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.

Post by Jordibe
Hi Brent,
we have the same problem with cluster resource on Veritas Volum Manager and
Symantec Storage Foundation, can you solve this problem ?
Any have resolved this limitation with Physical Dics in Microsoft Cluster
configuration ?.
Best regards.

Post by Brent
Any thoughts on this issue?
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

Post by Daveg
Understood. Can you share the exact error? I am not sure why dynamic
disks would be a factor on the client. Perhaps there is another
variable we are missing?
daveg