Skip to content
DataMiner DoJo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Empower Replay: Limited Edition
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • YouTube Videos
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Agility
      • Book your Agile Fundamentals training
      • Book you Kanban workshop
      • Learn more about Agile
        • Agile Webspace
        • Everything Agile
          • The Agile Manifesto
          • Best Practices
          • Retro Recipes
        • Methodologies
          • The Scrum Framework
          • Kanban
          • Extreme Programming
        • Roles
          • The Product Owner
          • The Agile Coach
          • The Quality & UX Coach (QX)
    • >> Go to DataMiner Docs
  • DevOps
    • About the DevOps Program
    • Sign up for the DevOps Pogram
    • DataMiner DevOps Support
    • Feature Suggestions
  • Swag Shop
  • Downloads
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Solutions
    • Deal Registration
  • Contact
    • Sales, Training & Certification
    • DataMiner Support
    • Global Feedback Survey
  • >> Go to dataminer.services

Prevent synchronization

Solved678 views19th September 2024synchronization
2
Arunkrishna Shreeder [SLC] [DevOps Enabler]4.13K 23rd July 2024 0 Comments

Hello,

I am looking into preventing DataMiner from synchronizing the ‘AppearTV General Platform’ version 4.4.1.33 connector.

What is the procedure to implement this ? Should I consider altering the syncinfo files or is there any other way ? Thank you.

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 19th September 2024

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
4
João Severino [SLC] [DevOps Catalyst]13.43K Posted 23rd July 2024 4 Comments

Hi,

I am not sure if such a thing is possible to achieve as connectors should always be synchronized across the cluster to have consistent behavior if you migrate an element from one agent to another or even if you create multiple elements in different agents.

Additionally, the error message that is displayed in your alarm console would indicate to me that the specific version of the connector is not compatible with your current DataMiner version and another range should be selected or DataMiner should be upgraded to a compatible version.

Would you be able to clarify the use case for not wanting to synchronize? Is it because of the error in your screenshot or is there any other reason?

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 19th September 2024
Arunkrishna Shreeder [SLC] [DevOps Enabler] commented 23rd July 2024

Hi Joao, we want to get rid of the alarm; so we are looking for options to not synchronize this protocol I believe.
In the syncinfo file {DO_NOT_REMOVE_C0E05277-A7C5-4969-904D-E2E52076400A}.xml, does changing type=remove of any use ?

João Severino [SLC] [DevOps Catalyst] commented 23rd July 2024

I think to get rid of the alarm you should not try to force a file from being synchronized and instead the best option would be to address the root cause of the problem.
All your agents should be running the same DataMiner version and in that case, the connector should not have been able to be uploaded in the first place, and it should be removed and replaced with an appropriate version.
If you have the cluster running different DataMiner versions, this should be addressed as it is not advised and can cause other issues.

Arunkrishna Shreeder [SLC] [DevOps Enabler] commented 23rd July 2024

The problem is, there is an alarm storm due to these notices, which is why we want to get rid of it. Sorry, just got this info.
Do you have any other ideas on how we can address this ?
The DMA version is old, but there are plans to upgrade in the near future.
The connector is available on file in the protocols folder but not in Cube.

João Severino [SLC] [DevOps Catalyst] commented 23rd July 2024

If the protocol is not visible in Cube then it is very likely that it is also not being loaded to do anything with it (i.e. elements are not using it) but I would still double-check this as there could be elements but they would be in an error state.
With this being said, I suggest manually removing the file from the filesystem and afterward clearing any pending sync info, and then no further syncing will be attempted.

Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs