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

File level recovery of Linux assets from incremental backups may fail

SUMMARY

File level recovery of Linux assets from incremental backups may fail.when files contain hardlinks

ISSUE

File level recovery of Linux assets from incremental backups may fail, though recovery from the full backup is typically successful. This issue has primarily been observed in CentOS 5 but may also be encountered under CentOS 6 appliances, and is related to how hardlinks in a Linux OS may be cataloged and recovered.

RESOLUTION

To resolve this issue, upgrade to release 10.1.

The last release for CentOS 5 based appliances was 9.1.1. If your appliance is still on CentOS 5, it will require upgrading the OS if possible or replacement with a CentOS 6 system first. CentOS 5 was depreciated by Unitrends on Aug 31, 2017 and customers were asked to complete their migration to CentOS 6 between Feb 2015 and Aug 2016. You may contact Unitrends Support to see if your appliance may still be able to upgrade to CentOS 6 even past this deadline.

CAUSE

The issue related is with hardlinks associated to the file failing to recover when the original file is modified in an incremental and the newer version of the hardlinked original file is recovered prior to the linked object which may be from a different backup version. This can occur if rsync or other tool moved one or both ends of the link between 2 backups. We have adapted code to handle this very rare scenario successfully.