Why Client Agent based backups fail for the directory C:\mount? - Converting from Server 2012 Core install to Full GUI - 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

Why Client Agent based backups fail for the directory C:\mount? - Converting from Server 2012 Core install to Full GUI - Connect IT Community | Kaseya

ISSUE

Your Windows Client Agent based Master backups fail. The failure may show up as a "Verify Failure" or "Incomplete Backup". If you review the Master backups files in the C:\PCBP directory (Master journal has the naming format of Mast_Month_Day_Hour_Minute_second.txt. Example: Mast_Nov_25-02_00_58.txt) you will find entries similar to the following:

C:\mount\Windows\System32\ServerManagerLauncher.exe, < 98.9% real data>
C:\mount\Windows\System32\ServerTelemetryConfig.exe, < 100.0% real data>
C:\mount\Windows\System32\ServerWerOptin.exe, <<scan failed>, <Not backed up>

These sparse files may also present their hardlinks to a path that no longer exists or is not accessible.

C:\mount\Windows\WinSxS\amd64_mchgr.inf_31bf3856ad364e35_6.3.9600.16384_none_05b90a2b2d434dac\ddsmc.sys
is a hardlink to ===> | C:/mount/Windows/System32/DriverStore/FileRepository/mchgr.inf_amd64_6e053e26f7e6e8c3/ddsmc.sys

RESOLUTION

Research if this data is needed. If the data is needed, you will need to determine why it can not be called during a backup. There is a good chance the data is also not accessible to your Antivirus scans.

In the case of a migration from Windows Core to a full Windows 2012, the directory does not contain data that you will need for proper restoration of the Windows 2012 server. In this case excluding the C:\mount directory from your backup schedule, and running a new one time Master backup will correct the backup chain set.

CAUSE

These files are either not accessible by normal measure or are no longer existing on the system. The C:\mount directory could have been created as part of a software install or migration (example: to add a GUI to Core 2012).