Ask the Community
Groups
Protection of Pass-through disks on Hyper-v or VMware - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Protection of Pass-through disks on Hyper-v or VMware</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <h3 data-id="purpose">Purpose</h3> <p>Describe the process for protecting Pass-Through disks in VMWare or HyperV environments. </p> <h3 data-id="description">Description</h3> <p>In a virtual machine, disks are most commonly locally attached or SAN storage presented and managed by the hypervisor itself to the guest operating system through the guest OS configuration and settings. However, in some cases, the guest itself manages remotely attached storage or USB connected volumes as part of its own storage. This may include iSCSI maps to network shares or mounted NAS volumes that are not part of the hypervisor’s directly managed storage.</p> <h3 data-id="cause">Cause</h3> <p>Because the mounted resource is not visible to the hypervisor, only the guest OS is aware of that connectivity. That means that Unitrends App Aware backups of the VM guest through connection to the hypervisor would also not be aware of that storage, and would not protect it. </p> <h3 data-id="resolution">Resolution</h3> <p>In these cases, where storage has been configured inside the guest OS instead of inside the hypervisor, known commonly as pass-through storage, the guest machine will have to be backed up using the Agent method and cannot be properly protected using the hypervisor aware backup. </p> <p>To do this, Exclude the machine from VMWare or HyperV backups, and configure the guest machine as you would a physical machine by installing and registering an agent to the client OS for backup, and managing the system as if it was a physical server by including it in traditional backup schedules. </p> <h3 data-id="third-party-sources">Third-Party Sources</h3> </article> </main>