EV not allowing retrieval of archived items after primary centera node is powered down

Hello,

I am in no way an EV with Centera expert, but this is what I would do:

Pool Address: EMC-ATMOS-101,10.4.1.91,10.4.1.92,10.4.1.93?\\ms-symev-102\ATMOS PEA FILE\Stoke-Atmos-EV-Email.PEA

In EV, can you verify the settings on the Vault Store Partition, the Connection tab, click Test Settings, and Test. When ok, click apply and save. That should have tested access to the nodes of Centera.

The authentication might be on the pea file, or perhaps on the replica centera?

Sorry for not being able to help out. Perhaps a support call helps?

Check the permissions on the DR Centera and also whether the PEA file is correct and merged, I dont 100% trust the connectivity tests from EV to Centera (in my experiance it seems to be slighlty better than a ping to the access nodes and nothing much more) so hopefully they'd have done a full test when they implemneted the DR centera and regular ones after (not just clicking on the test button) .....  The Access rights on the Pool in the DR centera should be the same as those on the production centera Pool ideally (they may have just added enough rights to allow replication to work.)

To check Centera permissions they would need to have access to the CLI for the nodes, there's a whole list of 'SHOW' commands that will show the properties of the POOL's and permissions setup, been a little while so not got them to hand.

I would suggest bypassing EV operations and looking at communicating with the APIs directly.  This can be done using the jcasscript from EMC.  See the following article for details:

http://www.symantec.com/docs/TECH65517
How to extract BLOB data from an EMC Centera Clip when requested by Enterprise Vault Support

Using this, you can test a poolopen request independantly as well as a clipopen request.  This will also test that the PEA file works with the replica.

I hope this helps.

Probably you might have to modify the dbo.PartitionEntry in SQL server to force it to only use the DR centera IP address probably this might help to access the DR centera box .

Hello all.. Customer has sent me the log files from testing JCenteraVerify on both their Centera Sites from their Enterprise Vault server. In one they use the primary site as access points, in the other they use the secondary site as access points.

Both log files show that the .pea file authenticates and writes to both sites and recognises each other as a replica.

There is additional output from the "replica test" where it writes a clip to one side and verifies that appears on the other.

Secondary Log

*******************************************************************************************************

Replica address: 10.4.24.121?C:\SUPPORT\ATMOS PEA FILE\Stoke-Atmos-EV-Email.PEA
, 10.4.24.122?C:\SUPPORT\ATMOS PEA FILE\Stoke-Atmos-EV-Email.PEA
, 10.4.24.123?C:\SUPPORT\ATMOS PEA FILE\Stoke-Atmos-EV-Email.PEA
, 10.4.24.124?C:\SUPPORT\ATMOS PEA FILE\Stoke-Atmos-EV-Email.PEA

Connecting to 10.4.1.93?C:\SUPPORT\ATMOS PEA FILE\Stoke-Atmos-EV-Email.PEA     ... Done
Connecting to 10.4.24.121?C:\SUPPORT\ATMOS PEA FILE\Stoke-Atmos-EV-Email.PEA     ... Done

Writing a  clip to 10.4.1.93?C:\SUPPORT\ATMOS PEA FILE\Stoke-Atmos-EV-Email.PEA     ... Done
The CA of the Clip is : 8OL8VTVF2RBRDe87LDB7H6RH880HpAQBWgTsqd0ymzIsFEl3kkAiC

Checking for the clip on replica (0 Sec): Clip Found

Deleting the clip from the Src cluster :     ... Done

*******************************************************************************************************

Primary Log

*******************************************************************************************************

Replica address: 10.4.1.90?C:\SUPPORT\ATMOS PEA FILE\Stoke-Atmos-EV-Email.PEA
, 10.4.1.91?C:\SUPPORT\ATMOS PEA FILE\Stoke-Atmos-EV-Email.PEA
, 10.4.1.92?C:\SUPPORT\ATMOS PEA FILE\Stoke-Atmos-EV-Email.PEA
, 10.4.1.93?C:\SUPPORT\ATMOS PEA FILE\Stoke-Atmos-EV-Email.PEA

Connecting to 10.4.24.124?C:\SUPPORT\ATMOS PEA FILE\Stoke-Atmos-EV-Email.PEA     ... Done
Connecting to 10.4.1.90?C:\SUPPORT\ATMOS PEA FILE\Stoke-Atmos-EV-Email.PEA     ... Done

Writing a  clip to 10.4.24.124?C:\SUPPORT\ATMOS PEA FILE\Stoke-Atmos-EV-Email.PEA     ... Done
The CA of the Clip is : EAP7CPUEEJGP1eFOOEIJKBGH1O6HogQYeQTsty0kQUmIFEl3sSDnE

Checking for the clip on replica (0 Sec): Clip Found

Deleting the clip from the Src cluster :     ... Done

*******************************************************************************************************

Thank you Chris !

This is the xml report customer has sent by after he bypassed EV server and tested APIs directly using jcassript:

That CDF (Clip Descriptor File) looks good.  If you got this CDF through jcas, using the Replica IP and PEA file, it looks like a basic call works. I'd get an SDK log and replicate to see what is happening before EMC returns the -10153 error.

http://www.symantec.com/docs/TECH43501
How to enable EMC Centera SDK Logging for Enterprise Vault (EV)