Backups fail and the following message appears in the bpfis log:

emcclariionfi: Unable to find SP that owns LUN 1. Verify that credentials have been supplied for the SP that owns LUN 1.

In this example, the message appears because LUN 1 is owned by a CLARiiON storage processor for which credentials have not been supplied. In a single path configuration, all LUNs must be owned by one storage processor and credentials must be supplied for at least that storage processor. It is okay to supply credentials for both storage processors because NetBackup automatically determines which set of credentials should be used. In a multipath configuration, credentials for both storage processors should be supplied because multipathing software may automatically change which storage processor owns the LUN.

Backups fail and the following message appears in the bpfis log:

emcclariionfi: WARNING: Unable to import any login credentials for any appliances.

Credentials must be added for the CLARiiON array by means of the NetBackup Administration Console.

Backups fail and one or both of the following messages appear in the bpfis log:

emcclariionfi: The host hostname was not found in any storage groups. To import a snapshot to host hostname, hostname must be in a Clariion storage group.

emcclariionfi: LUN masking failed. Could not find a storage group containing the hostname [hostname].

NetBackup searches the CLARiiON's storage groups for the import host. (For a local backup, the import host is the host where the source device is mounted. For an off-host backup, the import host is the alternate client.) When the host is found, the snapshot device is assigned to that storage group, thus making it visible to the import host where the backup can proceed. If the import host is not in any storage groups, the backup fails.

Backups fail and the following message appears in the bpfis log:

emcclariionfi: No more available HLU numbers in storage group. LUN LUN number cannot be LUN masked at this time

The device cannot be imported to the host, because the maximum number of devices from the array is already imported to this host. Expire any unneeded backup images.

EMC_CLARiiON_Snapview_Clone backups fail and the following message appears in the bpfis log:

emcclariionfi: Could not find LUN LUN number in clonegroup clonegroup name

The clone target device does not exist in the clonegroup belonging to the source device. Either correct the target list in the policy or use Navisphere to add the target device to the source device's clone group.

Both types of CLARiiON backups fail with the following in the bpfis log:

emcclariionfi: CLIDATA: Error: snapview command failed emcclariionfi: CLIDATA: This version of Core Software does not support Snapview

These messages appear when the Snapview software is not installed on the CLARiiON array. Snapview must be installed on the array before CLARiiON clone or snapshot backups can succeed. Please see the array documentation or contact EMC for more information.

Backups fail and the following message appears in the bpfis log:

execNAVISECCLI: CLI Command [CLI command] failed with error [error number]

NetBackup uses naviseccli to send commands to the CLARiiON array. If naviseccli encounters an error, it is captured and placed in the bpfis log. The lines immediately following the above line should contain the output from naviseccli that indicates why the command failed.

After a point-in-time rollback from a Windows VSS backup that was made with the EMC CLARiiON Snapview Clone snapshot provider, all clones are fractured (split from the primary)

As a best practice, avoid performing a point-in-time rollback from a Windows VSS backup that was made with the EMC CLARiiON Snapview Clone snapshot provider, if one of the clones is configured for the policy has not been used for an Instant Recovery backup. After a rollback, all the clones are placed in a "fractured" state. (Fractured clones are no longer synchronized with the primary.) As a result, any clone that had not already been used for a backup is no longer available for a future Instant Recovery backup.

If you must perform a point-in-time rollback before all clones have been used for backups, note which clones are still synchronized before you do the rollback. After the rollback, you can manually resynchronize the clones.

Policy validation fails for Standard policy with the following message:

The error message is Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries.

Policy validation for a Standard policy created with the EMC_CLARiiON_Snapview_Snapshot fails with error 4201.

The policy validation fails when the CLI is installed at a location where NetBackup fails to identify it. The CLI must be installed in the /sbin/naviseccli. If the CLI is installed at another location, NetBackup fails to identify that location and policy validation fails.

To fix the policy validation, add the following entry into the emcclariionfi.conf file:

[CLI_TOOL_INFO]

"FILEPATH_NAVISEC_EXE"="<NAVI CLI path>"

"FILENAME"="<NAVI CLI tool file name>"

For example, for the HP platform the path would be:

/usr/openv/lib/vxfi/configfiles/emcclariionfi.conf

The entry would be:

[CLI_TOOL_INFO]

"FILEPATH_NAVISEC_EXE"="/opt/Navisphere/bin"

"FILENAME_NAVISEC_EXE"="naviseccli"