3.4.0 Matrix Server Release Notes

PolyServe Matrix Server Release Notes 30

13557 Avoid forcing Virtual CIFS Servers to new primaries

MxFS for CIFS supports subdirectory Virtual File Shares (VFS).

Starting a subdirectory VFS may trigger the creation of

thousands of shares. This can take some time, even on fast

nodes. It is not uncommon for this operation to take several

minutes in large configurations. During this time, the Virtual

CIFS Server (VCS) is not completely up, and some of the shares

are unavailable for client connections. Virtual File Shares on

Virtual CIFS Server backup nodes create these shares in advance

to avoid unavailability on failover.

To avoid temporary unavailability of subdirectory shares, when

changing the Virtual CIFS Serverʹs configuration be careful not

to force the VCS to a new primary. That is, a node newly

designated as the VCS primary, but which before the

configuration change did not have the VCS present.

Instead, when selecting new primaries, select from the existing

backup nodes (which already have the Virtual File Share up).

When adding new nodes to the Virtual CIFS Server, make them

backups (this is the default). Avoid using

AUTOFAILBACK on

VCSs with more than one Virtual File Share (

NOAUTOFAILBACK

is the default for VCS creation).

For the maximum flexibility and fine-grained failure handling,

have only one Virtual File Share per Virtual CIFS Server if

possible. This will not always be possible, as in some

consolidation scenarios where legacy server/share names must

be preserved.

Bug

Description