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
    • ditzy-oliveD

      suggestions for upgrade path XCP-ng 8.2.1 -> XCP-ng 8.3.0

      Watching Ignoring Scheduled Pinned Locked Moved XCP-ng
      9
      0 Votes
      9 Posts
      58 Views
      olivierlambertO
      So if you follow the proper path (master first, evacuate to slaves, upgrade master, reboot, and repeat), there's no reasons to do otherwise
    • A

      Continuous Replication isnt deleting old Replikas anymore since Update

      Watching Ignoring Scheduled Pinned Locked Moved Solved Backup
      7
      1 Votes
      7 Posts
      363 Views
      olivierlambertO
      Hi @0x68 can you provide more details?
    • P

      NOT_SUPPORTED_DURING_UPGRADE()

      Watching Ignoring Scheduled Pinned Locked Moved Management
      2
      0 Votes
      2 Posts
      11 Views
      olivierlambertO
      The upgrade process doesn't involve downtime. You start with the master: evacuate all VMs to slaves Upgrade the master to 8.3 via the iSO When done, target one slave: move all VMs elsewhere (including the up to date master), and repeat the process. In short, you always migrate VMs BEFORE upgrading a node, and always starting with the master. The order of slaves doesn't matter.
    • P

      FILE RESTORE / overlapping loop device exists

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      3
      0 Votes
      3 Posts
      41 Views
      P
      on another simpler install (One host, one XOA, no proxy, SMB remote in same lan not an S3 remote), XOA 5.112.1 same problem ! I think something has been broken along the way @bastien-nollet @florent granular file restore is important for us, otherwise we have to get Veeam Agent backup instead of XO Backup