<h2 style="margin-top: 0px; margin-bottom: 10px;">What is included in Macrium SiteBackup?</h2>
<p style="margin-top: 0px; margin-bottom: 0px;"><strong>Centralized Console</strong> – Manage backups across networked Windows machines remotely.<br /><strong>Image-Based Backup</strong> – Full disk images plus file-level definitions.<br /><strong>Image Guardian</strong> – Ransomware protection locks stored backup files.<br /><strong>Rapid Recovery</strong> – Built-in PXE server and dissimilar-hardware restore.<br /><strong>Performance Metric</strong> – Backup and restore up to twice as fast.<br /><strong>Important</strong> – Windows-only; no native Linux or macOS agents.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What are the main benefits of Macrium SiteBackup?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Macrium SiteBackup is a centralized backup and recovery platform that protects many networked Windows workstations and servers from a single web console. It is built for IT teams that need scheduled imaging, fast restores, and ransomware-resistant repositories across a whole fleet.<br /><br /><strong>One Console</strong> – Schedule and monitor every agent centrally.<br /><strong>Faster RTO</strong> – Multithreaded restores cut recovery time sharply.<br /><strong>Ransomware Defense</strong> – Image Guardian blocks unauthorized backup changes.<br /><strong>Flexible Storage</strong> – Network, local, Azure, and AWS repositories.<br /><strong>Scalable Seats</strong> – Add single seats without minimum quantities.<br /><strong>Continued Access</strong> – Restore-only mode keeps backups readable later.</p>
<p style="margin-top: 15px; margin-bottom: 15px;"><a href="https://keys.express/EN/blog/post/data-loss-is-costly-how-backups-help-you-avoid-downtime" target="_blank"><strong>Why backups protect against expensive data loss</strong><br />For more background on backup planning, read our guide on how reliable backups prevent costly downtime.</a></p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What does Macrium SiteBackup do?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">SiteBackup centrally backs up, restores, and monitors multiple networked Windows computers from one web-based console. Each protected machine runs a SiteBackup Agent that reports to the central server, so a single administrator can schedule disk-image and file-and-folder backups across an entire fleet. It is powered by the SiteManager Platform and is the successor to Macrium Site Manager. Instead of configuring each machine separately, you define a schedule once and apply it to grouped or tagged agents, which removes most of the repetitive per-device setup.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Which operating systems and workloads does Macrium SiteBackup cover?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">SiteBackup protects Windows systems only; the agent runs from Windows XP SP3 and Server 2003 SP2 up to Windows 11 and current Server releases, with no native Linux or macOS agents. It is sold in Workstation, Server, and Virtual Server editions, so you match the edition to each machine's role. A site running mixed Windows and Linux infrastructure will still need a separate tool for the non-Windows hosts. Note that granular SQL and Exchange protection (Server Plus) sits in the standalone Reflect line, not in SiteBackup, so confirm your database hosts are covered before standardizing on it.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What is the difference between Macrium SiteBackup and Reflect X?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Reflect X is a standalone product licensed and managed per machine, while SiteBackup centralizes scheduling, deployment, and monitoring for many machines from one server. Reflect X suits a small number of systems or air-gapped machines managed individually; SiteBackup suits fleets where central agent deployment, Active Directory integration, and grouped scheduling cut admin time. Both share the same imaging engine and the same open-source image format, so images stay compatible across the range. The practical rule: choose Reflect X for a handful of independent machines, and move to SiteBackup once manual per-machine management becomes the bottleneck.</p>
<table style="width: 100%; border-collapse: collapse; background-color: #efefef; margin-top: 15px; margin-bottom: 15px; font-size: 14px; line-height: 1.35;">
<tbody>
<tr><th style="border: 1px solid #ffffff; padding: 9px 8px; text-align: left; font-weight: bold; background-color: #dedede;">Feature</th><th style="border: 1px solid #ffffff; padding: 9px 8px; text-align: center; font-weight: bold; background-color: #dedede;">Reflect X</th><th style="border: 1px solid #ffffff; padding: 9px 8px; text-align: center; font-weight: bold; background-color: #dedede;">SiteBackup</th></tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Management model</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">Per machine</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">Central console</td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Best suited for</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">Single systems</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">Networked fleets</td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Central agent deployment</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #d9534f; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✕</span></td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #32a852; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✓</span></td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Active Directory integration</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #d9534f; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✕</span></td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #32a852; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✓</span></td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Grouping and tagging</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #d9534f; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✕</span></td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #32a852; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✓</span></td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Built-in PXE server</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #d9534f; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✕</span></td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #32a852; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✓</span></td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Offline activation</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #32a852; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✓</span></td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #32a852; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✓</span></td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Available editions</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">Workstation, Server</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">Adds Virtual Server</td>
</tr>
</tbody>
</table>
<h3 style="margin-top: 30px; margin-bottom: 10px;">How does Macrium SiteBackup protect backups from ransomware?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">SiteBackup uses Macrium Image Guardian (MIG) to lock backup files so only authorized Macrium processes can modify them, which stops ransomware from encrypting or deleting existing images. MIG status is shown per repository in the console alongside disk usage and a forecast of upcoming backups. Pairing this with repository synchronization to a second location keeps an off-server copy if the primary repository is hit. A backup that ransomware can silently overwrite offers no recovery guarantee, which is why this file-level lock matters more than scheduling alone.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What storage repositories can Macrium SiteBackup use?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">SiteBackup can store images in local repositories, network shares, Azure Storage Accounts, and AWS Storage Gateway, and it can synchronize one repository to a second location. This lets you keep fast on-site restores while replicating to cloud or remote storage for disaster recovery. Repository disk usage, MIG status, and a backup forecast appear in the console, so capacity problems surface before a job fails. Automatic retry on intermittent write errors also reduces failed backups over unreliable network links, which is useful when agents back up across branch connections.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What happens to your backups if the plan ends?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">If a plan lapses, SiteBackup switches to restore-only mode, so existing backups stay readable and recoverable even though new scheduled backups stop. This means a renewal gap never locks you out of images you have already captured. You can still run recoveries and browse repositories, but resuming scheduled protection requires an active plan. For secure deployments, offline activation supports fully air-gapped networks, so isolated sites can be licensed without internet access.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Frequently asked questions about Macrium SiteBackup</h3>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Can existing Macrium Site Manager backups still be used in SiteBackup?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Yes. Backups created in Site Manager remain fully accessible after moving to SiteBackup, so historical images stay protected during the transition. Existing Macrium Agent Licenses (MALs) are converted to SiteBackup seats automatically as part of the upgrade, with one seat equal to one previous agent license. This lets you migrate at your own pace without re-creating definitions or losing access to older recovery points.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Can SiteBackup deploy and organize agents across a network?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Yes. Agents can be deployed remotely at scale with Active Directory integration, and a command-line installer is available for scripted rollouts. Grouping and tagging then let you apply one schedule or definition to many machines at once instead of configuring each device. For a team onboarding dozens of endpoints, this is the main difference from running standalone Reflect installs machine by machine.</p>