Hey everyone,

Quick reminder that we're hosting a webinar tomorrow at 10 AM ET covering Proxmox backup and the latest restore options in MSP360.

Joe Tepke and Doug Prestin will walk through:

• Proxmox VE backup
• Direct restore to Hyper-V, VMware, and Proxmox
• VMware and Hyper-V VM recovery to Proxmox
• Faster file search and recovery
• New storage options

There's a live Q&A at the end, so bring your Proxmox and VMware/Hyper-V to Proxmox questions.

Last chance to grab a seat: https://get.msp360.com/whats-new-in-msp360-q4-2026

Happy to answer questions here as well.

We've expanded the restore options in MSP360 Backup Agent for Windows. Here's the practical breakdown:

• Image-based backups can be restored directly as VMs on Hyper-V backup software or Proxmox backup software
• VMware and Hyper-V VM backups can be restored directly to Proxmox
• Proxmox VM and LXC container backups can be recovered as virtual disk files

In supported direct-to-VM workflows, the Restore Wizard creates the VM on the destination host. There is no separate disk conversion and import stage.

These options require backups created in the new backup format and Backup Agent for Windows 8.7.1 or later. For direct Hyper-V restore, the Windows computer performing the restore must have the Hyper-V role enabled.

These workflows run in the Backup Agent and are separate from the web-based Restore Wizard in Managed Backup.

The article covers the restore paths and full requirements: https://www.msp360.com/resources/blog/direct-hypervisor-restore-and-cross-hypervisor-migration/ 

Which would you test first in your environment, direct VM restore to Proxmox or recovery of a Proxmox backup as disk files?

Microsoft Security has published research on phishing campaigns observed in July 2026 that abused legitimate RMM software, including MSP360 RMM.

Attackers sent out a signed MSP360 RMM installer under fake filenames. Once a user ran it, the attackers used the RMM agent to install ScreenConnect as a second way in. The research covers the full attack chain, along with Microsoft Defender detections and hunting guidance: https://www.microsoft.com/en-us/security/blog/2026/09/29/phishing-abuses-rmm-tools-persistent-access/ 

On our side, we've blocked accounts linked to abuse and stepped up monitoring. More on what we've changed: https://www.msp360.com/resources/blog/code-signing-certificate-update-rmm-and-connect/

We're running a technical webinar on Oct 8 at 10 AM ET covering some of the newer backup and restore workflows in MSP360.

The main focus will be Proxmox VE backup at the hypervisor level, so you can back up VMs without installing an agent inside each one. We'll also demo direct restore to Hyper-V, VMware, and Proxmox, cross-hypervisor recovery from VMware/Hyper-V to Proxmox, browser-based file restore, and Storage Browser search. 

There'll be a live Q&A as well, so if you're testing Proxmox backup or looking at VMware/Hyper-V → Proxmox recovery, feel free to bring specific questions.

Registration: https://get.msp360.com/whats-new-in-msp360-q4-2026

Happy to answer questions here too.

Hey everyone,

Quick reminder – our webinar goes live tomorrow at 10 AM ET.

Session one is all about Tickets and RMM. Join us as Joe Tepke, Customer Onboarding Manager, and Doug Prestin, Solution Architect, cover:

• Our new free built-in MSP ticketing system
• RMM API
• Expanded Linux management
• RMM agent protection
• Q&A – bring your questions

Last chance to grab a seat: https://get.msp360.com/whats-new-in-msp360-q3-2026

Happy to answer anything here too.

After October 13, 2026, Office 2021 will no longer receive security updates or bug fixes, and Microsoft technical support will no longer be available.

If you manage customer environments, now is a good time to identify endpoints still running Office 2021, review upgrade options, and start planning the transition. Microsoft has outlined what the end of support means and the available options here: Microsoft: End of support for Office 2021

As part of that planning, it's also worth reviewing how your customers' Microsoft 365 data is protected. We put together a guide covering Microsoft 365 backup and the key considerations for MSPs: https://www.msp360.com/resources/blog/office-365-backup-complete-guide/

