Clariion discovery command fails with error
The symcfg discover -clariion command fails with the following error:
Invalid certificate encountered - End-of-chain encountered without finding a trusted certificate
The discovery command fails because there is no LUN coming from the Clariion array to the proxy computer. To solve this issue, consider the following scenario:
If you have two storage arrays (Clariion 1 and Clariion 2) and a proxy computer, where the proxy has access to a LUN residing on Clariion 2 and your source LUN comes from Clariion 1. Clariion 1 does not have any LUN on the proxy. For the discovery operation to be successful, you must add a LUN to Clariion 1 and mount it to the proxy computer to allow connectivity. It is recommended to perform this workaround instead of using the Clariion discovery command.
Failure to create VNX snapshots
Verify that the source LUN is the pool LUN. This limitation exists because VNX Snapshots require storage space from the pool.
Verify that setup steps required for VNX snapshots are completed successfully.
Note
SnapView Snapshots are compatible with pool LUNs. VNX Snapshots and SnapView Snapshots can coexist on the same pool LUN.
Failure to revert from VNX snapshots
The revert operation from a VNX Snapshot may fail if the primary LUN has any Snapview session. In order to continue the revert operation, all the Snapview sessions on the primary LUN must be stopped.
Snapshots are not being created
It is recommended that multiple IntelliSnap backups using the same host must be run one after the other. Multiple IntelliSnap backups running at the same time may cause the snapshot creation to fail due to the database lock.
Unable to perform cloning operation
For clone operations, ensure that Clone Private LUN (CPL) is created for each storage processor prior to performing the snapshot operations.