Hi ​@jkunysz - yeah...there’s no real migration from Agents to VM-based backups even for Veeam’s native hypervisors (VMW and HV). Unless you have a need to move them (aside from less complexity..which I get), you can just continue to back those systems up with an Agent. It sounds like those VMs are Scale VMs? About the only thing you can do I know of is create a new Backup Job of those VMs to start from scratch. You could of course keep the Agent Backups for a time to cover your Retention until your VM-based Backup Jobs meet your Retention, then delete those Agent Restore Points to recover Repository space.

Best.

I appreciate the quick response. Yes, these are Scale VM’s. I did think about creating new backup jobs using the Scale plugin and letting the Windows Agent jobs age out but I figured it’d be worth asking about any migration path.

Also, I don’t think there would be any issues running Agent jobs and Scale plugin jobs but want to ensure before I install the Scale plugin on my production environment. I don’t have a lab Scale array so, I only installed the Scale plugin on a cloned copy of my production B&R server to validate the install process.

Yeah...no way to do what you’re wanting I can think of.

The Plugin should not affect anything. If it’s like other Plugins I’ve looked at, it just provides a several areas “Scale” options in VBR to backup those hypervisor-specific VMs. The XCP-ng Plugin install (currently only in Public Beta), for example, was really lightweight and just added menus to VBR specific for XCP-ng backup.

Yeah..no issue at all running Agents until your VM backups catch up to your Retention. Of course doesn’t hurt to check/verify 😊

Coolsports, thanks again. It’s always easier to ask a question than recover from a failure. :-)

​@jkunysz - no problem...for sure!..glad to help out😊