Enterprise Vault cannot register as an FPolicy external-engine following a Vserver Storage transfer to a DR Cluster Site.

book

Article ID: 100047006

calendar_today

Updated On:

Description

Error Message

Source: Enterprise Vault
Date: 1/29/2020 09:30:00 AM
Event ID: 45084
Task Category: NetApp C-Mode File Placeholder Server
Level: Error
Computer: EVSERVER.PRDSITE.DOMAIN.EXT
Description: The NetApp C-Mode placeholder server for vserver: VSERVER-PROD.DRSITE.DOMAIN.EXT failed to configure FPolicy

 

Cause

The described behaviour is by design.

 

Resolution

 

Enterprise Vault provides full Support to NetApp C-Mode Vservers, including support when a Vserver is switched between nodes in the Cluster, known as a failover.

This failover basically means that the Interface Port, which the Vserver is using, is switched to a Port on the other node.

The ability to support cases when the Vserver storage is switched to a Cluster on a different site, such as a DR Site, is not provided with Enterprise Vault normal functionality.

However, it is possible to allow the EV server to register against the originally configured policy, while the Vservers have been brought online at the DR Cluster Site, by performing manual changes to the relevant references in the NetAppClusterModeFileServerConfig table.  

It is also necessary to implement the means to resolve name to IP, whether by DNS or hosts file, so that the EV server can continue to process the Vserver targets under the same FQDN as already recorded as a target in the database.

These changes should only be performed by a NetApp Storage Administrator with sufficient understanding about the NetApp Cluster implementation for information accuracy and the assistance of a Database Administrator.

 

Important: Before any changes are made to the database records, ensure that a full backup is performed against the entire set of Enterprise Vault databases.

We strongly recommend that customers implementing a similar procedure should engage the Veritas Enterprise Technical Support Team for proper assistance.

 

 

 

Issue/Introduction

When implementing File System Archiving to process NetApp C-Mode Storage Virtual Machines (SVM), the target Vservers are assigned specific configuration settings within the Enterprise Vault Directory database. The table NetAppClusterModeFileServerConfig stores references that are unique and specific to each Vserver added as a target. The relevant columns are: VserverName - this is the name given to the CIFS server from which users access the storage content, via the CIFS shares. This name is usually associated with the Data LIF. ManagementLif – If a separate Management LIF is created for the Vserver, the corresponding LIF name will be recorded. The Management LIF is used for API level access. VserverUUID – The VserverUUID is a unique value assigned to the Vserver when created. Each Vserver will have a unique UUID. These values are validated every time the Enterprise Vault Admin service initialises the process responsible for registering the EV server against FPolicy. If the values do not correspond to the actual names and IDs for Vservers active in the Cluster, the registration against the policy will fail. Taking this into a context where the Storage Volumes allocated to Vservers have been ‘replicated’ to a DR Cluster Site, and the Vservers on the DR Site have been made active, the EV server will not be able to continue processing the Vservers due to the discrepancies between the entries in VserverName, ManagementLIF and VserverUUID and the corresponding values set at the Vserver hosted at the DR Site.