Backups of Individual VMware Virtual Machines are Not Seen - Connect IT Community

/* * 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

Backups of Individual VMware Virtual Machines are Not Seen - Connect IT Community | Kaseya

SUMMARY

Backups of Individual VMware Virtual Machines are Not Seen

ISSUE

Purpose

To inform customers that filtering of Backups of certain VMware Virtual Machines (VMs) will work incorrectly if there are more than one vCenters registered to the Unitrends’ appliance and one or more VMs on those vCenters have the same name.

Description

Consider that there are more than one vCenters registered to a Unitrends appliance and there are 2 VMs with same name on those vCenters. The backups of these VMs will proceed normally.

On the ‘Status’ page, if you click on either of the vCenters, the backups of the respective VMs will be seen correctly. However, if you click on those VMs individually, no backups will be shown (although they exist).

Cause

The filtering of Virtual Machine Backups is done on the basis of the VM’s names. Hence, this kind of discrepancy is seen.

Resolution

This is fixed in Unitrends Software Version 7.2.0 and higher.

There is also a workaround available for pre 7.2.0 systems. The steps are as follows:

Consider a setup where 2 vCenters (VC1 and VC2) are registered to a Unitrends appliance. There are 2 Virtual Machines with the same name (foo1) existing on each of the vCenters
Open a vSphere Client for VC1
Rename foo1 to foo2
On Unitrends appliance –

a. Click on VC1
b. Go to ‘Backup’ page
c. Click on ‘Reload VMs’
d. Click on ‘Refresh System’

You should now start seeing the backups of individual VMs for foo1 as required

Third-Party Sources

N/A