Restart the toolstack on each server.

You should be able to delete the snapshots without causing any harm. A couple of things to keep in mind --

• If the snapshot is associated with an existing backup job, then the next run of that job will result in a full backup instead of a delta

• It may take some time for the snapshots to coalesce following deletion, so this could still affect your backups until they are completely removed

• If you want to delete the backups associated with the old job, then you can from the Backup > Health tab in XO

It is also possible to perform this activity from within XO as described here. There are some prerequisites for performing this action that you should review -- https://docs.xcp-ng.org/installation/requirements/#-pool-requirements

I would setup a Continuous Replication backup job to create a duplicate VM on the new storage repository. When you are ready to perform the cutover, shutdown the original VM, perform one final run of the CR job, and then start the new VM on the new pool.

Interesting read that mentions xcp-ng!

https://www.theregister.com/2022/09/30/citrix_xen/

Yes, it's technically possible, as long as the underlying hardware is compatible. For example, you can't put a server using AMD processors into a pool with Intel processors.

The server being moved into the existing pool will lose its local storage and all VMs stored there, so you will need to migrate those VMs to the main pool before the server is merged. Afterwards, you can move them back if desired.

@JoyceBabu They are now available at https://www.xenserver.com/downloads

@jr-m4 Yes, it seems that all dropdown lists are broken by a recent dependency update. XO team has been notified.

@BrianDLC The error ""EACCES: permission denied" should have pointed you to a permissions error to begin with.

Since we have no knowledge of how that script operates, it often makes more sense to refer you to their repo for help rather than us guessing at the reason for the issue.

@Ascar I suspect that Olivier means to register with the XO instance using this syntax --

xo-cli register [--allowUnauthorized] [--expiresIn <duration>] [--otp <otp>] <XO-Server URL> <username> [<password>]

You can run xo-cli without any parameters to get the full usage text.

Is xo-server running? Check systemctl status xo-server

You can also check the recent logs with journalctl -u xo-server -f -n 50

@rustylh Great! Are you now able to move beyond the error you posted above?

@rustylh Did you follow the instructions to visit the page and a cept the self-signed certificates?

@olivierlambert Pretty sure the problem originates from this PR.

@wf said in XO Community edition backups dont work as of build 6b263:

How do I roll back to a previous commit?

git checkout <target commit>

Then rebuild with yarn; yarn build

@venkatm Which firmware is the VM using to boot, BIOS or UEFI? Are you ending up in the dracut emergency shell?

@francescomaria-c A few things to check --

• Is the pool master fully patched? If the slave is more up-to-date than the master, then it can display behavior such as you describe where it is unable to communicate with the master.

• When joining a new host to a pool, this new host should only have the management network configured as it will inherit its network configuration from the pool.

Thanks for letting us know. I've passed the information on to our IT staff. In the interim, you should be able to respond to that ticket by accessing the support portal at https://xen-orchestra.com/#!/member/support

@kmgallo From your description, it sounds like these hosts were in separate pools. Is that correct? Are you able to SSH into the host and check its status from within xsconsole?

@joneill Switch to the Licenses tab (XOA > Licenses) and then click the red button to activate the license on the appliance.