From a network perspective it requires two additional ports to be opened - 5433 - and your data to be pulled from the hypervisor manager. Assuming you have OLVM 4.2 or newer – just add your manager to vProtect and setup is done. This strategy supports incremental backups. So instead of having to install multiple Proxy VMs, you can have a single external Node installation, which just invokes APIs via the OLVM manager. This API appeared in OLVM 4.2 and allowed export of individual snapshots directly from the OLVM manager. Please make sure you follow these steps: LVM setup on vProtect Node for disk attachment backup mode.
This approach does not require an export storage domain to be set up. The disk attachment mode requires Virtio-SCSI to be enabled on the vProtect Node VM (which can be enabled in VM settings -> Resource Allocation -> VirtIO-SCSI Enabled at the bottom).ĭuring backup/restore operations, disks are transferred by attaching them to the proxy VM. vProtect should automatically detect the VM with vProtect during the index operation. Note: OLVM API v4 environments require vProtect Node to be installed in one of the VMs residing in the OLVM cluster.
optional application consistency using pre/post snapshot command execution.optionally FS freeze can be executed before snapshot can be executed (FS thaw once the snapshot is completed) if enabled and guest tools installed inside.crash-consistent snapshot using hypervisor's API.Remember that you need to install 1 Proxy VM per cluster so that the drives the node tries to attach are reachable.ĭrawback - no incremental backup for now. This strategy allows you to exclude drives from backup that you do not need. The proxy VM is able to read the data from the attached disk snapshots and forward them to the backup provider. In this strategy, you have a VM called “Proxy VM” that invokes commands on your hypervisor manager to snapshot and attach drives of a specific VM to itself (Proxy VM). If the snapshot command fails because there is no compatible guest agent present, the live snapshot is re-initiated without the use-quiescing flag. Note: All live snapshots are attempted with quiescing enabled. Note: Different strategies require a node to be installed either as a VM in the environment that you back up or installed separately.
OLVM environments can be protected in several ways. This user must have all permissions related to managing snapshots, creating/removing VMs, operating disks and exporting data. Note: a username for OLVM environments needs to be provided in the format - i.e.
0 kommentar(er)
