SR_BACKEND_FAILURE_109
-
Well unfortunately the previous guy put in a production environment. He left now I'm cleaning up his messes. So yes it is in a production environment I am currently trying to resolve the issues that were created by him.
-
Ouch. And I suppose there's no pro support for this production environment?
-
Not that I am aware of. We have support individual VMs because they have paid software on them, but we don't have support on the VM manager itself.
-
While we'll try to help, that would be a good time to tell people who write the checks to think about supporting this critical part of the infrastructure
Please provide the entire SMlog so we can take a look.
-
@ntinthomas I fixed your post above so that the log displays correctly. Please follow the below example in the future --
``` log goes here ``` -
The log is longer than i can post any suggestions to get it on here?
-
Just download the entire file and host it somewhere
-
https://drive.google.com/file/d/1sbfZsUlONmtwKGNwhKLZPNdH5-v91EpQ/view?usp=sharing
I believe this is the entire log.
-
In XO: SR view, click on the SR, advanced. Can you share a screenshot here?
Also, do you have VMs with a lot of snapshots?
-
This is the screen i generally see and work from. And yes we have about 13 VM's with screenshots being sent to a FreeNas box.
-
XCP-ng center isn't an officially supported client, and worse than that, it doesn't expose the number of disks left to coalesce, unlike XO.
Also, you are on 8.1, which is EOL
-
So what would be the best solution to get this resolved?
-
Do you have a lot of snapshots in your VMs?
Having an XOA deployed would help to diagnose too.
-
So we had them scheduled to take snapshots every night of every VM. I noticed that errors were accumulating this week. How would I deploy XOA to help diagnose the issue?
-
In the XCP-NG Center GUI we have 16 VM's with 41 snapshots currently in the snapshot section on the center.
-
Using XCP-ng Center scheduled snapshot? That's really a poorly crafted feature vs XO backup capabilities (and it's not taking into account the chain, unlike XO).
I strongly suggest to get rid of XCP-ng Center at some point.
Regarding XOA deploy: https://help.vates.fr/kb/en-us/9-xen-orchestra-appliance-xoa/18-deploy-your-xoa
To fix your chain issues, please start to remove snapshots.
-
One question does the Xen Orchestra manager have to be ran on XCPNG or can get rid of XCPNG all together?
-
Also getting this log error on the Xen Orchestra Web Interface.[0_1629315103732_2021-08-18T19_31_00.542Z - XO.log](Uploading 100%)
SR_BACKEND_FAILURE_47(, The SR is not available [opterr=directory not mounted: /var/run/sr-mount/4e765024-1b4d-fca2-bc51-1a09dfb669b6], )
-
- You can run Xen Orchestra anywhere you like, as long it can reach your pool master
- Please do as I said earlier: SR view, click on the SR in question, Advanced tab. Do you have uncoalesced disks in there?
-
So in the ISCSI virtual disk storage pool 1 there are 606 items I do not see the option for coalesce at all. Here's some screenshots.
Also after researching I have found that there are 352 Items that need to be coalesce.
On the VDI to Coalesce page what is the Depth?