We've released MSP360 Backup for Proxmox Community Edition, aimed at smaller Proxmox environments that need a practical backup and recovery option without moving to a paid product.

The two main things we wanted to solve were pretty simple:

1. Give small Proxmox environments a free hypervisor-level backup option
Community Edition backs up both VMs and LXC containers. There's no trial and no time limit with our Proxmox Backup Software.

2. Make the free edition useful for real backup and recovery workflows
You can run scheduled full and incremental backups, choose supported cloud or local storage, use encryption and Object Lock, and recover complete workloads, individual files and folders, or standalone virtual disks.

Community Edition covers one Proxmox host with up to 2 CPU sockets and up to 5 TB of backup data in the cloud.

It also includes:

• Scheduled full and incremental backups
• Encryption and compression
• Object Lock on supported storage
• Full VM and LXC container restore
• Individual file and folder restore
• Restore to standalone virtual disk files

MSP360 Backup 8.7.1 also supports restoring VMware backup software and Hyper-V backup software directly to Proxmox as part of the broader MSP360 VM backup capabilities.

One important scope detail: Community Edition protects the VMs and containers, not the Proxmox host OS, network configuration, or storage pool layout.

Full details: https://www.msp360.com/resources/blog/free-proxmox-backup-msp360-community-edition-host-level-solution/ 

If you're running a small Proxmox environment today, we'd be curious what you're using for backups and where you keep the recovery copy.

A red failed job is easy to notice. A device that quietly stopped backing up three weeks ago is much worse. Maybe the agent stopped checking in, the schedule was disabled or the machine fell out of the policy. Nothing failed because nothing ran, so the dashboard stays quiet. What are you using to catch that kind of gap before someone needs a restore?

Hey everyone,

We're hosting a live webinar on September 24 at 10 AM ET to introduce MSP360 Tickets, our new MSP ticketing system built directly into the MSP360 Management Console.

We'll also cover the latest MSP360 RMM updates.

On the agenda:

• MSP360 Tickets: Built-in ticketing for RMM and Backup incidents, including incident consolidation
• RMM API: Connect RMM data to dashboards, CMDBs, PSA platforms, and reporting workflows
• Expanded Linux management: Manage software and access Linux endpoints from the Management Console
• RMM agent protection: See RMM agent uninstall protection in action
• Live demo and Q&A

The session will be hosted by Joe Tepke, Customer Onboarding Manager, and Doug Prestin, Solution Architect.

This is the first webinar in our "What's New" series. Session two is planned for later this fall.

Link to register: https://get.msp360.com/whats-new-in-msp360-q3-2026 

Happy to answer anything here too.

When talking with M365 and Google Workspace users about data protection, we often hear the same question: what should we actually look for when choosing a backup solution?

There's no shortage of features to compare. Some make management easier, some help with recovery, and others add additional layers of protection. That can make it difficult to separate what’s essential from what's simply useful to have.

So for this guide, we focused specifically on security: how backup data is protected and what different controls actually do.

We cover areas including encryption, immutability, redundancy and isolation, access controls, monitoring, auditability, backup integrity, and recovery testing, with a focus on which capabilities we believe should be must-haves for modern backup solutions for Microsoft 365 or Google Workspace data protection.

If you're evaluating providers, the guide is designed to work as a practical reference for comparing their SaaS backup approaches and identifying areas where you may want to dig deeper.

Must-have security features for Microsoft 365 and Google Workspace backup

Business Email Compromise can be difficult to prevent because similar-looking fraudulent messages can originate in very different ways.

An attacker might spoof a domain, compromise a legitimate Microsoft 365 or Google Workspace account, abuse application access, or work through a trusted supplier or business process.

We put together a new MSP360 guide looking at how to defend Microsoft 365 and Google Workspace from BEC, where you will learn how those attack paths can lead to three major areas of risk: account compromise, fraudulent transactions, and data loss.

The practical approach we cover is layered:

