# mount -t spfs /backup

Backup the XEN VM nodes using above example

if [ ! -d “$MOUNTPOINT” ] ; then echo “Mount point ${MOUNTPOINT} not found, kindly check”; exit 0; fi

A little wordier, but it works on my system. I changed the other ‘if exists’ type statements as well to explicit if’s and it all works as expected.

DATE=`date +%F`
XSNAME=`echo $HOSTNAME`
MOUNTPOINT=/xenmnt
UUIDFILE=”/tmp/xen-uuids.txt”
NFS_SERVER_IP=”10.10.20.230″

xe vm-list is-control-domain=false is-a-snapshot=false | grep uuid | cut -d”:” -f2 > ${UUIDFILE}

while read VMUUID
do
VMNAME=`xe vm-list uuid=$VMUUID | grep name-label | cut -d”:” -f2 | sed ‘s/^ *//g’`

SNAPUUID=`xe vm-snapshot uuid=$VMUUID new-name-label=”SNAPSHOT-$DATE”`

xe template-param-set is-a-template=false ha-always-run=false uuid=${SNAPUUID}

done ${UUIDFILE}

while read VMUUID
do

xe snapshot-uninstall uuid=$VMUUID –force

done < ${UUIDFILE}

The line

#######GET VBD######
for VBDUUID in $(xe vbd-list vm-uuid=${SNAPUUID} empty=false –minimal | sed “s/,/ /g” );

is what controls which volumes are backed up. You can run it “by hand” to see what exactly is include, for example:

# get a list of the VM UUIDS
xe vm-list

# Show the volues attached to the VM you want to look at
xe vbd-list uuid=(enter the UUID you got from the previous command)

So, yes it can be done, but would take some hacking of the script – particularly to have it deal with different situations for different VM’s

Contained in the VM backup set you will find several files, an xva file and a VHD image of the hard drives. The XVA file is the definition and or metadata of the vm itself without the VHD or Hard disk.

Get list of SR
xe sr-list

record the sr-uuid you will be using
example:
uuid ( RO) : 0c67c214-5041-2d9e-14db-2d2b7e92a8a2
name-label ( RW): XENSR1
name-description ( RW): iSCSI SR [10.10.20.221 (iqn.1992-04.com.emc:cx.apm00155221699.b5; LUN 2: APM00155221699: 10240 GB (DGC))]
host ( RO):
type ( RO): lvmoiscsi
content-type ( RO):

Import Metadata of VM
xe vm-import preservce=false filename=hylafax-12Mar2017.xva –force sr-uuid=0c67c214-5041-2d9e-14db-2d2b7e92a8a2

Get uuid of imported vm

[root@xenbl460-1 hylafax]# xe vm-list name-label=hylafax
uuid ( RO) : b2fb074f-b024-6d1d-364c-8ac2c73c90b8
name-label ( RW): hylafax
power-state ( RO): haltedGet list of snapshots of MV

Get list of snapshot of vm

[root@xenbl460-1 hylafax]# xe snapshot-list snapshot-of=b2fb074f-b024-6d1d-364c-8ac2c73c90b8
uuid ( RO) : 002ad76c-c281-5ef8-e1dd-afa637c63822
name-label ( RW): SNAPSHOT-6edb308d-4cb7-e16e-f565-fbe95609ab79-12Mar2017
name-description ( RW):

Destroy Snapshot of VM
[root@xenbl460-1 hylafax]# xe snapshot-destroy uuid=002ad76c-c281-5ef8-e1dd-afa637c63822

get list of VBD for VM
[root@xenbl460-1 hylafax]# xe vbd-list vm-uuid=b2fb074f-b024-6d1d-364c-8ac2c73c90b8
uuid ( RO) : e8c9b02a-f73d-907b-b717-ed19b6d5e751
vm-uuid ( RO): b2fb074f-b024-6d1d-364c-8ac2c73c90b8
vm-name-label ( RO): hylafax
vdi-uuid ( RO): a2eea760-6131-4afa-ac7e-87faec69a818
empty ( RO): false
device ( RO):

uuid ( RO) : 893b1267-d3bf-6520-2416-3e7bbadd61d9
vm-uuid ( RO): b2fb074f-b024-6d1d-364c-8ac2c73c90b8
vm-name-label ( RO): hylafax
vdi-uuid ( RO): 53a07b39-eac0-4e72-b0c0-69702474bd4d
empty ( RO): false
device ( RO):

uuid ( RO) : aae311d1-847a-b67c-056c-fd367136889e
vm-uuid ( RO): b2fb074f-b024-6d1d-364c-8ac2c73c90b8
vm-name-label ( RO): hylafax
vdi-uuid ( RO):
empty ( RO): true
device ( RO):

Get VDI info for each VBD
xe vdi-list uuid=53a07b39-eac0-4e72-b0c0-69702474bd4d
xe vdi-list uuid=a2eea760-6131-4afa-ac7e-87faec69a818

Pay attention to the size of the output

[root@xenbl460-1 hylafax]# xe vdi-list uuid=a2eea760-6131-4afa-ac7e-87faec69a818
uuid ( RO) : a2eea760-6131-4afa-ac7e-87faec69a818
name-label ( RW): hylafax_1
name-description ( RW): hylafax_1
sr-uuid ( RO): 0c67c214-5041-2d9e-14db-2d2b7e92a8a2
virtual-size ( RO): 17179869184
sharable ( RO): false
read-only ( RO): false

Import VDI
Now you will import each vhd file that matches the size of the vdi. if your unsure of the size use the following command as an example

Get VHD file information
[root@xenbl460-1 hylafax]# vhd-util scan -f -p -m *.vhd
vhd=hylafax_0-d9d6c6ff-f862-44ca-afc9-48b29c4b4c31.vhd capacity=5368709120 size=365006336 hidden=0 parent=none
vhd=hylafax_1-d487610b-12dc-4d9a-9981-9a97c33fa74b.vhd capacity=17179869184 size=12214732800 hidden=0 parent=none

Manually match the VHD to the VDI based on size or name label of the filename and or VDI
example: xe vdi-import format=VHD filename=hylafax_0-d9d6c6ff-f862-44ca-afc9-48b29c4b4c31.vhd uuid=53a07b39-eac0-4e72-b0c0-69702474bd4d

Do this for each VDI / VHD

Start VM
xe vm-start uuid=b2fb074f-b024-6d1d-364c-8ac2c73c90b8
or
xe vm-start name-label=hylafax

Repeat this process for each VM

thanks for your quick response.

I will try the script of REVERSEARP, (he uses mount -t nfs).
Ofcourse exiting the script when the Mount point directory is not created makes sense. I see ur goal here. But please have a closer look to this line:

‘[ ! -d ${MOUNTPOINT} ] && echo “No mount point found, kindly check”; exit 0’

I did some tests:

[root@xenhost ~]# false && echo “ok” —> nothing happens
[root@xenhost ~]# true && echo “ok” —> shell outputs “ok” (makes sense)
[root@xenhost ~]# false && echo “ok”; exit 0 –> Shell closes
[root@xenhost ~]# true && echo “ok”; exit 0 –> Shell closes

To my mind this script cant work because you always exit the script no matter the mount point directory exist or not… Sorry, just wanna verify this line. I am just wondering why this script works for you?? Where is my mistake …