Centera Replication report

Hi

Unfortunately, as of now there is no specific way to automatically pull the weekly Centera Replication report, The Continuity of the Replication depends upon the volume of the active clip list which is sent.

Regards,

Phukon

You could always use the Centera CLI to script something to send status emails or alerts for parked entries etc.

Sagle

Ho w do i get the script configured .

Download the CLI.

run the script maunally at first to setup the key to not prompt and make sure it works. (ie enter perm to the security message)  I had to set the window size on the centera CLI larger to capture all the output on my scripts as well.

java -cp PATH/CenteraViewer.jar com.filepool.remote.cli.CLI -u user -p pass -ip CENTERA_NAME_OR_IP:3682 -script PATH/script.cli

Replace the PATH with the appropriate path to the java file and script file.  Replace the Centera IP or name.

Put commands in the script file like follows

show replication detail

exit

It has been a while since I set this up so I may have missed a step or two as this is all from memory.  I did not find a linux version of the download, but just copied the solaris jar file to a linux machine and it worked.  Once you get the basics working you can parse out data to format reports or setup alerts.

Sagle

Hi

We base our monitoring on looking into the system with Centera Viewer and the CLI. There the show replication detail command gives you all you need to know. I will install the latest release of Centera Console to have a look at what it tells about replication.

To your questions:

1. Once you have verified that all links are up and running you are all set. When an issue with replication arises the Centera will alert you. The alert messages for replication are:

Alernatively script a show replication detail using the various examples provided in the forum.

2. See above for the error messages.

3. If an ethernet port goes down of the system you will receive a notification. This does not tell you if anything in the rest of the replication chain like further switches or links go down in real time. Once the queue has built up an and notification levels are reached you will receive the alert from the system.

Best regards, Holger

Hi Kumar

You will receive an email notification with the symptom code. If EMC needs to so something depends on the symptom code. For the errors above these are not things you need customer service to fix them.

• 1.1.1.1.20.01: The target cluster does not have enough capacity to process the replication request. (Error)
  

Add more capacity in the target system

• 1.1.1.1.20.02: The replication parking on the cluster contains more than 10,000 entries on one or more nodes. (Error)
  

issue replication parking process. Check the type of parked entries. If need be open a SR on your own.

• 1.1.1.1.20.03: The target cluster has refused a replication request because the access profile used for replication does not have the correct capabilities. (Error)
  

Use set grants to grant the profile used for replication the required rights in all replicated pools (Most typically delete, exists and clipcopy)

• 1.1.1.1.20.04: The access profile used for replication could not be authenticated. (Error)
  

Use set cluster replication to choose a .pea file that can be authenticated. Not a combined profile (.pea).

• 1.1.1.1.20.05: The target cluster has refused a replication request because the pool for the C-Clip being replicated was not found on the target cluster. (Error)
  

Use export poolprofilesetup and import poolprofilesetup to create the required pool on the target system.

• 1.1.1.1.20.06: Replication has been paused by the user. (Warning)
  

use replication resume to get replication going again.

• 1.1.1.1.20.07: Replication has been cancelled by the user. (Warning)
  

use set cluster replication to setup replication again. Perform a partial restore for the timeframe between the cancellation and the time replication was again configured to ensure full data redundancy

• 1.1.1.1.20.08: The target cluster does not support the advanced compliancy feature(s) Event Based Retention (EBR) and/or Litigation Hold (LH). (Warning)
  

Buy the licenses for the target cluster and configure the cluster as the source cluster

As you can see these are all symptom codes that do not EMC attention but yours.

The daily receipt of the Health Report is the best way to ensure that the full chain of notification works. The HR receipt confirms that EMC is able to receive both HR and Alerts as well as notify field reports. Depending on the symptom code EMC will open a SR. Currently often also for Alerts where the description says EMC will not open one. And as the documentation says EMC does not do something check the symptom code and validate if you or EMC need to do something about it.

Holger

Hi Bravo,

I see you posted a question regarding a Centera Replication report and that your question in this post appears to have been answered. Was this a correct or helpful answer? If so could you please mark the question as Answered (helpful or correct)?

Thanks for your assistance and participation in the Support Forums.

Regards,

Ronan