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

Release Notes for Recovery Series and Unitrends Backup 10.4

DESCRIPTION

This document describes fixes introduced in the 10.4 release. For upgrade instructions and considerations, reference the Upgrade Guide for Recovery Series, Recovery MAX, and Unitrends Backup.

Features

This release adds these new features:

Multiple hot backup copy targets - You can now copy backups from your source backup appliance to multiple hot backup copy targets. This feature enables you to add one or more Unitrends appliance and Unitrends Cloud targets to a single source appliance. For details, see these topics in the Administrator Guide for Recovery Series, Recovery MAX, and Unitrends Backup:
Log truncation for image-level backups – This release adds a new Allow application aware option to run image-level backups that truncate logs of hosted Exchange and SQL applications. Configure this setting by checking these boxes in the Edit Asset dialog: Show Image Level Backup Settings and Allow application aware. For details, see these topics in the Administrator Guide for Recovery Series, Recovery MAX, and Unitrends Backup:
- Windows Image-level Backups Overview
- To edit an agent-based asset

Fixes

The table below lists fixes included in this release. Unless stated otherwise, you can apply each fix by simply upgrading your appliance.

Component

Bug

Cold backup
copy

Backup copy to Amazon S3 - Resolved an issue where the copy job was terminated due to insufficient space, even though no space limit had been configured for the S3 target. With this fix, space is dynamically added as needed to the S3 bucket so that jobs complete successfully.
Preparing disk media – Resolved an issue where CentOS 7 appliances could not prepare disk media containing backup copies that were written by a CentOS 6 appliance. The operation would fail with a Failed to prepare device for use error.

Recovery

Windows replica with hosted SQL application – Resolved an issue where replica recovery and related DRaaS recovery failed due to missing SQL metadata. This fix requires the 10.4 Windows agent.