From cce456242bcc6ca45c20b5bc2cbf233db3811588 Mon Sep 17 00:00:00 2001 From: Olivier Lambert Date: Tue, 23 May 2017 16:34:39 +0200 Subject: [PATCH] feat(backup): add link to the blog post about coalescing --- docs/backup_troubleshooting.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/backup_troubleshooting.md b/docs/backup_troubleshooting.md index baf19e081..f2516a1e7 100644 --- a/docs/backup_troubleshooting.md +++ b/docs/backup_troubleshooting.md @@ -25,6 +25,8 @@ First one is a chain that contains more than 30 elements (fixed XenServer limit) So in the end, this message is a **protection mechanism against damaging your SR**. THe backup job will fail but maybe next time it will be run, that chain will be OK. +> You can read more on this into our dedicated blog post regarding [XenServer coalesce detection](https://xen-orchestra.com/blog/xenserver-coalesce-detection-in-xen-orchestra/). + ### `SR_BACKEND_FAILURE_44 (insufficient space)` > This message could be triggered by any backup method.