Backups failing because of a nonexistent space limitation - 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 failing because of a nonexistent space limitation - Connect IT Community | Kaseya

SUMMARY

Multiple subsystem backups were failing, due to not being able to register/reserve space on a system.

ISSUE

Multiple subsystems are failing and not able to register / reserve space on the system.

RESOLUTION

Update to version 9.1.0 or later of the Unitrends software.

CAUSE

This condition is due to an excessive number of SMGR registrations that are stale (no longer being used).

Failures during open and close could result in a reservation being left on the system. There is a limit of 512 reservations so eventually this can cause the subsystems to fail when enough of these occur. This particular failure will have 10MB reservations that are stale and smgr_display will show an entry similar to the following, where the 4th field is the size of the registration:

2  1929379984      D2DBackups/1    10485760     0       Mon Aug 15 10:39:04 2016

The specific failure detected is where a backup begins and the client stops responding. The bpserverd-backup error log will have an entry:

Aug 15 11:12:51 : [LOG3] archive.c:5052: All data has been received from the client, finishing up ...

Aug 15 11:12:51 : [LOG0] archive.c:5063: Expected EOF undetected, failing backup (total_data sent 133660672).