Skip to main content
Declined

Evolution du plugin Datadomain mode Replication

Related products:Infra Monitoring - Connectors
  • Mar 23, 2023 6:19 PM UTC
  • 7 replies
  • 326 views

Forum|alt.badge.img+2

Bonjour,

Nous avons des baies Datadomain qui répliquent en environnement CyberRecovery.

Il y a 2 réplications en production de la baie principale vers la secours, et une réplication "recovery" de la baie secours vers la production.

Sachant que la réplication "recovery" n'est lancée qu'en cas de secours, elle n'est jamais à jour.

Nous souhaiterions une évolution du plugin afin de pouvoir filtrer les instances, comme cela est possible sur le plugin "DataDomain/mode/Filesystem".

Sachant que nous utilisons les paramètres supplémentaires suivants, est-il possible de prévoir une évolution du plugin en ce sens ?

 --warning-offset='108000' --critical-offset='172800'

Dans l'attente de votre retour,

Cordialement,

Florian ROUXEL

7 replies

fgbetokpanou
Centreonian
Forum|alt.badge.img+12
  • Centreonian
  • Mar 27, 2023 9:42 AM UTC

Hey @GHT Armor, In order to help as many users as possible, could you please post your question in English? That way, anyone else who might be experiencing a similar issue can also benefit from the solutions that will be suggested. And this can even help you reach more people in the community. Thanks for your understanding. Cheers 😉


Forum|alt.badge.img+2
  • Author
  • Steward *
  • Mar 27, 2023 3:04 PM UTC

Hello @Fabrix, I will try to to my best.

We’ve got two Data Domain Appliance which are in sync for a Cyber Recovery environnement.

 * There are 2 replications contexts from the production (Veeam) Data Domain to the Cyber Recovery Data Domain. These replication are running every day on a specific schedule.

  * There is 1 replication context pre-created from the Cyber Recovery Data Domain to the production one. This replication is only there in order to make the recover process easier (in case the production data Domain is still available, and don’t need to be reconfigure from scratch). This replication context is only run during recover tests, indeed, the associated out-of-sync time is huge.

 

Regarding the 3 replications contexts, we cannot use the “Offset” option of the Centreon plugin to monitoring the production Data Domain replication, because it always report the “recovery replication context” as critical, due to his out-of-sync time.

 

The object of this “Evolution request” would be to have the avaibility to filter Replication context in the “replication mode” of the Centreon EMC DataDomain Plugin (run with “offset threehold”). We saw that an “instance” filter is already availlable in the “FileSystem” mode of the same plugin, We hope it may be possible to apply the same filtering option to the “replication mode”.

 

Since our Cyber Recovery has been integrated by Dell/EMC, we think that we may not be alone with an “out-of-sync” Recovery Replication context, and this evolution may be reused by several users.

Hope you will undestand what we are expecting.

 

Here is the result we have without filtering option :

/usr/lib/centreon/plugins/centreon_emc_datadomain.pl --plugin=storage::emc::DataDomain::plugin --mode=replication --hostname=DD-PROD-IP --snmp-version='2c' --snmp-community='my-community'  --warning-status='%{state} =~ /disabledNeedsResync|uninitialized/i' --critical-status='%{state} =~ /initializing|recovering/i'  --warning-offset='108000' --critical-offset='172800' --verbose

[centreon@SRV-CENTREON ~]$ /usr/lib/centreon/plugins/centreon_emc_datadomain.pl --plugin=storage::emc::DataDomain::plugin --mode=replication --hostname=10.230.12.231 --snmp-version='2c' --snmp-community='ght-ro'  --warning-status='%{state} =~ /disabledNeedsResync|uninitialized/i' --critical-status='%{state} =~ /initializing|recovering/i'  --warning-offset='108000' --critical-offset='172800' --verbose
CRITICAL: Replication 'mtree://DD-CYB/data/col1/veeam_restore/mtree://DD-PROD/data/col1/veeam_restore_from_crs' last time peer sync : 22384919 seconds ago | 'offset_mtree://DD-PROD/data/col1/DD-PROD_SU01/mtree://DD-CYB/data/col1/DD-PROD_SU01_REPL'=24633;0:108000;0:172800;; 'offset_mtree://DD-CYB/data/col1/veeam_restore/mtree://DD-PROD/data/col1/veeam_restore_from_crs'=22384919;0:108000;0:172800;; 'offset_mtree://DD-PROD/data/col1/DD-PROD_SU02/mtree://DD-CYB/data/col1/DD-PROD_SU02_REPL'=19804;0:108000;0:172800;;
Replication 'mtree://DD-PROD/data/col1/DD-PROD_SU01/mtree://DD-CYB/data/col1/DD-PROD_SU01_REPL' status is 'normal', last time peer sync : 24633 seconds ago
Replication 'mtree://DD-CYB/data/col1/veeam_restore/mtree://DD-PROD/data/col1/veeam_restore_from_crs' status is 'normal', last time peer sync : 22384919 seconds ago
Replication 'mtree://DD-PROD/data/col1/DD-PROD_SU02/mtree://DD-CYB/data/col1/DD-PROD_SU02_REPL' status is 'normal', last time peer sync : 19804 seconds ago
[centreon@SRV-CENTREON ~]$

 

Regards,

GHT Armor


rchauvel
Centreonian
Forum|alt.badge.img+18
  • Centreonian
  • Nov 12, 2024 11:23 AM UTC

Since this is an enhancement request, i have converted it to idea. It is now open to votes.


rchauvel
Centreonian
Forum|alt.badge.img+18
  • Centreonian
  • Nov 15, 2024 1:13 PM UTC
New→Needs Votes

Forum|alt.badge.img+5
  • Centreonian
  • Apr 18, 2025 12:38 PM UTC

Hello :)

We gave your idea a chance to be voted on by the community. However, some time has gone by since this idea was put to the vote without it garnering many votes. We're convinced that your need is legitimate and well thought-out, but unfortunately we receive a huge number of idea proposals and we have to sort and prioritise those that best reflect the needs indicated by the community (via the votes). That's why we need to decline this idea as a community idea for better visibility. This doesn't mean that your need can't be solved, you can try to make do with the collections (see the dedicated tutorials) or request a quote from Centreon support if you want to have this development carried out.

Kind regards.


Forum|alt.badge.img+5
  • Centreonian
  • Apr 18, 2025 12:38 PM UTC
Needs Votes→Declined

Forum|alt.badge.img+2
  • Author
  • Steward *
  • Apr 28, 2026 6:27 AM UTC

Hello,

Just a few word to report that the plugin has upgraded 2 years ago 

EMC Data Domain SNMP | Centreon Documentation

 

it is now possible to filter replication instance by source or destination, with a warning or critical threshold in day.

Here is en exemple of check which is working in our environnement

centreon@SRVCENTREON:~$ /usr/lib/centreon/plugins/centreon_emc_datadomain.pl --plugin=storage::emc::datadomain::snmp::plugin --mode=replications --hostname=10.123.12.23 --snmp-version='2c' --snmp-community='ght-ro'  --custom-perfdata-instances='%(type) %(source) %(destination)' --warning-status='%{state} =~ /disabledNeedsResync|uninitialized/i' --critical-status='%{state} =~ /initializing|recovering/i' --filter-repl-destination ASPDD201.intdom.org --warning-last-insync-time='1' --critical-last-insync-time='2' --verbose 
 

Regards,