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

Unitrends Protect

Space issues may occur on the appliance as a result of inaccurate free space calculation

SUMMARY

Space issues may occur on the appliance as a result of inaccurate free space calculation.

ISSUE

The appliance's purging subsystem may misjudge the amount of available space on the appliance which can lead to slow or failed backups and insufficient space warnings.

RESOLUTION

To resolve this issue, upgrade your appliance to version 10.1.

For resolutions to other space issues, customers can review the article titled Error: No more space on device.

CAUSE

A defect can occur where the appliance tries to manage free space within the /backups volume itself instead of managing space to the appropriately configured logical device size (a subset of /backups), resulting in not choosing to purge backups that should be purged normally. This can result in not purging data that should be purged, further exacerbating space issues. This is commonly triggered on appliances that are not using retention settings to manage maximum backup age and run full most of the time, then a large backup occurs of unexpected size resulting in overrunning the logical D2D size with new backup data.

This issue typically self-resolves but in busy units may not. 10.1 resolved this issue.

Note: If you are impacted by this condition, after upgrading to release 10.1, the appliance will properly ID backups that it shoudl have prior already purged per rule and remove them. Some customers may perceive this as a reduction in appliance retention, but these backups should not have been allowed to remain.