MountV agent changes ( folder mounts on local system disks)

[Zahid_Haseeb]

What is the idea of Symantec behind introducing the below new feature with the MountV agent ?

Extract from sfha 5.1 SP2 release update, Page # 15

MountV agent changes

The VCS MountV agent supports folder mounts on local system disks. You can

mount shared disks on local system drives using folder mounts. The VCS MountV

agent is modified such that during failover, the agent creates the folder mount

directories, if they do not exist on the target node.

For example, a shared disk is mounted as Mydata on a system drive (C:\). The path

of the mount is now C:\Mydata. When the MountV agent is failed over to another

node, it creates the folder Mydata, if it does not exist on that node, and then

mounts it on C:\ on that node.

[Wally_Heim · Accepted solution]

Hi Zahid,

In the past versions of VCS, VCS needed to control the drive letter that the mount point mounts to.  Due to Windows limiting the number of driver letters available there was a limit on the number of active/active service groups that could be configured using mount points.

With our 5.1 SP2 release, the Exchange 2010 recommended configuration is 1 Exchange information store per service group.  With this the drive letter under VCS control would be the limiting factor on the number of information stores that we could support.  Removing the need to control the drive letter when using mount points allows us to support the maximum number of Exchange information stores mounted to mount points with our recommendation configuration.

Keep in mind that this new feature of the MountV agent is not limited to use with Exchange only.  It can be used with any configuration that we support.

Thanks,

Wally