/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Backup Recovery

Disks offline after a Hyper-V IR

SUMMARY

Some Guest VM disks go offline after a Hyper-V IR has completed.

ISSUE

Purpose

To explain how to resolve an issue where disks are offline for some Windows servers after they are recovered through Hyper-V instant recovery in audit or instant recovery mode.

Description

This problem occurs only when performing a Hyper-V instant recovery. (It does not occur when performing a VM restore.) It affects only Windows server VMs meeting all of the following criteria:

The servers have multiple SCSi controllers.
Multiple disks reside on each controller.
The location number for a disk on one controller is the same as the location number for a disk on another controller.

For example, a Windows server with the following disk configuration would be affected:

SCSi controller 1 with disks residing in locations 1, 2, and 3.
SCSi controller 2 with disks residing in locations 1, 4, and 5.

After the recovery, all three disks for SCSi controller 1 would be online, and disks in locations 4 and 5 for controller 2 would also be online. However, the disk in location 1 on controller 2 would be offline.

Resolution

You can resolve this issue by accessing Disk Management on the server VM, right-clicking on the disk in an offline state, and then clicking Online. Procedures may vary slightly depending on the server version.

For more information about Hyper-V instant recovery, see Instant recovery for Hyper-V in the Unitrends Recovery-Series and UEB Adminstrator’s Guide.