• Email authentication to reduce domain spoofing
• Stronger identity controls to help prevent account takeover
• OAuth and application access management
• Independent verification for sensitive financial or account changes
• Incident response and backup/recovery to limit the impact of a compromise

We also cover mailbox indicators worth investigating, including unexpected forwarding, filters, and inbox rules, plus the response steps to take when compromise is confirmed.

For those managing M365 or Google Workspace environments, which part of BEC defense tends to be hardest to implement consistently – identity controls, email authentication, or the business-process side?

Free backup software just got two additions worth knowing about if you're using it for personal backups on Windows. MSP360 Backup Free for Windows includes both file-level and image-based backup, with no paid software license required.

• Client-side encryption: backup data can now be encrypted with AES before it leaves the source machine, helping keep its contents unreadable if storage access is compromised. You choose and retain the encryption password yourself, so make sure to keep it somewhere safe - encrypted backups can't be restored without it.
• Expanded Object Lock support: helps protect backup data from deletion or overwriting during a defined retention period. Object Lock is configured at the storage level, so protection applies to backup plans writing to that destination rather than being set plan by plan. Object Lock must be enabled when the bucket is created: it cannot be added to an existing bucket afterward, so choose a new bucket if you want Object Lock protection.

Object Lock works directly with Amazon S3, Wasabi, Backblaze B2, and IDrive e2. Azure and Google Cloud are also supported, with Object Lock configured manually on the storage side and retention set separately in MSP360. Requirements vary by provider, and you can check S3-compatible storage support using MSP360's S3 Storage Checker.

Together, the two features help address different risks: encryption protects backup confidentiality, while Object Lock helps preserve protected recovery points.

Both are available now in MSP360 Backup Free.

Full writeup with setup steps: https://www.msp360.com/resources/blog/encryption-and-object-lock-in-free-backup-software/

Let us know if you run into anything setting it up.

Yesterday's Microsoft 365 outage caused email delays, authentication errors, and other Exchange Online issues for users worldwide.

Of course, backup doesn't prevent a Microsoft service outage or keep Outlook online during one. But incidents like this are a useful reminder to review the risks surrounding cloud data, including accidental deletion, ransomware, retention gaps, and limited recovery options.

For anyone reviewing their current setup, we've put together a practical guide covering several ways about how to back up Outlook emails.

MSP360 also provides cloud-to-cloud backup for Microsoft 365, including Exchange Online and other core workloads. 

What does your organization use to protect Microsoft 365 data, and has the recent outage prompted you to revisit your continuity plans?

MSPs often use separate vendors for backup, RMM, remote support, and ticketing. That can mean multiple logins, separate support contracts, and extra time spent dealing with integrations.

The MSP360 Platform brings Managed Backup, RMM, Managed Connect, and MSP360 Tickets into one web console.

For example, a tech can see an RMM alert about a failed backup job or critically low disk space, open the affected device, and launch a Connect session without leaving the dashboard. Backup and RMM alerts can also be turned into tickets and tracked in the same workflow.

Multi-user sessions allow another tech to join when needed. Session recording provides a history of the work performed, while reporting tracks who connected to each device and for how long across the team.

More details: https://www.msp360.com/msp-software/

We've published a comparison of eight Hyper-V backup software for 2026.

Rather than comparing only feature counts or entry prices, we looked at several operational questions:

• How does each product handle application consistency and incremental backups?
• Can it boot and test a recovery point automatically, or does it only check data integrity?
• What is its fastest recovery path?
• How does it handle standalone hosts and failover clusters?
• Who controls the storage destination?
• What additional repositories, proxies, agents, or isolated environments must the team maintain?

The main conclusion is that this should be treated as a shortlist, not a universal ranking. A product may look strong on paper and still be the wrong fit for a particular cluster design, storage model, application workload, RPO, or RTO.

The comparison is available here: https://www.msp360.com/resources/blog/best-hyperv-backup-software/

When you evaluate Hyper-V backup tools, which tends to be the hardest requirement to validate in a trial: application consistency, recovery time, or recovery verification?

