HP BL680c XenServer Administrator's Guide 4.1.0 - Page 12

Backups

Get HP BL680c - ProLiant - G5 PDF manuals and user guides
UPC - 884420396314
View all HP BL680c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 12 highlights

XenServer Hosts and resource pools Procedure 2.4. To remove XenServer Host b from a resource pool via the CLI 1. Open a text console on any XenServer Host in the pool. 2. Find the UUID corresponding to XenServer Host b using the command xe host-list 3. Command XenServer Host b to leave the pool with the command xe pool-eject host-uuid=uuid The XenServer Host will be ejected and left in a freshly-installed state. Warning Do not eject a host from a resource pool if it contains important data stored on its local disks. All of the data will be erased upon ejection from the pool. If you wish to preserve this data, copy the VM to shared storage on the pool first, or use the xe vm-copy CLI command. When a member XenServer Host containing locally stored VMs is ejected from a pool, those VMs will still be present in the pool database and visible to the other XenServer Hosts. They will not start until the virtual disks associated with them have been changed to point at shared storage which can be seen by other XenServer Hosts in the pool, or simply removed. It is for this reason that you are strongly advised to move any local storage to shared storage upon joining a pool, so that individual XenServer Hosts can be ejected (or physically fail) without loss of data. 2.6. Backups Citrix recommends that you frequently perform as many of the following backup procedures as possible to recover from possible server and / or software failure. Procedure 2.5. To backup pool metadata 1. Run the command: xe pool-dump-database file-name=backup 2. Run the command: xe pool-restore-database file-name=backup --dry-run This command checks that the target machine has an appropriate number of appropriately named NICs, which is required for the backup to succeed. Procedure 2.6. To backup host configuration and software • Run the command: xe host-backup host=host file-name=hostbackup 6

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
XenServer Hosts
and resource pools
6
Procedure 2.4. To remove XenServer Host
b
from a resource pool via the CLI
1.
Open a text console on any XenServer Host in the pool.
2.
Find the UUID corresponding to XenServer Host
b
using the command
xe host-list
3.
Command XenServer Host
b
to leave the pool with the command
xe pool-eject host-uuid=
uuid
The XenServer Host will be ejected and left in a freshly-installed state.
Warning
Do
not
eject a host from a resource pool if it contains important data stored on its local disks. All of
the data will be erased upon ejection from the pool. If you wish to preserve this data, copy the VM
to shared storage on the pool first, or use the
xe vm-copy
CLI command.
When a member XenServer Host containing locally stored VMs is ejected from a pool, those VMs will still
be present in the pool database and visible to the other XenServer Hosts. They will not start until the virtual
disks associated with them have been changed to point at shared storage which can be seen by other
XenServer Hosts in the pool, or simply removed. It is for this reason that you are strongly advised to move
any local storage to shared storage upon joining a pool, so that individual XenServer Hosts can be ejected
(or physically fail) without loss of data.
2.6. Backups
Citrix recommends that you frequently perform as many of the following backup procedures as possible to
recover from possible server and / or software failure.
Procedure 2.5. To backup pool metadata
1.
Run the command:
xe pool-dump-database file-name=
backup
2.
Run the command:
xe pool-restore-database file-name=
backup
--dry-run
This command checks that the target machine has an appropriate number of appropriately named
NICs, which is required for the backup to succeed.
Procedure 2.6. To backup host configuration and software
•
Run the command:
xe host-backup host=
host
file-name=
hostbackup