feat(doc): check dead links and duplicate (#5664)

docs/full_backups.md

@@ -1,18 +0,0 @@
-# Full backups
-
-You can schedule full backups of your VMs, by exporting them to the local XOA file-system, or directly to an NFS or SMB share. The "rentention" parameter allows you to modify how many backups are retained (by removing the oldest one).
-
-[![](./assets/backupexample.png)](https://xen-orchestra.com/blog/backup-your-xenserver-vms-with-xen-orchestra/)
-
-:::tip
-Full backups are space consuming! But they allow a very simple restoration without anything to think of (the file will contain all the VM disks and information). To use less space and data transferred, take a look at the [delta backups](delta_backups.md) feature.
-:::
-
-## Backup without snapshot
-
-In some cases you will need to do a backup without doing a snapshot.
-
-The most common use case for this is a large VM on a small local SR where you just don't have the space to do a snapshot before backup.
-So for that you need to open the advanced settings of your backup job, and check the offline backup check box:
-
-![](./assets/backupnosnap.png)

docs/load_balancing.md

@@ -10,7 +10,7 @@ In the case of virtualization, you have multiple physical hosts, which runs your
 Maybe you already heard about VMWare DRS (Distributed Resource Scheduler): that's the same principle here, but for XCP-ng.
 :::
 
-So the first objective is to adapt your VM placement in live (without service interruption), depending of the load. Because Xen Orchestra is connected to [multiple pools](xo-server.md) and XCP-ng supports live storage motion, we can perform load balancing on a **whole XCP-ng infrastructure** (even between remote datacenters). A load balancing policy is called a "**plan**".
+So the first objective is to adapt your VM placement in live (without service interruption), depending of the load. Because Xen Orchestra is connected to [multiple pools](architecture.md#xo-server-server) and XCP-ng supports live storage motion, we can perform load balancing on a **whole XCP-ng infrastructure** (even between remote datacenters). A load balancing policy is called a "**plan**".
 
 Let's take a simple example, with these 2 hosts running 6 VMs:
 

docs/manage_infrastructure.md

@@ -38,7 +38,7 @@ Let's take a quick tour:
 You can edit a VM name, description and even current host by long clicking on the field
 :::
 
-## Bulk actions
+### Bulk actions
 
 You can select multiple objects (eg VMs) at once to perform a bulk action. The master checkbox will select all, or you can select anything yourself.
 
@@ -285,7 +285,7 @@ These templates will use PV configuration in order to boot: either from the righ
 
 Because there is already disks installed, you shouldn't have "Install settings" _per se_. But you can use our `config drive` setup if your template already has CloudInit installed!
 
-Please refer to the [XenServer CloudInit section](cloudinit.md) for more.
+Please refer to the [XCP-ng CloudInit section](advanced.md#cloud-init) for more.
 
 #### Interfaces
 
@@ -316,8 +316,10 @@ In the advanced tab, you have extra options:
 - Each VM has a maximum vCPU number. This value can't be changed while the VM is running. You can reduce the number of vCPUs, but you can't assign more than the set max. In XO, while your VM is halted, set the max vCPUs you would need, then boot it. Now you can reduce it and then expand it later to this maximum.
 - The same limitation applies to static RAM.
 
-You can learn more about XenServer [resource management on the Citrix Website](https://docs.citrix.com/de-de/xencenter/6-5/xs-xc-vms-configuring/xs-xc-vms-memory/xs-xc-dmc-about.html).
-
+You can learn more about XenServer [resource management on the Citrix Website](https://docs.citrix.com/en-us/citrix-hypervisor/system-requirements/configuration-limits.html).
+:::tip
+XCP-ng doesn't limit VMs to 32 vCPU
+:::
 ### VDI live migration
 
 Thanks to Xen Storage Motion, it's easy to move a VM disk from one storage location to another, while the VM is running! This feature can help you migrate from your local storage to a SAN, or just upgrade your SAN without any downtime.
@@ -349,7 +351,7 @@ If you pool supports HA (must have shared storage), you can activate "HA". Read
 #### Docker management
 
 :::tip
-Please [read the dedicated section](docker_support.md) to install a Docker Ready VM.
+Please [read the dedicated section](manage_infrastructure.md#docker-support) to install a Docker Ready VM.
 :::
 
 ### VM CPU priority
@@ -593,4 +595,4 @@ xscontainer-prepare-vm -v <VM_UUID> -u <username>
 
 :::tip
 Because "prepare-vm" is not exposed outside of the Dom0 (yet?), we can't use Xen Orchestra to give you a one-click solution as of now.
-:::
+:::

docs/purchase.md

@@ -111,7 +111,7 @@ Once you have bound the plan to your end user account, you cannot change it. Dou
 The Xen Orchestra partner program is designed to offer you the opportunity to become a reseller of Xen Orchestra and deliver a full stack solution to your customers.
 
 :::tip
-Becoming a reseller will grant you a standard discount. However, **the reseller status is designed for companies that want to actively prospect for new Xen Orchestra users**. That's why we are asking our partners to **resell Xen Orchestra at least two times a year**. If you are acting as a third party purchaser answering to a specific request from one of your customers, you don't need to apply to the reseller program - you can follow [this process](https://xen-orchestra.com/docs/through_purchase_department.html) instead.
+Becoming a reseller will grant you a standard discount. However, **the reseller status is designed for companies that want to actively prospect for new Xen Orchestra users**. That's why we are asking our partners to **resell Xen Orchestra at least two times a year**. If you are acting as a third party purchaser answering to a specific request from one of your customers, you don't need to apply to the reseller program - you can follow [this process](purchase.md#purchase-xoas) instead.
 :::
 
 ### Apply to the program

docs/troubleshooting.md

@@ -176,7 +176,7 @@ The system logs are visible by using this command:
 $ tail -f /var/log/syslog
 ```
 
-You can read more about logs [in the dedicated logs chapter](logs.md).
+You can read more about logs [in the dedicated logs chapter](troubleshooting.md#logs).
 
 ### Ghost tasks
 

docs/users.md

@@ -315,7 +315,7 @@ Finally, if a user has been granted access to multiple resource sets, they can b
 
 ### Toward the Cloud
 
-Self-service is a major step in the Cloud. Combine it with our [Cloudinit compatible VM creation](cloudinit.md) for a full experience:
+Self-service is a major step in the Cloud. Combine it with our [Cloudinit compatible VM creation](advanced.md#cloud-init) for a full experience:
 
 - create a Cloud ready template
 - create a set and put Cloud templates inside

docs/xosan.md

@@ -27,11 +27,11 @@ The objectives are to:
 
 To deploy XOSAN, please follow the rest of the documentation:
 
-- [XOSAN Requirements](xosan_requirements.md)
-- [Types of XOSAN](xosan_types.md)
-- [How to create a new XOSAN Storage](xosan_create.md)
-- [XOSAN management](xosan_management.md)
-- [Get a free XOSAN trial](xosan_trial.md)
+- [XOSAN Requirements](xosan.md#requirements))
+- [Types of XOSAN](xosan.md#xosan-types)
+- [How to create a new XOSAN Storage](xosan.md#creation))
+- [XOSAN management](xosan.md#advanced-options)
+- [Get a free XOSAN trial](xosan.md#try-it)
 
 ## Requirements