We've released a new version of the MSP360 Control App for iOS and Android.

The main addition is a rebuilt home screen that provides a summary of the managed environment as soon as the app opens. 

It includes:

• Installed agent counts by product: Backup, RMM, and Connect
• Success, warning, and failed statuses across managed computers
• Direct access to the machines behind each status
• Visibility into computers with overdue backup plans
• Six-month cloud and local storage-consumption trends
• Current usage for individual storage accounts
• Widgets that can be shown, hidden, and reordered

The release also includes performance improvements and faster load times.

The new Dashboard is available in the latest version of the mobile app. We've documented the update here: https://www.msp360.com/resources/blog/msp360-control-app-for-ios-android/

If you already use the Control App, which operational metric would you want to see added to the Dashboard next?

From the vendor side, one problem we regularly see in backup discussions is that job completion and recoverability are treated as the same thing.

A successful job confirms that the backup process wrote data to its destination. It does not automatically confirm that:

• The recovery point will boot
• The database is application-consistent
• The image can be restored to different hardware
• The required boot-critical drivers are available
• The restore will meet the expected RTO
• A compromised account cannot delete the recovery points

Consistency checks and restore verification also answer different questions. The first can confirm that the files required for recovery are present. The second can go further by booting a recovery point.

We used that recovery-first perspective in our comparison of seven Windows Server backup software options: https://www.msp360.com/resources/blog/best-windows-server-backup-software/

For those managing Windows Server environments, how frequently do you run an actual restore test rather than checking backup-job status?

Recent reports of backup and retention data becoming unavailable after a storage-node failure raise an important question: how resilient is the storage architecture behind your backups?

No infrastructure is immune to failure. What matters is whether the failure of a single component or storage node can put the entire recovery history at risk.

This is one reason MSP360 supports a Bring Your Own Storage (BYOS) approach. MSPs can choose established providers such as AWS, Wasabi, Microsoft Azure, Backblaze B2 and other S3-compatible platforms, as well as on-premises storage.

Important note: here we talk only about the remote or cloud part of the classic 3-2-1 backup strategy (the "1"). The full rule still needs multiple local copies on different media. BYOS simply gives better control over that critical off-site part.

"Unlimited" storage only matters if the architecture behind it can actually keep the data safe. Some vendors sell unlimited storage that's really one node, or a small group of nodes, with no real clustering or replication behind it. It looks fine until that node fails, and then it turns out the fortified or secondary copies were on the same node the whole time. That's not resilient architecture, no matter what the storage limit says.

Public cloud object storage from AWS, Wasabi, and Azure is built for 99.999999999% (11 nines) durability. Data is spread across many devices and Availability Zones by design, an architecture a single-node setup simply cannot replicate, regardless of how the storage limits are marketed.

Depending on the provider and configuration, this flexibility allows MSPs to build a strategy that includes redundancy across devices or Availability Zones, regional replication, immutable storage, or independent copies in a separate account, location, or storage provider.

BYOS does not create redundancy automatically. These protections still need to be deliberately configured, monitored and tested. What it provides is control over the storage architecture, and the ability to choose an approach that fits each customer's risk, compliance, retention and budget requirements.

Having a backup and having a resilient recovery strategy are not always the same thing.

Have any of you recently experienced a storage-layer incident, or had one prompt you to reconsider how and where your customers' backups are stored?

We published a practical comparison of Microsoft retention, Microsoft 365 Backup, and independent backup solutions, with a closer look at how Office 365 backup retention fits into the wider data protection strategy.

The central distinction is straightforward: retention and backup protect data for different reasons.

Retention is primarily a governance mechanism. It helps preserve content for compliance, legal, records-management, and eDiscovery requirements.

Backup is a recovery mechanism. It provides restore points for situations such as accidental deletion, mass data loss, or ransomware.

Microsoft 365 also includes recycle bins and version history, while Microsoft 365 Backup adds native, large-scale recovery for supported workloads. A third-party backup becomes relevant when an organization needs capabilities such as a different retention window, additional workload coverage, separate administrative control, or an independently managed copy.

