Citrix XenServer Recovery Guide Version 8.
Citrix XenServer Recovery Guide The purpose of this document is to provide the steps necessary to perform system recovery when using Citrix XenServer and to define the aspects of system recovery that are and are not supported. This guide does not include all the features and options available with SBAdmin, but is intended to be used as an addendum to the SBAdmin User Guide and the SBAdmin Linux System Recovery Guide. SBAdmin provides support for Citrix XenServer versions 5.6 and 6.0.
Here we can see the uuid used to identify the disk. Using the “lvdisplay” command we can see all logical volumes on the dom0 system. # lvdisplay --- Logical volume --LV Name /dev/VG_XenStorage-f8d9b6cb-6a94-5340-0cc9-5182785b1391/VHD477479e2-e5b5-4e3e-bf99-ad82e5263c67 VG Name VG_XenStorage-f8d9b6cb-6a94-5340-0cc9-5182785b1391 LV UUID 1TJBQp-7qML-SY3T-Oz8j-b6nk-O5DE-y3wgOR LV Write Access read/write LV Status NOT available Activate the volume with the following command.
append /boot/xen-3.4.2.gz dom0_mem=752M lowmem_emergency_pool=1M crashkernel=64M@32M console= vga=mode-0x0311 --- /boot/vmlinuz-2.6.32.12-0.7.1.xs5.6.100.307.170586xen root=/dev/sda1 xencons=hvc quiet vga=785 splash --- /boot/initrd-storix-sda1.img To specify the hypervisor to SBAdmin, create the file /storix/config/multibootfile (assuming /storix is your Storix data directory). Within this file, specify the path to the Xen hypervisor. In this case it would be as follows. /boot/xen-3.4.2.
System Recovery of Citrix XenServer virtualized guests(domU) The steps to perform system recovery of a Citrix XenServer virtual machine (domU) using SBAdmin are very similar to the steps for any other Linux system. Refer to the SBAdmin Linux System Recovery Guide for additional details. However, the following considerations deserve mention because they are specific to Citrix XenServer: Determining virtualization type Citrix XenServer is capable of doing both HVM and PV virtualization.
You will see output similar to the following. PV-bootloader (RW) : pygrub You can change the boot loader with the following command. Replacing the uuid for the domU. #xe vm-list param-set uuid=94012487-6bfa-306d-6e92387682eb9b0f PV-bootloader=eliloader Once the bootloader has been set, the domU can be booted to the SBAdmin boot media and recovery can take place. Further information about system recovery can be found in the SBAdmin Linux System Recovery Guide.
