Pool Metadata Backup in XO throwing a Redis Configuration Error

MichaelCropper

Backup > New > Backup Metadata > Pool Metadata

Error also when doing

Backup > New > Backup Metadata > XO Config

Create

MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.

I can't find any settings in either XO or XCP-ng Center that allows any kind of configuration related to this option.

A Google search turned up virtually nothing XCP-ng related on this topic, so I'm a bit lost.

Any ideas?

Danp

Some additional details would likely help. For example --

Are you running XOA or XO from source?
Is your install up-to-date? What version / commit?
Is this a new install or did it recently "break"?
Etc

Also, it isn't clear when the error message appears. I assume that it is when you click the Create button, but no way to know for sure without more details.

MichaelCropper

@Danp

XO from Source
Yeah updated from latest Git commit about a week or two ago and re-ran the handy installer/updater script - Git Commit ID: 9c1acdc2bb5bb9c524e39638b3f725119e52c20d (12th August)
XCP-Server has been up and running for about a year I imagine, ran about 100x patches recently, but I've nothing to compare with as this is in a lab setting and this is the first time I've been playing with the Metadata backups to take a look at what they do
Yeah, error came up when I clicked the Create button

Summary though... I did the old IT solution of turning the server off and back on again, and magically it's working now. How bizarre.

That being said, I've just successfully ran the two backups manually which have worked successfully, but when I click on the 'Disable' button to try to 'Enable' the automated backups, the same error occurs

Same error.

I'm wondering if this could in some how be related to the Backup HDDs currently going through a migration from JBOD to RAID Array which is happening at present. I'll have to wait a few days until I can re-test this once this background process isn't running due to the lengthy time for this happening. I wouldn't have thought that would have caused an issue though as the HBA should take care of all of this under the hood.

Interestingly, the VM backups I've set up previously worked fine.

Yet when I try to create a new VM backup that has worked previously, this is now failing.

Same for when I try to Edit then Save (no changes) to an existing backup, that also now fails. Hmm. May be pointing to a bug in the latest version of XO in that commit.

I'll update to the very latest version at some point over the next few days and give this another test as it may have already been fixed in recent commits, assuming it is a bug and not something weird with my setup.

MichaelCropper

Updated to latest commit and that seems to have solved things.

olivierlambert

As stated in the big warning yellow box here in the official doc: https://xen-orchestra.com/docs/community.html#report-a-bug

Closing then