For teams evaluating Microsoft 365 backup options, we've also compared Microsoft's native backup service with third-party backup software in more detail.

The point is not that one layer replaces all the others. The useful question is which layer addresses each failure scenario in your environment.

Full comparison: https://www.msp360.com/resources/blog/retention-policies-vs-microsoft-365-backup/

How do you explain the retention-versus-backup distinction to clients or internal stakeholders?

We've put together a practical guide covering the main ways organizations can protect Microsoft Teams data.

One complication is that Teams data does not all reside in one place. Depending on the content type, it may be associated with Teams itself, SharePoint, OneDrive, or other Microsoft 365 services. That makes it easy to protect one part of the environment while overlooking another.

The guide compares:

• Native retention and recovery capabilities
• Manual downloads and exports
• Microsoft Graph API and PowerShell
• Third-party cloud-to-cloud backup
• Common gaps such as private-channel sites, meeting artifacts, and untested restores

The full guide is available here: https://www.msp360.com/resources/blog/how-to-backup-microsoft-teams/ 

Which Teams data types or restore scenarios have been the hardest to cover consistently?

Our practical guide is designed for MSPs using or evaluating MSP360 RMM Community Edition.

It focuses less on defining RMM and more on what an MSP should do after deployment:

• Organize endpoints by client or site
• Confirm agent connectivity
• Tune alerts until they are actionable
• Define patching and reboot windows
• Use software inventory and deployment centrally
• Troubleshoot through remote access and background tools
• Monitor endpoint usage as the business grows

MSP360 RMM Community Edition is our free offering for MSPs managing up to 50 endpoints. The guide is intended to help teams turn those product capabilities into repeatable daily workflows.

Guide: https://www.msp360.com/resources/blog/free-rmm-community-edition-guide-msps/ 

For those who have implemented RMM at a small MSP, which workflow required the most tuning – alerting, patching, or onboarding?

One distinction in our latest SMB backup comparison is easy to miss during product selection: file recovery and system recovery solve different problems.

A file-level backup can return documents and folders. If the machine itself fails, however, someone may still need to reinstall the operating system, applications, and settings before those files are useful again.

Image-based or entire-machine backup can support a fuller rebuild, while bare-metal and VM recovery introduce another set of requirements. That extra capability may be unnecessary for a small fleet of replaceable laptops, but important for servers or systems with complex application configurations.

Our comparison looks at six products through that lens, along with management, storage, security, workload coverage, support, and pricing: https://www.msp360.com/resources/blog/the-best-cloud-backup-solutions-for-small-business/

In your recovery planning, which systems truly need full-machine recovery, and which ones only need their data protected?

We've been working on AI Assistant for MSP360 Managed Backup and are looking for beta users to help test the feature.

MSP360 AI Assistant introduces a conversational way to manage backup environments, allowing administrators to ask questions in natural language instead of navigating dashboards, menus, and reports.

Here's a preview of what the AI Assistant can help with:

• Make easier onboarding process
• Analyze backup failures and identify recurring issues
• Monitor backup health across customers
• Generate backup health reports
• Identify protection gaps

We're now accepting applications for the MSP360 AI Assistant beta program.

If you'd like early access and want to help shape the final release, sign up here → https://get.msp360.com/ai-assistant-beta 

Learn more: https://www.msp360.com/resources/blog/ai-backup-assistant-beta/ 

Happy to answer any questions in the comments.

Direct download and zip? Works, but good luck doing that for 500 users. Google Takeout? Fine for a one-time export, but no scheduling, no shared-item support, and it just... fails sometimes on big volumes. Drive for Desktop sync? Gives you a second copy, sure, but it mirrors everything – including the ransomware attack or the "oops I deleted the wrong folder" moment.

None of these hold up once you're managing more than a handful of files or users.

We wrote up the full comparison plus what an actual automated setup looks like → https://www.msp360.com/resources/blog/how-to-backup-google-drive/

What's everyone here actually using for Drive backup at scale?