The storage location on which a PHD Virtual Backup Appliance resides determines which virtual machines it can back up
The storage location on which a PHD Virtual Backup Appliance resides determines which virtual machines it can back up. For example, consider the following scenario:
Your virtual environment consists of two hosts, HostA and HostB. You have multiple virtual machines running on each host, most of which are stored on a shared network storage location which both hosts have been configured to access. The remaining few VMs are stored on each host's local storage.
You deploy a PHD Virtual Backup Appliance to HostA and select to store it on the shared storage location.
Since the PHD VBA was stored on the shared storage location, it will be able to backup up all of the VMs also on that same shared storage, regardless of the host they were deployed to. Additionally, since the PHD VBA was deployed to HostA, it will also be able to backup any of the VMs stored on HostA's local storage.
The VMs on Host2's local storage cannot be backed up, as the PHD VBA cannot access that local storage location.
To avoid situations where you end up with VMs that cannot be backed up in your environment, you can:
- Store all VMs on the shared storage locations (make sure each host has access to these locations).
- Deploy additional PHD VBAs to the hosts with VMs on local storage.