Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. Question about backup

Question about backup

Scheduled Pinned Locked Moved Support
4 Posts 3 Posters 17.2k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • I
    I
    johnny
    wrote on last edited by
    #1

    Hello guys,
    I have a cronjob evey night for backing up everything, mysql and configuration files. The mysqldump takes some time though, around 6 minutes +
    netxms reports a critical event after 3 minutes of the start of dump: Thread "Syncer Thread" is not responding
    I assume that this is because of the mysqldump.
    Is there another approach of doing daily backups?
    should you stop/pause netxms service and then backup?
    or is there a way to disable that check?

    1 Reply Last reply
    0
    • A
      A
      Alex Kirhenshtein
      wrote on last edited by
      #2

      Yes, mysqldump lock tables, that's normal.
      There are two solutions:

      1. use mysql replication for backup
      2. block SYS_THREAD_HANG for backup timeframe (I use this option in most setups).

      Add new EPP rule at the top of the policy:

      Event: SYS_THREAD_HANG
      Script:
        now = localtime();
        return (now->hour == 3 && (now->min >= 10 && now->min =< 20));
      Action: Stop processing

      (I assume that backup is between 3:10 and 3:20 - adjust script as needed)

      1 Reply Last reply
      0
      • I
        I
        johnny
        wrote on last edited by
        #3

        ok I see, great thanks for the info.
        I've just inserted in the existing rule in event processing Policy "Generate an alarm when one of the system threads hangs or stops unexpectedly"
        I've added in the filtering script the following:

        now = localtime();
        return (now->hour == 1 && (now->min >= 00 && now->min =< 10));
        if ( $node->name ="NODE_NAME" ){
        Action: Stop processing}
        

        I just want to stop only for the netxms server so replacing the NODE_NAME with netxms name would it work?

        edit:
        it didn't work I've understand why, it's because we say to the whole event to stop process

        In order to do a specific for that node I should create a new rule and add as a source object that node right?

        1 Reply Last reply
        0
        • V
          V
          Victor Kirhenshtein
          wrote on last edited by
          #4

          Hi,

          if you need rule to work only for specific node it is easier to put that node into "Source" list and not attempt to filter it in the script.

          Best regards,
          Victor

          1 Reply Last reply
          0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          Powered by NodeBB Contributors
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Users
          • Groups