XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics

    • All categories
    • stormiS

      XCP-ng 8.3 updates announcements and testing

      Watching Ignoring Scheduled Pinned Locked Moved News
      490
      1 Votes
      490 Posts
      205k Views
      B
      @stormi installed updates. Did some backups and VM migrations between various storages (bad and qcow2) looks good so far.
    • J

      Backups Fail with ENOENT: no such file or directory

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      3
      0 Votes
      3 Posts
      46 Views
      nikadeN
      Had major issues with backups a while ago, it was due to the firmware of the NIC in the physical server. We found out by moving our XO vm to another physical host and then error went away, moving it back made it come back.
    • G

      auth-ldap (v0.10.11) - Specifying Multiple (Primary / Secondary) AD Servers under the URI field

      Watching Ignoring Scheduled Pinned Locked Moved Advanced features
      3
      0 Votes
      3 Posts
      100 Views
      J
      @gcpeters4 said: Is there a way to specify a primary and secondary Active Directory server when configuring auth-ldap? I've encountered situations where the specified URI (ldap://activedirectory1.domain.x.y) server isn't reachable so I'd like to be able to specify a secondary AD server using something like this: ldap://activedirectory1.domain.x.y, ldap://activedirectory2.domain.x.y Basically multiple AD servers; separated by a comma. Unlike the other forum post regarding Multiple AD Sources, both of these control the same domain. Thanks. Another option is to setup AD clustering (clusters) with both controllers part of the same cluster. Alternatively setup an AD Failover which has a single FQDN endpoint but two members. Either or both of these likely to result in a single FQDN that can be fed into the plugin.